CN117178508A - Out-of-order hybrid automatic repeat request (HARQ) transmission in the presence of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH) - Google Patents

Abstract

Certain aspects of the present disclosure provide a method for wireless communication by a User Equipment (UE). The UE determines that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol. The UE reports, defers, or discards HARQ feedback for the first SPS PDSCH in response to the determination if resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID.

Description

Out-of-order hybrid automatic repeat request (HARQ) transmission in the presence of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH)

Cross Reference to Related Applications

The present application claims priority from U.S. application Ser. No.17/659,323, filed on 4.14 at 2022, which claims the benefit of U.S. provisional application Ser. No.63/175,512, filed on 15 at 4.2021, the entire contents of both of which are hereby incorporated by reference.

Technical Field

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for managing hybrid automatic repeat request (HARQ) transmissions.

Introduction to the invention

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power). Examples of such multiple-access techniques 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.

In some examples, a wireless multiple-access communication system may include several base stations, each supporting communication for multiple communication devices (otherwise referred to as User Equipment (UE)) simultaneously. In a Long Term Evolution (LTE) or LTE-advanced (LTE-a) network, a set of one or more base stations may define an evolved node B (eNB). In other examples (e.g., in next generation or 5G networks), a wireless multiple access communication system may include a number of Distributed Units (DUs) (e.g., edge Units (EUs), edge Nodes (ENs), radio Heads (RH), smart Radio Heads (SRHs), transmission Reception Points (TRPs), etc.) in communication with a number of Central Units (CUs) (e.g., central Nodes (CNs), access Node Controllers (ANCs), etc.), wherein a set of one or more distributed units in communication with a central unit may define an access node (e.g., a new radio base station (NR BS), a new radio node B (NR NB), a network node, a 5G NB, a gNB, etc.). The base station or DU may communicate with the set of UEs on a downlink channel (e.g., for transmission from or to the base station) and an uplink channel (e.g., for transmission from or to the base station or the distributed unit).

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example of an emerging telecommunication standard is New Radio (NR), e.g. 5G radio access. NR is an enhanced set of LTE mobile standards promulgated by the third generation partnership project (3 GPP). It is designed to better support mobile broadband internet access by using OFDMA with Cyclic Prefix (CP) on Downlink (DL) and Uplink (UL) and supporting beamforming, multiple Input Multiple Output (MIMO) antenna technology and carrier aggregation to improve spectral efficiency, reduce cost, improve service, utilize new spectrum, and integrate better with other open standards.

Despite the tremendous technological advances made over the years in wireless communication systems, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between a wireless transmitter and a wireless receiver. Accordingly, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of use of shared communication media, reducing the power used by transmitters and receivers in performing communications, improving the reliability of wireless communications, avoiding redundant transmission and/or reception and associated processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access a wireless communication system, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available, and so forth. Accordingly, there is a need for further improvements in wireless communication systems to overcome the foregoing technical challenges and others.

SUMMARY

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for managing out-of-order hybrid automatic repeat request (HARQ) transmissions in the presence of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH).

Certain aspects of the present disclosure provide a method for wireless communication by a User Equipment (UE). The method generally includes determining that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol; and in response to the determination, reporting, deferring, or discarding the ARQ feedback for the first SPS PDSCH if resources for reporting HARQ feedback for the first SPS PDSCH are not available until a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID or thereafter.

Certain aspects of the present disclosure provide a method for wireless communication by a network entity. The method generally includes transmitting a first SPS Physical Downlink Shared Channel (PDSCH) of a first HARQ process ID to the UE; transmitting a second PDSCH of the same first HARQ process ID to the UE before receiving HARQ feedback for the first SPS PDSCH from the UE; receiving HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH; and deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform one or more of the methods described previously and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the foregoing methods, as well as those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the foregoing methods and those described elsewhere herein; and apparatus comprising means for performing the foregoing methods, as well as those methods described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or a processing system cooperating over one or more networks.

For purposes of illustration, the following description and the annexed drawings set forth certain features.

Brief Description of Drawings

The drawings depict certain features of the aspects described herein and are not intended to limit the scope of the disclosure.

Fig. 1 is a block diagram conceptually illustrating an example wireless communication network in accordance with certain aspects of the present disclosure.

Fig. 2 is a block diagram illustrating an example logical architecture of a distributed Radio Access Network (RAN) in accordance with certain aspects of the present disclosure.

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

Fig. 4 is a block diagram conceptually illustrating a design of an example Base Station (BS) and User Equipment (UE) in accordance with certain aspects of the present disclosure.

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

Fig. 6 illustrates an example of a frame format for a New Radio (NR) system in accordance with certain aspects of the present disclosure.

Fig. 7 illustrates an example of semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) occasions that may be used to activate Configured Grant (CG) occasions, in accordance with certain aspects of the disclosure.

Fig. 8 illustrates an example timeline of deferring hybrid automatic repeat request (HARQ) feedback until a first available Physical Uplink Control Channel (PUCCH) resource, in accordance with certain aspects of the present disclosure.

Fig. 9 illustrates an example timeline of delayed HARQ feedback in accordance with aspects of the present disclosure.

Fig. 10 is a flowchart of example operations that may be performed by a UE in accordance with aspects of the present disclosure.

Fig. 11 is a flowchart of example operations that may be performed by a network entity in accordance with aspects of the present disclosure.

Fig. 12 illustrates an example timeline of deferral times before a next HARQ instance, in accordance with aspects of the present disclosure.

Fig. 13 illustrates a communication device that can include various components configured to perform operations for the techniques disclosed herein, in accordance with aspects of the disclosure.

Fig. 14 illustrates a communication device that may include various components configured to perform operations for the techniques disclosed herein, in accordance with aspects of the present disclosure.

Fig. 15 depicts an example split BS architecture.

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

Detailed Description

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for managing out-of-order hybrid automatic repeat request (HARQ) transmissions in the case of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH).

In some cases, to handle collisions of the same HARQ process due to deferred SPS HARQ acknowledgements (HARQ-ACKs), one or more techniques for managing out-of-order HARQ transmissions are implemented. For example, when a User Equipment (UE) receives a Physical Downlink Shared Channel (PDSCH) of a particular HARQ process Identifier (ID), deferred SPS HARQ bit(s) for that HARQ process ID are discarded based on one or more techniques described herein. In other words, deferred HARQ bits (e.g., first HARQ bits) may be initially stored, however, when new HARQ bits (e.g., second HARQ bits) associated with the same HARQ process are available, the first HARQ bits are no longer stored but discarded. Accordingly, in this case, the UE does not report the first HARQ bit because the first HARQ bit is discarded. The techniques described herein provide for higher reliability and lower latency communications.

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for a New Radio (NR) (e.g., NR access technology or 5G technology). NR may support various wireless communication services such as enhanced mobile broadband (emmbb) targeting a wide bandwidth (e.g., over 80 MHz), millimeter wave (mmW) targeting a high carrier frequency (e.g., 60 GHz), large-scale MTC (mctc) targeting non-backward compatible MTC technology, and/or critical tasks targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different Transmission Time Intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services may coexist in the same subframe.

Certain multi-beam wireless systems, such as mmW systems, bring gigabit speeds to cellular networks due to the availability of large amounts of bandwidth. However, the unique challenges of severe path loss faced by millimeter wave systems require new technologies such as hybrid beamforming (analog and digital), which are not present in 3G and 4G systems. Hybrid beamforming may enhance the link budget/signal-to-noise ratio (SNR) available during RACH.

In such systems, a Node B (NB) and a User Equipment (UE) may communicate using beamformed transmissions. In order for beamforming to work properly, the NB may need to monitor the beam using beam measurements performed at the UE (e.g., based on reference signals transmitted by the NB) and generated feedback. However, since the direction of the reference signal is unknown to the UE, the UE may 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 measurements (e.g., to determine the best Rx beam for a given NB Tx beam), the UE may incur significant measurement delay and battery life impact. Furthermore, the resource efficiency of having to sweep through all Rx beams is very low. Accordingly, aspects of the present disclosure provide techniques to assist UEs in performing measurements of serving and neighboring cells when using Rx beamforming.

The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Moreover, features described with reference to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using such structure, functionality, or both as a complement to, or in addition to, the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims. The term "exemplary" 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.

The techniques described herein may 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 may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may implement radio technologies 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 parts of Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology being developed in conjunction with the 5G technology forum (5 GTF). 3GPP Long Term Evolution (LTE) and LTE-advanced (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a and GSM are described in the literature from an organization named "third generation partnership project" (3 GPP). cdma2000 and UMB are described in literature from an organization named "third generation partnership project 2" (3 GPP 2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terms commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure may be applied in other generation-based communication systems (such as 5G and offspring) including NR technologies.

Example Wireless communication network

The techniques and methods described herein may be used for various wireless communication networks. Although aspects may be described herein using terms commonly associated with 3G, 4G, and/or 5G wireless technologies, aspects of the disclosure may be equally applicable to other communication systems and standards not explicitly mentioned herein.

Fig. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be implemented. For example, according to certain aspects, the wireless communication network 100 may include a network entity (e.g., a Base Station (BS) 110) and/or a User Equipment (UE) 120) for managing out-of-order hybrid automatic repeat request (HARQ) transmissions in the case of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH). As shown in fig. 1, UE 120a includes HARQ manager 122 and BS110a includes HARQ manager 112.HARQ manager 122 is configured to perform operation 1000 of fig. 10. HARQ manager 112 is configured to perform operation 1100 of fig. 11.

As illustrated in fig. 1, wireless communication network 100 may include several BSs 110 and other network entities. According to one example, network entities (including BSs and UEs) may communicate using beams on high frequencies (e.g., >6 GHz).

BS110 may be a station in communication with a UE. Each BS110 may 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 an NR system, the terms "cell" and gNB, node B, 5GNB, AP, NR BS, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected with each other and/or to one or more other base stations or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. RATs may also be referred to as radio technologies, air interfaces, etc. The frequency may also be referred to as a carrier wave, frequency channel, etc. Each frequency may support a single RAT in a given geographical area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

BS110 may provide communication coverage for macro cells, pico cells, femto cells, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG), UEs 120 for users in a residence, etc.). BS110 for a macro cell may be referred to as a macro BS. BS110 for a pico cell may be referred to as a pico BS. The BS110 for a femto cell may be referred to as a femto BS or a home BS. In the example shown in fig. 1, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS110x may be a pico BS for pico cell 102 x. BSs 110y and 110z may be femto BSs for femtocells 102y and 102z, respectively. BS110 may support one or more (e.g., three) cells.

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

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

The wireless communication network 100 may support synchronous or asynchronous operation. For synchronous operation, each BS110 may have similar frame timing, and transmissions from different BSs 110 may be approximately aligned in time. For asynchronous operation, each BS110 may have different frame timing and transmissions from different BSs 110 may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

Network controller 130 may be coupled to a set of BSs 110 and provide coordination and control of these BSs 110. Network controller 130 may communicate with BS110 via a backhaul. BS110 may also communicate with each other directly or indirectly, e.g., via a wireless or wired backhaul.

UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer Premise Equipment (CPE), cellular telephone, smart phone, personal Digital Assistant (PDA), wireless modem, wireless communication device, handheld device, laptop, cordless telephone, wireless Local Loop (WLL) station, tablet device, camera, gaming device, netbook, smartbook, superbook, medical device or equipment, biometric sensor/device, wearable device (such as a smartwatch, smart garment, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart necklace, etc)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter/sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium. Some UEs may be considered as evolved or Machine Type Communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, gauges, monitors, location tags, etc., which may communicate with BS110, another device (e.g., a remote device), or some other entity. The wireless node may provide connectivity to or to a network (e.g., a wide area network such as the internet or a cellular network), for example, via a wired or wireless communication link. Some UEs 120 may be considered internet of things (IoT) devices.

In fig. 1, the solid line with double arrows indicates the desired transmission between UE 120 and serving BS110, which serving BS110 is the BS110 designated to serve UE 120 on the downlink and/or uplink. The dashed lines with double arrows indicate interfering transmissions between UE 120 and BS110.

Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into a plurality of (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, the modulation symbols are transmitted in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing of the subcarriers may be 15kHz, while the minimum resource allocation (referred to as a 'resource block') may be 12 subcarriers (or 180 kHz). Thus, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for a system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may also be divided into sub-bands. For example, a subband may cover 1.08MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20MHz, respectively.

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

NR may utilize OFDM with CP on uplink and downlink and include support for half duplex operation using TDD. A single component carrier bandwidth of 100MHz may be supported. The NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75kHz over a 0.1ms duration. In one aspect, each radio frame may include 50 subframes having a length of 10 ms. Thus, each subframe may have a length of 0.2 ms. In another aspect, each radio frame may include 10 subframes having a length of 10ms, where each subframe may have a length of 1 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction of each subframe may be dynamically switched. Each subframe may include DL/UL data and DL/UL control data. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configuration in DL may support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE 120. Multi-layer transmissions of up to 2 streams per UE may be supported. Up to 8 serving cells may be used to support aggregation of multiple cells. Alternatively, the NR may support a different air interface than OFDM based. An NR network may comprise entities such as CUs and/or DUs.

In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., BS 110) allocates resources for communication among some or all devices and equipment within its service area or cell. Within this disclosure, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities, as discussed further below. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. BS110 is not the only entity that can act as a scheduling entity. That is, in some examples, UE 120 may act as a scheduling entity to schedule resources for one or more subordinate entities (e.g., one or more other UEs 120). In this example, the UE 120 is acting as a scheduling entity, and other UEs 120 utilize resources scheduled by the UE 120 for wireless communication. UE 120 may act as a scheduling entity in a peer-to-peer (P2P) network and/or in a mesh network. In a mesh example, UEs 120 may optionally communicate directly with each other in addition to communicating with the scheduling entity.

Thus, in a wireless communication network having scheduled access to time-frequency resources and having cellular, P2P, and mesh configurations, a scheduling entity and one or more subordinate entities may utilize the scheduled resources to communicate.

As mentioned above, the RAN may include CUs and DUs. NR BSs (e.g., gNB, 5G B node, node B, transmission-reception point (TRP), access Point (AP)) may correspond to one or more BSs 110. The NR cell may be configured as an access cell (ACell) or a data only cell (DCell). For example, the RAN (e.g., a central unit or a distributed unit) may configure the cells. The DCell may be a cell used for carrier aggregation or dual connectivity but not for initial access, cell selection/reselection, or handover. In some cases, the DCell may not transmit a synchronization signal, in some cases, the DCell may transmit an SS. NR BS110 may transmit a downlink signal indicating a cell type to UE 120. Based on the cell type indication, UE 120 may communicate with NR BS110. For example, UE 120 may determine NR BS110 to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

In various aspects, BS110 (or network node) may be implemented as an aggregated BS, a split BS, an Integrated Access and Backhaul (IAB) node, a relay node, or a sidelink node, to name a few. Fig. 15, discussed in further detail later in this disclosure, depicts an example split BS architecture.

Fig. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN) 200, which may be implemented in the wireless communication system illustrated in fig. 1. The 5G access node 206 may include an Access Node Controller (ANC) 202. The ANC may be a Central Unit (CU) of the distributed RAN 200. The backhaul interfaces to the next generation core network (NG-CN) 204 (e.g., which is associated with the 5G control plane (5G C-plane) 212 and the 5G gateway (5G-GW) 214) may terminate at the ANC. The backhaul interface to the neighboring next generation access node (NG-AN) may terminate at the ANC. ANC may include one or more TRP 208a, 208B, 208c (which may also be referred to as BS, NR BS, node B, 5G NB, AP, or some other terminology). As above, TRP may be used interchangeably with "cell".

TRP 208a, 208b, 208c may be DUs. TRP 208a, 208b, 208c may 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, TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRPs 208a, 208b, 208c may be configured to service traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

The distributed RAN 200 may be used to illustrate forward (fronthaul) definitions. The architecture may be defined to support outbound solutions across different deployment types. For example, the architecture may be based on transport network capabilities (e.g., bandwidth, latency, and/or jitter).

The architecture may share features and/or components with LTE. According to aspects, a next generation AN (NG-AN) 210 may support dual connectivity with AN NR. For LTE and NR, NG-AN may share a common round trip.

The architecture may enable collaboration between and among the TRPs 208a, 208b, 208 c. For example, the collaboration may be preset within the TRP 208a, 208b, 208c and/or across the TRP 208a, 208b, 208c via the ANC 202. According to aspects, an inter-TRP interface may not be required/present.

According to aspects, dynamic configuration of split logic functions may exist within the distributed RAN 200. As will be described in more detail with reference to fig. 5, a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer may be adaptively placed at a DU or CU (e.g., at TRP or ANC, respectively). According to certain aspects, the BS may include a Central Unit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g., one or more TRPs 208).

Fig. 3 illustrates an example physical architecture of a distributed RAN 300 in accordance with aspects of the present disclosure. A centralized core network unit (C-CU) 302, e.g., associated with a 5G control plane 308 and a 5G-GW 310 associated with a Mobile Radio (MR) Communication Network (CN) 312, may host core network functions. C-CU 302 can be deployed centrally. The C-CU functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

A centralized RAN unit (C-RU) 304 (e.g., associated with MR Access Networks (AN) 314 and 5g AN 316) may host one or more ANC functions. Optionally, the C-RU 304 may host the core network functions locally. The C-RU 304 may have a distributed deployment. The C-RU 304 may be closer to the network edge.

DU 306 (e.g., 306a, 306b, or 306 c) may host one or more TRPs (edge node (EN), edge Unit (EU), radio Head (RH), smart Radio Head (SRH), etc.). DU 306 may be at the edge of a network with Radio Frequency (RF) functionality.

Fig. 4 illustrates example components of a network entity (e.g., BS110 a) and UE 120a (e.g., in wireless communication network 100 of fig. 1).

At BS110a, transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be used for a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), a group common PDCCH (GC PDCCH), and the like. The data may be used for a Physical Downlink Shared Channel (PDSCH) or the like. A medium access control-control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel, such as PDSCH, physical Uplink Shared Channel (PUSCH), or physical side link shared channel (PSSCH).

Transmit processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 420 may also generate reference symbols, such as for a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a channel state information reference signal (CSI-RS). A transmit multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to Modulators (MODs) 432a-432t in the transceiver. Each MOD 432a-432t in a transceiver can process a respective output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM), etc.) to obtain a stream of output samples. Each MOD in transceivers 432a-432t can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a Downlink (DL) signal. DL signals from MODs 432a-432t in a transceiver may be transmitted via antennas 434a-434t, respectively.

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

On the Uplink (UL), at UE 120a, a transmit processor 464 may receive and process data from a data source 462 (e.g., for PUSCH) and control information from a controller/processor 480 (e.g., for a Physical Uplink Control Channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal, e.g., a Sounding Reference Signal (SRS). The symbols from transmit processor 464 may be precoded by a transmit MIMO processor 466 if applicable, further processed by the MOD in transceivers 454a-454r (e.g., for SC-FDM, etc.), and transmitted to BS110 a. At BS110a, the UL signal from UE 120a may be received by antenna 434, processed by DEMOD 432 in the transceiver, detected by MIMO detector 436 if applicable, and further processed by receive processor 438 to obtain decoded data and control information sent by UE 120 a. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to the controller/processor 440.

Memories 442 and 482 may store data and program codes for BS110a and UE 120a, respectively. Scheduler 444 may schedule UE 120a for data transmission on DL and/or UL.

The antenna 452, processors 466, 458, 464 and/or controller/processor 480 of UE 120a, and/or the antenna 434, processors 420, 430, 438 and/or controller/processor 440 of BS110a may be used to perform the various techniques and methods described herein. For example, as shown in fig. 4, controller/processor 440 of BS110a has HARQ manager 441 that may be configured to perform the operations illustrated in fig. 11, as well as other operations disclosed herein. As shown in fig. 4, the controller/processor 480 of UE 120a has a HARQ manager 481 that may be configured to perform the operations illustrated in fig. 10, as well as other operations disclosed herein. Although shown at a controller/processor, other components of UE 120a and BS110a may also be used to perform the operations described herein.

NR may utilize OFDM with Cyclic Prefix (CP) on UL and DL. NR may support half-duplex operation using Time Division Duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into a plurality of orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. The modulation symbols may be transmitted with OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers may depend on the system bandwidth. The minimum resource allocation, referred to as a Resource Block (RB), may be 12 consecutive subcarriers. The system bandwidth may also be divided into sub-bands. For example, one subband may cover multiple RBs. The NR may support a 15KHz base subcarrier spacing (SCS) and may define other SCSs (e.g., 30kHz, 60kHz, 120kHz, 240kHz, etc.) with respect to the base SCS.

Fig. 5 illustrates a diagram 500 showing an example for implementing a communication protocol stack in accordance with aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a 5G system. 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 may 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. The co-located and non-co-located implementations may be used for network access devices (e.g., AN, CU, and/or DU) or UEs, for example, in a protocol stack.

A first option 505-a illustrates a split implementation of a protocol stack, wherein the implementation of the protocol stack is split between a centralized network access device (e.g., ANC 202 in fig. 2) and a distributed network access device (e.g., DU in fig. 2). In the first option 505-a, the RRC layer 510 and PDCP layer 515 may be implemented by a central unit, and the RLC layer 520, MAC layer 525 and PHY layer 530 may be implemented by DUs. In various examples, a CU and a DU may be co-located or non-co-located. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

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

Regardless of whether the network access device implements part or all of the protocol stack, at 505c the ue may implement the entire protocol stack (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530).

Fig. 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 through 9, each subframe being 1ms. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing. An index may be assigned for the symbol period in each slot. Mini-slots (which may be referred to as sub-slot structures) refer to transmission time intervals having a duration (e.g., 2, 3, or 4 symbols) that is less than a slot.

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

In NR, a Synchronization Signal (SS) block is transmitted. The SS block includes PSS, SSs and two symbol PBCH. The SS blocks may be transmitted in fixed slot positions, such as symbols 0-3 shown in fig. 6. PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half frame timing and the SS may provide CP length and frame timing. PSS and SSS may provide cell identity. The PBCH carries some basic system information such as downlink system bandwidth, timing information within the radio frame, SS burst set periodicity, system frame number, etc. SS blocks may be organized into SS bursts to support beam sweep. Further system information, such as Remaining Minimum System Information (RMSI), system Information Blocks (SIBs), other System Information (OSI), may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

The UE may operate in various radio resource configurations, including configurations associated with transmitting pilots using a dedicated set of resources (e.g., radio Resource Control (RRC) dedicated state, etc.), or configurations associated with transmitting pilots using a common set of resources (e.g., RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a set of dedicated resources for transmitting pilot signals to the network. While operating in the RRC shared state, the UE may select a set of shared resources for transmitting pilot signals to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices (such as DUs, or portions thereof). Each receiving network access device may be configured to receive and measure pilot signals transmitted on a common set of resources and also to receive and measure pilot signals transmitted on a dedicated set of resources allocated to a UE for which the network access device is a member of a monitoring network access device set. The one or more recipient network access devices or CUs to which the recipient network access devices transmit pilot signal measurements may use these measurements to identify or initiate a change to the serving cell of the UE.

Example semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) configuration

Semi-persistent scheduling (Semi-persistently scheduled) or Semi-persistent scheduling (Semi-persistent scheduling) (SPS) resource allocation, sometimes referred to as configured downlink assignment, refers to a scheduling technique in which User Equipment (UE) is preconfigured with periodicity and offset by a network entity (e.g., eNB, gNB, etc.).

As illustrated in fig. 7, once preconfigured, if the UE is to receive an allocation of downlink resources, the allocation of SPS opportunities will repeat according to the preconfigured periodicity resulting in periodic SPS opportunities. For SPS, a network entity may use Radio Resource Control (RRC) signaling to define the periodicity of configured downlink assignments. Similarly, once configured with Configured Grant (CG) opportunities, allocation of CG opportunities may be repeated according to a preconfigured periodicity.

As used herein, the term occasion refers to a time in which resources are allocated for a transmission that may or may not ultimately occur. For example, downlink transmissions may or may not occur in SPS opportunities. Similarly, uplink (UL) transmissions may or may not occur in CG occasions. If transmissions are likely to occur, the opportunities may be considered activated and thus those opportunities should be monitored.

Example hybrid automatic repeat request (HARQ) delay for SPS PDSCH

The New Radio (NR) may provide support for Downlink (DL) semi-persistent scheduling (SPS) for periodic traffic. For a Time Division Duplex (TDD) system (e.g., in release 15 and/or release 16), if the time slot scheduled for reporting hybrid automatic repeat request (HARQ) feedback for SPS is a DL time slot, or overlaps at least one DL symbol, then the User Equipment (UE) will not transmit HARQ feedback. This may result in waste of system resource(s) because the network entity (e.g., a Base Station (BS) such as the gNB) may need to retransmit the SPS Physical Downlink Shared Channel (PDSCH) again due to missing HARQ reports.

The overlap may be due to various reasons. For example, DL slots/symbols may be semi-statically configured as DL, or slots/symbols may be converted from semi-static "flexible" to DL (or "dynamic flexible") by dynamic Slot Format Indicators (SFIs) or dynamic DL Control Information (DCIs), e.g., DL grants scheduling PDSCH or grants scheduling aperiodic channel state information reference signal (CSI-RS) transmissions.

In some cases (e.g., in NR release 17), HARQ feedback for SPS PDSCH may be enhanced by delaying HARQ feedback that conflicts with DL symbols/slots (or "dynamic flexible" symbols) to later Uplink (UL) symbols/slots. For example, if an SPS HARQ-ACK cannot be transmitted in the first slot or sub-slot of a scheduled Physical Uplink Control Channel (PUCCH) occasion due to collision with a DL symbol/slot, the SPS HARQ-ACK may be delayed (deferred) to the next (or later) UL slot or sub-slot.

In some cases, when a slot scheduled to report HARQ feedback for SPS overlaps/conflicts with DL symbols, as illustrated in fig. 8, HARQ feedback may be deferred until a first available/valid PUCCH resource. This may be done using already configured SPS PUCCH resources. In some cases, the slot format change may occur according to a pattern defined in an Information Element (IE), such as, for example, a slot format combination per cell (sfc) for example. Also, SPS PUCCH a/N may indicate PUCCH format 0 (1 bit). Thus, the first UL PUCCH resource may correspond to the first available UL symbol. Also, in this case, there may be no multiplexing with other PUCCH transmissions from the same UE.

The example in fig. 9 may assume that ultra-reliable low latency communication (URLLC) traffic periodicity is 1ms, sps configuration indicates 2 DL symbols and periodicity is 1ms, DL packet expiration is 1ms, and k1_def_max (k1_deferral_max) is 2ms.

In this example scenario, when the UE receives a new SPS PDSCH from the network entity, the slot for reporting HARQ feedback for that SPS PDSCH is assumed to be k1 slots later. However, when resources for reporting HARQ feedback for an earlier SPS PDSCH are not available until when or after the HARQ feedback is scheduled to transmit HARQ feedback for a new PDSCH, there may be a problem of how to report HARQ feedback or what HARQ feedback is to report. In such a case, PUCCH may be available only for new HARQ feedback (e.g., because insufficient UL resources are available for HARQ feedback/deferred HARQ bits for the earlier SPS PDSCH) (i.e., k1_def (k1_deferred) is less than k1_def_max). In this case, when the UE sends HARQ feedback for the new SPS PDSCH to the network entity, the network entity may not know which PDSCH is being acknowledged (e.g., where they share the same HARQ process ID).

Example deferral time before next HARQ instance

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable media for managing out-of-order hybrid automatic repeat request (HARQ) transmissions in the case of deferred semi-persistent scheduling (SPS) Physical Uplink Control Channel (PUCCH) HARQ.

For example, to handle collisions of the same HARQ process due to deferred SPS HARQ acknowledgements (HARQ-ACKs), one or more techniques for managing out-of-order HARQ transmissions are implemented. Based on one or more techniques described herein, when a User Equipment (UE) receives a Physical Downlink Shared Channel (PDSCH) of a particular HARQ process Identifier (ID), deferred SPS HARQ bit(s) for that HARQ process ID are discarded. The techniques described herein provide for higher reliability and lower latency communications.

Fig. 10 is a flowchart illustrating example operations 1000 for wireless communication in accordance with certain aspects of the present disclosure. The operations 1000 may be performed, for example, by a User Equipment (UE) (e.g., such as the UE 120a of fig. 1). The operations 1000 may be implemented as software components executing and running on one or more processors (e.g., the controller/processor 480 of fig. 4). Further, the signal transmission and reception by the UE in operation 1000 may be implemented, for example, by one or more antennas (e.g., antenna 452 of fig. 4). In certain aspects, signal transmission and/or reception by the UE may be achieved via a bus interface of one or more processors (e.g., controller/processor 480) to obtain and/or output signals.

Operation 1000 begins at block 1002 with determining that a scheduled occasion for reporting HARQ feedback for a first SPS Physical Downlink Shared Channel (PDSCH) for a first HARQ process Identifier (ID) overlaps with at least one Downlink (DL) symbol or flexible symbol. For example, the UE may use the processor of UE 120a shown in fig. 1 or fig. 4 and/or the processor of the apparatus shown in fig. 13 to determine that the scheduled occasion for reporting HARQ feedback for the first SPS PDSCH of the first HARQ process ID overlaps with the at least one DL symbol or flexible symbol.

At 1004, the UE reports, defers, or discards HARQ feedback for the first SPS PDSCH in response to the determination if resources for reporting HARQ feedback for the first SPS PDSCH are not available until a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID or later. For example, the UE may use the processor of UE 120a shown in fig. 1 or fig. 4 and/or the processor of the apparatus shown in fig. 13 to report, defer, or discard HARQ feedback for the first SPS PDSCH if resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID.

In certain aspects, deferred HARQ information bits (e.g., associated with a first HARQ process ID) are stored until new HARQ information bits from the same HARQ process ID (e.g., new HARQ information bits associated with the first HARQ process ID) are available. This means that when there is a first available PDSCH resource and there is a list of N HARQ process IDs, the deferred HARQ information bits replaced by new HARQ information bits are not reported.

In some aspects, the UE may discard HARQ feedback for the first SPS PDSCH (e.g., where resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH for the same first HARQ process ID).

In some aspects, the UE may not be available to report, defer, or discard HARQ feedback for the first SPS PDSCH based on resources used to report HARQ feedback for the first SPS PDSCH until a threshold amount of time after the scheduled opportunity to report the HARQ feedback.

In some aspects, the UE may not be available to report, defer, or discard HARQ feedback for the first SPS PDSCH until at or after an opportunity to report HARQ feedback for a subsequent SPS PDSCH based on resources used to report the HARQ feedback.

In some aspects, the UE may include sending a request to the network entity to not send a dynamic grant for PDSCH transmissions having the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred. If granted, the request may avoid the problem of the UE reporting out-of-order HARQ feedback for PDSCH with the same HARQ process ID. In other words, the UE requests that the same HARQ process ID (same HARQ process ID as used for the HARQ process experiencing deferred SPS) is not scheduled for the new dynamic grant PDSCH.

In certain aspects, the second PDSCH may be scheduled via dynamic grants. In some cases, the UE may discard HARQ feedback for the first SPS PDSCH. For example, the UE may stop deferring SPS PUCCH HARQ until the time of PUCCH HARQ transmission for the new dynamic grant PDSCH (i.e., the UE discards the deferred SPS PUCCH HARQ bits).

In some cases, the UE may report the HARQ feedback with an indication of whether the HARQ feedback is for the first SPS PDSCH or for the dynamically grant scheduled PDSCH. For example, the UE may add a bit indicating that HARQ corresponds to dynamic grant PDSCH or SPS PDSCH.

In some cases, the UE may report HARQ feedback for the first SPS PDSCH along with an indication that the HARQ feedback is out of order. For example, the UE may add a bit indicating that HARQ feedback is out of order.

In some cases, the UE may report HARQ feedback for the first SPS PDSCH along with an indication of the DL slot or sub-slot in which the first SPS PDSCH was received. For example, the UE may add a field with the DL (sub) slot number of PDSCH reception.

Fig. 11 is a flow chart illustrating example operations 1100 for wireless communications in accordance with certain aspects of the present disclosure. For example, operation 1100 may be performed by a network entity, such as Base Station (BS) 110a of fig. 1, for example. The operations 1100 may be implemented as software components executing and running on one or more processors (e.g., the controller/processor 440 of fig. 4). Further, the signal transmission and reception by the network entity in operation 1100 may be implemented, for example, by one or more antennas (e.g., antenna 434 of fig. 4). In certain aspects, signal transmission and/or reception by the network entity may be achieved via bus interfaces of one or more processors (e.g., controller/processor 440) to obtain and/or output signals.

Operation 1100 begins at 1102 by transmitting a first SPS PDSCH of a first HARQ process ID to a UE. For example, the network entity may transmit the first SPS PDSCH of the first HARQ process ID to the UE using the antenna(s) and transmitter/transceiver component of BS110a shown in fig. 1 or fig. 4 and/or the apparatus shown in fig. 14.

At 1104, the network entity transmits a second PDSCH of the same first HARQ process ID to the UE before receiving HARQ feedback for the first SPS PDSCH from the UE. For example, the network entity may transmit a second SPS PDSCH of the same HARQ process ID to the UE using antenna(s) and transmitter/transceiver component(s) of BS110a shown in fig. 1 or fig. 4 and/or the apparatus shown in fig. 14.

At 1106, the network entity receives HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH. For example, the network entity may use the antenna(s) and receiver/transceiver components of BS110a shown in fig. 1 or fig. 4 and/or the apparatus shown in fig. 14 to receive HARQ feedback for the first HARQ process ID at or after the scheduled occasion for reporting HARQ feedback for the second PDSCH.

At 1108, the network entity decides whether the received HARQ feedback is for the first SPS PDSCH or for the second PDSCH. For example, the network entity may use the BS110a shown in fig. 1 or fig. 4 and/or the processor of the apparatus shown in fig. 14 to decide whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

The operations shown in fig. 10 and 11 are further described with reference to fig. 12.

As illustrated in fig. 12, the UE may discard the deferred SPS HARQ bits to avoid out-of-order (OoO) HARQ feedback to the network entity (e.g., the gNB).

In the illustrated example, the network entity transmits a first SPS PDSCH (e.g., the earliest SPS PDSCH) of a first HARQ process ID (e.g., HARD process ID # 2) to the UE. The UE determines that a scheduled occasion for reporting HARQ feedback for the first SPS PDSCH overlaps with a DL symbol. The UE may report, defer, or discard HARQ feedback for the first SPS PDSCH (e.g., where resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH for the same first HARQ process ID).

In this example scenario, the ultra-reliable low latency communication (URLLC) traffic periodicity is 1ms, the sps configuration indicates 2 DL symbols and periodicity is 1ms, the DL packet expiration is 1ms, and k1_def_max is 2ms (before the next HARQ occasion).

In the illustrated example, the UE discards HARQ feedback (i.e., deferred SPS HARQ bits) for the first SPS PDSCH to avoid out-of-order HARQ feedback to the network entity. For example, when resources for reporting HARQ feedback for a first SPS PDSCH are not available for a threshold amount of time until after a scheduled opportunity for reporting HARQ feedback for a second PDSCH for the same first HARQ process ID (i.e., the next SPS PUCCH HARQ opportunity when k1_def_max is less than SPS period +k1), the UE does not allow HARQ feedback for the first SPS PDSCH (i.e., deferred SPS PUCCH HARQ) to be transmitted to the network entity. In some cases, the UE stops deferring SPS PUCCH HARQ until the next SPS PUCCH HARQ occasion (based on RRC configuration).

In certain aspects, the UE considers the timing of the true PUCCH HARQ transmission. In the case of SPS PUCCH HARQ deferral: the time of deferred SPS PUCCH HARQ transmissions.

In certain aspects, the UE requests that the network entity not schedule the same HARQ process ID for the new dynamic grant for PDSCH transmission (the same HARQ process ID as used for SPS PDSCH that experiences deferral).

In certain aspects, the second PDSCH (e.g., DG PDSCH with the same HARQ process ID as the first SPS PDSCH) is scheduled via dynamic grants. In this case, the UE may stop deferring HARQ feedback for the first SPS PDSCH (i.e., SPS PUCCH HARQ) until the time of PUCCH HARQ transmission for the second PDSCH (i.e., the UE discards the deferred SPS PUCCH HARQ bits). In some cases, the UE may report the HARQ feedback and add bits indicating that the HARQ feedback corresponds to the second SPS PDSCH (e.g., DG PDSCH) or the first SPS PDSCH (e.g., SPS PDSCH). In some cases, the UE may add a bit indicating that HARQ feedback (for the first SPS PDSCH) is out-of-order HARQ transmission. In some cases, the UE may add a field with the DL sub-slot number received by the PDSCH.

Example communication device

Fig. 13 illustrates a communication device 1300 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in fig. 10. The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and/or receiver). The transceiver 1308 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1300 via the antenna 1310. The processing system 1302 is configured to perform processing functions for the communication device 1300, including processing signals received and/or to be transmitted by the communication device 1300.

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 the operations illustrated in fig. 10, or other operations for performing the various techniques discussed herein. In certain aspects, the computer-readable medium/memory 1312 stores code 1314 for determining and code 1316 for reporting, deferring, or discarding. The code for determining 1314 may include code for determining that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol. The code 1316 for reporting, deferring, or discarding may include code for reporting, deferring, or discarding HARQ feedback for the first SPS PDSCH in response to the determination if resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID.

The processor 1304 may include circuitry configured to implement code stored in the computer-readable medium/memory 1312, such as for performing the operations illustrated in fig. 10 and for performing other operations of the various techniques discussed herein. For example, the processor 1304 includes circuitry 1318 for determining and circuitry 1320 for reporting, deferring, or discarding. The circuitry for determining 1318 may include circuitry for determining that a scheduled occasion for reporting HARQ feedback for a first SPS PDSCH of a first HARQ process ID overlaps with at least one downlink symbol or flexible symbol. Circuitry 1320 for reporting, deferring, or discarding may include circuitry for reporting, deferring, or discarding HARQ feedback for the first SPS PDSCH in response to the determination if resources for reporting HARQ feedback for the first SPS PDSCH are not available until or after a scheduled occasion for reporting HARQ feedback for a second PDSCH for the same first HARQ process ID.

Fig. 14 illustrates a communication device 1400 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations of the techniques disclosed herein, such as the operations illustrated in fig. 11. The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., transmitter and/or receiver). The transceiver 1408 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1400 via the antenna 1410. The processing system 1402 is configured to perform processing functions for the communication device 1400, including processing signals received and/or to be transmitted by the communication device 1400.

The processing system 1402 includes a processor 1404 coupled to a computer-readable medium/memory 1412 via a bus 1406. In certain aspects, the computer-readable medium/memory 1412 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1404, cause the processor 1404 to perform the operations illustrated in fig. 11, or other operations for performing the various techniques discussed herein. In certain aspects, the computer-readable medium/memory 1412 stores code 1414 for transmitting, code 1416 for transmitting, code 1418 for receiving, and code 1420 for deciding. Code 1414 for transmitting may include code for transmitting a first SPS PDSCH of a first HARQ process ID to a User Equipment (UE). Code 1416 for transmitting may include code for transmitting a second PDSCH of the same first HARQ process ID to the UE prior to receiving HARQ feedback for the first SPS PDSCH from the UE. The code for receiving 1418 may include code for receiving HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH. The code 1420 for deciding may include code for deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

The processor 1404 may include circuitry configured to implement code stored in the computer-readable medium/memory 1412, such as for performing the operations illustrated in fig. 11 and for performing other operations of the various techniques discussed herein. For example, the processor 1404 includes circuitry 1422 for transmitting, circuitry 1424 for transmitting, circuitry 1426 for receiving, and circuitry 1428 for deciding. Circuitry for transmitting 1422 may include circuitry for transmitting a first SPS PDSCH of a first HARQ process ID to a UE. Circuitry for transmitting 1424 may include circuitry to transmit a second PDSCH of the same first HARQ process ID to the UE prior to receiving HARQ feedback for the first SPS PDSCH from the UE. The circuitry for receiving 1426 may include circuitry to receive HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH. The circuitry for deciding 1428 may include circuitry to decide whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

Example split BS

Fig. 15 depicts an example exploded Base Station (BS) 1500 architecture. The split BS1500 architecture may include one or more Central Units (CUs) 1510 that may communicate directly with the core network 1520 via a backhaul link, or indirectly with the core network 1520 through one or more split BS units, such as Near real-time (Near-RT) RAN Intelligent Controllers (RIC) 1525 via E2 links, or Non-real-time (Non-RT) RIC 1515 associated with a Service Management and Orchestration (SMO) framework 1505, or both. CU 1510 can communicate with one or more Distributed Units (DUs) 1530 via a corresponding mid-range link, such as an F1 interface. The DU 1530 may communicate with one or more Radio Units (RUs) 1540 via a corresponding outbound link. RU 1540 may communicate with respective UEs 120 via one or more Radio Frequency (RF) access links. In some implementations, UE 120 may be served simultaneously by multiple RUs 1540.

Each of the units (i.e., CU 1510, DU 1530, RU 1540, and near RT RIC 1525, non-RT RIC 1515, and SMO framework 1505) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller that provides instructions to a communication interface of the units, may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a Radio Frequency (RF) transceiver) configured to receive or transmit signals to one or more of the other units, or both, over a wireless transmission medium.

In some aspects, the CU 1510 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), packet Data Convergence Protocol (PDCP), service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 1510. CU 1510 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 1510 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface, such as an E1 interface. CU 1510 can be implemented in communication with DU 1530 for network control and signaling, as desired.

The DU 1530 may correspond to a logic unit that includes one or more base station functions to control the operation of the one or more RUs 1540. In some aspects, the DU 1530 may host one or more of the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers, such as modules for Forward Error Correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc., depending at least in part on a functional partitioning, such as defined by the third generation partnership project (3 GPP). In some aspects, the DU 1530 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1530 or with control functions hosted by the CU 1510.

Lower layer functionality may be implemented by one or more RUs 1540. In some deployments, RU 1540 controlled by DU 1530 may correspond to a logical node hosting RF processing functions or lower PHY layer functions (such as performing Fast Fourier Transforms (FFTs), inverse FFTs (iffts), digital beamforming, physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, RU(s) 1540 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, the real-time and non-real-time aspects of control and user plane communications with RU(s) 1540 can be controlled by corresponding DUs 1530. In some scenarios, this configuration may enable the DU(s) 1530 and CU 1510 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

SMO framework 1505 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 1505 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, SMO framework 1505 may be configured to interact with a Cloud computing platform, such as an open Cloud (O-Cloud) 1590, to perform network element lifecycle management (such as instantiating virtualized network elements) via a Cloud computing platform interface, such as an O2 interface. Such virtualized network elements may include, but are not limited to, CU 1510, DU 1530, RU 1540, and near RT RIC 1525. In some implementations, SMO framework 1505 may communicate with hardware aspects of the 4G RAN, such as open eNB (O-eNB) 1511, via an O1 interface. Additionally, in some implementations, SMO framework 1505 may communicate directly with one or more RUs 1540 via an O1 interface. SMO framework 1505 may also include a non-RT RIC 1515 configured to support the functionality of SMO framework 1505.

The non-RT RIC 1515 may be configured to include logic functions that implement RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updating, or non-real-time control and optimization of policy-based guidance of applications/features in the near RT RIC X25. The non-RT RIC 1515 may be coupled to or in communication with the near-RT RIC 1525 (such as via an A1 interface). Near RT RIC 1525 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 1510, one or more DUs 1530, or both, and an O-eNB with near RT RIC 1525.

In some implementations, to generate the AI/ML model to be deployed in the near RT RIC 1525, the non-RT RIC 1515 may receive parameters or external rich information from an external server. Such information may be utilized by the near RT RIC 1525 and may be received at SMO framework 1505 or non-RT RIC 1515 from a non-network data source or from a network function. In some examples, the non-RT RIC 1515 or near-RT RIC 1525 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 1515 may monitor long-term trends and patterns of performance and employ AI/ML models to perform corrective actions through the SMO framework 1505 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

Example aspects

Examples of implementations are described in the following numbered aspects:

in a first aspect, a method of wireless communication by a User Equipment (UE) includes: determining that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) for a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol; and in response to the determination, reporting, deferring, or discarding HARQ feedback for the first SPS PDSCH if resources for reporting HARQ feedback for the first SPS PDSCH are not available until a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID or thereafter.

In a second aspect, alone or in combination with the first aspect, the reporting, deferring, or discarding is based on the resource for reporting HARQ feedback for the first SPS PDSCH not being available until a threshold amount of time after the scheduled occasion for reporting the HARQ feedback.

In a third aspect, alone or in combination with the first aspect, the reporting, deferring or discarding is based on resources for reporting the HARQ feedback not being available until at or after an opportunity for reporting HARQ feedback for a subsequent SPS PDSCH.

In a fourth aspect, alone or in combination with the first aspect, a request is sent to a network entity to not send a dynamic grant for PDSCH transmissions with the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

In a fifth aspect, alone or in combination with the first aspect, the second PDSCH is scheduled via dynamic grants.

In a sixth aspect, alone or in combination with the fifth aspect, HARQ feedback for the first SPS PDSCH is discarded.

In a seventh aspect, alone or in combination with the fifth aspect, reporting HARQ feedback comprises: the HARQ feedback is reported with an indication of whether the HARQ feedback is for the first SPS PDSCH or for the dynamically grant scheduled PDSCH.

In an eighth aspect, alone or in combination with the fifth aspect, reporting HARQ feedback comprises: the HARQ feedback is reported with an indication that the HARQ feedback for the first SPS PDSCH is out of order.

In a ninth aspect, alone or in combination with the fifth aspect, reporting HARQ feedback comprises: HARQ feedback for the first SPS PDSCH is reported along with an indication of a downlink time slot or sub-time slot in which the first SPS PDSCH is received.

In a tenth aspect, a method for wireless communication by a network entity comprises: transmitting a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) to a User Equipment (UE); transmitting a second PDSCH of the same first HARQ process ID to the UE before receiving HARQ feedback for the first SPS PDSCH from the UE; receiving HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH; and deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

In an eleventh aspect, alone or in combination with the tenth aspect, an indication is received from the UE indicating whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

In a twelfth aspect, alone or in combination with the eleventh aspect, the indication comprises a bit.

In a thirteenth aspect, alone or in combination with the twelfth aspect, the decision is based on the bit indicating whether the received HARQ feedback is for the first SPS PDSCH or for the second PDSCH.

In a fourteenth aspect, alone or in combination with the tenth aspect, a request is received from the UE to not send a dynamic grant for PDSCH transmissions having the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

In a fifteenth aspect, alone or in combination with the tenth aspect, the second PDSCH is scheduled via dynamic grants.

An apparatus for wireless communication, comprising: at least one processor and a memory coupled to the at least one processor, the memory including code executable by the at least one processor to cause the apparatus to perform the method of any of the first to fifteenth aspects.

An apparatus comprising means for performing the method of any of the first to fifteenth aspects.

A computer-readable medium having stored thereon computer-executable code for wireless communication, which when executed by at least one processor causes an apparatus to perform a method as in any of the first to fifteenth aspects.

Additional considerations

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

As used herein, a phrase referring to a list of items "at least one of" refers to any combination of these items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a. b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, researching, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and the like. Also, "determining" may include parsing, selecting, choosing, establishing, and the like.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" (unless specifically so stated) but rather "one or more". The term "some" means one or more unless specifically stated otherwise. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents that are presently or later to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No element of a claim should be construed under the provisions of 35u.s.c. ≡112, sixth clause, unless the element is explicitly recited using the term "means for … …" or in the case of method claims, the element is recited using the term "step for … …".

The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These means may comprise various hardware and/or software components and/or modules including, but not limited to, circuits, application Specific Integrated Circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, these operations may have corresponding counterpart means-plus-function components with similar numbers. For example, processors 458, 464, 466 and/or controller/processor 480 of UE 120a and/or processors 420, 430, 438 and/or controller/processor 440 of BS110a shown in fig. 4 may be configured to perform operation 1000 of fig. 10 and operation 1100 of fig. 11.

The means for receiving may comprise a receiver (such as one or more antennas and/or a receive processor) illustrated in fig. 4. Also, the means for transmitting may include a transmitter (such as one or more antennas and/or a transmit processor) illustrated in fig. 4. The means for monitoring, means for indicating, means for signaling, means for activating, and means for deactivating may comprise a processing system that may include one or more processors, such as processors 458, 464, 466 and/or controller/processor 480 of UE 120a and/or processors 420, 430, 438 and/or controller/processor 440 of BS110a shown in fig. 4.

In some cases, a device may not actually transmit a frame, but may have an interface (means for outputting) for outputting the frame for transmission. For example, the processor may output frames via a bus interface to a Radio Frequency (RF) front end for transmission. Similarly, a device may not actually receive a frame, but may have an interface (means for acquiring) for acquiring a frame received from another device. For example, the processor may obtain (or receive) frames from the RF front end via the bus interface for reception.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a graphics processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, 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.

If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including processors, machine-readable media, and bus interfaces. A bus interface may be used to connect network adapters and the like to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of UE 120 (see fig. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. A processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Those skilled in the art will recognize how to optimally implement the functionality described with respect to the processing system, depending upon the particular application and overall design constraints imposed on the overall system.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should 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 includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on a machine-readable storage medium. A computer readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, machine-readable media may comprise a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium having instructions stored thereon, separate from the wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, the machine-readable medium, or any portion thereof, may be integrated into the processor, such as the cache and/or general purpose register file, as may be the case. By way of example, a machine-readable storage medium may comprise RAM (random access memory), flash memory, phase change memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be implemented in a computer program product.

A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer readable medium may include a plurality of software modules. These software modules include instructions that, when executed by equipment (such as a processor), cause a processing system to perform various functions. These software modules may include a transmit module and a receive module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a trigger event occurs, the software module may be loaded into RAM from a hard drive. During execution of the software module, the processor may load some instructions into the cache to increase access speed. One or more cache lines may then be loaded into a general purpose register file for execution by the processor. Where functionality of a software module is described below, it will be understood that such functionality is implemented by a processor when executing instructions from the software module.

Also, any connection is properly termed a computer-readable medium. For example, if the software is from a web site, service using coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, and microwave And transmitted from another remote source, 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 (disc) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk, and diskA disc, in which the disc (disk) often magnetically reproduces data, and the disc (disk) optically reproduces data with a laser. Thus, in some aspects, a computer-readable medium may comprise a non-transitory computer-readable medium (e.g., a tangible medium). Additionally, for other aspects, the computer-readable medium may include a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such computer program products may include a computer-readable medium having instructions stored (and/or encoded) thereon that are executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and in the figures.

Further, it should be appreciated that modules and/or other suitable 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 transfer of an apparatus for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a Compact Disc (CD) or floppy disk, etc.), such that the apparatus can obtain the various methods once the storage device is coupled to or provided to a user terminal and/or base station. Further, any other suitable technique suitable for providing the methods and techniques described herein to a device may be utilized.

It is to be understood that the claims are not limited to the precise configurations and components illustrated above. Various modifications, substitutions and alterations can be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims (30)

1. A method for wireless communication by a User Equipment (UE), comprising:

determining that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) for a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol; and

In response to the determination, HARQ feedback for the first SPS PDSCH is reported, deferred, or discarded if resources for reporting HARQ feedback for the first SPS PDSCH are not available until a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID or thereafter.

2. The method of claim 1, wherein the reporting, deferring, or discarding is based on the resources used to report HARQ feedback for the first SPS PDSCH not being available until a threshold amount of time after the scheduled occasion for reporting the HARQ feedback.

3. The method of claim 1, wherein the reporting, deferring, or discarding is based on resources used to report HARQ feedback not being available until at or after an opportunity to report HARQ feedback for a subsequent SPS PDSCH.

4. The method of claim 1, further comprising: a request is sent to the network entity to not send a dynamic grant for PDSCH transmissions with the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

5. The method of claim 1, wherein the second PDSCH is scheduled via dynamic grants.

6. The method of claim 5, further comprising: and discarding HARQ feedback for the first SPS PDSCH.

7. The method of claim 5, wherein reporting HARQ feedback comprises: the HARQ feedback is reported with an indication of whether the HARQ feedback is for the first SPS PDSCH or for a dynamically grant scheduled PDSCH.

8. The method of claim 5, wherein reporting HARQ feedback comprises: the HARQ feedback for the first SPS PDSCH is reported along with an indication that the HARQ feedback is out of order.

9. The method of claim 5, wherein reporting HARQ feedback comprises: HARQ feedback for the first SPS PDSCH is reported along with an indication of a downlink time slot or sub-time slot in which the first SPS PDSCH is received.

10. A method for wireless communication by a network entity, comprising:

transmitting a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) to a User Equipment (UE);

transmitting a second PDSCH of the same first HARQ process ID to the UE prior to receiving HARQ feedback for the first SPS PDSCH from the UE;

receiving HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH; and

Deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

11. The method of claim 10, further comprising: an indication is received from the UE indicating whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

12. The method of claim 11, wherein the indication comprises a bit.

13. The method of claim 12, wherein the decision indicates whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH based on the bits.

14. The method of claim 10, further comprising: a request is received from the UE to not send a dynamic grant for a PDSCH transmission with the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

15. The method of claim 10, wherein the second PDSCH is scheduled via dynamic grants.

16. An apparatus for wireless communication by a User Equipment (UE), comprising:

a memory including computer-executable instructions; and

a processor configured to execute the computer-executable instructions and cause the UE to:

determining that a scheduled occasion for reporting HARQ feedback for a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) for a first hybrid automatic repeat request (HARQ) process Identifier (ID) overlaps with at least one downlink symbol or flexible symbol; and

In response to the determination, HARQ feedback for the first SPS PDSCH is reported, deferred, or discarded if resources for reporting HARQ feedback for the first SPS PDSCH are not available until a scheduled occasion for reporting HARQ feedback for a second PDSCH of the same first HARQ process ID or thereafter.

17. The apparatus of claim 16, wherein the reporting, deferring, or discarding is based on the resources used to report HARQ feedback for the first SPS PDSCH not being available until a threshold amount of time after the scheduled occasion for reporting the HARQ feedback.

18. The apparatus of claim 16, wherein the reporting, deferring, or discarding is based on resources used to report HARQ feedback not being available until at or after an opportunity to report HARQ feedback for a subsequent SPS PDSCH.

19. The apparatus of claim 16, wherein the processor is further configured to execute the computer-executable instructions and cause the UE to: a request is sent to the network entity to not send a dynamic grant for PDSCH transmissions with the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

20. The apparatus of claim 16, wherein the second PDSCH is scheduled via dynamic grants.

21. The apparatus of claim 20, wherein the processor is further configured to execute the computer-executable instructions and cause the UE to: and discarding HARQ feedback for the first SPS PDSCH.

22. The apparatus of claim 20, wherein the processor is further configured to execute the computer-executable instructions and cause the UE to: the HARQ feedback is reported with an indication of whether the HARQ feedback is for the first SPS PDSCH or for a dynamically grant scheduled PDSCH.

23. The apparatus of claim 20, wherein the processor is further configured to execute the computer-executable instructions and cause the UE to: the HARQ feedback for the first SPS PDSCH is reported along with an indication that the HARQ feedback is out of order.

24. The apparatus of claim 20, wherein the processor is further configured to execute the computer-executable instructions and cause the UE to: HARQ feedback for the first SPS PDSCH is reported along with an indication of a downlink time slot or sub-time slot in which the first SPS PDSCH is received.

25. An apparatus for wireless communication by a network entity, comprising:

a memory including computer-executable instructions; and

A processor configured to execute the computer-executable instructions and cause the network entity to:

transmitting a first semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH) of a first hybrid automatic repeat request (HARQ) process Identifier (ID) to a User Equipment (UE);

transmitting a second PDSCH of the same first HARQ process ID to the UE prior to receiving HARQ feedback for the first SPS PDSCH from the UE;

receiving HARQ feedback for the first HARQ process ID at or after a scheduled occasion for reporting HARQ feedback for the second PDSCH; and

deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

26. The apparatus of claim 25, wherein the processor is further configured to execute the computer-executable instructions and cause the apparatus to: an indication is received from the UE indicating whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

27. The apparatus of claim 26, wherein the indication comprises a bit.

28. The apparatus of claim 27, wherein the decision indicates whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH based on the bits.

29. The apparatus of claim 25, wherein the processor is further configured to execute the computer-executable instructions and cause the apparatus to: a request is received from the UE to not send a dynamic grant for a PDSCH transmission with the same HARQ process ID as the SPS PDSCH whose HARQ report is being deferred.

30. The apparatus of claim 25, wherein the second PDSCH is scheduled via dynamic grants.