Scheduling offset for hybrid automatic repeat request acknowledgement codebook

By sending the scheduling offset indication of the HARQ ACK codebook in the wireless communication system, the UE adjusts the codebook transmission based on the scheduling offset and feedback channel offset values, solving the problem of inefficiency of the HARQ confirmation codebook in the NTN environment, and improving the Communication efficiency and throughput.

CN119013933APending Publication Date: 2024-11-22QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034006.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-21
Filing Date
2023-04-24
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In wireless communication systems, the scheduling offset problem of hybrid automatic repeat request (HARQ) confirmation codebooks leads to inefficient communication efficiency, especially in non-terrestrial network (NTN) environments, large propagation delays lead to insufficient HARQ ACK codebook timeline Provide feedback, resulting in waste of error detection and correction resources, increased latency and reduced throughput.

Method used

By sending a scheduling offset indication associated with the HARQ ACK codebook between the user equipment (UE) and the network entity, the UE transmits the HARQ ACK codebook based at least in part on the scheduling offset and feedback channel offset values, adjusting the uplink The route time slot overlaps with the downlink time slot to reduce resource consumption.

Benefits of technology

The calculation, power and network resource consumption of detecting and correcting communication errors is reduced, delay is reduced, communication efficiency and throughput is improved, and the use of network resources is optimized.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119013933A_ABST
    Figure CN119013933A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. 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 the HARQ ACK codebook to the network entity based at least in part on the scheduling offset. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 363,539, filed on April 25, 2022, entitled “SCHEDULING OFFSET FOR HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGEMENT CODEBOOK,” and U.S. Non-Provisional Patent Application No. 18 / 304,965, filed on April 21, 2023, entitled “SCHEDULING OFFSET FOR HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGEMENT CODEBOOK,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for scheduling offsets for a hybrid automatic repeat request acknowledgement codebook. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

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

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

[0009] 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, the one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a scheduling offset associated with a HARQ ACK codebook from a network entity. The one or more processors may be configured to send the HARQ ACK codebook to the network entity based at least in part on the scheduling offset.

[0010] 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, the one or more processors coupled to the memory. The one or more processors may be configured to send an indication of a scheduling offset associated with a HARQ ACK codebook to a UE. The one or more processors may be configured to receive the HARQ ACK codebook from the UE based at least in part on the scheduling offset.

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

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

[0013]

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

[0014]

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

[0015] The various aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of an open radio access network architecture according to the present disclosure.

[0022] FIG. 4A to FIG. 4B is a diagram illustrating an example of time domain resource allocation according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a non-terrestrial network according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example associated with a scheduling offset for a HARQ ACK codebook according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example associated with a scheduling offset for a HARQ ACK codebook according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0029] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or 5G and beyond (e.g., 6G) RATs.

[0034] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE120b, UE120c, UE120d, and UE120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). In addition, although the base station 110 Figure 1 In some other aspects, the functionality of base station 110 may be decomposed according to an open radio access network (O-RAN) architecture, etc., which may be combined with Figure 3 Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0035] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0036] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0037] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communications between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0038] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0039] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0040] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0041] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0044] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

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

[0048] In some aspects, the network entity described herein may be associated with the base station 110. The network entity may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send an indication of a scheduling offset associated with a HARQ ACK codebook to a UE (e.g., UE 120); and receive a HARQ ACK codebook from the UE based at least in part on the scheduling offset. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0050] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0051] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0055] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 7 to 12 ) any aspects of any of the methods described herein.

[0056] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 7 to 12 ) any aspects of any of the methods described herein.

[0057] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the may perform one or more techniques associated with scheduling offsets for HARQ ACK codebooks, as described in more detail elsewhere herein. In some aspects, the network entity described herein is a base station 110, is included in a base station 110, or includes Figure 2 One or more components of the base station 110 are shown. The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig. 9 The process of 900 Fig.10 1000 and / or other processes described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Fig. 9 The process of 900 Fig.10 The operations of process 1000 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the UE 120 includes means for receiving an indication of a scheduling offset associated with the HARQ ACK codebook from a network entity; and / or means for sending the HARQ ACK codebook to the network entity based at least in part on the scheduling offset. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0059] In some aspects, the network entity described elsewhere herein includes means for sending an indication of a scheduling offset associated with a HARQ ACK codebook to a UE (e.g., UE 120); and / or means for receiving the HARQ ACK codebook from the UE 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 the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0060] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0061] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0062] Figure 3 3 is a diagram illustrating an example 300 of an O-RAN architecture according to the present disclosure. Figure 3 As shown, the O-RAN architecture may include a centralized unit (CU) 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links. The DUs 330 may each communicate with one or more radio units (RUs) 340 via corresponding fronthaul links, and the RUs 340 may each communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DU 330 and the RU 340 may also be referred to as O-RAN DU (O-DU) 330 and O-RAN RU (O-RU) 340, respectively.

[0063] In some aspects, the DU 330 and the RU 340 may be implemented according to a functional split architecture in which the functionality of a base station 110 (e.g., an eNB or gNB) is provided by a DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, a base station 110 may include a DU 330 and one or more RUs 340 that may be co-located or geographically distributed. In some aspects, a DU 330 and an associated RU 340 may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0064] Thus, the DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, in some aspects, the DU 330 may 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 the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. The RU 340 controlled by the DU 330 may correspond to a logical node that hosts 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. Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture.

[0065] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0066] FIG. 4A to FIG. 4B is a diagram illustrating an example 400 of time domain resource allocation (TDRA) according to the present disclosure. Figure 4A An example downlink TDRA table 410 is shown, and Figure 4BAn example uplink TDRA table 420 is shown. The downlink TDRA table 410 may be, for example, a physical downlink shared channel (PDSCH) TDRA table. The uplink TDRA table 420 may be, for example, a physical uplink shared channel (PUSCH) TDRA table. In some aspects, the base station 110 and the UE 120 may use the same FIG. 4A to FIG. 4B The TDRA tables shown in FIG. 10A and 10B may be different TDRA tables, such as for different configurations, different cells and / or different subcarrier spacings of cells.

[0067] When scheduling downlink or uplink communications, the base station 110 may send a physical downlink control channel (PDCCH) carrying downlink control information (DCI) indicating the TDRA to be used for the downlink or uplink communications. 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). For downlink or uplink communications scheduled via the DCI, the base station 110 and the UE 120 may use the TDRA parameters in the corresponding row index. FIG. 4A to FIG. 4B In the example shown, the TDRA index value m in the DCI may correspond to the row index m+1 in the TDRA table. For example, the TDRA index value 0 may correspond to the row index 1.

[0068] like Figure 4A As shown, for downlink communication (e.g., PDSCH communication), the TDRA parameters may include, for example, a K0 value, an S value, and an L value. The K0 value may represent a timing offset (e.g., in number of time slots) between a time slot containing a scheduling DCI (carrying a grant for scheduling PDSCH communication) and a time slot containing a scheduled PDSCH communication (scheduled via the scheduling DCI). For example, Figure 4AAs shown and indicated by reference numeral 412, the UE may receive a DCI scheduling a PDSCH in a PDCCH monitoring opportunity of time slot number 0, and the value of parameter K0 may indicate a time slot in which the UE may expect to receive a PDSCH scheduled via the DCI. For example, as shown by reference numeral 414, based on receiving a scheduling DCI in time slot number 0 (wherein parameter K0 indicates a timing offset of three time slots), the UE may expect to receive a PDSCH in time slot number 3. The S value may represent a starting symbol for a PDSCH communication in the indicated time slot. The L value may represent a length (e.g., the number of consecutive symbols) of a PDSCH communication (e.g., in the indicated time slot). In some cases, the S value and the L value may be collectively referred to as a start and length indicator value (SLIV). In some aspects, the same row index value may correspond to different sets of TDRA parameters based on the type ADMRS location (e.g., the symbol within the resource block containing the DMRS) and / or the PDSCH mapping type (e.g., indicating the starting symbol of the DMRS, the length of the DMRS and / or whether slot-based scheduling or mini-slot-based scheduling is used).

[0069] In addition, in some aspects, parameter K1 may be used to indicate a timing offset between a PDSCH scheduled via DCI and a time slot in which the UE will send a physical uplink control channel (PUCCH) carrying acknowledgement / negative acknowledgement (ACK / NACK) feedback (such as HARQ ACK / NACK feedback) for the PDSCH. For example, as indicated by reference numeral 416, the UE may be expected to receive a PDSCH in time slot number 3 based on the value of parameter K0, and may send a PUCCH carrying ACK / NACK feedback for the PDSCH in time slot number 8 based on parameter K1, parameter K1 indicating a timing offset of five time slots from a time slot in which the PDSCH is scheduled (e.g., time slot number 3 in the illustrated example). In the case where the PDCCH contains multiple PDSCH grants, parameter K1 may be counted starting from the time slot in which the last granted PDSCH is scheduled.

[0070] like Figure 4B As shown, for uplink communication (e.g., PUSCH communication), the TDRA parameters may include, for example, a K2 value, an S value, and an L value. The K2 value may represent a timing offset (e.g., in number of time slots) between a time slot containing a scheduling DCI (carrying a grant for scheduling PUSCH communication) and a time slot containing a scheduled PUSCH communication (scheduled via the scheduling DCI). For example, Figure 4B As shown and indicated by reference numeral 422, the UE may receive a DCI scheduling a PUSCH in a PDCCH monitoring opportunity of time slot number 4, and the value of parameter K2 may indicate a time slot in which the UE may expect to receive a PUSCH scheduled via the DCI. Figure 4BAs shown and indicated by reference numeral 424, based on receiving a scheduling DCI in slot number 4 (where parameter K2 indicates a timing offset of five slots), the UE may expect to receive a PUSCH in slot number 9. The S value may indicate a starting symbol for a PUSCH communication in the indicated slot. The L value may indicate a length (e.g., number of consecutive symbols) of a PUSCH communication (e.g., in the indicated slot). In some aspects, the same row index value may correspond to different sets of TDRA parameters, for example, based on a PUSCH mapping type (e.g., indicating a starting symbol for a DMRS, a length of a DMRS, and / or whether slot-based scheduling or mini-slot-based scheduling is used).

[0071] Therefore, 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 parameter K0 may indicate a timing offset (or a time slot offset) between a time slot in which a PDCCH is received and a time slot in which a PDSCH granted by a PDCCH is scheduled, a parameter K1 may indicate a timing offset between a time slot in which a PDSCH is scheduled and a time slot in which a UE will send ACK / NACK feedback for a PDSCH, and / or a parameter K2 may indicate a timing offset between a time slot in which a PDCCH is received and a time slot in which a PUSCH granted by a PDCCH is scheduled. In general, parameters K0, K1, and / or K2 may be determined based on a TDRA field in a scheduling DCI. For example, the TDRA field may have a value indicating a row index in a TDRA table configured by an RRC, and the indicated row index may include values ​​of parameters K0, K1, and / or K2 (e.g., depending on whether the DCI schedules PDSCH and / or PUSCH). However, in some cases, the UE may receive a PDCCH that schedules the PDSCH and / or PUSCH before receiving the RRC configuration. In such cases, the UE may determine the values ​​of parameters K0, K1, and / or K2 from a default set of values ​​indicated by the default TDRA table. For example, in the PDSCH default TDRA table, parameter K0 may have a value of zero slots or one slot, thereby scheduling the PDSCH in the same slot as the PDCCH or in the next slot after the PDSCH, and when carrying ACK / NACK feedback for a PDSCH scheduled via a fallback DCI (e.g., DCI format 1_0), parameter K1 may have a value in the range of one slot to eight slots. Alternatively, when a DCI format other than DCI format 1_0 schedules PDSCH or semi-persistent scheduling (SPS) release, parameter K1 may be determined by the PDSCH to HARQ feedback timing indicator field in the scheduling DCI, which may be mapped to a value of parameter K1 provided by a configured parameter (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 for DCI format 1_2), which may have a value in the range of zero to fifteen. In addition, in the PUSCH default TDRA table, the value of parameter K2 may be j, j+1, j+2, or j+3, where j is 1 for a subcarrier spacing of 15 kilohertz (kHz); j is 1 for a subcarrier spacing of 30 kHz; j is 2 for a subcarrier spacing of 60 kHz; or j is 3 for a subcarrier spacing of 120 kHz.

[0072] In some aspects, a HARQ ACK codebook may be used to provide ACK / NACK feedback corresponding to multiple downlink time slots (e.g., multiple PDSCHs), and thus the HARQ ACK codebook may be based at least in part on multiple K1 values, each K1 value being associated with a corresponding downlink time slot. Figure 5 Various aspects of the HARQ ACK codebook are described in more detail.

[0073] As indicated above, FIG. 4A to FIG. 4B are provided as examples. Other examples can be found in the FIG. 4A to FIG. 4B Different than described.

[0074] Figure 5 is a diagram illustrating an example 500 of a HARQ ACK codebook according to the present disclosure.

[0075] In some instances, UE 120 may provide HARQ ACK / NACK feedback for downlink transmission (e.g., PDSCH transmission) to a network entity (e.g., base station 110, CU 310, DU 330, RU 340, or similar network entity) using a HARQ ACK codebook sent in a PUSCH or PUCCH. The HARQ ACK codebook is a bit sequence constructed using ACK / NACK feedback of multiple downlink receptions (e.g., multiple PDSCH transmissions) during a configured time window. The HARQ ACK codebook may be a type 1 codebook or a type 2 codebook. The type 1 codebook is a fixed size codebook (e.g., having a fixed number of bits) indicated by the network entity via RRC signaling (e.g., a type 1 codebook may be referred to as a semi-static codebook). The total size of the type 1 codebook is equal to the sum of the downlink transmission opportunities (e.g., PDSCH opportunities) of a given time window. The sum of downlink transmission opportunities may take into account 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 particular PDSCH transmission, and / or multiple code block groups (CBGs) for each TB. The type 2 codebook has a dynamic size that varies according to resource allocation (e.g., the type 2 codebook may be referred to as a dynamic codebook).

[0076] In some cases, the HARQ ACK codebook may therefore provide HARQ ACK / NACK feedback corresponding to multiple downlink time slots (e.g., multiple PDSCH transmissions). More specifically, UE 120 may transmit HARQ ACK / NACK feedback in an uplink time slot (sometimes referred to as n U ) in the PUCCH or PUSCH to send the corresponding HARQ ACK / NACK information, such as Figure 5 In addition, in time slot n UThe HARQ ACK codebook sent in may contain feedback for a set of downlink time slots, where each time slot is sometimes referred to as n D,k The number of downlink time slots for which HARQ ACK / NACK feedback may be provided in the HARQ ACK codebook (sometimes referred to as N K ) may be equal to the number n of downlink time slots that overlap with uplink time slots U –K 1,k , where K 1,k Corresponding to the corresponding time slot n D,k The K1 offset associated with the downlink transmission in.

[0077] For example and Figure 5 As shown, in the uplink time slot n U The PUSCH or PUCCH used to send the HARQ ACK codebook is scheduled in the uplink time slot n U In the depicted example, this is slot 11. In this example, the HARQ ACK codebook includes HARQ ACK / NACK feedback associated with the following four downlink slots: n D,1 (e.g., time slot 8), n D,2 (e.g., time slot 7), n D,3 (e.g., time slot 6) and n D,4 (e.g., time slot 5). This is because each corresponding downlink time slot (e.g., n D,1 、n D,2 、n D,3 and n D,4 Each of the uplink time slots n U –K 1,k More specifically, in n D,1 The DCI for scheduling PDSCH transmission in time slot (e.g., time slot 8) may have indicated the corresponding K1 offset (e.g., K 1,1 ) is equal to 3 time slots, and thus for n D,1 The ACK / NACK feedback can be U (e.g., time slot 11) because n D,1 With uplink time slot n U –K 1,k (e.g., uplink time slot 11-3 = time slot 8) overlaps. Similarly, in time slot n D,2 (e.g., time slot 7), n D,3 (e.g., time slot 6) and n D,4 The DCI that schedules the PDSCH transmission in time slot (e.g., time slot 5) may have indicated the corresponding K1 offset (e.g., K 1,2 , K 1,3 and K 1,4) are equal to 4 time slots, 5 time slots and 6 time slots respectively, and thus for n D,2 、n D,3 and n D,4 The ACK / NACK feedback can be U (e.g., time slot 11) because n D,2 、n D,3 and n D,4 With uplink time slot n U –K 1,k (For example, for n D,2 , uplink time slot 11-4 = time slot 7; for n D,3 , uplink time slot 11-5 = time slot 6; and for n D,4 , uplink time slots 11-6 = time slot 5) overlap. Therefore, in this example, in n U The HARQ ACK codebook sent in (eg, transmission in PUSCH or PUCCH in slot 11) may be a bit sequence constructed using ACK / NACK feedback of downlink reception received in PDSCH in slots 5, 6, 7, and 8.

[0078] In some cases, UE 120 may receive a downlink transmission from a network entity associated with a non-terrestrial network (NTN) and, therefore, send a HARQ ACK codebook to the network entity. In such cases, the above HARQ ACK codebook timeline may not be sufficient to provide feedback due to, for example, large propagation delays associated with the NTN. Figure 6 Aspects of NTN are described in more detail.

[0079] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0080] Figure 6 is a diagram illustrating an example 600 of an NTN according to the present disclosure.

[0081] like Figure 6As shown, for an NTN, a base station 110 or other network entity (e.g., a CU 310, a DU 330, a RU 340, or a similar network entity) may communicate with a gateway 605, which may communicate with a satellite 610 via a feeder link 615. The satellite 610 may provide coverage to one or more UEs 120 in a cell 620 via a corresponding service link 625 (e.g., the satellite 610 may act as a gNB, etc., to provide coverage to the UEs 120 in the cell 620). In this regard, due to propagation delays between the base station 110 and the UE 120 via the gateway 605 and the satellite 610, communications between the base station 110 or other network components and the UE 120 may be associated with a large round trip time (RTT), such as 500 milliseconds (ms) or even greater RTT.

[0082] In such cases, combined Figure 5 The described HARQ ACK codebook timeline may not be sufficient for UE 120 to provide meaningful feedback to base station 110 or other network entities. More specifically, due to the one or more downlink time slots n D,k The propagation delay associated with the transmission, used for providing feedback uplink time slot n U (e.g., time slot 11) may occur before UE 120 receives these transmissions. Therefore, UE 120 may not be able to provide a complete HARQ ACK codebook, or may also signal NACKs in the HARQ ACK codebook for some downlink transmissions that are shorter than uplink time slot n. U 120. Therefore, UE 120 and / or one or more network entities may consume computing, power, network, and / or communication resources to detect and / or correct communication errors, including retransmitting a signal that eventually arrives safely at UE 120 but at uplink time slot n. U This can result in increased latency and reduced throughput, as well as an overall inefficient use of network resources.

[0083] Some techniques and apparatus described herein enable the use of a scheduling offset associated with a HARQ ACK codebook to be signaled. The scheduling offset may indicate an offset (in number of time slots) for sending a HARQ ACK codebook, such as a HARQ ACK codebook associated with one or more downlink communications received via the NTN. In some aspects, a UE (e.g., UE 120) may send the HARQ ACK codebook based at least in part on the scheduling offset, and in some aspects, may also send the HARQ ACK codebook based at least in part on a feedback channel offset value, such as a K1 offset value. In this regard, the HARQ ACK codebook may include a plurality of HARQ ACK information bits, wherein each HARQ ACK information bit indicates feedback corresponding to a downlink time slot that overlaps with another uplink time slot that is a plurality of time slots ahead of the HARQ ACK time slot, the plurality of time slots being equal to the sum of the scheduling offset and the feedback channel offset. As a result of the UE sending the HARQ ACK codebook based at least in part on the scheduling offset, the UE and / or one or more network entities may save computing resources, power resources, network resources, and / or communication resources that would otherwise be consumed by sending the HARQ ACK codebook without considering the scheduling offset. For example, based at least in part on the UE sending the HARQ ACK codebook based at least in part on the scheduling offset, the UE and one or more network entities may communicate at a reduced error rate, which may save computing resources, power resources, network resources, and / or communication resources that would otherwise be consumed by detecting and / or correcting communication errors. Therefore, aspects of the present disclosure may result in reduced latency and increased throughput, as well as overall efficient use of network resources.

[0084] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0085] Figure 7 7 is a diagram of an example 700 associated with a scheduling offset for a HARQ ACK codebook according to the present disclosure. Figure 7 As shown, UE 705 (e.g., UE 120) can communicate with network entity 710 (e.g., base station 110, CU 310, DU 330, RU 340, satellite 610, and / or similar network entities). In some aspects, UE 705 and network entity 710 can be a wireless network (such as a combination of Figure 1 The wireless network 100 and / or in combination Figure 6 UE 705 and network entity 710 may be part of the NTN described above. Figure 7 The operations shown are performed after a wireless connection has been established.

[0086] As indicated by reference numeral 715, the UE 705 may receive configuration information from the network entity 710. In some aspects, the UE 705 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 705 (e.g., known to the UE 705 and / or previously indicated by the network entity 710 or other network entity), and / or explicit configuration information for the UE 705 to configure the UE 705, etc.

[0087] In some aspects, the configuration information may configure the UE 705 to use the scheduling offset to send the HARQ ACK codebook. For example, the configuration information may indicate that the HARQ ACK information bits in the HARK ACK codebook should indicate the number of downlink time slots (e.g., n D,k ) ACK / NACK feedback, the downlink time slot is shorter than the uplink time slot (e.g., n U ) Feedback channel offset value in advance (K 1,k ) plus a scheduling offset, which is sometimes referred to as K sch_offset (In some aspects, it may be equal to 2 μ *K offset , where μ is the parameter set used for transmission, for example, μ represents the subcarrier spacing of 2 μ *15kHz, and K offset 715. In this regard, in communication indicated by reference numeral 715, UE 705 may receive from network entity 710 a scheduling offset associated with a HARQ ACK codebook (e.g., K sch_offset and / or K offset ) instructions. If the following combination Figure 8 As described in more detail, the scheduling offset may indicate an offset (in number of time slots) associated with the transmission of the HARQ ACK codebook relative to a downlink time slot containing a corresponding downlink data transmission (e.g., PDSCH). Additionally or alternatively, in some aspects, UE 120 may use an expression (e.g., 2 μ *K offset ) is used to identify an offset (in number of time slots) associated with the transmission of the HARQ ACK codebook relative to a downlink time slot containing a corresponding downlink data transmission (e.g., PDSCH), the expression being based at least in part on a scheduling offset parameter (e.g., K ) signaled by the network entity 710 to the UE 705. offset ) and a set of parameters for sending (e.g., μ), which will be described in more detail below.

[0088] In some aspects, the network entity 710 may utilize a cell-specific offset (sometimes referred to as K cell,offset ) or UE-specific offset (sometimes referred to as K UE,offset ) to configure the UE 705. The cell-specific offset may be applicable to a given cell (such as in conjunction with Figure 6 In this regard, the satellite 610 may configure each UE 120 within the cell 620 with a cell-specific offset. The UE-specific offset may be a scheduling offset that applies only to one or more UEs receiving the UE-specific offset and / or one or more UEs indicated as being associated with the UE-specific offset. For example, in Figure 6 In the arrangement shown, the satellite 610 may configure a first UE 120 of three UEs 120 with a first UE-specific offset, the satellite 610 may configure a second UE 120 of three UEs 120 with a second UE-specific offset, and / or the satellite 610 may configure a third UE 120 of three UEs 120 with a third UE-specific offset.

[0089] Thus, in some aspects, the scheduling offset indicated by the message shown at reference numeral 715 may be the cell-specific offset and / or UE-specific offset described above, or may also be a zero value. For example, the network entity 710 may indicate the cell-specific offset using a system information block (SIB) broadcast (such as a cellspecificKoffset information element broadcast via the SIB). Additionally or alternatively, the network entity 710 may 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 entity 710 may explicitly indicate the zero value through at least one of a MAC-CE message or an RRC message, or the network entity 710 may implicitly indicate the zero value through signaling that there is no offset value (e.g., signaling that there is no cell-specific offset and UE-specific offset).

[0090] The UE 705 may configure itself based at least in part on the configuration information. In some aspects, the UE 705 may 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., K sch_offset , K offset , K cell,offset and / or K UE,offset), the UE 705 may be configured to send the HARQ ACK codebook to the network entity 710 based at least in part on the scheduling offset. Additionally or alternatively, if the UE 705 is configured to use one of the cell-specific offset or the UE-specific offset, the UE 705 may be configured to send the HARQ ACK codebook to the network entity 710 based at least in part on the cell-specific offset or the UE-specific offset. In some aspects, the UE 705 may be configured with only the cell-specific offset, and thus the UE 705 may be configured to send the HARQ ACK codebook based at least in part on the cell-specific offset. In some other aspects, the UE 705 may be configured with only the UE-specific offset, and thus the UE 705 may be configured to send the HARQ ACK codebook based at least in part on the UE-specific offset. In some other aspects, the UE 705 may be configured with both the cell-specific offset and the UE-specific offset, and thus the UE 705 may be configured to send the HARQ ACK codebook based at least in part on the cell-specific offset or the UE-specific offset. For example, in some aspects, when the configuration information configures both a cell-specific offset and a UE-specific offset, the UE 705 may send the HARQ ACK codebook based at least in part on the UE-specific offset.

[0091] In addition, in some aspects, the UE 705 may also provide a feedback channel offset value (e.g., K1 offset or K2 offset) based at least in part on the feedback channel offset value. 1,k Value, such as combined Figure 4A and Figure 5 In such aspects and as indicated by reference numeral 720, the UE 705 may receive an indication of a feedback channel offset value associated with the HARQ ACK codebook from the network entity 710. For example, in some aspects, the UE 705 may receive an indication of the feedback channel offset value in a DCI that schedules downlink communications (e.g., PDSCH) associated with a downlink time slot corresponding to the feedback channel offset value. Figure 8 Various aspects of feeding back channel offset values ​​are described in greater detail.

[0092] As indicated by reference numeral 725, in some aspects, the UE 705 can schedule the sch_offset , K offset , K cell,offset and / or K UE,offset ) sends the HARQ ACK codebook to the network entity 710. In some aspects, the HARQ ACK codebook may be sent in one of the PUSCH or the PUCCH. In addition, when the UE 705 receives a feedback channel offset value (e.g., K1 offset or K 1,kIn some aspects of an indication of a scheduling offset (e.g., a scheduling offset and a feedback channel offset value), the sending may also be based at least in part on the feedback channel offset value (e.g., the UE 705 may send the HARQ ACK codebook to the network entity 710 based at least in part on the scheduling offset and the feedback channel offset value). More specifically, in some aspects, the sending may be based at least in part on the feedback channel offset value (e.g., the UE 705 may send the HARQ ACK codebook to the network entity 710 based at least in part on the scheduling offset and the feedback channel offset value). U ) to send the HARQ ACK codebook and feedback the channel offset value (e.g., K 1,k ) can be combined with the downlink time slot (e.g., n D,k ), and the HARQ ACK information bits associated with the HARQ ACK codebook may indicate feedback corresponding to the downlink time slot. In such aspects, the downlink time slot (e.g., n D,k ) may overlap with another uplink time slot that is shorter than the uplink time slot (eg, n U ) is advanced by a number of time slots equal to the scheduling offset (e.g., K sch_offset ) and the feedback channel offset (e.g., K 1,k That is, the HARQ ACK information bit in the HARQ ACK codebook may indicate the sum of the HARQ ACK information bits for the HARQ ACK codebook in time slot (n D,k ) is sent in the downlink communication, which is the same as the time slot located at n U –(K sch_offset +K 1,k )(Or, in other words, n U -K sch_offset -K 1,k and / or U –2 μ ×K offset –K 1,k ) at an uplink time slot overlapped. In some aspects, the UE 705 may send the HARQ ACK codebook based at least in part on an expression associated with the scheduling offset and the feedback channel offset value, and in some aspects, the expression may be equal to K sch_offset +K 1,k .

[0093] 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, a downlink time slot (e.g., n D,k ) may be associated with an opportunity for 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 time slot (e.g., n D,k) may be associated with a monitoring opportunity corresponding to a PDCCH associated with a DCI format that schedules PDSCH reception, or may be associated with a monitoring opportunity corresponding to a PDCCH associated with a DCI format that does not schedule PDSCH reception but is still associated with HARQ ACK information. In such aspects, the HARQ ACK codebook may be a type 2 codebook.

[0094] In some other aspects, the scheduling offset (e.g., K sch_offset ) may be based at least in part on a signaled value. For example, in some aspects, the network entity 710 may send a signaled offset value (sometimes referred to as K offset ), and the UE 705 may determine the scheduling offset based at least in part on the signaled offset value. In some aspects, the scheduling offset (e.g., K sch_offset ) may be based at least in part on a signaled offset value (e.g., K offset ) and the subcarrier spacing scaling factor. In addition, in some aspects, the subcarrier spacing scaling factor may be based at least in part on a parameter set for sending the HARQ ACK codebook (sometimes referred to as μ for ease of discussion). UL In some aspects, μ UL Corresponds to In other words, for an SCS of 15kHz, 30kHz, 60kHz, 120kHz, or 240kHz, μ UL and may be equal to 0, 1, 2, 3, or 4, respectively. In some aspects, the subcarrier spacing scaling factor is equal to 2 raised to the power of the parameter set for sending the HARQ ACK codebook (e.g., ). Therefore, in this regard, Combination Figure 8

[0013] Various aspects of sending a HARQ ACK codebook based at least in part on a scheduling offset are described in further detail.

[0095] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0096] Figure 8 is a diagram illustrating an example 800 of a scheduling offset for a HARQ ACK codebook according to the present disclosure.

[0097] exist Figure 8 In the aspect shown, a UE (eg, UE 705) may be configured to transmit data in an uplink time slot (eg, n U), which in the depicted example is time slot 11. More specifically, the UE may be configured to send the HARQ ACK codebook in the PUSCH and / or PUCCH associated with time slot 11. In this example, the UE has been configured with a scheduling offset (e.g., K sch_offset and / or K offset More specifically, the UE may have received a corresponding message from a network entity (eg, network entity 710) based at least in part on the scheduling offset (eg, K sch_offset and / or 2 μ *K offset ) to send an indication of the HARQ ACK codebook, in the depicted example, the scheduling offset is 4 time slots. As described above, in some aspects, the scheduling offset can take into account the propagation delay associated with NTN, etc. In addition, the scheduling offset can be a cell-specific offset or a UE-specific offset, such as in combination with Figure 7 The scheduling offset may also be based at least in part on a signaled offset value (eg, K offset ), such as combined Figure 7 For example, in some aspects, the scheduling offset may be equal to

[0098] In such aspects, for a time slot in the uplink (eg, n U ) carries uplink control information (UCI) of the HARQ ACK codebook, and the HARQ ACK information bit may correspond to a downlink time slot (e.g., n D,k ), the downlink time slot and time slot index are (For example, ) uplink time slots overlap, where K 1,k is for downlink time slots (e.g., n D,k ) of PDSCH to HARQ feedback timing parameters. Figure 8 In the example shown, the HARQ ACK information bit corresponds to a downlink time slot (eg, N k ), including n D,1 (e.g., time slot 4), n D,2 (e.g., time slot 3), n D,3 (e.g., time slot 2) and n D,4 (e.g., time slot 1). More specifically, n D,1 Can be offset from K1 of 3 time slots (e.g., K 1,1 ), and thus the UE can address n in the HARQ ACK codebook D,1 Provide HARQ ACK / NACK feedback, because n D,1 than n U 7 time slots ahead (e.g. ). Similarly, n D,2 、n D,3 and n D,4 The K1 offsets may be 4 slots, 5 slots, and 6 slots, respectively (e.g., K 1,2 , K 1,3 and K 1,4 ), and thus the UE can specify n in the HARQ ACK codebook D,2 、n D,3 and n D,4 Provide HARQ ACK / NACK feedback, because n D,2 、n D,3 and n D,4 Respectively than n U 8 slots, 9 slots, and 10 slots ahead. Thus, in the depicted example, the HARQ ACK codebook may include using n D,1 、n D,2 、n D,3 and n D,4 The bit sequence constructed by the ACK / NACK feedback.

[0099] More generally, in some aspects, a UE may be permitted to U In such aspect, if (where μ UL corresponds to the parameter set for uplink, and μ DL corresponding to the parameter set for the downlink), or if a PUCCH length parameter (sometimes referred to as subslotLengthForPUCCH) is provided for the HARQ ACK codebook, n D can be set to 0 (i.e., the index of a downlink slot that overlaps with an uplink slot), and if subslotLengthForPUCCH is provided for the HARQ ACK codebook, N k Can be set to the number of downlink timeslots that overlap with uplink timeslots (Otherwise N k Can be equal to ).

[0100] In other words, in some aspects, the UE may be permitted to In such aspect, if Or if a PUCCH length parameter (e.g., subslotLengthForPUCCH) is provided for the HARQ ACK codebook, n Dcan be set to 0 (i.e., the index of a downlink slot that overlaps with an uplink slot), and if subslotLengthForPUCCH is provided for the HARQ ACK codebook, N k can be set to the number of downlink time slots n that overlap with uplink time slots U –K 1,k (Otherwise N k Can be equal to ).

[0101] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Different than described.

[0102] Fig. 9 9 is a diagram illustrating an example process 900, performed, for example, by a UE, according to the present disclosure. Example process 900 is an example in which a UE (eg, UE 705) performs operations associated with scheduling offsets for a HARQ ACK codebook.

[0103] like Fig. 9 As shown, in some aspects, process 900 may include receiving an indication of a scheduling offset associated with a HARQ ACK codebook from a network entity (block 910). Fig.12 The depicted communication manager 1108 and / or receiving component 1202) may receive, from a network entity, an indication of a scheduling offset associated with a HARQ ACK codebook, as described above.

[0104] like Fig. 9 As further shown, in some aspects, process 900 may include sending the HARQ ACK codebook to the network entity based at least in part on the scheduling offset (block 920). Fig.11 The depicted communication manager 1108 and / or transmitting component 1104) may transmit a HARQ ACK codebook to a network entity based at least in part on a scheduling offset, as described above.

[0105] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0106] In a first aspect, process 900 includes receiving, from the network entity, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein sending the HARQ ACK codebook is also based at least in part on the feedback channel offset value.

[0107] In a second aspect, alone or in combination with the first aspect, the HARQ ACK codebook is transmitted in an uplink time slot, the feedback channel offset value is associated with a downlink time slot, and the HARQ ACK information bits associated with the HARQ ACK codebook indicate feedback corresponding to the downlink time slot.

[0108] In a third aspect, either alone or in combination with one or more of the first and second aspects, the downlink time slot overlaps with another uplink time slot, and the other uplink time slot is earlier than the uplink time slot by a plurality of time slots, the plurality of time slots being equal to the sum of the scheduling offset and the feedback channel offset value.

[0109] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the downlink time slot is associated with at least one of: an opportunity for candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator status update.

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

[0111] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the downlink time slot is associated with a monitoring opportunity corresponding to at least one of the following items: a PDCCH associated with a DCI format that schedules PDSCH reception, or a PDCCH associated with a DCI format that does not schedule PDSCH reception and is associated with HARQ ACK information.

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

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

[0114] In a ninth aspect, either alone or in combination with one or more of the first to 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.

[0115] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

[0116] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the subcarrier spacing scaling factor is based at least in part on 2 to the power of the parameter set used to send the HARQ ACK codebook.

[0117] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset values.

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

[0119] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 900 includes receiving a configuration from the network entity that configures only the cell-specific offset, wherein sending the HARQ ACK codebook is at least partially based on the cell-specific offset.

[0120] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 900 includes receiving a configuration for configuring the cell-specific offset and a configuration for configuring the UE-specific offset from the network entity, wherein sending the HARQ ACK codebook is at least partially based on the UE-specific offset.

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

[0122] In a seventeenth aspect, alone or in combination with one or more of the first to 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.

[0123] In an eighteenth aspect, either alone or in combination with one or more of the first to 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 signaling in which an offset value is not present.

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

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

[0126] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0127] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a network entity in accordance with the present disclosure. Example process 1000 is an example in which a network entity (eg, network entity 710) performs operations associated with scheduling offsets for a HARQ ACK codebook.

[0128] like Fig.10 As shown, in some aspects, process 1000 may include sending an indication of a scheduling offset associated with a HARQ ACK codebook to a UE (e.g., UE 705) (block 1010). For example, a network entity (e.g., using Fig.12 The depicted communication manager 1208 and / or transmitting component 1204) may send an indication of a scheduling offset associated with a HARQ ACK codebook to the UE, as described above.

[0129] like Fig.10 As further shown, in some aspects, process 1000 may include receiving the HARQ ACK codebook from the UE based at least in part on the scheduling offset (block 1020). Fig.12 The depicted communication manager 1208 and / or receiving component 1202) can receive a HARQ ACK codebook from the UE based at least in part on the scheduling offset, as described above.

[0130] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0131] In a first aspect, process 1000 includes sending an indication of a feedback channel offset value associated with the HARQ ACK codebook to the UE, wherein receiving the HARQ ACK codebook is also based at least in part on the feedback channel offset value.

[0132] In a second aspect, alone or in combination with the first aspect, the HARQ ACK codebook is sent in an uplink time slot, wherein the feedback channel offset value is associated with a downlink time slot, and wherein the HARQ ACK information bits associated with the HARQ ACK codebook indicate feedback corresponding to the downlink time slot.

[0133] In a third aspect, either alone or in combination with one or more of the first and second aspects, the downlink time slot overlaps with another uplink time slot, and the other uplink time slot is earlier than the uplink time slot by a plurality of time slots, the plurality of time slots being equal to the sum of the scheduling offset and the feedback channel offset value.

[0134] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the downlink time slot is associated with at least one of: an opportunity for candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator status update.

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

[0136] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the downlink time slot is associated with a monitoring opportunity corresponding to at least one of the following items: a PDCCH associated with a DCI format that schedules PDSCH reception, or a PDCCH associated with a DCI format that does not schedule PDSCH reception and is associated with HARQ ACK information.

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

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

[0139] In a ninth aspect, either alone or in combination with one or more of the first to 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.

[0140] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

[0141] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the subcarrier spacing scaling factor is based at least in part on 2 to the power of the parameter set used to send the HARQ ACK codebook.

[0142] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset values.

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

[0144] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 1000 includes sending a configuration to the UE that configures only the cell-specific offset, wherein receiving the HARQ ACK codebook is at least partially based on the cell-specific offset.

[0145] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 1000 includes sending a configuration for configuring the cell-specific offset and a configuration for configuring the UE-specific offset to the UE, wherein receiving the HARQ ACK codebook is at least partially based on the UE-specific offset.

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

[0147] In a seventeenth aspect, alone or in combination with one or more of the first to 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.

[0148] In an eighteenth aspect, either alone or in combination with one or more of the first to 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 signaling in which an offset value is not present.

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

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

[0151] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0152] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE (e.g., UE 705), or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 1108 (e.g., communication manager 140). Communication manager 1108 may include feedback component 1110, etc.

[0153] In some aspects, the apparatus 1100 may be configured to perform Figures 7 and 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0154] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE 120 .

[0155] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted UE 120. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0156] Receiving component 1102 and / or feedback component 1110 may receive an indication of a scheduling offset associated with the HARQ ACK codebook from a network entity, e.g., network entity 710. Sending component 1104 and / or feedback component 1110 may send the HARQ ACK codebook to the network entity based at least in part on the scheduling offset.

[0157] Receiving component 1102 and / or feedback component 1110 can receive an indication of a feedback channel offset value associated with the HARQ ACK codebook from a network entity, and sending the HARQ ACK codebook can also be based at least in part on the feedback channel offset value.

[0158] Receiving component 1102 and / or feedback component 1110 can receive a configuration from a network entity that configures only the cell-specific offset, and sending the HARQ ACK codebook can be based at least in part on the cell-specific offset.

[0159] Receiving component 1102 and / or feedback component 1110 can receive a configuration configuring a cell-specific offset and a configuration configuring a UE-specific offset from a network entity, and sending the HARQ ACK codebook can be based at least in part on the UE-specific offset.

[0160] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

[0161] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network entity (e.g., network entity 710), or a network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 1208 (e.g., communication manager 150). Communication manager 1208 may include configuration component 1210, etc.

[0162] In some aspects, the apparatus 1200 may be configured to perform Figures 7 and 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0163] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 The base station 110 is depicted as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0164] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted base station 110. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0165] Transmitting component 1204 and / or configuring component 1210 can transmit an indication of a scheduling offset associated with the HARQ ACK codebook to a UE (eg, UE 705). Receiving component 1202 can receive the HARQ ACK codebook from the UE based at least in part on the scheduling offset.

[0166] Transmitting component 1204 and / or configuring component 1210 can transmit an indication of a feedback channel offset value associated with the HARQ ACK codebook to the UE, and receiving the HARQ ACK codebook can also be based at least in part on the feedback channel offset value.

[0167] Transmitting component 1204 and / or configuring component 1210 can transmit a configuration to the UE that configures only the cell-specific offset, and the receive HARQ ACK codebook can be based at least in part on the cell-specific offset.

[0168] Transmitting component 1204 and / or configuring component 1210 can transmit a configuration configuring a cell-specific offset and a configuration configuring a UE-specific offset to the UE, and receiving the HARQ ACK codebook can be based at least in part on the UE-specific offset.

[0169] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12 Another component shown may be a collection of components that perform one or more functions.

[0170] The following provides an overview of some aspects of the disclosure:

[0171] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving an indication of a scheduling offset associated with a HARQ ACK codebook from a network entity; and sending the HARQ ACK codebook to the network entity based at least in part on the scheduling offset.

[0172] Aspect 2: According to the method of aspect 1, the method also includes: receiving an indication of a feedback channel offset value associated with the HARQ ACK codebook from the network entity, wherein sending the HARQ ACK codebook is also based at least in part on the feedback channel offset value.

[0173] Aspect 3: A method according to aspect 2, wherein the HARQ ACK codebook is sent in an uplink time slot, wherein the feedback channel offset value is associated with a downlink time slot, and wherein the HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink time slot.

[0174] Aspect 4: A method according to Aspect 3, wherein the downlink time slot overlaps with another uplink time slot, and wherein the other uplink time slot is a plurality of time slots ahead of the uplink time slot, and the plurality of time slots is equal to the sum of the scheduling offset and the feedback channel offset value.

[0175] Aspect 5: The method according to any one of aspects 3 to 4, wherein the downlink time slot is associated with at least one of the following items: an opportunity for candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator status update.

[0176] Aspect 6: The method according to aspect 5, wherein the HARQ ACK codebook is a type 1 codebook.

[0177] Aspect 7: A method according to any one of Aspects 3 to 4, wherein the downlink time slot is associated with a monitoring opportunity corresponding to at least one of the following items: a PDCCH associated with a DCI format that schedules PDSCH reception, or a PDCCH associated with a DCI format, wherein the DCI format does not schedule PDSCH reception and is associated with HARQ ACK information.

[0178] Aspect 8: The method according to aspect 7, wherein the HARQ ACK codebook is a type 2 codebook.

[0179] Aspect 9: The method according to any one of aspects 1 to 8, wherein the scheduling offset is based at least in part on a signaled offset value received from the network entity.

[0180] Aspect 10: The method according to aspect 9, wherein the scheduling offset is based at least in part on the product of the signaled offset value and a subcarrier spacing scaling factor.

[0181] Aspect 11: The method according to aspect 10, wherein the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

[0182] Aspect 12: The method according to aspect 11, wherein the subcarrier spacing scaling factor is based at least in part on 2 to the power of the parameter set used to send the HARQ ACK codebook.

[0183] Aspect 13: The method according to any one of aspects 1 to 12, wherein sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset value.

[0184] Aspect 14: The method according to any one of aspects 1 to 13, wherein the scheduling offset is one of a cell-specific offset, a UE-specific offset or a zero value.

[0185] Aspect 15: The method according to aspect 14 further comprises: receiving a configuration configuring only the cell-specific offset from the network entity, wherein sending the HARQ ACK codebook is at least partially based on the cell-specific offset.

[0186] Aspect 16: According to the method according to aspect 14, the method also includes: receiving a configuration for configuring the cell-specific offset and a configuration for configuring the UE-specific offset from the network entity, wherein sending the HARQ ACK codebook is at least partially based on the UE-specific offset.

[0187] Aspect 17: The method according to 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.

[0188] Aspect 18: The method according to 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.

[0189] Aspect 19: The method according to 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 signaling that an offset value is not present.

[0190] Aspect 20: The method according to any one of aspects 1 to 19, wherein the HARQ ACK codebook is sent via one of a physical uplink control channel or a physical uplink shared channel.

[0191] Aspect 21: The method according to any one of aspects 1 to 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.

[0192] Aspect 22: A method of wireless communication performed by a network entity, the method comprising: sending an indication of a scheduling offset associated with a HARQ ACK codebook to a UE; and receiving the HARQ ACK codebook from the UE based at least in part on the scheduling offset.

[0193] Aspect 23: The method according to aspect 22 further includes: sending an indication of a feedback channel offset value associated with the HARQ ACK codebook to the UE, wherein receiving the HARQ ACK codebook is also based at least in part on the feedback channel offset value.

[0194] Aspect 24: A method according to aspect 23, wherein the HARQ ACK codebook is sent in an uplink time slot, wherein the feedback channel offset value is associated with a downlink time slot, and wherein the HARQ ACK information bit associated with the HARQ ACK codebook indicates feedback corresponding to the downlink time slot.

[0195] Aspect 25: A method according to Aspect 24, wherein the downlink time slot overlaps with another uplink time slot, and wherein the other uplink time slot is a plurality of time slots ahead of the uplink time slot, and the plurality of time slots is equal to the sum of the scheduling offset and the feedback channel offset value.

[0196] Aspect 26: The method according to any one of aspects 24 to 25, wherein the downlink time slot is associated with at least one of the following items: an opportunity for candidate PDSCH reception, a semi-persistent PDSCH release, or a transmission configuration indicator status update.

[0197] Aspect 27: The method according to aspect 26, wherein the HARQ ACK codebook is a type 1 codebook.

[0198] Aspect 28: A method according to Aspect 24, wherein the downlink time slot is associated with a monitoring opportunity corresponding to at least one of the following items: a PDCCH associated with a DCI format that schedules PDSCH reception, or a PDCCH associated with a DCI format, wherein the DCI format does not schedule PDSCH reception and is associated with HARQ ACK information.

[0199] Aspect 29: The method according to aspect 28, wherein the HARQ ACK codebook is a type 2 codebook.

[0200] Aspect 30: The method according to any one of aspects 22 to 19, wherein the scheduling offset is based at least in part on a signaled offset value sent by the network entity.

[0201] Aspect 31: A method according to aspect 30, wherein the scheduling offset is based at least in part on the product of the signaled offset value and a subcarrier spacing scaling factor.

[0202] Aspect 32: The method according to aspect 31, wherein the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

[0203] Aspect 33: The method according to aspect 32, wherein the subcarrier spacing scaling factor is based at least in part on 2 to the power of the parameter set used to send the HARQ ACK codebook.

[0204] Aspect 34: The method according to any one of aspects 22 to 33, wherein sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset value.

[0205] Aspect 35: A method according to any one of aspects 22 to 34, wherein the scheduling offset is one of a cell-specific offset, a UE-specific offset or a zero value.

[0206] Aspect 36: The method according to aspect 35 further comprises: sending a configuration to the UE that configures only the cell-specific offset, wherein receiving the HARQ ACK codebook is at least partially based on the cell-specific offset.

[0207] Aspect 37: According to the method according to aspect 35, the method also includes: sending a configuration for configuring the cell-specific offset and a configuration for configuring the UE-specific offset to the UE, wherein receiving the HARQ ACK codebook is at least partially based on the UE-specific offset.

[0208] Aspect 38: The method according to 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.

[0209] Aspect 39: The method according to 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.

[0210] Aspect 40: The method according to 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 signaling that an offset value is not present.

[0211] Aspect 41: The method according to any one of aspects 22 to 40, wherein the HARQ ACK codebook is received via one of a physical uplink control channel or a physical uplink shared channel.

[0212] Aspect 42: The method according to any one of aspects 22 to 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.

[0213] Aspect 43: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 21.

[0214] Aspect 44: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 21.

[0215] Aspect 45: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 1 to 21.

[0216] 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 according to one or more of aspects 1 to 21.

[0217] Aspect 47: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of Aspects 1 to 21.

[0218] Aspect 48: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 22 to 42.

[0219] Aspect 49: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 22 to 42.

[0220] Aspect 50: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 22 to 42.

[0221] 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 according to one or more of aspects 22 to 42.

[0222] Aspect 52: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 22 to 42.

[0223] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0224] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0225] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0226] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0227] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from a network entity, an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook; and The HARQ ACK codebook is sent to the network entity based at least in part on the scheduling offset.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to: receive, from the network entity, an indication of a feedback channel offset value associated with the HARQ ACK codebook, wherein sending the HARQ ACK codebook is also based at least in part on the feedback channel offset value.

3. The apparatus of claim 2, wherein the HARQ ACK codebook is sent in an uplink time slot, wherein the feedback channel offset value is associated with a downlink time slot, and wherein the HARQ ACK information bits associated with the HARQ ACK codebook indicate feedback corresponding to the downlink time slot.

4. The apparatus according to claim 3, wherein the downlink time slot overlaps with another uplink time slot, and wherein the another uplink time slot is earlier than the uplink time slot by a plurality of time slots, the plurality of time slots being equal to the sum of the scheduling offset and the feedback channel offset value.

5. The apparatus of claim 3, wherein the downlink time slot is associated with at least one of: an opportunity for candidate physical downlink shared channel (PDSCH) reception, a semi-persistent PDSCH release, or a transmission configuration indicator status update. The apparatus of claim 5 , wherein the HARQ ACK codebook is a type 1 codebook.

7. An apparatus according to claim 3, wherein the downlink time slot is associated with a monitoring opportunity corresponding to at least one of the following items: a physical downlink control channel (PDCCH) associated with a downlink control information (DCI) format that schedules physical downlink shared channel (PDSCH) reception, or a PDCCH associated with a DCI format that does not schedule PDSCH reception and is associated with HARQ ACK information.

8. The apparatus of claim 7, wherein the HARQ ACK codebook is a type 2 codebook.

9. The apparatus of claim 1, wherein the scheduling offset is based at least in part on a signaled offset value received from the network entity.

10. The apparatus of claim 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.

11. The apparatus of claim 10, wherein the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

12. The apparatus of claim 11, wherein the subcarrier spacing scaling factor is based at least in part on the parameter set raised to a power of 2 for sending the HARQ ACK codebook.

13. The apparatus of claim 1, wherein sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset values.

14. The apparatus of claim 1, wherein the scheduling offset is one of a cell-specific offset, a UE-specific offset, or a zero value.

15. The apparatus of claim 14, wherein the one or more processors are further configured to: receive a configuration from the network entity that configures only the cell-specific offset, wherein sending the HARQ ACK codebook is based at least in part on the cell-specific offset.

16. The apparatus of claim 14, wherein the one or more processors are further configured to: receive a configuration to configure the cell-specific offset and a configuration to configure the UE-specific offset from the network entity, wherein sending the HARQ ACK codebook is based at least in part on the UE-specific offset.

17. The apparatus of claim 14, wherein the scheduling offset is the cell-specific offset, and wherein the cell-specific offset is indicated by a system information block message.

18. The apparatus of claim 14, wherein the scheduling offset is the UE-specific offset, and wherein the UE-specific offset is indicated by one of a medium access control (MAC) control element (MAC-CE) message or a radio resource control (RRC) message.

19. The apparatus of claim 14, wherein the scheduling offset is the zero value, and wherein the zero value is indicated by one of a medium access control (MAC) control element (MAC-CE) message, a radio resource control (RRC) message, or signaling in which an offset value is not present.

20. The apparatus of claim 1, wherein the HARQ ACK codebook is sent via one of a physical uplink control channel or a physical uplink shared channel.

21. The apparatus of claim 1, wherein the network entity is associated with a non-terrestrial network (NTN), and wherein the scheduling offset is associated with a propagation delay associated with the NTN.

22. An apparatus for wireless communication at a network entity for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: sending an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook to a user equipment (UE); and The HARQ ACK codebook is received from the UE based at least in part on the scheduling offset.

23. The apparatus of claim 22, wherein the scheduling offset is based at least in part on a signaled offset value sent by the network entity.

24. The apparatus of claim 23, wherein the scheduling offset is based at least in part on a product of the signaled offset value and a subcarrier spacing scaling factor.

25. The apparatus of claim 24, wherein the subcarrier spacing scaling factor is based at least in part on a parameter set used to send the HARQ ACK codebook.

26. The apparatus of claim 25, wherein the subcarrier spacing scaling factor is based at least in part on 2 to a power of the parameter set used to send the HARQ ACK codebook.

27. The apparatus of claim 22, wherein sending the HARQ ACK codebook is based at least in part on an expression associated with the scheduling offset and feedback channel offset values.

28. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from a network entity, an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook; as well as The HARQ ACK codebook is sent to the network entity based at least in part on the scheduling offset.

29. The method of claim 28, wherein the scheduling offset is based at least in part on a product of a signaled offset value received from the network entity and a subcarrier spacing scaling factor, wherein the subcarrier spacing scaling factor is based at least in part on a parameter set raised to a power of 2 for sending the HARQ ACK codebook.

30. A method of wireless communication performed by a network entity, the method comprising: sending an indication of a scheduling offset associated with a hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook to a user equipment (UE); as well as The HARQ ACK codebook is received from the UE based at least in part on the scheduling offset.