CN117730499A

CN117730499A - Transmission of hybrid automatic repeat request acknowledgement codebook

Info

Publication number: CN117730499A
Application number: CN202280052880.XA
Authority: CN
Inventors: 杨桅; 黄轶; S·侯赛尼; K·竹田; L·魏; M·霍什内维桑
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-08-05
Filing date: 2022-07-29
Publication date: 2024-03-19

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) may receive one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indicator Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook. The UE may transmit a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs. Many other aspects are described.

Description

Transmission of hybrid automatic repeat request acknowledgement codebook

Cross Reference to Related Applications

This patent application claims U.S. provisional patent application No. 63/203,977, entitled "TRANSMISSION OF A HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGMENT CODEBOOK", filed 8.5 a 2021, and U.S. non-provisional patent application No. 17/815,787, entitled "TRANSMISSION OF A HYBRID AUTOMATIC REPEAT REQUEST ACKNOWLEDGEMENT CODEBOOK", filed 28 a 2022, which are expressly incorporated herein by reference.

Technical Field

Aspects of the present disclosure relate generally to techniques and apparatuses for wireless communication and for transmitting hybrid automatic repeat request acknowledgement codebooks.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, 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 (3 GPP).

A wireless network may include one or more network nodes that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the network node through downlink and uplink communications. "downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node.

The multiple access techniques described above have been employed in various telecommunications standards to provide a common protocol that enables different UEs to communicate at a municipal, national, regional, and/or global level. A New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3 GPP. NR aims to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), using CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), to integrate with other open standards, and to support beamforming, multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation. With the increasing demand for mobile broadband access, further improvements in LTE, NR and other radio access technologies remain useful.

Disclosure of Invention

Some aspects described herein relate to a wireless communication method performed by a User Equipment (UE). The method may include: one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indicator Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook is received. The method may include transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to a wireless communication method performed by a network node. The method may include: one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook is transmitted. The method may include receiving a HARQ-ACK codebook, the HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Some aspects described herein relate to a UE for wireless communication. The user device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook is received. The one or more processors may be configured to: the method further includes transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook is transmitted. The one or more processors may be configured to: a HARQ-ACK codebook is received, the HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook is received. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: the method further includes transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for a network node to wirelessly communicate. The set of instructions, when executed by one or more processors of the network node, may cause the network node to: one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook is transmitted. The set of instructions, when executed by one or more processors of the network node, may cause the network node to: a HARQ-ACK codebook is received, the HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving one or more of an indication of a set of timing offset values associated with a HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook. The apparatus may include means for transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting one or more of an indication of a set of timing offset values associated with a HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook. The apparatus may include means for receiving a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user device, base station, network node, wireless communication device, and/or processing system substantially as described herein with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures to achieve the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and method of operation, together with the associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.

Although aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that the aspects may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented by integrated chip embodiments or other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial devices, retail/procurement devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-chip-level components, device-level components, and/or system-level components. The apparatus incorporating the described aspects and features may include additional components and features for achieving and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or accumulators) for analog and digital purposes. It is intended that the aspects described herein may be practiced in a variety of different size, shape, and configuration devices, components, systems, distributed arrangements, and/or end user devices.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to some aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example of a network node in communication with a User Equipment (UE) in a wireless network according to the present disclosure.

Fig. 3 is a diagram illustrating an example of timing offset values according to the present disclosure.

Fig. 4 is a diagram illustrating an example of start and length values for candidate data channels according to the present disclosure.

Fig. 5 is a diagram illustrating an example associated with transmission of a hybrid automatic repeat request acknowledgement codebook in accordance with the present disclosure.

Fig. 6 and 7 are diagrams illustrating example processes associated with transmission of a hybrid automatic repeat request acknowledgement codebook according to this disclosure.

Fig. 8 and 9 are diagrams of example apparatuses for wireless communication according to the present disclosure.

Detailed Description

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Furthermore, the scope of the present disclosure is intended to cover an apparatus or method that is practiced with other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

Several aspects of the telecommunications system will now be described 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 upon the particular application and design constraints imposed on the overall system.

Although aspects are described using terms associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as BS110a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Network node 110 is an entity in communication with UE 120. The network node 110 (sometimes referred to as a BS) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or Transmission and Reception Points (TRP). Each network node 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a network node 110 and/or a network node subsystem serving the coverage area, depending on the context in which the term is used.

The network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow limited access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell may be referred to as a macro base station. The network node 110 of the pico cell may be referred to as a pico base station. The network node 110 of the femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, BS110a may be a macro base station of macro cell 102a, BS110 b may be a pico base station of pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A network node may support one or more (e.g., three) cells.

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

The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., network node 110 or UE 120) and send data transmissions to a downstream station (e.g., UE 120 or network node 110). The relay station may be a UE 120 that may relay transmissions for other UEs 120. In the example shown in fig. 1, BS110d (e.g., a relay network node) may communicate with BS110a (e.g., a macro network node) and UE 120d to facilitate communications between BS110a and UE 120 d. The network node 110 relaying communications may be referred to as a relay station, a relay network node, a relay, etc.

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

The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network node 110 via a backhaul communication link. Network nodes 110 may communicate with each other directly or indirectly through wireless or wired backhaul communication links.

UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be fixed or mobile. UE 120 may include, for example, an access terminal, a mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (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, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or smartband)), 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 device, a global positioning system device, and/or any other suitable device configured to communicate over a wireless medium.

Some UEs 120 may be considered 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, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses components (e.g., processor components and/or memory components) of UE 120. 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., memory) can be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

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

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various categories, bands, channels, etc. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been determined to specify FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz) for the frequency range. It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "below 6GHz" frequency band in various documents and articles. FR2 sometimes suffers from similar naming problems, although it is often referred to (interchangeably) in documents and articles as the "millimeter wave" band, unlike the Extremely High Frequency (EHF) band (30 GHz-300 GHz), which is defined by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have determined the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 features and/or FR2 features and may therefore effectively extend the features of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend the operation of 5G NR above 52.6 GHz. For example, three higher operating bands have been determined to be frequency ranges specifying FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands belongs to the EHF frequency band.

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

Deployment of a communication system, such as a 5G New Radio (NR) system, may be arranged in a variety of ways with various components or parts. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, radio Access Network (RAN) nodes, core network nodes, network elements, base stations, or network devices may be implemented in an aggregated or non-aggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR Base Station (BS), 5G NB, gndeb (gNB), access Point (AP), transmission Reception Point (TRP), or cell) or one or more units (or one or more components) performing the functions of a base station may be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or as a non-aggregated base station. A "network entity" or "network node" may refer to a non-aggregated base station, or one or more units of a non-aggregated base station (e.g., one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). The non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units (e.g., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs)).

The operation of the base station type or network design may take into account the aggregate nature of the base station functions. For example, non-aggregated base stations may be used in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN (e.g., network configuration sponsored by the O-RAN alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate extension of a communication system by separating base station functionality into one or more units that may be deployed separately. The non-aggregated base station may include functionality implemented across two or more units at multiple physical locations, as well as functionality virtually implemented for at least one unit, which may enable flexibility in network design. The respective units of the non-aggregated base station may be configured for wired or wireless communication with at least one other unit of the non-aggregated base station.

In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request (HARQ) -Acknowledgement (ACK) (HARQ-ACK) codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook; and transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, network node 110 may include a communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook; and receiving a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

As described above, fig. 1 is provided as an example. Other examples may differ from that described with respect to fig. 1.

Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100 according to the present disclosure. Network node 110 may be equipped with a set of antennas 234a through 234T, e.g., T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, e.g., R antennas (r.gtoreq.1).

At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning 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)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if 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), as indicated by modems 232a through 232T. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232T may transmit a set of downlink signals (e.g., T downlink signals) through a corresponding set of antennas 234 (e.g., T antennas), such as antennas 234a through 234T.

At UE 120, a set of antennas 252 (shown as antennas 252a through 252R) may receive downlink signals from network node 110 and/or other network nodes 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 through 254R. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal using a corresponding demodulator component to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to a 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, etc. In some examples, one or more components of UE 120 may be included in housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may comprise, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 through a communication unit 294.

The one or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in 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. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmit and/or receive components, such as one or more components of fig. 2.

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ and/or CQI). Transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110, if applicable. For example, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., with reference to fig. 5-9).

At network node 110, uplink signals from UE 120 and/or other UEs may be received by antennas 234, processed by modems 232 (e.g., the demodulator components of modems 232, shown as DEMODs), detected (if applicable) by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The network node 110 may comprise a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 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 perform aspects of any of the methods described herein (e.g., with reference to fig. 5-9).

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component of fig. 2 may perform one or more techniques associated with transmission of the hybrid automatic repeat request acknowledgement codebook, as described in more detail elsewhere herein. For example, controller/processor 240 of network node 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, and/or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 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, the one or more instructions, when executed by one or more processors of network node 110 and/or UE 120 (e.g., directly or after compiling, converting, and/or interpreting), may cause the one or more processors, UE 120, and/or network node 110 to perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, and/or other processes described herein. In some examples, executing the instructions may include executing the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions.

In some aspects, the UE includes means for receiving one or more of an indication of a set of timing offset values associated with a HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook; and/or means for transmitting a HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs. The means for the UE to perform the operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, the network node includes means for one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook; and/or means for receiving a HARQ-ACK codebook based at least in part on one or more of different values of a set of timing offset values or different values of the set of SLIVs. The means for the network node to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Although the blocks in fig. 2 are shown as distinct components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by or under the control of controller/processor 280.

As described above, fig. 2 is provided as an example. Other examples may differ from that described with respect to fig. 2.

Fig. 3 is a diagram illustrating an example 300 of timing offset values according to the present disclosure. As shown in fig. 3, the network node may communicate with the UE via one or more Physical Downlink Shared Channel (PDSCH) communications and/or HARQ-ACK reports (e.g., via Physical Uplink Control Channel (PUCCH) communications). In some aspects, the network node and the UE may be part of a wireless network. The UE and the network node may have established a wireless connection prior to the operation shown in fig. 3.

As shown in fig. 3, a network node may transmit and a UE may receive PDSCH communication 305 with a timing offset value (K1 value) of 4. The timing offset value indicates the number of slots until the UE is to send HARQ-ACKs for PDSCH communication 305. For example, the UE receives PDSCH communication 305 during time slot n-2 and time offset value 4 indicates that the UE is scheduled to transmit HARQ-ACKs during time slot n+2.

The network node may transmit and the UE may receive PDSCH communication 310 with a timing offset value (K1 value) of 3. Based at least in part on the UE receiving PDSCH communication 310 during time slot n-1, the UE is scheduled to transmit HARQ-ACKs during time slot n+2.

The network node may transmit and the UE may receive PDSCH communications 315 with a timing offset value (K1 value) of 2. Based at least in part on the reception of PDSCH communication 315 by the UE during time slot n, the UE is scheduled to transmit HARQ-ACKs during time slot n+2.

The UE may be configured to use a type 1 HARQ-ACK codebook (e.g., a HARQ-ACK codebook having a fixed size that is pre-configured and/or semi-statically configured) during time slot n+2. To generate a HARQ-ACK codebook for transmission as HARQ-ACK report 320, the UE determines a set of candidate data channels based at least in part on a set of timing offset values (e.g., slot timing value K1) associated with the active uplink bandwidth portion. If the UE is configured to monitor PDCCH for Downlink Control Information (DCI) format 1_0 on serving cell c and is not configured to monitor Physical Downlink Control Channel (PDCCH) for DCI format 1_1 or DCI format1_2 on serving cell c, the set of offset values includes, for example, {1,2,3,4,5,6,7,8}. If the UE is configured to monitor PDCCH for DCI format 1_1 for serving cell c and is not configured to monitor PDCCH for DCI format1_2, the set of timing offset values is indicated by a first parameter (e.g., dl-DataToUL-ACK). If the UE is configured to monitor PDCCH for DCI format1_2 for serving cell c and is not configured to monitor PDCCH for DCI format 1_1, the set of timing offset values is indicated by a second parameter (e.g., dl-DataToUL-ACK-fordciformat1_2). If the UE is configured to monitor PDCCH for DCI format 1_1 and DCI format1_2 for serving cell c, the set of timing offset values is provided by a union of the first and second parameters. The union of the first parameter and the second parameter may form a dataset having duplicate values.

As described above, fig. 3 is provided as an example. Other examples may differ from that described with respect to fig. 3.

Fig. 4 is a diagram illustrating an example 400 of start and length values of candidate data channels according to the present disclosure. As shown in fig. 4, the network node may communicate with the UE via one or more candidate data channels (e.g., PDSCH channels). In some aspects, the network node and the UE may be part of a wireless network. The UE and the network node may have established a wireless connection prior to the operation shown in fig. 4.

As shown in fig. 4, a UE may be configured with a set of candidate data channels 405 for a slot. Fig. 4 further shows the start and length values 410 of candidate data channels 405 during a time slot. For example, each candidate data channel 405 may be indicated by a Time Domain Resource Allocation (TDRA) having a start value associated with a symbol of a slot during which the associated candidate data channel 405 begins, and a length value indicating the number of symbols over which the associated candidate data channel 405 extends. As shown in fig. 4, a candidate data channel 405 having a start value of 2 and a length value of 12 extends in the time domain from symbol 2 to symbol 13 of the slot. The candidate data channel 405 with a start value of 3 and a length value of 11 extends in the time domain from symbol 3 to symbol 13 of the slot. The candidate data channel 405 with a start value of 2 and a length value of 10 extends in the time domain from symbol 2 to symbol 11 of the slot. The candidate data channel 405 with a start value of 3 and a length value of 7 extends in the time domain from symbol 3 to symbol 9 of the slot. The candidate data channel 405 with a start value of 3 and a length value of 4 extends in the time domain from symbol 3 to symbol 6 of the slot. A candidate data channel 405 with a start value 8 and a length value 2 extends in the time domain from symbol 8 to symbol 9 of the slot. A candidate data channel 405 having a start value of 8 and a length value of 6 extends in the time domain from symbol 8 to symbol 13 of the slot.

Within one time slot, the UE may identify all TDRA associated with the candidate data channel 405 for one cell. Based at least in part on the TDRA, the UE may determine a maximum number of non-overlapping candidate data channels 405 that may be scheduled within the slot and allocate a number of HARQ-ACK bits based at least in part on the maximum number of non-overlapping candidate data channels 405. For example, in fig. 4, based at least in part on candidate data channel 405 having a start value of 3 and a length value of 4, the candidate data channel 405 may be combined with candidate data channel 405 having a start value of 8 and a length value of 2 or candidate data channel 405 having a start value of 8 and a length value of 6, the maximum number of non-overlapping candidate data channels 405 being 2.

In some networks, the UE may be configured to determine the number of HARQ-ACK bits and map each candidate data channel 405 to HARQ-ACK bits. For a subset of candidate data channels 405 mapped to the same HARQ-ACK bits, at most one candidate data channel 405 may be used to schedule PDSCH.

The TDRA and/or the set of candidate data channels 405 may be determined based at least in part on an indication in one or more parameters (e.g., pdsch-timedomainalllocation list and/or pdsch-timedomainalllocation list dci-1-2-r16, etc.) or may be determined based at least in part on a configuration within the communication protocol.

As described herein, the set of timing offset values may include redundancy (e.g., repetition values) and/or the set of candidate data channels may include redundancy. In a first example, a parameter providing a timing offset value (e.g., dl-DataToUL-ACK or dl-DataToUL-ACK-fordcifamat1_2) indicates a non-distinct value (e.g., a set comprising {1,2,3,3,3,4,4 }). In a second example, a plurality of parameters providing timing offset values (e.g., dl-DataToUL-ACK and dl-DataToUL-ACK-fordcifamat1_2) are configured and contain shared values (e.g., a first subset of values {1,2,3} and a second set of values {2,3,4,5,6 }). In a second example, a union (e.g., direct union) of multiple parameters (e.g., radio Resource Control (RRC) parameters) will contain a repetition value, (e.g., a combined set of values {1,2,3,2,3,4,5,6 }). In a third example, an indication of a set of SLIV for a candidate data channel (e.g., pdsch-TimeDomainAlllocation List or pdsch-TimeDomainAlllocation ListDCI-1-2-r 16) contains an entry with a duplicate SLIV. For example, each entry of the TDRA set may include information about "slot offset K0, and/or start and length indicator SLIV". The two entries may have the same SLIV and different K0 values. In this case, the SLIV set (e.g., pdsch-TimeDomainAlllocation List or pdsch-TimeDomainAlllocation ListDCI-1-2-r 16) determined from the indication of the SLIV set may include repeated SLIV. In a fourth example, an indication of a set of SLIV for a candidate data channel (e.g., pdsch-TimeDomainAlllocation List or pdsch-TimeDomainAlllocation ListDCI-1-2-r 16) includes entries having the same SLIV. For example, the indication of a set of SLIV may indicate multiple SLIV for different time slots, which may result in duplicate values in the set of SLIV.

Based at least in part on having repeated timing offset values and/or repeated SLIV values, the associated HARQ-ACK codebook may have repeated bits (e.g., multiple bits mapped to the same candidate data channel with the same indication), which may unnecessarily consume communication, network, power, and/or computing resources to communicate repeated bits. Additionally or alternatively, the network node and the UE may be unsynchronized with respect to whether repeated bits are included, which may cause the network node to misinterpret the HARQ-ACK codebook. Based at least in part on the network node misunderstanding the HARQ-ACK codebook, the network node may retransmit communications that are misinterpreted as not being received by the UE, or the network node may be unable to retransmit communications that are misinterpreted as being received by the UE. The network node and/or UE may consume communication, network, power, and/or computing resources to detect and/or correct these communication errors.

In some aspects described herein, a UE may receive an indication of a set of timing offset values associated with a HARQ-ACK codebook and/or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook. The UE may generate (e.g., construct and/or determine) a HARQ-ACK codebook (e.g., a HARQ-ACK codebook of type 1) using a different set of (e.g., non-duplicate) timing offset values (e.g., according to parameters such as dl-DataToUL-ACK and/or dl-DataToUL-ACK-fordcifamat1_2) and/or using a different set of SLIV values for each of the respective slots determined from the { n-K1} set. For example, the UE may identify and/or remove duplicate timing offset values from the set of timing offset values, and/or the UE may identify and/or remove duplicate SLIV values from a union of row indices of TDRA tables of DCI formats that the UE is configured to monitor for PDCCHs associated with the serving cell. .

In some aspects, the network node may be configured to transmit parameters that do not include duplicate timing offset values (e.g., dl-DataToUL-ACK and/or dl-DataToUL-ACK-forkdata 1_2) and/or a SLIV value that indicates no duplicate SLIV value (e.g., using pdsch-timedomainaliation list or pdsch-timedomainaliation list dci-1-2-r 16).

In some aspects, the network node and the UE may communicate to synchronize whether the repeated SLIV values and/or repeated timing offset values should be removed to generate the HARQ-ACK codebook.

Based at least in part on removing the duplicate timing offset value and/or the duplicate SLIV value, the associated HARQ-ACK codebook may not have duplicate bits (e.g., multiple bits mapped to the same candidate data channel with the same indication), which may save communication, network, power, and/or computing resources. Additionally or alternatively, the network node and the UE may synchronize with respect to whether repeated bits are included, which may reduce the network node's misunderstanding of the HARQ-ACK codebook. Based at least in part on the network node properly interpreting the HARQ-ACK codebook, the network node may avoid retransmitting communications that might otherwise be misinterpreted as not being received by the UE and the network node may retransmit communications that might otherwise be misinterpreted as being received by the UE. The network node and/or UE may save communication, network, power, and/or computing resources that might otherwise have been consumed to detect and/or correct communication errors associated with misinterpretation of the HARQ-ACK codebook.

Fig. 5 is a diagram illustrating an example 500 associated with transmission of a HARQ-ACK codebook according to the present disclosure. As shown in fig. 5, a network node (e.g., network node 110) may communicate with a UE (e.g., UE 120). In some aspects, the network node and UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may have established a wireless connection prior to the operation shown in fig. 5.

As indicated by reference numeral 505, the network node may transmit and the UE may receive configuration information. In some aspects, the UE may receive the configuration information via one or more of RRC signaling, MAC CE, DCI, and/or the like. In some aspects, the configuration information may include an indication of one or more configuration parameters for the UE to select (e.g., known to the UE), and/or explicit configuration information for the UE to use to configure the UE, etc.

In some aspects, the configuration information may indicate that the UE is to send an indication of support for sending a HARQ-ACK codebook based at least in part on different values of the timing offset value and/or different values of the SLIV. In some aspects, the configuration information may indicate that the UE is to transmit a HARQ-ACK codebook based at least in part on different values of timing offset values and/or different values of SLIVs for communicating with the network node.

As indicated by reference numeral 510, the UE may configure the UE based at least in part on the configuration information. In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

As indicated by reference numeral 515, the UE may transmit and the network node may receive an indication of support for transmitting a HARQ-ACK codebook based at least in part on different values of the timing offset value and/or different values of the set of SLIVs. In some aspects, the UE may send the indication of support via RRC signaling (e.g., as part of an RRC connection procedure).

As indicated by reference numeral 520, the UE may receive and the network node may transmit an indication that the HARQ-ACK codebook will be based at least in part on different values of the set of timing offset values and/or different values of the set of SLIVs. In some aspects, the UE may receive the indication in RRC communication to be applied to one or more HARQ-ACK codebooks. For example, the indication may be associated with a duration, a number of HARQ-ACK codebook transmissions, a set of scheduling grants based on semi-persistent scheduling, and/or a bandwidth portion, etc. Additionally or alternatively, the UE may receive the indication via dynamic signaling such as resource grant (e.g., DCI).

As shown at reference numeral 525, the UE may receive and the network node may transmit an indication of the set of timing offset values and/or information associated with the SLIVs for the candidate data channels. For example, the UE may receive the indication and/or information through RRC signaling and/or through scheduling grants. In some aspects, the set of timing offset values and/or the set of SLIVs include repetition values (e.g., repetition and/or redundancy, etc.) that map to the same HARQ-ACK codebook. For example, the repetition value may be mapped to a HARQ-ACK indication associated with the same data channel communication (e.g., associated with the same candidate data channel).

In some aspects, the indication of the set of timing offset values may include one or more RRC-based parameters (e.g., dl-DataToUL-ACK and/or dl-DataToUL-ACK-format 1_2). The set of timing offset values may be based at least in part on a union of a first subset of timing offset values (e.g., associated with a first parameter of the one or more RRC-based parameters) and a second subset of timing offset values (e.g., associated with a second parameter of the one or more RRC-based parameters). In some aspects, the information associated with the SLIV set can include one or more RRC-based parameters (e.g., using pdsch-TimeDomainAlllocation List or pdsch-TimeDomainAlllocation ListDCI-1-2-r 16). The set of SLIVs may be based at least in part on a union of a third subset of SLIVs (e.g., associated with a third parameter of the one or more RRC-based parameters) and a fourth subset of SLIVs (e.g., associated with a fourth parameter of the one or more RRC-based parameters).

As indicated by reference numeral 530, the network node may transmit and the UE may attempt to receive one or more PDSCH communications over the candidate data channels. For example, the UE may monitor one or more candidate data channels in one or more time slots as indicated in the scheduling grant. The UE may attempt to decode the signal sampled from one or more candidate data channels and determine whether the decoding was successful.

As indicated by reference numeral 535, the UE can determine and/or generate a HARQ-ACK codebook based at least in part on different values of the set of timing offset values and/or different (e.g., non-repeated and/or non-redundant) values of SLIV. The UE may determine the HARQ-ACK codebook based at least in part on determining the size of the HARQ-ACK codebook. The size of the HARQ-ACK codebook may be based at least in part on different values of the set of timing offset values and/or different values of the set of SLIVs. The network node may similarly determine and/or generate a HARQ-ACK codebook (e.g., size, number of bits, and/or mapping to one or more PDSCH communications, etc.) intended for reception by the UE.

In some aspects, the UE may generate the HARQ-ACK codebook based at least in part on different values of the set of timing offset values and/or different values of the set of SLIVs. The different values of the set of timing offset values may include fewer values than the set of timing offset values and/or the different values of the set of SLIVs include fewer values than the set of SLIVs. In some aspects, the UE may generate the HARQ-ACK codebook based at least in part on generating different values of the set of timing offset values or values of different values of the set of SLIVs. The UE may generate a value of a different value of the set of timing offset values or a different value of the set of SLIVs based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

In some aspects, the UE may determine different values for the set of SLIVs from the set of TDRA parameters. In some aspects, the TDRA parameters in the TDRA parameter set include a slot parameter and a SLIV. The UE may determine that the first TDRA parameter includes a first slot parameter and a first SLIV and the second TDRA parameter includes a second slot parameter and a first SLIV. The UE may include only the first SLIV one time in the different values of the set of SLIVs.

As indicated by reference numeral 540, the UE may transmit and the network node may receive a HARQ codebook based at least in part on different values of the set of timing offset values and/or different values of SLIV. The HARQ-ACK codebook may have a size and/or format based at least in part on different values of the set of timing offset values and/or different values of the set of SLIVs.

As indicated by reference numeral 545, the network node may decode the HARQ-ACK codebook based at least in part on the expected size, the expected number of bits, and/or the mapping to one or more PDSCH communications. In some aspects, the network node may decode the HARQ-ACK codebook based at least in part on: the transmitting user equipment of the HARQ-ACK codebook is generated based at least in part on the different values of the set of timing offset values and/or the different values of the set of SLIVs. For example, the network node may determine a HARQ-ACK codebook (e.g., an expected HARQ-ACK codebook) having a size and/or format (e.g., including a mapping to PDSCH communications) based at least in part on different values of the set of timing offset values and/or different values of the set of SLIVs.

As described above, fig. 5 is provided as an example. Other examples may differ from that described with respect to fig. 5.

Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example of a UE (e.g., UE 120) performing operations associated with transmission of a HARQ-ACK codebook.

As shown in fig. 6, in some aspects, process 600 may include receiving one or more of an indication of a set of timing offset values associated with a HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook (block 610). For example, the UE (e.g., using the communication manager 140 and/or the receiving component 802 depicted in fig. 8) may receive one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook, as described above.

As further shown in fig. 6, in some aspects, process 600 may include transmitting a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs (block 620). For example, the UE (e.g., using the communication manager 140 and/or the transmission component 804 depicted in fig. 8) may transmit a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs, as described above.

Process 600 may include additional aspects, such as any individual aspect or any combination of aspects described below and/or related to one or more other processes described elsewhere herein.

In a first aspect, process 600 includes generating a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

In a second aspect, alone or in combination with the first aspect, the different values of the set of timing offset values comprise fewer values than the set of timing offset values, or wherein the different values of the set of SLIVs comprise fewer values than the set of SLIVs.

In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes receiving an indication that a HARQ-ACK codebook is to be based at least in part on one or more of a different value of the set of timing offset values or a different value of the set of SLIVs.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or wherein the set of SLIVs is based at least in part on a union of a first subset of SLIVs associated with the information and a second subset of SLIVs associated with the information.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a first subset of timing offset values is indicated by a first RRC parameter and a second subset of timing offset values is indicated by a second RRC parameter, or wherein information associated with the first subset of SLIVs is indicated by a third RRC parameter and a second subset associated with information associated with the second subset of SLIVs is indicated by a fourth RRC parameter.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the process 600 includes determining a HARQ-ACK codebook.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, determining the HARQ-ACK codebook comprises determining a size of the HARQ-ACK codebook.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the size of the HARQ-ACK codebook is based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 600 includes generating a value of a different value of the set of timing offset values or a different value of the set of SLIVs based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 600 includes determining different values for the set of SLIVs from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation parameters include a slot parameter and a SLIV.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the process 600 includes determining that the first time domain resource allocation parameter includes a first time slot parameter and a first SLIV, determining that the second time domain resource allocation parameter includes a second time slot parameter and a first SLIV, and including only the first SLIV once in different values of the set of SLIVs.

While fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a network node, in accordance with the present disclosure. Example process 700 is an example of a network node (e.g., network node 110) performing operations associated with transmission of a HARQ-ACK codebook.

As shown in fig. 7, in some aspects, process 700 may include transmitting one or more of an indication of a set of timing offset values associated with a HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook (block 710). For example, the network node (e.g., using the communication manager 150 and/or the transmission component 904 depicted in fig. 9) may send one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook, as described above.

As further shown in fig. 7, in some aspects, process 700 may include receiving a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs (block 720). For example, the network node (e.g., using the communication manager 150 and/or the receiving component 902 depicted in fig. 9) may receive a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs, as described above.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or related to one or more other processes described elsewhere herein.

In a first aspect, receiving a HARQ-ACK codebook comprises: decoding the HARQ-ACK codebook based at least in part on: the transmitting user equipment generates a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

In a third aspect, alone or in combination with one or more of the first and second aspects, process 700 includes transmitting an indication that the HARQ-ACK codebook is to be based at least in part on one or more of a different value of the set of timing offset values or a different value of the set of SLIVs.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or wherein the set of SLIV is based at least in part on a union of a first subset of SLIV associated with the information and a second subset of SLIV associated with the information.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a first subset of timing offset values is indicated by a first RRC parameter and a second subset of timing offset values is indicated by a second RRC parameter, or wherein information associated with the first subset of SLIVs is indicated by a third RRC parameter and a second subset associated with information associated with the second subset of the second SLIVs is indicated by a fourth RRC parameter.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the process 700 includes determining a HARQ-ACK codebook.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the size of the HARQ-ACK codebook is based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 700 comprises: the different values of the set of timing offset values comprise the same number of values as the set of timing offset values, or wherein the different values of the set of SLIV contain the same number of values as the set of SLIV.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 700 includes: generating a value of a different value of the set of timing offset values or a different value of the set of SLIVs is based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the process 700 comprises: different values of the set of SLIV are determined from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation parameters include a slot parameter and SLIV.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the process 700 comprises: the first time domain resource allocation parameter is determined to include a first time slot parameter and a first SLIV, the second time domain resource allocation parameter is determined to include a second time slot parameter and a first SLIV, and the first SLIV is included only once in different values of the SLIV set.

While fig. 7 shows example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 7. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

Fig. 8 is a diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 800 can communicate with another apparatus 806 (e.g., a UE, a network node, or another wireless communication device) using a receiving component 802 and a transmitting component 804. As further shown, the apparatus 800 can include a communication manager 808 (e.g., the communication manager 140).

In some aspects, device 800 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, device 800 may be configured to perform one or more processes described herein, such as process 600 of fig. 6. In some aspects, the apparatus 800 and/or one or more components shown in fig. 8 may include one or more components of the UE described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 8 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 802 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 806. The receiving component 802 can provide the received communication to one or more other components of the apparatus 800. In some aspects, the receiving component 802 can perform signal processing (e.g., filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 806. In some aspects, the receiving component 802 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for the UE described in connection with fig. 2.

The transmission component 804 can transmit communications such as reference signals, control information, data communications, or a combination thereof to the device 806. In some aspects, one or more other components of the apparatus 806 may generate a communication and may provide the generated communication to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 can perform signal processing (e.g., filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, etc.) on the generated communication and can transmit the processed signal to the device 806. In some aspects, the transmission component 804 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the UE described in connection with fig. 2. In some aspects, the transmission component 804 may be collocated with the reception component 802 in a transceiver.

The receiving component 802 can receive one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook. The transmission component 804 can transmit a HARQ-ACK codebook based at least in part on one or more of different values of a set of timing offset values or different values of a set of SLIVs.

The communication manager 808 can generate a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

The receiving component 802 can receive an indication that the HARQ-ACK codebook is to be based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

The communication manager 808 may determine the HARQ-ACK codebook.

The communication manager 808 can generate a value of a different value of the set of timing offset values or a different value of the set of SLIVs based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

The communication manager 808 may determine different values for the set of SLIVs from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation parameters include a slot parameter and a SLIV.

The communication manager 808 may determine that the first time domain resource allocation parameter includes a first time slot parameter and a first SLIV.

The communication manager 808 may determine that the second time domain resource allocation parameter includes a second slot parameter and a first SLIV.

The communication manager 808 may include only the first SLIV in a different value of the set of SLIVs.

The number and arrangement of components shown in fig. 8 are provided as examples. In fact, there may be additional components, fewer components, different components, or components in a different arrangement than the components shown in FIG. 8. Further, two or more components shown in fig. 8 may be implemented within a single component, or a single component shown in fig. 8 may be implemented as multiple distributed components. Additionally or alternatively, the set of component(s) shown in fig. 8 may perform one or more functions described as being performed by another set of components shown in fig. 8.

Fig. 9 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a network node or the network node may comprise the apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (e.g., a UE, a network node, or another wireless communication device) using a receiving component 902 and a transmitting component 904. As further illustrated, apparatus 900 can include a communication manager 908 (e.g., communication manager 150).

In some aspects, device 900 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as process 700 of fig. 7, or a combination thereof. In some aspects, the apparatus 900 and/or one or more components shown in fig. 9 may include one or more components of the network node described in connection with fig. 2. Additionally or alternatively, one or more components shown in fig. 9 may be implemented within one or more components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 902 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the apparatus 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can perform signal processing (e.g., filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 906. In some aspects, the receiving component 902 can include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a network node described in connection with fig. 2.

The transmission component 904 can transmit communications such as reference signals, control information, data communications, or a combination thereof to the device 906. In some aspects, one or more other components of the apparatus 906 may generate a communication and may provide the generated communication to the transmission component 904 for transmission to the apparatus 906. In some aspects, the transmission component 904 can perform signal processing (e.g., filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, etc.) on the generated communication and can transmit the processed signal to the device 906. In some aspects, the transmission component 904 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the network node described in connection with fig. 2. In some aspects, the transmission component 904 can be co-located with the reception component 902 in the transceiver.

The transmission component 904 can transmit one or more of an indication of a set of timing offset values associated with the HARQ-ACK codebook or information associated with a set of SLIVs for candidate data channels associated with the HARQ-ACK codebook. The receiving component 902 can receive a HARQ-ACK codebook based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

The transmission component 904 can transmit an indication that the HARQ-ACK codebook is to be based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

The communication manager 908 may determine a HARQ-ACK codebook.

The communication manager 908 may generate a value for a different value of the set of timing offset values or a different value of the set of SLIVs based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

The communication manager 908 may determine different values for the set of SLIVs from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation parameters include a slot parameter and a SLIV.

The communication manager 908 may determine that the first time domain resource allocation parameters include a first time slot parameter and a first SLIV.

The communication manager 908 may determine that the second time domain resource allocation parameter includes a second slot parameter and a first SLIV.

The communication manager 908 may include only the first SLIV in the different values of the set of SLIVs.

The number and arrangement of components shown in fig. 9 are provided as examples. In fact, there may be additional components, fewer components, different components, or components in a different arrangement than the components shown in FIG. 9. Further, two or more components shown in fig. 9 may be implemented within a single component, or a single component shown in fig. 9 may be implemented as multiple distributed components. Additionally or alternatively, the set of component(s) shown in fig. 9 may perform one or more functions described as being performed by another set of components shown in fig. 9.

The following provides an overview of some aspects of the disclosure:

aspect 1: a wireless communication method performed by a User Equipment (UE), comprising: receiving one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indication Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook; and transmitting a HARQ-ACK codebook, the HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Aspect 2: the method of aspect 1, further comprising generating the HARQ-ACK codebook based at least in part on one or more of: different values of the set of timing offset values, or different values of the set of SLIVs.

Aspect 3: the method of any of aspects 1-2, wherein the different values of the set of timing offset values comprise fewer values than the set of timing offset values, or wherein the different values of the set of SLIVs comprise fewer values than the set of SLIVs.

Aspect 4: the method of any one of aspects 1-3, further comprising: an indication is received that the HARQ-ACK codebook is to be based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Aspect 5: the method of any of aspects 1-4, wherein the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or wherein the set of SLIVs is based at least in part on a union of a first subset of SLIVs associated with information and a second subset of SLIVs associated with information.

Aspect 6: the method of aspect 5, wherein a first subset of the timing offset values are indicated by a first Radio Resource Control (RRC) parameter and a second subset of the timing offset values are indicated by a second RRC parameter, or wherein information associated with the first subset of SLIVs is indicated by a third RRC parameter and a second subset associated with information associated with the second subset of SLIVs is indicated by a fourth RRC parameter.

Aspect 7: the method of any of aspects 1-6, further comprising determining a HARQ-ACK codebook.

Aspect 8: the method of aspect 7, wherein determining the HARQ-ACK codebook comprises determining a size of the HARQ-ACK codebook.

Aspect 9: the method of aspect 8, wherein a size of the HARQ-ACK codebook is based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Aspect 10: the method of any one of aspects 1-9, further comprising: a value of a different value of the set of timing offset values or a different value of the set of SLIVs is generated based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

Aspect 11: the method of any one of aspects 1-10, further comprising: different values of the set of SLIV are determined from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation include a slot parameter and SLIV.

Aspect 12: the method of aspect 11, further comprising: determining that the first time domain resource allocation parameter includes a first time slot parameter and a first SLIV; determining that the second time domain resource allocation parameter includes a second slot parameter and a first SLIV; and only the first SLIV is included in the different values of the set of SLIVs.

Aspect 13: a method of wireless communication performed by a network node, comprising: transmitting one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indication Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook; and receiving a HARQ-ACK codebook, the HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Aspect 14: the method of aspect 13, wherein receiving the HARQ-ACK codebook comprises: generating the HARQ-ACK codebook based at least in part on a transmitting user equipment decoding the HARQ-ACK codebook based at least in part on one or more of: different values of the set of timing offset values, or different values of the set of SLIVs.

Aspect 15: the method of any of aspects 13-14, wherein the different values of the set of timing offset values comprise fewer values than the set of timing offset values, or wherein the different values of the set of SLIVs comprise fewer values than the set of SLIVs.

Aspect 16: the method of any one of aspects 13-15, further comprising: an indication is sent that the HARQ-ACK codebook is to be based at least in part on one or more of the different values of the set of timing offset values or the different values of the set of SLIVs.

Aspect 17: the method of any of aspects 13-16, wherein the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or wherein the set of SLIVs is based at least in part on a union of a first subset of SLIVs associated with information and a second subset of SLIVs associated with information.

Aspect 18: the method of aspect 17, wherein a first subset of the timing offset values are indicated by a first Radio Resource Control (RRC) parameter and a second subset of the timing offset values are indicated by a second RRC parameter, or wherein information associated with the first subset of SLIVs is indicated by a third RRC parameter and a second subset associated with information associated with the second subset of SLIVs is indicated by a fourth RRC parameter.

Aspect 19: the method of any of aspects 13-18, further comprising determining a HARQ-ACK codebook.

Aspect 20: the method of aspect 19, wherein determining the HARQ-ACK codebook comprises determining a size of the HARQ-ACK codebook.

Aspect 21: the method of aspect 20, wherein a size of the HARQ-ACK codebook is based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

Aspect 22: the method of any of aspects 13-21, wherein, based at least in part on a configuration of the network node, one or more of: the different values of the set of timing offset values comprise the same number of values as the set of timing offset values, or wherein the different values of the set of SLIV comprise the same number of values as the set of SLIV.

Aspect 23: the method of any one of aspects 13-22, further comprising: a value of a different value of the set of timing offset values or a different value of the set of SLIVs is generated based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

Aspect 24: the method of any one of aspects 13-23, further comprising: different values of the set of SLIV are determined from a set of time domain resource allocation parameters, wherein the time domain resource allocation parameters in the set of time domain resource allocation parameters include a slot parameter and SLIV.

Aspect 25: the method of aspect 24, further comprising: determining that the first time domain resource allocation parameter includes a first time slot parameter and a first SLIV; determining that the second time domain resource allocation parameter includes a second slot parameter and a first SLIV; and comprises: only the first SLIV is included in the different values of the set of SLIVs.

Aspect 26: an apparatus for wireless communication at a device, 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 the method of one or more of aspects 1-25.

Aspect 27: an apparatus for wireless communication comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-25.

Aspect 28: an apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-25.

Aspect 29: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-25.

Aspect 30: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more aspects 1-25.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit these aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the aspects.

Further disclosure is contained in the appendix. The appendix is provided as an example only and should be considered as part of the specification. The definitions, illustrations, or other descriptions in the appendix are not intended to replace or cover the detailed description or similar information contained in the drawings. Furthermore, the definitions, illustrations, or other descriptions in the detailed description or drawings do not replace or cover similar information contained in the appendix. Furthermore, the appendix is not intended to limit the disclosure of possible aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. "software" should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures and/or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or other terminology. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It is apparent that the systems and/or methods described herein may be implemented in different forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of these aspects. Thus, the operations and behavior of the systems and/or methods were described without reference to the specific software code-as one of ordinary skill in the art would understand that software and hardware could be designed to implement the systems and/or methods based at least in part on the description herein.

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

Although specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim of the set of claims. As used herein, a phrase referring to "at least one" of a list of items refers to any combination of these items, including individual members. For example, "at least one of a, b, or c" is intended to encompass a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combinations with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c b+b, b+b+b, b+b+c, c+c and c+c+c, or any other order of a, b and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items associated with the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". If an item is intended to be described, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "having," "having," and the like are intended to be open-ended terms (e.g., the element "having" a and also B) that are not limiting to the elements they modify. Furthermore, unless explicitly stated otherwise, the phrase "based on" is intended to mean "based, at least in part, on". Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and may be used interchangeably with "and/or" unless otherwise specifically indicated (e.g., if used in combination with "or (other)" or "only one of …").

Claims

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

a memory; and

one or more processors coupled to the memory configured to:

receiving one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indicator Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook; and

the method further includes transmitting the HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

2. The UE of claim 1, wherein the one or more processors are further configured to: the HARQ-ACK codebook is generated based at least in part on one or more of:

different values of the set of timing offset values, or

Different values of the set of SLIV.

3. The UE of claim 1, wherein the different values of the set of timing offset values comprise fewer values than the set of timing offset values, or

Wherein the different values of the set of SLIV include fewer values than the set of SLIV.

4. The UE of claim 1, wherein the one or more processors are further configured to:

an indication is received that the HARQ-ACK codebook is to be based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

5. The UE of claim 1, wherein the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or

Wherein the set of SLIV is based at least in part on a union of a first subset of SLIV associated with the information and a second subset of SLIV associated with the information.

6. The UE of claim 5, wherein a first subset of the timing offset values are indicated by a first Radio Resource Control (RRC) parameter and a second subset of the timing offset values are indicated by a second RRC parameter, or

Wherein information associated with a first subset of the SLIV is indicated by a third RRC parameter and a second subset associated with information associated with a second subset of the SLIV is indicated by a fourth RRC parameter.

7. The UE of claim 5, wherein the first subset of timing offset values and the second subset of timing offset values do not contain duplicate timing offset values, or

Wherein the first subset of SLIV and the second subset of SLIV do not contain duplicate SLIV.

8. The UE of claim 1, wherein the one or more processors are further configured to determine the HARQ-ACK codebook.

9. The UE of claim 8, wherein the one or more processors to determine the HARQ-ACK codebook are configured to determine a size of the HARQ-ACK codebook.

10. The UE of claim 9, wherein a size of the HARQ-ACK codebook is based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

11. The UE of claim 1, wherein the one or more processors are further configured to:

a value of a different value of the set of timing offset values or a different value of the set of SLIVs is generated based at least in part on removing at least one value from the set of timing offset values or the set of SLIVs.

12. The UE of claim 1, wherein the one or more processors are further configured to:

determining different values of the set of SLIVs from a set of time domain resource allocation parameters,

wherein the time domain resource allocation parameters in the time domain resource allocation parameter set include a time slot parameter and a SLIV.

13. The UE of claim 12, wherein the one or more processors are further configured to:

determining that the first time domain resource allocation parameter includes a first time slot parameter and a first SLIV;

determining that a second time domain resource allocation parameter includes a second slot parameter and the first SLIV; and

the first SLIV is included only once in the different values of the set of SLIV.

14. A network node for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory configured to:

transmitting one or more of an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook or information associated with a set of Start and Length Indicator Values (SLIVs) for candidate data channels associated with the HARQ-ACK codebook; and

the method further includes receiving the HARQ-ACK codebook, the HARQ-ACK codebook based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

15. The network node of claim 14, wherein the one or more processors for receiving the HARQ-ACK codebook are configured to:

The HARQ-ACK codebook is decoded based at least in part on the transmitting user equipment generating the HARQ-ACK codebook based at least in part on one or more of:

different values of the timing offset value, or

Different values of said SLIV.

16. The network node of claim 14, wherein the different values of the set of timing offset values comprise fewer values than the set of timing offset values, or

17. The network node of claim 14, wherein the one or more processors are further configured to:

sending an indication that the HARQ-ACK codebook is to be based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

18. The network node of claim 14, wherein the set of timing offset values is based at least in part on a union of a first subset of timing offset values and a second subset of timing offset values, or

19. The network node of claim 18, wherein a first subset of the timing offset values are indicated by a first Radio Resource Control (RRC) parameter and a second subset of the timing offset values are indicated by a second RRC parameter, or

20. The network node of claim 14, wherein the one or more processors are further configured to determine the HARQ-ACK codebook.

21. The network node of claim 20, wherein the one or more processors to determine the HARQ-ACK codebook are configured to determine a size of the HARQ-ACK codebook.

22. The network node of claim 21, wherein a size of the HARQ-ACK codebook is based at least in part on one or more of different values of the set of timing offset values or different values of the set of SLIVs.

23. The network node of claim 14, wherein one or more of the following is performed based at least in part on a configuration of the network node:

The different values of the set of timing offset values comprise the same number of values as the set of timing offset values, or

Wherein the different values of the set of SLIV include the same number of values as the set of SLIV.

24. The network node of claim 14, wherein the one or more processors are further configured to:

generating a value of a different value of the set of timing offset values or a different value of the set of SLIV based at least in part on removing at least one value from the set of timing offset values or the set of SLIV, or

25. The network node of claim 24, wherein the one or more processors are further configured to:

26. A wireless communication method performed by a User Equipment (UE), comprising:

27. The method of claim 26, further comprising:

28. The method of claim 26, further comprising:

29. A method of wireless communication performed by a network node, comprising:

30. The method of claim 29, further comprising: