100 may support synchronous or asynchronous operation. For synchronous operation, the BSs 110 may have similar frame timing, and transmissions from different BSs 110 may be approximately aligned in time. For asynchronous operation, the BSs 110 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.

A network controller 130 may couple to a set of BSs 110 and provide coordination and control for these BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.

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

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

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

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

NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration. In one aspect, each radio frame may consist of 50 subframes with a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms. In another aspect, each radio frame may consist of 10 subframes with a length of 10 ms, 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 for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE 120. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based. NR networks may include entities such CUs and/or DUs.

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

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

As noted above, a RAN may include a CU and DUs. A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) may correspond to one or multiple BSs 110. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases, DCells may not transmit synchronization signals—in some case cases DCells may transmit SS. NR BSs 110 may transmit downlink signals to UEs 120 indicating the cell type. Based on the cell type indication, the UE 120 may communicate with the NR BS 110. For example, the UE 120 may determine NR BSs 110 to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

In various aspects, a BS 110 (or a network node) can be implemented as an aggregated BS, a disaggregated BS, an integrated access and backhaul (IAB) node, a relay node, or a sidelink node, to name a few examples. FIG. 15, discussed in further detail later in this disclosure, depicts an example disaggregated BS architecture.

FIG. 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which may be implemented in the wireless communications system illustrated in FIG. 1. A 5G access node 206 may include an access node controller (ANC) 202. The ANC may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 (e.g., associated with 5G control plane (5G C-plane) 212 and 5G gateway (5G-GW) 214) may terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG ANs) may terminate at the ANC. The ANC may include one or more TRPs 208a, 208b, 208c (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with “cell.”

The TRPs 208a, 208b, 208c may be a DU. The TRPs 208a, 808b, 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, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs 208a, 208b, 208c may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

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

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

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

According to aspects, a dynamic configuration of split logical functions may be present within the distributed RAN 200. As will be described in more detail with reference to FIG. 5, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively). According to certain aspects, a 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, according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 (e.g., associated with 5G C-plane 308 and 5G-GW 310 associated with mobile radio (MR) communication network (CN) 312) may host core network functions. The C-CU 302 may be centrally deployed. 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 network (AN) 314 and 5G AN 316) may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have distributed deployment. The C-RU 304 may be closer to the network edge.

A DU 306 (e.g., 306a, 306b, or 306c) may host one or more TRPs (edge node (EN), an edge unit (EU), a radio head (RH), a smart radio head (SRH), or the like). The DU 306 may be located at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of a network entity (e.g., a BS 110a) and a UE 120a (e.g., in the wireless communication network 100 of FIG. 1).

At the BS 110a, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be 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), etc. The data may be for a physical downlink shared channel (PDSCH), etc. 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 a PDSCH, a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

The 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, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) in transceivers 432a-432t. Each MOD in transceivers 432a-432t may process a respective output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM), etc.) to obtain an output sample stream. Each MOD in transceivers 432a-432t may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal. The DL signals from the MODs in transceivers 432a-432t may be transmitted via antennas 434a-434t, respectively.

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

On an uplink (UL), at the UE 120a, a transmit processor 464 may receive and process data (e.g., for a PUSCH) from a data source 462 and control information (e.g., for a physical uplink control channel (PUCCH) from the controller/processor 480. The transmit processor 464 may also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a transmit MIMO processor 466 if applicable, further processed by the MODs in transceivers 454a-454r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the UL signals from the UE 120a may be received by the antennas 434, processed by the DEMODs in transceivers 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120a. The receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.

Memories 442 and 482 may store data and program codes for the BS 110a and the UE 120a, respectively. A scheduler 444 may schedule the UE 120a for data transmission on a DL and/or an UL.

Antennas 452, processors 466, 458, 464, and/or controller/processor 480 of the UE 120a and/or antennas 434, processors 420, 430, 438, and/or controller/processor 440 of the BS 110a may be used to perform the various techniques and methods described herein. For example, as shown in FIG. 4, the controller/processor 440 of the BS 110a has a 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 the 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 the controller/processor, other components of the UE 120a and the BS 110a may be used to perform the operations described herein.

NR may utilize OFDM with a cyclic prefix (CP) on the UL and the DL. The NR may support half-duplex operation using time division duplexing (TDD). The OFDM and single-carrier frequency division multiplexing (SC-FDM) partition system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Modulation symbols may be sent in a frequency domain with the OFDM and in a time domain with the SC-FDM. The spacing between adjacent subcarriers may be fixed, and a total number of subcarriers may be dependent on the system bandwidth. The minimum resource allocation, called a resource block (RB), may be 12 consecutive subcarriers. The system bandwidth may also be partitioned into subbands. For example, a subband may cover multiple RBs. The NR may support a base subcarrier spacing (SCS) of 15 KHz and other SCS may be defined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.).

FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a 5G system. Diagram 500 illustrates a communications 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 the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.

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

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

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

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 partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. 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. The symbol periods in each slot may be assigned indices. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

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 directions may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information.

In NR, a synchronization signal (SS) block is transmitted. The SS block includes a PSS, a SSS, and a two symbol PBCH. The SS block can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in FIG. 6. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes.

A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.

Example Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) Configuration

Semi-persistently scheduled or semi-persistent scheduling (SPS) resource allocation, which is sometimes called configured downlink assignment, refers to a scheduling technique where a user equipment (UE) is pre-configured by a network entity (e.g., eNBs, gNB, etc.) with a periodicity and an offset.

As illustrated in FIG. 7, once pre-configured, if the UE were to receive an allocation of downlink resources, then the allocation of SPS occasions would repeat according to the pre-configured periodicity, resulting in periodic SPS occasions. For SPS, the network entity may use radio resource control (RRC) signaling to define the periodicity of configured downlink assignments. Similarly, once configured with configured grant (CG) occasions, the allocation of CG occasions may repeat according to the pre-configured 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 happen. For example, a downlink transmission may or may not occur in an SPS occasion. Similarly, an uplink (UL) transmission may or may not occur in a CG occasion. Occasions may be considered activated if the transmission may occur and, thus, those occasions should be monitored.

Example Hybrid Automatic Repeat Request (HARQ) Delay for SPS PDSCH

New radio (NR) may provide support for downlink (DL) semi-persistent scheduling (SPS) for periodic traffic. For a time division duplexed (TDD) system (e.g., in Rel-15 and/or Rel-16), if a slot scheduled for reporting hybrid automatic repeat request (HARQ) feedback for the SPS is a DL slot, or overlapping with at least one DL symbol, a user equipment (UE) will not transmit the HARQ feedback. This may result in a waste of system resource(s), since a network entity (e.g., a base station (BS) such as a gNB) may need to retransmit the SPS physical downlink shared channel (PDSCH) again due to missed a HARQ report.

The overlap may be due to various reasons. For example, the DL slot/symbols may be semi-statically configured to be DL, or the slots/symbols may be converted to the DL (or “dynamic flexible”) from semi-static “flexible” by a dynamic slot format indicator (SFI) or dynamic DL control information (DCI) (e.g., a DL grant scheduling PDSCH, or a grant scheduling aperiodic channel state information reference signals (CSI-RS) transmission).

In some cases (e.g., in NR Rel-17), the HARQ feedback for SPS PDSCH may be enhanced by delaying the HARQ feedback that conflicts with the DL symbols/slots (or “dynamic flexible” symbols) to later uplink (UL) symbols/slots. For example, if an SPS HARQ-ACK cannot be transmitted in a first slot or subslot of a scheduled physical uplink control channel (PUCCH) occasion due to conflict with the DL symbols/slots, it can be delayed (deferred) to a next (or a later) UL slot/subslot.

In some cases, when the slot scheduled for reporting the HARQ feedback for the SPS overlaps/collides with a DL symbol, as illustrated in FIG. 8, the HARQ feedback can be deferred up to a first available/valid PUCCH resource. This may be done using already configured SPS PUCCH resources. In some cases, a change in a slot format may happen according to a pattern defined in an information element (IE) (e.g., such as SlotFormatCombinationsPerCell). Also, SPS PUCCH A/N may indicate a PUCCH Format 0 (1 bit). Thus, a first UL PUCCH resource may correspond to a first available UL symbol. Also, in this case, there may be no multiplexing with other PUCCH transmissions from a same UE.

The example in FIG. 9 may assume an ultra-reliable low latency communication (URLLC) traffic periodicity is 1 ms, SPS configuration indicates 2 DL symbols and periodicity is 1 ms, DL packet expiration is 1 ms, and K1_def_max is 2 ms.

In this example case, when a UE receives a new SPS PDSCH from a network entity, a slot for reporting a HARQ feedback for this SPS PDSCH is assumed to be k1 slots later. However, when resources for reporting a HARQ feedback for an earlier SPS PDSCH are not available until at or after the HARQ feedback is scheduled to send the HARQ feedback for the new PDSCH, there may be an issue with how or what the HARQ feedback to report. In such cases, a PUCCH may only be available for a new HARQ feedback (e.g., as there are no sufficient UL resources available for the HARQ feedback for the earlier SPS PDSCH/deferred HARQ bits) (i.e., K1_def is less than k1_def_max). In this case, when the UE sends the HARQ feedback to the network entity for the new SPS PDSCH, the network entity may not know which PDSCH is being acknowledged (e.g., if they share a same HARQ process ID).

Example Deferral Time Prior to Next HARQ Instant

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer readable mediums for managing an out of order hybrid automatic repeat request (HARQ) transmission in case of a deferred semi-persistently scheduled (SPS) physical uplink control channel (PUCCH) HARQ.

For example, to handle a collision for a same HARQ process due to a deferred SPS HARQ acknowledgement (HARQ-ACK), one or more techniques for managing the out of order HARQ transmission are implemented. Based on the one or more techniques described herein, when a user equipment (UE) receives a physical downlink shared channel (PDSCH) of a certain HARQ process identifier (ID), the deferred SPS HARQ bit(s) for this HARQ process ID are dropped. The techniques described herein provide higher reliability and lower latency communications.

FIG. 10 is a flow diagram 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 that are executed and run on one or more processors (e.g., the controller/processor 480 of FIG. 4). Further, the transmission and reception of signals by the UE in operations 1000 may be enabled, for example, by one or more antennas (e.g., the antennas 452 of FIG. 4). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., the controller/processor 480) obtaining and/or outputting signals.

The operations 1000 begin, at block 1002, by determining that a scheduled occasion for reporting HARQ feedback for a first SPS physical downlink shared channel (PDSCH) of a first HARQ process identifier (ID) overlaps with at least one downlink (DL) or flexible symbol. For example, the UE may determine that the scheduled occasion for reporting the HARQ feedback for the first SPS PDSCH of the first HARQ process ID overlaps with the at least one DL or flexible symbol, using a processor of the UE 120a shown in FIG. 1 or FIG. 4 and/or of the apparatus shown in FIG. 13.

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

In certain aspects, deferred HARQ information bits (e.g., associated with the first HARQ process ID) are stored until new HARQ information bits are available from a same HARQ process ID (e.g., the new HARQ information bits are associated with the first HARQ process ID). 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 that are replaced with the new HARQ information bits are not reported.

In certain aspects, the UE may drop the HARQ feedback for the first SPS PDSCH (e.g., if the resources for reporting the HARQ feedback for the first SPS PDSCH are not available until on or after the scheduled occasion for reporting the HARQ feedback for the second PDSCH of the same first HARQ process ID).

In certain aspects, the UE may report, defer, or drop the HARQ feedback for the first SPS PDSCH, based on the resources for reporting the HARQ feedback not being available until a threshold amount of time after the scheduled occasion for reporting the HARQ feedback for the first SPS PDSCH.

In certain aspects, the UE may report, defer, or drop the HARQ feedback for the first SPS PDSCH, based on the resources for reporting the HARQ feedback not being available until on or after an occasion for reporting a HARQ feedback for a subsequent SPS PDSCH.

In certain aspects, the UE may send a request to a network entity to not send a dynamic grant for PDSCH transmissions with a same HARQ process ID as SPS PDSCHs for which HARQ reporting is being deferred. If granted, this request could avoid the problem of the UE reporting an out of order HARQ feedback for a PDSCH with a same HARQ process ID. In other words, the UE requests for not scheduling same HARQ process IDs (as the ones used for SPS experiencing deferrals) for new dynamic grant PDSCH.

In certain aspects, the second PDSCH may be scheduled via a dynamic grant. In some cases, the UE may drop the HARQ feedback for the first SPS PDSCH. For example, the UE may stop deferring SPS PUCCH HARQ up to the moment of PUCCH HARQ transmission for new dynamic grant PDSCH (i.e., UE drops deferred SPS PUCCH HARQ bits).

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

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

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

FIG. 11 is a flow diagram illustrating example operations 1100 for wireless communication, in accordance with certain aspects of the present disclosure. For example, the operations 1100 may be performed by a network entity (e.g., such as the base station (BS) 110a of FIG. 1. The operations 1100 may be implemented as software components that are executed and run on one or more processors (e.g., the controller/processor 440 of FIG. 4). Further, the transmission and reception of signals by the network entity in operations 1100 may be enabled, for example, by one or more antennas (e.g., the antennas 434 of FIG. 4). In certain aspects, the transmission and/or reception of signals by the network entity may be implemented via a bus interface of one or more processors (e.g., the controller/processor 440) obtaining and/or outputting signals.

The operations 1100 begin, 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 antenna(s) and transmitter/transceiver components of the BS 110a shown in FIG. 1 or FIG. 4 and/or of 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 a HARQ feedback from the UE for the first SPS PDSCH. For example, the network entity may transmit the second PDSCH of the same first HARQ process ID to the UE, using antenna(s) and transmitter/transceiver components of the BS 110a shown in FIG. 1 or FIG. 4 and/or of the apparatus shown in FIG. 14.

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

At 1108, the network entity decides whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH. For example, the network entity may decide whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH, using a processor of the BS 110a shown in FIG. 1 or FIG. 4 and/or of the apparatus shown in FIG. 14.

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

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

In the illustrated example, the network entity sends a first SPS PDSCH (e.g., an 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 a HARQ feedback for the first SPS PDSCH overlaps with a DL symbol. The UE may report, defer, or drop the HARQ feedback for the first SPS PDSCH (e.g., if resources for reporting the HARQ feedback for the first SPS PDSCH are not available until on or after a scheduled occasion for reporting a HARQ feedback for a second PDSCH of the same first HARQ process ID).

In this example case, an ultra-reliable low latency communication (URLLC) traffic periodicity is 1 ms, SPS configuration indicates 2 DL symbols and periodicity is 1 ms, DL packet expiration is 1 ms, and K1_def_max is 1.2 ms (prior to a next HARQ occasion).

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

In certain aspects, the UE considers a timing of a real PUCCH HARQ transmission. In case of a SPS PUCCH HARQ deferral: a time instant of a deferred SPS PUCCH HARQ transmission.

In certain aspects, the UE requests the network entity to not schedule same HARQ process IDs (as the ones used for the SPS PDSCHs experiencing deferrals) for a new dynamic grant for PDSCH transmissions.

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

Example Communication Devices

FIG. 13 illustrates a communications 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 communications device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and/or a receiver). The transceiver 1308 is configured to transmit and receive signals for the communications device 1300 via an antenna 1310, such as the various signals as described herein. The processing system 1302 is configured to perform processing functions for the communications device 1300, including processing signals received and/or to be transmitted by the communications 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., a 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, computer-readable medium/memory 1312 stores code 1314 for determining and code 1316 for reporting, deferring, or dropping. The code 1314 for determining may include code for determining that a scheduled occasion for reporting hybrid automatic repeat request (HARQ) feedback for a first semi-persistently scheduled (SPS) physical downlink shared channel (PDSCH) of a first HARQ process identifier (ID) overlaps with at least one downlink or flexible symbol. The code 1316 for reporting, deferring, or dropping may include code for reporting, deferring, or dropping the HARQ feedback for the first SPS PDSCH if resources for reporting the HARQ feedback for the first SPS PDSCH are not available until on or after a scheduled occasion for reporting a HARQ feedback for a second PDSCH of the same first HARQ process ID, in response to the determining.

The processor 1304 may include circuitry configured to implement the code stored in the computer-readable medium/memory 1312, such as for performing the operations illustrated in FIG. 10, as well as other operations for performing the various techniques discussed herein. For example, the processor 1304 includes circuitry 1318 for determining and circuitry 1320 for reporting, deferring, or dropping. The circuitry 1318 for determining 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 or flexible symbol. The circuitry 1320 for reporting, deferring, or dropping may include circuitry for reporting, deferring, or dropping may include code for reporting, deferring, or dropping the HARQ feedback for the first SPS PDSCH if resources for reporting the HARQ feedback for the first SPS PDSCH are not available until on or after a scheduled occasion for reporting a HARQ feedback for a second PDSCH of the same first HARQ process ID, in response to the determining.

FIG. 14 illustrates a communications device 1400 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. 11. The communications device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and/or a receiver). The transceiver 1408 is configured to transmit and receive signals for the communications device 1400 via an antenna 1410, such as the various signals as described herein. The processing system 1402 is configured to perform processing functions for the communications device 1400, including processing signals received and/or to be transmitted by the communications 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., a 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, computer-readable medium/memory 1412 stores code 1414 for transmitting, code 1416 for transmitting, code 1418 for receiving, and code 1420 for deciding. The code 1414 for transmitting may include code for transmitting a first SPS PDSCH of a first HARQ process ID to a user equipment (UE). The code 1416 for transmitting may include code for transmitting a second PDSCH of the same first HARQ process ID to the UE before receiving a HARQ feedback from the UE for the first SPS PDSCH. The code 1418 for receiving may include code for receiving the HARQ feedback for the first HARQ process ID on or after a scheduled occasion for reporting the 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 the code stored in the computer-readable medium/memory 1412, such as for performing the operations illustrated in FIG. 11, as well as other operations for performing 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. The circuitry 1422 for transmitting may include circuitry for transmitting a first SPS PDSCH) of a first HARQ) process ID) to a UE. The circuitry 1424 for transmitting may include circuitry for transmitting a second PDSCH of the same first HARQ process ID to the UE before receiving a HARQ feedback from the UE for the first SPS PDSCH. The circuitry 1426 for receiving may include circuitry for receiving the HARQ feedback for the first HARQ process ID on or after a scheduled occasion for reporting the HARQ feedback for the second PDSCH. The circuitry 1428 for deciding may include circuitry for deciding whether the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

Example Disaggregated BS

FIG. 15 depicts an example disaggregated base station (BS) 1500 architecture. The disaggregated BS 1500 architecture may include one or more central units (CUs) 1510 that can communicate directly with a core network 1520 via a backhaul link, or indirectly with the core network 1520 through one or more disaggregated BS units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 1525 via an E2 link, or a Non-Real Time (Non-RT) RIC 1515 associated with a Service Management and Orchestration (SMO) Framework 1505, or both). A CU 1510 may communicate with one or more distributed units (DUs) 1530 via respective midhaul links, such as an F1 interface. The DUs 1530 may communicate with one or more radio units (RUs) 1540 via respective fronthaul links. The RUs 1540 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, the UE 120 may be simultaneously served by multiple RUs 1540.

Each of the units, i.e., the CUs 1510, the DUs 1530, the RUs 1540, as well as the Near-RT RICs 1525, the Non-RT RICs 1515 and the SMO Framework 1505, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 1510 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1510. The 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, the CU 1510 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 1510 can be implemented to communicate with the DU 1530, as necessary, for network control and signaling.

The DU 1530 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 1540. In some aspects, the DU 1530 may host one or more of a radio link control (RLC) layer, a 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, or the like) depending, at least in part, on a functional split, such as those defined by the 3^rdGeneration Partnership Project (3GPP). In some aspects, the DU 1530 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1530, or with the control functions hosted by the CU 1510.

Lower-layer functionality can be implemented by one or more RUs 1540. In some deployments, an RU 1540, controlled by a DU 1530, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 1540 can be implemented to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 1540 can be controlled by the corresponding DU 1530. In some scenarios, this configuration can enable the DU(s) 1530 and the CU 1510 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 1505 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 1505 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the 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 life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 1510, DUs 1530, RUs 1540 and Near-RT RICs 1525. In some implementations, the SMO Framework 1505 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 1511, via an O1 interface. Additionally, in some implementations, the SMO Framework 1505 can communicate directly with one or more RUs 1540 via an O1 interface. The SMO Framework 1505 also may include a Non-RT RIC 1515 configured to support functionality of the SMO Framework 1505.

The Non-RT RIC 1515 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC X25. The Non-RT RIC 1515 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 1525. The Near-RT RIC 1525 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 1510, one or more DUs 1530, or both, as well as an O-eNB, with the Near-RT MC 1525.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 1525, the Non-RT MC 1515 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 1525 and may be received at the SMO Framework 1505 or the Non-RT RIC 1515 from non-network data sources or from network functions. In some examples, the Non-RT RIC 1515 or the Near-RT MC 1525 may be configured to tune RAN behavior or performance. For example, the Non-RT MC 1515 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 1505 (such as reconfiguration via O1) or via creation of RAN management policies (such as AI policies).

Example Aspects

Implementation examples are described in the following numbered aspects.

In a first aspect, a method for wireless communications by a user equipment (UE), comprising: determining that a scheduled occasion for reporting hybrid automatic repeat request (HARQ) feedback for a first semi-persistently scheduled (SPS) physical downlink shared channel (PDSCH) of a first HARQ process identifier (ID) overlaps with at least one downlink or flexible symbol; and reporting, deferring, or dropping the HARQ feedback for the first SPS PDSCH if resources for reporting the HARQ feedback for the first SPS PDSCH are not available until on or after a scheduled occasion for reporting a HARQ feedback for a second PDSCH of the same first HARQ process ID, in response to the determining.

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

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

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

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

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

In a seventh aspect, alone or in combination with the fifth aspect, reporting the HARQ feedback comprises reporting the HARQ feedback with an indication that the HARQ feedback is for the first SPS PDSCH or the dynamic grant scheduled PDSCH.

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

In a ninth aspect, alone or in combination with the fifth aspect, reporting the HARQ feedback comprises reporting the HARQ feedback for the first SPS PDSCH with an indication in a downlink slot or a subslot in which the first SPS PDSCH was received.

In a tenth aspect, a method for wireless communications by a network entity, comprising: transmitting a first semi-persistently scheduled (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 a HARQ feedback from the UE for the first SPS PDSCH; receiving the HARQ feedback for the first HARQ process ID on or after a scheduled occasion for reporting the 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, receiving an indication from the UE indicating 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 the received HARQ feedback is for the first SPS PDSCH or the second PDSCH.

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

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

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