TW202312701A - Transmission of a hybrid automatic repeat request acknowledgment codebook - Google Patents

Abstract

Various aspects of the present disclosure generally relate to wireless communication. 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 acknowledgment (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 the HARQ-ACK codebook, the HARQ-ACK codebook being based at least in part on one or more of distinct values of the set of timing offset values or distinct values of the set of SLIVs. Numerous other aspects are described.

Description

Hybrid Automatic Repeat Request Acknowledging Transmission of Encryption Book

The aspects of this case generally relate to wireless communication and technologies and devices for transmitting HARQ acknowledgment codebooks.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging and broadcasting. A typical wireless communication system may adopt a multiple access technology capable of supporting communication with multiple users by sharing available system resources (eg, 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, Access (OFDMA) system, Single Carrier Frequency Division Multiple Access (SC-FDMA) system, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile service standard promulgated by the Third Generation Partnership Project (3GPP).

A wireless network may include one or more network nodes supporting communication for a user equipment (UE) or multiple UEs. The UE can communicate with the network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from a network node to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a network node.

The multiple access techniques described above have been adopted in various telecommunication standards to provide a common protocol enabling different UEs to communicate at municipal, national, regional and/or global levels. New Radio (NR), which may be called 5G, is a set of enhancements to the LTE mobile service standard promulgated by 3GPP. NR is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and use Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, Use CP-OFDM and/or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink for better integration with other open standards , and supports beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook or a start and One or more of the information associated with a length indicator value (SLIV) set. The method may include sending 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 method of wireless communication performed by a network node. The method may include sending one 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 or more. The method may include receiving 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.

Some aspects described herein relate to UEs for wireless communications. A user device may include memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive an indication of a set of timing offset values associated with a HARQ-ACK codebook or associated with a set of SLIVs for candidate data channels associated with a HARQ-ACK codebook One or more of the information in . The one or more processors may be configured to: transmit 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 SLIV of.

Some aspects described herein relate to network nodes for wireless communications. A network node may include memory and one or more processors coupled to the memory. The one or more processors may be configured to: send an indication of a set of timing offset values associated with a HARQ-ACK codebook or associated with a set of SLIVs for candidate data channels associated with a HARQ-ACK codebook One or more of the information in . The one or more processors may be configured to: receive 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 SLIV of.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of a UE, the set of instructions may cause the UE to: receive an indication of a set of timing offset values associated with a HARQ-ACK codebook or to be used in conjunction with a HARQ-ACK codebook One or more of the information associated with the SLIV set of candidate data channels associated with the book. When executed by one or more processors of the UE, the set of instructions may cause the UE to: transmit a HARQ-ACK codebook, the HARQ-ACK codebook is based at least in part on different values of the set of timing offset values or One or more of the different values of the SLIV set.

Some aspects described herein relate to non-transitory computer-readable media storing sets of instructions for network nodes to communicate wirelessly. When executed by one or more processors of a network node, the set of instructions may cause the network node to: send an indication of a set of timing offset values associated with a HARQ-ACK codebook or communicate with One or more of the information associated with the SLIV set of the candidate data channel associated with the HARQ-ACK codebook. When executed by one or more processors of a network node, the set of instructions may cause the network node to: receive a HARQ-ACK codebook based at least in part on the set of timing offset values or one or more of the distinct values of the SLIV set.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include one of receiving 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 A component of one or more. The apparatus can include 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.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include one of sending 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 A component of one or more. The apparatus can include means for receiving 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.

Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations substantially as described herein with reference to and as illustrated by the drawings and specification , a network node, a wireless communication device and/or a processing system.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. 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, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure is provided for purposes of illustration and description, and not as a definition of the limits of the claimed terms.

Although aspects are described in this case by way of illustration of some examples, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes and/or packaging arrangements. For example, some aspects may be implemented by integrating chip embodiments or other non-modular 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) to achieve. Aspects may be implemented in wafer-level components, modular components, non-modular components, non-wafer-level components, device-level components, and/or system-level components. Apparatus incorporating the described aspects and features may include additional elements and features for realizing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for both analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors , interleaver, adder and/or accumulator). It is intended that aspects described herein may be practiced in devices, components, systems, distributed arrangements and/or end-user devices of various sizes, shapes and configurations.

Aspects of the present case are described more fully hereinafter with reference to the accompanying drawings. However, the present case may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present case. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art should appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether practiced independently of or in conjunction with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be implemented using any number of aspects set forth herein. Furthermore, the scope of the present invention is intended to cover such devices or methods practiced using structure, function, or structure and function in addition to the aspects of the present invention set forth herein or using aspects of the present invention other than those set forth herein other structure, function or structure and function of the practice. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

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

Although terms associated with 5G or New Radio (NR) Radio Access Technology (RAT) are used to describe aspects, aspects of this case can be applied to other RATs such as 3G RAT, 4G RAT and/or 5G (e.g., 6G ) after the RAT.

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 (eg, NR) network and/or a 4G (eg, Long Term Evolution (LTE)) network, among others. Wireless network 100 may include one or more network nodes 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120, or multiple UEs 120 (shown as UE 120a, UE 120b , UE 120c, UE 120d, and UE 120e) and/or other network entities. The network node 110 is the entity that communicates with the UE 120 . Network nodes 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and/or transport Receive Point (TRP). Each network node 110 can provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to a coverage area of a network node 110 and/or a network node subsystem serving that coverage area, depending on the context in which the term is used.

Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and/or another type of cell. A macrocell may cover a relatively large geographic area (eg, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with a service subscription. A femtocell may cover a relatively small geographic area (eg, a home) and may allow limited access by UEs 120 associated with the femtocell (eg, UEs 120 in a Closed Subscriber Group (CSG)). A network node 110 for a macrocell may be referred to as a macro base station. A network node 110 for a pico cell may be referred to as a pico base station. A network node 110 of a femtocell may be referred to as a femto base station or a home base station. In the example shown in FIG. 1, BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. tower. A network node may support one or more (eg, three) cells.

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

Wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from upstream stations (eg, network node 110 or UE 120 ) and send data transmissions to downstream stations (eg, UE 120 or network node 110 ). A relay station may be a UE 120 that may relay transmissions to other UEs 120 . In the example shown in FIG. 1, BS 110d (eg, a relay network node) may communicate with BS 110a (eg, a macro network node) and UE 120d to facilitate communication between BS 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay network node, a relay, or the like.

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, femto, and repeater base stations may have lower transmit power levels (e.g., 0.1 to 40 watts). 2 watts).

A 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 can communicate with the network node 110 via a backhaul communication link. Network nodes 110 may communicate with each other directly or indirectly via 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, terminal, mobile station, and/or subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a wireless phone, a wireless local loop (WLL) station, a tablet Computers, cameras, gaming devices, small laptops, smart computers, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart ring or smart bracelet)), entertainment equipment (such as music equipment, video equipment and/or satellite radio), vehicle parts or sensors, smart meters/sensors, industrial manufacturing equipment, GPS equipment and/or any other suitable device configured to communicate via 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 communication. Some UEs 120 may be considered Internet of Things (IoT) devices, and/or may be implemented as NB-IoT (Narrow Band IoT) devices. Some UEs 120 may be considered customer premise equipment. UE 120 may be included within a housing housing elements of UE 120 such as processor elements and/or memory elements. In some examples, a processor element and a memory element may be coupled together. For example, processor elements (eg, one or more processors) and memory elements (eg, memories) may be operatively, communicatively, electronically, 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. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be called a carrier, channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

The devices of the wireless network 100 can use the electromagnetic spectrum for communication, and the electromagnetic spectrum can be subdivided into various categories, frequency bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 may use one or more operating frequency bands for communication. In 5G NR, two initial operating frequency bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles, although a portion of FR1 is greater than 6 GHz. FR2 sometimes suffers from a similar nomenclature problem, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) (which the International Telecommunication Union (ITU) defines as the "millimeter wave" band), in documents and articles It is commonly referred to (interchangeably) as the "millimeter wave" band in

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have decided on an operating band for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus effectively extend FR1 and/or FR2 characteristics to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been decided to designate the frequency ranges 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 band.

With the above examples in mind, and unless expressly stated otherwise, it should be understood that the terms "sub-6 GHz", etc., if used herein, can refer broadly to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequency of frequency. In addition, unless expressly stated otherwise, it should be understood that the term "millimeter wave" and the like, if used herein, can be broadly meant to include mid-band frequencies, available in FR2, FR4, FR4-a or FR4-1, and/or Frequencies within FR5, or possibly within the EHF band. It is contemplated that the frequencies included in these operating frequency bands (eg, FR1 , FR2, FR3, FR4, FR4-a, FR4-1 and/or FR5) may be modified and that the techniques described herein apply to those modified frequency ranges.

The deployment of communication systems, such as 5G New Radio (NR) systems, can be arranged in a variety of ways with various elements or components. In a 5G NR system or network, network nodes, network entities, mobile elements of the network, radio access network (RAN) nodes, core network nodes, network elements, base stations or network equipment can be Implemented in aggregated or non-aggregated architecture. For example, a base station (such as Node B (NB), evolved NB (eNB), NR base station (BS), 5G NB, gNodeB (gNB), access point (AP), transmit-receive point (TRP), or cell ) or one or more units (or one or more elements) performing base station functions may be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a non-aggregated base station. A "network entity" or "network node" may represent a non-aggregated base station, or one or more units of a non-aggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or combination).

An aggregated base station may be configured to utilize a stack of radio protocols that are physically or logically integrated within a single RAN node (eg, within a single device or unit). Non-aggregated base stations may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (eg, 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 CU, DU, and RU may also be implemented as a virtual unit (eg, a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU)).

Base station type operations or network design may take into account the aggregation nature of the base station functions. For example, it can be implemented in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network ( vRAN, also known as Cloud Radio Access Network (C-RAN), uses non-aggregated base stations to facilitate communication system scaling by separating base station functions into one or more separately deployable components. A non-aggregated base station may include functions performed across two or more units at multiple physical locations, as well as functions performed virtually for at least one unit, which may allow flexibility in network design. Each unit of a non-aggregated base station may be configured for wired or wireless communication with at least one other unit of a non-aggregated base station.

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

In some aspects, the network node 110 may include a communication manager 150 . As described in more detail elsewhere herein, the communication manager 150 may send an indication of a set of timing offset values associated with a HARQ-ACK codebook or a set of SLIVs for candidate data channels associated with a HARQ-ACK codebook one or more of the associated information; and 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 a set of SLIVs. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

As before, Figure 1 is provided as an example. Other examples may differ from those described with respect to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, for example T antennas (T≧1). UE 120 may be equipped with a set of antennas 252a through 252r, eg, R antennas (R≧1).

At network node 110 , transmit processor 220 may receive data intended for UE 120 (or group of UEs 120 ) from data source 212 . Transmit processor 220 may select one or more modulation and coding schemes (MCS) 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 (eg, encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols to UE 120 . The transmit processor 220 may process system information (eg, for semi-static resource partitioning information (SRPI)) and control information (eg, CQI requests, grants, and/or upper layer signaling) and provide management overhead symbols and control symbols. Transmit processor 220 may generate signals for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). reference symbol. If applicable, transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, administrative burden symbols, and/or reference symbols, and may combine a set of output symbols The streams (eg, T output symbol streams) are provided to a corresponding set of data engines 232 (eg, T data engines), shown as data machines 232a through 232t. For example, each output symbol stream may be provided to a modulator element (shown as MOD) of modem 232 . Each modem 232 may process a corresponding output symbol stream (eg, for OFDM) using a corresponding modulator element to obtain an output sample stream. Each modem 232 may also process (eg, convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator element to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (eg, antennas 234a to 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 group of modems 254 (eg, R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator element (shown as DEMOD) of modem 254 . Each modem 254 may condition (eg, filter, amplify, downconvert, and/or digitize) the received signal using a corresponding demodulator element to obtain input samples. Each modem 254 may further process the input samples (eg, for OFDM) using demodulator elements to obtain received symbols. MIMO detector 256 may obtain received symbols from modem 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. Receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for UE 120 to data slot 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 elements 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 include, for example, one or more devices in the core network. The network controller 130 can communicate with the network node 110 via the communication unit 294 .

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and/or one or more The antenna array may be included in one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and/or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays may include one or more antenna elements (in a single enclosure or multiple enclosures), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and/or coupled One or more antenna elements, such as one or more elements of FIG. 2, to one or more transmit and/or receive elements.

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 information including RSRP, RSSI, RSRQ, and/or CQI). Report). Transmit processor 264 may generate reference symbols for one or more reference signals. If applicable, symbols from transmit processor 264 may be precoded by TX MIMO processor 266, further processed by data engine 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to network node 110 . In some examples, 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 antenna 252 , modem 254 , MIMO detector 256 , receive processor 258 , transmit processor 264 and/or TX MIMO processor 266 . The transceiver may be used by a processor (eg, controller/processor 280 ) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIGS. 5-9 ).

At network node 110, uplink signals from UE 120 and/or other UEs may be received by antenna 234, processed by modem 232 (e.g., the demodulator element of modem 232, shown as DEMOD), if applicable ) is detected by MIMO detector 236 and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120 . Receive processor 238 may provide decoded data to data slot 239 and decoded control information to controller/processor 240 . The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244 . The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234 , modem 232 , MIMO detector 236 , receive processor 238 , transmit processor 220 and/or TX MIMO processor 230 . The transceiver may be used by a processor (eg, controller/processor 240 ) and memory 242 to perform aspects of any of the methods described herein (eg, with reference to FIGS. 5-9 ).

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other elements of FIG. 2 may perform one or more operations associated with transmission of the HARQ acknowledgment codebook technique, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other element of FIG. 2 may execute or direct, for example, the procedure 600 of FIG. 6, the procedure 700 of FIG. Or the operation of other programs as described in this article. 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 that stores one or more instructions (eg, code and/or program code) for wireless communication. For example, 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 result in one or more The processor, UE 120 and/or network node 110 perform or direct operations such as procedure 600 of FIG. 6, procedure 700 of FIG. 7, and/or other procedures described herein. In some examples, execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions.

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

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

Although the blocks in Figure 2 are shown as distinct elements, the functions described above with respect to these blocks may be implemented in a single hardware, software or combination element or in various combinations of elements. For example, functionality 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 before, FIG. 2 is provided as an example. Other examples may differ from those described with respect to FIG. 2 .

FIG. 3 is a diagram illustrating an example 300 of timing offset values in accordance with the present disclosure. As shown in Figure 3, the network node may communicate with the UE via one or more physical downlink shared channel (PDSCH) communications and/or HARQ-ACK reports (eg, via physical uplink control channel (PUCCH) communications) . In some aspects, network nodes and UEs may be part of a wireless network. The UE and the network node may have established a wireless connection before the operation shown in FIG. 3 .

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

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

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

The UE may be configured to use a Type 1 HARQ-ACK codebook (eg, a fixed-size HARQ-ACK codebook with pre-configured and/or semi-static configuration) during slot n+2. To generate a HARQ-ACK codebook for transmission as a HARQ-ACK report 320, the UE determines 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 A collection of candidate data channels. 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 for DCI format 1_1 or DCI format 1_2 on serving cell c ( PDCCH), 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 and not configured to monitor PDCCH for DCI format 1_2 for serving cell c, the set of timing offset values is indicated by the first parameter (eg dl-DataToUL-ACK). If the UE is configured to monitor PDCCH for DCI format 1_2 for serving cell c, and is not configured to monitor PDCCH for DCI format 1_1, then the set of timing offset values is determined by the second parameter (eg, dl-DataToUL-ACK-ForDCIFormat1_2) instruct. If the UE is configured to monitor PDCCH for DCI format 1_1 and DCI format 1_2 for serving cell c, the set of timing offset values is provided by the union of the first parameter and the second parameter. The union of the first parameter and the second parameter may form a data set with repeated values.

As before, FIG. 3 is provided as an example. Other examples may differ from those described with respect to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of start and length values for candidate data channels in accordance with the present disclosure. As shown in FIG. 4 , the network node can communicate with the UE via one or more candidate data channels (eg, PDSCH channels). In some aspects, network nodes and UEs may be part of a wireless network. The UE and the network node may have established a wireless connection before the operation shown in FIG. 4 .

As shown in Figure 4, a UE may be configured with a set of candidate data channels 405 for a time slot. FIG. 4 further illustrates 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 the symbol of the time 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 with a start value of 2 and a length value of 12 extends from symbol 2 to symbol 13 of the time slot in the time domain. A candidate data channel 405 with a start value of 3 and a length value of 11 extends from symbol 3 to symbol 13 of the time slot in the time domain. A candidate data channel 405 with a start value of 2 and a length value of 10 extends from symbol 2 to symbol 11 of the time slot in the time domain. A candidate data channel 405 with a start value of 3 and a length value of 7 extends from symbol 3 to symbol 9 of the time slot in the time domain. A candidate data channel 405 with a start value of 3 and a length value of 4 extends from symbol 3 to symbol 6 of the time slot in the time domain. A candidate data channel 405 with a start value of 8 and a length value of 2 extends from symbol 8 to symbol 9 of the time slot in the time domain. A candidate data channel 405 with a start value of 8 and a length value of 6 extends from symbol 8 to symbol 13 of the time slot in the time domain.

Within one slot, the UE can identify all TDRAs associated with candidate data channels 405 for one cell. Based at least in part on TDRA, the UE may determine the maximum number of non-overlapping candidate data channels 405 that can be scheduled within a time slot and allocate the 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 is the same as candidate data channel 405 having a start value of 8 and a length value of 2 or having a value of 8. Candidate data channels 405 with a start value of 6 and a length value of 6 can be combined, and the maximum number of non-overlapping candidate data channels 405 is 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 the HARQ-ACK bits. For a subset of candidate data channels 405 mapped to the same HARQ-ACK bit, at most one candidate data channel 405 can be used to schedule the PDSCH.

The set of TDRA and/or candidate data channels 405 may be determined based at least in part on indications in one or more parameters (e.g., pdsch-TimeDomainAllocationList and/or pdsch-TimeDomainAllocationListDCI-1-2-r16, etc.) or may be determined at least in part It is determined based on the configuration in the communication protocol.

As before, FIG. 3 is provided as an example. Other examples may differ from those described with respect to FIG. 3 .

As described herein, the set of timing offset values may include redundancy (eg, duplicate values) and/or the set of candidate data channels may include redundancy. In a first example, a parameter providing a timing offset value (eg, dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCIFormat1_2) indicates a non-distinct value, (eg, includes {1,2,3,3,3, 4,4} set). In the second example, multiple parameters are configured that provide timing offset values (for example, dl-DataToUL-ACK and dl-DataToUL-ACK-ForDCIFormat1_2), and they contain shared values (for example, the values {1,2,3 } and the second set of values {2,3,4,5,6}). In a second example, a union (eg, direct union) of multiple parameters (eg, radio resource control (RRC) parameters) would contain repeated values, (eg, the values {1,2,3,2,3,4, 5,6} combination set). In a third example, an indication of a set of SLIVs for candidate data channels (eg, pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListDCI-1-2-r16) contains entries with duplicate SLIVs. For example, each entry of the TDRA set may include information about "slot offset 𝐾0, and/or start and length indicator SLIV". Two entries may have the same SLIV and different K0 values. In this case, the SLIV set determined according to the indication of the SLIV set (for example, pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListDCI-1-2-r16) may include duplicate SLIVs. In a fourth example, an indication of a set of SLIVs for candidate data channels (eg, pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListDCI-1-2-r16) includes entries with the same SLIV. For example, an indication of a SLIV set may indicate multiple SLIVs for different time slots, which may result in duplicate values in the SLIV set.

Based at least in part on having duplicate timing offset values and/or duplicate SLIV values, an associated HARQ-ACK codebook may have duplicate bits (e.g., multiple bits that map to the same candidate data channel with the same indication bits), 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 out of sync as to whether repetition bits are included, which may cause the network node to misinterpret the HARQ-ACK codebook. Based at least in part on the network node misinterpreting the HARQ-ACK codebook, the network node may retransmit communications that were misinterpreted as not being received by the UE, or the network node may fail to retransmit communications that were misinterpreted as being received by the UE. Network nodes and/or UEs 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 a set of SLIVs for candidate data channels associated with a HARQ-ACK codebook associated information. The UE may use different (e.g., non-repeating) sets of timing offset values (e.g., according to parameters such as dl-DataToUL-ACK and/or dl-DataToUL-ACK-ForDCIFormat1_2) and/or use a set of timing offset values according to {n-K1 } A set of different SLIV values for each time slot of each time slot determined by the set to generate (for example, construct and/or determine) a HARQ-ACK codebook (for example, a type 1 HARQ-ACK codebook). For example, the UE may identify and/or remove duplicate timing offset values from a set of timing offset values, and/or the UE may obtain from a TDRA table in DCI format that the UE is configured to monitor for a PDCCH associated with the serving cell. Identify and/or remove duplicate SLIV values in unions of row indices. .

In some aspects, a network node may be configured to send parameters that do not include repeat timing offset values (eg, dl-DataToUL-ACK and/or dl-DataToUL-ACK-ForDCIFormat1_2) and/or indicate that repeat SLIV is not indicated SLIV value for the value (for example, use pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListDCI-1-2-r16).

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

Based at least in part on deduplicated timing offset values and/or duplicate SLIV values, the associated HARQ-ACK codebook may not have duplicate bits (e.g., multiple bits map to the same candidate data channel with the same indication) , which can save communication, network, power and/or computing resources. Additionally or alternatively, the network node and the UE can synchronize on whether repetition bits are included, which can reduce the network node's misinterpretation of the HARQ-ACK codebook. Based at least in part on the correct interpretation of the HARQ-ACK codebook by the network node, the network node can avoid retransmissions that might otherwise be misinterpreted as not being received by the UE and the network node can retransmit communications that might otherwise be misinterpreted as being received by the UE communication. Network nodes and/or UEs can 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 in accordance with the present disclosure. As shown in FIG. 5 , a network node (eg, network node 110 ) may communicate with a UE (eg, UE 120 ). In some aspects, network nodes and UEs may be part of a wireless network (eg, wireless network 100). The UE and the network node may have established a wireless connection before the operation shown in FIG. 5 .

As indicated by reference numeral 505, the network node can send and the UE can receive configuration information. In some aspects, the UE may receive configuration information via one or more of RRC signaling, MAC CE, and/or DCI. In some aspects, the configuration information may include an indication of one or more configuration parameters selected by the UE (eg, known by the UE), and/or explicit configuration information used by the UE to configure the UE, and the like.

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

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

As indicated by element numeral 515, the UE may transmit and the network node may receive an indication that the transmission of a HARQ-ACK codebook is supported, the HARQ-ACK codebook is based at least in part on different values of the timing offset value and/or on the SLIV set different values. In some aspects, the UE may send the indication of support via RRC signaling (eg, as part of an RRC connection procedure).

As indicated by reference numeral 520, the UE may receive and the network node may send an indication that the HARQ-ACK codebook is to be based at least in part on a different value of a set of timing offset values and/or a different value of a set of SLIV. In some aspects, the UE may receive the indication in RRC communication that the indication is 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, and/or the like. Additionally or alternatively, the UE may receive the indication via dynamic signaling such as a resource grant (eg, DCI).

As indicated by reference numeral 525, the UE may receive and the network node may send an indication of the set of timing offset values and/or information associated with the SLIV for the candidate data lane. For example, the UE may receive indications and/or information via RRC signaling and/or via scheduling grants. In some aspects, the set of timing offset values and/or the set of SLIVs includes repeated values (eg, repeated and/or redundant, etc.) that map to the same HARQ-ACK codebook. For example, repeated values can be mapped to HARQ-ACK indications associated with the same data channel communication (eg, 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 (eg, dl-DataToUL-ACK and/or dl-DataToUL-ACK-ForDCIFormat1_2). The set of timing offset values may be based at least in part on a first subset of timing offset values (eg, associated with a first parameter of the one or more RRC-based parameters) and a timing offset value (eg, associated with A union of the second subset of the second parameter associated with the one or more RRC-based parameters. In some aspects, the information associated with the SLIV set may include one or more RRC-based (eg, using pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListDCI-1-2-r16) parameters. The set of SLIV may be based at least in part on a third subset of SLIV (eg, associated with a third parameter of the one or more RRC-based parameters) and a third subset of SLIV (eg, associated with a third parameter of the one or more RRC-based parameters). associated with the fourth argument) the union of the fourth subset.

As indicated by reference numeral 530, via the candidate data channel, the network node may transmit and the UE may attempt to receive one or more PDSCH communications. 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 signals sampled from one or more candidate data channels and determine whether the decoding was successful.

As indicated by reference numeral 535, the UE may determine and/or generate HARQ based at least in part on different values of the set of timing offset values and/or different (eg, non-repetitive and/or non-redundant) values of SLIV -ACK codebook. 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. A network node may similarly determine and/or generate a HARQ-ACK codebook (eg, size, number of bits, and/or mapping to one or more PDSCH communications, etc.) expected to be received by the UE.

In some aspects, the UE may generate a 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 a value that generates a different value of a set of timing offset values or a different value of a set of SLIV values. The UE may generate a different value for the set of timing offset values or a different value for 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.

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

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. A 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, a network node may decode a HARQ-ACK codebook based at least in part on an expected size, an expected number of bits, and/or a 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 generating a HARQ-ACK codebook based at least in part on different values of the set of timing offset values, and/or different values of the SLIV set. The sending user equipment of the ACK codebook. For example, a network node may determine a size and/or format (e.g., including mapping to PDSCH traffic) of a HARQ-ACK codebook based at least in part on different values of a set of timing offset values and/or different values of a set of SLIV (eg, expected HARQ-ACK codebook).

As before, FIG. 5 is provided as an example. Other examples may differ from those described with respect to FIG. 5 .

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

As shown in FIG. 6, in some aspects, procedure 600 may include receiving an indication of a set of timing offset values associated with a HARQ-ACK codebook or a candidate data channel for association with a HARQ-ACK codebook. One or more of the information associated with the SLIV set (block 610). For example, a UE (e.g., using the communication manager 140 and/or the receiving element 802 illustrated in FIG. 8 ) may receive an indication of a set of timing offset values associated with a HARQ-ACK codebook or communicate with the HARQ-ACK codebook for One or more of the information associated with the SLIV set of the candidate data channel associated with the ACK codebook, as described above.

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

Procedure 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in relation to one or more other procedures described elsewhere herein.

In a first aspect, procedure 600 includes generating 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.

In a second aspect, alone or in combination with the first aspect, the different values of the set of timing offset values include 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 timing offset values. SLIV sets fewer values.

In a third aspect, alone or in combination with one or more of the first and second aspects, procedure 600 includes receiving a HARQ-ACK codebook based at least in part on a different value of the set of timing offset values or An indication of one or more of the different values for this SLIV set.

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

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 set is indicated by a second RRC parameter, or wherein the information associated with the first SLIV subset is indicated by a third RRC parameter and the second subset associated with information associated with the second SLIV subset is indicated by a fourth RRC parameter indication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, procedure 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 includes determining the size of the HARQ-ACK codebook.

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

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

In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the procedure 600 includes determining different values of the SLIV set from the time domain resource configuration parameter set, wherein the time domain resource The time domain resource configuration parameters in the configuration parameter set include time slot parameters and SLIV.

In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the procedure 600 includes determining that the first time domain resource configuration parameters include the first time slot parameter and the first SLIV, determining The second time domain resource configuration parameter includes the second time slot parameter and the first SLIV, and the first SLIV is only included once in different values of the SLIV set.

Although FIG. 6 illustrates example blocks of procedure 600, in some aspects, procedure 600 may include additional blocks, fewer blocks, different blocks, or different arrangements of blocks than those illustrated in FIG. . Additionally or alternatively, two or more of the blocks of procedure 600 may be executed in parallel.

Fig. 7 is a diagram illustrating an example procedure 700, eg executed by a network node, in accordance with the present disclosure. The example procedure 700 is an example of a network node (eg, network node 110 ) performing operations associated with transmission of a HARQ-ACK codebook.

As shown in FIG. 7 , in some aspects, procedure 700 may include sending an indication of a set of timing offset values associated with a HARQ-ACK codebook or a candidate data channel for association with a HARQ-ACK codebook. One or more of the information associated with the SLIV set (block 710). For example, a network node (e.g., using the communication manager 150 and/or the transport element 904 illustrated in FIG. 9 ) may send an indication of a set of timing offset values associated with a HARQ-ACK codebook or communicate with One or more of the information associated with the SLIV set of the candidate data channel associated with the HARQ-ACK codebook, as described above.

As further shown in FIG. 7 , in some aspects, procedure 700 may include receiving a HARQ-ACK codebook based at least in part on different values of the set of timing offset values or different values of the set of SLIV values. One or more of (block 720). For example, a network node (e.g., using communication manager 150 and/or receiving element 902 illustrated in FIG. 9 ) may receive a HARQ-ACK codebook based at least in part on the set of timing offset values One or more of the different values or different values of the SLIV set, as previously described.

Procedure 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in relation to one or more other procedures described elsewhere herein.

In a first aspect, receiving the HARQ-ACK codebook includes: decoding the HARQ-ACK codebook based at least in part on: the sending UE is based at least in part on a different value of the set of timing offset values or a different value of the set of SLIV One or more of different values to generate a HARQ-ACK codebook.

In a second aspect, alone or in combination with the first aspect, the different values of the set of timing offset values include 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 Set fewer values.

In a third aspect, alone or in combination with one or more of the first and second aspects, procedure 700 includes sending a different value or An indication of one or more of the different values of the SLIV set.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the set of timing offset values is based at least in part on the first subset of timing offset values and the 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 news and a second subset of SLIVs associated with the news.

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 The set is indicated by the second RRC parameter, or wherein the information associated with the first subset of SLIV is indicated by the third RRC parameter, and the second subset is associated with the information associated with the second subset of the second SLIV Indicated by the fourth RRC parameter.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, procedure 700 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 includes determining the size of the HARQ-ACK codebook.

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

In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, procedure 700 includes: the different values of the set of timing offset values include the same number of different values as the set of timing offset values values, or where distinct values of the SLIV set contain the same number of values as the SLIV set.

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

In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the procedure 700 includes: determining different values of the SLIV set from the time domain resource configuration parameter set, wherein the time domain The time domain resource configuration parameters in the resource configuration parameter set include time slot parameters and SLIV.

In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the procedure 700 includes: determining that the first time domain resource configuration parameters include the first time slot parameters and the first SLIV , it is determined that the second time domain resource configuration parameter includes the second time slot parameter and the first SLIV, and the first SLIV is only included once in different values of the SLIV set.

Although FIG. 7 illustrates example blocks of procedure 700, in some aspects, procedure 700 may include additional blocks, fewer blocks, different blocks, or different arrangements of blocks than those illustrated in FIG. . Additionally or alternatively, two or more blocks of procedure 700 may be executed in parallel.

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, device 800 includes a receiving element 802 and a transmitting element 804 that can communicate with each other (eg, via one or more bus bars and/or one or more other elements). As shown, the device 800 can communicate with another device 806 (eg, a UE, a network node, or another wireless communication device) using a receiving element 802 and a transmitting element 804 . As further shown, apparatus 800 can include a communication manager 808 (eg, communication manager 140).

In some aspects, device 800 may be configured to perform one or more operations described herein in conjunction with FIG. 5 . Additionally or alternatively, device 800 may be configured to execute one or more procedures described herein, such as procedure 600 of FIG. 6 . In some aspects, the apparatus 800 and/or one or more elements shown in FIG. 8 may include one or more elements of the UE described in connection with FIG. 2 . Additionally or alternatively, one or more elements shown in FIG. 8 may be implemented within one or more elements described in connection with FIG. 2 . Additionally or alternatively, one or more elements of the set of elements may be at least partially implemented as software stored in memory. For example, an element (or a part of an element) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

The receiving component 802 can receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. Receiving component 802 may provide the received communication to one or more other components of device 800 . In some aspects, receiving element 802 may perform signal processing (eg, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communication, And the processed signal may be provided to one or more other elements of apparatus 806 . In some aspects, receiving element 802 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memories, or combination.

Transmission element 804 may send communications, such as reference signals, control information, data communications, or combinations thereof, to device 806 . In some aspects, one or more other elements of device 806 may generate communications and may provide the generated communications to transmission element 804 for transmission to device 806 . In some aspects, transmission element 804 may perform signal processing (eg, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the resulting communication and may transmit the processed signal to Device 806. In some aspects, transmission element 804 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller/processors, memory or other UEs described in connection with FIG. combination. In some aspects, the transmit element 804 can be collocated with the receive element 802 in the transceiver.

Receiving component 802 may receive 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 a HARQ-ACK codebook . Transmission element 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 SLIV.

Receiving component 802 may receive an indication that a 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.

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

The communication manager 808 can generate 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.

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

The communication manager 808 may determine that the first time domain resource configuration parameters include the first time slot parameters and the first SLIV.

The communication manager 808 may determine that the second time domain resource configuration parameters include the second time slot parameters and the first SLIV.

The communication manager 808 may include the first SLIV only once in different values of the SLIV set.

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

9 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a network node, or a network node may include the apparatus 900 . In some aspects, device 900 includes a receiving element 902 and a transmitting element 904 that can communicate with each other (eg, via one or more bus bars and/or one or more other elements). As shown, the device 900 can use the receiving element 902 and the transmitting element 904 to communicate with another device 906 (eg, a UE, a network node, or another wireless communication device). As further shown, apparatus 900 can include communication manager 908 (eg, communication manager 150).

In some aspects, device 900 may be configured to perform one or more operations described herein in conjunction with FIG. 5 . Additionally or alternatively, device 900 may be configured to execute one or more procedures described herein, such as procedure 700 of FIG. 7 , or a combination thereof. In some aspects, the apparatus 900 and/or one or more elements shown in FIG. 9 may include one or more elements of the network node described in connection with FIG. 2 . Additionally or alternatively, one or more elements shown in FIG. 9 may be implemented within one or more elements described in connection with FIG. 2 . Additionally or alternatively, one or more elements of the set of elements may be at least partially implemented as software stored in memory. For example, an element (or a part of an element) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

The receiving component 902 can receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. Receiving component 902 may provide the received communication to one or more other components of device 900 . In some aspects, receiving element 902 may perform signal processing (eg, filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communication, And the processed signal may be provided to one or more other elements of apparatus 906 . In some aspects, the receiving element 902 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controller/processors, memory of the network nodes described in connection with FIG. 2 or a combination thereof.

Transmission element 904 may send communications, such as reference signals, control information, data communications, or combinations thereof, to device 906 . In some aspects, one or more other elements of device 906 may generate communications and may provide the generated communications to transmission element 904 for transmission to device 906 . In some aspects, transmission element 904 may perform signal processing (eg, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the resulting communication and may transmit the processed signal to Device 906. In some aspects, transmission element 904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller/processors, memory or a combination thereof. In some aspects, the transmit element 904 can be co-located with the receive element 902 in the transceiver.

Transmission element 904 may transmit 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 a HARQ-ACK codebook indivual. Receiving element 902 may receive 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 transmitting element 904 can send 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 can determine the HARQ-ACK codebook.

The communication manager 908 can generate 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.

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

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

The communication manager 908 may determine that the second time domain resource configuration parameters include the second time slot parameters and the first SLIV.

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

The number and arrangement of elements shown in FIG. 9 are provided as examples. In fact, there may be additional elements, fewer elements, different elements or different arrangements of elements than those shown in FIG. 9 . Furthermore, two or more elements shown in FIG. 9 may be implemented within a single element, or a single element shown in FIG. 9 may be implemented as a plurality of distributed elements. Additionally or alternatively, a set of element(s) shown in FIG. 9 may perform one or more functions described as being performed by another set of elements shown in FIG. 9 .

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

Aspect 1: A wireless communication method performed by a user equipment (UE), including: receiving an indication of a timing offset value set associated with a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook or used for one or more of information associated with a set of start and length indicator values (SLIVs) for candidate data channels associated with a HARQ-ACK codebook; and sending a HARQ-ACK codebook, at least in part based on one or more of different values of the set of timing offset values or different values of the set of SLIV.

Aspect 2: The method according to 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 SLIV.

Aspect 3: The method of any of Aspects 1-2, wherein the different values of the set of timing offset values include fewer values than the set of timing offset values, or wherein the different values of the set of SLIV Include fewer values than the SLIV set.

Aspect 4: The method according to any one of aspects 1-3, further comprising: receiving the HARQ-ACK codebook based at least in part on different values of the set of timing offset values or different values of the set of SLIV Instructions for one or more of .

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

Aspect 6: The method of Aspect 5, wherein the first subset of timing offset values is indicated by a first radio resource control (RRC) parameter and the second subset of timing offset values is indicated by a second RRC parameter , or wherein information associated with a first subset of SLIV is indicated by a third RRC parameter, and a second subset of information associated with a second subset of SLIV is indicated by a fourth RRC parameter.

Aspect 7: The method of any one of Aspects 1-6, further comprising determining a HARQ-ACK codebook.

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

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

Aspect 10: The method of any of Aspects 1-9, further comprising: generating a difference in the set of timing offset values based at least in part on removing at least one value from the set of timing offset values or the set of SLIV value or a value of a distinct value for this SLIV set.

Aspect 11: The method according to any one of Aspects 1-10, further comprising: determining different values of the SLIV set from the time domain resource configuration parameter set, wherein the time domain resource in the time domain resource configuration set Configuration parameters include time slot parameters and SLIV.

Aspect 12: The method according to Aspect 11, further comprising: determining that the first time domain resource configuration parameter includes the first time slot parameter and the first SLIV; determining that the second time domain resource configuration parameter includes the second time slot parameter and the first time slot parameter SLIV; and the first SLIV is included only once in different values of the SLIV set.

Aspect 13: A wireless communication method performed by a network node, comprising: sending an indication of a set of timing offset values associated with a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook or used in connection with HARQ-ACK one or more of information associated with start and length indicator value (SLIV) sets of candidate data channels associated with the ACK codebook; and receiving a HARQ-ACK codebook, the HARQ-ACK codebook being based at least in part on timing One or more of the different values of the set of offset values or the different values of the set of SLIV.

Aspect 14: The method of Aspect 13, wherein receiving the HARQ-ACK codebook comprises: decoding the HARQ-ACK codebook based at least in part on the sending UE generating the HARQ-ACK codebook based at least in part on one or more of: - ACK codebook: different values of the set of timing offset values, or different values of the set of SLIV.

Aspect 15: The method of any of aspects 13-14, wherein the different values of the set of timing offset values include 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 timing offset values SLIV sets fewer values.

Aspect 16: The method according to any one of aspects 13-15, further comprising: sending the HARQ-ACK codebook based at least in part on different values of the set of timing offset values or different values of the set of SLIV Instructions for one or more of .

Aspect 17: The method of any of Aspects 13-16, wherein the set of timing offset values is based at least in part on the first subset of timing offset values and the second subset of timing offset values. A union, 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 the first subset of timing offset values is indicated by a first radio resource control (RRC) parameter and the second subset of timing offset values is indicated by a second RRC parameter , or wherein information associated with a first subset of SLIV is indicated by a third RRC parameter, and a second subset of information associated with a second subset of SLIV 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 includes determining a size of the HARQ-ACK codebook.

Aspect 21: The method of aspect 20, wherein 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.

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

Aspect 23: The method of any of Aspects 13-22, further comprising: generating a difference in the set of timing offset values based at least in part on removing at least one value from the set of timing offset values or the set of SLIV value or a value of a distinct value for this SLIV set.

Aspect 24: The method according to any one of aspects 13-23, further comprising: determining different values of the SLIV set from the time domain resource configuration parameter set, wherein the time domain resource in the time domain resource configuration parameter set Configuration parameters include time slot parameters and SLIV.

Aspect 25: The method as in Aspect 24, further comprising: determining that the first time domain resource configuration parameters include the first time slot parameter and the first SLIV; determining the second time domain resource configuration parameter includes the second time slot parameter and the first time slot parameter SLIV; and comprising: including the first SLIV only once in different values of the set of SLIVs.

Aspect 26: An apparatus for performing wireless communication at a device, comprising a processor; a memory coupled to the processor; and stored in the memory and executable by the processor to cause the apparatus to perform any of aspects 1-25 Directives for one or more methods.

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

Aspect 28: A device for wireless communication, comprising at least one component for performing one or more methods 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 one or more of the methods of Aspects 1-25.

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

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

Further disclosures are included in the appendix. The appendices are provided as examples only and should be considered part of the specification. Definitions, illustrations or other descriptions in an appendix do not supersede or overwrite similar information contained in the detailed description or drawings. Furthermore, definitions, diagrams or other descriptions in the detailed description or drawings do not supersede or overwrite similar information contained in the appendices. Furthermore, the Addendum is not intended to limit the possible disclosures.

As used herein, the term "component" is intended to be construed broadly as hardware and/or a combination of hardware and software. "Software" shall be construed broadly to mean instructions, sets of instructions, code, code fragments, code, programs, subroutines, software modules, applications, software applications, packages, routines, subroutines, objects , executable files, executable threads, programs and/or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other terms. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. Obviously, the systems and/or methods described herein can be implemented with different forms of hardware and/or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and/or methods does not limit these aspects. Accordingly, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will appreciate that software and hardware can be designed to implement the systems and/or methods based at least in part on the description herein. /or method.

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

Although certain combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of the individual aspects. Many of these features can 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 in combination with each other 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 those items, including individual members. For example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, and any combination with 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 sequence of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless expressly stated otherwise. Also, 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 related to the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "set" are intended to include one or more items and may be used interchangeably with "one or more". If the intent is to describe one item, use the phrase "only one" or similar language. Furthermore, as used herein, the terms "has," "have," "having," etc., are intended to be open-ended terms that do not limit the elements they modify (eg, an element "has" A may There is also B). Additionally, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Furthermore, as used herein, the term "or" when used in a sequence is intended to be inclusive and may be used interchangeably with "and/or" unless expressly stated otherwise (eg, if used with "either) ” or “only one of” in combination).

100: wireless network 102a: Macrocytosis 102b: pico cells 102c: Femtocells 110: Network node 110a:BS 110b:BS 110c:BS 110d:BS 120: User Equipment (UE) 120a:UE 120b:UE 120c:UE 120d:UE 120e:UE 130: Network controller 140:Communication Manager 150:Communication Manager 200: example 212: Sources of information 220: launch processor 230: Transmit (TX) Multiple-Input Multiple-Output (MIMO) Processor 232a: modem 232t: modem 234a: Antenna 234t: Antenna 236:MIMO detector 238: Receive processor 240: Controller/Processor 242: memory 244: Communication unit 246: Scheduler 252a: Antenna 252r: Antenna 254a: modem 254r: modem 256:MIMO detector 258: Receive processor 260: data slot 262: Sources of information 264: Transmit Processor 266:TX MIMO processor 280: Controller/Processor 282: memory 290: Controller/Processor 292: memory 294: Communication unit 300: Example 305:PDSCH communication 310:PDSCH communication 315:PDSCH communication 320: HARQ-ACK report 400: Example 405: Candidate Data Channel 410: start and length values 500: example 505: Step 510: step 515: Step 520: step 525: step 530: step 535: step 540: step 545: step 600: sample program 610: block 620: block 700: sample program 710: block 720: block 800: Example device 802: receiving element 804: transmission element 806:Another device 808:Communication Manager 900: Example device 902: receiving element 904: transmission element 906: another device 908:Communication Manager

In order that the above recited features of the present disclosure can be understood in detail, a more particular description briefly summarized above may be had by reference to several aspects, some of which are illustrated in the accompanying drawings. It is to be noted, however, that the drawings illustrate only certain typical aspects of the present case, and are therefore not to be considered limiting of its scope, as 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 application.

FIG. 2 is a diagram illustrating an example of a network node communicating with a user equipment (UE) in a wireless network according to the present invention.

FIG. 3 is a diagram illustrating an example of a timing offset value according to the present application.

4 is a diagram illustrating examples of start and length values for candidate material channels in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example associated with transmission of a HARQ acknowledgment codebook according to the present disclosure.

6 and 7 are diagrams illustrating example procedures associated with transmission of HARQ acknowledgment codebooks according to the present disclosure.

8 and 9 are diagrams of example devices for wireless communication in accordance with the present disclosure.

Domestic deposit information (please note in order of depositor, date, and number) none Overseas storage information (please note in order of storage country, institution, date, and number) none

500: example

505: Step

510: step

515: Step

520: step

525: step

530: step

535: step

540: step

545: step

Claims (30)

A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: receiving an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook or a start and one or more of the information associated with the length indicator value (SLIV) set; and sending 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. The UE according to claim 1, wherein the one or more processors are further configured to: generate the HARQ-ACK codebook based at least in part on one or more of the following: A different value for the set of timing offset values, or Different values for this SLIV set. The UE according to 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 SLIV set include fewer values than the SLIV set. The UE according to claim 1, wherein the one or more processors are further configured to: 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 is received. The UE according to 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 SLIVs is based at least in part on a union of a first subset of SLIVs associated with the message and a second subset of SLIVs associated with the message. The UE according to claim 5, wherein the first subset of the timing offset values is indicated by a first radio resource control (RRC) parameter, and the second subset of the timing offset values is indicated by a second RRC parameter ,or Wherein the information associated with the first subset of SLIV is indicated by a third RRC parameter, and the second subset associated with the information associated with the second subset of SLIV is indicated by a fourth RRC parameter. The UE according to claim 5, wherein the first subset of timing offset values and the second subset of timing offset values do not contain repeated timing offset values, or Wherein the first subset of SLIVs and the second subset of SLIVs do not contain duplicate SLIVs. The UE according to claim 1, wherein the one or more processors are further configured to determine the HARQ-ACK codebook. The UE according to claim 8, wherein the one or more processors for determining the HARQ-ACK codebook are configured to determine a size of the HARQ-ACK codebook. The UE according to claim 9, wherein 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 SLIV. The UE according to claim 1, wherein the one or more processors are further configured to: A different value of the set of timing offset values or a different value of the set of SLIV is generated based at least in part on removing at least one value from the set of timing offset values or the set of SLIV. The UE according to claim 1, wherein the one or more processors are further configured to: determining different values of the SLIV set from a time domain resource configuration parameter set, A time domain resource configuration parameter in the time domain resource configuration parameter set includes a time slot parameter and a SLIV. The UE according to claim 12, wherein the one or more processors are further configured to: Determining a first time domain resource configuration parameter includes a first time slot parameter and a first SLIV; determining a second time domain resource configuration parameter including a second time slot parameter and the first SLIV; and The first SLIV is included only once in different values of the SLIV set. A network node for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: Send an indication of a set of timing offset values associated with a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook or a start and one or more of the information associated with the length indicator value (SLIV) set; and The HARQ-ACK codebook is received, 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. The network node according to claim 14, wherein the one or more processors for receiving the HARQ-ACK codebook are configured to: Decoding the HARQ-ACK codebook based at least in part on a sending UE generating the HARQ-ACK codebook based at least in part on one or more of the following: A different value for this timing offset value, or A different value for this SLIV. The network node according to claim 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 distinct values of the SLIV set include fewer values than the SLIV set. The network node according to 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. The network node according to 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 Wherein the set of SLIVs is based at least in part on a union of a first subset of SLIVs associated with the message and a second subset of SLIVs associated with the message. The network node according to claim 18, wherein the first subset of the timing offset values is indicated by a first radio resource control (RRC) parameter, and the second subset of the timing offset values is indicated by a second RRC parameter indication, or wherein the information associated with the first subset of SLIV is indicated by a third RRC parameter, and the second subset associated with the information associated with the second subset of SLIV is indicated by a fourth RRC parameter instruct. The network node according to claim 14, wherein the one or more processors are further configured to determine the HARQ-ACK codebook. The network node according to claim 20, wherein the one or more processors for determining the HARQ-ACK codebook are configured to determine a size of the HARQ-ACK codebook. The network node according to claim 21, wherein 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 SLIV. The network node according to claim 14, wherein based at least in part on a configuration of the network node, one or more of the following: the distinct values of the set of timing offset values include the same number of values as the set of timing offset values, or Wherein the different values of the SLIV set include the same number of values as the SLIV set. The network node according to claim 14, wherein the one or more processors are further configured to: generating the values of the different values of the set of timing offset values or the different values 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 determining the different values of the SLIV set from a time domain resource configuration parameter set, A time domain resource configuration parameter in the time domain resource configuration parameter set includes a time slot parameter and a SLIV. The network node according to claim 24, wherein the one or more processors are further configured to: Determining a first time domain resource configuration parameter includes a first time slot parameter and a first SLIV; determining a second time domain resource configuration parameter including a second time slot parameter and the first SLIV; and The first SLIV is included only once in the distinct values of the set of SLIVs. A wireless communication method performed by a user equipment (UE), comprising: receiving an indication of a set of timing offset values associated with a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook or a start and one or more of the information associated with the length indicator value (SLIV) set; and sending 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. According to the method of claim 26, further comprising: 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 is received. According to the method of claim 26, further comprising: A different value of the set of timing offset values or a different value of the set of SLIV is generated based at least in part on removing at least one value from the set of timing offset values or the set of SLIV. A wireless communication method performed by a network node, comprising: Send an indication of a set of timing offset values associated with a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook or a start and one or more of the information associated with the length indicator value (SLIV) set; and The HARQ-ACK codebook is received, 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. According to the method of claim 29, further comprising: 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.

Images