SCHEDULING OFFSET FOR HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGEMENT CODEBOOK

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, from a network entity, an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook. The UE may transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for a scheduling offset for a hybrid automatic repeat request acknowledgement codebook.

BACKGROUND

A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications.

“Downlink” (or “DL”) refers to a communication link from the base station to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the base station.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving, from a network entity, an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook. The method may include transmitting, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include transmitting, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook. The method may include receiving, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook. The one or more processors may be configured to transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to an apparatus for wireless communication associated with a network entity. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook. The one or more processors may be configured to receive, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook. The apparatus may include means for transmitting, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook. The apparatus may include means for receiving, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.

DETAILED DESCRIPTION

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive, from a network entity, an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook; and transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, the network entity described herein may be associated with the base station110. The network entity may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit, to a UE (e.g., UE120), an indication of a scheduling offset associated with a HARQ ACK codebook; and receive, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, the UE120includes means for receiving, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook; and/or means for transmitting, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset. The means for the UE120to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, the network entity described elsewhere herein includes means for transmitting, to a UE (e.g., the UE120), an indication of a scheduling offset associated with a HARQ ACK codebook; and/or means for receiving, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.3is a diagram illustrating an example300of an O-RAN architecture, in accordance with the present disclosure. As shown inFIG.3, the O-RAN architecture may include a centralized unit (CU)310that communicates with a core network320via a backhaul link. Furthermore, the CU310may communicate with one or more distributed units (DUs)330via respective midhaul links. The DUs330may each communicate with one or more radio units (RUs)340via respective fronthaul links, and the RUs340may each communicate with respective UEs120via radio frequency (RF) access links. The DUs330and the RUs340may also be referred to as O-RAN DUs (O-DUs)330and O-RAN RUs (O-RUs)340, respectively.

In some aspects, the DUs330and the RUs340may be implemented according to a functional split architecture in which functionality of a base station110(e.g., an eNB or a gNB) is provided by a DU330and one or more RUs340that communicate over a fronthaul link. Accordingly, as described herein, a base station110may include a DU330and one or more RUs340that may be co-located or geographically distributed. In some aspects, the DU330and the associated RU(s)340may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, to exchange non-real-time management information via an LLS management plane (LLS-M) interface, and/or to exchange user plane information via an LLS user plane (LLS-U) interface.

Accordingly, the DU330may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs340. For example, in some aspects, the DU330may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and/or modulation and demodulation) based at least in part on a lower layer functional split. Higher layer control functions, such as a packet data convergence protocol (PDCP), radio resource control (RRC), and/or service data adaptation protocol (SDAP), may be hosted by the CU310. The RU(s)340controlled by a DU330may correspond to logical nodes that host RF processing functions and low-PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and/or physical random access channel (PRACH) extraction and filtering) based at least in part on the lower layer functional split. Accordingly, in an O-RAN architecture, the RU(s)340handle all over the air (OTA) communication with a UE120, and real-time and non-real-time aspects of control and user plane communication with the RU(s)340are controlled by the corresponding DU330, which enables the DU(s)330and the CU310to be implemented in a cloud-based RAN architecture.

FIGS.4A-4Bare diagrams illustrating examples400of time domain resource allocations (TDRAs), in accordance with the present disclosure.FIG.4Ashows an example downlink TDRA table410andFIG.4Bshows an example uplink TDRA table420. The downlink TDRA table410may be, for example, a physical downlink shared channel (PDSCH) TDRA table. The uplink TDRA table420may be, for example, a physical uplink shared channel (PUSCH) TDRA table. In some aspects, the base station110and the UE120may use different TDRA tables than those shown inFIGS.4A-4B, such as for different configurations, different cells, and/or different sub-carrier spacings of cells.

When scheduling a downlink communication or an uplink communication, a base station110may transmit a physical downlink control channel (PDCCH) carrying downlink control information (DCI) that indicates a TDRA for the downlink or uplink communication. For example, the DCI may include a TDRA field that includes a TDRA index value. The TDRA index value may indicate a row index of a corresponding TDRA table, and the row index may correspond to a set of TDRA parameters (sometimes referred to as scheduling parameters or scheduling information). The base station110and the UE120may use the TDRA parameters in the corresponding row index for the downlink or uplink communication scheduled via the DCI. In the examples shown inFIGS.4A-4B, a TDRA index value of in in the DCI may correspond to a row index of m+1 in the TDRA table. For example, a TDRA index value of 0 may correspond to a row index of 1.

As shown inFIG.4A, for a downlink communication (e.g., a PDSCH communication), the TDRA parameters may include, for example, a K0value, an S value, and an L value. The K0value may represent a timing offset (e.g., in number of slots) between a slot containing the scheduling DCI (carrying a grant that schedules the PDSCH communication) and a slot containing the scheduled PDSCH communication (scheduled via the scheduling DCI). For example, as shown inFIG.4A, and by reference number412, a UE may receive DCI scheduling a PDSCH in a PDCCH monitoring occasion of slot number 0, and a value of the K0parameter may indicate the slot in which the UE can expect to receive the PDSCH scheduled via the DCI. For example, as shown by reference number414, the UE may expect to receive the PDSCH in slot number 3 based on receiving the scheduling DCI in slot number 0 with the K0parameter indicating a timing offset of three slots. The S value may represent a starting symbol for the PDSCH communication in the indicated slot. The L value may represent a length (e.g., a number of consecutive symbols) of the PDSCH communication (e.g., in the indicated slot). In some cases, the S value and the L value may collectively be referred to as a start and length indicator value (SLIV). In some aspects, the same row index value may correspond to a different set of TDRA parameters depending on a Type A DMRS position (e.g., a symbol within a resource block that contains the DMRS) and/or a PDSCH mapping type (e.g., indicating a starting symbol of the DMRS, a length of the DMRS, and/or whether slot-based scheduling or mini-slot-based scheduling is used).

Furthermore, in some aspects, a K1parameter may be used to indicate a timing offset between the PDSCH scheduled via the DCI and a slot in which the UE is to transmit a physical uplink control channel (PUCCH) that carries acknowledgement/negative acknowledgement (ACK/NACK) feedback for the PDSCH, such as HARQ ACK/NACK feedback. For example, as shown by reference number416, the UE may be expected to receive a PDSCH in slot number 3 based on the value of the K0parameter, and may transmit a PUCCH that carries ACK/NACK feedback for the PDSCH in slot number 8 based on the K1parameter indicating a timing offset of five slots from the slot in which the PDSCH is scheduled (e.g., slot number 3 in the illustrated example). In cases where a PDCCH contains a multi-PDSCH grant, the K1parameter may be counted from the slot in which the last granted PDSCH is scheduled.

As shown inFIG.4B, for an uplink communication (e.g., a PUSCH communication), the TDRA parameters may include, for example, a K2value, an S value, and an L value. The K2value may represent a timing offset (e.g., in number of slots) between a slot containing the scheduling DCI (carrying a grant that schedules the PUSCH communication) and a slot containing the scheduled PUSCH communication (scheduled via the scheduling DCI). For example, as shown inFIG.4B, and by reference number422, a UE may receive DCI scheduling a PUSCH in a PDCCH monitoring occasion of slot number 4, and a value of the K2parameter may indicate the slot in which the UE can expect to receive the PUSCH scheduled via the DCI. For example, as shown inFIG.4B, and by reference number424, the UE may expect to receive the PUSCH in slot number 9 based on receiving the scheduling DCI in slot number 4 with the K2parameter indicating a timing offset of five slots. The S value may represent a starting symbol for the PUSCH communication in the indicated slot. The L value may represent a length (e.g., a number of consecutive symbols) of the PUSCH communication (e.g., in the indicated slot). In some aspects, the same row index value may correspond to a different set of TDRA parameters depending on, for example, a PUSCH mapping type (e.g., indicating a starting symbol of the DMRS, a length of the DMRS, and/or whether slot-based scheduling or mini-slot-based scheduling is used).

Accordingly, various timing offsets may be used in a wireless network to indicate a timing offset between a PDCCH, a PDSCH, a PUCCH, and/or a PUSCH. For example, as described above, a K0parameter may indicate a timing offset (or slot offset) between a slot in which a PDCCH is received and a slot in which a PDSCH granted by the PDCCH is scheduled, a K1parameter may indicate a timing offset between the slot in which the PDSCH is scheduled and a slot in which a UE is to transmit ACK/NACK feedback for the PDSCH, and/or a K2parameter may indicate a timing offset between a slot in which a PDCCH is received and a slot in which a PUSCH granted by the PDCCH is scheduled. In general, the K0, K1, and/or K2parameters may be determined based on a TDRA field in the scheduling DCI. For example, the TDRA field may have a value that indicates a row index in an RRC-configured TDRA table, and the indicated row index may include a value for the K0, K1, and/or K2parameter (e.g., depending on whether the DCI schedules a PDSCH and/or a PUSCH). However, in some cases, a UE may receive a PDCCH that schedules a PDSCH and/or a PUSCH before receiving an RRC configuration. In such cases, the UE may determine the value(s) of the K0, K1, and/or K2parameters from a default set of values indicated in a default TDRA table. For example, in the PDSCH default TDRA table, the K0parameter may have a value of zero slots or one slot, whereby the PDSCH is either scheduled in the same slot as the PDCCH or the next slot after the PDSCH, and the K1parameter may have a value in a range from one to eight slots when carrying ACK/NACK feedback for a PDSCH scheduled via fallback DCI (e.g., DCI format 1_0). Alternatively, when a DCI format other than DCI format 1_0 schedules a PDSCH or a semi-persistent scheduling (SPS) release, the K1parameter may be determined by a PDSCH-to-HARQ feedback timing indicator field in the scheduling DCI, which may map to a value for the K1parameter that is provided by a configured parameter (e.g., dl-DataToUL-ACK, or dl-DataToUL-ACKForDCIForat1_2 for DCI format 1_2) that can have a value in a range from zero to fifteen. Furthermore, in the PUSCH default TDRA table, the K2parameter may have a value of j, j+1, j+2, or j+3, where j is one for a subcarrier spacing of 15 kilohertz (kHz), one for a subcarrier spacing of 30 kHz, two for a subcarrier spacing of 60 kHz, or three for a subcarrier spacing of 120 kHz.

In some aspects, a HARQ ACK codebook may be used to provide ACK/NACK feedback corresponding to multiple downlink slots (e.g., multiple PDSCHs), and thus the HARQ ACK codebook may be based at least in part on multiple K1values, each associated with a corresponding downlink slot. Aspects of the HARQ ACK codebook are described in more detail in connection withFIG.5.

As indicated above,FIGS.4A-4Bare provided as examples. Other examples may differ from what is described with regard toFIGS.4A-4B.

FIG.5is a diagram illustrating an example500of a HARQ ACK codebook, in accordance with the present disclosure.

In some instances, a UE120may provide HARQ ACK/NACK feedback to a network entity (e.g., a base station110, a CU310, a DU330, an RU340, or a similar network entity) for a downlink transmission (e.g., a PDSCH transmission) using a HARQ ACK codebook transmitted in a PUSCH or a PUCCH. A HARQ ACK codebook is a sequence of bits that is constructed using ACK/NACK feedback of multiple downlink receptions (e.g., multiple PDSCH transmissions) during a configured time window. A HARQ ACK codebook may be a type 1 codebook or a type 2 codebook. A type 1 codebook is a fixed size codebook (e.g., has a fixed number of bits) indicated by a network entity via RRC signaling (e.g., a type 1 codebook may be referred to as a semi-static codebook). A total size of a type 1 codebook is equal to the sum of downlink transmission occasions (e.g., PDSCH occasion) for a given time window. The sum of downlink transmission occasions may account for multiple PDSCH transmissions in a single slot, multiple PDSCH transmissions across multiple slots, multiple PDSCH transmissions across component carriers, multiple transport blocks (TBs) for a specific PDSCH transmission, and/or multiple code block groups (CBGs) for each TB. A type 2 codebook has a dynamic size that changes according to resource allocation (e.g., a type 2 codebook may be referred to as a dynamic codebook).

In some cases, a HARQ ACK codebook may thus provide HARQ ACK/NACK feedback corresponding to multiple downlink slots (e.g., multiple PDSCH transmissions). More particularly, a UE120may transmit corresponding HARQ ACK/NACK information in a PUCCH or PUSCH in an uplink slot, sometimes referred to as nU, as shown inFIG.5. Moreover, the HARQ ACK codebook transmitted in slot nUmay contain feedback for a set of downlink slots, with each slot sometimes referred to as nD,k. A number of downlink slots (sometimes referred to as NK) for which HARQ ACK/NACK feedback may be provided in the HARQ ACK codebook may be equal to a number of downlink slots overlapping with uplink slot nU-K1,k, where K1,kcorresponds to the K1offset associated with the downlink transmission in the corresponding slot, nD,k.

For example, and as shown inFIG.5, a PUSCH or a PUCCH used to transmit a HARQ ACK codebook may be scheduled in an uplink slot, nU, which in the depicted example is slot 11. In this example, the HARQ ACK codebook includes HARQ ACK/NACK feedback associated with four downlink slots: nD,1(e.g., slot 8), nD,2(e.g., slot 7) nD,3(e.g., slot 6), and nD,4(e.g., slot 5). This is because each corresponding downlink slot (e.g., each of nD,1, nD,2, nD,3, and nD,4) overlaps with a corresponding uplink slot nU-K1,k. More particularly, a DCI scheduling a PDSCH transmission in nD,1(e.g., slot 8) may have indicated that a corresponding K1offset (e.g., K1,1) is equal to 3 slots, and thus ACK/NACK feedback for nD,1may be provided in nU(e.g., slot 11) because nD,1overlaps with uplink slot nU-K1,k(e.g., uplink slot 11-3=slot 8). Similarly, a DCI scheduling a PDSCH transmission in slots nD,2(e.g., slot 7), nD,3(e.g., slot 6), and nD,4(e.g., slot 5) may have indicated that a corresponding K1offset (e.g., K1,2, K1,3, and K1,4) is equal to 4 slots, 5 slots, and 6 slots, respectively, and thus ACK/NACK feedback for nD,2, nD,3, and nD,4may be provided in nU(e.g., slot 11) because nD,2, nD,3, and nD,4overlap with uplink slot nU-K1,k(e.g., uplink slot 11-4=slot 7 for nD,2, uplink slot 11-5=slot 6 for nD,3, and uplink slot 11-6=slot 5 for nD,4). Accordingly, in this example, the HARQ ACK codebook transmitted in nU(e.g., transmission in the PUSCH or PUCCH in slot 11) may be a sequence of bits constructed using ACK/NACK feedback of downlink receptions received in PDSCH in slots 5, 6, 7, and 8.

In some cases, a UE120may receive downlink transmissions from, and thus transmit a HARQ ACK codebook to, a network entity associated with a non-terrestrial network (NTN). In such cases, the above-described HARQ ACK codebook timeline may be inadequate for providing feedback, due to large propagation delays associated with the NTN, or the like. Aspects of the NTN are described in more detail in connection withFIG.6.

FIG.6is a diagram illustrating an example600of an NTN, in accordance with the present disclosure.

As shown inFIG.6, for an NTN, a base station110or other network entity (e.g., a CU310, a DU330, an RU340, or a similar network entity) may be in communication with a gateway605, which may be in communication with a satellite610via a feeder link615. The satellite610may provide coverage to one or more UEs120in a cell620via respective service links625(e.g., the satellite610may act as a gNB or the like, providing coverage to the UEs120in the cell620). In this regard, communications between the base station110or other network component and a UE120may be associated with a large round trip time (RTT), such as an RTT of 500 milliseconds (ms) or even more, due to the propagation delay between the base station110and the UE120, via the gateway605and the satellite610.

In such cases, the HARQ ACK codebook timeline described in connection withFIG.5may be inadequate for a UE120to provide meaningful feedback to the base station110or other network entity. More particularly, the uplink slot for providing feedback, nU(e.g., slot 11), may occur prior to a UE120receiving transmissions associated with one or more downlink slots, nD,k, due to the propagation delay associated with those transmissions. Accordingly, the UE120may not be able to provide a complete HARQ ACK codebook, or else may signal NACK in the HARQ ACK codebook for certain downlink transmissions that safely arrive later-in-time at the UE120than the uplink slot, nU. As a result, the UE120and/or one or more network entities may consume computing, power, network, and/or communication resources in order to detect and/or correct communication errors, including retransmitting communications that ultimately safely arrive at the UE120, but after the uplink slot, nU. This may lead to increased latency and decreased throughput, and overall inefficient usage of network resources.

Some techniques and apparatuses described herein enable signaling of a scheduling offset associated with a HARQ ACK codebook. The scheduling offset may indicate an offset, in a number of slots, for transmitting a HARQ ACK codebook, such as a HARQ ACK codebook associated with one or more downlink communications received via an NTN. In some aspects, a UE (e.g., UE120) may transmit the HARQ ACK codebook based at least in part on the scheduling offset, and, in some aspects, further based at least in part on a feedback channel offset value, such as a K1offset value. In this regard, the HARQ ACK codebook may include a number of HARQ ACK information bits, with each HARQ ACK information bit indicating feedback corresponding to a downlink slot that overlaps with another uplink slot preceding the HARQ ACK slot by a number of slots equal to a sum of the scheduling offset and the feedback channel offset. As a result of the UE transmitting the HARQ ACK codebook based at least in part on the scheduling offset, the UE and/or one or more network entities may conserve computing, power, network, and/or communication resources that may have otherwise been consumed transmitting a HARQ ACK codebook without consideration of the scheduling offset. For example, based at least in part on UE transmitting the HARQ ACK codebook based at least in part on the scheduling offset, the UE and the one or more network entities may communicate with a reduced error rate, which may conserve computing, power, network, and/or communication resources that may have otherwise been consumed to detect and/or correct communication errors. As a result, aspects of the disclosure may result in decreased latency and increased throughput, and overall efficient usage of network resources.

FIG.7is a diagram of an example700associated with a scheduling offset for a HARQ ACK codebook, in accordance with the present disclosure. As shown inFIG.7, a UE705(e.g., UE120) may communicate with a network entity710(e.g., a base station110, a CU310, a DU330, an RU340, a satellite610, and/or a similar network entity). In some aspects, the UE705and the network entity710may be part of a wireless network, such as the wireless network100described in connection withFIG.1and/or the NTN described in connection withFIG.6. The UE705and the network entity710may have established a wireless connection prior to operations shown inFIG.7.

As shown by reference number715, the UE705may receive, from the network entity710, configuration information. In some aspects, the UE705may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and/or DCI, among other examples. In some aspects, the configuration information may include an indication of one or more configuration parameters (e.g., already known to the UE705and/or previously indicated by the network entity710or other network entity) for selection by the UE705, and/or explicit configuration information for the UE705to use to configure the UE705, among other examples.

In some aspects, the configuration information may configure the UE705to use a scheduling offset for transmitting a HARQ ACK codebook. For example, the configuration information may indicate that HARQ ACK information bits in the HARK ACK codebook should indicate ACK/NACK feedback for downlink slots (e.g., nD,k) that precede an uplink slot (e.g., nU) by a sum of a feedback channel offset value (K1,k) and the scheduling offset, sometimes referred to as Ksch_offset(which, in some aspects, may be equal to 2μ*Koffset, where μ is a numerology used for transmission, e.g., μ stands for a subcarrier spacing of 2μ*15 kHz, and Koffsetis a parameter signaled to the UE705by the network entity710, as described in more detail below). In that regard, in the communication indicated by reference number715, the UE705may receive, from the network entity710, an indication of the scheduling offset (e.g., Ksch_offsetand/or Koffset) associated with a HARQ ACK codebook. As described in more detail in connection withFIG.8below, the scheduling offset may indicate an offset, in a number of slots, associated with transmission of the HARQ ACK codebook with respect to a downlink slot containing a corresponding downlink data transmission (e.g., a PDSCH). Additionally, or alternatively, in some aspects the UE120may identify an offset, in a number of slots, associated with transmission of the HARQ ACK codebook with respect to a downlink slot containing a corresponding downlink data transmission (e.g., a PDSCH) using an expression (e.g., 2μ*Koffset) that is based at least in part on a scheduling offset parameter signaled to the UE705by the network entity710(e.g., Koffset) and a numerology used for transmission (e.g., μ), which is described in more detail below.

In some aspects, the network entity710may configure the UE705with at least one of a cell-specific offset (sometimes referred to as Kcell,offset) or a UE-specific offset (sometimes referred to as KUE,offset). A cell-specific offset may be a scheduling offset that is applicable to each UE within a given cell, such as the cell620described in connection withFIG.6. In that regard, the satellite610may configure each UE120within the cell620with the cell-specific offset. A UE-specific offset may be a scheduling offset that is applicable only to one or more UEs receiving the UE-specific offset and/or one or more UEs indicated to be associated with the UE-specific offset. For example, in the arrangement shown inFIG.6, the satellite610may configure a first UE120of the three UEs120with a first UE-specific offset, the satellite610may configure a second UE120of the three UEs120with a second UE-specific offset, and/or the satellite610may configure a third UE120of the three UEs120with a third UE-specific offset.

Accordingly, in some aspects, the scheduling offset indicated by the message shown at reference number715may be the cell-specific offset and/or the UE-specific offset described above, or else may be a zero value. For example, the network entity710may indicate the cell-specific offset using a system information block (SIB) broadcast, such as via a cellspecificKoffset information element of a SIB broadcast. Additionally, or alternatively, the network entity710may indicate the UE-specific offset using at least one of a MAC-CE message or an RRC message. When the scheduling offset is a zero value, the network entity710may explicitly indicate the zero value by at least one of a MAC-CE message or an RRC message, or the network entity710may implicitly indicate the zero value by an absence of signaling of an offset value (e.g., absence of signaling of a cell-specific offset and a UE-specific offset).

The UE705may configure itself based at least in part on the configuration information. In some aspects, the UE705may be configured to perform one or more operations described herein based at least in part on the configuration information. For example, when the configuration information configures a scheduling offset (e.g., Ksch_offset, Koffset, Kcell,offset, and/or KUE,offset), the UE705may be configured to transmit, to the network entity710, the HARQ ACK codebook based at least in part on the scheduling offset. Additionally, or alternatively, if the UE705is configured to use one of a cell-specific offset or a UE-specific offset, the UE705may be configured to transmit, to the network entity710, the HARQ ACK codebook based at least in part on the one of the cell-specific offset or the UE-specific offset. In some aspects, the UE705may be configured with only the cell-specific offset, and thus the UE705may be configured to transmit the HARQ ACK codebook based at least in part on the cell-specific offset. In some other aspects, the UE705may be configured with only the UE-specific offset, and thus the UE705may be configured to transmit the HARQ ACK codebook based at least in part on the UE-specific offset. In some other aspects, the UE705may be configured with both the cell-specific offset and the UE-specific offset, and thus the UE705may be configured to transmit the HARQ ACK codebook based at least in part on one of the cell-specific offset or the UE-specific offset. For example, in some aspects, when the configuration information configures both the cell-specific offset and the UE-specific offset, the UE705may transmit the HARQ ACK codebook based at least in part on the UE-specific offset.

Moreover, in some aspects, the UE705may transmit the HARQ ACK codebook further based at least in part on a feedback channel offset value (e.g., a K1offset or K1,kvalue, as described in connection withFIGS.4A and5). In such aspects, and as shown by reference number720, the UE705may receive, from the network entity710, an indication of the feedback channel offset value associated with the HARQ ACK codebook. For example, in some aspects, the UE705may receive the indication of the feedback channel offset value in DCI scheduling a downlink communication (e.g., a PDSCH) associated with a downlink slot corresponding to the feedback channel offset value. Aspects of the feedback channel offset value are described in more detail in connection withFIG.8.

As shown at reference number725, in some aspects, the UE705may transmit, to the network entity710, the HARQ ACK codebook based at least in part on the scheduling offset (e.g., Ksch_offset, Koffset, Kcell,offset, and/or KUE,offset). In some aspects, the HARQ ACK codebook may be transmitted in one of a PUSCH or a PUCCH.

Moreover, in aspects in which the UE705received an indication of a feedback channel offset value (e.g., a K1offset or K1,kvalue), the transmission may be further based at least in part on the feedback channel offset value (e.g., the UE705may transmit, to the network entity710, the HARQ ACK codebook based at least in part on the scheduling offset and the feedback channel offset value). More particularly, in some aspects, the HARQ ACK codebook may be transmitted in an uplink slot (e.g., nU), the feedback channel offset value (e.g., K1,k) may be associated with a downlink slot (e.g., nD,k), and a HARQ ACK information bit associated with the HARQ ACK codebook may indicate feedback corresponding to the downlink slot. In such aspects, the downlink slot (e.g., nD,k) may overlap with another uplink slot that precedes the uplink slot (e.g., nU) by a number of slots equal to a sum of the scheduling offset (e.g., Ksch_offset) and the feedback channel offset (e.g., K1,k). That is, a HARQ ACK information bit in a HARQ ACK codebook may indicate feedback for a downlink communication transmitted in a slot (nD,k) that overlaps with an uplink slot located at nU— (Ksch_offset+K1,k) (or, put a different way, nU-Ksch_offset-K1,kand/or nU−2μ×Koffset-K1,k). In some aspects, the UE705may transmit the HARQ ACK codebook based at least in part on an expression associated with the scheduling offset and a feedback channel offset value, and, in some aspects, the expression may be equal to Ksch_offset+K1,k.

The HARQ ACK codebook may be one of a type 1 codebook (e.g., a semi-static codebook), or a type 2 codebook (e.g., a dynamic codebook). For example, in some aspects, the downlink slot (e.g., nD,k) may be associated with an occasion for a candidate PDSCH reception, may be associated with a semi-persistent PDSCH release, and/or may be associated with a transmission configuration indicator (TCI) state update. In such aspects, the HARQ ACK codebook may be a type 1 codebook. In some other aspects, the downlink slot (e.g., nD,k) may be associated with a monitoring occasion corresponding to a PDCCH associated with a DCI format scheduling a PDSCH reception, or may be associated with a monitoring occasion corresponding to a PDCCH associated with a DCI format that does not schedule a PDSCH reception but that is nonetheless associated with HARQ ACK information. In such aspects, the HARQ ACK codebook may be a type 2 codebook.

In some other aspects, the scheduling offset (e.g., Ksch_offset) may be based at least in part on a signaled value. For example, in some aspects, the network entity710may transmit a signaled offset value (sometimes referred to as Koffset), and the UE705may determine the scheduling offset based at least in part on the signaled offset value. In some aspects, the scheduling offset (e.g., Ksch_offset) may be based at least in part on a product of the signaled offset value (e.g., Koffset) and a subcarrier spacing scaling factor. Moreover, in some aspects, the subcarrier spacing scaling factor may be based at least in part on a numerology used for transmission of the HARQ ACK codebook, sometimes referred to as μULor simply μ for ease of discussion. In some aspects, μULmay correspond to an uplink subcarrier spacing (SCS) of 15*2μULkHz. Put another way, μULmay be equal to 0, 1, 2, 3, or 4 for SCSs of 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz, respectively. In some aspects, the subcarrier spacing scaling factor is equal to two to a power of the numerology used for transmission of the HARQ ACK codebook (e.g., 2μUL). Thus, in such aspects, Ksch_offset=2μUL*Koffset. Aspects of transmitting the HARQ ACK codebook based at least in part on the scheduling offset are described in more detail in connection withFIG.8.

FIG.8is a diagram illustrating an example800of a scheduling offset for a HARQ ACK codebook, in accordance with the present disclosure.

In this aspect shown inFIG.8, a UE (e.g., UE705) may be configured to transmit a HARQ ACK codebook in an uplink slot (e.g., nU), which, in the depicted example, is slot 11. More particularly, the UE may be configured to transmit the HARQ ACK codebook in a PUSCH and/or a PUCCH associated with slot 11. In this example, the UE has been configured with a scheduling offset (e.g., Ksch_offsetand/or Koffset). More particularly, the UE may have received an indication from a network entity (e.g., network entity710) that the HARQ ACK codebook should be transmitted based at least in part on the scheduling offset (e.g., Ksch_offsetand/or 2μ*Koffset), which, in the depicted example, is 4 slots. As described above, in some aspects the scheduling offset may account for a propagation delay associated with an NTN, or the like. Moreover, the scheduling offset may be a cell-specific offset or a UE-specific offset, as described in connection withFIG.7. The scheduling offset may further be based at least in part on a signaled offset (e.g., Koffset), as described in connection withFIG.7. For example, in some aspects, the scheduling offset may be equal to 2μUL*Koffset.

In such aspects, for an uplink control information (UCI) carrying the HARQ ACK codebook in the uplink slot (e.g., nU), a HARQ ACK information bit may correspond to a downlink slot (e.g., nD,k) that overlaps an uplink slot with slot index nU−K1,k−2μUL*Koffset(e.g., nU−(K1,k2μUL*Koffset)), where K1,kis the PDSCH-to-HARQ feedback timing parameter for the downlink slot (e.g., nD,k). In the example shown inFIG.8, this corresponds to a set of downlink slots (e.g., Nk) including nD,1(e.g., slot 4), nD,2(e.g., slot 3), nD,3(e.g., slot 2), and nD,4(e.g., slot 1). More particularly, nod may be associated with a K1offset (e.g., K1,1) of 3 slots, and thus the UE may provide HARQ ACK/NACK feedback for nD,1in the HARQ ACK codebook because nD,1precedes nUby 7 slots (e.g., K1,1(3 slots)+2μUL*Koffset(4 slots)). Similarly, nD,2, nD,3, and nD,4may be associated with K1offsets (e.g., K1,2, K1,3, and K1,4) of 4 slots, 5 slots, and 6 slots, and thus the UE may provide HARQ ACK/NACK feedback for nD,2, nD,3, and nD,4in the HARQ ACK codebook because nD,2, nD,3, and nD,4precede nUby 8 slots, 9 slots, and 10 slots, respectively. Thus, in the depicted example, the HARQ ACK codebook may include a sequence of bits that is constructed using ACK/NACK feedback of nD,1, nD,2, nD,3, and nD,4.

More broadly, in some aspects, a UE may be permitted to transmit corresponding HARQ ACK information in a PUCCH or PUSCH in slot nU. In such aspects, if mod (nU−2μULKoffset−K1,k+1,max(2μUL-μDL, 1))=0 (with μUL, corresponding to the numerology used for the uplink and μDLcorresponding to the numerology used for the downlink), or if a PUCCH length parameter (sometimes referred to as subslotLengthForPUCCH) is provided for the HARQ ACK codebook, nDmay be set to 0-index of a downlink slot overlapping with an uplink slot, and Nkmay be set to a number of downlink slots overlapping with uplink slot nU−2μULKoffset−K1,kif subslotLengthForPUCCH is provided for the HARQ ACK codebook (otherwise, Nkmay be equal to max(2μUL-μDL,1)).

Put another way, in some aspects, a UE may be permitted to transmit corresponding HARQ ACK information in a PUCCH or PUSCH in slot nU+2μULKoffset. In such aspects, if mod (nU−K1,k+1,max(2μUL-μDL,1))=0, or if a PUCCH length parameter (e.g., subslotLengthForPUCCH) is provided for the HARQ ACK codebook, then nDmay be set to 0-index of a downlink slot overlapping with an uplink slot, and Nkmay be set to a number of downlink slots overlapping with uplink slot nU−K1,kif subslotLengthForPUCCH is provided for the HARQ ACK codebook (otherwise, Nkmay be equal to max(2μUL-μDL, 1)).

FIG.9is a diagram illustrating an example process900performed, for example, by a UE, in accordance with the present disclosure. Example process900is an example where the UE (e.g., UE705) performs operations associated with a scheduling offset for a HARQ ACK codebook.

As shown inFIG.9, in some aspects, process900may include receiving, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook (block910). For example, the UE (e.g., using communication manager1108and/or reception component1202, depicted inFIG.12) may receive, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook, as described above.

As further shown inFIG.9, in some aspects, process900may include transmitting, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset (block920). For example, the UE (e.g., using communication manager1108and/or transmission component1104, depicted inFIG.11) may transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset, as described above.

In a first aspect, process900includes receiving, from the network entity, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein transmitting the HARQ ACK codebook is further based at least in part on the feedback channel offset value.

In a second aspect, alone or in combination with the first aspect, the HARQ ACK codebook is transmitted in an uplink slot, the feedback channel offset value is associated with a downlink slot, and a HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink slot.

In a third aspect, alone or in combination with one or more of the first and second aspects, the downlink slot overlaps with another uplink slot, and the other uplink slot precedes the uplink slot by a number of slots equal to a sum of the scheduling offset and the feedback channel offset value.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the downlink slot is associated with at least one of an occasion for a candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator state update.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the HARQ ACK codebook is a type 1 codebook.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the downlink slot is associated with a monitoring occasion corresponding to at least one of a PDCCH associated with a DCI format scheduling a PDSCH reception, or a PDCCH associated with a DCI format that does not schedule a PDSCH reception and is associated with HARQ ACK information.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the HARQ ACK codebook is a type 2 codebook.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the scheduling offset is based at least in part on a signaled offset value received from the network entity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the scheduling offset is based at least in part on a product of the signaled offset value and a subcarrier spacing scaling factor.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the subcarrier spacing scaling factor is based at least in part on a numerology used for transmission of the HARQ ACK codebook.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the subcarrier spacing scaling factor is based at least in part on two to a power of the numerology used for transmission of the HARQ ACK codebook.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, transmitting the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and a feedback channel offset value.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the scheduling offset is one of a cell-specific offset, a UE-specific offset, or a zero value.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process900includes receiving, from the network entity, a configuration configuring only the cell-specific offset, wherein transmitting the HARQ ACK codebook is based at least in part on the cell-specific offset.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process900includes receiving, from the network entity, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, wherein transmitting the HARQ ACK codebook is based at least in part on the UE-specific offset.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the scheduling offset is the cell-specific offset, and the cell-specific offset is indicated by a system information block message.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the scheduling offset is the UE-specific offset, and the UE-specific offset is indicated by one of a MAC-CE message, or an RRC message.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the scheduling offset is the zero value, and the zero value is indicated by one of a MAC-CE message, an RRC message, or an absence of signaling of an offset value.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the HARQ ACK codebook is transmitted via one of a physical uplink control channel or a physical uplink shared channel.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the network entity is associated with an NTN, and the scheduling offset is associated with a propagation delay associated with the NTN.

FIG.10is a diagram illustrating an example process1000performed, for example, by a network entity, in accordance with the present disclosure. Example process1000is an example where the network entity (e.g., network entity710) performs operations associated with a scheduling offset for a HARQ ACK codebook.

As shown inFIG.10, in some aspects, process1000may include transmitting, to a UE (e.g., UE705), an indication of a scheduling offset associated with a HARQ ACK codebook (block1010). For example, the network entity (e.g., using communication manager1208and/or transmission component1204, depicted inFIG.12) may transmit, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook, as described above.

As further shown inFIG.10, in some aspects, process1000may include receiving, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset (block1020). For example, the network entity (e.g., using communication manager1208and/or reception component1202, depicted inFIG.12) may receive, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset, as described above.

In a first aspect, process1000includes transmitting, to the UE, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein receiving the HARQ ACK codebook is further based at least in part on the feedback channel offset value.

In a second aspect, alone or in combination with the first aspect, the HARQ ACK codebook is transmitted in an uplink slot, wherein the feedback channel offset value is associated with a downlink slot, and wherein a HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink slot.

In a third aspect, alone or in combination with one or more of the first and second aspects, the downlink slot overlaps with another uplink slot, and the other uplink slot precedes the uplink slot by a number of slots equal to a sum of the scheduling offset and the feedback channel offset value.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the downlink slot is associated with at least one of an occasion for a candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator state update.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the HARQ ACK codebook is a type 1 codebook.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the downlink slot is associated with a monitoring occasion corresponding to at least one of a PDCCH associated with a DCI format scheduling a PDSCH reception, or a PDCCH associated with a DCI format that does not schedule a PDSCH reception and is associated with HARQ ACK information.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the HARQ ACK codebook is a type 2 codebook.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the scheduling offset is based at least in part on a signaled offset value transmitted by the network entity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the scheduling offset is based at least in part on a product of the signaled offset value and a subcarrier spacing scaling factor.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the subcarrier spacing scaling factor is based at least in part on a numerology used for transmission of the HARQ ACK codebook.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the subcarrier spacing scaling factor is based at least in part on two to a power of the numerology used for transmission of the HARQ ACK codebook.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, transmitting the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and a feedback channel offset value.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the scheduling offset is one of a cell-specific offset, a UE-specific offset, or a zero value.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process1000includes transmitting, to the UE, a configuration configuring only the cell-specific offset, wherein receiving the HARQ ACK codebook is based at least in part on the cell-specific offset.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, process1000includes transmitting, to the UE, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, wherein receiving the HARQ ACK codebook is based at least in part on the UE-specific offset.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the scheduling offset is the cell-specific offset, and the cell-specific offset is indicated by a system information block message.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the scheduling offset is the UE-specific offset, and the UE-specific offset is indicated by one of a MAC-CE message, or an RRC message.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the scheduling offset is the zero value, and the zero value is indicated by one of a MAC-CE message, an RRC message, or an absence of signaling of an offset value.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the HARQ ACK codebook is received via one of a physical uplink control channel or a physical uplink shared channel.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the network entity is associated with an NTN, and the scheduling offset is associated with a propagation delay associated with the NTN.

The reception component1102and/or the feedback component1110may receive, from a network entity (e.g., network entity710), an indication of a scheduling offset associated with a HARQ ACK codebook. The transmission component1104and/or the feedback component1110may transmit, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.

The reception component1102and/or the feedback component1110may receive, from the network entity, an indication of a feedback channel offset value associated with the HARQ ACK codebook, and transmitting the HARQ ACK codebook may be further based at least in part on the feedback channel offset value.

The reception component1102and/or the feedback component1110may receive, from the network entity, a configuration configuring only the cell-specific offset, and transmitting the HARQ ACK codebook may be based at least in part on the cell-specific offset.

The reception component1102and/or the feedback component1110may receive, from the network entity, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, and transmitting the HARQ ACK codebook may be based at least in part on the UE-specific offset.

FIG.12is a diagram of an example apparatus1200for wireless communication, in accordance with the present disclosure. The apparatus1200may be a network entity (e.g., network entity710), or a network entity may include the apparatus1200. In some aspects, the apparatus1200includes a reception component1202and a transmission component1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1200may communicate with another apparatus1206(such as a UE, a base station, or another wireless communication device) using the reception component1202and the transmission component1204. As further shown, the apparatus1200may include the communication manager1208(e.g., communication manager150). The communication manager1208may include a configuration component1210, among other examples.

The transmission component1204and/or the configuration component1210may transmit, to a UE (e.g., UE705), an indication of a scheduling offset associated with a HARQ ACK codebook. The reception component1202may receive, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.

The transmission component1204and/or the configuration component1210may transmit, to the UE, an indication of a feedback channel offset value associated with the HARQ ACK codebook, and receiving the HARQ ACK codebook may be further based at least in part on the feedback channel offset value.

The transmission component1204and/or the configuration component1210may transmit, to the UE, a configuration configuring only the cell-specific offset, and receiving the HARQ ACK codebook may be based at least in part on the cell-specific offset.

The transmission component1204and/or the configuration component1210may transmit, to the UE, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, and receiving the HARQ ACK codebook may be based at least in part on the UE-specific offset.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a UE, comprising: receiving, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook; and transmitting, to the network entity, the HARQ ACK codebook based at least in part on the scheduling offset.Aspect 2: The method of Aspect 1, further comprising receiving, from the network entity, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein transmitting the HARQ ACK codebook is further based at least in part on the feedback channel offset value.Aspect 3: The method of Aspect 2, wherein the HARQ ACK codebook is transmitted in an uplink slot, wherein the feedback channel offset value is associated with a downlink slot, and wherein a HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink slot.Aspect 4: The method of Aspect 3, wherein the downlink slot overlaps with another uplink slot, and wherein the other uplink slot precedes the uplink slot by a number of slots equal to a sum of the scheduling offset and the feedback channel offset value.Aspect 5: The method of any of Aspects 3-4, wherein the downlink slot is associated with at least one of an occasion for a candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator state update.Aspect 6: The method of Aspect 5, wherein the HARQ ACK codebook is a type 1 codebook.Aspect 7: The method of any of Aspects 3-4, wherein the downlink slot is associated with a monitoring occasion corresponding to at least one of a PDCCH associated with a DCI format scheduling a PDSCH reception, or a PDCCH associated with a DCI format that does not schedule a PDSCH reception and is associated with HARQ ACK information.Aspect 8: The method of Aspect 7, wherein the HARQ ACK codebook is a type 2 codebook.Aspect 9: The method of any of Aspects 1-8, wherein the scheduling offset is based at least in part on a signaled offset value received from the network entity.Aspect 10: The method of Aspect 9, wherein the scheduling offset is based at least in part on a product of the signaled offset value and a subcarrier spacing scaling factor.Aspect 11: The method of Aspect 10, wherein the subcarrier spacing scaling factor is based at least in part on a numerology used for transmission of the HARQ ACK codebook.Aspect 12: The method of Aspect 11, wherein the subcarrier spacing scaling factor is based at least in part on two to a power of the numerology used for transmission of the HARQ ACK codebook.Aspect 13: The method of any of Aspects 1-12, wherein transmitting the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and a feedback channel offset value.Aspect 14: The method of any of Aspects 1-13, wherein the scheduling offset is one of a cell-specific offset, a UE-specific offset, or a zero value.Aspect 15: The method of Aspect 14, further comprising receiving, from the network entity, a configuration configuring only the cell-specific offset, wherein transmitting the HARQ ACK codebook is based at least in part on the cell-specific offset.Aspect 16: The method of Aspect 14, further comprising receiving, from the network entity, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, wherein transmitting the HARQ ACK codebook is based at least in part on the UE-specific offset.Aspect 17: The method of Aspect 14, wherein the scheduling offset is the cell-specific offset, and wherein the cell-specific offset is indicated by a system information block message.Aspect 18: The method of Aspect 14, wherein the scheduling offset is the UE-specific offset, and wherein the UE-specific offset is indicated by one of a MAC-CE message, or an RRC message.Aspect 19: The method of Aspect 14, wherein the scheduling offset is the zero value, and wherein the zero value is indicated by one of a MAC-CE message, an RRC message, or an absence of signaling of an offset value.Aspect 20: The method of any of Aspects 1-19, wherein the HARQ ACK codebook is transmitted via one of a physical uplink control channel or a physical uplink shared channel.Aspect 21: The method of any of Aspects 1-20, wherein the network entity is associated with an NTN, and wherein the scheduling offset is associated with a propagation delay associated with the NTN.Aspect 22: A method of wireless communication performed by a network entity, comprising: transmitting, to a UE, an indication of a scheduling offset associated with a HARQ ACK codebook; and receiving, from the UE, the HARQ ACK codebook based at least in part on the scheduling offset.Aspect 23: The method of Aspect 22, further comprising transmitting, to the UE, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein receiving the HARQ ACK codebook is further based at least in part on the feedback channel offset value.Aspect 24: The method of Aspect 23, wherein the HARQ ACK codebook is transmitted in an uplink slot, wherein the feedback channel offset value is associated with a downlink slot, and wherein a HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink slot.Aspect 25: The method of Aspect 24, wherein the downlink slot overlaps with another uplink slot, and wherein the other uplink slot precedes the uplink slot by a number of slots equal to a sum of the scheduling offset and the feedback channel offset value.Aspect 26: The method of any of Aspects 24-25, wherein the downlink slot is associated with at least one of an occasion for a candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator state update.Aspect 27: The method of Aspect 26, wherein the HARQ ACK codebook is a type 1 codebook.Aspect 28: The method of Aspect 24, wherein the downlink slot is associated with a monitoring occasion corresponding to at least one of a PDCCH associated with a DCI format scheduling a PDSCH reception, or a PDCCH associated with a DCI format that does not schedule a PDSCH reception and is associated with HARQ ACK information.Aspect 29: The method of Aspect 28, wherein the HARQ ACK codebook is a type 2 codebook.Aspect 30: The method of any of Aspects 22-19, wherein the scheduling offset is based at least in part on a signaled offset value transmitted by the network entity.Aspect 31: The method of Aspect 30, wherein the scheduling offset is based at least in part on a product of the signaled offset value and a subcarrier spacing scaling factor.Aspect 32: The method of Aspect 31, wherein the subcarrier spacing scaling factor is based at least in part on a numerology used for transmission of the HARQ ACK codebook.Aspect 33: The method of Aspect 32, wherein the subcarrier spacing scaling factor is based at least in part on two to a power of the numerology used for transmission of the HARQ ACK codebook.Aspect 34: The method of any of Aspects 22-33, wherein transmitting the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and a feedback channel offset value.Aspect 35: The method of any of Aspects 22-34, wherein the scheduling offset is one of a cell-specific offset, a UE-specific offset, or a zero value.Aspect 36: The method of Aspect 35, further comprising transmitting, to the UE, a configuration configuring only the cell-specific offset, wherein receiving the HARQ ACK codebook is based at least in part on the cell-specific offset.Aspect 37: The method of Aspect 35, further comprising transmitting, to the UE, a configuration configuring the cell-specific offset and a configuration configuring the UE-specific offset, wherein receiving the HARQ ACK codebook is based at least in part on the UE-specific offset.Aspect 38: The method of Aspect 35, wherein the scheduling offset is the cell-specific offset, and wherein the cell-specific offset is indicated by a system information block message.Aspect 39: The method of Aspect 35, wherein the scheduling offset is the UE-specific offset, and wherein the UE-specific offset is indicated by one of a MAC-CE message, or an RRC message.Aspect 40: The method of Aspect 35, wherein the scheduling offset is the zero value, and wherein the zero value is indicated by one of a MAC-CE message, an RRC message, or an absence of signaling of an offset value.Aspect 41: The method of any of Aspects 22-40, wherein the HARQ ACK codebook is received via one of a physical uplink control channel or a physical uplink shared channel.Aspect 42: The method of any of Aspects 22-41, wherein the network entity is associated with an NTN, and wherein the scheduling offset is associated with a propagation delay associated with the NTN.Aspect 43: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-21.Aspect 44: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-21.Aspect 45: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-21.Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-21.Aspect 47: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-21.Aspect 48: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 22-42.Aspect 49: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 22-42.Aspect 50: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 22-42.Aspect 51: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 22-42.Aspect 52: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 22-42.