Unsuccessful hybrid automatic repeat request process termination based on new data indicator value
By detecting NACK to ACK errors through NDI value changes in DCI messages, the method addresses latency and signaling overhead issues in 5G NR networks by allowing early HARQ process termination and reducing ARQ process initiation latency.
Patent Information
- Application Number
- PCT/CN2025/093363
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in detecting NACK to ACK errors before the expiration of a timer, leading to premature initiation of ARQ processes and increased latency due to unsuccessful decoding of initial DCI messages, particularly in 5G New Radio (NR) networks.
A receiving device, such as a UE, detects NACK to ACK errors by identifying a change in the new data indicator (NDI) value in DCI messages, allowing for early termination of HARQ processes and reducing latency by reporting unsuccessful HARQ terminations to the transmitting device.
This approach decreases latency and signaling overhead by enabling timely detection of NACK to ACK errors, preventing premature ARQ processes and reducing buffering requirements at the receiving device.
Smart Images

Figure CN2025093363_12112026_PF_FP_ABST
Abstract
Description
UNSUCCESSFUL HYBRID AUTOMATIC REPEAT REQUEST PROCESS TERMINATION BASED ON NEW DATA INDICATOR VALUEFIELD 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 based at least in part on a new data indicator value. 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 (UE) 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 (NACK) 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 downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The processing system may be configured to cause the UE to transmit, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The processing system may be configured to cause the network node to receive, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The method may include transmitting, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The method may include receiving, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The apparatus may include means for transmitting, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The apparatus may include means for receiving, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, in accordance with the first NDI value being different from the second NDI value, 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. 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 first NDI value being different from the second NDI value, 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 based at least in part on a new data indicator (NDI) value.
[0017] Fig. 4 is a diagram illustrating examples associated with scheduling configurations.
[0018] Fig. 5 is a diagram illustrating an example process performed, for example, at a user equipment (UE) or an apparatus of a UE.
[0019] Fig. 6 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node.
[0020] Fig. 7 is a diagram of an example apparatus for wireless communication.
[0021] Fig. 8 is a diagram of an example apparatus for wireless communication.DETAILED DESCRIPTION
[0022] 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.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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) .
[0028] 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 transport block 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.
[0029] 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 transport block 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.
[0030] However, these approaches may not enable the UE to detect NACK to ACK errors before the expiration of the timer in examples where the UE does not successfully decode a DCI message that schedules an initial TB transmission (e.g., carrying new data) for a TB index and a HARQ process identifier for the first time. In such examples, the UE may report a NACK and a NACK to ACK error may occur. However, because the UE may not identify that the NDI value corresponding to the HARQ process identifier associated with the DCI message has changed, the UE may not identify the NACK to ACK error before the expiration of the timer. As a result, in the examples where the UE does not successfully decode the DCI message that schedules the initial TB transmission for a TB index and a HARQ process identifier for the first time, 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. The probability of such an occurrence may be non-negligible. For example, the probability of the UE not successfully decoding the DCI message may be approximately 10-2, and the probability of a NACK to ACK error occurring may be approximately 10-3, resulting in a total probability of approximately 10-5.
[0031] 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 the UE does not successfully decode a DCI message that schedules an initial TB transmission for a TB index and a HARQ process identifier for the first time. Some aspects more specifically relate to the UE detecting an unsuccessful termination of a HARQ process (for example, due to a NACK to ACK error in examples where the UE reports a NACK for an initial TB transmission scheduled by a DCI message that is not successfully decoded by the UE) associated with a TB index prior to the expiration of the timer, and reporting the unsuccessful termination of the HARQ process associated with the TB index to a transmitting device (for example, a network node) . For example, the UE may detect and report instances where an initial DCI message that schedules a TB associated with a TB index and a HARQ process identifier is not decoded and the UE receives another DCI message that schedules another TB associated with the same TB index and the same HARQ process identifier. In some aspects, the UE may detect such instances by identifying that an NDI value associated with the other TB is different from an NDI value associated with an initial NDI value. The initial NDI value may indicate that a DCI message scheduling a TB associated with a TB index and a HARQ process identifier is an initial DCI message scheduling a TB associated with the TB index and the HARQ process. In some aspects, the initial NDI value may be a default initial NDI value that is predefined or configured. In some aspects, whether or not the NDI value is different from the initial NDI value may be indicated by a bit field in a DCI message that schedules the TB. The UE may, based at least in part on identifying that the NDI value differs from the initial NDI value, detect and report NACK to ACK errors prior to the expiration of the timer in examples where the UE reports a NACK for an initial TB transmission scheduled by a DCI message that is not successfully decoded by the UE. 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.
[0032] 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 a UE does not successfully decode an initial DCI message that schedules an initial TB transmission. For example, the UE detecting and reporting NACK to ACK errors associated with initial DCI messages that schedule initial TB transmissions prior to the expiration of the timer may decrease the latency associated with initiating RLC retransmissions in instances of the 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 initial DCI messages that schedule initial TB transmissions are not successfully decoded. 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 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) .
[0033] 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.
[0034] 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.
[0035] 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.
[0036] 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.
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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) .
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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 an RLC layer, a MAC layer, or one or more higher physical (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.
[0045] 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.
[0046] 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) .
[0047] 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.
[0048] 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.
[0049] 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) .
[0050] 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.
[0051] 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 redundancy version 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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) .
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; and transmit, in accordance with the first NDI value being different from the second NDI value, 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.
[0062] 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 DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; and receive, in accordance with the first NDI value being different from the second NDI value, 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.
[0063] 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 based at least in part on an NDI value, 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 500 of Fig. 5, process 600 of Fig. 6, 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 500 of Fig. 5, process 600 of Fig. 6, 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.
[0064] In some aspects, the UE 120 includes means for receiving a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; or means for transmitting, in accordance with the first NDI value being different from the second NDI value, 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 702 depicted and described in connection with Fig. 7) , or a transmission component (for example, transmission component 704 depicted and described in connection with Fig. 7) , among other examples.
[0065] In some aspects, the network node 110 includes means for transmitting a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; or means for receiving, in accordance with the first NDI value being different from the second NDI value, 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 802 depicted and described in connection with Fig. 8) , or a transmission component (for example, transmission component 804 depicted and described in connection with Fig. 8) , among other examples.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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-a is 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-a is 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 layer 215-a is operating in accordance with the acknowledged mode, the transmitting device 205 may perform the segmentation or resegmentation functionality 235 and the ARQ functionality 240.
[0070] When operating the RLC layer 215-a in 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.
[0071] 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-a may provide the RLC PDU 245 to the MAC / PHY layers 220-a of the transmitting device, and the MAC / PHY layers 220-a may receive the MAC PDU 250.
[0072] 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.
[0073] 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 successful 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.
[0074] 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.
[0075] 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) .
[0076] 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.
[0077] 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) .
[0078] 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 285 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) .
[0079] 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.
[0080] 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) .
[0081] In examples where a UE does not successfully decode a DCI message that schedules an initial TB transmission, the UE may be unable to detect NACK to ACK errors before the expiration of a timer (e.g., the t-Reassembly timer) . In such examples, the UE may report a NACK and a NACK to ACK error may occur. However, because the UE may not identify that an NDI value corresponding to a TB index and a HARQ process identifier associated with the DCI message has changed, the UE may not identify the NACK to ACK error before the expiration of the timer. As a result, in the examples where the UE does not successfully decode the DCI message that schedules the initial TB transmission and a NACK to ACK error occurs for the TB scheduled by the non-decoded DCI, 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 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) even if the receiving device 210 could not successfully decode a DCI message that schedules an initial TB transmission.
[0082] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with respect to Fig. 2.
[0083] Fig. 3 is a diagram illustrating an example 300 associated with signaling for unsuccessful HARQ process termination based at least in part on an NDI value. As shown in Fig. 3, a network node 110 and a UE 120 may communicate with one another.
[0084] As shown by reference number 310, the network node 110 may transmit, and the UE 120 may receive, a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value. 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. The TB may be associated with the first NDI value in that the first NDI value may indicate whether the TB is transmitted by the network node 110 for a first time or the TB is a retransmission within the HARQ process.
[0085] In some aspects, the first NDI value may be different from a second NDI value that is an initial NDI value associated with the TB index and the HARQ process identifier. The second NDI value may be an initial NDI value associated with the TB index and the HARQ process identifier in that the initial NDI value may indicate that a DCI message scheduling a TB associated with the TB index and the HARQ process identifier is an initial DCI message scheduling a TB associated with the TB index and the HARQ process. That is, the second NDI value may indicate that the TB associated with the TB index and the HARQ process identifier is transmitted by the network node 110 for the first time. Thus, the first NDI value being different from the second NDI value may indicate that the DCI message that schedules the TB associated with the TB index, the HARQ process identifier, and the first NDI value is not an initial DCI message scheduling a TB associated with the TB index and the HARQ process. In some aspects, the DCI message may be an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. For example, before receiving the DCI message, the UE 120 may not successfully decode any DCI messages that schedule a TB associated with the TB index and HARQ process identifier. For example, the DCI message may be the first DCI message that the UE 120 successfully decodes and that schedules a TB associated with the TB index and HARQ process identifier.
[0086] In some aspects, the second NDI value may be the default initial NDI value. The default initial NDI value may be an NDI value (e.g., “0” ) that is, by default, assigned to an initial DCI message scheduling a TB associated with a TB index and a HARQ process. For example, the network node 110 may apply the default initial NDI value to an initial DCI message scheduling a TB associated with a TB index and a HARQ process ID for the first time. The UE 120 may detect and report the unsuccessful HARQ termination in response to receiving the DCI message that schedules the TB associated with the TB index, the HARQ process identifier, and the first NDI value for the first time, and the first NDI value being different from the default initial NDI value. The first NDI value being different from the default initial NDI value may indicate that no HARQ retransmission is to take place for the TB, associated with that TB index and the HARQ process identifier, scheduled by the initial DCI message and previously negatively acknowledged by the UE 120. In some aspects, the default initial NDI value may be predefined. For example, the default initial NDI value may be predefined in one or more wireless communications standards specifications. In some aspects, the default initial NDI value may be configured. For example, the network node 110 may transmit, and the UE 120 may receive, a configuration of the default initial NDI value.
[0087] In some aspects, the DCI message may include a bit field (e.g., a 1-bit field) indicating that the first NDI value is different from the second NDI value. The UE 120 may detect and report the unsuccessful HARQ termination in response to receiving the DCI message that schedules the TB associated with the TB index, the HARQ process identifier, and the first NDI value for the first time, and the bit field indicating that the first NDI value is different from the second NDI value. The first NDI value being different from the second NDI value may indicate that no HARQ retransmission is to take place for the TB, associated with that TB index and the HARQ process identifier, scheduled by the initial DCI message and previously negatively acknowledged by the UE 120.
[0088] As shown by reference number 320, the UE 120 may transmit, and the network node 110 may receive, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination 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 network node 110 may terminate the unsuccessful HARQ process for a TB associated with the TB index and the HARQ process identifier. For example, the UE 120 may not have successfully decoded the initial DCI message, and, due to a NACK to ACK error, the network node 110 may terminate the unsuccessful HARQ process and proceed with transmitting the DCI message instead of retransmitting the initial DCI message as part of the HARQ process. The UE 120 may transmit, and the network node 110 may receive, the indication of an unsuccessful HARQ process termination in accordance with the first NDI value being different from the second NDI value in that the UE 120 may use the difference identify that the DCI message is not the initial DCI message. For example, the UE 120 may identify, based at least in part on the difference, that the network node 110 transmitted the initial DCI message which was not successfully decoded by the UE 120 and that a NACK to ACK error caused the network node 110 to proceed with transmitting the DCI message instead of retransmitting the initial DCI message. In some examples, the first NDI value may include multiple bits, in which case the UE 120 may report multiple NACK to ACK errors based at least in part on the change between the first NDI value and the second NDI value. Accordingly, the change between the first NDI value and the second NDI value may be indicated by a DCI message that schedules a TB associated with a TB index and a HARQ process identifier. For example, if the change between the first NDI value and the second NDI value is k, then the UE 120 may report a NACK to ACK error for k-1 events, corresponding to the k-1 missing DCI messages that scheduled the TB index and the HARQ process identifier.
[0089] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with respect to Fig. 3.
[0090] Fig. 4 is a diagram illustrating examples 400 and 401 associated with single-and multiple-TB scheduling configurations.
[0091] In some aspects, 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 time-frequency resources, and the maximum quantity may be equal to one. In some examples, an absence of a reception of the configuration for the maximum quantity of TBs schedulable in a set of time-frequency resources may indicate that the maximum quantity is one. As a result, the TB may be an only TB scheduled by the DCI message in a set of time-frequency resources. In some examples, the network node 110 may configure the maximum quantity of TBs by setting a higher layer parameter maxNrofCodeWordsScheduledByDCI to one (where a codeword may correspond to a TB) . In some examples, the network node 110 may configure the higher layer parameter maxNrofCodeWordsScheduledByDCI, which may indicate that the maxNrofCodeWordsScheduledByDCI is one by default. As shown in example 400, a DCI message 402 may schedule an initial transmission of a TB 404 (e.g., a PDSCH communication) , and may indicate that the TB 404 is associated with a HARQ process identifier 406 and an NDI value 408. The NDI value 408 may be the second NDI value (e.g., the initial NDI value associated with the TB index and the HARQ process identifier 406) . For example, the NDI value 408 may be the default initial NDI value, such as zero. The UE 120 may be unable to successfully decode the initial transmission of the DCI message 402, and, accordingly, may transmit a HARQ NACK 410 to the network node 110. Due to a NACK to ACK error (e.g., a discontinuous transmission (DTX) to ACK error) , the network node 110 may not schedule one or more retransmissions of the TB 404 (e.g., the network node 110 may terminate an unsuccessful HARQ process associated with the HARQ process identifier 406) .
[0092] A DCI message 412 may schedule an initial transmission of a TB 414 (e.g., a PDSCH communication) , and may indicate that the TB 414 is associated with a HARQ process identifier 416, and an NDI value 418. The NDI value 418 may be the first NDI value (e.g., one) different from the second NDI value (e.g., zero) . In some examples, the NDI value 418 may be different from the default initial NDI value (e.g., the NDI value 408) . In some examples, the DCI message 412 may include a bit field indicating that the NDI value 418 is different from the initial NDI value (e.g., the NDI value 408) . In some examples, the HARQ process identifier 406 and the HARQ process identifier 416 may be the same. The UE 120 may transmit, and the network node 110 may receive, the indication of the unsuccessful HARQ process termination associated with the HARQ process identifier 406 in accordance with the NDI value 418 being different from the NDI value 408. In some examples, the UE 120 may transmit a HARQ ACK or NACK 420 to the network node 110, and a DCI message 422 may schedule a transmission of a TB (e.g., a PDSCH communication) , and may indicate that the TB is associated with a HARQ process identifier 424 and an NDI value 426 (e.g., zero) .
[0093] In some aspects, 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 time-frequency resources, and the maximum quantity may be greater than one. As a result, in some aspects, the DCI message may schedule a plurality of TBs (including the TB) associated with respective TB indexes. For example, the DCI message may schedule the plurality of TBs in the same set of time-frequency resources. For example, the network node 110 may configure the maximum quantity of TBs by setting a higher layer parameter maxNrofCodeWordsScheduledByDCI to more than one (where a codeword may correspond to a TB) . In some aspects, the DCI message may include a plurality of bit fields corresponding to the plurality of TB indexes. For example, each bit field may indicate whether or not an NDI value associated with a TB index and a HARQ process identifier is the same as the initial NDI value associated with the same TB index and the same HARQ process identifier. In some aspects, a bit field of the plurality of bit fields may indicate that the first NDI value is different from the second NDI value. The UE 120 may detect and report the unsuccessful HARQ termination in response to receiving the DCI message that includes the plurality of bit fields, including the bit field indicating that the first NDI value is different from the second NDI value for the TB index corresponding to the TB. The first NDI value being different from the second NDI value may indicate that no HARQ retransmission is to take place for the TB, associated with that TB index and the HARQ process identifier, scheduled by the initial DCI message and previously negatively acknowledged by the UE 120.
[0094] As shown in example 401, a DCI message 428 may schedule an initial transmission of a TB 430 and may disable transmission of a TB 432. The DCI message 428 may indicate that the TB 430 is associated with a first TB index, a HARQ process identifier 434, and an NDI value 436 (e.g., zero) . In some examples, the DCI message 428 may include a bit field indicating that the NDI value 436 is the same as an initial NDI value for the first TB index. The UE 120 may transmit, to the network node 110, a HARQ ACK 438 for the TB 430 and a HARQ NACK 440 for the (disabled) TB 432. A DCI message 442 may schedule an initial transmission of a TB 444 and an initial transmission of a TB 446. The DCI message 442 may indicate that the TB 444 is associated with the first TB index, a HARQ process identifier 448, and an NDI value 450 (e.g., 1) . In some examples, the DCI message 442 may include a first bit field indicating that the NDI value 450 is different from the initial NDI value (e.g., the NDI value 436) . The HARQ process identifier 448 may be the HARQ process identifier 434. The NDI value 450 may be one. The DCI message 442 may also indicate that the TB 446 is associated with a second TB index, the HARQ process identifier 448, and an NDI value 452 (e.g., zero) . The NDI value 452 may be the second NDI value (e.g., the initial NDI value associated with the second TB index and the HARQ process identifier 448) . For example, the NDI value 452 may be the default initial NDI value, such as zero. In some examples, the DCI message 442 may include a second bit field indicating that the NDI value 452 is the same as an initial NDI value for the second TB index. The UE 120 may be unable to successfully decode the initial transmission of the DCI message 442, and, accordingly, may transmit, to the network node 110, a HARQ NACK 454 for the TB 444 and a HARQ NACK 456 for the TB 446. Due to a NACK to ACK error (e.g., a DTX to ACK error) for the HARQ NACK 456 for the TB 446, the network node 110 may not schedule one or more retransmissions of the TB 446 (e.g., the network node 110 may terminate an unsuccessful HARQ process associated with the HARQ process identifier 448 for the second TB index) .
[0095] A DCI message 458 may schedule an initial transmission of a TB 460 and a TB 462. The DCI message 458 may indicate that the TB 460 is associated with the first TB index, a HARQ process identifier 464, and an NDI value 466 (e.g., one) . The HARQ process identifier 464 may be the HARQ process identifier 448. The DCI message 442 may also indicate that the TB 462 is associated with the second TB index, the HARQ process identifier 464, and an NDI value 468 (e.g., one) . The NDI value 468 may be the first NDI value (e.g., one) different from the second NDI value (e.g., zero) . In some examples, the NDI value 468 may be different from the default initial NDI value (e.g., the NDI value 452) . In some examples, the DCI message 458 may include a first bit field indicating that the NDI value 466 is different from the initial NDI value for the first TB index (e.g., the NDI value 436) , and a second bit field indicating that the NDI value 468 is different from the initial NDI value for the second TB index (e.g., the NDI value 452) . The UE 120 may transmit, and the network node 110 may receive, the indication of the unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier 448 in accordance with the NDI value 468 being different from the NDI value 452 and the DCI message 458 may be the first decoded DCI that schedules the TB 462 associated with the second TB index and the HARQ process identifier 448. In some examples, the UE 120 may transmit, to the network node 110, a HARQ ACK 470 for the TB 460 and a HARQ NACK 472 for the TB 462.
[0096] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
[0097] Transmitting or receiving the indication of the unsuccessful HARQ process termination in accordance with the first NDI value being different from the second NDI value may help to decrease a latency and signaling overhead associated with communications between devices in examples where the 120 UE does not successfully decode an initial DCI message that schedules an initial TB transmission. For example, the UE 120 detecting and reporting NACK to ACK errors associated with initial DCI messages that schedule initial TB transmissions prior to the expiration of the timer may decrease the latency associated with initiating RLC retransmissions in instances of the 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, transmitting or receiving the indication of the unsuccessful HARQ process termination in accordance with the first NDI value being different from the second NDI value may help to decrease overhead at the UE by decreasing buffering at the UE 120 (or at another receiving device) in examples where initial DCI messages that schedule initial TB transmissions are not successfully decoded. 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) .
[0098] Fig. 5 is a diagram illustrating an example process 500 performed, for example, at a UE or an apparatus of a UE. Example process 500 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with unsuccessful HARQ process termination based at least in part on an NDI value.
[0099] As shown in Fig. 5, in some aspects, process 500 may include receiving a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier (block 510) . For example, the UE (e.g., using reception component 702 or communication manager 706, depicted in Fig. 7) may receive a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier, as described above.
[0100] As further shown in Fig. 5, in some aspects, process 500 may include transmitting, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier (block 520) . For example, the UE (e.g., using transmission component 704 or communication manager 706, depicted in Fig. 7) may transmit, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier, as described above.
[0101] Process 500 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.
[0102] In a first aspect, the second NDI value is a default initial NDI value.
[0103] In a second aspect, alone or in combination with the first aspect, the default initial NDI value is predefined.
[0104] In a third aspect, alone or in combination with one or more of the first and second aspects, the default initial NDI value is configured.
[0105] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.
[0106] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 500 includes receiving a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, and the maximum quantity is equal to one.
[0107] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 500 includes receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, and the maximum quantity is greater than one.
[0108] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.
[0109] Although Fig. 5 shows example blocks of process 500, in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 5. Additionally, or alternatively, two or more of the blocks of process 500 may be performed in parallel.
[0110] Fig. 6 is a diagram illustrating an example process 600 performed, for example, at a network node or an apparatus of a network node. Example process 600 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with unsuccessful HARQ process termination based at least in part on an NDI value.
[0111] As shown in Fig. 6, in some aspects, process 600 may include transmitting a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier (block 610) . For example, the network node (e.g., using transmission component 804 or communication manager 806, depicted in Fig. 8) may transmit a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier, as described above.
[0112] As further shown in Fig. 6, in some aspects, process 600 may include receiving, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier (block 620) . For example, the network node (e.g., using reception component 802 or communication manager 806, depicted in Fig. 8) may receive, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier, as described above.
[0113] Process 600 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.
[0114] In a first aspect, the second NDI value is a default initial NDI value.
[0115] In a second aspect, alone or in combination with the first aspect, the default initial NDI value is predefined.
[0116] In a third aspect, alone or in combination with one or more of the first and second aspects, the default initial NDI value is configured.
[0117] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.
[0118] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 600 includes transmitting a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, and the maximum quantity is equal to one.
[0119] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 600 includes transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, and the maximum quantity is greater than one.
[0120] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.
[0121] Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.
[0122] Fig. 7 is a diagram of an example apparatus 700 for wireless communication. The apparatus 700 may be a UE, or a UE may include the apparatus 700. In some aspects, the apparatus 700 includes a reception component 702, a transmission component 704, or a communication manager 706, 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 706 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 700 may communicate with another apparatus 708, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 702 and the transmission component 704. The communication manager 706 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.
[0123] In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with Figs. 3-4. Additionally, or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as process 500 of Fig. 5. In some aspects, the apparatus 700 or one or more components shown in Fig. 7 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. 7 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.
[0124] The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 708. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 700. In some aspects, the reception component 702 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.
[0125] The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 708. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 708. In some aspects, the transmission component 704 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 708. In some aspects, the transmission component 704 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 704 may be co-located with the reception component 702.
[0126] The communication manager 706 may support operations of the reception component 702 or the transmission component 704. For example, the communication manager 706 may receive information associated with configuring reception of communications by the reception component 702 or transmission of communications by the transmission component 704. Additionally, or alternatively, the communication manager 706 may generate or provide control information to the reception component 702 or the transmission component 704 to control reception or transmission of communications.
[0127] The reception component 702 may receive a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The transmission component 704 may transmit, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0128] The reception component 702 may receive a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.
[0129] The reception component 702 may receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.
[0130] The number and arrangement of components shown in Fig. 7 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. 7. Furthermore, two or more components shown in Fig. 7 may be implemented within a single component, or a single component shown in Fig. 7 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 7 may perform one or more functions described as being performed by another set of components shown in Fig. 7.
[0131] Fig. 8 is a diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a network node, or a network node may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, or a communication manager 806, 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 806 is the communication manager 155 described in connection with Fig. 1. As shown, the apparatus 800 may communicate with another apparatus 808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 802 and the transmission component 804. The communication manager 806 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.
[0132] In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with Figs. 3-4. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6. In some aspects, the apparatus 800 or one or more components shown in Fig. 8 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. 8 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.
[0133] The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 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 802 or the transmission component 804 may include or may be included in a network interface. The network interface may be configured to obtain or output signals for the apparatus 800 via one or more communications links, such as a backhaul link, a midhaul link, or a fronthaul link.
[0134] The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 808. In some aspects, the transmission component 804 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 804 may be co-located with the reception component 802.
[0135] The communication manager 806 may support operations of the reception component 802 or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate or provide control information to the reception component 802 or the transmission component 804 to control reception or transmission of communications.
[0136] The transmission component 804 may transmit a DCI message that schedules a TB associated with a TB index, a HARQ process identifier, and a first NDI value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier. The reception component 802 may receive, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0137] The transmission component 804 may transmit a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.
[0138] The transmission component 804 may transmit a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.
[0139] The number and arrangement of components shown in Fig. 8 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. 8. Furthermore, two or more components shown in Fig. 8 may be implemented within a single component, or a single component shown in Fig. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 8 may perform one or more functions described as being performed by another set of components shown in Fig. 8.
[0140] The following provides an overview of some Aspects of the present disclosure:
[0141] Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: receiving a downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; and transmitting, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0142] Aspect 2: The method of Aspect 1, wherein the second NDI value is a default initial NDI value.
[0143] Aspect 3: The method of Aspect 2, wherein the default initial NDI value is predefined.
[0144] Aspect 4: The method of Aspect 2, wherein the default initial NDI value is configured.
[0145] Aspect 5: The method of any of Aspects 1-4, wherein the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.
[0146] Aspect 6: The method of any of Aspects 1-5, further comprising: receiving a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.
[0147] Aspect 7: The method of any of Aspects 1-6, further comprising: receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.
[0148] Aspect 8: The method of Aspect 7, wherein the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.
[0149] Aspect 9: A method of wireless communication performed by a network node, comprising: transmitting a downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; and receiving, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.
[0150] Aspect 10: The method of Aspect 9, wherein the second NDI value is a default initial NDI value.
[0151] Aspect 11: The method of Aspect 10, wherein the default initial NDI value is predefined.
[0152] Aspect 12: The method of Aspect 10, wherein the default initial NDI value is configured.
[0153] Aspect 13: The method of any of Aspects 9-12, wherein the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.
[0154] Aspect 14: The method of any of Aspects 9-13, further comprising: transmitting a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.
[0155] Aspect 15: The method of any of Aspects 9-14, further comprising: transmitting a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.
[0156] Aspect 16: The method of Aspect 15, wherein the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.
[0157] Aspect 17: 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-16.
[0158] Aspect 18: 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-16.
[0159] Aspect 19: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-16.
[0160] Aspect 20: 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-16.
[0161] Aspect 21: 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-16.
[0162] Aspect 22: 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-16.
[0163] Aspect 23: 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-16.
[0164] Aspect 24: 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-16.
[0165] Aspect 25: 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-16.
[0166] 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.
[0167] 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.
[0168] 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) .
[0169] 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.
[0170] 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.
[0171] 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 downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; andtransmit, in accordance with the first NDI value being different from the second NDI value, 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 the second NDI value is a default initial NDI value.3.The UE of claim 2, wherein the default initial NDI value is predefined.4.The UE of claim 2, wherein the default initial NDI value is configured.5.The UE of claim 1, wherein the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.6.The UE of claim 1, wherein the processing system is configured to cause the UE to:receive a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.7.The UE of claim 1, wherein the processing system is configured to cause the UE to:receive a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.8.The UE of claim 7, wherein the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.9.A method of wireless communication performed by a user equipment (UE) , comprising:receiving a downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; andtransmitting, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.10.The method of claim 9, wherein the second NDI value is a default initial NDI value.11.The method of claim 10, wherein the default initial NDI value is predefined.12.The method of claim 10, wherein the default initial NDI value is configured.13.The method of claim 9, wherein the DCI message includes a bit field indicating that the first NDI value is different from the second NDI value.14.The method of claim 9, further comprising:receiving a configuration of a maximum quantity of TBs schedulable in a set of time-frequency resources, wherein the maximum quantity is equal to one.15.The method of claim 9, further comprising:receiving a configuration of a maximum quantity of TBs schedulable in a set of shared time-frequency resources, wherein the maximum quantity is greater than one.16.The method of claim 15, wherein the DCI message schedules a plurality of TBs associated with respective TB indexes, the DCI message includes a plurality of bit fields corresponding to the plurality of TB indexes, and a bit field of the plurality of bit fields indicates that the first NDI value is different from the second NDI value.17.An apparatus for wireless communication, comprising:means for receiving a downlink control information (DCI) message that schedules a transport block (TB) associated with a TB index, a hybrid automatic repeat request (HARQ) process identifier, and a first new data indicator (NDI) value that is different from a second NDI value, the second NDI value being an initial NDI value associated with the TB index and the HARQ process identifier, the DCI message being an initial decoded DCI message that schedules any TB associated with the TB index and HARQ process identifier; andmeans for transmitting, in accordance with the first NDI value being different from the second NDI value, an indication of an unsuccessful HARQ process termination associated with the TB index and the HARQ process identifier.18.The apparatus of claim 17, wherein the second NDI value is a default initial NDI value.19.The apparatus of claim 18, wherein the default initial NDI value is predefined.20.The apparatus of claim 18, wherein the default initial NDI value is configured.
