Unsuccessful hybrid automatic repeat request process termination for multiple transport blocks
By enabling early detection of NACK to ACK errors for multiple TBs in wireless communication, the method reduces latency and signaling overhead by allowing timely ARQ process initiation and minimizing buffering, addressing the challenge of detecting unsuccessful HARQ process terminations in wireless networks.
Patent Information
- Application Number
- PCT/CN2025/093350
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
In wireless communication networks, detecting NACK to ACK errors for multiple transport blocks (TBs) configured in a single DCI message is challenging, leading to increased latency and premature ARQ processes due to the inability to identify unsuccessful HARQ process terminations before a timer expires.
A receiving device, such as a UE, detects NACK to ACK errors through lower-layer assisted methods before the expiration of a timer by identifying unsuccessful HARQ process terminations for individual TBs, even when multiple TBs share the same HARQ process identifier, and reports these to the transmitting device.
This approach reduces latency and signaling overhead by allowing timely initiation of ARQ processes and decreases buffering requirements at the receiving device, especially when multiple TBs are configured.
Smart Images

Figure CN2025093350_12112026_PF_FP_ABST
Abstract
Description
UNSUCCESSFUL HYBRID AUTOMATIC REPEAT REQUEST PROCESS TERMINATION FOR MULTIPLE TRANSPORT BLOCKSFIELD OF THE DISCLOSURE
[0001] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods associated with unsuccessful hybrid automatic repeat request process termination for multiple transport blocks. DESCRIPTION OF THE RELATED TECHNOLOGY
[0002] Wireless communication systems are widely deployed to provide various services, which may involve carrying or supporting voice, text, other messaging, video, data, or other traffic. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication among multiple wireless communication devices including user devices or other devices by sharing the available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, or device transmit power, among other examples) . Such multiple-access RATs are supported by technological advancements that have been adopted in various telecommunication standards, which define common protocols that enable different wireless communication devices to communicate on a local, municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR) . NR, which also may be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . As the demand for connectivity continues to increase, further improvements in NR may be implemented, and other RATs, such as 6G and beyond, may be introduced to enable new applications and facilitate new use cases.
[0003] In some wireless communication networks, devices (for example, a user equipment or a network node) may perform a hybrid automatic repeat request (HARQ) process to improve a reliability of communications exchanged between the devices. For example, a transmitting device may send a transport block (for example, data) to a receiving device, and the receiving device may attempt to decode the data. In cases where the receiving device successfully decodes the data, the receiving device may transmit a HARQ acknowledgement (ACK) message to the transmitting device. In cases where the receiving device fails to successful decode the data, the receiving device may transmit a HARQ negative ACK message to the transmitting device.SUMMARY
[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0005] Some aspects described herein relate to a user equipment (UE) . The UE may include a processing system that includes processor circuitry and code-storing memory circuitry. The processing system may be configured to cause the UE to receive a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The processing system may be configured to cause the UE to transmit, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0006] Some aspects described herein relate to a network node. The network node may include a processing system that includes processor circuitry and code-storing memory circuitry. The processing system may be configured to cause the network node to transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The processing system may be configured to cause the network node to receive, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The method may include transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The method may include receiving, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The apparatus may include means for transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The apparatus may include means for receiving, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0011] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0012] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0013] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, network node, wireless communication device, or processing system as substantially described in the Detailed Description with reference to, and as illustrated by, the accompanying drawings. Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Fig. 1 is a diagram illustrating an example of a wireless communication network.
[0015] Fig. 2 is a diagram illustrating an example associated with identifying unsuccessful terminations of hybrid automatic repeat request (HARQ) processes.
[0016] Fig. 3 is a diagram illustrating an example associated with signaling for unsuccessful HARQ process termination for multiple transport blocks (TBs) .
[0017] Fig. 4 is a diagram illustrating an example associated with no HARQ feedback bundling.
[0018] Fig. 5 is a diagram illustrating an example associated with HARQ feedback bundling.
[0019] Fig. 6 is a diagram illustrating an example associated with HARQ retransmission thresholds.
[0020] Fig. 7 is a diagram illustrating an example associated with timers that start upon transmission of negative HARQ feedback where HARQ feedback bundling is not configured.
[0021] Fig. 8 is a diagram illustrating an example associated with timers that start upon transmission of negative HARQ feedback where HARQ feedback bundling is configured.
[0022] Fig. 9 is a diagram illustrating an example associated with differing new data indicator (NDI) values.
[0023] Fig. 10 is a diagram illustrating an example associated with timers that start upon transmission of HARQ feedback where HARQ feedback bundling is not configured.
[0024] Fig. 11 is a diagram illustrating an example associated with timers that start upon transmission of HARQ feedback where HARQ feedback bundling is configured.
[0025] Fig. 12 is a diagram illustrating an example associated with multi-bit NDI values.
[0026] Fig. 13 is a diagram illustrating examples associated with multi-bit NDI values where HARQ feedback bundling is not configured.
[0027] Fig. 14 is a diagram illustrating an example associated with multi-bit NDI values where HARQ feedback bundling is configured.
[0028] Fig. 15 is a diagram illustrating examples associated with multiple negative acknowledgement (NACK) to acknowledgement ACK errors with unsuccessful decoding of a downlink control information (DCI) message.
[0029] Fig. 16 is a diagram illustrating examples associated with unchanged NDI values.
[0030] Fig. 17 is a diagram illustrating examples associated with unsuccessful HARQ process termination reporting blocks.
[0031] Fig. 18 is a diagram illustrating examples associated with unsuccessful HARQ process termination reporting using bitmaps.
[0032] Fig. 19 is a diagram illustrating examples associated with virtual HARQ process identifiers.
[0033] Fig. 20 is a diagram illustrating an example process performed, for example, at a user equipment (UE) or an apparatus of a UE.
[0034] Fig. 21 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node.
[0035] Fig. 22 is a diagram of an example apparatus for wireless communication.
[0036] Fig. 23 is a diagram of an example apparatus for wireless communication.DETAILED DESCRIPTION
[0037] In response to receiving a hybrid automatic repeat request (HARQ) negative acknowledgement (NACK) message from a receiving device (e.g., a user equipment (UE) ) , a transmitting device (e.g., a network node) may perform a retransmission associated with a transport block (TB) . For example, the transmitting device may retransmit a portion of the TB (for example, corresponding to the portion of the TB that the receiving device was unable to successfully decode) . Additionally, or alternatively, the transmitting device may retransmit the TB using a same or different redundancy version (RV) , such as by using the same or different set of coded bits associated with the TB, which may allow for the receiving device to perform soft combining or incremental redundancy combining. Upon receiving the retransmission from the transmitting device, the receiving device may attempt to decode the TB using a combination of the data received in the initial transmission of the TB and the data received in the retransmission.
[0038] In some cases, the transmitting device may continue to send retransmissions associated with the TB until the transmitting device receives a HARQ acknowledgement (ACK) message from the receiving device (for example, indicating that the receiving device successfully decoded the TB) . In response to receiving the HARQ ACK message from the receiving device, the transmitting device may terminate the HARQ process. To terminate the HARQ process, the transmitting device may discard data associated with the TB (for example, from a buffer that is maintained prior to the termination of the HARQ process) . In some other cases, the transmitting device may terminate the HARQ process without receiving a HARQ ACK message from the receiving device. For example, the transmitting device may terminate the HARQ process after a quantity of retransmissions performed by the transmitting device satisfies (for example, is equal to or greater than) a quantity threshold associated with a quantity of retransmissions.
[0039] In some wireless communication networks, the devices may additionally support certain radio link control (RLC) processes to improve a reliability of communications between devices. The RLC processes may correspond to processes and communications performed at an RLC layer of the devices. In some cases, the receiving device may detect “holes” (for example, may detect one or more RLC service data unit (SDU) segments that the receiving device has failed to decode) . For example, the receiving device may detect holes based on a sequence number associated with the RLC SDU segments, segmentation information associated with the RLC SDU segments, or a segment offset associated with the RLC SDU segments.
[0040] In response to detecting or failing to detect holes associated with the RLC, the receiving device may transmit an RLC NACK or RLC ACK, respectively. In some cases, the receiving device transmitting an RLC NACK may trigger the transmitting device to retransmit one or more segments of the RLC SDU. Additionally, or alternatively, the receiving device transmitting an RLC ACK may trigger the transmitting device to release a buffer (for example, an upper layer buffer) associated with the RLC SDU.
[0041] A receiving device may detect holes as part of an RLC process when the RLC is operating in accordance with an acknowledgement mode in instances where the transmitting device terminates the HARQ process without receiving a HARQ ACK from the receiving device (for example, due to a channel condition between the transmitting and receiving devices, due to a quantity of retransmissions of the TB performed as part of the HARQ process satisfying a threshold, or the like) . In this example, a lower layer of the transmitting device (for example, a physical (PHY) layer) may report the termination of the HARQ process to an upper layer of the transmitting device (for example, the RLC layer) . Here, the transmitting device may be triggered to retransmit the one or more segments of the RLC SDU in response to receiving the indication of the termination of the HARQ process from the lower layer.
[0042] In another example, the receiving device may detect holes as part of an RLC process when the RLC is operating in accordance with the acknowledgement mode as a result of a premature automatic repeat request (ARQ) process initiation. Here, the receiving device may transmit an RLC NACK to the transmitting device in cases where the HARQ process has not been terminated (for example, in an RLC status report) , and may eventually decode the TB via the HARQ process. Additionally, the receiving device may detect holes as part of the RLC process in instances of a NACK to ACK error. For example, if the receiving device transmits a HARQ NACK to the transmitting device and the transmitting device interprets the HARQ NACK as a HARQ ACK, the transmitting device may terminate the HARQ process (for example, may stop transmissions or retransmissions for a TB) .
[0043] In some cases, a receiving device (for example, a UE) may detect NACK to ACK errors based on hole detection and a timer. That is, the UE may be configured to transmit an RLC status report indicating RLC NACKs upon an expiration of the timer. The expiration time of the timer may be configured with a value to decrease a latency associated with the UE detecting and reporting NACK to ACK errors while also avoiding instances where the UE initiates a premature ARQ process (for example, when the UE transmits an RLC NACK associated with a TB and subsequently decodes the TB as part of a HARQ process) . In some cases, increasing an amount of time prior to the expiration of the timer may decrease a likelihood that the UE initiates the premature ARQ process, but may in turn increase a latency associated with the UE detecting the NACK to ACK errors.
[0044] Accordingly, in some approaches, a receiving device (for example, a UE) may detect NACK to ACK errors before an expiration of the timer associated with the UE indicating RLC NACKs. For example, the UE may use lower-layer (e.g., PHY or medium access control (MAC) layer) information, such as information in scheduling downlink control information (DCI) , to detect an unsuccessful termination of a HARQ process (for example, due to a NACK to ACK error) associated with a TB before the expiration of the timer, and report the unsuccessful termination of the HARQ process associated with the TB to a transmitting device (for example, a network node) . For example, if a physical downlink shared channel (PDSCH) communication of a HARQ process identifier and new data indicator (NDI) value remains undecoded while the UE receives DCI that schedules another PDSCH communication with the same HARQ process identifier and a different NDI value, then the UE may report an unsuccessful termination of a HARQ process for that HARQ process identifier to the network node.
[0045] However, these approaches may not enable the UE to detect NACK to ACK errors before the expiration of the timer in examples where multiple TBs are configured. For example, the network node may configure a maximum quantity of TBs that can be scheduled by a single DCI message to be greater than one. The UE may not detect NACK to ACK errors before the expiration of the timer in examples where multiple TBs are configured, because the multiple TBs scheduled by the single DCI message may share the same HARQ process identifier, the single DCI message may be associated with one or more NDI values, and each of the one or more NDI values may correspond to one of the multiple TBs. As a result, in the examples where multiple TBs are configured, the UE may transmit the RLC status report indicating RLC NACKs upon the expiration of the timer, which may lead to premature initiation of ARQ processes or increased latency associated with the UE detecting the NACK to ACK errors.
[0046] Various aspects relate generally to a receiving device (for example, a UE) detecting NACK to ACK errors prior to an expiration of the timer associated with the UE indicating RLC NACKs in examples where multiple TBs are configured. Some aspects more specifically relate to the UE performing lower-layer assisted detection of an unsuccessful termination of a HARQ process (for example, due to a NACK to ACK error) associated with a TB prior to the expiration of the timer in examples where multiple TBs are configured, and reporting the unsuccessful termination of the HARQ process associated with the TB to a transmitting device (for example, a network node) . For example, the UE may detect and report instances where multiple TBs are configured, a TB associated with a HARQ process identifier and TB index is not decoded, and the UE receives another DCI message that schedules another TB associated with the same HARQ process identifier and TB index. In some aspects, the UE may detect such instances by identifying an unsuccessful HARQ process termination event that indicates the unsuccessful termination of the HARQ process for the TB index. In some examples, the network node may initiate an ARQ process (for example, in response to receiving the report from the UE that indicates the unsuccessful termination of the HARQ process) prior to the expiration of the timer.
[0047] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to decrease a latency and signaling overhead associated with communications between devices in examples where multiple TBs are configured. For example, the UE detecting and reporting NACK to ACK errors in examples where multiple TBs are configured prior to the expiration of the timer may decrease the latency associated with initiating RLC retransmissions in instances of NACK to ACK errors without increasing signaling overhead (for example, due to increased instances of the UE initiating the ARQ process prematurely) . Additionally, or alternatively, the described techniques can be used to decrease overhead at the UE by decreasing buffering at the UE (or at another receiving device) in examples where multiple TBs are configured. For example, if a latency associated with receiving missing packets (for example, missing RLC SDUs, missing RLC SDU segments) is reduced by decreasing a delay associated with initiating ARQ processes, the UE can decrease a usage of a high-layer buffer (for example, a buffer at the RLC layer, a buffer at the packet data convergence protocol (PDCP) layer) in cases when in-order delivery of packets is required (for example, such as when the RLC is operating in accordance with the acknowledgement mode) .
[0048] 5G New Radio (NR) may support enhanced mobile broadband (eMBB) access, Internet of Things (IoT) networks or reduced capability (RedCap) device deployments, ultra-reliable low-latency communication (URLLC) applications, or massive machine-type communication (mMTC) , among other examples. To support these and other target verticals, a wireless communication system may be designed to implement a modularized functional infrastructure, a disaggregated and service-based network architecture, network function virtualization, network slicing, multi-access edge computing, millimeter wave (mmWave) technologies including massive multiple-input multiple-output (MIMO) , beamforming, IoT device or RedCap device connectivity and management, industrial connectivity, licensed and unlicensed spectrum access, sidelink and other device-to-device direct communication (for example, cellular vehicle-to-everything (CV2X) communication) , frequency spectrum expansion, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, device aggregation, advanced duplex communication (for example, sub-band full-duplex (SBFD) ) , multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, network energy savings (NES) , low-power signaling and radios, or artificial intelligence or machine learning (AI / ML) , among other examples.
[0049] The foregoing and other technological improvements may support use cases, such as wireless fronthauls, wireless midhauls, wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial or aerial platforms, among other examples.
[0050] The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies or new technologies or support one or more of the foregoing use cases or new use cases.
[0051] Fig. 1 is a diagram illustrating an example of a wireless communication network 100. The wireless communication network 100 may be or may include elements of a 5G network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110. For example, in Fig. 1, the wireless communication network 100 includes multiple network nodes 110, including a network node 110a and a network node 110b (each of which also may be referred to herein simply as a “network node 110” ) . The network nodes 110 may support communications with multiple UEs 120. For example, in Fig. 1, the network nodes 110 support communication with a UE 120a, a UE 120b, and a UE 120c (each of which also may be referred to herein simply as a “UE 120” ) . In some examples, a UE 120 also may communicate with other UEs 120 and a network node 110 also may communicate with a core network and with other network nodes 110.
[0052] The network nodes 110 and the UEs 120 of the wireless communication network 100 communicate using the electromagnetic spectrum, which may be subdivided into various licensed or unlicensed operating bands, frequency ranges, component carriers, or channels that define associated frequencies available for communications. In some examples, each of the network nodes 110 and the UEs 120 may communicate using one or multiple component carriers in one or more operating bands or ranges. Typically, various operating bands are defined as frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles.
[0053] A network node 110 or a UE 120 may include one or more devices, components, or systems that enable communication with other devices, components, or systems of the wireless communication network 100. For example, a UE 120 and a network node 110 may each include one or more chips, system-on-chips (SoCs) , chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. As shown in Fig. 1, each UE 120 includes a processing system 140 and each network node 110 includes a processing system 145. A processing system (for example, the processing system 140 or the processing system 145) includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs) , graphics processing units (GPUs) , neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , or digital signal processors (DSPs) ) , processing blocks, application-specific integrated circuits (ASICs) , programmable logic devices (PLDs) , or other discrete gate or transistor logic or circuitry (any one or more of which may be generally referred to herein individually as a “processor” or collectively as “the processor” or “the processor circuitry” ) . Such processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set. In some other examples, each of a group of processors may be configurable or configured to perform a same set of functions.
[0054] The processing system 140 and the processing system 145 may each include memory circuitry in the form of one or multiple memory devices, memory blocks, memory elements, or other discrete gate or transistor logic or circuitry, each of which may include or implement tangible storage media, such as random-access memory, or read-only memory, or combinations thereof (any one or more of which may be generally referred to herein individually as a “memory” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors. One or more of the memories may individually or collectively store processor-executable code or instructions (such as software) (for example, which may be referred to as “one or more code-storing memories” or “code-storing memory circuitry” ) . For example, “code-storing memory” or “code-storing memory circuitry” refers to memory (or memory circuitry) that is configured to store processor-executable code or instructions. The processor-executable code or instructions, when executed by one or more of the processors, may configure one or more of the processors (or processing circuitry) to perform various functions or operations described herein. Additionally, or alternatively, in some examples, one or more of the processors may be configured to perform various functions or operations described herein without requiring configuration by software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0055] The processing system 140 and the processing system 145 may each include or be coupled with one or more modems (such as a cellular (for example, a 5G or 6G compliant) modem) . In some examples, one or more processors of the processing system 140 or the processing system 145 may include or implement one or more of the modems. The processing system 140 and the processing system 145 also may include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some examples, one or more processors of the processing system 140 or the processing system 145 may include or implement one or more of the radios, RF chains, or transceivers. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by the processing system 140 or by the processing system 145) .
[0056] A network node 110 and a UE 120 may each include one or multiple antennas or antenna arrays. Typical network nodes 110 and UEs 120 may include multiple antennas, which may be organized or structured into one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. As used herein, the term “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. The term “antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters associated with the group of antennas. The term “antenna module” may refer to circuitry including one or more antennas as well as one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device, such as the network node 110 and the UE 120.
[0057] A network node 110 may be, may include, or also may be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, a gNB, an access point (AP) , a transmission reception point (TRP) , a network entity, a network element, a network equipment, or another type of device, component, or system included in a radio access network (RAN) . In various deployments, a network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures) . For example, a network node 110 may be a device or system that implements a part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack) , or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node having an aggregated architecture, meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single physical structure in the wireless communication network 100. For example, an aggregated network node 110 may include a single standalone base station or a single TRP that operates with a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.
[0058] Alternatively, a network node 110 may be a disaggregated network node 110 (sometimes referred to as a disaggregated base station) , having a disaggregated architecture, meaning that the network node 110 may operate with a radio protocol stack that is physically distributed or logically distributed among two or more nodes in the same geographic location or in different geographic locations. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance) , or in a virtualized radio access network (vRAN) , also known as a cloud radio access network (C-RAN) , to facilitate scaling by separating network functionality into multiple units or modules that can be individually deployed.
[0059] The disaggregated network nodes 110 of the wireless communication network 100 may include one or more central units (CUs) , one or more distributed units (DUs) , and one or more radio units (RUs) . A CU may host one or more higher layers, such as a radio resource control (RRC) layer, a PDCP layer, and a service data adaptation protocol (SDAP) layer, among other examples. A CU can communicate with a core network either directly (for example, via a backhaul link) or indirectly (for example, via one or more disaggregated control units, such as a non-real-time (Non-RT) RAN intelligent controller (RIC) associated with a Service Management and Orchestration (SMO) framework or a near-real-time (Near-RT) RIC) . A DU may host one or more of a RLC layer, a MAC layer, or one or more higher PHY layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host a lower PHY layer that is configured to perform functions, such as a fast Fourier transform (FFT) , an inverse FFT (IFFT) , beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. An RU may perform RF processing functions or lower PHY layer functions, such as an FFT, an IFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer split (LLS) . In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120. A CU may communicate with one or more DUs via respective midhaul links, such as via F1 interfaces. Each of the DUs may communicate with one or more RUs via respective fronthaul links. Each of the RUs may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs.
[0060] In some examples, a single network node 110 may include a combination of one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU, a DU, or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples, which may be implemented as a virtual network function, such as in a cloud deployment (for example, an open cloud (O-Cloud) platform) . An SMO framework may support RAN deployment and provisioning of non-virtualized and virtualized network elements.
[0061] In some examples, the wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of various types. Different types of network nodes 110 may generally operate on the same or different operating bands, transmit at different power levels, or serve different coverage areas, each of which may be referred to as or associated with a particular cell 130 (for example, a cell 130a and a cell 130b) .
[0062] The UEs 120 may be physically dispersed throughout the coverage area of the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or also may be referred to as an access terminal, a mobile station, a client device, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, or smart jewelry) , a gaming device, an entertainment device (for example, a music device, a video device, or a satellite radio) , an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device) , an artificially intelligent robot or other device implementing artificial intelligence, a UE function of a network node, or any other suitable device or function that may communicate in the wireless communication network 100.
[0063] Some UEs 120 may be classified according to different categories in association with different complexities or different capabilities. UEs 120 in a first category may be associated with relatively low complexity or cost such as NB-IoT devices or eMTC UEs. UEs 120 in a second category may include higher complexity or cost devices, such as mission-critical IoT devices, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, or premium UEs that are capable of URLLC, eMBB, or precise positioning in the wireless communication network 100. A third category of UEs 120 may have mid-tier complexity or capabilities (for example, capabilities between that of the UEs 120 of the first category and the UEs 120 of the second category) . A UE 120 of the third category may be referred to as a reduced capability UE ( “RedCap UE” ) , a mid-tier UE, an NR-Light UE, or an NR-Lite UE, among other examples.
[0064] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link) . The radio access link may include a downlink and an uplink. “Downlink” (or “DL” ) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL” ) refers to a communication direction from a UE 120 to a network node 110. Downlink and uplink resources may include time domain resources (for example, frames, subframes, slots, and symbols) , frequency domain resources (for example, frequency bands, component carriers (CCs) , subcarriers, resource blocks, and resource elements) , and spatial domain resources (for example, particular transmit directions or beams) .
[0065] Frequency domain resources may be subdivided into bandwidth parts (BWPs) . A BWP may be a block of frequency domain resources (for example, a continuous set of resource blocks (RBs) within a full component carrier bandwidth) that may be configured at a UE-specific level. A UE 120 may be configured with both an uplink BWP and a downlink BWP (which may be the same or different) . Each BWP may be associated with its own numerology (indicating a sub-carrier spacing (SCS) and cyclic prefix (CP) ) . A BWP may be dynamically configured or activated (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) or reconfigured (for example, in real-time or near-real-time) according to changing network conditions in the wireless communication network 100 or specific requirements of one or more UEs 120. An active BWP defines the operating bandwidth of the UE 120 within the operating bandwidth of the serving cell.
[0066] As used herein, a downlink signal may be or include a reference signal, control information, or data. For example, downlink reference signals include a primary synchronization signal (PSS) , a secondary SS (SSS) , an SS block (SSB) (for example, that includes a PSS, an SSS, and a physical broadcast channel (PBCH) ) , a demodulation reference signal (DMRS) , a phase tracking reference signal (PTRS) , a tracking reference signal (TRS) , and a channel state information (CSI) reference signal (CSI-RS) , among other examples. A downlink signal carrying control information or data may be transmitted via a downlink channel. Downlink channels may include one or more control channels for transmitting control information and one or more data channels for transmitting data. Downlink reference signals may be transmitted in addition to, or multiplexed with, downlink control channel communications or downlink data channel communications. A downlink control channel may be specifically used to transmit DCI from a network node 110 to a UE 120. DCI generally contains the information the UE 120 needs to identify RBs in a subsequent subframe and how to decode them, including a modulation and coding scheme (MCS) or RV parameters. Different DCI formats carry different information, such as scheduling information in the form of downlink or uplink grants, slot format indicators (SFIs) , preemption indicators (PIs) , transmit power control (TPC) commands, HARQ information, NDIs, among other examples. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include physical downlink control channels (PDCCHs) , and downlink data channels may include PDSCHs. Control information or data communications may be transmitted on a PDCCH and PDSCH, respectively. For example, a PDCCH can carry DCI, while a PDSCH can carry a MAC control element (MAC-CE) , an RRC message, or user data, among other examples. Each PDSCH may carry one or more TBs of data.
[0067] As used herein, an uplink signal may include a reference signal, control information, or data. For example, uplink reference signals include a sounding reference signal (SRS) , a PTRS, and a DMRS, among other examples. An uplink signal carrying control information or data may be transmitted via an uplink channel. An uplink channel may include one or more control channels for transmitting control information and one or more data channels for transmitting data. Uplink reference signals may be transmitted in addition to, or multiplexed with, uplink control channel communications or uplink data channel communications. An uplink control channel may be specifically used to transmit uplink control information (UCI) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include physical uplink control channels (PUCCHs) , and uplink data channels may include physical uplink shared channels (PUSCHs) . Control information or data communications may be transmitted on a PUCCH and PUSCH, respectively. For example, a PUCCH can carry UCI, while a PUSCH can carry a MAC-CE, an RRC message, or user data, among other examples. UCI can include a scheduling request (SR) , HARQ feedback information (for example, a HARQ ACK indication or a HARQ NACK indication) , uplink power control information (for example, an uplink TPC parameter) , or CSI, among other examples. CSI can include a channel quality indicator (CQI) (indicative of downlink channel conditions to facilitate selection of transmission parameters, such as an MCS, by a network node 110) , a precoding matrix indicator (PMI) , a CSI-RS resource indicator (CRI) (for example, indicative of a beam used to transmit a CSI-RS) , an SS / PBCH resource block indicator (SSBRI) (for example, indicative of a beam used to transmit an SSB) , a layer indicator (LI) , a rank indicator (RI) , or measurement information (for example, a layer 1 (L1) -reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, among other examples) which can be used for beam management, among other examples. Each PUSCH may carry one or more TBs of data.
[0068] The information (for example, data, control information, or reference signal information) transmitted by a network node 110 to a UE 120, or vice versa, may be represented as a sequence of binary bits that are mapped (for example, modulated) to an analog signal waveform (for example, a discrete Fourier transform (DFT) -spread-orthogonal frequency division multiplexing (OFDM) (DFT-s-OFDM) waveform or a CP-OFDM waveform) that is transmitted by the network node 110 or UE 120 over a wireless communication channel. In some examples, the network node 110 or the UE 120 (for example, using the processing system 145 or the processing system 140, respectively) may select an MCS (for example, an order of quadrature amplitude modulation (QAM) , such as 64-QAM, 128-QAM, or 256-QAM, among other examples) for a downlink signal or an uplink signal. For example, the network node 110 may select an MCS for a downlink signal in accordance with UCI received from the UE 120 or may transmit, to the UE 120, an indication of an MCS to be applied for an uplink signal.
[0069] A network node 110 or a UE 120 (such as by using the processing system 145 or the processing system 140, respectively, or one or more coupled modems) may perform signal processing on the information (such as filtering, amplification, modulation, digital-to-analog conversion, an IFFT operation, multiplexing, interleaving, mapping, or encoding, among other examples) to generate a processed signal in accordance with the selected MCS. In some examples, the network node 110 or the UE 120 (for example, using the processing system 145 or the processing system 140, respectively, or one or more coupled encoders or modems) may perform a channel coding operation or a forward error correction (FEC) operation to control errors in transmitted information. For example, the network node 110 or the UE 120 may perform an encoding operation to generate encoded information (such as by selectively introducing redundancy into the information, typically using an error correction code (ECC) , such as a polar code or a low-density parity-check (LDPC) code) . The network node 110 or the UE 120 (for example, using the processing system 145 or one or more modems) may further perform spatial processing (for example, precoding) on the encoded information to generate one or more processed or precoded signals for downlink or uplink transmission, respectively. In some examples, the network node 110a or the UE 120a may perform codebook-based precoding or non-codebook-based precoding. Codebook-based precoding may involve selecting a precoder (for example, a precoding matrix) using a codebook. For example, the network node 110a may provide precoding information indicating which precoder, defined by the codebook, is to be used by the UE 120a. Non-codebook-based precoding may involve selecting or deriving a precoder based on, or otherwise associated with, one or more downlink or uplink signal measurements. The network node 110a or the UE 120a may transmit the processed downlink or uplink signals, respectively, via one or more antennas.
[0070] The network node 110a or the UE 120a may receive uplink signals or downlink signals, respectively, via one or more antennas. The network node 110a or the UE 120a (for example, using the processing system 145 or the processing system 140, respectively, or one or more coupled modems) may perform signal processing (for example, in accordance with the MCS) on the received uplink or downlink signals, respectively (such as filtering, amplification, demodulation, analog-to-digital conversion, an FFT operation, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , to map the received signal (s) to a sequence of binary bits (for example, received information) that estimates the information transmitted by the network node 110 or the UE 120 via the downlink or uplink signals. The network node 110a or the UE 120a (for example, using the processing system 145 or the processing system 140, respectively, or a coupled decoder or one or more modems) may decode the received information (such as by using an ECC, a decoding operation, or an FEC operation) to detect errors or correct bit errors in the received information to generate decoded information. The decoded information may estimate the information transmitted via the downlink or uplink signals.
[0071] In some examples, a UE 120 and a network node 110 may perform MIMO communication. MIMO communication generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. A network node 110 or a UE 120 may communicate using single-user MIMO or multi-user MIMO (MU-MIMO) , the latter of which being used by a network node 110 to simultaneously transmit signals to multiple UEs 120. MIMO techniques may involve spatial multiplexing (multi-layer transmission) or beamforming. To implement beamforming, the amplitudes or phases of signals transmitted via antenna elements may be modulated and shifted relative to each other (such as by manipulating a phase shift, a phase offset, or an amplitude) to generate one or more beams. For example, a network node 110 may generate one or more beams 160a, and a UE 120 may generate one or more beams 160b. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction, a directional reception of a wireless signal from a transmitting device or otherwise in a desired direction, a direction associated with such a directional transmission or directional reception, a set of directional resources associated with a signal transmission or signal reception (for example, an angle of arrival, a horizontal direction, or a vertical direction) , or a set of parameters or resources associated with one or more aspects of a directional signal, among other examples.
[0072] In some examples, a network node 110 or a UE 120 may implement massive MIMO, which may be associated with an increased (for example, “massive” ) quantity of antennas at the network node 110 or at the UE 120, such as in a network implementing mmWave technology, which enables more precise beamforming or reduced interference. In some examples, the wireless communication network 100 may implement multi-TRP (mTRP) operation (including redundant transmission or reception on multiple TRPs) or non-coherent joint transmission (NC-JT) .
[0073] The network node 110 and the UE 120 may establish a communication link or beam pair, and otherwise increase reliability, throughput, signal strength, or other signal properties for MIMO communications, by performing beam management operations, such as an initial beam acquisition operation, a beam refinement operation, or a beam recovery operation. For example, an initial beam acquisition operation may involve the network node 110 transmitting signals (for example, SSBs or other signals) via respective beams (for example, of the beams 160 of the network node 110) and the UE 120 receiving and measuring the signal (s) via respective beams of multiple beams (for example, from the beams 160 of the UE 120) to identify a best beam (or beam pair) for communication between the UE 120 and the network node 110. A beam refinement operation may involve a first device (for example, the UE 120 or the network node 110) transmitting signal (s) via a subset of beams (for example, identified based on, or otherwise associated with, measurements reported as part of one or more other beam management operations) . A second device (for example, the network node 110 or the UE 120) may receive the signal (s) via a single beam (for example, to identify the best beam for communication from the subset of beams) . The beam (s) may be identified or defined via one or more spatial parameters, such as a transmission configuration indicator (TCI) state or a quasi co-location (QCL) parameter, among other examples.
[0074] Some aspects and techniques as described herein may be implemented, at least in part, using an artificial intelligence (AI) program (for example, referred to herein as an “AI / ML model” ) , such as a program that includes a machine learning (ML) model or an artificial neural network (ANN) model. The AI / ML model may be deployed at one or more devices 165 (for example, one or more network nodes 110, one or more UEs 120, one or more servers, or one or more components of a cloud computing network, among other examples) . For example, in a deployment in which AI / ML functionality is performed independently at a device 165, sometimes referred to as “overlay AI / ML, ” the AI / ML model (or an instance or portion of the AI / ML model) may be deployed at a UE 120 (for example, by the processing system 140) , a network node 110 (for example, by the processing system 145) , one or more servers, or one or more components of a cloud computing network, among other examples. Additionally, or alternatively, in a deployment where AI / ML functionality is coordinated between different devices 165, sometimes referred to as “coordinated AI / ML, ” or performed at all device and network layers, sometimes referred to as “native AI / ML, ” the AI / ML model (or an instance of the AI / ML model) may be deployed at multiple devices 165 (for example, a first portion of the AI / ML model may be deployed at a UE 120 and a second portion of the AI / ML model may be deployed at a network node 110) . In other examples of coordinated AI / ML or native AI / ML, a first AI / ML model may be deployed at a UE 120 and a second AI / ML model may be deployed at a network node 110. The AI / ML model (s) may be configured to enhance various aspects of the wireless communication network 100 (for example, to increase privacy, reliability, or efficient use of network bandwidth, or to reduce latency, among other examples) . For example, the AI / ML model (s) may be trained to identify patterns or relationships in data corresponding to the wireless communication network 100, a device, or an air interface, among other examples. The AI / ML model (s) may support operational decisions relating to one or more aspects associated with wireless communications devices, networks, or services.
[0075] Accordingly, in some examples, the AI / ML model (s) may enable AI-as-a-Service (for example, an end-to-end AI / ML service via a user plane) for use cases, such as a self-organizing network (SON) , minimization of drive test (MDT) , quality of experience (QoE) , positioning, sensing, predictive mobility, or traffic prediction, among other examples. In some examples, AI-as-a-Service use cases may include measurement collection reporting by a UE 120, device selection criteria (for example, according to a geographical area where measurements are to be collected or UE capabilities to be used to collected measurements) , or reporting configurations (for example, reporting parameters such as location, time, or sensor information, among other examples) . Additionally, or alternatively, the AI / ML model (s) may enable AI / ML procedures (for example, RAN-triggered service establishment, configuration, inferencing using UE-side or network-side models, performance monitoring or management, or capability signaling, among other examples) . Additionally, or alternatively, the AI / ML model (s) may enable RAN-based AI / ML services via one or more application program interfaces (APIs) or management interfaces for use cases, such as beam management, radio resource monitoring (RRM) relaxation, mobility prediction, load prediction, network energy savings, or coverage and capacity improvements, among other examples.
[0076] In some aspects, the UE 120 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; and transmit, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0077] In some aspects, the network node 110 may include a communication manager 155. As described in more detail elsewhere herein, the communication manager 155 may transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; and receive, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier. Additionally, or alternatively, the communication manager 155 may perform one or more other operations described herein.
[0078] The network node 110, the processing system 145 of the network node 110, the UE 120, the processing system 140 of the UE 120, or any other component (s) of Fig. 1 may implement one or more techniques or perform one or more operations associated with unsuccessful HARQ process termination for multiple TBs, as described in more detail elsewhere herein. For example, the processing system 145 of the network node 110, or the processing system 140 of the UE 120 may perform or direct operations of, for example, process 2000 of Fig. 20, process 2100 of Fig. 21, or other processes as described herein (alone or in conjunction with one or more other processors) . Memory of the network node 110 may store data and program code (or instructions) for the network node 110. In some examples, the memory of the network node 110 may store data relating to a UE 120, such as RRC state information or a UE context. Memory of a UE 120 may store data and program code (or instructions) for the UE 120, such as context information. In some examples, the memory of the UE 120 or the memory of the network node 110 may include a non-transitory computer-readable medium storing a set of instructions for wireless communication. For example, the set of instructions, when executed by one or more processors (for example, of the processing system 145 or the processing system 140) of the network node 110, or the UE 120, may cause the one or more processors to perform process 2000 of Fig. 20, process 2100 of Fig. 21, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, among other examples.
[0079] In some aspects, the UE 120 includes means for receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; or means for transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 150, processing system 140, a radio, one or more RF chains, one or more transceivers, one or more antennas, one or more modems, a reception component (for example, reception component 2202 depicted and described in connection with Fig. 22) , or a transmission component (for example, transmission component 2204 depicted and described in connection with Fig. 22) , among other examples.
[0080] In some aspects, the network node 110 includes means for transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; or means for receiving, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier. The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 155, processing system 145, a radio, one or more RF chains, one or more transceivers, one or more antennas, one or more modems, a reception component (for example, reception component 2302 depicted and described in connection with Fig. 23) , or a transmission component (for example, transmission component 2304 depicted and described in connection with Fig. 23) , among other examples.
[0081] Fig. 2 is a diagram illustrating an example 200 associated with identifying unsuccessful terminations of HARQ processes. As shown in Fig. 2, a transmitting device 205 and a receiving device 210 may communicate with one another. For example, the transmitting device 205 may transmit, to the receiving device 210, the MAC protocol data unit (PDU) 250.
[0082] In some cases, the transmitting device 205 may correspond to a network node 110, the receiving device 210 may correspond to a UE 120, and the transmitting device 205 may transmit communications to the receiving device 210 via a downlink. In some other cases, the transmitting device 205 may correspond to a UE 120, the receiving device 210 may correspond to a network node 110, and the transmitting device 205 may transmit communications to the receiving device 210 via an uplink.
[0083] Both the transmitting device 205 and the receiving device 210 may include an RLC layer 215 and MAC / PHY layers 220 (for example, including a MAC layer, a PHY layer, or both a MAC layer and a PHY layer) . Although not illustrated, the transmitting device 205 and the receiving device 210 may also include additional layers, such as PDCP layers, RRC layers, or SDAP layers. In the example 200, the RLC 215-a of the transmitting device 205 and the RLC layer 215-b of the receiving device 210 may exchange RLC signaling 290. Additionally, the MAC / PHY layers 220-a of the transmitting device 205 and the MAC / PHY layers 220-b of the receiving device 210 may exchange MAC / PHY signaling 275.
[0084] In the example 200, the RLC layer 215-a of the transmitting device 205 may receive the RLC SDU 225 from a PDCP layer of the transmitting device 205. The RLC layers 215 (for example, 215-a and 215-b) may have multiple different modes. In particular, the transmitting device 205 and the receiving device 210 may operate the RLC layers 215 in accordance with a transparent mode, an unacknowledged mode, or an acknowledged mode. In an example where the RLC layer 215-ais operating in accordance with the transparent mode, the receiving device 210 may pass the RLC SDU 225 through the RLC layer 215-a (for example, from the PDCP layer to the MAC layer of the transmitting device 205) as an RLC PDU 245 without additional processing by the RLC layer 215-a. In another example where the RLC layer 215-ais operating in accordance with the unacknowledged mode, the transmitting device 205 may perform segmentation functionality (for example, of the segmentation or resegmentation functionality 235 illustrated in example 200) , but may not perform the ARQ functionality 240. In another example where the RLC layer215-ais operating in accordance with the acknowledged mode, the transmitting device 205 may perform the segmentation or resegmentation functionality 235 and the ARQ functionality 240.
[0085] When operating the RLC layer 215-ain accordance with the acknowledgement mode, the transmitting device 205 may perform the segmentation or resegmentation functionality 235 to fit the RLC SDU 225 into available resources (for example, for transmission) . For example, the transmitting device 205 may segment the RLC SDU 225 to generate multiple RLC SDU segments. The transmitting device 205 may perform re-segmentation functionalities (for example, of the segmentation or resegmentation functionality 235) to support the ARQ functionality 240, where an available payload size may change.
[0086] The RLC layer 215-a of the transmitting device 205 may generate the RLC PDU 245, which may include the RLC SDU 225. In some cases, the RLC PDU 245 may include one or multiple RLC SDUs 225 or one or multiple RLC SDU segments (for example, generated by the segmentation functionality of the segmentation or resegmentation functionality 235) associated with the RLC SDU 225. Each RLC SDU segment in the RLC PDU 245 may include a header that includes a sequence number associated with the RLC SDU segment. Then, the RLC layer 215-amay provide the RLC PDU 245 to the MAC / PHY layers 220-a of the transmitting device, and the MAC / PHY layers 220-amay receive the MAC PDU 250.
[0087] The MAC PDU 250 may correspond to a TB (for example, transmitted from the transmitting device 205 to the receiving device via the MAC / PHY signaling 275) . The MAC PDU 250 may include one or multiple sub-PDUs 255 (for example, MAC SDUs) . Each sub-PDU 255 may include a MAC sub-header 260, an RLC header 265, and an RLC SDU or RLC SDU segment 270. In some examples, the RLC PDU 245 may correspond to the RLC header 265 and the RLC SDU or RLC SDU segment 270 in each sub-PDU 255. The RLC header 265 may include information related to the RLC SDU or RLC SDU segment 270. For example, the RLC header 265 may include a sequence number associated with the RLC SDU or RLC SDU segment 270, segmentation information associated with an RLC SDU segment of the RLC SDU or RLC SDU segments 270, or a segment offset associated with an RLC SDU segment of the RLC SDU or RLC SDU segments 270.
[0088] The MAC / PHY layers 220-a of the transmitting device 205 may transmit, via the MAC / PHY signaling 275, the MAC PDU 250 to the receiving device 210. The MAC / PHY layers 220-b of the receiving device 210 may provide the MAC PDU 250 to the RLC layer 215-b of the receiving device 210. The receiving device 210 may perform a HARQ process associated with the MAC PDU 250. For example, in cases where the receiving device 210 successfully decodes the MAC PDU 250, the receiving device 210 may transmit a HARQ ACK message to the transmitting device 205 via the MAC / PHY signaling 275. Additionally, in cases where the receiving device 210 fails to successfully decode the MAC PDU 250, the receiving device 210 may transmit a HARQ NACK message to the transmitting device 205 via the MAC / PHY signaling 275. In response to receiving a HARQ NACK message from the receiving device 210, the transmitting device 205 may perform a retransmission associated with the MAC PDU 250. For example, the transmitting device 205 may retransmit a portion of the MAC PDU 250 (for example, that is selected based on the portion of the MAC PDU 250 that the receiving device 210 was unable to successfully decode) . Upon receiving the retransmission from the transmitting device 205, the receiving device 210 may attempt to decode the MAC PDU 250 using a combination of the data received in the initial transmission of the TB and the data received in the retransmission.
[0089] In some cases, the transmitting device 205 may continue to send retransmissions associated with the MAC PDU 250 until the transmitting device 205 receives a HARQ ACK message from the receiving device 210 (for example, indicating that the receiving device successfully decodes the MAC PDU 250) . In response to receiving the HARQ ACK message from the receiving device 210, the transmitting device 205 may terminate the HARQ process. In some other cases, the transmitting device 205 may terminate the HARQ process without receiving a HARQ ACK message from the receiving device 210. For example, the transmitting device 205 may terminate the HARQ process after a quantity of retransmissions performed by the transmitting device 205 satisfies (for example, is equal to or greater than) a quantity threshold associated with a quantity of retransmissions.
[0090] In cases where the RLC layer 215-b of the receiving device is operating in accordance with the acknowledgement mode, the receiving device 210 may additionally perform an ARQ process. For example, the RLC layer 215-b of the receiving device 210 may support the ARQ functionality 240. Here, the RLC layer 215-b of the receiving device 210 may have a hole detection functionality 280, which may enable the receiving device 210 to detect holes (for example, to detect one or more RLC SDU segments 270 in a MAC PDU 250 that the receiving device 210 has failed to decode) . In some cases, the receiving device 210 may detect holes based on a sequence number associated with the RLC SDU or RLC SDU segments 270 (for example, included in the RLC header 265) , segmentation information associated with the RLC SDU or RLC SDU segments 270 (for example, included in the RLC header 265, included in the MAC sub-header 260) , or a segment offset associated with the RLC SDU or RLC SDU segments 270 (for example, included in the RLC header 265, included in the MAC sub-header 260) . In some instances, the receiving device 210 may detect the holes with or without assistance from a lower layer (for example, MAC / PHY layers 220-b of the receiving device 210) .
[0091] The receiving device 210 may detect holes associated with a transmission of the MAC PDU 250 based on a timer (for example, a t-Reassembly timer) . For example, the receiving device 210 may identify one or more missing RLC SDUs or RLC SDU segments 270 based on the sequence numbers associated with RLC SDUs or RLC SDU segments 270 that have been successfully received and decoded. The receiving device 210 may initiate the timer in response to identifying that one or more RLC SDUs or RLC SDU segments 270 are missing. If, prior to an expiration of the timer, the receiving device 210 does successfully receive and decode the one or more missing RLC SDUs or RLC SDU segments 270 (for example, as part of a HARQ process associated with the MAC PDU 250) , the receiving device 210 may reset the timer. Additionally, if the receiving device 210 does not successfully receive and decode the one or more missing RLC SDUs or RLC SDU segments 270 prior to the expiration of the timer, the receiving device 210 may generate and transmit the status report 285 to the transmitting device 205.
[0092] In one example, the receiving device may detect holes as part of the RLC process in instances of a HARQ NACK to HARQ ACK error. In this example, the receiving device 210 may transmit a HARQ NACK to the transmitting device 205, and the transmitting device 205 may interpret the HARQ NACK as a HARQ ACK. As a result, the transmitting device 205 may terminate the HARQ process (for example, may stop HARQ transmissions or retransmissions for the MAC PDU 250) .
[0093] The status report 285 may be associated with a timer (for example, a t-StatusProhibit timer) . Here, the receiving device 210 may refrain from transmitting the status report 285 until the timer expires. In some cases, the receiving device 210 waiting until the timer expires to transmit the status report 285 may decrease a periodicity associated with the receiving device 210 sending status reports 285. That is, after the receiving device 210 sends a status report 285, the receiving device 210 may reset and start (for example, initiate) the timer and may be unable to send another status report 4285 until an expiration of the timer. The status report 285 may include RLC ACK or RLC NACK for certain sequence numbers (for example, associated with the MAC PDU 250) .
[0094] The receiving device 210 may transmit a status report 285 in response to a polling request from the transmitting device 205. For example, the transmitting device 205 may include the polling functionality 230 at the RLC layer 215-a. In this example, the transmitting device may transmit, to the receiving device 210 (for example, via the RLC signaling 290, via the MAC / PHY signaling 275) a polling request triggering the receiving device 210 to transmit the status report 285 to the transmitting device 205. The transmitting device 205 may transmit the polling request based on a quantity of MAC PDUs 250 transmitted to the receiving device 210. For example, the transmitting device 205 may transmit the polling request after transmitting a certain quantity of MAC PDUs 250 (for example, as indicated by a variable such as a pollPDU variable) . In another case, the transmitting device 205 may transmit the polling request based on a quantity of bytes transmitted (for example, via one or more MAC PDUs 250) to the receiving device 210. For example, the transmitting device 205 may transmit the polling request after transmitting a certain quantity of bytes (for example, as indicated by a variable such as a pollByte variable) . In some examples, expiration of a timer (e.g., a t-PollRetransmit timer) may prompt the transmitting device 205 to initiate one or more of data retransmissions or poll retransmissions.
[0095] The receiving device 210 may transmit the status report 285 via the MAC / PHY signaling 275 or, in some other cases, via the RLC signaling 290. In response to receiving the status report 285, the transmitting device 205 may perform an ARQ process (for example, using the ARQ functionality 240 of the RLC layer 215-a) . For example, the transmitting device 205 may retransmit any of the RLC SDU or RLC SDU segments 270 that correspond to a sequence number indicated as not successfully received and decoded in the status report 285. In some cases, the transmitting device 205 may continue transmitting retransmissions of any RLC SDUs or RLC SDU segments 270 until the receiving device 210 indicates that the RLC SDUs or RLC SDU segments 270 have been successfully received and decoded (for example, via an RLC ACK for the sequence numbers associated with the RLC SDUs or RLC SDU segments 270) . Additionally, or alternatively, the transmitting device 205 may refrain from transmitting a retransmission of an RLC SDU or RLC SDU segment 270 in instances where a quantity of retransmissions associated with that RLC SDU or RLC SDU segment 270 is greater than a threshold (for example, a maxRetxThreshold) .
[0096] In examples where multiple TBs for downlink spatial multiplexing are configured, a UE may be unable to detect NACK to ACK errors before the expiration of a timer (e.g., the t-Reassembly timer) . The UE may be unable to detect NACK to ACK errors before the expiration of the timer in examples where multiple TBs are configured because the multiple TBs scheduled by the single DCI message may share the same HARQ process identifier, the single DCI message may be associated with one or more NDI values, and each of the one or more NDI values may correspond to a TB of the multiple TBs. For example, the network node 110 may configure multiple TBs using a higher layer parameter maxNrofCodeWordsScheduledByDCI (where a codeword may correspond to a TB) . As a result, in the examples where multiple TBs are configured, the UE may transmit a status report indicating RLC NACKs upon the expiration of the timer, which may lead to premature initiation of ARQ processes or increased latency associated with the UE detecting the NACK to ACK errors. Accordingly, in the example 200, the receiving device 210 (e.g., the UE 120) may, while multiple TBs are configured, detect NACK to ACK errors prior to an expiration of the timer associated with the hole detection functionality 280 (for example, prior to the expiration of the t-Reassembly timer) .
[0097] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with respect to Fig. 2.
[0098] Fig. 3 is a diagram illustrating an example 300 associated with signaling for unsuccessful HARQ process termination for multiple TBs. As shown in Fig. 3, a network node 110 and a UE 120 may communicate with one another.
[0099] As shown by reference number 310, the network node 110 may transmit, and the UE 120 may receive, a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources. For example, the network node 110 may configure the maximum quantity of TBs that can be scheduled by a single DCI message within a single set of time-frequency resources (e.g., for downlink spatial multiplexing with more than one TB) . The network node 110 may configure the maximum quantity of TBs using a higher layer parameter maxNrofCodeWordsScheduledByDCI (where a codeword may correspond to a TB) . In some aspects, the maximum quantity may be greater than one. For example, the network node 110 may configure multi-TB scheduling by setting the higher layer parameter maxNrofCodeWordsScheduledByDCI to more than one.
[0100] As shown by reference number 320, the UE 120 may transmit, and the network node 110 may receive, in accordance with the configuration, an indication of an unsuccessful HARQ process termination associated with a TB index and a HARQ process identifier. The unsuccessful HARQ process termination may be associated with the TB index and the HARQ process identifier in that the network node 110 may terminate the unsuccessful HARQ process for a TB associated with the TB index and the HARQ process identifier. The TB may be associated with the TB index in that the TB index may indicate that the TB is scheduled by the DCI. The TB may be associated with the HARQ process identifier in that the HARQ process identifier may indicate a HARQ process that handles transmission and potential retransmission (s) of the TB.
[0101] In some aspects, the UE 120 may transmit, and the network node 110 may receive, the indication of the unsuccessful HARQ process termination in accordance with the configuration in that the UE 120 may transmit, and the network node 110 may receive, the indication of the unsuccessful HARQ process termination while the configuration is active (e.g., while multi-TB scheduling is configured) . For example, the UE 120 may report a NACK for a TB scheduled by a DCI message that schedules multiple TBs, and, due to a NACK to ACK error, the network node 110 may terminate the unsuccessful HARQ process instead of scheduling retransmission of the TB using the DCI message as part of the HARQ process.
[0102] In some aspects, the UE 120 may transmit, and the network node 110 may receive, the indication of the unsuccessful HARQ process termination responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier. The unsuccessful HARQ process termination event may be associated with the TB index and the HARQ process identifier in that the unsuccessful HARQ process termination event may indicate the unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0103] In some aspects, the unsuccessful HARQ process termination event may include a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value has been decoded. For example, if the maximum quantity of TBs is configured to be greater than one, the UE 120 may detect and report the unsuccessful HARQ process termination event to the network node 110 in examples where the second TB (e.g., data) corresponding to the TB index, the HARQ process identifier, and the second NDI value has not been decoded, and the UE 120 receives the DCI message that schedules the first TB (e.g., other data) corresponding to the same TB index and the same HARQ process identifier but a different NDI value (e.g., the first NDI value) . That is, the first TB may be scheduled for the TB index and the HARQ process identifier, and with a toggled or changed NDI value, before the UE 120 has decoded the second TB corresponding to the same TB index and the same HARQ process identifier. In such examples, the network node 110 may terminate the HARQ process for the TB index unsuccessfully, meaning that no HARQ retransmissions may occur for the second TB. The UE 120 may detect and report the unsuccessful HARQ process termination event per TB index and HARQ process identifier.
[0104] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with respect to Fig. 3.
[0105] Fig. 4 is a diagram illustrating an example 400 associated with no HARQ feedback bundling.
[0106] In some aspects, HARQ feedback bundling across multiple TBs may not be configured. “HARQ feedback bundling” may refer to combining HARQ feedback for multiple TBs into a single feedback message. In examples where HARQ feedback bundling is not configured, HARQ feedback for the multiple TBs may be provided separately. For example, if the maximum quantity of TBs is configured to be greater than one, HARQ feedback bunding is not configured, and one TB is scheduled, then the UE 120 may generate a NACK for an unscheduled TB. The UE 120 may not be configured with HARQ feedback bundling if the network node 110 does not provide a harq-ACK-SpatialBundlingPUCCH parameter to the UE 120. In some examples, for a PDCCH monitoring occasion with a DCI format that schedules PDSCH reception, or having associated HARQ feedback information without scheduling a PDSCH reception, in the active downlink BWP of a serving cell, the UE 120 may receive a PDSCH communication with a first TB, or upon detecting a DCI format having associated HARQ feedback information without scheduling a PDSCH reception, the value of maxNrofCodeWordsScheduledByDCI may be two for at least one configured downlink BWP of at least one serving cell, and the HARQ feedback information may be associated with the first TB. In such examples, the UE 120 may generate a NACK for a second TB if harq-ACK-SpatialBundlingPUCCH is not provided.
[0107] In example 400, harq-ACK-SpatialBundlingPUCCH is not configured. As shown, the DCI message 402 may schedule an initial transmission of a TB 404 and a TB 406. The DCI message 402 may indicate a HARQ identifier 408, an NDI value 410 (e.g., zero) associated with the TB 404, and an NDI value 412 (e.g., zero) associated with the TB 406. However, the UE may be unable to successfully decode the initial transmission of the TB 404 or the initial transmission of the TB 406, and may transmit, to the network node 110, a HARQ NACK 414 for the TB 404 and a HARQ NACK 414 for the TB 406. The HARQ NACK 414 and the HARQ NACK 416 may be separate in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule a retransmission of the TB 404 and the TB 406 (for example, via the DCI message 418, which indicates the same HARQ identifier 408 and NDI values 410 and 412 as the initial transmission of the TBs 404 and 406) . In cases where the UE is unable to successfully decode the TBs 404 and 406 (for example, using a combination of the initial transmission of the TBs 404 and 406 and the retransmission of the TBs 404 and 406) , the UE 120 may transmit a HARQ NACK 420 for the TB 404 and a HARQ NACK 422 for the TB 406. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 422. As a result, the network node 110 may unsuccessfully terminate the HARQ process associated with the TB 406. In some examples, the network node 110 may transmit, and the UE 120 may receive, a DCI message 424 indicating the HARQ identifier 408, the NDI value 410, and an NDI value 426 (e.g., one) associated with the same TB index as the TB 406. Based at least in part on the NDI value 426 being different from the NDI value 412, the UE 120 may detect and report the unsuccessful HARQ process termination for the TB 406.
[0108] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
[0109] Fig. 5 is a diagram illustrating an example 500 associated with HARQ feedback bundling.
[0110] In some aspects, HARQ feedback bundling across multiple TBs may be configured. For example, HARQ feedback for multiple TBs may be bundled by applying a binary AND operation to HARQ feedback bits of the multiple TBs such that one HARQ feedback bit is provided for the multiple TBs. In some examples, if the maximum quantity of TBs is configured to be greater than one, HARQ feedback bunding is configured, and one TB is scheduled, then the UE 120 may generate an ACK for an unscheduled TB. The UE 120 may be configured with HARQ feedback bundling if the network node 110 provides the harq-ACK-SpatialBundlingPUCCH parameter to the UE 120. In some examples, for a PDCCH monitoring occasion with a DCI format that schedules PDSCH reception, or having associated HARQ feedback information without scheduling a PDSCH reception, in the active downlink BWP of a serving cell, the UE 120 may receive a PDSCH communication with a first TB, or upon detecting a DCI format having associated HARQ feedback information without scheduling a PDSCH reception, the value of maxNrofCodeWordsScheduledByDCI may be two for at least one configured downlink BWP of at least one serving cell, and the HARQ feedback information may be associated with the first TB. In such examples, the UE 120 may generate an ACK for a second TB if harq-ACK-SpatialBundlingPUCCH is provided.
[0111] In example 500, harq-ACK-SpatialBundlingPUCCH is configured. As shown, the DCI message 502 may schedule an initial transmission of a TB 504 and a TB 506. The DCI message 502 may indicate a HARQ identifier 508, an NDI value 510 (e.g., zero) associated with the TB 504, and an NDI value 512 (e.g., zero) associated with the TB 506. However, the UE may be unable to successfully decode the initial transmission of the TB 504 or the initial transmission of the TB 506, and may transmit, to the network node 110, a HARQ NACK 514 for the TB 504 and the TB 506. The HARQ NACK 514 may be bundled in accordance with harq-ACK-SpatialBundlingPUCCH being configured. The network node 110 may schedule a retransmission of the TB 504 and the TB 506 (for example, via the DCI message 516, which indicates the same HARQ identifier 508 and NDI values 510 and 512 as the initial transmission of the TBs 504 and 506) . In some examples, the UE 120 may successfully decode the TB 504, and may be unable to successfully decode the TB 506. In some examples, the UE 120 may be unable to successfully decode the TB 504 or the TB 506. In either case, the UE 120 may transmit a HARQ NACK 518 for the TB 504 and the TB 506. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 518, and the network node 110 may transmit, and the UE 120 may receive, a DCI message 520 indicating the HARQ identifier 508, the NDI value 522 (e.g., one) associated with the same TB index as the TB 504, and an NDI value 524 (e.g., one) associated with the same TB index as the TB 506. The UE 120 may, based at least in part on the NDI value 524 being different from the NDI value 512 and the TB 506 not being successfully decoded, detect and report an unsuccessful HARQ process termination for the TB 506. In examples where the UE 120 is also unable to successfully decode the TB 504, the UE 120 may, based at least in part on the NDI value 522 being different from the NDI value 510, detect and report an unsuccessful HARQ process termination for the TB 504. In examples where the UE 120 successfully decodes the TB 504, the UE 120 may, based at least in part on the TB 504 being successfully decoded, refrain from detecting and reporting an unsuccessful HARQ process termination for the TB 504, regardless of the NDI value 522 being different from the NDI value 510.
[0112] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
[0113] Fig. 6 is a diagram illustrating an example 600 associated with HARQ retransmission thresholds.
[0114] As discussed above in connection with Figs. 3-5, the UE 120 may report unsuccessful HARQ process termination due to NACK to ACK errors. However, in some examples, the UE 120 may report unsuccessful HARQ process termination due to the network node 110 ceasing HARQ retransmissions for a TB index upon reaching a HARQ retransmission threshold. Upon receiving an indication of the unsuccessful HARQ process termination, the network node 110 may identify whether the UE 120 transmitted the indication of the unsuccessful HARQ process termination because of a NACK to ACK error or because the network node 110 ceased HARQ retransmissions upon reaching the HARQ retransmission threshold. In either case, an RLC entity of the network node 110 may perform ARQ retransmission. If the network node 110 ceased HARQ retransmissions upon reaching the HARQ retransmission threshold, then the network node 110 need not necessarily wait to receive the indication of the unsuccessful HARQ process termination from the UE 120 to perform the ARQ retransmissions, whereas in the case of a NACK to ACK error, the network node 110 may schedule ARQ retransmission upon receiving the indication of the unsuccessful HARQ process termination from the UE 120. In some examples, the UE 120 may transmit many indications of unsuccessful HARQ process terminations due to the network node 110 ceasing HARQ retransmissions upon reaching the HARQ retransmission threshold, which may consume uplink time and frequency resources even though the network node 110 may perform ARQ retransmission without receiving the indication.
[0115] In some aspects, a quantity of HARQ retransmissions of the second TB may be less than a HARQ retransmission threshold. “HARQ retransmission threshold” may refer to a maximum quantity of times that a TB can be retransmitted in a HARQ process before the HARQ process is considered unsuccessful. In some examples, the network node 110 may transmit, and the UE 120 may receive, a configuration of the HARQ retransmission threshold. For example, the network node 110 may configure the HARQ retransmission threshold using an RRC parameter (e.g., a max_HARQ-ReTx parameter) . In some examples, if the maximum quantity of TBs is configured to be greater than one, and the HARQ retransmission threshold is configured, then the HARQ retransmission threshold may be applied separately for each TB index associated with a HARQ process identifier. In some examples, a single value for the HARQ retransmission threshold may be configured and applied to each TB index associated with a HARQ process identifier. In some examples, separate values for the HARQ retransmission threshold may be configured and applied to respective TB indexes associated with a HARQ process identifier. Additionally, or alternatively, for different HARQ processes, a common value or separate values for the HARQ retransmission threshold may be configured. The UE 120 may report an unsuccessful HARQ process termination for a TB index associated with a HARQ process identifier if the quantity of retransmissions for the TB index with the HARQ process ID and the same NDI value is less than the HARQ retransmission threshold configured for the TB index.
[0116] In example 600, a DCI message 602 may schedule an initial transmission of a TB 604 and a TB 606. The DCI message 602 may indicate a HARQ identifier 608, an NDI value 610 (e.g., zero) associated with the TB 604, and an NDI value 612 (e.g., zero) associated with the TB 606. However, the UE may be unable to successfully decode the initial transmission of the TB 604 or the initial transmission of the TB 606, and may transmit, to the network node 110, a HARQ NACK 614 for the TB 604 and a HARQ NACK 616 for the TB 606. The HARQ NACK 614 and the HARQ NACK 616 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule a retransmission of the TB 604 and the TB 606 (for example, via the DCI message 618, which indicates the same HARQ identifier 608 and NDI values 610 and 612 as the initial transmission of the TBs 604 and 606) . In some examples, the UE 120 may be unable to successfully decode the TB 604 or the TB 606, and may transmit a HARQ NACK 620 for the TB 604 and a HARQ NACK 622 for the TB 606. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 622. The network node 110 may schedule a retransmission of the TB 604 and an initial transmission of a TB 624 (for example, via the DCI message 626, which indicates the same HARQ identifier 608, the same NDI value 610 as the initial transmission of the TB 604, and an NDI value 628 (e.g., one) that is different from the NDI value 612) . The NDI value 628 may correspond to TB 624, and may be associated with the same TB index as the TB 606. In example 600, the UE 120 may be configured with a HARQ retransmission threshold of four for TB 604 and TB 606. Accordingly, based at least in part on the NDI value 628 being different from the NDI value 612, the TB 606 not being successfully decoded, and the quantity of transmissions or retransmissions of the TB 606 (e.g., two) being less than the HARQ retransmission threshold (e.g., four) , the UE 120 may detect and report an unsuccessful HARQ process termination for the TB 606. In some examples, the UE 120 may be unable to successfully decode the TB 604 and, thus, may transmit a HARQ NACK 630 for the TB 604. Additionally, or alternatively, the UE 120 may successfully decode the TB 624, and, thus, may transmit a HARQ ACK 632 for the TB 624.
[0117] A DCI message 634 may schedule a retransmission of the TB 604. The DCI message 602 may indicate the HARQ identifier 608, and the NDI value 610 associated with the TB 604. In some examples, the DCI message 634 may indicate that a TB 636 for the TB index associated with the TBs 606 and 624 is disabled. In some examples, if the maximum quantity of TBs is configured to be greater than one, then one of the TBs can be disabled using scheduling DCI by setting an MCS and RV field to specific values. For example, in cases where a higher-layer parameter maxNrofCodeWordsScheduledByDCI in a PDSCH-config parameter indicates that two-codeword transmission is enabled, then one of the two TBs may be disabled using DCI format 1_1 or 1_3 if an MCS index (IMCS) equals 26 and the RV identifier equals 1 for the corresponding TB. Similarly, if a higher-layer parameter maxNrofCodeWordsScheduledByDCI in a pdsch-ConfigMulticast parameter indicates that two-codeword transmission is enabled, then one of the two TBs may be disabled by DCI format 4_2 if the IMCS equals 26 and the RV identifier equals 1 for the corresponding TB. If the UE 120 is configured with the higher-layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, then either the first or the second TB of all scheduled PDSCHs may be disabled using DCI format 1_1 if the IMCS equals 26 and the RV identifier equals 2 for the corresponding TB of all scheduled PDSCHs. If both TBs are enabled, then the first TB and the second TB may be mapped to a first codeword and a second codeword, respectively. However, if only one TB is enabled, then the enabled TB may always be mapped to the first codeword. In some examples, the UE 120 may be unable to successfully decode the TB 604 and, thus, may transmit a HARQ NACK 638 for the TB 604. Additionally, or alternatively, the UE 120 may transmit a HARQ NACK 640 for the (disabled) TB 636. Because the HARQ retransmission threshold is four, and the TB 604 has been transmitted or retransmitted four times, the network node 110 may cease HARQ retransmissions of the TB 604 upon reaching the HARQ retransmission threshold. Accordingly, the network node 110 may transmit, and the UE 120 may receive, a DCI message 642 that may schedule a transmission of a TB associated with the HARQ identifier 608 and an NDI value 644 that is different from the NDI value 610. Based at least in part on the quantity of transmissions or retransmissions of the TB 604 (e.g., four) being greater than or equal to the HARQ retransmission threshold (e.g., four) , the UE 120 may refrain from detecting and reporting an unsuccessful HARQ process termination for the TB 604, regardless of the NDI value 644 being different from the NDI value 610 and the TB 604 not being successfully decoded.
[0118] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.
[0119] Fig. 7 is a diagram illustrating an example 700 associated with timers that start upon transmission of negative HARQ feedback where HARQ feedback bundling is not configured.
[0120] In some examples, a NACK to ACK error may occur for a TB index such that the network node 110 incorrectly stores information indicating that the TB (e.g., data) associated with the TB index has been decoded. Furthermore, the network node 110 may not transmit another DCI message scheduling another TB associated with the same TB index and HARQ process identifier, but an NDI value different from an NDI value of the TB, for an excessive length of time. Additionally, or alternatively, the UE 120 may be unable to successfully decode the other DCI message. In such examples, the UE 120 may detect the change in NDI values for the TB index and HARQ process identifier after the excessive length of time. As a result, the UE 120 may be unable to detect the NACK to ACK error, or report the unsuccessful termination of the HARQ process, until after the excessive length of time. Thus, such examples may introduce additional latency associated with detection and reporting of the unsuccessful HARQ process termination.
[0121] In some aspects, the unsuccessful HARQ process termination event may include an expiration of a timer associated with the TB index and the HARQ process identifier. The timer may be associated with the TB index and the HARQ process identifier in that the timer may start or stop in response to an event or non-event that occurs for the TB index and the HARQ process. In some examples, the network node 110 may transmit, and the UE 120 may receive, a configuration of one or more such timers associated with one or more TB indexes and HARQ processes (e.g., in examples where the maximum quantity of TBs is configured to be greater than one) . In some examples, a single timer of the one or more timers may be configured and applied to each TB index associated with a HARQ process identifier. In some examples, separate timers may be configured, and each timer may be applied to a given TB index associated with a HARQ process identifier. In some examples, a single timer or separate timers may be configured for different HARQ processes. Based at least in part on the configuration of the one or more timers, the UE 120 may separately maintain the one or more timers for one or more TB indexes and one or more HARQ processes. If a timer for a TB index and HARQ process identifier expires, then the UE 120 may identify that a HARQ process for the TB index and HARQ process identifier has unsuccessfully terminated (e.g., due to a NACK to ACK error) and report the unsuccessful HARQ process termination for the TB index. In some aspects, the timer may start upon transmission of negative HARQ feedback (e.g., a HARQ NACK indicating that a TB associated with the TB index and the HARQ process has not been received) . For example, after transmitting the negative HARQ feedback, the UE 120 may start the timer by setting the timer to an initial starting value of the timer (e.g., an RRC-configured value) . In some aspects, the timer may stop and reset upon reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier (regardless of whether or not the NDI value in the DCI message has changed) . For example, upon receiving the DCI message, the UE 120 may reset the timer to the initial starting value.
[0122] In example 700, a DCI message 702 may schedule an initial transmission of a TB 704 and a TB 706. The DCI message 702 may indicate a HARQ identifier 708, an NDI value 710 (e.g., zero) associated with the TB 704, and an NDI value 712 (e.g., zero) associated with the TB 706. However, the UE 120 may be unable to successfully decode the initial transmission of the TB 704 or the initial transmission of the TB 706, and may transmit, to the network node 110, a HARQ NACK 714 for the TB 704 and a HARQ NACK 716 for the TB 706. The HARQ NACK 714 and the HARQ NACK 716 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. At time 718, the UE 120 may start (or restart) a timer for the TB 704 in response to transmitting the HARQ NACK 714 and start (or restart) a timer for the TB 706 in response to transmitting the HARQ NACK 716. The network node 110 may schedule a retransmission of the TB 704 and the TB 706 (for example, via the DCI message 720, which indicates the same HARQ identifier 708 and NDI values 710 and 712 as the initial transmission of the TBs 704 and 706) . Accordingly, at time 722, the UE 120 may stop and reset the timer for the TB 704 upon receiving the DCI message 720 based at least in part on the DCI message indicating the same HARQ identifier 708 for the TB index associated with the TB 704. Additionally, or alternatively, at time 722, the UE 120 may stop and reset the timer for the TB 706 upon receiving the DCI message 720 based at least in part on the DCI message indicating the same HARQ identifier 708 for the TB index associated with the TB 706.
[0123] In some examples, the UE 120 may be unable to successfully decode the TB 704 or the TB 706, and may transmit a HARQ NACK 724 for the TB 704 and a HARQ NACK 726 for the TB 706. At time 728, the UE 120 may restart the timer for the TB 704 in response to transmitting the HARQ NACK 724 and restart the timer for the TB 706 in response to transmitting the HARQ NACK 726. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 726. The network node 110 may schedule a retransmission of the TB 704 (for example, via the DCI message 730, which indicates the same HARQ identifier 708 and the same NDI value 710 as the initial transmission of the TB 704) . Accordingly, at time 734, the UE 120 may stop and reset the timer for the TB 704 upon receiving the DCI message 730 based at least in part on the DCI message 730 indicating the same HARQ identifier 708 for the TB index associated with the TB 704. In some examples, the DCI message 730 may indicate that a TB 732 for the TB index associated with the TBs 706 is disabled, as discussed above in connection with Fig. 6. In examples where harq-ACK-SpatialBundlingPUCCH is not configured, if a NACK is transmitted for a given TB index of a given HARQ process identifier due to the given TB index being disabled, then the UE 120 may not restart the timer for the given TB index. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 706 based at least in part on the DCI message 730 not indicating the same HARQ identifier 708 for the TB index associated with the TB 706.
[0124] In some examples, the UE 120 may be unable to successfully decode the TB 704, and may transmit a HARQ NACK 736 for the TB 704 and a HARQ NACK 738 for the (disabled) TB 706. At time 740, the UE 120 may restart the timer for the TB 704 in response to transmitting the HARQ NACK 736. The network node 110 may schedule a retransmission of the TB 704 (for example, via the DCI message 742, which indicates the same HARQ identifier 708 and the same NDI value 710 as the initial transmission of the TB 704) . Accordingly, at time 744, the UE 120 may stop and reset the timer for the TB 704 upon receiving the DCI message 742 based at least in part on the DCI message 742 indicating the same HARQ identifier 708 for the TB index associated with the TB 704. In some examples, the DCI message 742 may indicate that a TB 746 for the TB index associated with the TB 706 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 706 based at least in part on the DCI message 742 not indicating the same HARQ identifier 708 for the TB index associated with the TB 706.
[0125] In some examples, the UE 120 may be unable to successfully decode the TB 704, and may transmit a HARQ NACK 748 for the TB 704 and a HARQ NACK 750 for the (disabled) TB 746. At time 752, the UE 120 may restart the timer for the TB 704 in response to transmitting the HARQ NACK 736. At time 754, the timer for the TB 706 may expire prior to the UE 120 detecting a retransmission associated with the TB 706 or prior to the UE 120 detecting a DCI scheduling a TB associated with the same HARQ identifier 708 and TB index as the TB 706. Accordingly, the UE 120 may identify an unsuccessful termination of the HARQ process associated with the TB 706. In some examples, the network node 110 may transmit, and the UE 120 may receive, a DCI message 756, which indicates the same HARQ identifier 708, an NDI value 758 (e.g., one) associated with the TB index for TB 704, and an NDI value 760 (e.g., one) associated with the TB index for TB 706. Accordingly, at time 762, the UE 120 may stop and reset the timer for the TB index associated with TB 704 and the TB index associated with TB 706 upon receiving the DCI message 756 based at least in part on the DCI message 756 indicating the same HARQ identifier 708 and a different NDI value 758 for the TB index associated with the TB 704 and the NDI value 760 for the TB index associated with the TB 706.
[0126] As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.
[0127] Fig. 8 is a diagram illustrating an example 800 associated with timers that start upon transmission of negative HARQ feedback where HARQ feedback bundling is configured.
[0128] In example 800, a DCI message 802 may schedule an initial transmission of a TB 804 and a TB 806. The DCI message 802 may indicate a HARQ identifier 808, an NDI value 810 (e.g., zero) associated with the TB 804, and an NDI value 812 (e.g., zero) associated with the TB 806. However, the UE 120 may be unable to successfully decode the initial transmission of the TB 804 or the initial transmission of the TB 806, and may transmit, to the network node 110, a HARQ NACK 814 for the TB 804 and the TB 806. The HARQ NACK 814 may be bundled in accordance with harq-ACK-SpatialBundlingPUCCH being configured. At time 818, the UE 120 may start (or restart) a timer for the TB 804 and start (or restart) a timer for the TB 806 in response to transmitting the HARQ NACK 814. The network node 110 may schedule a retransmission of the TB 804 and the TB 806 (for example, via the DCI message 820, which indicates the same HARQ identifier 808 and NDI values 810 and 812 as the initial transmission of the TBs 804 and 806) . Accordingly, at time 822, the UE 120 may stop and reset the timer for the TB 804 upon receiving the DCI message 820 based at least in part on the DCI message indicating the same HARQ identifier 808 for the TB index associated with the TB 804. Additionally, or alternatively, at time 822, the UE 120 may stop and reset the timer for the TB 806 upon receiving the DCI message 820 based at least in part on the DCI message indicating the same HARQ identifier 808 for the TB index associated with the TB 806.
[0129] In some examples, the UE 120 may be unable to successfully decode the TB 804 or the TB 806, and may transmit a HARQ NACK 824 for the TB 804 and for the TB 806. At time 828, the UE 120 may restart the timer for the TB 804 and restart the timer for the TB 806 in response to transmitting the HARQ NACK 824. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 824. The network node 110 may schedule an initial transmission of a TB 830 (for example, via the DCI message 832, which indicates the same HARQ identifier 808 and an NDI value 834 (e.g., one) , which may be different from the NDI value 810) . Accordingly, at time 836, the UE 120 may stop and reset the timer for the TB 804 upon receiving the DCI message 832 based at least in part on the DCI message 832 indicating a different NDI value 834 for the TB index associated with the TB 804. Additionally, or alternatively, the UE 120 may identify an unsuccessful termination of the HARQ process associated with the TB 804 based at least in part on the NDI value 834 being different from the NDI value 810. In some examples, the DCI message 832 may indicate that a TB 838 for the TB index associated with the TB 806 is disabled, as discussed above in connection with Fig. 6. In examples where harq-ACK-SpatialBundlingPUCCH is configured, if a NACK is transmitted for both TBs and the TB (e.g., data) for a given TB index is decoded or disabled, then the UE 120 may refrain from restarting the timer for the given TB index. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 838 based at least in part on the DCI message 832 indicating that the TB 838 is disabled.
[0130] In some examples, the UE 120 may be unable to successfully decode the TB 830, and may transmit a HARQ NACK 840 for the TB 830 and for the (disabled) TB 838. At time 842, the UE 120 may restart the timer for the first TB index in response to transmitting the HARQ NACK 840. The network node 110 may schedule an initial transmission of a TB 843 (for example, via the DCI message 844, which indicates the same HARQ identifier 808 and the same NDI value 834 as the initial transmission of the TB 804) . Accordingly, at time 846, the UE 120 may stop and reset the timer for the first TB index upon receiving the DCI message 844 based at least in part on the DCI message 844 indicating the HARQ identifier 808 and the NDI value 834. In some examples, the DCI message 844 may indicate that a TB 848 for the TB index associated with the TB 806 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 806 based at least in part on the DCI message 844 disabling the TB 848.
[0131] In some examples, the UE 120 may be unable to successfully decode the TB 843, and may transmit a HARQ NACK 850 for the TB 843 and for the (disabled) TB 848. At time 852, the UE 120 may restart the timer for the first TB index in response to transmitting the HARQ NACK 850. At time 854, the timer for the TB 806 may expire prior to the UE 120 detecting a retransmission associated with the TB 806 or prior to the UE 120 detecting a DCI scheduling a TB associated with the same HARQ identifier 808 and TB index as the TB 806. Accordingly, the UE 120 may identify an unsuccessful termination of the HARQ process associated with the TB 806. In some examples, the network node 110 may transmit, and the UE 120 may receive, a DCI message 856, which indicates the same HARQ identifier 808, the NDI value 834 (e.g., one) , and an NDI value 858 (e.g., one) associated with the TB index for TB 806. Accordingly, at time 860, the UE 120 may stop and reset the timer for the first TB index and the second TB index upon receiving the DCI message 856 based at least in part on the DCI message 856 indicating the same HARQ identifier 808 for the TB index associated with the TB 804 and the second TB index associated with TB 806.
[0132] As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.
[0133] Fig. 9 is a diagram illustrating an example 900 associated with differing NDI values.
[0134] In some aspects, the TB index may be a first TB index, and the unsuccessful HARQ process termination event may include a reception of a DCI message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first NDI value that is different from a second NDI value associated with the second TB, before the second TB has been decoded. For example, if the maximum quantity of TBs is configured to be greater than one, then the UE 120 may detect and report the unsuccessful HARQ process termination for the first TB index and the HARQ process identifier if the second TB (e.g., data) has not been decoded before receiving the DCI message that schedules the first TB. The DCI message may not schedule the second TB (or any TB associated with the first TB index) . Additionally, or alternatively, the DCI message may indicate the first NDI value, which may correspond to the first TB index and the HARQ process identifier. The first NDI value may differ from the second NDI value, which may have previously corresponded to the first TB index and the HARQ process identifier. For example, the DCI message may change the NDI value for the first TB index.
[0135] In example 900, a DCI message 902 may schedule an initial transmission of a TB 904 and a TB 906. The DCI message 902 may indicate a HARQ identifier 908, an NDI value 910 (e.g., zero) associated with the TB 904, and an NDI value 912 (e.g., zero) associated with the TB 906. However, the UE 120 may be unable to successfully decode the initial transmission of the TB 904 or the initial transmission of the TB 906, and may transmit, to the network node 110, a HARQ NACK 914 for the TB 904 and a HARQ NACK 916 for the TB 906. The HARQ NACK 914 and the HARQ NACK 916 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule a retransmission of the TB 904 and the TB 906 (for example, via the DCI message 920, which indicates the same HARQ identifier 908 and NDI values 910 and 912 as the initial transmission of the TBs 904 and 906) . In some examples, the UE 120 may be unable to successfully decode the TB 904 or the TB 906, and may transmit a HARQ NACK 924 for the TB 904 and a HARQ NACK 926 for the TB 906.
[0136] In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 926. The network node 110 may schedule a retransmission of the TB 904 (for example, via the DCI message 930, which indicates the same HARQ identifier 908 and the same NDI value 910 as the initial transmission of the TB 904) . The DCI message 930 may also indicate that a TB 932 for the TB index associated with the TB 906 is disabled, as discussed above in connection with Fig. 6. The DCI message 930 may also indicate an NDI value 934 (e.g., one) that is associated with the TB index associated with the TB 906 and that is different from the NDI value 912. If the network node 110 does not intend to schedule the TB index associated with the TB 906, and does intend to schedule the TB index associated with the TB 904, then the network node 110 may pre-terminate the HARQ process for the TB 906 using the NDI value 934; by contrast, if the network node 110 were to intend to schedule the TB index associated with the TB 906 but could not due to channel conditions, then the network node 110 may refrain from changing the NDI value from NDI value 912 in the DCI message 930. Accordingly, the UE 120 may identify an unsuccessful HARQ process termination for the TB 906 based at least in part on transmitting the HARQ NACK 926, the NDI value 934 being different from the NDI value 912, and the TB 932 being disabled. In some examples, the UE 120 may be unable to successfully decode the TB 904, and may transmit a HARQ NACK 936 for the TB 904 and a HARQ NACK 938 for the (disabled) TB 906. The network node 110 may schedule a retransmission of the TB 904 (for example, via the DCI message 942, which indicates the same HARQ identifier 908 and the same NDI value 910 as the initial transmission of the TB 904) . In some examples, the DCI message 942 may indicate that a TB 946 for the TB index associated with the TB 906 is disabled, as discussed above in connection with Fig. 6. In some examples, the UE 120 may be unable to successfully decode the TB 904, and may transmit a HARQ NACK 948 for the TB 904 and a HARQ NACK 950 for the (disabled) TB 946.
[0137] As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with respect to Fig. 9.
[0138] Fig. 10 is a diagram illustrating an example 1000 associated with timers that start upon transmission of HARQ feedback where HARQ feedback bundling is not configured.
[0139] In some examples, the UE 120 may fail to decode a DCI message that schedules an initial TB transmission for a TB index and a HARQ process identifier, the UE 120 may report a HARQ NACK, and a NACK to ACK error may occur. Furthermore, the network node 110 may not use the TB index associated with the HARQ process identifier to schedule an initial TB transmission for a long time. Additionally, or alternatively, the UE 120 may be unable to successfully decode one or more DCI messages indicating the same HARQ process identifier and the TB index for scheduling an initial TB transmission. In such examples, the UE 120 may detect a change in NDI values for the TB index and HARQ process identifier after an excessive length of time. As a result, the UE 120 may be unable to detect the NACK to ACK error, or report the unsuccessful termination of the HARQ process, until after the excessive length of time. Thus, such examples may introduce additional latency associated with detection and reporting of the unsuccessful HARQ process termination.
[0140] In some aspects, the unsuccessful HARQ process termination event may include an expiration of a timer associated with the TB index and the HARQ process identifier. The timer may be associated with the TB index and the HARQ process identifier in that the timer may start or stop in response to an event or non-event that occurs for the TB index and the HARQ process. In some examples, the network node 110 may transmit, and the UE 120 may receive, a configuration of one or more such timers associated with one or more TB indexes and HARQ processes (e.g., in examples where the maximum quantity of TBs is configured to be greater than one) . If a timer for a TB index and HARQ process identifier expires, then the UE 120 may identify that a HARQ process for the TB index and HARQ process identifier has unsuccessfully terminated (e.g., due to a NACK to ACK error) and report the unsuccessful HARQ process termination for the TB index and the HARQ process identifier. In some aspects, the timer may start upon transmission of HARQ feedback (e.g., positive HARQ feedback, such as a HARQ ACK indicating that a TB associated with the TB index and the HARQ process has been received) . For example, after transmitting the HARQ feedback, the UE 120 may start the timer by setting the timer to an initial starting value of the timer (e.g., an RRC-configured value) . In some aspects, the timer may stop and reset upon a reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier. For example, upon receiving the DCI message, the UE 120 may reset the timer to the initial starting value.
[0141] In example 1000, a DCI message 1002 may schedule an initial transmission of a TB 1004 and a TB 1006. The DCI message 1002 may indicate a HARQ identifier 1008, an NDI value 1010 (e.g., zero) associated with the TB 1004, and an NDI value 1012 (e.g., zero) associated with the TB 1006. The UE 120 may successfully decode the initial transmission of the TB 1004 and the initial transmission of the TB 1006, and may transmit, to the network node 110, a HARQ ACK 1014 for the TB 1004 and a HARQ ACK 1016 for the TB 1006. The HARQ ACK 1014 and the HARQ ACK 1016 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. At time 1018, the UE 120 may start (or restart) a timer for the TB 1004 in response to transmitting the HARQ ACK 1014 and start (or restart) a timer for the TB 1006 in response to transmitting the HARQ ACK 1016. The network node 110 may schedule an initial transmission of a TB 1020 and the TB 1022 (for example, via a DCI message 1024, which indicates the HARQ identifier 1008, an NDI value 1026 (e.g., one) associated with the TB 1020, and an NDI value 1028 (e.g., one) associated with the TB 1022) .
[0142] In some examples, the UE 120 may be unable to successfully decode the DCI message 1024. As a result, the UE 120 may not receive an indication of the NDI values 1026 or 1028, and may transmit a HARQ NACK 1030 for the TB 1020 and a HARQ NACK 1032 for the TB 1022. In some examples, a NACK to ACK error (e.g., a discontinuous transmission (DTX) to ACK error) may occur with respect to the HARQ NACK 1032. The network node 110 may schedule a retransmission of the TB 1020 (for example, via the DCI message 1034, which indicates the same HARQ identifier 1008 and the same NDI value 1026 as the initial transmission of the TB 1020) . Accordingly, at time 1036, the UE 120 may stop and reset the timer for the TB 1004 upon receiving the DCI message 1034 based at least in part on the DCI message 1034 indicating the same HARQ identifier 1008 for the TB index associated with the TB 1004. In some examples, the DCI message 1034 may indicate that a TB 1038 for the TB index associated with the TB 1006 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 1006 based at least in part on the DCI message 1034 indicating that the TB 1038 for the TB index associated with the TB 1006 is disabled.
[0143] In some examples, the UE 120 may be unable to successfully decode the TB 1020, and may transmit a HARQ NACK 1040 for the TB 1020 and a HARQ NACK 1042 for the (disabled) TB 1038. At time 1044, the UE 120 may restart the timer for the TB 1020 in response to transmitting the HARQ NACK 1040. The network node 110 may schedule a retransmission of the TB 1020 (for example, via the DCI message 1046, which indicates the same HARQ identifier 1008 and the same NDI value 1026 as the initial transmission of the TB 1020) . In some examples, the DCI message 1046 may indicate that a TB 1048 for the TB index associated with the TB 1038 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 1006 based at least in part on the DCI message 1046 indicating that the TB 1048 for the TB index associated with the TB 1006 is disabled. At time 1050, the timer for the TB 1006 may expire prior to the UE 120 detecting a retransmission associated with the TB 1006 or prior to the UE 120 detecting a DCI scheduling a TB associated with the same HARQ identifier 1008 and TB index as the TB 1006. Accordingly, the UE 120 may identify an unsuccessful termination of the HARQ process associated with the TB 1006. In some examples, the UE 120 may be unable to successfully decode the TB 1020, and may transmit a HARQ NACK 1052 for the TB 1020 and a HARQ NACK 1054 for the (disabled) TB 1048.
[0144] As indicated above, Fig. 10 is provided as an example. Other examples may differ from what is described with respect to Fig. 10.
[0145] Fig. 11 is a diagram illustrating an example 1100 associated with timers that start upon transmission of HARQ feedback where HARQ feedback bundling is configured.
[0146] In example 1100, a DCI message 1102 may schedule an initial transmission of a TB 1104 and a TB 1106. The DCI message 1102 may indicate a HARQ identifier 1108, an NDI value 1110 (e.g., zero) associated with the TB 1104, and an NDI value 1112 (e.g., zero) associated with the TB 1106. The UE 120 may successfully decode the initial transmission of the TB 1104 and the initial transmission of the TB 1106, and may transmit, to the network node 110, a HARQ ACK 1114 for the TB 1104 and for the TB 1106. The HARQ ACK 1114 may be bundled in accordance with harq-ACK-SpatialBundlingPUCCH being configured. At time 1118, the UE 120 may start (or restart) a timer for the TB 1104 and start (or restart) a timer for the TB 1106 in response to transmitting the HARQ ACK 1114. The network node 110 may schedule an initial transmission of a TB 1120 and the TB 1122 (for example, via a DCI message 1124, which indicates the HARQ identifier 1108, an NDI value 1126 (e.g., one) associated with the TB 1120, and an NDI value 1128 (e.g., one) associated with the TB 1122) .
[0147] In some examples, the UE 120 may be unable to successfully decode the DCI message 1124. As a result, the UE 120 may not receive an indication of the NDI values 1126 or 1128, and may transmit a HARQ NACK 1130 for the TB 1120 and for the TB 1122. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1130. The network node 110 may schedule a retransmission of the TB 1120 (for example, via the DCI message 1134, which indicates the same HARQ identifier 1108 and the same NDI value 1110 as the initial transmission of the TB 1120) . Accordingly, at time 1136, the UE 120 may stop and reset the timer for the TB 1104 upon receiving the DCI message 1134 based at least in part on the DCI message 1134 indicating the same HARQ identifier 1108 for the TB index associated with the TB 1104. In some examples, the DCI message 1134 may indicate that a TB 1138 for the TB index associated with the TB 1106 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 1106 based at least in part on the DCI message 1134 indicating that the TB 1138 for the TB index associated with the TB 1106 is disabled.
[0148] In some examples, the UE 120 may successfully decode the TB 1120, and may transmit a HARQ ACK 1140 for the TB 1020 and for the (disabled) TB 1038. At time 1144, the UE 120 may restart the timer for the TB 1120 in response to transmitting the HARQ NACK 1140. In examples where HARQ feedback bundling is configured, if the UE 120 transmits a HARQ ACK for both TBs, but the TB (e.g., data) for one of the TB indexes is disabled, then the UE 120 may not restart the timer for the disabled TB index. Accordingly, the UE 120 may refrain from restarting the timer for the TB 1122. The network node 110 may schedule an initial transmission of a TB 1146 (for example, via the DCI message 1148, which indicates the same HARQ identifier 1108 and the same NDI value 1126 as the initial transmission of the TB 1120) . In some examples, the DCI message 1148 may indicate that a TB 1150 for the TB index associated with the TB 1138 is disabled, as discussed above in connection with Fig. 6. Accordingly, the UE 120 may refrain from stopping and resetting the timer for the TB 1106 based at least in part on the DCI message 1148 indicating that the TB 1150 for the TB index associated with the TB 1106 is disabled. At time 1152, the timer for the TB 1106 may expire prior to the UE 120 detecting a retransmission associated with the TB 1106 or prior to the UE 120 detecting a DCI scheduling a TB associated with the same HARQ identifier 1108 and TB index as the TB 1106. Accordingly, the UE 120 may identify an unsuccessful termination of the HARQ process associated with the TB 1106. In some examples, the UE 120 may be unable to successfully decode the TB 1120, and may transmit a HARQ NACK 1154 for the TB 1146 and for the (disabled) TB 1150.
[0149] As indicated above, Fig. 11 is provided as an example. Other examples may differ from what is described with respect to Fig. 11.
[0150] Fig. 12 is a diagram illustrating an example 1200 associated with multi-bit NDI values.
[0151] In some examples, a UE 120 may be unable to successfully decode a DCI message that schedules an initial transmission of a first TB (e.g., data) for a TB index, and the UE 120 may report a HARQ NACK for the TB index. If a NACK to ACK error occurs, then the network node 110 may schedule a second TB associated with the same TB index and the same HARQ identifier. Furthermore, because the UE 120 does not successfully decode the DCI message, the UE 120 may not detect a change in a one-bit NDI value for the TB index, and, thus, may interpret the NDI value as having not changed from a TB received before the first TB. As a result, the UE 120 may not detect or report the unsuccessful termination of the HARQ process associated with the second TB. The probability of an occurrence of such an event may be non-negligible (e.g., on the order of 10-5) .
[0152] In some aspects, the unsuccessful HARQ process termination event may include a reception of a first DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value. A bit width of an NDI field of the first NDI value, and a bit width of an NDI field of the second NDI value, may be greater than one. For example, the first and second NDI values may each be represented by multiple bits. In the examples where multiple TBs are configured, the bit width K of an NDI value for each TB index may be increased from one bit to multiple bits, which may lead to modulo 2k operation (e.g., instead of modulo 2 operation) . In some aspects, a difference between the first NDI value and the second NDI value may be greater than one. For example, upon detecting the second DCI message with the second NDI value indicating that the difference compared to the first DCI message indicating the same HARQ process identifier and the same TB index is greater than one, the UE 120 may report the unsuccessful HARQ process termination for a TB scheduled by an undetected DCI message transmitted between the first and second DCI messages.
[0153] In example 1200, a DCI message 1202 may schedule an initial transmission of a TB 1204 and a TB 1206. The DCI message 1202 may indicate a HARQ identifier 1208, an NDI value 1210 (e.g., zero) associated with the TB 1204, and an NDI value 1212 (e.g., zero) associated with the TB 1206. The UE 120 may successfully decode the initial transmission of the TB 1204 and the initial transmission of the TB 1206, and may transmit, to the network node 110, a HARQ ACK 1214 for the TB 1204 and a HARQ ACK 1216 for the TB 1206. The HARQ ACK 1214 and the HARQ ACK 1216 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule an initial transmission of a TB 1220 and a TB 1222 (for example, via a DCI message 1224, which indicates the HARQ identifier 1208, an NDI value 1226 (e.g., one) associated with the TB 1220, and an NDI value 1228 (e.g., one) associated with the TB 1222) .
[0154] In some examples, the UE 120 may be unable to successfully decode the DCI message 1224. As a result, the UE 120 may not receive an indication of the NDI values 1226 or 1228, and may transmit a HARQ NACK 1230 for the TB 1220 and a HARQ NACK 1232 for the TB 1222. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1232. The network node 110 may schedule a retransmission of the TB 1220 and an initial transmission of a TB 1234 (for example, via the DCI message 1236, which indicates the HARQ identifier 1208, the NDI value 1226 (e.g., one) for the TB 1220, and an NDI value 1238 (e.g., two) for the TB 1234) . In some cases, the NDI value 1238 may include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify the NACK to ACK error in response to a difference between the NDI value 1238 and the NDI value 1212 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1222 associated with the HARQ identifier 1208. Accordingly, the UE may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1222. In some examples, the UE 120 may successfully decode the TB 1220 and may not successfully decode the TB 1234, and, thus, may transmit a HARQ ACK 1240 for the TB 1220 and a HARQ NACK 1242 for the TB 1234.
[0155] As indicated above, Fig. 12 is provided as an example. Other examples may differ from what is described with respect to Fig. 12.
[0156] Fig. 13 is a diagram illustrating examples 1300 and 1301 associated with multi-bit NDI values where HARQ feedback bundling is not configured.
[0157] In example 1300, a DCI message 1302 may schedule an initial transmission of a TB 1304 and a TB 1306. The DCI message 1302 may indicate a HARQ identifier 1308, an NDI value 1310 (e.g., zero) associated with the TB 1304, and an NDI value 1312 (e.g., zero) associated with the TB 1306. The UE 120 may successfully decode the initial transmission of the TB 1304 and the initial transmission of the TB 1306, and may transmit, to the network node 110, a HARQ ACK 1314 for the TB 1304 and a HARQ ACK 1316 for the TB 1306. The HARQ ACK 1314 and the HARQ ACK 1316 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule an initial transmission of a TB 1320 (for example, via a DCI message 1324, which indicates the HARQ identifier 1308 and an NDI value 1326 (e.g., one) associated with the TB 1320. In some examples, the DCI message 1324 may indicate that a TB 1322 for the TB index associated with the TB 1306 is disabled, as discussed above in connection with Fig. 6. The NDI for the TB index associated with the disabled TB may not be used, and, thus, is not shown in Fig. 13.
[0158] In some examples, the UE 120 may be unable to successfully decode the DCI message 1324. As a result, the UE 120 may not receive an indication of the NDI values 1326, and may transmit a HARQ NACK 1330 for the TB 1320 and a HARQ NACK 1332 for the (disabled) TB 1322. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1330. The network node 110 may schedule an initial transmission of a TB 1334 and an initial transmission of a TB 1336 (for example, via the DCI message 1338, which indicates the HARQ identifier 1308, the NDI value 1340 (e.g., two) for the TB 1334, and the NDI value 1326 (e.g., one) for the TB 1336) . In some cases, the NDI value 1340 may include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify the NACK to ACK error in response to a difference between the NDI value 1340 and the NDI value 1310 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1320 associated with the TB index for 1304 and the HARQ identifier 1308. For example, if the NDI value 1340 included one bit, then the NDI value 1340 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1340 as having not changed due to not successfully decoding the DCI message 1324. Because the difference between the NDI value 1340 and the NDI value 1310 is greater than one (e.g., two) , the UE may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1320. In some examples, the UE 120 may successfully decode the TB 1334, and may transmit a HARQ ACK 1341 for the TB 1334. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1336, and may transmit a HARQ NACK 1342 for the TB 1336.
[0159] In example 1301, a DCI message 1344 may schedule an initial transmission of a TB 1346 and a TB 1348. The DCI message 1344 may indicate a HARQ identifier 1308, an NDI value 1310 (e.g., zero) associated with the TB 1346, and an NDI value 1312 (e.g., zero) associated with the TB 1348. The UE 120 may successfully decode the initial transmission of the TB 1346 and the initial transmission of the TB 1348, and may transmit, to the network node 110, a HARQ ACK 1350 for the TB 1346 and a HARQ ACK 1352 for the TB 1348. The HARQ ACK 1350 and the HARQ ACK 1352 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule an initial transmission of a TB 1354 and an initial transmission of a TB 1356 (for example, via a DCI message 1358, which indicates the HARQ identifier 1308, the NDI value 1326 (e.g., one) associated with the TB 1354, and an NDI value 1359 (e.g., one) associated with the TB 1356.
[0160] In some examples, the UE 120 may be unable to successfully decode the DCI message 1358. As a result, the UE 120 may not receive an indication of the NDI value 1326 or the NDI value 1359. Accordingly, the UE 120 may transmit a HARQ NACK 1360 for the TB 1354 and a HARQ NACK 1362 for the TB 1356. In some examples, a first NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1360, and a second NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1362. The network node 110 may schedule an initial transmission of a TB 1364 and an initial transmission of a TB 1366 (for example, via the DCI message 1367, which indicates the HARQ identifier 1308, the NDI value 1340 (e.g., two) for the TB 1364, and an NDI value 1368 (e.g., two) for the TB 1366) . In some cases, the NDI value 1340 and the NDI value 1368 may each include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify the NACK to ACK error for the HARQ NACK 1360 in response to a difference between the NDI value 1340 and the NDI value 1310 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1354 associated with the HARQ identifier 1308. For example, if the NDI value 1340 included one bit, then the NDI value 1340 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1340 as having not changed due to not successfully decoding the DCI message 1358. Because the difference between the NDI value 1340 and the NDI value 1310 is greater than one (e.g., two) , the UE 120 may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1354. Similarly, the UE 120 may identify the NACK to ACK error for the HARQ NACK 1362 in response to a difference between the NDI value 1368 and the NDI value 1312 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1356 associated with the HARQ identifier 1308. For example, if the NDI value 1368 included one bit, then the NDI value 1368 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1368 as having not changed due to not successfully decoding the DCI message 1358. Because the difference between the NDI value 1368 and the NDI value 1312 is greater than one (e.g., two) , the UE 120 may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1356. In some examples, the UE 120 may successfully decode the TB 1364, and may transmit a HARQ ACK 1370 for the TB 1364. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1366, and may transmit a HARQ NACK 1372 for the TB 1366.
[0161] As indicated above, Fig. 13 is provided as an example. Other examples may differ from what is described with respect to Fig. 13.
[0162] Fig. 14 is a diagram illustrating an example 1400 associated with multi-bit NDI values where HARQ feedback bundling is configured.
[0163] In example 1400, a DCI message 1402 may schedule an initial transmission of a TB 1404 and a TB 1406. The DCI message 1402 may indicate a HARQ identifier 1408, an NDI value 1410 (e.g., zero) associated with the TB 1404, and an NDI value 1412 (e.g., zero) associated with the TB 1406. The UE 120 may successfully decode the initial transmission of the TB 1404 and the initial transmission of the TB 1406, and may transmit, to the network node 110, a HARQ ACK 1414 for the TB 1404 and for the TB 1406. The HARQ ACK 1414 may be bundled in accordance with harq-ACK-SpatialBundlingPUCCH being configured. The network node 110 may schedule an initial transmission of a TB 1420 (for example, via a DCI message 1424, which indicates the HARQ identifier 1408 and an NDI value 1426 (e.g., one) associated with the TB 1420) . In some examples, the DCI message 1424 may indicate that a TB 1422 for the TB index associated with the TB 1406 is disabled, as discussed above in connection with Fig. 6. The NDI for the TB index associated with the disabled TB may not be used, and, thus, is not shown in Fig. 14.
[0164] In some examples, the UE 120 may be unable to successfully decode the DCI message 1424. As a result, the UE 120 may not receive an indication of the NDI values 1426, and may transmit a HARQ NACK 1430 for the TB 1420 and for the (disabled) TB 1422. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1430. The network node 110 may schedule an initial transmission of a TB 1434 and an initial transmission of a TB 1436 (for example, via the DCI message 1438, which indicates the HARQ identifier 1408, the NDI value 1440 (e.g., two) for the TB 1434, and the NDI value 1426 (e.g., one) for the TB 1436) . In some cases, the NDI value 1440 may include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify the NACK to ACK error in response to a difference between the NDI value 1440 and the NDI value 1410 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1420 associated with the HARQ identifier 1408. For example, if the NDI value 1440 included one bit, then the NDI value 1440 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1440 as having not changed due to not successfully decoding the DCI message 1424. Because the difference between the NDI value 1440 and the NDI value 1410 is greater than one (e.g., two) , the UE may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1420.
[0165] In example 1401, a DCI message 1444 may schedule an initial transmission of a TB 1446 and a TB 1448. The DCI message 1444 may indicate a HARQ identifier 1408, an NDI value 1410 (e.g., zero) associated with the TB 1446, and an NDI value 1412 (e.g., zero) associated with the TB 1448. The UE 120 may successfully decode the initial transmission of the TB 1446 and the initial transmission of the TB 1448, and may transmit, to the network node 110, a HARQ ACK 1450 for the TB 1446 and for the TB 1448. The HARQ ACK 1450 may be bundled in accordance with harq-ACK-SpatialBundlingPUCCH being configured. The network node 110 may schedule an initial transmission of a TB 1454 and an initial transmission of a TB 1456 (for example, via a DCI message 1458, which indicates the HARQ identifier 1408, the NDI value 1426 (e.g., one) associated with the TB 1454, and an NDI value 1459 (e.g., one) associated with the TB 1456.
[0166] In some examples, the UE 120 may be unable to successfully decode the DCI message 1458. As a result, the UE 120 may not receive an indication of the NDI value 1426 or the NDI value 1459. Accordingly, the UE 120 may transmit a HARQ NACK 1460 for the TB 1454 and for the TB 1456. In some examples, a first NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1460. The network node 110 may schedule an initial transmission of a TB 1464 and an initial transmission of a TB 1466 (for example, via the DCI message 1467, which indicates the HARQ identifier 1408, the NDI value 1440 (e.g., two) for the TB 1464, and an NDI value 1468 (e.g., two) for the TB 1466) . In some cases, the NDI value 1440 and the NDI value 1468 may each include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify the NACK to ACK error for the HARQ NACK 1460 in response to a difference between the NDI value 1440 and the NDI value 1410 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1454 associated with the HARQ identifier 1408. For example, if the NDI value 1440 included one bit, then the NDI value 1440 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1440 as having not changed due to not successfully decoding the DCI message 1458. Because the difference between the NDI value 1440 and the NDI value 1410 is greater than one (e.g., two) , the UE 120 may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1420. Similarly, the UE 120 may identify the NACK to ACK error for the HARQ NACK 1460 in response to a difference between the NDI value 1468 and the NDI value 1412 being greater than one (for example, being two or more) . In particular, the difference being greater than one may indicate, to the UE 120, that the UE 120 has not successfully decoded at least the TB 1456 associated with the HARQ identifier 1408. For example, if the NDI value 1468 included one bit, then the NDI value 1468 would be equal to zero instead of two, and the UE 120 would interpret the NDI value 1468 as having not changed due to not successfully decoding the DCI message 1458. Because the difference between the NDI value 1468 and the NDI value 1412 is greater than one (e.g., two) , the UE 120 may transmit an indication of an unsuccessful termination of a HARQ process associated with the TB 1456.
[0167] As indicated above, Fig. 14 is provided as an example. Other examples may differ from what is described with respect to Fig. 14.
[0168] Fig. 15 is a diagram illustrating examples 1500 and 1501 associated with multiple NACK to ACK errors with unsuccessful decoding of a DCI message.
[0169] In some aspects, the detection of the unsuccessful HARQ process termination event may be based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded. For example, the UE 120 may report a quantity of unsuccessful HARQ process terminations that is equal to the difference between the first NDI value and the second NDI value in examples where the first TB is not decoded. In some examples, a NACK to ACK error occurs, followed by a DCI message that is not successfully decoded by the UE 120, followed by another NACK to ACK error associated with the DCI message. For example, a HARQ process may terminate unsuccessfully for two consecutive TBs associated with the same HARQ process identifier. In such examples, the UE 120 may detect both of the NACK to ACK errors for a given TB index based at least in part on the difference being greater than one. For example, if the bit width of the first and second NDI values is two, then the UE 120 may detect a difference of two (e.g., the first NDI value may be zero, and the second NDI value may be two) . Thus, the UE 120 may report both unsuccessful HARQ process terminations. In some examples, the UE 120 may detect the difference as a gap k in NDI values (e.g., k may be greater than one, such as two) . In some examples, the gap k in NDI values for a given TB index may be based at least in part on a DCI message that scheduled a TB for the given TB index. Additionally, or alternatively, the gap k in NDI values may be iterated even if a DCI message does not schedule the given TB index (e.g., in examples where the network node 110 does not intend to schedule the given TB index) . As discussed in greater detail in connection with example 1500 below, if the UE 120 has not decoded the TB (e.g., data corresponding to the TB index for a previous NDI value) , then the UE 120 may report k unsuccessful HARQ process termination events, corresponding to the k-1 undetected NDI values and the previous NDI value associated with a TB for which a HARQ NACK is transmitted. As discussed in greater detail in connection with example 1501 below, if the UE 120 has decoded the TB (e.g., data corresponding to the TB index for a previous NDI value) , then the UE 120 may report k-1 unsuccessful HARQ process termination events, corresponding to the k-1 undetected NDI values.
[0170] In example 1500, a DCI message 1502 may schedule an initial transmission of a TB 1504 and a TB 1506. The DCI message 1502 may indicate a HARQ identifier 1508, an NDI value 1510 (e.g., zero) associated with the TB 1504, and an NDI value 1512 (e.g., zero) associated with the TB 1506. The UE 120 may successfully decode the initial transmission of the TB 1504 but not the initial transmission of the TB 1506, and may transmit, to the network node 110, a HARQ ACK 1514 for the TB 1504 and a HARQ NACK 1516 for the TB 1506. The HARQ ACK 1514 and the HARQ NACK 1516 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 1516. The network node 110 may schedule an initial transmission of a TB 1520 (for example, via a DCI message 1524, which indicates the HARQ identifier 1508, an NDI value 1526 (e.g., one) associated with the TB 1520, and an NDI value 1528 (e.g., one) associated with the TB 1522.
[0171] In some examples, the UE 120 may be unable to successfully decode the DCI message 1524. As a result, the UE 120 may not receive an indication of the NDI values 1526, and may transmit a HARQ NACK 1530 for the TB 1520 and a HARQ NACK 1532 for the TB 1522. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1532. The network node 110 may schedule a retransmission of the TB 1520 and an initial transmission of a TB 1536 (for example, via the DCI message 1538, which indicates the HARQ identifier 1508, the NDI value 1526 (e.g., one) for the TB 1520, and the NDI value 1540 (e.g., one) for the TB 1536) . In some cases, the NDI value 1540 may include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify and report the NACK to ACK errors associated with the HARQ NACK 1516 and the HARQ NACK 1532 in response to the difference between the NDI value 1540 and the NDI value 1512 being equal to two and the UE having not successfully decoded the TB 1506. In some examples, the UE 120 may successfully decode the TB 1520, and may transmit a HARQ ACK 1542 for the TB 1520. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1536, and may transmit a HARQ NACK 1544 for the TB 1536.
[0172] In example 1501, a DCI message 1546 may schedule an initial transmission of a TB 1548 and a TB 1550. The DCI message 1546 may indicate a HARQ identifier 1508, an NDI value 1510 (e.g., zero) associated with the TB 1548, and an NDI value 1512 (e.g., zero) associated with the TB 1550. The UE 120 may successfully decode the initial transmission of the TB 1548 and the initial transmission of the TB 1550, and may transmit, to the network node 110, a HARQ ACK 1552 for the TB 1548 and a HARQ ACK 1554 for the TB 1550. The HARQ ACK 1552 and the HARQ ACK 1554 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule an initial transmission of a TB 1556 and an initial transmission of a TB 1558 (for example, via a DCI message 1559, which indicates the HARQ identifier 1508, an NDI value 1526 (e.g., one) associated with the TB 1556, and an NDI value 1560 (e.g., one) associated with the TB 1558.
[0173] In some examples, the UE 120 may be unable to successfully decode the DCI message 1559. As a result, the UE 120 may not receive an indication of the NDI values 1526 or 1560, and may transmit a HARQ NACK 1562 for the TB 1556 and a HARQ NACK 1564 for the TB 1558. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1564. The network node 110 may schedule a retransmission of the TB 1556 and an initial transmission of a TB 1566 (for example, via the DCI message 1568, which indicates the HARQ identifier 1508, the NDI value 1526 (e.g., one) for the TB 1556, and an NDI value 1570 (e.g., two) for the TB 1566) . In some cases, the NDI value 1570 may include more than one bit (for example, may include K bits, where K > 1 (e.g., K = 2) ) . Here, the UE 120 may identify and report the NACK to ACK error associated with the HARQ NACK 1564 in response to the difference between the NDI value 1540 and the NDI value 1512 being equal to two and the UE having successfully decoded TB 1550. In some examples, the UE 120 may successfully decode the TB 1556, and may transmit a HARQ ACK 1572 for the TB 1556. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1566, and may transmit a HARQ NACK 1574 for the TB 1566.
[0174] As indicated above, Fig. 15 is provided as an example. Other examples may differ from what is described with respect to Fig. 15.
[0175] Fig. 16 is a diagram illustrating examples 1600 and 1601 associated with unchanged NDI values.
[0176] In some aspects, the unsuccessful HARQ process termination event may include a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and an NDI value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded. For example, in cases where multiple TBs are configured, the UE 120 may report an unsuccessful HARQ process termination if the second TB is decoded (e.g., and the UE 120 transmits a HARQ ACK) , but the NDI value for the first TB (e.g., as indicated in the DCI message) is unchanged. For example, the NDI value being the same for the second TB and the first TB may indicate an unsuccessful HARQ process termination for the second TB.
[0177] In example 1600, a DCI message 1602 may schedule an initial transmission of a TB 1604 and a TB 1606. The DCI message 1602 may indicate a HARQ identifier 1608, an NDI value 1610 (e.g., zero) associated with the TB 1604, and an NDI value 1612 (e.g., zero) associated with the TB 1606. The UE 120 may successfully decode the initial transmission of the TB 1604 and the initial transmission of the TB 1606, and may transmit, to the network node 110, a HARQ ACK 1614 for the TB 1604 and a HARQ ACK 1616 for the TB 1606. The HARQ ACK 1614 and the HARQ ACK 1616 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule an initial transmission of a TB 1618 and an initial transmission of a TB 1620 (for example, via a DCI message 1622, which indicates the HARQ identifier 1608, an NDI value 1624 (e.g., one) associated with the TB 1618, and an NDI value 1626 (e.g., one) associated with the TB 1620.
[0178] In some examples, the UE 120 may be unable to successfully decode the DCI message 1622. As a result, the UE 120 may not receive an indication of the NDI values 1624 or 1626, and may transmit a HARQ NACK 1628 for the TB 1618 and a HARQ NACK 1630 for the TB 1620. In some examples, a NACK to ACK error (e.g., a DTX to ACK error) may occur with respect to the HARQ NACK 1630. The network node 110 may schedule a retransmission of the TB 1618 and an initial transmission of a TB 1632 (for example, via the DCI message 1634, which indicates the HARQ identifier 1608, the NDI value 1624 (e.g., one) for the TB 1618, and an NDI value 1612 (e.g., zero) for the TB 1632) . Thus, the UE 120 receives two consecutive DCI messages 1602 and 1634 with the same NDI value 1612 for the same TB index and HARQ identifier 1608, and the TB 1606 associated with the same TB index and HARQ process identifier scheduled by the previously received DCI message 1602 has been decoded, which indicates that a NACK to ACK error occurred for the TB index and the HARQ process identifier. Accordingly, the UE 120 may report an unsuccessful HARQ termination for the TB 1620. In some examples, the UE 120 may successfully decode the TB 1618, and may transmit a HARQ ACK 1636 for the TB 1618. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1632, and may transmit a HARQ NACK 1638 for the TB 1632.
[0179] In some aspects, a first MCS associated with the first TB may be different from a second MCS of the second TB or a reserved MCS, a first TB size (TBS) associated with the first TB may be different from a second TBS of the second TB, or the first TB may be associated with a redundancy version (RV) of zero. An MCS may be associated with a TB in that the MCS may be used to modulate and encode the TB. In some examples, the second MCS or the reserved MCS may not be used for the same TB index in the DCI message. A TBS may be associated with a TB in that a TB may have the TBS. In some examples, the UE 120 may identify, based at least in part on one or more parameters in the DCI message, that the first TBS is not the same as the second TBS of the previous TB corresponding to the same TB index (e.g., the second TB) . The first TB may be associated with an RV of zero in that the first TB may be transmitted with the RV of zero. In some examples, the DCI message may indicate RV=0 for the TB index of the first and second TBs. The first MCS being different from the second MCS or the reserved MCS, the first TBS being different from the second TBS, and the first TB being associated with the RV of zero, may be conditions that enable the UE 120 to detect scenarios where a NACK to ACK error has not occurred. As discussed in greater detail in connection with example 1601, the UE 120 may use these conditions to refrain from reporting an unsuccessful HARQ process termination in scenarios where an ACK to NACK error has occurred. For example, in the event of an ACK to NACK error, the network node 110 may schedule a HARQ retransmission of a TB with the same TBS as an initial transmission of the TB. If the UE 120 detects a NACK to ACK error using one or more of these conditions, then the UE 120 may report the unsuccessful HARQ process termination and refrain from soft combining the first TB with the second TB.
[0180] In example 1601, a DCI message 1640 may schedule an initial transmission of a TB 1642 and a TB 1644. The DCI message 1640 may indicate a HARQ identifier 1608, an NDI value 1610 (e.g., zero) associated with the TB 1642, and an NDI value 1612 (e.g., zero) associated with the TB 1644. The UE 120 may successfully decode the initial transmission of the TB 1642 and the initial transmission of the TB 1644, and may transmit, to the network node 110, a HARQ ACK 1646 for the TB 1642 and a HARQ ACK 1648 for the TB 1644. The HARQ ACK 1646 and the HARQ ACK 1648 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. In some examples, an ACK to NACK error may occur with respect to the HARQ ACK 1648. The network node 110 may schedule an initial transmission of a TB 1650 and a retransmission of the TB 1644 (for example, via a DCI message 1652, which indicates the HARQ identifier 1608, an NDI value 1624 (e.g., one) associated with the TB 1650, and an NDI value 1612 (e.g., zero) associated with the TB 1644. Thus, the DCI message 1652 includes the same NDI values for the same TB indexes as the DCI message 1634, even though in example 1601 the TB 1644 was successfully decoded and in example 1600 the TB 1620 was not.
[0181] Applying one or more of the conditions discussed above may help the UE 120 to identify that example 1601 involves an ACK to NACK error and, thus, does not warrant reporting an unsuccessful HARQ process termination. For example, the UE 120 may refrain from identifying an unsuccessful termination of a HARQ process associated with the TB 1644 based at least in part on an MCS of the TB 1644 indicated by the DCI message 1652 being the same as an MCS of the TB 1644 indicated by the DCI message 1640 or the reserved MCS. Additionally, or alternatively, the UE 120 may refrain from identifying an unsuccessful termination of a HARQ process associated with the TB 1644 based at least in part on a TBS of the TB 1644 indicated by the DCI message 1652 being the same as a TBS of the TB 1644 indicated by the DCI message 1640. Additionally, or alternatively, the UE 120 may refrain from identifying an unsuccessful termination of a HARQ process associated with the TB 1644 based at least in part on an RV of the TB 1644 indicated by the DCI message 1652 being zero. In some examples, the UE 120 may successfully decode the TB 1650, and may transmit a HARQ ACK 1654 for the TB 1650. Additionally, or alternatively, the UE 120 may not successfully decode the TB 1644, and may transmit a HARQ NACK 1656 for the TB 1644.
[0182] As indicated above, Fig. 16 is provided as an example. Other examples may differ from what is described with respect to Fig. 16.
[0183] Fig. 17 is a diagram illustrating examples 1700 and 1701 associated with unsuccessful HARQ process termination reporting blocks.
[0184] In some aspects, the indication of the unsuccessful HARQ process termination may include a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier. The block may be a set of one or more unsuccessful HARQ process termination fields. The block may be associated with the unsuccessful HARQ process termination in that the block may carry information related to the unsuccessful HARQ process termination, such as the TB index and the HARQ process identifier. For example, if multiple TBs are configured, then the UE 120 may transmit, and the network node 110 may receive, a report that includes one or more such blocks, where each block corresponds to a different unsuccessful HARQ process termination for a given TB index and a given HARQ process identifier.
[0185] In some aspects, the indication of the unsuccessful HARQ process termination may include one or more of a component carrier index associated with the unsuccessful HARQ process termination event, an NDI value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event. The component carrier index may be associated with the unsuccessful HARQ process termination event in that the unsuccessful HARQ process termination event may have occurred for a TB transmitted in a component carrier corresponding to the component carrier index. For example, the block may include a component carrier index in examples where the UE 120 is configured with multiple component carriers. The NDI value may be associated with the unsuccessful HARQ process termination event in that the NDI value may be associated with a TB for which the unsuccessful HARQ process termination event is reported. The time stamp may be associated with the unsuccessful HARQ process termination event in that the time stamp may indicate a time at or near the unsuccessful HARQ process termination event. The time stamp may be a slot number, a subframe number, a system frame number, or the like. In some examples, as discussed in greater detail below in connection with example 1701 the time stamp may indicate one or more of: a slot number at which a DCI message is decoded which results in detecting the unsuccessful HARQ process termination event; a slot number of a NACK transmission that the UE 120 suspects may have been decoded as an ACK by the network node 110; a slot number of a previous DCI message or a previous PDSCH communication corresponding to the latest NDI for the HARQ process identifier before the new DCI that resulted in detecting the unsuccessful HARQ process termination event; or a slot number at which the unsuccessful HARQ process termination event is reported for the first time.
[0186] In example 1700, a block indicates a component carrier index 1702, a HARQ process identifier 1704, a TB index 1706, an NDI value 1708, and a time stamp 1710. The block may be associated with an unsuccessful HARQ process termination event. As noted, the UE 120 may report multiple such blocks corresponding to respective unsuccessful HARQ process termination events. Examples of times that may be indicated by the time stamp 1710 are provided in example 1701.
[0187] In example 1701, a DCI message 1712 may schedule an initial transmission of a TB 1714 and a TB 1716. The DCI message 1712 may indicate a HARQ identifier 1718, an NDI value 1720 (e.g., zero) associated with the TB 1714, and an NDI value 1722 (e.g., zero) associated with the TB 1716. However, the UE 120 may be unable to successfully decode the initial transmission of the TB 1714 or the initial transmission of the TB 1716, and may transmit, to the network node 110, a HARQ NACK 1724 for the TB 1714 and a HARQ NACK 1726 for the TB 1716. The HARQ NACK 1724 and the HARQ NACK 1726 may not be bundled in accordance with harq-ACK-SpatialBundlingPUCCH not being configured. The network node 110 may schedule a retransmission of the TB 1714 and the TB 1716 (for example, via the DCI message 1730, which indicates the same HARQ identifier 1718 and NDI values 1720 and 1722 as the initial transmission of the TBs 1714 and 1716) . In some examples, the UE 120 may be unable to successfully decode the TB 1714 or the TB 1716, and may transmit a HARQ NACK 1734 for the TB 1714 and a HARQ NACK 1736 for the TB 1716. In some examples, a NACK to ACK error may occur with respect to the HARQ NACK 1736. Accordingly, the network node 110 may transmit a DCI message 1740 that schedules a retransmission of the TB 1714 and an initial transmission of another TB index corresponding to TB 1716. The DCI message 1740 may indicate the HARQ identifier 1718, the NDI value 1720 (e.g., zero) for the TB 1714, and an NDI value 1742 (e.g., one) for the other TB. In some examples, the UE 120 may transmit a report 1744 indicating an unsuccessful HARQ process termination based at least in part on detecting the NACK to ACK error in accordance with aspects described herein.
[0188] In some examples, the time stamp 1710 may indicate a time 1746 at which DCI (e.g., the DCI message 1730) corresponding to a most recent NDI value for the HARQ process identifier before DCI that resulted in detecting the unsuccessful HARQ process termination event (e.g., the DCI message 1740) is transmitted, received, or decoded. In some examples, the time stamp 1710 may indicate a time 1748 at which a PDSCH communication corresponding to a most recent NDI value for the HARQ process identifier before DCI that resulted in detecting the unsuccessful HARQ process termination event (e.g., the TB 1716) is transmitted, received, or decoded. In some examples, the time stamp 1710 may indicate a time 1750 at which the NACK transmission that was decoded as an ACK by the network node 110 (e.g., the HARQ NACK 1736) is transmitted, received, or decoded. In some examples, the time stamp 1710 may indicate a time 1752 at which a DCI message that results in detecting the unsuccessful HARQ process termination event (e.g., the DCI message 1740) is transmitted, received, or decoded. In some examples, the time stamp 1710 may indicate a time 1754 at which the unsuccessful HARQ process termination event is reported for the first time (e.g., a time at which the report 1744 is transmitted, received, or decoded) .
[0189] As indicated above, Fig. 17 is provided as an example. Other examples may differ from what is described with respect to Fig. 17.
[0190] Fig. 18 is a diagram illustrating examples 1800 and 1801 associated with unsuccessful HARQ process termination reporting using bitmaps.
[0191] In some aspects, the indication of the unsuccessful HARQ process termination may include a bitmap associated with a plurality of TB indexes and a plurality of HARQ process identifiers. The bitmap may be associated with the plurality of TB indexes and the plurality of HARQ process identifiers in that the bitmap may indicate, for each of the plurality of TB indexes and the plurality of HARQ process identifiers, whether or not an unsuccessful HARQ process termination occurred. In some aspects, the bitmap may include a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit may indicate that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier. The unsuccessful HARQ process termination may be associated with the TB index and the HARQ process identifier in that the unsuccessful HARQ process termination may have occurred for the TB index and the HARQ process identifier. In some examples, a value of the bit being zero may indicate that the unsuccessful HARQ process termination occurred, and a value of the bit being one may indicate that the unsuccessful HARQ process termination did not occur. In some examples, the UE 120 may transmit, and the network node 110 may receive, in addition to the bitmap, an indication of one or more of the component carrier (s) , NDI value (s) , or time stamp (s) associated with the unsuccessful HARQ process termination (s) , as discussed above in connection with Fig. 17.
[0192] In some aspects, the bitmap may include a set of consecutive bit positions corresponding to the TB index. For example, the bitmap may be mapped to HARQ process identifiers and TB indexes such that the HARQ process identifiers corresponding to a first TB index are placed before the HARQ process identifiers corresponding to a second TB index. As shown in example 1800, the bitmap 1810 may be for HARQ process identifiers corresponding to the first TB index, and the bitmap 1820 may be for HARQ process identifiers corresponding to the second TB index. For example, the four “0” bits in the bitmap 1810 may indicate that an unsuccessful HARQ process termination occurred for the first TB index for HARQ process identifiers one, three, seven, and nine, respectively. Additionally, or alternatively, the four “0” bits in the bitmap 1820 may indicate that an unsuccessful HARQ process termination occurred for the second TB index for HARQ process identifiers two, five, seven, and eleven, respectively. As shown, the UE 120 may also report an NDI value and time stamp for each unsuccessful HARQ process termination. Examples of times that may be indicated by the time stamps are provided in example 1701 (Fig. 17) .
[0193] In some aspects, the bitmap may include a set of alternating bit positions corresponding to the TB index. For example, the bitmap may be mapped to HARQ process identifiers and TB indexes such that bits mapped to the HARQ process identifiers corresponding to a first TB index and bits mapped to the HARQ process identifiers corresponding to a second TB index are interlaced within the bitmap. As shown in example 1801, the bitmap 1830 may be for HARQ process identifiers corresponding to the first TB index, and the bitmap 1840 may be for HARQ process identifiers corresponding to the second TB index. For example, all “0” bits, other than bit 1850, may indicate that an unsuccessful HARQ process termination occurred for the second TB index for HARQ process identifiers zero, one, three, four, ten, eleven, and thirteen, respectively. Additionally, or alternatively, the bit 1850 may indicate that an unsuccessful HARQ process termination occurred for the first TB index for HARQ process identifier nine. As shown, the UE 120 may also report an NDI value and time stamp for each unsuccessful HARQ process termination. Examples of times that may be indicated by the time stamps are provided in example 1701 (Fig. 17) .
[0194] As indicated above, Fig. 18 is provided as an example. Other examples may differ from what is described with respect to Fig. 18.
[0195] Fig. 19 is a diagram illustrating examples 1900 and 1901 associated with virtual HARQ process identifiers.
[0196] In some aspects, the indication of the unsuccessful HARQ process termination may indicate the HARQ process identifier in accordance with the TB index being a first TB index associated with a DCI message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message. For example, instead of reporting NACK to ACK errors for each pair of {HARQ process identifier, TB index} , a set of virtual HARQ process identifiers may be introduced for the second TB index. For example, HARQ process identifiers 0-15 corresponding to the first TB index may be mapped to HARQ process identifiers 0-15, and HARQ process identifiers 0-15 corresponding to the second TB index may be mapped to virtual HARQ process identifiers 16-31, respectively. If a NACK to ACK error is detected for the first TB index for HARQ process ID x, then the UE 120 may detect and report the NACK to ACK error for HARQ process ID x. If a NACK to ACK error is detected for the second TB index for HARQ process ID x, then the UE 120 may detect and report the NACK to ACK error for virtual HARQ process ID x + 16. As a result, the UE 120 may refrain from including the TB index in the report, and the HARQ process identifier for the second TB index may be replaced with the virtual HARQ process identifiers. For example, with reference to example 1701 (Fig. 17) , the UE 120 may indicate, in the report 1744, the virtual HARQ process identifier x + 16 for the second TB index associated with the unsuccessful HARQ process termination.
[0197] In example 1900, a block associated with an unsuccessful HARQ process termination event may indicate a component carrier index 1910, a HARQ process identifier 1920, an NDI value 1930, and a time stamp 1940. The HARQ process identifier 1920 may be a HARQ process identifier corresponding to the first TB index or a virtual HARQ process identifier corresponding to the second TB index. The UE 120 may report multiple such blocks corresponding to respective unsuccessful HARQ process termination events. Examples of times that may be indicated by the time stamp 1940 are provided in example 1701 (Fig. 17) .
[0198] As shown in example 1901, the bitmap 1950 may be for HARQ process identifiers corresponding to the first TB index and for virtual HARQ process identifiers corresponding to the second TB index. For example, the bits in the bitmap 1950 may correspond to HARQ process identifiers 0-31 (e.g., from left to right) . For example, the four leftmost “0” bits in the bitmap 1950 may indicate that an unsuccessful HARQ process termination occurred for the first TB index for HARQ process identifiers one, three, seven, and nine, respectively. Additionally, or alternatively, the four rightmost “0”bits in the bitmap 1950 may indicate that an unsuccessful HARQ process termination occurred for the second TB index for virtual HARQ process identifiers eighteen, twenty-one, twenty-three, and twenty-seven, respectively (corresponding to HARQ process identifiers for the second TB index of two, five, seven, and eleven, respectively) . As shown, the UE 120 may also report an NDI value and time stamp for each unsuccessful HARQ process termination. Examples of times that may be indicated by the time stamps are provided in example 1701 (Fig. 17) .
[0199] As indicated above, Fig. 19 is provided as an example. Other examples may differ from what is described with respect to Fig. 19.
[0200] Transmitting the indication of the unsuccessful HARQ process termination responsive to the detection of the unsuccessful HARQ process termination event may help to decrease a latency and signaling overhead associated with communications between devices in examples where multiple TBs are configured. For example, the UE 120 detecting and reporting NACK to ACK errors in examples where multiple TBs are configured prior to the expiration of the timer may decrease the latency associated with initiating RLC retransmissions in instances of NACK to ACK errors without increasing signaling overhead (for example, due to increased instances of the UE 120 initiating the ARQ process prematurely) . Additionally, or alternatively, the described techniques can be used to decrease overhead at the UE 120 by decreasing buffering at the UE 120 (or at another receiving device) in examples where multiple TBs are configured. For example, if a latency associated with receiving missing packets (for example, missing RLC SDUs, missing RLC SDU segments) is reduced by decreasing a delay associated with initiating ARQ processes, then the UE 120 can decrease a usage of a high-layer buffer (for example, a buffer at the RLC layer, a buffer at the PDCP layer) in cases when in-order delivery of packets is required (for example, such as when the RLC is operating in accordance with the acknowledgement mode) .
[0201] A quantity of HARQ retransmissions of the second TB being less than a HARQ retransmission threshold may help to reduce consumption of uplink time and frequency resources by causing the UE 120 to transmit the indication of the unsuccessful HARQ process termination in cases where NACK to ACK error occurs (e.g., instead of in cases where the network node 110 ceases HARQ retransmissions for a TB index upon reaching the HARQ retransmission threshold) .
[0202] The unsuccessful HARQ process termination event including an expiration of the timer that starts upon transmission of negative HARQ feedback may help to reduce latency associated with detection and reporting of unsuccessful HARQ process termination in cases where a TB index associated with a NACK to ACK error is not signaled (or the UE 120 does not decode the signaling) for a long time after the NACK to ACK error.
[0203] The unsuccessful HARQ process termination event including an expiration of the timer that starts upon transmission of HARQ feedback may enable the UE 120 to identify unsuccessful terminations of HARQ processes in cases where a TB index associated with a NACK to ACK error corresponding to an initial TB transmission is not signaled (or the UE 120 does not decode the signaling) for a long time after the NACK to ACK error.
[0204] The unsuccessful HARQ process termination event including a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and an NDI value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded, may help to further reduce latency by enabling the UE 120 to identify unsuccessful terminations of HARQ processes in cases where the DCI scheduling an initial transmission of a TB is not detected by the UE 120.
[0205] The detection of the unsuccessful HARQ process termination event being based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded may help the UE 120 to identify unsuccessful terminations of HARQ processes in cases where a NACK to ACK error occurs, followed by a DCI message that is not successfully decoded by the UE 120, followed by another NACK to ACK error associated with the DCI message.
[0206] The difference between the first NDI value and the second NDI value being greater than one may help to further reduce latency by enabling the UE 120 to identify unsuccessful terminations of HARQ processes in cases where the DCI message (s) scheduling an initial transmission of a TB is / are not detected by the UE 120.
[0207] The first MCS being different from the second MCS, the first TBS being different from the second TBS, or the first TB being associated with a redundancy version of zero, may help the UE 120 to refrain from reporting scenarios involving ACK to NACK scenarios, thereby conserving uplink time and frequency resources.
[0208] Fig. 20 is a diagram illustrating an example process 2000 performed, for example, at a UE or an apparatus of a UE. Example process 2000 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with unsuccessful HARQ process termination for multiple TBs.
[0209] As shown in Fig. 20, in some aspects, process 2000 may include receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one (block 2010) . For example, the UE (e.g., using reception component 2202 or communication manager 2206, depicted in Fig. 22) may receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one, as described above.
[0210] As further shown in Fig. 20, in some aspects, process 2000 may include transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier (block 2020) . For example, the UE (e.g., using transmission component 2204 or communication manager 2206, depicted in Fig. 22) may transmit, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier, as described above.
[0211] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0212] In a first aspect, HARQ feedback bundling across multiple TBs is not configured.
[0213] In a second aspect, alone or in combination with the first aspect, HARQ feedback bundling across multiple TBs is configured.
[0214] In a third aspect, alone or in combination with one or more of the first and second aspects, the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value different from the first NDI value has been decoded.
[0215] In a fourth aspect, alone or in combination with one or more of the first through third aspects, a quantity of HARQ retransmissions of the second TB is less than a HARQ retransmission threshold.
[0216] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of negative HARQ feedback, and the timer stops and resets upon a reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier.
[0217] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the TB index is a first TB index, and the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first NDI value that is different from a second NDI value associated with the second TB, before the second TB has been decoded.
[0218] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of HARQ feedback, and the timer stops and resets upon a reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier.
[0219] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the unsuccessful HARQ process termination event includes a reception of a first DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value, a bit width of an NDI field of the first NDI value is greater than one, a bit width of an NDI field of the second NDI value is greater than one, and a difference between the first NDI value and the second NDI value is greater than one.
[0220] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the detection of the unsuccessful HARQ process termination event is based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded.
[0221] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and an NDI value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded.
[0222] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a first MCS associated with the first TB is different from a second MCS of the second TB or a reserved MCS, a first TBS associated with the first TB is different from a second TBS of the second TB, or the first TB is associated with a redundancy version of zero.
[0223] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication of the unsuccessful HARQ process termination includes a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier.
[0224] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the indication of the unsuccessful HARQ process termination includes one or more of a component carrier index associated with the unsuccessful HARQ process termination event, a new data indicator value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event.
[0225] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the indication of the unsuccessful HARQ process termination includes a bitmap associated with a plurality of TB indexes including the TB index and a plurality of HARQ process identifiers including the HARQ process identifier, the bitmap includes a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit indicates that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier.
[0226] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the bitmap includes a set of consecutive bit positions corresponding to the TB index.
[0227] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the bitmap includes a set of alternating bit positions corresponding to the TB index.
[0228] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the indication of the unsuccessful HARQ process termination indicates the HARQ process identifier in accordance with the TB index being a first TB index associated with a DCI message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message.
[0229] Although Fig. 20 shows example blocks of process 2000, in some aspects, process 2000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 20. Additionally, or alternatively, two or more of the blocks of process 2000 may be performed in parallel.
[0230] Fig. 21 is a diagram illustrating an example process 2100 performed, for example, at a network node or an apparatus of a network node. Example process 2100 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with unsuccessful HARQ process termination for multiple TBs.
[0231] As shown in Fig. 21, in some aspects, process 2100 may include transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one (block 2110) . For example, the network node (e.g., using transmission component 2304 or communication manager 2306, depicted in Fig. 23) may transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one, as described above.
[0232] As further shown in Fig. 21, in some aspects, process 2100 may include receiving, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier (block 2120) . For example, the network node (e.g., using reception component 2302 or communication manager 2306, depicted in Fig. 23) may receive, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier, as described above.
[0233] Process 2100 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0234] In a first aspect, HARQ feedback bundling across multiple TBs is not configured.
[0235] In a second aspect, alone or in combination with the first aspect, HARQ feedback bundling across multiple TBs is configured.
[0236] In a third aspect, alone or in combination with one or more of the first and second aspects, the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value different from the first NDI value has been decoded.
[0237] In a fourth aspect, alone or in combination with one or more of the first through third aspects, a quantity of HARQ retransmissions of the second TB is less than a HARQ retransmission threshold.
[0238] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of negative HARQ feedback, and the timer stops and resets upon a reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier.
[0239] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the TB index is a first TB index, and the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first NDI value that is different from a second NDI value associated with the second TB, before the second TB has been decoded.
[0240] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of HARQ feedback, and the timer stops and resets upon a reception of a DCI message that schedules a TB associated with the TB index and the HARQ process identifier.
[0241] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the unsuccessful HARQ process termination event includes a reception of a first DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first NDI value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value, a bit width of an NDI field of the first NDI value is greater than one, a bit width of an NDI field of the second NDI value is greater than one, and a difference between the first NDI value and the second NDI value is greater than one.
[0242] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the detection of the unsuccessful HARQ process termination event is based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded.
[0243] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the unsuccessful HARQ process termination event includes a reception of a DCI message that schedules a first TB associated with the TB index, the HARQ process identifier, and an NDI value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded.
[0244] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a first MCS associated with the first TB is different from a second MCS of the second TB or a reserved MCS, a first TBS associated with the first TB is different from a second TBS of the second TB, or the first TB is associated with a redundancy version of zero.
[0245] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication of the unsuccessful HARQ process termination includes a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier.
[0246] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the indication of the unsuccessful HARQ process termination includes a bitmap associated with a plurality of TB indexes including the TB index and a plurality of HARQ process identifiers including the HARQ process identifier, the bitmap includes a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit indicates that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier.
[0247] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the bitmap includes a set of consecutive bit positions corresponding to the TB index.
[0248] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the bitmap includes a set of alternating bit positions corresponding to the TB index.
[0249] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the indication of the unsuccessful HARQ process termination indicates the HARQ process identifier in accordance with the TB index being a first TB index associated with a DCI message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message.
[0250] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the indication of the unsuccessful HARQ process termination includes one or more of a component carrier index associated with the unsuccessful HARQ process termination event, a new data indicator value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event.
[0251] Although Fig. 21 shows example blocks of process 2100, in some aspects, process 2100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 21. Additionally, or alternatively, two or more of the blocks of process 2100 may be performed in parallel.
[0252] Fig. 22 is a diagram of an example apparatus 2200 for wireless communication. The apparatus 2200 may be a UE, or a UE may include the apparatus 2200. In some aspects, the apparatus 2200 includes a reception component 2202, a transmission component 2204, or a communication manager 2206, which may be in communication with one another (for example, via one or more buses or one or more other components) . In some aspects, the communication manager 2206 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 2200 may communicate with another apparatus 2208, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 2202 and the transmission component 2204. The communication manager 2206 may be included in, or implemented via, a processing system (for example, the processing system 140 described in connection with Fig. 1) of the UE.
[0253] In some aspects, the apparatus 2200 may be configured to perform one or more operations described herein in connection with Figs. 3-19. Additionally, or alternatively, the apparatus 2200 may be configured to perform one or more processes described herein, such as process 2000 of Fig. 20. In some aspects, the apparatus 2200 or one or more components shown in Fig. 22 may include one or more components of the UE described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 22 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0254] The reception component 2202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 2208. The reception component 2202 may provide received communications to one or more other components of the apparatus 2200. In some aspects, the reception component 2202 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 2200. In some aspects, the reception component 2202 may include one or more components of the UE described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE.
[0255] The transmission component 2204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 2208. In some aspects, one or more other components of the apparatus 2200 may generate communications and may provide the generated communications to the transmission component 2204 for transmission to the apparatus 2208. In some aspects, the transmission component 2204 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 2208. In some aspects, the transmission component 2204 may include one or more components of the UE described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE described in connection with Fig. 1. In some aspects, the transmission component 2204 may be co-located with the reception component 2202.
[0256] The communication manager 2206 may support operations of the reception component 2202 or the transmission component 2204. For example, the communication manager 2206 may receive information associated with configuring reception of communications by the reception component 2202 or transmission of communications by the transmission component 2204. Additionally, or alternatively, the communication manager 2206 may generate or provide control information to the reception component 2202 or the transmission component 2204 to control reception or transmission of communications.
[0257] The reception component 2202 may receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The transmission component 2204 may transmit, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0258] The number and arrangement of components shown in Fig. 22 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 22. Furthermore, two or more components shown in Fig. 22 may be implemented within a single component, or a single component shown in Fig. 22 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 22 may perform one or more functions described as being performed by another set of components shown in Fig. 22.
[0259] Fig. 23 is a diagram of an example apparatus 2300 for wireless communication. The apparatus 2300 may be a network node, or a network node may include the apparatus 2300. In some aspects, the apparatus 2300 includes a reception component 2302, a transmission component 2304, or a communication manager 2306, which may be in communication with one another (for example, via one or more buses or one or more other components) . In some aspects, the communication manager 2306 is the communication manager 155 described in connection with Fig. 1. As shown, the apparatus 2300 may communicate with another apparatus 2308, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 2302 and the transmission component 2304. The communication manager 2306 may be included in, or implemented via, a processing system (for example, the processing system 145 described in connection with Fig. 1) of the network node.
[0260] In some aspects, the apparatus 2300 may be configured to perform one or more operations described herein in connection with Figs. 3-19. Additionally, or alternatively, the apparatus 2300 may be configured to perform one or more processes described herein, such as process 2100 of Fig. 21. In some aspects, the apparatus 2300 or one or more components shown in Fig. 23 may include one or more components of the network node described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 23 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0261] The reception component 2302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 2308. The reception component 2302 may provide received communications to one or more other components of the apparatus 2300. In some aspects, the reception component 2302 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 2300. In some aspects, the reception component 2302 may include one or more components of the network node described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the network node. In some aspects, the reception component 2302 or the transmission component 2304 may include or may be included in a network interface. The network interface may be configured to obtain or output signals for the apparatus 2300 via one or more communications links, such as a backhaul link, a midhaul link, or a fronthaul link.
[0262] The transmission component 2304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 2308. In some aspects, one or more other components of the apparatus 2300 may generate communications and may provide the generated communications to the transmission component 2304 for transmission to the apparatus 2308. In some aspects, the transmission component 2304 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 2308. In some aspects, the transmission component 2304 may include one or more components of the network node described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the network node described in connection with Fig. 1. In some aspects, the transmission component 2304 may be co-located with the reception component 2302.
[0263] The communication manager 2306 may support operations of the reception component 2302 or the transmission component 2304. For example, the communication manager 2306 may receive information associated with configuring reception of communications by the reception component 2302 or transmission of communications by the transmission component 2304. Additionally, or alternatively, the communication manager 2306 may generate or provide control information to the reception component 2302 or the transmission component 2304 to control reception or transmission of communications.
[0264] The transmission component 2304 may transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one. The reception component 2302 may receive, in accordance with the configuration, responsive to a detection of an unsuccessful HARQ process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0265] The number and arrangement of components shown in Fig. 23 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 23. Furthermore, two or more components shown in Fig. 23 may be implemented within a single component, or a single component shown in Fig. 23 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 23 may perform one or more functions described as being performed by another set of components shown in Fig. 23.
[0266] The following provides an overview of some Aspects of the present disclosure:
[0267] Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: receiving a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; and transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0268] Aspect 2: The method of Aspect 1, wherein HARQ feedback bundling across multiple TBs is not configured.
[0269] Aspect 3: The method of any of Aspects 1-2, wherein HARQ feedback bundling across multiple TBs is configured.
[0270] Aspect 4: The method of any of Aspects 1-3, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value different from the first NDI value has been decoded.
[0271] Aspect 5: The method of Aspect 4, wherein a quantity of HARQ retransmissions of the second TB is less than a HARQ retransmission threshold.
[0272] Aspect 6: The method of any of Aspects 1-5, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of negative HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.
[0273] Aspect 7: The method of any of Aspects 1-6, wherein the TB index is a first TB index, and the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first new data indicator (NDI) value that is different from a second NDI value associated with the second TB, before the second TB has been decoded.
[0274] Aspect 8: The method of any of Aspects 1-7, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.
[0275] Aspect 9: The method of any of Aspects 1-8, wherein the unsuccessful HARQ process termination event includes a reception of a first downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value, a bit width of an NDI field of the first NDI value is greater than one, a bit width of an NDI field of the second NDI value is greater than one, and a difference between the first NDI value and the second NDI value is greater than one.
[0276] Aspect 10: The method of Aspect 9, wherein the detection of the unsuccessful HARQ process termination event is based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded.
[0277] Aspect 11: The method of any of Aspects 1-10, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a new data indicator (NDI) value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded.
[0278] Aspect 12: The method of Aspect 11, wherein a first modulation and coding scheme (MCS) associated with the first TB is different from a second MCS of the second TB or a reserved MCS, a first TB size (TBS) associated with the first TB is different from a second TBS of the second TB, or the first TB is associated with a redundancy version of zero.
[0279] Aspect 13: The method of any of Aspects 1-12, wherein the indication of the unsuccessful HARQ process termination includes a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier.
[0280] Aspect 14: The method of any of Aspects 1-13, wherein the indication of the unsuccessful HARQ process termination includes one or more of a component carrier index associated with the unsuccessful HARQ process termination event, a new data indicator value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event.
[0281] Aspect 15: The method of any of Aspects 1-14, wherein the indication of the unsuccessful HARQ process termination includes a bitmap associated with a plurality of TB indexes including the TB index and a plurality of HARQ process identifiers including the HARQ process identifier, the bitmap includes a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit indicates that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier.
[0282] Aspect 16: The method of Aspect 15, wherein the bitmap includes a set of consecutive bit positions corresponding to the TB index.
[0283] Aspect 17: The method of Aspect 15, wherein the bitmap includes a set of alternating bit positions corresponding to the TB index.
[0284] Aspect 18: The method of any of Aspects 1-17, wherein the indication of the unsuccessful HARQ process termination indicates the HARQ process identifier in accordance with the TB index being a first TB index associated with a downlink control information (DCI) message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message.
[0285] Aspect 19: A method of wireless communication performed by a network node, comprising: transmitting a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; and receiving, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0286] Aspect 20: The method of Aspect 19, wherein HARQ feedback bundling across multiple TBs is not configured.
[0287] Aspect 21: The method of any of Aspects 19-20, wherein HARQ feedback bundling across multiple TBs is configured.
[0288] Aspect 22: The method of any of Aspects 19-21, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value different from the first NDI value has been decoded.
[0289] Aspect 23: The method of Aspect 22, wherein a quantity of HARQ retransmissions of the second TB is less than a HARQ retransmission threshold.
[0290] Aspect 24: The method of any of Aspects 19-23, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of negative HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.
[0291] Aspect 25: The method of any of Aspects 19-24, wherein the TB index is a first TB index, and the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first new data indicator (NDI) value that is different from a second NDI value associated with the second TB, before the second TB has been decoded.
[0292] Aspect 26: The method of any of Aspects 19-25, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.
[0293] Aspect 27: The method of any of Aspects 19-26, wherein the unsuccessful HARQ process termination event includes a reception of a first downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value, a bit width of an NDI field of the first NDI value is greater than one, a bit width of an NDI field of the second NDI value is greater than one, and a difference between the first NDI value and the second NDI value is greater than one.
[0294] Aspect 28: The method of Aspect 27, wherein the detection of the unsuccessful HARQ process termination event is based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded.
[0295] Aspect 29: The method of any of Aspects 19-28, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a new data indicator (NDI) value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded.
[0296] Aspect 30: The method of Aspect 29, wherein a first modulation and coding scheme (MCS) associated with the first TB is different from a second MCS of the second TB or a reserved MCS, a first TB size (TBS) associated with the first TB is different from a second TBS of the second TB, or the first TB is associated with a redundancy version of zero.
[0297] Aspect 31: The method of any of Aspects 19-30, wherein the indication of the unsuccessful HARQ process termination includes a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier.
[0298] Aspect 32: The method of any of Aspects 19-31, wherein the indication of the unsuccessful HARQ process termination includes a bitmap associated with a plurality of TB indexes including the TB index and a plurality of HARQ process identifiers including the HARQ process identifier, the bitmap includes a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit indicates that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier.
[0299] Aspect 33: The method of Aspect 32, wherein the bitmap includes a set of consecutive bit positions corresponding to the TB index.
[0300] Aspect 34: The method of Aspect 32, wherein the bitmap includes a set of alternating bit positions corresponding to the TB index.
[0301] Aspect 35: The method of any of Aspects 19-34, wherein the indication of the unsuccessful HARQ process termination indicates the HARQ process identifier in accordance with the TB index being a first TB index associated with a downlink control information (DCI) message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message.
[0302] Aspect 36: The method of any of Aspects 19-35, wherein the indication of the unsuccessful HARQ process termination includes one or more of a component carrier index associated with the unsuccessful HARQ process termination event, a new data indicator value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event.
[0303] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-36.
[0304] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-36.
[0305] Aspect 39: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-36.
[0306] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-36.
[0307] Aspect 41: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-36.
[0308] Aspect 42: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-36.
[0309] Aspect 43: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-36.
[0310] Aspect 44: A device comprising a processing system that includes one or more processors and one or more code-storing memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-36.
[0311] Aspect 45: A device comprising a processing system that includes processor circuitry and code-storing memory circuitry, the processing system configured to cause the device to perform the method of one or more of Aspects 1-36.
[0312] It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.
[0313] As used herein, the term “determine” or “determining” can encompass one or more of a wide variety of actions. For example, “determining” can include one or more of calculating, computing, processing, deriving, detecting, estimating, investigating, looking up, inferring, ascertaining, measuring, resolving, selecting, choosing, obtaining, identifying, interpreting, demodulating, decoding, reading, establishing, forming or generating, among other examples. In some such examples, determining can involve a processor performing some type of calculating, computing, deriving, estimating, inferring, ascertaining, resolving, predicting or other processing to obtain one or more numerical values, sets, elements or other information or results. In some other such examples, determining can involve a processor identifying, looking up, investigating or otherwise obtaining some type of value, set, element or other information or result from a table, a data structure, a database or other memory device or location. In some other such examples, determining can involve a processor identifying, interpreting, demodulating, decoding, detecting, reading or otherwise obtaining some type of value, set, element or other information or result signaled in, for example, a received wireless packet. In some other such examples, determining can involve a processor selecting or choosing one or more values, sets, elements or other information or results from a larger set of values, sets elements or other information or results. In some other such examples, determining can involve a processor performing a measurement, such as on a received signal.
[0314] As used herein, the articles “a” and “an” are intended to refer to one or more items and may be used interchangeably with “one or more” or “at least one. ” As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. Additionally, as used herein, a phrase referring to “a” or “an” element refers to one or more of such elements acting individually or collectively to perform the recited function (s) . Additionally, as used herein, a “set” can refer to one or more items, and a “subset” can refer to a whole set or less than the whole set, but not an empty set. “Set, ” “group, ” and similar terms are intended to include one or more items and may be used interchangeably with “one or more. ” Furthermore, as used herein, the term “or” is intended to be interpreted in the inclusive sense (such as when referring to a series) and may be used interchangeably with “and / or, ” unless otherwise explicitly indicated (for example, if used in conjunction with “either” or “only one of” ) . For example, “A or B” may include A only, B only, or a combination of A and B. Also, as used herein, the terms “has, ” “have, ” “having, ” “comprise, ” “comprising, ” “include” and “including, ” and derivatives thereof or similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A also may have B) .
[0315] As used herein, the phrase “associated with” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, the phrase “associated with” is not to be construed as a reference to a closed set of conditions, factors, criteria, elements, components, or actions, among other examples. Specifically, unless a phrase refers to “associated with only ‘a, ’ ” or the equivalent in context, whatever it is that is “associated with ‘a, ’ ” may be associated with “a” alone or associated with a combination of “a” and one or more other conditions, factors, criteria, elements, components, or actions, among other examples.
[0316] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.
[0317] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the scope of all aspects described herein. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.
Claims
1.A user equipment (UE) , comprising:a processing system that includes processor circuitry and code-storing memory circuitry, the processing system configured to cause the UE to:receive a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; andtransmit, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.2.The UE of claim 1, wherein HARQ feedback bundling across multiple TBs is not configured.3.The UE of claim 1, wherein HARQ feedback bundling across multiple TBs is configured.4.The UE of claim 1, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, before a second TB associated with the TB index, the HARQ process identifier, and a second NDI value different from the first NDI value has been decoded.5.The UE of claim 4, wherein a quantity of HARQ retransmissions of the second TB is less than a HARQ retransmission threshold.6.The UE of claim 1, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of negative HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.7.The UE of claim 1, wherein the TB index is a first TB index, and the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with a second TB index and the HARQ process identifier, does not schedule a second TB associated with the first TB index and the HARQ process identifier, and associates the first TB index with a first new data indicator (NDI) value that is different from a second NDI value associated with the second TB, before the second TB has been decoded.8.The UE of claim 1, wherein the unsuccessful HARQ process termination event includes an expiration of a timer associated with the TB index and the HARQ process identifier, the timer starts upon transmission of HARQ feedback, and the timer stops and resets upon a reception of a downlink control information (DCI) message that schedules a TB associated with the TB index and the HARQ process identifier.9.The UE of claim 1, wherein the unsuccessful HARQ process termination event includes a reception of a first downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a first new data indicator (NDI) value, after a reception of a second DCI message that schedules a second TB associated with the TB index, the HARQ process identifier, and a second NDI value, a bit width of an NDI field of the first NDI value is greater than one, a bit width of an NDI field of the second NDI value is greater than one, and a difference between the first NDI value and the second NDI value is greater than one.10.The UE of claim 9, wherein the detection of the unsuccessful HARQ process termination event is based at least in part on the difference between the first NDI value and the second NDI value and whether or not the first TB is decoded.11.The UE of claim 1, wherein the unsuccessful HARQ process termination event includes a reception of a downlink control information (DCI) message that schedules a first TB associated with the TB index, the HARQ process identifier, and a new data indicator (NDI) value after a second TB associated with the TB index, the HARQ process identifier, and the NDI value has been decoded.12.The UE of claim 11, wherein a first modulation and coding scheme (MCS) associated with the first TB is different from a second MCS of the second TB or a reserved MCS, a first TB size (TBS) associated with the first TB is different from a second TBS of the second TB, or the first TB is associated with a redundancy version of zero.13.The UE of claim 1, wherein the indication of the unsuccessful HARQ process termination includes a block associated with the unsuccessful HARQ process termination that indicates at least the TB index and the HARQ process identifier.14.The UE of claim 1, wherein the indication of the unsuccessful HARQ process termination includes one or more of a component carrier index associated with the unsuccessful HARQ process termination event, a new data indicator value associated with the unsuccessful HARQ process termination event, or a time stamp associated with the unsuccessful HARQ process termination event.15.The UE of claim 1, wherein the indication of the unsuccessful HARQ process termination includes a bitmap associated with a plurality of TB indexes including the TB index and a plurality of HARQ process identifiers including the HARQ process identifier, the bitmap includes a plurality of bits including a bit associated with the TB index and the HARQ process identifier, and a value of the bit indicates that the unsuccessful HARQ process termination is associated with the TB index and the HARQ process identifier.16.The UE of claim 15, wherein the bitmap includes a set of consecutive bit positions corresponding to the TB index.17.The UE of claim 15, wherein the bitmap includes a set of alternating bit positions corresponding to the TB index.18.The UE of claim 1, wherein the indication of the unsuccessful HARQ process termination indicates the HARQ process identifier in accordance with the TB index being a first TB index associated with a downlink control information (DCI) message or a virtual HARQ process identifier corresponding to the HARQ process identifier in accordance with the TB index being a second TB index associated with the DCI message.19.A method of wireless communication performed by a user equipment (UE) , comprising:receiving a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; andtransmitting, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.20.An apparatus for wireless communication, comprising:means for receiving a configuration of a maximum quantity of transport blocks (TBs) schedulable in a set of shared time-frequency resources, the maximum quantity being greater than one; andmeans for transmitting, in accordance with the configuration, responsive to a detection of an unsuccessful hybrid automatic repeat request (HARQ) process termination event associated with a TB index and a HARQ process identifier, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
