Resource allocation for repetition of non-acknowledgement feedback

Abstract

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a UE or a component thereof configured to transmit, to a network entity, feedback including an ACK or a NACK corresponding to a transmission from the network entity on a first set of resources. The feedback can be transmitted without repetition when the feedback includes the ACK corresponding to the transmission. The apparatus can be further configured to transmit, to the network entity, a repetition of the feedback on a second set of resources when the feedback includes the NACK corresponding to the transmission.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of Greek Patent Application No. 20200100645, entitled “On demand repetition in space / time / frequency for HARQ NACK,” filed October 23, 2020, the disclosure of which is hereby expressly incorporated by reference in its entirety. BACKGROUND TECHNICAL FIELD

[0004] The present disclosure relates generally to communication systems, and more specifically to scheduling and configuration of transmissions and repetitions for hybrid automatic repeat request (HARQ) feedback.

[0005] INTRODUCTION

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is a continuing

[0008] SUMMARY

[0009] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0010] In some radio access networks or other wireless networks, certain traffic can be expected to meet various conditions, e.g., as part of a use case conveying such traffic. In the context of some radio access technologies (RATs), such as 5G New Radio (NR), certain traffic can be expected to exhibit reliability and / or latency characteristics that do not violate respective thresholds. For example, traffic identified as Ultra-Reliable Low-Latency Communication (URLLC) or Industrial Internet of Things (IIoT) can be expected to meet an applicable error rate threshold, such as a threshold of 10 -5 Packet Error Probability or Packet Error Rate (PER)), while also meeting an applicable latency threshold, such as a threshold of 0.5 milliseconds (ms) or one (1) ms.

[0011] Certain RATs can use Hybrid Automatic Repeat Request (HARQ) acknowledgement (ACK) or non-ACK (NACK) feedback to enable error correction or error control. For example, a user equipment (UE) can be assigned particular uplink resources for reporting HARQ ACK / NACK feedback corresponding to a downlink packet, protocol data unit (PDU), etc., from a base station (or other network entity). However, in real-world deployments, the HARQ feedback mechanism cannot be expected to function perfectly all the time. Illustratively, a base station can mistakenly find a HARQ NACK feedback that was not intended for the base station, e.g., due to channel properties that cause the base station to erroneously interpret the HARQ resources as empty, or due to a decoding error that causes the base station to mistakenly find a HARQ ACK feedback.

[0012] HARQ feedback errors can cause latency and / or reliability to be impacted, which can negatively affect performance and user experience, and further can prevent certain traffic from meeting its expected applicable use case parameters, e.g., including not more than 10 -5reliability parameters (e.g., PER or packet error probability reliability parameters, latency parameters including packet transmission times of no more than 0.5 ms or one (1) ms). Moreover, performance degradation caused by one error interpretation of HARQ resources can be compounded or otherwise exacerbated while the error interpretation is propagated through the system, e.g., until the base station and UE are able to correct packet alignment, reacquire synchronization, etc. Thus, for example, in systems and networks in which latency, reliability, and / or other constraints are imposed on certain traffic, such as URLLC and IIoT, there is a need to improve reliability in conveying HARQ feedback.

[0013] The present disclosure describes various low-overhead mechanisms via which HARQ feedback errors can be avoided and / or corrected. In particular, the present disclosure provides various approaches and solutions designed to improve reliability in conveying HARQ feedback in a manner that does not increase latency beyond levels deemed acceptable by the applicable use cases. For example, various aspects described herein can improve reliability of HARQ feedback for URLLC and / or IIoT traffic, respectively, without exceeding URLLC and / or IIoT latency budgets. In some instances, as a complement or alternative to mitigating or preventing latency escalation and / or reliability degradation that can be compounded or propagated over time while the base station and UE resolve packet (or PDU) misalignment, synchronization errors, and / or other alignment disparities, the concepts and various aspects described herein can enable certain traffic to adhere to its intended use case parameters.

[0014] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a UE or a component thereof configured to transmit, to a network entity, feedback including an ACK or a NACK corresponding to a transmission from the network entity on a first set of resources. The feedback can be transmitted without repetition when the feedback includes the ACK corresponding to the transmission. The apparatus can be further configured to transmit, to the network entity, a repetition of the feedback on a second set of resources when the feedback includes the NACK corresponding to the transmission.

[0015] In another aspect of the disclosure, another method, another computer-readable medium, and another apparatus are provided. The other apparatus can be a network entity or a component thereof configured to decode feedback received from a UE on a first set of resources, where the feedback includes an ACK or a NACK corresponding to a transmission to the UE. The other apparatus can be further configured to decode a repetition of the feedback received from the UE on a second set of resources when the decoded feedback on the first set of resources includes the NACK corresponding to the transmission.

[0016] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects can be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF DRAWINGS

[0018] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0019] Figure 2A is a diagram illustrating an example of a first frame in accordance with various aspects of the present disclosure.

[0020] Figure 2B is a diagram illustrating an example of downlink channels within a subframe in accordance with various aspects of the present disclosure.

[0021] Figure 2C is a diagram illustrating an example of a second frame in accordance with various aspects of the present disclosure.

[0022] Figure 2D is a diagram illustrating an example of uplink channels within a subframe in accordance with various aspects of the present disclosure.

[0023] Figure 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0024] Figure 4 is a diagram illustrating an example implementation of error control and / or error correction using feedback from a UE to a base station.

[0025] Figure 5 is a diagram illustrating another example implementation of error control and / or error correction using acknowledgement (ACK) / non-ACK (NACK) feedback from a UE to a base station.

[0026] Figure 6 is a flow diagram of a method of wireless communication by a UE.

[0027] Figure 7 is a flow diagram of a method of wireless communication by a network entity.

[0028] Figure 8 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0029] Figure 9 is a diagram illustrating another example of a hardware implementation for another example apparatus.

[0030] DETAILED DESCRIPTION

[0031] The detailed description set forth below, in connection with the appended drawings and illustrations, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts and related aspects can be practiced without some or all of the specific details. In some instances, well-known structures, components, and so on have not been shown or described in excruciating detail in order to avoid unnecessarily obscuring the concepts.

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0033] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLD), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0034] Accordingly, in one or more example embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or encoded as one or more instructions or computer-readable code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that is capable of storing computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0035] In some radio access networks or other wireless networks, certain traffic can be expected to meet various conditions, e.g., as part of a use case that conveys such traffic. In the context of some radio access technologies (RATs), such as 5G New Radio (NR), certain traffic can be expected to exhibit reliability and / or latency characteristics that do not violate respective thresholds. For example, traffic identified as Ultra-Reliable Low-Latency Communication (URLLC) or Industrial Internet of Things (IIoT) can be expected to meet an applicable error rate threshold, such as a threshold of 10 -5 Packet Error Probability or Packet Error Rate (PER)), while also meeting an applicable latency threshold, such as a threshold of 0.5 milliseconds (ms) or one (1) ms.

[0036] Certain RATs can use Hybrid Automatic Repeat Request (HARQ) acknowledgement (ACK) or non-ACK (NACK) feedback (NACK can additionally or alternatively refer to “negative ACK”) to enable error correction or error control. For example, a user equipment (UE) can be assigned particular uplink resources for reporting HARQ ACK / NACK feedback corresponding to downlink packets, protocol data units (PDUs), etc., from a base station (or other network entity). However, in real-world deployments, the HARQ feedback mechanism cannot be expected to function perfectly all the time. Illustratively, a base station can mistakenly find a NACK feedback that is not intended for the base station, e.g., due to channel properties that cause the base station to erroneously interpret the HARQ resources as empty, or due to a decoding error that causes the base station to mistakenly find a HARQ ACK feedback.

[0037] In networks in which some or all traffic is carried in millimeter wave (mmW) or near mmW spectrum, reliability of the air interface and / or other wireless communication traffic can be a function of various factors, including environmental factors (e.g., blockers, reflectors, etc.), network characteristics, resource availability, etc. Such factors are inherently unpredictable in real-world deployments and will tend to change over relatively short periods of time. Thus, for example, communications over the air interface or other wireless communication interface between a base station (or other network entity) and a UE can benefit from low-overhead mechanisms designed to mitigate some of the adverse effects of those factors.

[0038] While beam and / or channel reciprocity can not always be relied upon for channel measurement and / or scheduling, a beam or channel being blocked in one direction can be indicative of the beam or channel being blocked in another direction. For example, a blocked downlink receive (RX) beam configured on a physical downlink shared channel (PDSCH) can indicate that an uplink transmit (TX) beam configured on a physical uplink control channel (PUCCH) is also blocked.

[0039] In certain instances, a base station (and / or other network entity) can expect HARQ ACK or NACK feedback on certain resources without finding that feedback. In cases where no ACK feedback is detected and no NACK feedback is detected on a HARQ resource (such as in cases where HARQ resource energy is below a threshold or in cases where the HARQ resource is not properly decoded), a discontinuous transmission (DTX) can be assumed. In some instances, the DTX can imply that the UE failed to receive the transmission and, thus, is not aware of the HARQ feedback expected for the transmission or the UE also does not respond with the HARQ feedback.

[0040] In some implementations, a base station can interpret a DTX on a HARQ resource as NACK feedback, which can prompt the base station to retransmit information corresponding to the HARQ resource without knowing the reason for the DTX. For example, the DTX on the HARQ resource can be due to a blocked beam or can be due to frequency-selective fading (e.g., in cases where the number of antennas at the UE is equal to the number of antennas used by the base station). In response to the HARQ resource DTX (e.g., interpreted as NACK feedback), the base station can select a new beam for transmission, but the new beam can experience the same failure as the previously used beam, which can again result in NACK feedback for the retransmitted information (e.g., as indicated by a DTX on the corresponding HARQ resource again).

[0041] In some other instances, the UE may transmit NACK feedback on HARQ resources, but the base station may erroneously detect ACK feedback on HARQ resources, for example, due to interference on the uplink channel, decoding errors, etc. In response to an erroneously detected ACK feedback, the base station may proceed to transmit the next part of the information (e.g., packets, Protocol Data Units (PDUs), segments, sections, etc.) while the UE is expecting a retransmission of the previous part of the information. As a result, coherent errors may occur on the channel (e.g., PDSCH) because the UE may also provide NACK feedback in response to unexpectedly receiving the next part of the information.

[0042] In the above and other examples, invalid and / or erroneously interpreted HARQ feedback can adversely affect throughput and / or reliability, for example, because latency and error rates may increase directly with such invalid and / or erroneously interpreted HARQ feedback. Therefore, there is a need to improve the reliability of HARQ feedback delivery.

[0043] This disclosure describes various low-overhead mechanisms by which HARQ feedback errors can be avoided and / or corrected. Specifically, this disclosure provides various methods and solutions designed to improve the reliability of HARQ feedback delivery in a manner that does not increase latency beyond what is considered acceptable for the applicable use case. For example, the aspects described herein can improve the reliability of HARQ feedback for URLLC and / or IIoT traffic, respectively, without exceeding the latency budget for URLLC and / or IIoT. In some instances, the concepts and aspects described herein can enable certain traffic to conform to their intended use case parameters as a supplement or alternative to mitigating or preventing escalation of latency and / or reliability degradation that may occur over time as the base station and UE resolve packet (or PDU) mismatches, synchronization errors, and / or other alignment differences.

[0044] In some aspects of this disclosure, various methods and solutions are implemented by repeating the NACK after the initial transmission of HARQ feedback. For example, in addition to resources configured on the uplink control channel (e.g., PUCCH) to carry the initial HARQ ACK / NACK transmission for the corresponding transmission scheduled on the downlink data channel (e.g., PDSCH), at least one other resource may be configured to carry at least one repetition of HARQ feedback. However, in some aspects, the repetition of HARQ feedback may be transmitted when indicating NACK, but may not be transmitted when indicating ACK. In some other aspects, the repetition of HARQ feedback may be selectively transmitted, rather than always transmitted with every HARQ feedback transmission.

[0045] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0046] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation Radio Access Network (RAN) (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptographic decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages.

[0047] In some respects, base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184, and third backhaul link 134 can be wired, wireless, or a combination thereof. At least some base stations 102 can be configured for Integrated Access and Backhaul (IAB). Accordingly, such base stations can communicate wirelessly with other base stations (and can also be configured for IAB).

[0048] At least some of the base stations 102 configured for IAB may have a split architecture, including at least one of a central unit (CU), a distributed unit (DU), a radio unit (RU), a remote radio headend (RRH), and / or a remote unit, some or all of which may be co-located or distributed, and / or able to communicate with each other. In some configurations of such a split architecture, the CU may implement some or all of the functionality of the Radio Resource Control (RRC) layer, while the DU may implement some or all of the functionality of the Radio Link Control (RLC) layer.

[0049] Explained, some base stations 102 configured for IAB can communicate with the DU of an IAB donor node or other parent IAB node (e.g., a base station) via a corresponding CU, and further, can communicate with child IAB nodes (e.g., other base stations) and / or one or more UEs 104 via a corresponding DU. One or more base stations 102 configured for IAB can be IAB donors connected via a CU to at least one of EPC 160 and / or core network 190. Through such links to EPC 160 and / or core network 190, a base station 102 operating as an IAB donor can provide links to EPC 160 and / or core network 190 to one or more UEs and / or other IAB nodes, which can be directly or indirectly connected to the IAB donor (e.g., separated from the IAB donor by more than one hop). In the context of communicating with EPC 160 or core network 190, both the UE and the IAB node can communicate with the DU of the IAB donor. In some additional aspects, one or more base stations 102 may be configured with connectivity in an Open RAN (ORAN) and / or a Virtualized RAN (VRAN), which can be achieved through at least one corresponding CU, DU, RU, RRH and / or remote unit.

[0050] Base station 102 can wirelessly communicate with UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0051] Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110 (which may also be referred to as a "cell"). Potentially, two or more geographic coverage areas 110 may at least partially overlap, or one geographic coverage area 110 may contain another geographic coverage area. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0052] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The radio link may be on one or more carriers or component carriers (CCs). For each carrier allocated in a total of up to Y x MHz (e.g., x CCs) of carriers used for transmission in each direction, base station 102 and / or UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., Y may be equal to or approximately equal to 5, 10, 15, 20, 100, 400, etc.). These CCs may or may not be adjacent to each other. The allocation of CCs may be asymmetric with respect to the downlink and uplink (e.g., more or fewer CCs may be allocated to the downlink compared to the uplink).

[0053] A carrier cluster (CC) may include a primary CC and one or more secondary CCs. The primary CC may be referred to as the primary cell (PCell), and each secondary CC may be referred to as a secondary cell (SCell). A PCell may also be referred to as the "serving cell" when the UE is known to both a base station at the access network level and at least one core network entity (e.g., AMF and / or MME) at the core network level, and the UE can be configured to receive downlink control information in that access network (e.g., the UE may be in an RRC connected state). In some instances where carrier aggregation is configured for the UE, each of the PCell and one or more SCells may be the serving cell.

[0054] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use downlink / uplink WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0055] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0056] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.

[0057] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes arise regarding FR2, although it differs from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” (mmW) band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as “millimeter wave” (or “mmWave” or simply “mmW”) in various documents and articles.

[0058] In light of the foregoing, unless otherwise stated, for the purposes of this document, the terms "sub-6GHz," "sub-7GHz," etc., may broadly refer to frequencies less than 6GHz, frequencies less than 7GHz, frequencies within FR1, and / or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise stated, for the purposes of this document, the term "millimeter wave" and other similar references may broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, and / or frequencies within the EHF band.

[0059] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations 180 (such as gNBs) may operate in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When such base stations 180 (e.g., gNBs) operate at mmW or near-mmW frequencies, base station 180 may be referred to as an mmW base station. (mmW) base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0060] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. One or both of base station 180 and / or UE 104 may perform beamforming to determine the optimal reception and / or transmission directions for one or both of base station 180 and / or UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.

[0061] In various respects, one or more of the base stations 102 / 180 may include and / or be referred to as gNB, B-node, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit and receive point (TRP), or some other suitable term.

[0062] In some respects, one or more of base stations 102 / 180 may be connected to EPC 160 and may provide one or more of UEs 104 with a corresponding access point to EPC 160. EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UEs 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming service, and / or other IP services. BM-SC 170 provides functionality for MBMS user service provisioning and delivery. BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within the Public Land Mobile Network (PLMN), and schedule MBMS transmissions. MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0063] In some other aspects, one or more of base stations 102 / 180 may be connected to the core network 190 and may provide one or more of the UEs 104 with a corresponding access point to the core network 190. The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between the UE 104 and the core network 190. Generally, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are delivered via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP service 197. IP service 197 may include the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0064] In some aspects, UE 104 may be configured to transmit feedback to base station 102 / 180 on a first resource set, including an ACK or NACK corresponding to a transmission from base station 102 / 180. In some aspects, when the feedback includes an ACK corresponding to the transmission, the feedback may be transmitted without duplication. UE 104 may be further configured to transmit a duplication of the feedback to base station 102 / 180 on a second resource set when the feedback includes a NACK corresponding to the transmission (198).

[0065] Accordingly, base station 102 / 180 may be configured to decode feedback received from UE 104 on a first resource set, wherein the feedback includes an ACK or NACK corresponding to a transmission destined for UE 104. Base station 102 / 180 may be further configured to decode a repetition (198) of feedback received from UE 104 on a second resource set when the feedback decoded on the first resource set includes a NACK corresponding to the transmission. However, base station 102 / 180 may suppress the decoding of information on the second resource set when the feedback decoded on the first resource set includes an ACK corresponding to the transmission.

[0066] While this disclosure may focus on 5G NR, the concepts and aspects described herein are applicable to other similar fields, such as LTE, LTE-A Advanced, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.

[0067] Figure 2A This is a diagram 200 illustrating an example of the first subframe within the 5G NR frame structure. Figure 2B Figure 230 is an example illustrating the downlink channel within a 5G NR subframe. Figure 2C This is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of an uplink channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either downlink or uplink; or it can be Time Division Duplex (TDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both downlink and uplink. Figure 2A , Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly downlink) and subframe 3 is configured with slot format 34 (mostly uplink), where D is downlink, U is uplink, and F is for flexible use between downlink and uplink. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all downlink and all uplink, respectively. Other slot formats 2-61 include downlink, uplink, and a mixture of flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via Downlink Control Information (DCI) or semi-statically / statically configured via RRC signaling). Note that the following description also applies to 5G NR frame structures for TDD.

[0068] Other wireless communication technologies may have different frame structures and / or different channels. A frame (e.g., a 10-millisecond (ms) frame) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the downlink may be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the uplink may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 symbols per subframe. μ Each time slot. The subcarrier spacing and symbol length / duration vary depending on the design parameters. The subcarrier spacing can be equal to 2. μ *15 kHz, where μ is the parameter design from 0 to 4. Thus, a parameter design μ = 0 has a subcarrier spacing of 15 kHz, while a parameter design μ = 4 has a subcarrier spacing of 240 kHz. Symbol length / duration is inversely correlated with subcarrier spacing. Figures 2A-2DExamples are provided for a slot configuration of 0 with 14 symbols per slot and a parameter design of μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs). Within the frame set, there may be one or more different bandwidth portions (BWPs) that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have specific parameter designs.

[0069] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) extending 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0070] like Figure 2A As explained, some REs carry at least one pilot signal for the UE, such as a reference signal (RS). Broadly speaking, RS can be used for beam training and management, tracking and localization, channel estimation, and / or other such purposes. In some configurations, RS may include at least one demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x (where 100x is the port number, but other DM-RS configurations are possible) and / or at least one Channel State Information (CSI) RS (CSI-RS). In some other configurations, the RS may additionally or alternatively include at least one Beam Measurement (or Management) RS (BRS), at least one Beam Refinement RS (BRRS), and / or at least one Phase Tracking RS (PT-RS).

[0071] Figure 2BExamples of various downlink channels within a frame's subframes are explained. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in OFDM symbols. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can be located at higher and / or lower frequencies spanning the channel bandwidth. The Primary Synchronization Signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The PDSCH carries user data, broadcast system information not transmitted via the PBCH (such as the System Information Block (SIB)), and paging messages.

[0072] As in Figure 2C As explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for PUCCH and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and on the specific PUCCH format used. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the uplink.

[0073] Figure 2DExamples of various uplink channels within a subframe of a frame are explained. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), which may include a scheduling request (SR), channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUCCH carries data and may additionally be used to carry buffer status report (BSR), power clearance report (PHR), and / or UCI.

[0074] Figure 3 This is a block diagram showing the communication between base station 310 and UE 350 in the access network. In the downlink, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 2 (L2) and Layer 3 (L3) functionality. L3 includes the RRC layer, and L2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, RLC layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs (PDUs may be additionally or alternatively referred to as "Packet Data Units"), error correction via ARQ, concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), and demultiplexing MACs from TBs. SDU, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation are associated with MAC layer functionality.

[0075] The TX processor 316 and RX processor 370 implement Layer 1 (L1) functionality associated with various signal processing functions. L1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate can be derived from reference signals and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0076] At UE 350, each receiver 354RX receives signals via at least one corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 356. The TX processor 368 and RX processor 356 implement L1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base station 310 on the physical channel. This data and control signals are then provided to controller / processor 359, which implements L3 and L2 functionality.

[0077] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the uplink, the controller / processor 359 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0078] Similar to the functionality described in conjunction with downlink transmissions performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0079] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0080] Uplink transmissions are handled at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via at least one corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0081] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the uplink, the controller / processor 375 provides demultiplexing, packet reassembly, cipher decoding, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0082] In some respects, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in combination with the following operations: transmitting at least one repetition (198) to the base station 310 corresponding to the transmission from the base station 310, as described above. Figure 1 As described.

[0083] In some other aspects, at least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in combination with the following operations: receiving at least one repetition (198) from the UE 350 of feedback corresponding to a transmission from the base station 310, as described above. Figure 1 As described.

[0084] Figure 4 This is a diagram 400 illustrating an example implementation of error control and / or error correction using feedback from UE 404 to base station 402. Figure 4 The explanation details the communication between base station 402 and UE 404 in access network 482. Figure 1 and Figure 3 In this context, UE 404 may be implemented as UE 104 and / or UE 350, base station 402 may be implemented as base station 102 / 180 and / or base station 310, and access network 428 may include one or more geographical coverage areas 110 / 110' (e.g., cellular and / or small cell) provided by one or more base stations (including coverage area 110 of base station 102 / 180). In one aspect of this disclosure, the communication link between base station 402 and UE 404 (e.g., Figure 1 The communication link 120 shown may use MIMO antenna technology and / or multi-user MIMO (MU-MIMO) technology, which may include spatial multiplexing, beamforming, time-division transmission (e.g., time-division multiple access (TDMA) technology) and / or transmit diversity.

[0085] In one aspect of this disclosure, when UE 404 registers with base station 402, one or more of UE 404 and base station 402 may determine which channels, antenna beams, spatial multiplexing schemes, etc., will be used as communication links between base station 402 and UE 404. In another aspect of this disclosure, in beamforming and / or beam diversity systems (i.e., forming antenna beams and subsequently switching to a second beam on the same and / or other channels and / or frequencies for communication), base station 402 and / or UE 404 may also determine alternative communication links on one or more alternative antenna beams. This determination may be based at least in part on signal-to-noise ratio (SNR) measurements for a given beam, signal-to-interference-plus-noise ratio (SINR) measurements for a given beam, signal-to-interference ratio (SIR) measurements for a given beam, reference signal received power (RSRP) measurements, reference signal received quality (RSRQ) measurements, and / or other factors.

[0086] In one aspect of this disclosure, the communication link between base station 402 and UE 404 may have a desired and / or required error rate. For example, but not as a limitation, a maximum bit error rate (BER) and / or packet error rate (PER) may be determined for a given communication link. The maximum BER and / or PER may be configured as an example of an URLLC link, an IIoT link, and / or another type of communication link expected to meet specific use case parameters. For such a communication link, the BER and / or PER level may be defined as one error per hundred thousand bits / packet (1x10^6). -5 One error per megabit / block (1x10) -6 )wait.

[0087] Base station 402 can send semi-persistent scheduling (SPS) messages to UE 404 on the PDSCH. SPS messages can be in the form of one or more packets. SPS messages can be sent to UE 404 via more than one antenna (e.g., in a MIMO system), and / or can be sent from base station 402 to UE 404 via more than one beam.

[0088] like Figure 4As shown, within loop 440, base station 402 may send SPS packet sequence number 0 (SN0) 420 to UE 404 on PDSCH beam 1 (B1) 410 (which may refer to the downlink TX beam of base station 402 paired with the downlink RX beam of UE 404). Simultaneously and / or subsequently, base station 402 may send SPS packet SN0 422 to UE 404 on PDSCH beam 2 (B2) 412. SPS packet SN0 420 and SPS packet SN0 422 may be equivalent, and the repetition of SPS packets SN0 420 and 422 can increase the reliability of communication between base station 402 and UE 404 because it provides UE 404 with multiple opportunities to find and decode the information carried in SPS packets SN0 420 and 422. The SPS configuration sent from base station 402 to UE 404 can indicate multiple grants, which respectively configure multiple resource allocations for repeated use of the initial NACK message.

[0089] Upon receiving and successfully decoding SPS packets SN0 420 and 422 from base station 402, UE 404 may send an ACK message 424 to base station 402 to indicate that UE 404 has received and successfully decoded SPS packets SN0 420 and 422 from base station 402 (e.g., at the MAC layer or other L2 layers implementing HARQ). The ACK message 424 may be transmitted on one or more time and / or frequency resources of the PUCCH. In one aspect of this disclosure, the ACK message 424 may be transmitted on the PUCCH via one of the beams used by base station 402 to deliver packets 420 and 422 to UE 404. For example, according to beam reciprocity, PUCCH B2 414 may correspond to PDSCHB2412, where PUCCH B2 414 refers to the uplink RX beam of base station 402 paired with the downlink TX beam of UE 404.

[0090] In some respects, the ACK message 424 may be sent after the last packets 420 and 422 sent in cycle 440. In another respect, the ACK message 424 may be sent on the PUCCH via the beam link on which the UE 404 receives one of the SPS packets SN0 420 and 422—for example, the UE 404 may transmit ACK 424 on PUCCH B2 414 based on beam reciprocity, according to the SPS packet SN0 received from base station 402 via PDSCH B2 412, as... Figure 4 As shown in the image.

[0091] When the reception / decoding of SPS packets SN0 420 and 422 is acknowledged by UE 404 via ACK message 424, base station 402 can again send SPS packet SN1 426 using PDSCH B1 410 and PDSCH B2 412. Because one of SPS packets SN0 420 and 422 is correctly received and acknowledged by UE 404, base station 402 "knows" that PDSCH B1 410 and / or PDSCH B2 412 are downlink communication links suitable for communicating with UE 404. For example, base station 402 also "knows" that PUCCH B2 414 is a communication link suitable for UE 404 because base station 402 receives ACK message 424 on PUCCH B2 414.

[0092] In the next cycle 442, since communication between base station 402 and UE 404 on PDSCH B1 410, PDSCH B2 412, and PUCCH B2 414 is applicable, base station 402 can continue to send the next SPS packet SN1 426 on PDSCH B1 420 and the next SPS packet SN1 428 on PDSCH B2 412. Base station 402 can "anticipate" that UE 404 will send an ACK message 430 on PUCCH B2 414. In some respects, the communication link established between base station 402 and UE 404 (i.e., PDSCH B1 410, PDSCH B2 412, and PUCCH B2 414) can be used as long as the SPS packets are correctly received and acknowledged by UE 404.

[0093] Potentially, ACK / NACK feedback can be suppressed from being transmitted by UE 404 and / or received by base station 402. Accordingly, (e.g., in URLLC and / or other applications) there is a need to improve the reliability of ACK / NACK feedback transmitted from UE to base station.

[0094] In the first example, interference and / or obstruction may occur, causing one or more parts of the communication link between base station 402 and UE 404 to be interrupted and / or degraded. For example, one or more parts of the downlink beam may be blocked and / or impeded due to obstacles (e.g., cars, people, buildings, UE 404 may have moved, etc.) to the extent that PDSCH B1 410 and / or PDSCH B2 412 can no longer adequately deliver information to UE 404.

[0095] In the second example, PUCCH B2 414 may also be blocked and / or interfered to the extent that ACK message 424 (and / or ACK message 430) is not properly received at base station 402. In such respect, base station 402 may interpret the failure to receive ACK messages 424 / 430 as UE 404 operating in a discontinuous transmission (DTX) mode that suppresses transmissions.

[0096] In the third example, signal fading (e.g., frequency-selective fading) can also interfere with the communication link between base station 402 and UE 404. In the case of uplink interference (e.g., on PUCCH B2 414), ACK messages 424 / 430 may be misread by base station 402 as NACK messages, thereby indicating to base station 402 that UE 404 has not yet received one or more SPS packets when UE 404 has actually received one or more SPS packets.

[0097] One or more of the aforementioned examples can be resolved through the various aspects described herein, such as combining Figures 5-9 The aspects described herein. Specifically, the aspects of this disclosure provide for improving the reliability of ACK / NACK feedback by retransmitting one or more retransmissions of the initial NACK message on a resource dedicated to NACK feedback.

[0098] Figure 5 Figure 500 illustrates another example implementation of error control and / or error correction using ACK / NACK feedback from UE 404 to base station 402. Figure 500 illustrates a communication protocol according to one aspect of this disclosure. (See reference...) Figure 4 As described, base station 402 transmits SPS packets SN0 420 and 422 during cycle 440. UE 404 acknowledges receipt of SPS packets SN0 420 and 422 via ACK message 424.

[0099] Between cycle 440 and cycle 442, interference 550 prevents SPS packets SN1 426, 428 from being received / decoded at UE 404. Interference 550 may be caused by interference, particularly to PDSCH B1 410 and / or PDSCH B2 412, slow fading of signals used for PDSCH B1 410 and / or PDSCH B2 412, physical obstacles between the antennas(s) of base station 402 and the antennas(s) of UE 404, and / or other reasons.

[0100] Because UE 404 did not receive / correctly decode SPS packets SN1 426, 428, UE 404 sends a NACK message 504 to base station 402. In some respects, UE 404 not only sends the NACK message 504 on PUCCH B2 414 (on which UE 404 sent ACK message 424 in cycle 440), UE 404 also sends the NACK message 504 via one or more other beamlinks (e.g., the uplink beamlink corresponding to B1 410, depending on beam reciprocity) to ensure that base station 402 receives the NACK message 504. For example, but not as a limitation, UE 404 may send the NACK message 504 on a PUCCH (such as PUCCH B1 510) via the uplink beamlink corresponding to PDSCH B1 410.

[0101] On the other hand, UE 404 may also send NACK message 504 on other beams to further ensure that base station 402 receives NACK message 504. Such PUCCH transmissions via other beams can be used for secondary communication, replacement communication, and / or emergency communication between base station 402 and UE 404, and can be determined earlier by UE 404 and base station 402, such as by using DCI and / or other means (e.g., a candidate beam list including other beams or replacement beams can be configured by base station 402 and / or UE 404). One or more beam links can be determined as secondary communication links and / or replacement communication links between UE 404 and base station 402. Such transmissions performed by UE 404 can be performed sequentially and / or simultaneously, and / or in a determined order, without departing from the scope of this disclosure.

[0102] Thus, UE 404 can send NACK message 504 on PUCCH B3 512 and PUCCH B4 514 (and / or other beams carrying PUCCH transmission) to ensure that base station 402 receives NACK message 504.

[0103] Once base station 402 receives NACK message 504, base station 402 can also use the communication link previously established with UE 404 via DCI (or other means, such as RRC signaling and / or MAC control element (CE)). In some aspects, when base station 402 receives NACK message 504 on PUCCH, it can determine at least one beam through which NACK message 504 was received, and retransmit SPS packet SN1 on PDSCH via a downlink beam corresponding to the uplink beam through which NACK message 504 was received on PUCCH. For example, but not as a limitation, base station 402 can determine that NACK message 504 was received on PUCCH B3 512. Base station 402 can then retransmit SPS packet 426 on PDSCH B3 516, where PDSCH B3 516 is (e.g., according to beam reciprocity) a downlink beam corresponding to the uplink beam of PUCCH B3 512.

[0104] To maintain the repetition of SPS packet transmission, base station 402 can also transmit SPS packet SN1 426 on another downlink beam to ensure that SPS packet SN1 426 is received at UE 404. For example... Figure 5 As shown, base station 402 can transmit SPS packets SN1 426 on PDSCHB4 518.

[0105] In some respects, base station 402 can also switch to sub-beams to transmit to UE 404 once it receives NACK message 504.

[0106] When base station 402 changes the downlink beam and / or UE 404 sends a NACK message 504, access network 482 (e.g., base station 402) can reallocate network resources to allow a new communication link between UE 404 and base station 402. Thus, access network 482 can also modify resources in access network 482 that are being used by other UEs and / or base stations to accommodate changing network conditions. This can be done in access network 482 via DCI and / or other means.

[0107] In some respects, base station 402 and / or UE 404 (and / or another network entity of access network 482) may have a predetermined PUCCH beam pattern to retransmit the initial NACK message if UE 404 does not receive an SPS packet. In some respects, base station 402 may also follow the same PDSCH beam order when retransmitting SPS packets to UE 404.

[0108] When UE 404 receives SPS packet SN1 426 on PDSCH B3 516 and / or PDSCH B4 518, UE 404 may send ACK message 424 to base station 402 on PUCCH via one or more beams. In some respects, UE 404 may send ACK message on PUCCH B3 512, although PUCCH B4 514 and / or other beams may also be used for PUCCH transmission without departing from the scope of this disclosure.

[0109] In some respects, once base station 402 receives ACK message 424, a new primary communication link can be established between base station 402 and UE 404. For example... Figure 5 As shown, for example, PDSCH B3 516 and PDSCH B4 518 can be new primary (e.g., active or serving) downlink beams (where multiple downlink beams may be used in access network 482 for redundancy). PUCCH B3 512 and PUCCH B4 514 can be new uplink beams (again, where multiple uplink beams may be used in access network 482 for redundancy).

[0110] Although uplink / downlink beamforming has been described, redundancy and / or modifications may be performed in access network 482 in other ways to overcome interference 550 and / or to provide redundancy in the communication link between base station 402 and UE 404. For example, but not as a limitation, spatial differences, time differences, and / or frequency differences, combinations of spatial differences and / or time differences may be used to provide redundancy and / or adjustment for secondary communication links without departing from the scope of this disclosure.

[0111] In some respects, UE resources (e.g., beamforming) can also be allocated to various functions used for the communication link between UE 404 and base station 402. For example, but not as a limitation, such as Figure 5 As shown, PUCCH B2 414 can be allocated to UE 404 to provide both ACK message 424 and NACK message 504. Furthermore, other resources (such as PUCCH B1 510, PUCCH B3 512, and PUCCH B4 514) can be allocated to transmit only NACK message 504. In this respect, PUCCH B1 510, PUCCH B3 512, and PUCCH B4 514 can be used by other UEs 104 and / or base station 402 for other purposes within access network 482.

[0112] Furthermore, within each PUCCH available to UE 404, different subbands can be used by UE 404 to transmit various messages. For example, but not as a limitation, UE 404 can use subband 1 of PUCCH B2 414 to transmit ACK message 424 and NACK message 504. However, when UE 404 uses a different PUCCH (e.g., PUCCH B3 512), UE 404 can transmit in subband 3 of PUCCH B3 512 instead of subband 1. Such resource allocation can be made in access network 482 by the PUCCH Resource Indicator (PRI).

[0113] In some respects, base station 402 may primarily monitor only a specific PUCCH based on PRI allocation. For example, but not as a limitation, base station 402 may monitor only PUCCH B2 414 to determine whether UE 404 has transmitted ACK message 424 or NACK message 504. If ACK message 424 is received, base station 402 may not need to monitor other message PRI resources (e.g., PUCCH B1 510, PUCCH B3 512, and / or PUCCH B4 514) because UE 404 will not transmit any messages on those PUCCH beams.

[0114] Base station 402 may not receive ACK message 424 on PUCCH B2 414, meaning a DTX event may occur between base station 402 and UE 404. Base station 402 can interpret the DTX event as the same as receiving NACK message 504 from UE 404. In such a scenario, base station 402 may subsequently begin monitoring PRI 2, 3, 4, etc. (e.g., PUCCH B1 510, PUCCHB3 512, and / or PUCCH B4 514) to maintain / rebuild communication with UE 404.

[0115] When base station 402 switches to monitor secondary PRI resources (e.g., PUCCH B1 510, PUCCH B3 512, and / or PUCCH B4 514), base station 402 only searches for NACK message 504. To ensure that NACK message 504 is received, base station 402 may change the base station 402 receiver sensitivity threshold to a lower value to ensure that NACK message 504 is received. However, changing the base station 402 receiver sensitivity to a lower threshold may ultimately lead to a higher probability of false alarms, i.e., receiving ACK message 424 and interpreting it as NACK message 504.

[0116] In some respects, to reduce the possibility of false alarms, base station 402 may require NACK message 504 to be received in more than one PRI resource and / or more than a predetermined percentage of PRI resources used in the communication link between base station 402 and UE 404. For example, but not as a limitation, in Figure 5 In the loop 442 shown, base station 402 may wait until it receives NACK message 504 on at least two PUCCH beams (e.g., PUCCH B3 512 and PUCCH B4 514) before retransmitting SPS packet SN1 426 on PDSCH B3 516 and / or PDSCH B4 518.

[0117] In some respects, base station 402 may monitor PRI 1 (i.e., PUCCH B2 414), and if ACK message 424 is received and / or decoded at base station 402, base station 402 may not monitor and / or decode the remaining PRIs (i.e., PUCCH B1 510, PUCCH B3 512, and PUCCH B4 514). However, the base station may monitor the remaining PRIs based on other factors (e.g., RSRP, RSRQ, SINR, SNR, and / or SIR corresponding to PUCCH B2 414, and / or other signal characteristics or factors). If base station 402 receives a NACK message from UE 404 on PUCCH B2 414 (PRI 1), base station 402 may begin monitoring one or more other PRIs (e.g., PUCCH B1 510, etc.) and / or monitor all other PRIs until base station 402 receives NACK message 504.

[0118] In some respects, although access network 482 resources (e.g., PUCCH B1 510, PUCCH B3 512, PUCCH B4 514, PDSCH B3 516, and PDSCH B4 518) may be available to base station 402 and UE 404, such resources may not be allocated to base station 402 and UE 404 for continuous use. Thus, these resources may be allocated to base station 402 and UE 404 for communication when a given event occurs, is anticipated, and / or is determined to be imminent.

[0119] For example, but not as a limitation, UE 404 and / or base station 402 may measure the signal characteristics of the communication link. UE 404 may measure values ​​corresponding to PDSCH B1 410 and / or PDSCH B2 412 based on RS received on PDSCH B1 410 and / or PDSCH B2 412 respectively, and / or base station 402 may measure values ​​corresponding to PUCCH B2 414 based on RS received on PUCCH B2 414 for certain characteristics (e.g., RSRP, RSRQ, SINR, SNR, SIR and / or other signal characteristics).

[0120] If one or more of the measured characteristics change and / or fall outside a predetermined range (e.g., the measured SINR falls below a certain threshold level, the measured SNR begins to change, etc.), then UE 404 may (e.g., via CSI based on CSI-RS) report that one of the communication links between UE 404 and base station 402 is degraded. Another entity of base station 402 or access network 482 may subsequently adapt the communication link between base station 402 and UE 404 upon anticipating a NACK message 504 rather than waiting to receive an actual NACK message 504. Other feedback and / or modifications to the communication link may also be used, such as enhanced HARQ feedback from UE 404 to base station 402, modulation and coding scheme (MCS) changes, and / or other conditions, without departing from the scope of this disclosure.

[0121] Furthermore, the amount of Additional Resources (PRI) that can be activated / assigned to base station 402 / UE 404 can be based on one or more conditions measured and / or determined in the communication link between base station 402 / UE 404.

[0122] There may also be scenarios where UE 404 and base station 402 are unable to determine, on their own, which PDSCH and / or PUCCH beams / channels can be used for switching to maintain communication between UE 404 and base station 402. For example, if the uplink SINR measured at base station 402 is below a certain threshold, access network 482 may reassign PUCCHs via Radio Resource Control (RRC) protocol to avoid using PUCCH channels / subchannels used by other UEs 104 in access network 482. SPS configuration may also be used to determine which resources can be allocated to the communication link between base station 402 and UE 404; however, SPS configuration may only be reassigned / allocated within access network 482 by RRC protocol, not by base station 402 / UE 404.

[0123] When an event occurs and / or is anticipated and / or determined by access network 482, UE 404, and / or base station 402, resources can be allocated to maintain the communication link between UE 404 and base station 402. The number of resources allocated may depend on the event, the anticipated event, and / or the determined event. For example, if the uplink SINR is measured at a level below the expected threshold, a larger number of additional resources can be allocated; if the downlink SINR is fading, a smaller number of additional resources can be allocated.

[0124] In some respects, code allocations (such as shared orthogonal overlay code (OCC) allocations) can also be assigned for newly allocated resources. For example, an OCC length of 2 can be assigned to the first newly allocated resource (PRI III, PUCCH B3 512), an OCC length of 4 can be assigned to the second newly allocated resource (PRI IV, PUCCH B4 514), and so on. Resource allocations and / or OCC lengths can also be based on the PUCCH format as needed.

[0125] Figure 6 This is a flowchart 600 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 350), another wireless communication device (e.g., device 802), or one or more components thereof, or performed at the UE, the other wireless communication device, or one or more components thereof. Depending on various aspects, one or more of the illustrated blocks may be omitted, interchanged, and / or performed concurrently.

[0126] In 602, the UE receives from the network and / or base station at least one first resource allocation dedicated to ACK or NACK transmission and at least one second resource allocation dedicated only to NACK transmission. For example, refer to Figures 4-5 UE 404 receives from base station 402 or other components of access network 482 at least one first resource allocation (e.g., PUCCH B2 414) dedicated to ACK or NACK transmission and at least one second resource allocation (e.g., PUCCH B1 510) dedicated only to NACK transmission. For example, refer to Figure 8 602 can be referenced Figure 8 The described receiving component 830 is executed.

[0127] In step 604, the UE performs one or more measurements on the network, transmits the measurement values ​​to the base station, and receives information from the network associated with at least one repeat of the initial NACK message based on the transmission of the one or more measurements. In some aspects, the UE may obtain some or all of the measurements based on receiving RS from the base station and measuring values ​​upon receiving those RS. For example, refer to Figures 4-5UE 404 receives from base station 402 a DCI indicating which of one or more measurements to perform, and based on this, the UE can measure one or more measurements corresponding to each of PDSCH B1 410, B2 412, B2 412, B3 516, and / or B4 518 when receiving the corresponding RS (e.g., CSI-RS) set via the corresponding beam. The one or more measurements may include, for example, RSRP measurement, RSRQ measurement, SINR measurement, SNR measurement, SIR measurement, Reference Signal Strength Indicator (RSSI) measurement, CQI measurement, or any combination thereof. The UE can transmit the set of measurement values ​​to the base station, and the UE can receive information configuring the repetition of NACK feedback based on the transmitted set of measurement values.

[0128] For example, refer to Figures 4-5 UE 404 can measure the characteristics of the communication link. UE 404 can measure values ​​corresponding to PDSCH B1 410 and / or PDSCH B2 412 based on the RS received thereon, respectively. For example, refer to... Figure 8 604 can be referenced Figure 8 The described transmission component 834 and measurement component 842 are performed.

[0129] In step 606, the UE receives a DCI from the network, wherein the DCI indicates to the UE at least one duplicate of at least one second resource allocation in response to the initial NACK message. The DCI may be received before the initial NACK message is transmitted. For example, refer to... Figures 4-5 UE 404 receives DCI from base station 402 via PDCCH, and the DCI indicates the PUCCH beam to UE 404, for example, PUCCH B1510. For example, 606 can be referenced... Figure 8 The described receiving component 830 is executed.

[0130] At 608, the UE receives a DCI configuring an SPS associated with at least one second resource allocation. In some aspects, the DCI can reconfigure at least one second resource allocation based on an earlier configured resource allocation. The DCI can configure the SPS resources to be scheduled for periodicity. For example, refer to... Figures 4-5 UE 404 receives DCI from base station 402 via PDCCH. This DCI indicates to UE 404 that it should be used to encode and transmit SPS information for HARQ feedback on resources scheduled to appear periodically. For example, 608 can be referenced... Figure 8 The described receiving component 830 is executed.

[0131] At 610, the UE receives at least one repeated message activating the initial NACK message. For example, refer to Figures 4-5 UE 404 receives SPS packet 420 from base station 402, which configures UE 404 to transmit at least one repetition of initial NACK message 504. For example, 610 can be referenced. Figure 8 The described receiving component 830 is executed.

[0132] In 612, the UE transmits an initial NACK message to the network based on at least one first resource allocation. In some aspects, ACK feedback can be transmitted without duplication, but NACK feedback can be transmitted with duplication. For example, refer to... Figures 4-5 UE 404 transmits a NACK message 504 on PUCCH B2 414. For example, 612 can be referenced. Figure 8 The described transport component 834 is executed.

[0133] In step 614, the UE determines whether to transmit at least one repetition of the initial NACK message, the at least one repetition of the initial NACK message being transmitted based on the determination of whether to transmit the initial NACK message. For example, refer to Figures 4-5 UE 404 determines whether to transmit the initial NACK message on PUCCH B1 510. For example, 614 can be determined by reference... Figure 8 The described determination component 840 is executed.

[0134] In 616, the UE transmits at least one duplicate of the initial NACK message based on at least one second resource allocation. For example, refer to Figure 7 UE 404 transmits an initial NACK message 504 on PUCCH B1 510. On one hand, at least one repetition of the initial NACK message 504 can be transmitted based on received information. On the other hand, UE 404 can determine whether to transmit at least one repetition of the initial NACK message 504, which can be based on information associated with at least one repetition of the initial NACK message received from base station 402. For example, 616 can be determined by reference... Figures 4-5 The described transport component 834 is executed.

[0135] Figure 9 This is a flowchart 700 of a wireless communication method. The method can be performed by a network entity (such as a base station (e.g., base station 102 / 180, 310)), another wireless communication device (e.g., device 902), or one or more components thereof, or performed at that network entity, the other wireless communication device, or one or more components thereof. Depending on various aspects, one or more of the illustrated blocks may be omitted, interchanged, and / or performed concurrently.

[0136] In 702, the base station transmits to the UE at least one first resource allocation dedicated to ACK or NACK transmission and at least one second resource allocation dedicated only to NACK transmission. For example, refer to Figures 4-5 Base station 402 transmits to UE 404 at least one first resource allocation (e.g., PUCCH B2 414) dedicated to ACK or NACK transmission and at least one second resource allocation (e.g., PUCCH B1 510) dedicated only to NACK transmission. For example, 702 can be referenced... Figure 9 The described transport component 934 is executed.

[0137] In step 704, the base station may receive one or more measurements from the UE. These measurements may include values ​​of one or more of RSRP, RSRQ, SINR, SNR, RSSI, and / or CQI. One or more measurement values ​​may be based on RS transmitted from the base station to the UE. For example, referencing... Figures 4-5 Base station 402 receives from UE 404 one or more measurements corresponding to the channel on which base station and UE 404 communicate (e.g., PDSCH), at least one first resource allocation (e.g., PUCCHB2 414) dedicated to ACK or NACK transmission, and at least one second resource allocation (e.g., PUCCH B1 510) dedicated only to NACK transmission. For example, 704 may be determined by reference. Figure 9 The described measurement component 942 performs this function.

[0138] At 706, the base station determines whether to configure at least one repeated second resource allocation for the initial NACK message. In some aspects, the base station may determine to configure at least one second resource allocation based on one or more measurements received from the UE and / or one or more measurements measured from RS (e.g., SRS) transmitted by the UE to the base station. The base station may compare one or more of the measurements with a threshold, and the base station may determine to configure at least one second resource allocation based on the comparison of the measurements with the threshold. In some other aspects, the base station may compare several NACK feedback messages with a threshold, and the base station may determine to configure at least one second resource allocation based on the comparison of several NACK feedback messages with the threshold. For example, refer to... Figures 4-5 Base station 402 determines which PUCCH resources and / or beams (e.g., PUCCH B1 510) should be configured for at least one second resource allocation. For example, 706 can be determined by a reference. Figure 9 The described configuration component 940 is executed.

[0139] In 708, the base station transmits a DCI allocating at least one second resource allocation to the UE before transmitting the downlink transmission corresponding to the initial NACK message. For example, refer to Figures 4-5 Base station 402 transmits DCI via PDCCH, which indicates to UE 404 at least one second resource allocation PUCCH resource and / or beam. For example, 708 can be referenced. Figure 9 The described transport component 934 is executed.

[0140] At 710, the base station transmits a DCI that reconfigures the SPS configuration associated with at least one second resource allocation. For example, refer to Figures 4-5 Base station 402 can transmit information associated with PUCCH B1 510 to UE 404. For example, 710 can be referenced... Figure 9 The described transport component 934 is executed.

[0141] In 712, when the base station determines that at least one second resource allocation needs to be configured, it transmits at least one duplicate of the activation initial NACK message, the at least one duplicate of which is received based on the transmitted information. For example, refer to Figures 4-5 Base station 402 transmits DCI via PDCCH, which indicates PUCCH resources and / or beams (e.g., PUCCH B1 510) to UE 404. For example, 712 can be referenced... Figure 9 The described transport component 934 is executed.

[0142] In 714, the base station receives the initial NACK message based on at least one first resource allocation. The base station can decode resources scheduled by DCI configured for SPS and activated by DCI. The initial NACK can be the first transmitted HARQ message for the corresponding transmission to the UE. For example, refer to Figures 4-5 Base station 402 can receive initial NACK message 504 from UE 404 on PUCCH B2 414. For example, 714 can be referenced. Figure 9 The described receiving component 930 is executed.

[0143] In 716, the base station receives at least one duplicate of the initial NACK message based on at least one second resource allocation. The base station can decode at least one duplicate on the second resource allocation when the initial HARQ feedback message indicates NACK. The base station can suppress decoding of information on the second resource allocation when the initial HARQ transmission on the first resource allocation indicates ACK. For example, refer to... Figure 8 Base station 402 can receive a repeat of the initial NACK message 504 from UE 404 on PUCCH B1 510. For example, 716 can be referenced.Figure 3 The described receiving component 930 is executed.

[0144] Figure 3 Figure 800 illustrates an example of the hardware implementation of device 802. Device 802 may be a UE or similar device, or device 802 may be a component of a UE or similar device. Device 802 may include a cellular baseband processor 804 (also known as a modem) and / or a cellular RF transceiver 822, which may be coupled together and / or integrated into the same package, component, circuit, chip, and / or other circuit system.

[0145] In some aspects, device 802 may accept or may accept one or more Subscriber Identity Module (SIM) cards 820, which may be one or more integrated circuits, chips, or similar circuit systems, and may be removable or embedded. The one or more SIM cards 820 may carry identification and / or authentication information, such as International Mobile Subscriber Identity (IMSI) and / or IMSI-related keys. Furthermore, device 802 may include one or more of the following coupled to a Secure Digital (SD) card 808 and a screen 810: an application processor 806, a Bluetooth module 812, a Wireless Local Area Network (WLAN) module 814, a Global Positioning System (GPS) module 816, and / or a power supply 818.

[0146] Cellular baseband processor 804 communicates with UE 104 and / or base station 102 / 180 via cellular RF transceiver 822. Cellular baseband processor 804 may include computer-readable medium / memory. The computer-readable medium / memory may be non-transient. Cellular baseband processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. This software, when executed by cellular baseband processor 804, causes cellular baseband processor 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by cellular baseband processor 804 during software execution. Cellular baseband processor 804 further includes receiving component 830, communication manager 832, and transmission component 834. Communication manager 832 includes one or more of the described components. Components within communication manager 832 may be stored in computer-readable medium / memory and / or configured as hardware within cellular baseband processor 804.

[0147] exist Figure 6 In the context of this, the cellular baseband processor 804 may be a component of the UE 350 and may include memory 360 and / or at least one of the following: TX processor 368, RX processor 356, and / or controller / processor 359. In one configuration, device 802 may be a modem chip and / or may be implemented as baseband processor 804, while in another configuration, device 802 may be the entire UE (e.g.,Figure 6 The UE 350 may include some or all of the components, circuits, chips and / or other circuit systems described in the context of device 802. In one configuration, the cellular RF transceiver 822 may be implemented as at least one of transmitter 354TX and / or receiver 354RX.

[0148] The receiving component 830 can be configured to receive signaling on a wireless channel, such as signaling from base station 102 / 180 or UE 104. The transmitting component 834 can be configured to transmit signaling on a wireless channel, such as signaling to base station 102 / 180 or UE 104. The communication manager 832 can coordinate or manage some or all wireless communications performed by the device 802, including wireless communications across the receiving component 830 and the transmitting component 834.

[0149] The receiving component 830 may provide the communication manager 832 with some or all of the data and / or control information included in the received signaling, and the communication manager 832 may generate some or all of the data and / or control information to be included in the transmitted signaling and provide this data and / or control information to the transmission component 834. The communication manager 832 may include various explained components, including one or more components configured to process the received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission.

[0150] The communication manager 832 includes a determining component 840 configured to determine whether to transmit at least one repeat of an initial NACK message, the at least one repeat of the initial NACK message being transmitted based on the determination of whether to transmit at least one repeat of the initial NACK message, such as in conjunction with information from... Figures 4-6 As described in 608.

[0151] The communication manager 832 further includes a measurement component 842 that communicates with the transmission component 834 to perform one or more measurements; and the transmission component 834 transmits one or more measurements to the network and also communicates with the receiving component 830 to receive information associated with at least one repetition of the initial NACK message from the network. The receiving component 830 and the transmission component 834 can communicate to transmit one or more measurements. The transmission component 834 can also determine whether to transmit at least one repetition of the initial NACK message based on the information received from the network associated with at least one repetition of the initial NACK message, such as in combination with information from... Figures 4-6 As described in 610.

[0152] Device 802 may include execution Figure 9Some or all of the additional components of the algorithms, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts. Thus, Figure 7 Some or all of the boxes, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts may be executed by one or more components, and device 802 may include one or more such components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0153] In one configuration, device 802 (and particularly cellular baseband processor 804) includes: means for transmitting feedback to a network entity on a first resource set, including ACK or non-ACK feedback corresponding to a transmission from the network entity, wherein the feedback is transmitted without repetition when the feedback includes ACK corresponding to the transmission; and means for transmitting a repetition of the feedback to the network entity on a second resource set when the feedback includes NACK corresponding to the transmission.

[0154] In one configuration, device 802 (and in particular cellular baseband processor 804) may further include: means for receiving information indicating that a first resource set is allocated to include feedback for ACK or NACK corresponding to the transmission; and means for receiving information indicating that a second resource set is allocated to include feedback for NACK corresponding to the transmission.

[0155] In one configuration, at least one other repeating means is used to transmit feedback to the network entity on at least one third resource set when the feedback includes a NACK corresponding to the transmission.

[0156] In one configuration, the repetition of this feedback is based on a set of measurements associated with the channel on which the network entity communicates.

[0157] In one configuration, device 802 (and in particular cellular baseband processor 804) may further include: means for transmitting information indicating the set of measurements to the network entity; and means for receiving from the network entity a configuration associated with transmitting a repetition of the feedback including the NACK based on the information indicating the set of measurements, wherein the repetition of the feedback including the NACK is transmitted based on the configuration.

[0158] In one configuration, device 802 (and in particular cellular baseband processor 804) may further include means for receiving a repeating configuration that activates the feedback including the NACK, and the repeating of the feedback including the NACK is transmitted after the configuration is received.

[0159] In one configuration, device 802 (and in particular cellular baseband processor 804) may further include means for receiving from the network entity a DCI indicating an SPS configuration associated with a second resource set, and the repetition of the feedback including the NACK is transmitted after the SPS configuration is received.

[0160] In one configuration, the SPS configuration indicates an authorization for a repetition of the feedback including NACK transmitted on a second resource set, and further indicates at least one other authorization for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

[0161] In one configuration, the first resource set and the second resource set respectively include at least one of a time resource set, a frequency resource set, or a spatial resource set, and the corresponding spatial resource set includes the beam of the network entity.

[0162] In one configuration, the first resource set is different from the second resource set.

[0163] The aforementioned apparatus may be one or more of the aforementioned components in device 802 configured to perform the functions described by the aforementioned apparatus. As described above, device 802 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned apparatus may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the aforementioned apparatus.

[0164] Figure 7 Figure 900 illustrates an example of the hardware implementation of device 902. Device 902 may be a base station or similar device or system, or device 902 may be a component of a base station or similar device or system. Device 902 may include a baseband unit 904. Baseband unit 904 may communicate via a cellular RF transceiver. For example, baseband unit 904 may communicate with UE 104 via a cellular RF transceiver (e.g., for downlink and / or uplink communication), and / or with base stations 102 / 180 (e.g., for IAB).

[0165] Baseband unit 904 may include computer-readable medium / memory, which may be non-transient. Baseband unit 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by baseband unit 904, the software causes baseband unit 904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 904 during software execution. Baseband unit 904 further includes receiving component 930, communication manager 932, and transmission component 934. Communication manager 932 includes one or more of the described components. Components within communication manager 932 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 904. Baseband unit 904 may be a component of base station 310 and may include memory 376 and / or at least one of the following: TX processor 316, RX processor 370, and controller / processor 375.

[0166] The receiving component 930 can be configured to receive signaling on a wireless channel, such as signaling from UE 104 or base station 102 / 180. The transmitting component 934 can be configured to transmit signaling on a wireless channel, such as signaling to UE 104 or base station 102 / 180. The communication manager 932 can coordinate or manage some or all wireless communications performed by the device 902, including wireless communications across the receiving component 930 and the transmitting component 934.

[0167] The device 902 includes a receiving component 930 and a transmitting component 934, wherein the transmitting component 934 transmits to the UE 104 at least one first resource allocation dedicated to ACK transmission or NACK transmission and at least one second resource allocation dedicated only to NACK transmission; and the receiving component 930 receives an initial NACK message based on at least one first resource allocation and at least one duplicate of the initial NACK message based on at least one second resource allocation.

[0168] The communication manager 932 includes a configuration component 940 that determines whether to configure at least one second resource allocation for at least one repetition of the initial NACK message, and the at least one repetition of the initial NACK message is received when it is determined that at least one second resource allocation should be configured, for example, as in combination with Figure 4 As described in 708.

[0169] The communication manager 932 further includes a measurement component 942 that receives one or more measurements from the UE 104 to determine the characteristics of the communication link between the UE 104 and the base station 102 / 180, such as in combination with Figure 5 As described in 710.

[0170] The receiving component 930 may provide some or all of the data and / or control information included in the received signaling to the communication manager 932, and the communication manager 932 may generate some or all of the data and / or control information to be included in the transmitted signaling and provide this data and / or control information to the transmission component 934. The communication manager 932 may include various explained components, including one or more components configured to process the received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission. In some aspects, the generation of data and / or control information may include packetizing or otherwise reformatting the data and / or control information received from the core network (such as core network 190 or EPC 160) for transmission.

[0171] Device 902 may include execution Figure 7 , Figure 4 and / or Figure 5 Some or all of the additional components of the algorithms, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts. Thus, Figure 7 , Figure 4 and / or Figure 5 Figure 7 Some or all of the boxes, operations, signaling, etc., in the aforementioned call flow diagrams and / or flowcharts may be executed by a component, and device 902 may include one or more of those components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0172] In one configuration, device 902 (and in particular baseband unit 904) includes means for decoding feedback received from the UE on a first resource set, the feedback including an ACK or NACK corresponding to a transmission to the UE; and means for decoding a repetition of feedback received from the UE on a second resource set when the feedback decoded on the first resource set includes a NACK corresponding to the transmission.

[0173] In one configuration, device 902 (and in particular baseband unit 904) further includes means for transmitting to the UE information indicating that a first resource set is allocated to include feedback of ACK or NACK corresponding to the transmission; and means for transmitting to the UE information indicating that a second resource set is allocated to include feedback of NACK corresponding to the transmission.

[0174] In one configuration, device 902 (and in particular baseband unit 904) further includes at least one other repeating means for decoding feedback received from the UE on at least one third resource set when the feedback includes a NACK corresponding to the transmission.

[0175] In one configuration, device 902 (and in particular baseband unit 904) further includes means for receiving from the UE information indicating a set of measurements associated with a channel on which the UE communicates; and means for transmitting to the UE a configuration associated with transmitting a repetition of feedback including the NACK based on the information indicating the set of measurements, and the repetition of feedback including the NACK being decoded based on the configuration.

[0176] In one configuration, the set of measurements includes the value of at least one of RSRP, RSRQ, SINR, SNR, SIR, CQI, or RSSI.

[0177] In one configuration, device 902 (and in particular baseband unit 904) further includes means for transmitting to the UE a repeating configuration that activates feedback including NACK, and the repeating of feedback including NACK is decoded after the configuration is transmitted.

[0178] In one configuration, device 902 (and in particular baseband unit 904) further includes means for transmitting to the UE a DCI indicating an SPS configuration associated with a second resource set, and the repetition of feedback including NACK is decoded after the SPS configuration is transmitted.

[0179] In one configuration, the SPS configuration indicates an authorization for a repetition of transmitting feedback including NACK on a second resource set, and further indicates at least one other authorization for at least one other repetition of transmitting feedback including NACK on at least one third resource set.

[0180] In one configuration, the first resource set and the second resource set respectively include at least one of a time resource set, a frequency resource set, or a spatial resource set, wherein the corresponding spatial resource set includes the beam of the network entity.

[0181] In one configuration, the first resource set is different from the second resource set.

[0182] In one configuration, there are means for suppressing the decoding of information on a second resource set when the feedback decoded on a first resource set includes an ACK corresponding to the transmission.

[0183] The aforementioned apparatus may be one or more of the aforementioned components in device 902 configured to perform the functions described by the aforementioned apparatus. As described above, device 902 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the aforementioned apparatus may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the aforementioned apparatus.

[0184] The specific order or hierarchy of the various boxes or operations in each of the processes, flowcharts, and other illustrations disclosed herein is an explanation of exemplary methods. Based on design preferences, those skilled in the art will readily recognize that the specific order or hierarchy of the boxes or operations in each of the foregoing processes, flowcharts, and other illustrations can be rearranged, omitted, and / or performed concurrently without departing from the scope of this disclosure. Furthermore, some boxes or operations can be combined or omitted. The appended method claims present the elements of various boxes or operations in an exemplary order and are not intended to limit them to the specific order or hierarchy presented.

[0185] The following examples are merely illustrative and can be combined with other embodiments or aspects of the teachings described herein without limitation.

[0186] Example 1 is a method for wireless communication at a UE, the method comprising: transmitting feedback to a network entity on a first resource set, including an ACK or NACK corresponding to a transmission from the network entity, wherein when the feedback includes an ACK corresponding to the transmission, the feedback is transmitted without duplication; and when the feedback includes a NACK corresponding to the transmission, transmitting a duplication of the feedback to the network entity on a second resource set.

[0187] Example 2 can be the method of Example 1, further comprising: receiving information indicating that a first resource set is allocated to include the feedback corresponding to the ACK or NACK of the transmission; and receiving information indicating that a second resource set is allocated to include the feedback corresponding to the NACK of the transmission.

[0188] Example 3 can be the method of Example 1, further comprising: when the feedback includes a NACK corresponding to the transmission, transmitting at least one other repetition of the feedback to the network entity on at least one third resource set.

[0189] Example 4 can be the method of Example 1, and the repetition of the feedback is transmitted based on a set of measurements associated with the channel on which the network entity communicates.

[0190] Example 5 may be the method of Example 4, and the set of measurements includes values ​​of at least one of the following: Reference Received Power (RSRP), Reference Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Signal-to-Noise Ratio (SNR), Signal-to-Interference Ratio (SIR), Channel Quality Indicator (CQI), or Reference Signal Strength Indicator (RSSI).

[0191] Example 6 may be the method of Example 4, further comprising: transmitting information indicating the set of measurements to the network entity; and receiving from the network entity a configuration associated with transmitting a repetition of the feedback including NACK based on the information indicating the set of measurements, wherein the repetition of the feedback including NACK is transmitted based on the configuration.

[0192] Example 7 can be the method of Example 1, further including: receiving a repeating configuration that activates the feedback including NACK, and the repeating of the feedback including NACK is transmitted after the configuration is received.

[0193] Example 8 may be the method of Example 1, further comprising: receiving from the network entity a DCI indicating an SPS configuration associated with a second resource set, and the repetition of the feedback including NACK being transmitted after the SPS configuration is received.

[0194] Example 9 may be the method of Example 8, and the SPS configuration indicates an authorization for the repetition of the feedback including NACK transmitted on the second resource set, and further indicates at least one other authorization for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

[0195] Example 10 can be the method of Example 1, and the first resource set and the second resource set respectively include at least one of a time resource set, a frequency resource set or a spatial resource set, and the corresponding spatial resource set includes the beam of the network entity.

[0196] Example 11 can be the method of Example 1, and the first resource set is different from the second resource set.

[0197] Example 12 is a method for wireless communication at a network entity, the method comprising: decoding feedback received from a UE on a first resource set, the feedback including an ACK or NACK corresponding to a transmission to the UE; and decoding a repetition of feedback received from the UE on a second resource set when the feedback decoded on the first resource set includes a NACK corresponding to the transmission.

[0198] Example 13 may be the method of Example 12, further comprising: transmitting to the UE information indicating that a first resource set is allocated for including the feedback corresponding to the transmission (ACK or NACK); and transmitting to the UE information indicating that a second resource set is allocated for including the feedback corresponding to the transmission (NACK).

[0199] Example 14 may be the method of Example 12, further comprising: when the feedback includes a NACK corresponding to the transmission, decoding at least one other repetition of the feedback received from the UE on at least one third resource set.

[0200] Example 15 may be the method of Example 12, further comprising: receiving from the UE information indicating a set of measurements associated with a channel on which the UE communicates; and transmitting to the UE a configuration associated with the transmission of a repetition of the feedback including NACK based on the information indicating the set of measurements, wherein the repetition of the feedback including NACK is decoded based on the configuration.

[0201] Example 16 can be the method of Example 15, and the set of measurements includes the value of at least one of RSRP, RSRQ, SINR, SNR, SIR, CQI, or RSSI.

[0202] Example 17 may be the method of Example 12, further comprising: transmitting to the UE a repeated configuration that activates the feedback including NACK, and the repeated feedback including NACK is decoded after the configuration is transmitted.

[0203] Example 18 may be the method of Example 12, further comprising: transmitting to the UE a DCI indicating an SPS configuration associated with a second resource set, and the repetition of the feedback including NACK being decoded after the SPS configuration is transmitted.

[0204] Example 19 may be the method of Example 18, and the SPS configuration indicates an authorization for a repetition of the feedback including NACK transmitted on a second resource set, and further indicates at least one other authorization for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

[0205] Example 20 can be the method of Example 12, and the first resource set and the second resource set respectively include at least one of a time resource set, a frequency resource set or a spatial resource set, and the corresponding spatial resource set includes the beam of the network entity.

[0206] Example 21 can be the method of Example 12, and the first resource set is different from the second resource set.

[0207] Example 22 can be the method of Example 12, further comprising: suppressing the decoding of information on the second resource set when the feedback decoded on the first resource set includes an ACK corresponding to the transmission.

[0208] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein can be applied to other aspects. Therefore, the claims are not intended to limit the scope to the aspects shown herein, but are to be granted the full scope consistent with the language used herein.

[0209] As an example, the language "determine" can encompass a wide variety of actions and therefore may not be limited to the concepts and aspects explicitly described or explained by this disclosure. In some contexts, "determine" can include calculus, computation, processing, measurement, derivation, research, lookup (e.g., looking in a table, database, or other data structure), ascertainment, parsing, selection, choosing, establishing, and the like. In some other contexts, "determine" can include communication and / or memory operations / procedures through which information or values ​​are obtained, such as "receiving" (e.g., receiving information), "accessing" (e.g., accessing data in memory), "detecting," etc.

[0210] As another example, references to singular elements are not intended to mean "one and only one" (unless specifically stated otherwise), but rather "one or more." Furthermore, terms such as "if," "when," and "at" should be interpreted as meaning "under this condition," rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or event or during the occurrence of an action or event, but rather imply that another action or event will occur under the condition that a condition is met, without requiring a specific or immediate temporal constraint or direct relation for the occurrence of that other action or event. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term "some / a certain" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “apparatus.” Thus, no claim element should be interpreted as an apparatus plus a function unless the element is explicitly stated using the phrase “apparatus for…”.

Claims

1. A method for conducting wireless communication at a user equipment (UE), comprising: Transmitting feedback, including an acknowledgment (ACK) or non-ACK (NACK), corresponding to a transmission from a network entity, on a first resource set including a first beam, wherein the feedback is transmitted without repetition when it includes an ACK corresponding to the transmission, wherein the first beam corresponds to a beam link for the transmission from the network entity; and When the feedback includes a NACK corresponding to the transmission, the repetition of the feedback is transmitted on a second resource set including a second beam different from the first beam, wherein the second beam corresponds to a sub-beam link for the transmission from the network entity.

2. The method of claim 1, further comprising: The information of the first resource set is allocated to receive the feedback, which includes an ACK or NACK corresponding to the transmission; as well as The information received indicates that the second resource set is allocated to include the feedback of the NACK corresponding to the transmission.

3. The method of claim 1, further comprising: When the feedback includes a NACK corresponding to the transmission, at least one other repeat of the feedback is transmitted on at least one third resource set.

4. The method of claim 1, wherein, The feedback is repeated based on a set of measurements associated with the channel on which the network entity communicates.

5. The method of claim 4, wherein the set of measurements includes values ​​of at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference Plus Noise Ratio (SINR), Signal-to-Noise Ratio (SNR), Signal-to-Interference Ratio (SIR), Channel Quality Indicator (CQI), or Reference Signal Strength Indicator (RSSI).

6. The method of claim 4, further comprising: Transmit information indicating the set of measured values; as well as The configuration for receiving and transmitting feedback, including NACK, is based on the information indicating the set of measurements, wherein... The repetition of the feedback, including NACK, is transmitted based on the configuration.

7. The method of claim 1, further comprising: The configuration for receiving activation includes a repeat of the feedback of NACK, wherein the repeat of the feedback of NACK is transmitted after the configuration is received.

8. The method of claim 1, further comprising: Receive downlink control information (DCI) indicating a semi-persistent scheduling (SPS) configuration associated with the second resource set, including the repetition of the feedback of NACK, which is transmitted after the SPS configuration is received.

9. The method of claim 8, wherein, The SPS configuration indicates one permission for a repetition of the feedback including NACK transmitted on the second resource set, and further indicates at least one other permission for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

10. The method of claim 1, wherein, The first resource set and the second resource set each include at least one of a time resource set, a frequency resource set, or a spatial resource set, wherein the corresponding spatial resource set includes the beam of the network entity.

11. The method of claim 1, wherein, The first resource set is different from the second resource set.

12. A method for wireless communication at a network entity, comprising: Decoding feedback received from a user equipment (UE) on a first resource set including a first beam, the feedback including an acknowledgment (ACK) or non-ACK (NACK) corresponding to a transmission destined for the UE, wherein the first beam corresponds to a beam link for the transmission from the network entity; and When the feedback decoded on the first resource set includes a NACK corresponding to the transmission, the feedback received from the UE is decoded on a second resource set including a second beam different from the first beam, wherein the second beam corresponds to a sub-beam link for the transmission from the network entity. as well as When the feedback decoded on the first resource set includes the ACK corresponding to the transmission, decoding of information on the second resource set is suppressed.

13. The method of claim 12, further comprising: The transmission indication is assigned to the information of the first resource set, which includes the feedback of an ACK or NACK corresponding to the transmission; as well as The transmission indication is assigned to the information of the second resource set, which includes the feedback of the NACK corresponding to the transmission.

14. The method of claim 12, further comprising: When the feedback includes a NACK corresponding to the transmission, decode at least one other repetition of the feedback received from the UE on at least one third resource set.

15. The method of claim 12, further comprising: Receive information indicating a set of measurements associated with the channel on which the UE communicates; as well as A configuration is used to transmit a repetitive feedback, including a NACK, based on the information indicating the set of measurements, wherein The repetition of the feedback, including NACK, is decoded based on the configuration.

16. The method of claim 15, wherein the set of measurements includes values ​​of at least one of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference plus noise ratio (SINR), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), channel quality indicator (CQI), or reference signal strength indicator (RSSI).

17. The method of claim 12, further comprising: The transmission activation includes a configuration that repeats the feedback of NACK, wherein the repeat of the feedback of NACK is decoded after the transmission of the configuration.

18. The method of claim 12, further comprising: The transmission indicates the downlink control information (DCI) configuration associated with the second resource set, including the repetition of the feedback of NACK, which is decoded after the SPS configuration is transmitted.

19. The method of claim 18, wherein, The SPS configuration indicates one permission for a repetition of the feedback including NACK transmitted on the second resource set, and further indicates at least one other permission for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

20. The method of claim 12, wherein, The first resource set and the second resource set each include at least one of a time resource set, a frequency resource set, or a spatial resource set, wherein the corresponding spatial resource set includes the beam of the network entity.

21. The method of claim 12, wherein, The first resource set is different from the second resource set.

22. The method of claim 12, further comprising: When the feedback decoded on the first resource set includes an ACK corresponding to the transmission, the decoding of information on the second resource set is suppressed.

23. An apparatus for conducting wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor, the at least one processor being coupled to the memory and configured to: Transmitting feedback, including an acknowledgment (ACK) or non-ACK (NACK), corresponding to a transmission from a network entity, on a first resource set including a first beam, wherein the feedback is transmitted without repetition when it includes an ACK corresponding to the transmission, wherein the first beam corresponds to a beam link for the transmission from the network entity; and When the feedback includes a NACK corresponding to the transmission, the repetition of the feedback is transmitted on a second resource set including a second beam different from the first beam, wherein the second beam corresponds to a sub-beam link for the transmission from the network entity.

24. The apparatus of claim 23, wherein the at least one processor is further configured to: The information of the first resource set allocated to receive the indication is used to include the feedback of an ACK or NACK corresponding to the transmission; and The information received indicates that the second resource set is allocated to include the feedback of the NACK corresponding to the transmission.

25. The apparatus of claim 23, wherein the at least one processor is further configured to: When the feedback includes a NACK corresponding to the transmission, at least one other repetition of the feedback is transmitted on at least one third resource set.

26. The apparatus of claim 23, wherein, The feedback is repeated based on a set of measurements associated with the channel on which the network entity communicates.

27. The apparatus of claim 26, wherein the set of measurements includes values ​​of at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference Plus Noise Ratio (SINR), Signal-to-Noise Ratio (SNR), Signal-to-Interference Ratio (SIR), Channel Quality Indicator (CQI), or Reference Signal Strength Indicator (RSSI).

28. The apparatus of claim 26, wherein the at least one processor is further configured to: Transmit information indicating the set of measurements; and The configuration for receiving and transmitting feedback, including NACK, is based on the information indicating the set of measurements, wherein... The repetition of the feedback, including NACK, is transmitted based on the configuration.

29. The apparatus of claim 23, wherein the at least one processor is further configured to: The configuration for receiving activation includes a repeat of the feedback of NACK, wherein the repeat of the feedback of NACK is transmitted after the configuration is received.

30. The apparatus of claim 23, wherein the at least one processor is further configured to: Receive downlink control information (DCI) indicating a semi-persistent scheduling (SPS) configuration associated with the second resource set, including the repetition of the feedback of NACK, which is transmitted after the SPS configuration is received.

31. The apparatus of claim 30, wherein, The SPS configuration indicates one permission for a repetition of the feedback including NACK transmitted on the second resource set, and further indicates at least one other permission for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

32. The apparatus of claim 23, wherein, The first resource set and the second resource set each include at least one of a time resource set, a frequency resource set, or a spatial resource set, wherein the corresponding spatial resource set includes the beam of the network entity.

33. The apparatus of claim 23, wherein, The first resource set is different from the second resource set.

34. An apparatus for wireless communication at a network entity, comprising: Memory; as well as At least one processor, the at least one processor being coupled to the memory and configured to: Decoding feedback received from a user equipment (UE) on a first resource set including a first beam, the feedback including an acknowledgment (ACK) or non-ACK (NACK) corresponding to a transmission to the UE, wherein the first beam corresponds to a beam link for the transmission from the network entity; When the feedback decoded on the first resource set includes a NACK corresponding to the transmission, the feedback received from the UE is decoded on a second resource set including a second beam different from the first beam, wherein the second beam corresponds to a sub-beam link for the transmission from the network entity. as well as When the feedback decoded on the first resource set includes the ACK corresponding to the transmission, decoding of information on the second resource set is suppressed.

35. The apparatus of claim 34, wherein the at least one processor is further configured to: The transmission indication is assigned to the information of the first resource set, which includes the feedback of an ACK or NACK corresponding to the transmission; and The transmission indication is assigned to the information of the second resource set, which includes the feedback of the NACK corresponding to the transmission.

36. The apparatus of claim 34, wherein the at least one processor is further configured to: When the feedback includes a NACK corresponding to the transmission, decode at least one other repetition of the feedback received from the UE on at least one third resource set.

37. The apparatus of claim 34, wherein the at least one processor is further configured to: Receive information indicating a set of measurements associated with the channel on which the UE communicates; and A configuration is used to transmit a repetitive feedback, including a NACK, based on the information indicating the set of measurements, wherein The repetition of the feedback, including NACK, is decoded based on the configuration.

38. The apparatus of claim 37, wherein the set of measurements includes values ​​of at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference Plus Noise Ratio (SINR), Signal-to-Noise Ratio (SNR), Signal-to-Interference Ratio (SIR), Channel Quality Indicator (CQI), or Reference Signal Strength Indicator (RSSI).

39. The apparatus of claim 34, wherein the at least one processor is further configured to: The transmission activation includes a configuration that repeats the feedback of NACK, wherein the repeat of the feedback of NACK is decoded after the transmission of the configuration.

40. The apparatus of claim 34, wherein the at least one processor is further configured to: The transmission indicates the downlink control information (DCI) configuration associated with the second resource set, including the repetition of the feedback of NACK, which is decoded after the SPS configuration is transmitted.

41. The apparatus of claim 40, wherein, The SPS configuration indicates one permission for a repetition of the feedback including NACK transmitted on the second resource set, and further indicates at least one other permission for at least one other repetition of the feedback including NACK transmitted on at least one third resource set.

42. The apparatus of claim 34, wherein, The first resource set and the second resource set each include at least one of a time resource set, a frequency resource set, or a spatial resource set, wherein the corresponding spatial resource set includes the beam of the network entity.

43. The apparatus of claim 34, wherein, The first resource set is different from the second resource set.

44. The apparatus of claim 34, wherein the at least one processor is further configured to: When the feedback decoded on the first resource set includes an ACK corresponding to the transmission, the decoding of information on the second resource set is suppressed.

Images