Enhanced prefeedback for resending hybrid automatic repeat requests

By introducing a pre-feedback mechanism into the wireless communication system, the uncertain feedback problem in HARQ retransmission is solved, resource utilization efficiency is improved, retransmission of transmission blocks is reduced, and system performance is enhanced.

CN123125987APending Publication Date: 2026-11-17QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090971.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing wireless communication systems suffer from inefficiency when retransmitting transport blocks due to uncertain HARQ feedback during Hybrid Automatic Repeat Request (HARQ) retransmission, especially since retransmission is still required even after successful decoding by the UE.

Method used

By introducing a prefeedback mechanism, the network entity sends a prefeedback request when it receives uncertain HARQ feedback, and the UE sends a second ACK feedback according to the prefeedback instruction, thereby avoiding the retransmission of the transport block.

Benefits of technology

This reduces the retransmission of transport blocks that the UE successfully decodes, improves resource utilization efficiency, and enhances the performance of the wireless communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125987A_ABST
    Figure CN123125987A_ABST
Patent Text Reader

Abstract

Methods, systems, and apparatus for conducting wireless communications are described. The techniques described herein provide pre-feedback enhancements for Hybrid Automatic Repeat Request (HARQ) retransmission. In some examples, the User Equipment (UE) can receive transport blocks transmitted via a physical downlink shared channel. The UE can send a first acknowledgment (ACK) feedback indicating successful reception of the transport block in response to receiving it. The UE can receive downlink control information including the pre-feedback indication. The UE can send a second ACK feedback indicating successful reception of the transport block.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The following discussion relates to wireless communications, including enhanced pre-feedback for hybrid automatic repeat request retransmission. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses supporting enhanced pre-feedback for Hybrid Automatic Repeat Request (HARQ) retransmission. For example, the described pre-feedback technique for HARQ retransmission can reduce the retransmission of transport blocks successfully decoded by the UE. In some examples, the UE may receive transport blocks transmitted via the Physical Downlink Shared Channel (PDSCH). The UE may send a first acknowledgment (ACK) feedback indicating successful reception of the transport block in response to receiving it. The UE may receive downlink control information (DCI) including a pre-feedback indication requesting a second feedback message before receiving the retransmission of the first transport block. The UE may send a second ACK feedback indicating successful reception of the transport block.

[0004] A method for wireless communication by a user equipment (UE) is described. The method may include: receiving a first transport block transmitted by a first PDSCH; in response to receiving the first transport block, transmitting a first feedback message indicating an acknowledgment (ACK) of the first transport block; after transmitting the first feedback message, receiving a first DCI including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and in response to receiving the first DCI, transmitting a second feedback message indicating an ACK of the first transport block.

[0005] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors are capable of operating individually or jointly to execute code to cause the UE to: receive a first transport block transmitted by a first PDSCH; in response to receiving the first transport block, transmit a first feedback message indicating an ACK for the first transport block; after transmitting the first feedback message, receive a first DCI including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and in response to receiving the first DCI, transmit a second feedback message indicating an ACK for the first transport block.

[0006] Another UE for wireless communication is described. The UE may include: components for receiving a first transport block transmitted via a first PDSCH; components for transmitting a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block; components for receiving a first DCI including a pre-feedback indication after transmitting the first feedback message, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and components for transmitting a second feedback message indicating an ACK for the first transport block in response to receiving the first DCI.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a first transport block transmitted by a first PDSCH; in response to receiving the first transport block, send a first feedback message indicating an ACK for the first transport block; after sending the first feedback message, receive a first DCI including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and in response to receiving the first DCI, send a second feedback message indicating an ACK for the first transport block.

[0008] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first DCI includes a new data indicator (NDI) that has not been switched.

[0009] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first DCI includes a field indicating a pre-feedback indication.

[0010] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving a second DCI including a pre-feedback indication, wherein the second DCI includes a handover NDI indicating that the second DCI may be associated with a second transport block that may not have been successfully received by the UE; and in response to receiving the second DCI including the handover NDI, sending a first negative acknowledgment (NACK) feedback message indicating unsuccessful reception of the second transport block.

[0011] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling that indicates a configuration associated with a pre-feedback indication.

[0012] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending control signaling associated with a pre-feedback indication, wherein the sending control signaling may be based on the PDSCH drop rate.

[0013] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving a second DCI that schedules the first transport block prior to receiving the first transport block, wherein the second DCI indicates a first physical uplink control channel (PUCCH) resource associated with the first feedback message and a second PUCCH resource associated with the second feedback message.

[0014] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving a second DCI indicating a PUCCH resource associated with a second feedback message during PDSCH transmission.

[0015] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the second DCI can be rate-matched with the first transport block.

[0016] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the second DCI punches one or more resource elements associated with the first transport block. Attached Figure Description

[0017] Figure 1 An example of a wireless communication system supporting enhanced pre-feedback for hybrid automatic repeat request retransmission is shown, according to one or more aspects of this disclosure.

[0018] Figure 2 An example of a wireless communication system supporting enhanced pre-feedback for hybrid automatic repeat request retransmission is shown, according to one or more aspects of this disclosure.

[0019] Figure 3 An example of a process flow supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, is shown.

[0020] Figure 4 An example of a process flow supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, is shown.

[0021] Figure 5 An example of a process flow supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, is shown.

[0022] Figure 6 and Figure 7 A block diagram is shown of an apparatus that supports enhanced pre-feedback for retransmission of hybrid automatic repeat requests, according to one or more aspects of this disclosure.

[0023] Figure 8 A block diagram is shown of a communication manager that supports enhanced pre-feedback for retransmission of hybrid automatic repeat requests, according to one or more aspects of this disclosure.

[0024] Figure 9 A diagram is shown of a system including a device that supports enhanced pre-feedback for retransmission of hybrid automatic repeat requests, according to one or more aspects of this disclosure.

[0025] Figure 10 and Figure 11 A flowchart illustrating an enhanced pre-feedback method for retransmitting hybrid automatic repeat requests, supported by one or more aspects of this disclosure, is shown. Detailed Implementation

[0026] Some wireless communication systems may deploy one or more network entities to support communications for user equipment (UE). The UE can receive transport blocks transmitted via the Physical Downlink Shared Channel (PDSCH) from the network entities, and the UE can send Hybrid Automatic Repeat Request (HARQ) feedback in response to receiving the transport block. For example, if the transport block is successfully decoded, the UE can send a HARQ Acknowledgment (ACK) feedback, and if the transport block is not successfully decoded, the UE can send a HARQ Negative Acknowledgment (NACK) feedback. In some cases, although the UE can send ACK feedback within the scheduling resources used for HARQ feedback, the network entity may mark the expected ACK feedback as indeterminate (e.g., decoding of the scheduling resources may result in neither ACK nor NACK being marked). In some examples, the network entity may treat an indeterminate HARQ feedback as a NACK feedback and retransmit the transport block to the UE. Retransmission of transport blocks successfully decoded by the UE can be an inefficient use of resources.

[0027] Pre-feedback techniques for HARQ retransmission can reduce the retransmission of transport blocks successfully decoded by the UE. When a network entity receives indeterminate HARQ feedback, it can send downlink control information indicating a pre-feedback request. This allows the UE to retransmit ACK feedback and allows the network entity to avoid retransmission of transport blocks.

[0028] In some examples, the UE may receive a transport block sent by the ODSCH. In response to receiving the transport block, the UE may send a first ACK feedback indicating successful reception of the transport block. In response to sending the ACK feedback, the UE may receive downlink control information (DCI) including a pre-feedback indication that requests a second feedback message before the retransmission of the first transport block. In response to receiving the DCI including the pre-feedback indication, the UE may send a second ACK feedback indicating successful reception of the transport block. In some cases, the DCI includes a field providing the pre-feedback indication.

[0029] The aspects of this disclosure are first described in the context of a wireless communication system. They are also described in the context of a process flow. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to enhanced pre-feedback for hybrid automatic repeat request retransmission, and are described with reference to apparatus diagrams, system diagrams, and flowcharts relating to enhanced pre-feedback for hybrid automatic repeat request retransmission.

[0030] Figure 1An example of a wireless communication system 100 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission is shown, according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0031] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0032] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are shown below. Figure 1 As shown, the UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including the UE 115 or network entity 105).

[0033] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0034] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0035] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0036] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize a protocol stack physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) (such as CU 160), a Distributed Unit (DU) (such as DU 165), a Radio Unit (RU) (such as RU 170), a RAN Intelligent Controller (RIC) (such as RIC 175) (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system (such as SMO system 180), or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0037] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0038] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0039] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0040] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0041] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0042] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0043] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0044] The time interval of network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a multiple of a basic time unit. The sampling period is seconds, where It can represent the supported subcarrier spacing, and It can represent the supported Discrete Fourier Transform (DFT) size. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0045] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0046] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0047] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0048] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0049] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0050] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 sends to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0051] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0052] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0053] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0054] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0055] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., for the antenna array of the transmitting or receiving device or for some other orientation).

[0056] UE 115 and network entity 105 may support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0057] In some cases, UE 115 may receive transport blocks sent by PDSCH from network entity 105, and UE 115 may send HARQ feedback in response to receiving the transport block. For example, if the transport block is successfully decoded, UE 115 may send HARQ ACK feedback, and if the transport block is not successfully decoded, UE 115 may send HARQ NACK feedback. In some cases, although UE 115 may send ACK feedback, network entity 105 may mark the expected ACK feedback as indeterminate (e.g., decoding of the scheduling resources used for HARQ feedback may result in neither marking ACK nor NACK). In some examples, network entity 105 may treat an indeterminate HARQ feedback as NACK feedback and retransmit the transport block to UE 115. Retransmission of transport blocks successfully decoded by UE 115 may be an inefficient use of resources.

[0058] The pre-feedback technique for HARQ retransmission can reduce the retransmission of transport blocks successfully decoded by UE 115. When network entity 105 receives indeterminate HARQ feedback, network entity 105 can send downlink control information indicating a pre-feedback request, which allows UE 115 to retransmit ACK feedback and allows network entity 105 to avoid retransmission of transport blocks.

[0059] In some examples, UE 115 can receive transport blocks sent by PDSCH. In response to receiving a transport block, UE 115 can send a first ACK feedback indicating successful reception of the transport block. In response to sending the ACK feedback, UE 115 can receive a DCI including a pre-feedback indication that requests a second feedback message before the retransmission of the first transport block. In response to receiving the DCI including the pre-feedback indication, UE 115 can send a second ACK feedback indicating successful reception of the transport block. In some cases, the downlink control information includes a field providing the pre-feedback indication.

[0060] Figure 2 An example of a wireless communication system 200 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission is shown according to one or more aspects of this disclosure. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may also include a network entity 105-a, which may be an example of network entity 105 as described herein.

[0061] UE 115-a can communicate with network entity 105-a using communication link 125-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a can include a bidirectional link that enables both uplink and downlink communication. For example, network entity 105-a can use communication link 125-a to send downlink signals (e.g., downlink transmissions) to UE 115-a, such as downlink control signaling 205 and downlink data signaling 210, and UE 115-a can use communication link 125-a to send uplink signals (e.g., uplink transmissions) to network entity 105-a, such as uplink control signaling 215 and uplink data signaling 220.

[0062] UE 115-a can receive transport block 225 sent by PDSCH from network entity 105-a, and UE 115 can send a HARQ feedback message 230 in response to receiving the transport block. For example, if the transport block is successfully decoded, UE 115-a can send a HARQ ACK, and if the transport block is not successfully decoded, UE 115 can send a HARQ NACK. In some cases, UE 115-a can send a HARQ feedback message 230 indicating an ACK for the transport block, and network entity 105-a can mark the expected ACK as indeterminate (e.g., decoding of the scheduling resources used for HARQ feedback may result in neither marking an ACK nor a NACK). In some examples, network entity 105-a can treat an indeterminate HARQ feedback as a NACK feedback and retransmit the transport block to UE 115-a.

[0063] After sending feedback message 230, network entity 105-a may send DCI 235 including a pre-feedback indication, and UE 115-a may receive DCI 235 including the pre-feedback indication. The pre-feedback indication may request a second feedback message before receiving a retransmission of transport block 225. UE 115-a may send a second feedback message 240 indicating an ACK for the first transport block in response to receiving DCI 235, and UE 115-a may not expect to receive a retransmission of the transport block with the PDSCH indicated in the DCI. If the original transmission of the transport block is not received correctly, UE 115-a may send NACK as pre-feedback, and UE 115-a may receive a retransmission of the transport block.

[0064] In some cases, a lack of Physical Uplink Control Channel (PUCCH) reliability can increase the likelihood of indeterminate HARQ feedback. The PDSCH drop rate (e.g., the rate at which successfully decoded transport blocks of PDSCH are retransmitted to UE 115-a) can impact overall system downlink throughput. In some cases, the probability of HARQ feedback received by network entity 105-a being indeterminate may be non-negligible due to uplink coverage or PUCCH bottlenecks. Network entity 105-a may identify HARQ feedback as indeterminate if it is received as discontinuously transmitted (DTX) (e.g., no HARQ feedback transmission detected), such as for PUCCH format 0 received via incoherent sequence detection. Additionally or alternatively, when HARQ feedback is conveyed in an uplink control information (UCI) block with cyclic redundancy check (CRC), such as when the UCI payload size is greater than or equal to twelve, network entity 105-a may identify HARQ feedback as indeterminate due to CRC failure. From a network perspective, treating an indeterminate HARQ response as a NACK and retransmitting the transport block is likely the preferred option. Otherwise, if the indeterminate HARQ response is actually a NACK indicating unsuccessful decoding of the transport block, and network entity 105-a treats the indeterminate HARQ response as an ACK, it may be impossible to resolve the error of the transport block not being successfully decoded within the physical (PHY) or MAC layer. While a NACK sent by UE 115-a and detected as indeterminate by network entity 105-a (to indeterminate NACKs) may not be a problem, to indeterminate ACKs may result in the wasteful retransmission of transport blocks that would otherwise be discarded by UE 115-a.

[0065] Figure 3 Examples of process flow 300 supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, are shown. In some examples, process flow 300 may be implemented as described in reference respectively. Figure 1 and Figure 2 The aspects of the wireless communication systems 100 and 200 described herein, or as referred to respectively, Figure 1 and Figure 2 The described wireless communication systems 100 and 200 are implemented in various aspects. For example, process flow 300 can be implemented by network entities (e.g., network entity 105-b and network entity 105-c), which can be as described in the reference. Figure 1 and Figure 2 An example of network entity 105 is described. Process flow 300 can be implemented by a UE (e.g., UE 115-b and UE 115-c), which can be as described in the reference. Figure 1 and Figure 2 An example of a UE as described.

[0066] Process flow 305 illustrates an example of a wasted retransmission of an uncertain HARQ ACK for a transport block. At 310, network entity 105-b may send a DCI scheduling the PDSCH transmission. At 315, network entity 105-b may send the transport block for the PDSCH transmission. UE 115-b may receive the PDSCH transmission and successfully decode the transport block. At 320, UE 115-b may send a HARQ feedback message indicating an ACK for the transport block. Network entity 105-a may (e.g., incorrectly) receive the ACK as DTX or uncertain and treat the HARQ feedback message as a NACK. At 325, network entity 105-b may send a DCI scheduling the retransmission of the transport block (e.g., where the New Data Indicator (NDI) has not been switched). At 330, network entity 105-b may retransmit the transport block (e.g., a second PDSCH transmission with a redundant version of the transport block). Because the transport block was successfully received by UE115-b, UE115-b discarded the retransmitted transport block, and the retransmission of the transport block was wasted. At 335, UE115-b can send a HARQ feedback message indicating an ACK for the retransmitted transport block.

[0067] Process flow 340 illustrates an example of an uncertain NACK for retransmission of a transport block. At 345, network entity 105-c may send a DCI scheduling the PDSCH transmission. At 350, network entity 105-c may send the transport block sent via PDSCH. UE 115-c may receive the PDSCH transmission and attempt to decode the transport block, but decoding fails. At 355, UE 115-c may send a HARQ feedback message indicating a NACK for the transport block. Network entity 105-c may correctly receive the NACK. In some examples, network entity 105-c may incorrectly receive the HARQ feedback as uncertain or DTX and treat the feedback as a NACK. At 360, network entity 105-c may send a DCI scheduling the retransmission of a transport block for which NDI has not been switched. At 365, network entity 105-c may retransmit (e.g., in a second PDSCH transmission) the transport block. Because the transport block was not successfully received by UE 115-c, UE 115-b retains the retransmitted transport block (information received in the second PDSCH transmission) and performs additional decoding (e.g., combining information from the first and second PDSCH transmissions). At 370, UE 115-c may send a HARQ feedback message indicating an ACK for the retransmitted transport block (e.g., if the second decoding was successful).

[0068] Figure 4An example of a process flow 400 supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, is shown. In some examples, process flow 400 may be implemented as described in reference respectively. Figure 1 and Figure 2 The aspects of the wireless communication systems 100 and 200 described herein, or as referred to respectively, Figure 1 and Figure 2 The described wireless communication systems 100 and 200 are implemented in various aspects. For example, process flow 400 can be implemented by network entities (e.g., network entity 105-d, network entity 105-e, and network entity 105-f), which can be as described in the reference. Figure 1 and Figure 2 An example of network entity 105 is described. Process flow 400 can be implemented by a UE (e.g., UE 115-d, UE 115-e, and UE 115-f), which can be as described in the reference. Figure 1 and Figure 2 An example of a UE as described.

[0069] In some examples, when network entity 105-d receives an indeterminate HARQ feedback, network entity 105-d may send a DCI including a pre-feedback indication. The pre-feedback indication may request another feedback message before receiving a retransmission of a transport block. For example, when the HARQ feedback message is received as indeterminate or DTX, network entity 105-d may send a DCI for retransmission of the PDSCH for scheduling the transport block, and the DCI may indicate a pre-feedback request. UE 115-d may receive the retransmission DCI indicating a pre-feedback request, and UE 115-d may send the pre-feedback message as an ACK based on the fact that the corresponding scheduled transport block sent via the PDSCH has been correctly received. In some cases, UE 115-d may receive a retransmission DCI indicating that pre-feedback is not required, such as when network entity 105-d receives HARQ feedback as a NACK, and UE 115-d may not provide a pre-feedback message.

[0070] Process flow 402 illustrates an example of retransmitting an indeterminate ACK for a transport block without waste. At 404, network entity 105-d can send a DCI indicating the scheduling of PDSCH transmission. At 406, network entity 105-d can send the transport block sent by PDSCH. The UE can successfully decode the transport block. At 408, UE 115-d can send a HARQ feedback message indicating an ACK for the transport block. Network entity 105-d may (e.g., incorrectly) receive the ACK as DTX or indeterminate. At 410, network entity 105-d can send a DCI indicating a retransmission of the transport block (e.g., where NDI has not been switched). The DCI may include a pre-feedback indication. At 412, UE 115-d sends a pre-feedback message indicating an ACK for the transport block. Network entity 105-d can correctly receive the ACK pre-feedback message. At 414, network entity 105-d can avoid performing a retransmission of the transport block. At 414, UE 115-d can assume that no PDSCH is sent (although this was indicated in the previous scheduling DCI). At 416, UE 115-d can omit the sending of the HARQ feedback message (e.g., the sending in the resource associated with the HARQ feedback message can be omitted) because the transport block is not retransmitted.

[0071] Process flow 420 illustrates an example of a wasted retransmission of an uncertain ACK for a transport block. At 422, network entity 105-e may send a DCI scheduling PDSCH transmission. At 424, network entity 105-e may send a PDSCH transmission including the transport block. The UE may successfully decode the transport block. At 426, UE 115-e may send a HARQ feedback message indicating an ACK for the transport block. Network entity 105-e may incorrectly receive the ACK as DTX or uncertain. At 428, network entity 105-e may send a DCI scheduling a retransmission of a transport block for which NDI has not been switched, and the DCI may include a pre-feedback indication. At 430, UE 115-e may send a pre-feedback message indicating an ACK for the transport block. Network entity 105-e may (e.g., incorrectly) receive the ACK pre-feedback message as uncertain. At 432, network entity 105-e may send a second PDSCH transmission associated with the transport block (e.g., retransmission of the transport block). At 434, UE 115-e may send a HARQ feedback message indicating an ACK for the retransmitted transport block. Network entity 105-e may successfully receive the ACK from UE 115-e at 434 and terminate communication for the transport block (e.g., continue to subsequent transport blocks for the HARQ procedure).

[0072] Process flow 440 illustrates an example where UE 115-f does not send HARQ feedback after receiving the first transmission of a transport block. For example, at 442, network entity 105-f may send a DCI that schedules the PDSCH transmission (the first transmission of a transport block where NDI is switched), and UE 115-f may falsely detect the DCI that schedules the PDSCH transmission. In some cases, false detection of DCI by UE 115-f may occur in approximately one percent of DCI transmissions. At 444, network entity 105-f may send a PDSCH transmission including the transport block. UE 115-f may be unaware of the PDSCH transmission due to the false detection of the DCI, and therefore may not accept the transport block or attempt to decode the transport block. At 446, UE 115-f does not send the HARQ feedback message associated with the transport block, and network entity 105-e can correctly detect DTX. At 448, network entity 105-f may send a DCI scheduling a second PDSCH transmission (e.g., retransmission of the transport block) associated with a transport block in which NDI has not been switched, and the DCI may include a pre-feedback indication. UE 115-f may successfully detect the DCI sent at 448. At 450, UE 115-f may send a pre-feedback message indicating a NACK for the transport block. Network entity 105-f may correctly receive the NACK pre-feedback message, or may incorrectly detect the NACK as an uncertainty or DTX. At 452, network entity 105-f may retransmit the transport block. UE 115-f may receive the transport block and successfully decode it. At 454, UE 115-f may send a HARQ feedback message indicating either an ACK for successful reception of the retransmitted transport block or a NACK for unsuccessful reception of the retransmitted transport block. In some cases, for the second DCI (e.g., the DCI at 448), although network entity 105-f indicates that the NDI is not for a retransmission handover, UE 115-f may interpret the NDI as a handover (e.g., indicating a new transmission of a transport block) because the first DCI (e.g., the DCI at 442) was falsely detected. In some examples, the new transmission DCI (e.g., the DCI at 442) may indicate a pre-feedback indication.

[0073] In some examples, the probability of PDSCH dropping (e.g., UE 115-f correctly receiving a transport block that was subsequently retransmitted and dropped) can be approximately 15 percent or more of the PDSCH transmissions. Utilizing a DCI that indicates pre-feedback can improve resource efficiency. For example, assuming the probability of ACK versus uncertainty or DTX is approximately 15 percent, providing a DCI that indicates pre-feedback can reduce wasted PDSCH retransmissions to approximately 2.25% (e.g., 15%). 2Providing a pre-feedback indication in DCI can save approximately 85% (e.g., 15% of the other 12.75%) of wasted PDSCH retransmissions.

[0074] As illustrated in process flow 440, the DCI scheduled for PDSCH transmission can support a pre-feedback indication, regardless of whether the DCI is associated with a new transmission of a transport block or a retransmission of a transport block. For example, UE 115-a can receive a DCI that includes a pre-feedback indication, and the DCI may include a handover NDI (from UE 115-a's perspective, although from network entity 105-a's perspective, it is an unhandover NDI). Since the DCI includes an NDI indicating a handover of a new transport block that UE 115-a has not yet successfully decoded, UE 115-a can send a HARQ feedback message indicating NACK in the resources used for pre-feedback.

[0075] In some examples, a pre-feedback indication may be indicated in the DCI associated with a retransmission of a transport block, and it may not be indicated in the DCI associated with a new transmission of a transport block. For example, a DCI that includes a pre-feedback indication may include an unswitched NDI.

[0076] In some examples, the DCI including the prefeedback indication may include new dedicated fields, such as a single bit, for indicating the prefeedback indication. In some cases, the prefeedback indication may be based on a reinterpretation of existing DCI fields. For example, for a prefeedback indication indicated in a DCI associated with a retransmission of a transport block, the reinterpretation may be based on a combination of an unswitched NDI (e.g., retransmission) and one or more other DCI fields.

[0077] In some examples, network entity 105-a may provide a pre-feedback indication in the DCI based on the detection of an indeterminacy or DTX corresponding to a HARQ feedback message. When a NACK is received for a HARQ feedback message, network entity 105-a may not instruct UE 115-a to perform pre-feedback (e.g., the DCI scheduled for retransmission may not include a pre-feedback indication), because pre-feedback would increase the latency for a correct NACK.

[0078] In some examples, network entity 105-a can use RRC signaling to configure UE 115-a to indicate whether the PDSCH scheduling DCI includes or excludes a pre-feedback indication. In some cases, network entity 105-a can update the configuration via a MAC control element (CE). For example, network entity 105-a can configure a new DCI field indicating a pre-feedback indication in RRC signaling or MAC-CE. In some cases, UE 115-a can request the configuration for pre-feedback via RRC signaling or MAC-CE. For example, UE 115-a can identify that the PDSCH transmission drop rate meets a threshold (e.g., exceeds the threshold, reaches or exceeds the threshold), and UE 115-a can initiate dynamic control signaling (such as via uplink control information, MAC-CE, or semi-statically via RRC signaling) to request the pre-feedback configuration. In some cases, the threshold PDSCH drop rate can be predetermined (e.g., a 10% drop rate threshold) or can be configured by network entity 105-a. For example, network entity 105-a can send control signaling indicating the configuration associated with the pre-feedback indication, and UE 115-a can receive control signaling indicating the configuration associated with the pre-feedback indication.

[0079] In some examples, network entity 105-a may indicate uplink resources used for two-phase feedback. For instance, in a DCI message scheduling PDSCH, network entity 105-a may indicate two PUCCH resources, one for pre-feedback and one for HARQ feedback. The resources may be two corresponding indicators, such as a PUCCH resource indicator (PRI) and / or a slot offset. In some cases, the two resources may be shared indicators, such as PRI and / or slot offset, and the indicators may be applied differently to the reference slot (e.g., the slot offset of the DCI slot for pre-feedback and the slot offset of the PDSCH slot for HARQ feedback). In some cases, PUCCH resources for second-phase HARQ feedback may be indicated in the scheduled PDSCH. The DCI may rate-match with transport blocks (DL-SCH) on the PDSCH. In some cases, the DCI may puncture transport block (DL-SCH) resource elements on the PDSCH. Punching or rate matching can be based on whether the DCI size is less than a threshold (e.g., a 2-bit threshold, where 1 or 2 bits are used for punching and more than 2 bits are used for rate matching).

[0080] In some examples, out-of-order PDSCH to HARQ feedback from any two different HARQ processes may not be allowed, and out-of-order PDCCH to PDSCH from any two different HARQ processes may not be allowed. For example, UE 115-a may not expect out-of-order PDSCH to PDSCH in time slots. iThe first PDSCH is received, and the corresponding HARQ-ACK is assigned to the time slot. j The system sends and receives a second PDSCH that starts later than the first PDSCH, where the corresponding HARQ-ACK is assigned to be sent in the time slot. j Transmitted in the previous time slot. If UE 115-a is scheduled to transmit via symbol i The PDCCH ends in the middle to begin receiving at the symbol. j If the first PDSCH starts in the middle, then UE 115-a is not expected to be scheduled to receive a PDSCH that starts earlier than the end of the first PDSCH, where the PDCCH is longer than the symbol. i Late end. In some examples, out-of-order PDCCH to prefeedback from any two different HARQ procedures may not be allowed. For example, UE115-a may not expect in time slots i The first PDSCH is received in the time slot, where the corresponding pre-feedback is assigned to the time slot. j The second PDSCH is sent in the middle, and the second PDSCH starts later than the first PDSCH, wherein its corresponding prefeedback is assigned to be sent in the time slot. j Sending in the previous time slot. In some examples, if there is pre-feedback between at least one of two different HARQ processes in their corresponding PDCCH and (virtual) PDSCH, out-of-order PDCCH to (virtual) PDSCH from these two different HARQ processes may not be allowed, regardless of whether the PDSCH is actually sent. The virtual PDSCH may correspond to a scheduled PDSCH that has not been sent.

[0081] Figure 5 An example of a process flow 500 supporting enhanced pre-feedback for retransmission of hybrid automatic repeating requests, according to one or more aspects of this disclosure, is shown. In some examples, process flow 500 may be implemented as described in reference respectively. Figure 1 and Figure 2 The aspects of the wireless communication systems 100 and 200 described herein, or as referred to respectively, Figure 1 and Figure 2 The described wireless communication systems 100 and 200 are implemented in various aspects. For example, process flow 500 can be implemented by network entity 105-g, which can be as described in the reference. Figure 1 and Figure 2 An example of network entity 105 as described. Process flow 500 can be implemented by UE 115-g, which can be as shown in the reference. Figure 1 and Figure 2 An example of a UE as described.

[0082] In some examples, the operations illustrated in process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software executed by a processor), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0083] At position 505, UE 115-g can receive the first transport block sent by the first PDSCH. UE 115-g can successfully decode the first transport block.

[0084] At 510, UE 115-g can send a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block.

[0085] At 515, UE 115-g may receive a first DCI including a pre-feedback indication after sending a first feedback message. The pre-feedback indication may request a second feedback message before receiving a retransmission of the first transport block. In some cases, the first DCI may include an unhandled NDI. In some examples, the first DCI may include a field indicating the pre-feedback indication.

[0086] At 520, UE 115-g can, in response to receiving the first DCI, send a second feedback message indicating an ACK for the first transport block.

[0087] At 525, UE 115-g can receive control signaling indicating the configuration associated with the pre-feedback indication.

[0088] At 530, UE 115-g can send control signaling requesting configuration associated with a pre-feedback indication. The transmission of control signaling can be based at least in part on the PDSCH drop rate.

[0089] In some examples, UE 115-g may receive a second DCI that schedules the first transport block before receiving the first transport block. The second DCI may indicate a first PUCCH resource associated with the first feedback message and a second PUCCH resource associated with the second feedback message. In some examples, UE 115-g may receive a second DCI indicating the PUCCH resource associated with the second feedback message during PDSCH transmission. In some examples, the second DCI may be rate-matched with the first transport block. In some examples, the second DCI may puncture one or more resource elements associated with the first transport block.

[0090] In some examples, UE 115-g may receive a second DCI that includes a pre-feedback indication. The second DCI may include an NDI indicating a handover associated with a second transport block that has not yet been successfully received by the UE, and the UE may send a first NACK feedback message indicating unsuccessful reception of the second transport block in response to receiving the second DCI that includes the handover NDI.

[0091] Figure 6 A block diagram 600 is shown of a device 605 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0092] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with pre-feedback enhancements for hybrid automatic repeat request retransmission). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0093] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with pre-feedback enhancements for hybrid automatic repeat request retransmission). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0094] The communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be examples of components used to perform various aspects of enhanced pre-feedback for hybrid automatic repeat request retransmission as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0095] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0096] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0097] In some examples, the communication manager 620 may be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0098] Communication manager 620 may support wireless communication according to examples disclosed herein. For example, communication manager 620 may be capable of, configured to, or operable to support components for receiving a first transport block transmitted by a first PDSCH. Communication manager 620 may be capable of, configured to, or operable to support components for transmitting a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. Communication manager 620 may be capable of, configured to, or operable to support components for receiving first downlink control information including a pre-feedback indication after transmitting the first feedback message, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. Communication manager 620 may be capable of, configured to, or operable to support components for transmitting a second feedback message indicating an ACK for the first transport block in response to receiving the first downlink control information.

[0099] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0100] Figure 7 A block diagram 700 is shown of a device 705 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0101] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with pre-feedback enhancements for hybrid automatic repeat request retransmission). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0102] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with pre-feedback enhancements for hybrid automatic repeat request retransmission). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0103] Device 705 or its various components may be examples of parts for performing various aspects of enhanced pre-feedback for hybrid automatic repeat request retransmission as described herein. For example, communication manager 720 may include transport block manager 725, feedback manager 730, pre-feedback indication manager 735, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0104] Communication manager 720 can support wireless communication according to the examples disclosed herein. Transport block manager 725 is capable of, configured to, or operable to support components for receiving a first transport block transmitted via a first PDSCH. Feedback manager 730 is capable of, configured to, or operable to support components for transmitting a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. Pre-feedback indication manager 735 is capable of, configured to, or operable to support components for receiving first downlink control information including a pre-feedback indication after transmitting the first feedback message, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. Feedback manager 730 is capable of, configured to, or operable to support components for transmitting a second feedback message indicating an ACK for the first transport block in response to receiving the first downlink control information.

[0105] Figure 8A block diagram 800 is shown of a communication manager 820 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission according to one or more aspects of this disclosure. Communication manager 820 may be an example of aspects of communication manager 620, communication manager 720, or both as described herein. Communication manager 820 or its various components may be examples of parts for performing the various aspects of enhanced pre-feedback for hybrid automatic repeat request retransmission as described herein. For example, communication manager 820 may include transport block manager 825, feedback manager 830, pre-feedback indication manager 835, configuration manager 840, PUCCH resource manager 845, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0106] Communication manager 820 can support wireless communication according to examples disclosed herein. Transport block manager 825 is capable of, configured to, or operable to support components for receiving a first transport block transmitted via a first PDSCH. Feedback manager 830 is capable of, configured to, or operable to support components for transmitting a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. Pre-feedback indication manager 835 is capable of, configured to, or operable to support components for receiving first downlink control information including a pre-feedback indication after transmitting the first feedback message, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. In some examples, feedback manager 830 is capable of, configured to, or operable to support components for transmitting a second feedback message indicating an ACK for the first transport block in response to receiving the first downlink control information.

[0107] In some examples, the first downlink control information includes a New Data Indicator (NDI) that has not been switched over.

[0108] In some examples, the first downlink control information includes a field indicating a pre-feedback indication.

[0109] In some examples, the transport block manager 825 is capable of, configured to, or operable to support components for receiving second downlink control information including a pre-feedback indication, wherein the second downlink control information includes a New Data Indicator (NDI) indicating that the second downlink control information is associated with a second transport block that has not yet been successfully received by the UE. In some examples, the feedback manager 830 is capable of, configured to, or operable to support components for sending a first NACK feedback message indicating unsuccessful reception of the second transport block in response to receiving second downlink control information including a handover NDI.

[0110] In some examples, the configuration manager 840 is capable of, configured to, or able to operate to support components for receiving control signaling that indicates a configuration associated with a pre-feedback indication.

[0111] In some examples, the configuration manager 840 is capable of, configured to, or able to operate to support components for sending control signaling for configurations associated with requests and pre-feedback indications, wherein the sending of control signaling is based on the PDSCH drop rate.

[0112] In some examples, the PUCCH resource manager 845 is capable of, configured to, or able to operate to support components for receiving second downlink control information for scheduling the first transport block before the first transport block is received, wherein the second downlink control information indicates a first PUCCH resource associated with a first feedback message and a second PUCCH resource associated with a second feedback message.

[0113] In some examples, the PUCCH resource manager 845 is capable of, configured to, or able to operate to support components for receiving second downlink control information in PDSCH transmission that indicates a PUCCH resource associated with a second feedback message.

[0114] In some examples, the second downlink control information is rate-matched with the first transport block.

[0115] In some examples, the second downlink control information punches one or more resource elements associated with the first transport block.

[0116] Figure 9 A diagram of a system 900 including device 905 supporting enhanced pre-feedback for hybrid automatic repeat request retransmission, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may (e.g., wirelessly) communicate with one or more other devices (e.g., network entity 105, UE 115, or any combination thereof). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller (e.g., I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0117] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0118] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 using a wired or wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0119] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable code, computer-executable code, or processor-executable code, such as code 935. Code 935 may include instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 930 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0120] At least one processor 940 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks that support enhanced pre-feedback for retransmission of hybrid automatic repetitive requests). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, the at least one processor 940 and the at least one memory 930 being configured to perform the various functions described herein.

[0121] In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.

[0122] Communication manager 920 may support wireless communication according to examples disclosed herein. For example, communication manager 920 may be capable of, configured to, or operable to support components for receiving a first transport block transmitted by a first PDSCH. Communication manager 920 may be capable of, configured to, or operable to support components for transmitting a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. Communication manager 920 may be capable of, configured to, or operable to support components for receiving first downlink control information including a pre-feedback indication after transmitting the first feedback message, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. Communication manager 920 may be capable of, configured to, or operable to support components for transmitting a second feedback message indicating an ACK for the first transport block in response to receiving the first downlink control information.

[0123] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving communication reliability, utilizing communication resources more efficiently, and improving coordination between devices.

[0124] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported by or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of the pre-feedback enhancement for hybrid automatic repeat request retransmission as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0125] Figure 10 A flowchart illustrating a method 1000 for enhanced pre-feedback retransmission of hybrid automatic repeat requests, according to one or more aspects of this disclosure, is shown. Operation of method 1000 may be implemented by a UE or its components as described herein. For example, operation of method 1000 may be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0126] At point 1005, the method may include receiving a first transport block transmitted by a first PDSCH. The operation at point 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at point 1005 may be derived from references... Figure 8 The described transport block manager 825 is used to perform this.

[0127] At 1010, the method may include sending a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. The operation of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be derived from references... Figure 8 The feedback manager 830 described is used to execute this.

[0128] At 1015, the method may include, after sending the first feedback message, receiving first downlink control information including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. The operation of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1015 may be derived from references... Figure 8 The pre-feedback instruction manager 835 is described and executed accordingly.

[0129] At 1020, the method may include sending a second feedback message indicating an ACK for the first transport block in response to receiving first downlink control information. The operation of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1020 may be derived from references... Figure 8 The feedback manager 830 described is used to execute this.

[0130] Figure 11 A flowchart illustrating a method 1100 for enhanced pre-feedback retransmission of hybrid automatic repeat requests, according to one or more aspects of this disclosure, is shown. Operation of method 1100 may be implemented by a UE or its components as described herein. For example, operation of method 1100 may be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0131] At 1105, the method may include receiving a first transport block transmitted by a first PDSCH. The operation of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1105 may be derived from references... Figure 8 The described transport block manager 825 is used to perform this.

[0132] At 1110, the method may include sending a first feedback message indicating an ACK for the first transport block in response to receiving the first transport block. The operation of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be derived from references... Figure 8 The feedback manager 830 described is used to execute this.

[0133] At 1115, the method may include, after sending the first feedback message, receiving first downlink control information including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block. The operation of 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1115 may be derived from references... Figure 8 The pre-feedback instruction manager 835 is described and executed accordingly.

[0134] At 1120, the method may include sending a second feedback message indicating an ACK for the first transport block in response to receiving first downlink control information. The operation of 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1120 may be derived from references... Figure 8 The feedback manager 830 described is used to execute this.

[0135] At 1125, the method may include receiving control signaling indicating a configuration associated with a pre-feedback indication. The operation of 1125 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1125 may be provided by reference to [reference needed]. Figure 8 The configuration manager 840 described is executed.

[0136] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving a first transport block transmitted by a first PDSCH; in response to receiving the first transport block, transmitting a first feedback message indicating an ACK for the first transport block; after transmitting the first feedback message, receiving first downlink control information including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and in response to receiving the first downlink control information, transmitting a second feedback message indicating an ACK for the first transport block.

[0137] Aspect 2: According to the method of aspect 1, the first downlink control information includes unswitched NDI.

[0138] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the first downlink control information includes a field indicating the prefeedback indication.

[0139] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: receiving second downlink control information including the pre-feedback indication, wherein the second downlink control information includes a handover NDI, the handover NDI indicating that the second downlink control information is associated with a second transport block that has not yet been successfully received by the UE; and in response to receiving the second downlink control information including the handover NDI, sending a first NACK feedback message indicating unsuccessful reception of the second transport block.

[0140] Aspect 5: The method according to any one of aspects 1 to 4, the method further comprising: receiving control signaling indicating a configuration associated with the pre-feedback indication.

[0141] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: sending control signaling requesting a configuration associated with the pre-feedback indication, wherein sending the control signaling is at least partially based on the PDSCH drop rate.

[0142] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving, before receiving the first transport block, second downlink control information for scheduling the first transport block, wherein the second downlink control information indicates a first PUCCH resource associated with the first feedback message and a second PUCCH resource associated with the second feedback message.

[0143] Aspect 8: The method according to any one of Aspects 1 to 6, the method further comprising: receiving, during the PDSCH transmission, second downlink control information indicating a PUCCH resource associated with the second feedback message.

[0144] Aspect 9: According to the method of aspect 8, wherein the second downlink control information is rate-matched with the first transport block.

[0145] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the second downlink control information punches one or more resource elements associated with the first transport block.

[0146] Aspect 11: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 10.

[0147] Aspect 12: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 10.

[0148] Aspect 13: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of Aspects 1 to 10.

[0149] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0150] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0151] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0152] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0153] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0154] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0155] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0156] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0157] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0158] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0159] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0160] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive the first transport block transmitted via the first physical downlink shared channel (PDSCH); In response to receiving the first transport block, a first feedback message indicating an acknowledgment (ACK) of the first transport block is sent; After sending the first feedback message, first downlink control information including a pre-feedback indication is received, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; as well as In response to receiving the first downlink control information, a second feedback message indicating an ACK for the first transport block is sent.

2. The UE according to claim 1, wherein the first downlink control information includes a new data indicator (NDI) that has not been handed over.

3. The UE according to claim 1, wherein the first downlink control information includes a field indicating the prefeedback indication.

4. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive second downlink control information including the pre-feedback indication, wherein the second downlink control information includes a New Data Indicator (NDI) for handover, the NDI indicating that the second downlink control information is associated with a second transport block that has not yet been successfully received by the UE; and In response to receiving the second downlink control information including the switched NDI, a first negative acknowledgment (NACK) feedback message indicating unsuccessful reception of the second transport block is sent.

5. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive control signaling that indicates the configuration associated with the pre-feedback indication.

6. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Send control signaling for the configuration associated with the pre-feedback indication, wherein the sending of the control signaling is based at least in part on the PDSCH drop rate.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Before receiving the first transport block, second downlink control information for scheduling the first transport block is received, wherein the second downlink control information indicates a first physical uplink control channel (PUCCH) resource associated with the first feedback message and a second PUCCH resource associated with the second feedback message.

8. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: During the PDSCH transmission, second downlink control information indicating the PUCCH resources associated with the second feedback message is received.

9. The UE according to claim 8, wherein the second downlink control information is rate-matched with the first transport block.

10. The UE of claim 8, wherein the second downlink control information punctures one or more resource elements associated with the first transport block.

11. A method for wireless communication by a user equipment (UE), the method comprising: Receive the first transport block transmitted via the first physical downlink shared channel (PDSCH); In response to receiving the first transport block, a first feedback message indicating an acknowledgment (ACK) of the first transport block is sent; After sending the first feedback message, first downlink control information including a pre-feedback indication is received, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; as well as In response to receiving the first downlink control information, a second feedback message indicating an ACK for the first transport block is sent.

12. The method of claim 11, wherein the first downlink control information includes a new data indicator (NDI) that has not been switched.

13. The method of claim 11, wherein the first downlink control information includes a field indicating the prefeedback indication.

14. The method according to claim 11, further comprising: Receive second downlink control information including the pre-feedback indication, wherein the second downlink control information includes a New Data Indicator (NDI) for handover, the New Data Indicator (NDI) for handover indicating that the second downlink control information is associated with a second transport block that has not yet been successfully received by the UE; as well as In response to receiving the second downlink control information including the switched NDI, a first negative acknowledgment (NACK) feedback message indicating unsuccessful reception of the second transport block is sent.

15. The method according to claim 11, further comprising: Receive control signaling that indicates the configuration associated with the pre-feedback indication.

16. The method according to claim 11, further comprising: Send control signaling for the configuration associated with the pre-feedback indication, wherein the sending of the control signaling is based at least in part on the PDSCH drop rate.

17. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Receive the first transport block transmitted via the first physical downlink shared channel (PDSCH); In response to receiving the first transport block, a first feedback message indicating an acknowledgment (ACK) of the first transport block is sent; After sending the first feedback message, receive first downlink control information including a pre-feedback indication, wherein the pre-feedback indication requests a second feedback message before receiving a retransmission of the first transport block; and In response to receiving the first downlink control information, a second feedback message indicating an ACK for the first transport block is sent.

18. The non-transitory computer-readable medium of claim 17, wherein the first downlink control information includes a new data indicator (NDI) that has not been switched.

19. The non-transitory computer-readable medium of claim 17, wherein the first downlink control information includes a field indicating the pre-feedback indication.

20. The non-transitory computer-readable medium of claim 17, wherein the instructions are further executable by the one or more processors to: Receive second downlink control information including the pre-feedback indication, wherein the second downlink control information includes a New Data Indicator (NDI) for handover, the NDI indicating that the second downlink control information is associated with a second transport block that has not yet been successfully received; and In response to receiving the second downlink control information including the switched NDI, a first negative acknowledgment (NACK) feedback message indicating unsuccessful reception of the second transport block is sent.