Identifying unsuccessful termination of hybrid automatic repeat request process

Abstract

Various aspects of the present disclosure generally relate to wireless communication. Some aspects more specifically relate to a user equipment (UE) detecting an unsuccessful termination of a hybrid automatic repeat request (HARQ) process associated with a transport block (e.g., due to a negative acknowledgement (NACK) to acknowledgement (ACK) error) and reporting the unsuccessful termination of the HARQ process associated with the transport block to a network node. For example, the UE can detect and report a case where a transport block associated with a HARQ process identifier was not decoded and the UE received another transport block associated with the same HARQ process identifier. Additionally, the UE can detect and report a case where a transport block associated with a HARQ identifier is associated with a new data indicator value that is different from an expected value.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This Patent Application claims priority to U.S. Patent Application No. 18 / 634,826, filed April 12, 2024, entitled “IDENTIFYING UNSUCCESSFUL TERMINATIONS OF HYBRID AUTOMATIC REPEAT REQUEST PROCESSES,” and assigned to the assignee hereof. The disclosure of the prior application is considered part of and is incorporated by reference into this Patent Application. TECHNICAL FIELD

[0002] Aspects of the disclosure relate generally to wireless communication, and more specifically to techniques, apparatuses, and methods associated with identifying unsuccessful terminations of hybrid automatic repeat request processes. BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various types of communication such as voice, text, messaging, video, data, and / or other services. Services can include unicast services, multicast services, broadcast services, and / or the like. A typical wireless communication system can employ multiple-access technologies that can support communication with multiple users by sharing available system resources (e.g., time, frequency, space, and / or device transmit power). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide a common protocol that enables different wireless communication devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is New Radio (NR). NR, which can also be referred to as 5G, is a set of enhancements to the UE and NR mobile communication technologies introduced with a previous release of 3GPP that can be implemented by mobile network operators to provide a more capable mobile communication network that supports improved mobile broadband and

[0005] In some wireless communications networks, devices (e.g., user equipment (UE), network nodes) can perform hybrid automatic repeat request (HARQ) procedures to improve reliability of communications exchanged between devices. For example, a transmitting device can transmit a transport block (e.g., data) to a receiving device, and the receiving device can attempt to decode the data. In a case that the receiving device successfully decodes the data, the receiving device can send a HARQ acknowledgement (ACK) message to the transmitting device. Additionally, in a case that the receiving device fails to successfully decode the data, the receiving device can send a HARQ negative ACK (NACK) message to the transmitting device. In some cases, in a case that the receiving device indicates a NACK message, the transmitting device can incorrectly detect an ACK message. Such errors can reduce reliability of communications between the transmitting device and the receiving device, can introduce latency into communications between the transmitting device and the receiving device, or can otherwise degrade quality of communications between the transmitting device and the receiving device. SUMMARY

[0006] Some aspects described herein relate to a method of wireless communication by a user equipment (UE). The method can include receiving, from a network node, control information that schedules a first transport block and indicates that the first transport block has a same hybrid automatic repeat request (HARQ) identifier as a second transport block. The method can include identifying an unsuccessful termination of a HARQ process associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. The method can include sending, to the network node, signaling that indicates the unsuccessful termination of the HARQ process associated with the second transport block.

[0007] Some aspects described herein relate to a method of wireless communication by a network node. The method can include transmitting, to a UE, control information that schedules a first transport block and indicates that the first transport block has a same HARQ identifier as a second transport block. The method can include receiving, from the UE, signaling that indicates an unsuccessful termination of a HARQ process associated with the second transport block, where receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE can include a processing system including one or more processors and one or more memories coupled with the one or more processors. The processing system can be configured to cause the UE to receive, from a network node, control information that schedules a first transport block and indicates that the first transport block has a same HARQ identifier as a second transport block. The processing system can cause the UE to identify an unsuccessful termination of a HARQ process associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. The processing system can cause the UE to transmit, to the network node, signaling that indicates the unsuccessful termination of the HARQ process associated with the second transport block.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node can include a processing system including one or more processors and one or more memories coupled with the one or more processors. The processing system can cause the network node to transmit, to a UE, control information that schedules a first transport block and indicates that the first transport block has a same HARQ identifier as a second transport block. The processing system can cause the network node to receive, from the UE, signaling that indicates an unsuccessful termination of a HARQ process associated with the second transport block, where receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive control information from a network node scheduling a first transport block and indicating that the first transport block has the same HARQ identifier as a second transport block. When executed by one or more processors of the UE, the set of instructions enables the UE to identify the unsuccessful termination of the HARQ procedure associated with the second transport block in response to the UE's failure to successfully decode the second transport block, the control information scheduling a first transport block having the same HARQ identifier as the second transport block, or both. When executed by one or more processors of the UE, the set of instructions enables the UE to send signaling to the network node indicating the unsuccessful termination of the HARQ procedure associated with the second transport block.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to send control information to a UE scheduling a first transport block and indicating that the first transport block has the same HARQ identifier as a second transport block. When executed by one or more processors of the network node, the set of instructions enables the network node to receive signaling from the UE indicating unsuccessful termination of a HARQ procedure associated with the second transport block, wherein the receiving signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling a first transport block having the same HARQ identifier as the second transport block, or both.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving control information from a network node that schedules a first transport block and indicates that the first transport block has the same HARQ identifier as a second transport block. The apparatus may include components for identifying unsuccessful termination of a HARQ process associated with the second transport block in response to a UE's failure to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both. The apparatus may include components for sending signaling to the network node indicating unsuccessful termination of a HARQ process associated with the second transport block.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for sending control information to a UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as a second transport block. The apparatus may also include components for receiving from the UE signaling an unsuccessful termination of a HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling a first transport block having the same HARQ identifier as the second transport block, or both.

[0014] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0015] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating communication between an example network node and an example UE in a wireless network according to this disclosure.

[0019] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating an example of an unsuccessful termination of the HARQ identification process according to this disclosure.

[0021] Figure 5 This is a diagram illustrating a wireless communication network according to the present disclosure.

[0022] Figures 6A to 9B This is a diagram illustrating an example of signaling exchanged between a transmitting device and a receiving device according to this disclosure.

[0023] Figure 10 This is a diagram illustrating an example of signaling exchanged between a network node and a UE according to this disclosure.

[0024] Figure 11 and Figure 12This is a flowchart illustrating an example procedure performed according to this disclosure.

[0025] Figure 13 and Figure 14 This is a diagram of an example device for wireless communication that fails to terminate the HARQ process according to this disclosure. Detailed Implementation

[0026] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0028] In some wireless communication networks, devices (e.g., User Equipment (UE), network nodes) can perform a Hybrid Automatic Repeat Request (HARQ) procedure to improve the reliability of communications exchanged between devices. For example, a transmitting device may transmit a transport block (e.g., data) to a receiving device, and the receiving device may attempt to decode the data. If the receiving device successfully decodes the data, it may send a HARQ Acknowledgment (ACK) message to the transmitting device. Additionally, if the receiving device fails to decode the data, it may send a HARQ Negative Acknowledgment (NACK) message to the transmitting device. In response to receiving a HARQ NACK message from the receiving device, the transmitting device may perform a retransmission associated with the transport block. For example, the transmitting device may retransmit a portion of the transport block (e.g., the portion of the transport block that the receiving device failed to decode). Additionally or alternatively, the transmitting device may retransmit the transport block using the same or different redundant versions (e.g., using the same or different sets of decoded bits associated with the transport block), which may allow the receiving device to perform soft combination or incremental redundancy combination. When a retransmission is received from the sending device, the receiving device may attempt to decode the transport block using a combination of the data received in the initial transmission and the data received in the retransmission.

[0029] In some cases, the transmitting device may continue transmitting retransmissions associated with the transport block until it receives a HARQ ACK message from the receiving device (e.g., indicating that the receiving device has successfully decoded the transport block). In response to receiving a 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 transport block (e.g., data from buffers maintained before the HARQ process terminates). 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 the number of retransmissions performed by the transmitting device meets (e.g., is equal to or greater than) a threshold number associated with the number of retransmissions.

[0030] In some wireless communication networks, devices may additionally support certain Radio Link Control (RLC) procedures to improve the reliability of communication between devices. RLC procedures can correspond to processes and communications performed at the device's RLC layer. In some cases, the receiving device can detect "holes" (e.g., it can detect one or more RLC SDU segments that the receiving device failed to decode). For example, the receiving device can detect holes based on the sequence number associated with the RLC SDU segment, the segmentation information associated with the RLC SDU segment, and / or the segmentation offset associated with the RLC SDU segment.

[0031] In response to the detection or failure to detect a hole associated with the RLC, the receiving device may send an RLCNACK or an RLC ACK, respectively. In some cases, a receiving device sending an RLC NACK may trigger a transmitting device to retransmit one or more segments of the RLC SDU. Additionally, a receiving device sending an RLC ACK may trigger a transmitting device to release a buffer (e.g., an upper buffer) associated with the RLC SDU.

[0032] In cases where the transmitting device terminates the HARQ process without receiving a HARQ ACK from the receiving device (e.g., due to channel conditions between the transmitting and receiving devices, or because the number of retransmissions of a transport block performed as part of the HARQ process meets a threshold), the receiving device can detect the hole as part of the RLC process when the RLC operates according to the acknowledgment mode. In this example, a lower layer of the transmitting device (e.g., the PHY layer) can report the termination of the HARQ process to an upper layer of the transmitting device (e.g., the RLC layer). Here, in response to receiving an indication of termination of the HARQ process from the lower layer, the transmitting device can be triggered to retransmit one or more segments of the RLC SDU.

[0033] In another example, when the RLC operates under acknowledgment mode due to an premature ARQ procedure, the receiving device can detect a hole as part of the RLC procedure. Here, the receiving device can send an RLC NACK to the transmitting device before the HARQ procedure has terminated (e.g., in the RLC status report), and can eventually decode the transport block via the HARQ procedure. Additionally, in the case of a NACK-to-ACK error, the receiving device can detect a hole as part of the RLC procedure. For example, if the receiving device sends a HARQ NACK to the transmitting device and the transmitting device interprets the HARQ NACK as a HARQ ACK, the transmitting device can terminate the HARQ procedure (e.g., it can stop the transmission and / or retransmission of the transport block).

[0034] In some cases, the receiving device (e.g., the UE) can detect NACK-ACK errors based on hole detection and a timer. That is, the UE can be configured to send an RLC status report indicating an RLC NACK when the timer expires. The timer's expiration time can be configured to reduce the latency associated with the UE detecting and reporting the NACK-ACK error, while also preventing the UE from initiating a premature ARQ procedure (e.g., when the UE sends an RLC NACK associated with a transport block and subsequently decodes that transport block as part of a HARQ procedure). In some cases, increasing the amount of time before the timer expires can reduce the likelihood of the UE initiating a premature ARQ procedure, but may conversely increase the latency associated with the UE detecting the NACK-ACK error.

[0035] The various aspects generally involve a receiving device (e.g., a UE) detecting a NACK-ACK error before the timer associated with the UE indicating RLC NACK expires. Some aspects more specifically involve the UE detecting the unsuccessful termination of a HARQ procedure associated with a transport block (e.g., due to a NACK-ACK error) before the timer expires and reporting the unsuccessful termination of the HARQ procedure associated with that transport block to a transmitting device (e.g., a network node). For example, the UE may detect and report a situation where a transport block associated with a HARQ procedure identifier has not been decoded and the UE receives another transport block associated with the same HARQ procedure identifier. Additionally, the UE may detect and report a situation where a transport block associated with a HARQ identifier is associated with a new Data Indicator (NDI) value that differs from the expected value (e.g., this could correspond to a situation where the UE previously failed to receive or decode control information scheduling another transport block associated with the same HARQ identifier and another transport block). In both scenarios, the UE's ability to detect and report the unsuccessful termination of the HARQ procedure based on the HARQ identifier associated with the transport block, the UE's failure to successfully decode the transport block, and / or the value of the NDI allows the UE to detect and report a NACK to ACK error before the timer expires. The network node can then initiate an ARQ procedure before the timer expires (e.g., in response to receiving a report from the UE indicating the unsuccessful termination of the HARQ procedure).

[0036] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to reduce latency and signaling overhead associated with communication between devices. For example, the UE detecting and reporting a NACK-ACK error before a timer expires can reduce the latency associated with initiating an RLC retransmission in the case of a NACK-ACK error without increasing signaling overhead (e.g., due to an increase in cases where the UE initiates an ARQ procedure prematurely). Additionally, the described techniques can be used to reduce overhead at the UE by reducing buffering at the UE (or at another receiving device). For example, if the latency associated with receiving lost packets (e.g., lost RLC SDUs, lost RCL SDU segments) is reduced by reducing the latency associated with initiating an ARQ procedure, then in cases where packets need to be delivered in order (e.g., when the RLC operates according to an acknowledgment mode), the UE can reduce its use of higher-layer buffers (e.g., buffers at the RLC layer, buffers at the PDCP layer).

[0037] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0038] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0039] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0040] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0041] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0043] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0044] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0045] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, PDCP functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the RLC layer, MAC layer, and / or one or more higher PHY layers, at least in part, depending on function splits (such as those defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., depending on function splits (such as lower-layer function splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0046] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0047] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0048] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0049] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating 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. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0050] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0051] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0052] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In such examples, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0053] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle 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), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0054] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0055] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0056] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0057] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0058] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0059] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0060] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0061] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive control information from a network node scheduling a first transport block and indicating that the first transport block has the same HARQ identifier as the second transport block; in response to the UE failing to successfully decode the second transport block, the control information scheduling a first transport block having the same HARQ identifier as the second transport block, or both, to identify the unsuccessful termination of the HARQ procedure associated with the second transport block; and send signaling to the network node indicating the unsuccessful termination of the HARQ procedure associated with the second transport block. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0062] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send control information to the UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block; and receive from the UE signaling an indication of unsuccessful termination of a HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0063] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0064] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0065] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as referring to a combination of... Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0066] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with… Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0067] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0068] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0069] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0070] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0071] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0072] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0073] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0074] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0075] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0076] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0077] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output symbol streams (e.g., U A set of output symbol streams is provided to a set of modems 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0078] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmissions made directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0079] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0080] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0081] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0082] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0083] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0084] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0085] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0086] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0087] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0088] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0089] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with the unsuccessful termination of an identifying HARQ procedure, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with the identification of an unsuccessful termination of a HARQ procedure, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 1 Process 1100 Figure 12The operation of process 1200 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 11 Process 1100 Figure 12 The process 1200 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0090] In some aspects, UE 120 includes: components for receiving control information from a network node that schedules a first transport block and indicates that the first transport block has the same HARQ identifier as a second transport block; components for identifying the unsuccessful termination of a HARQ process associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both; and / or components for sending signaling to the network node indicating the unsuccessful termination of a HARQ process associated with the second transport block. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0091] In some aspects, network node 110 includes components for sending control information to the UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block; and / or components for receiving from the UE signaling an unsuccessful termination of a HARQ process associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. Components for network node 110 to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a collection of modems 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0092] Figure 4 This is a diagram illustrating example 400 associated with the unsuccessful termination of the HARQ identification process according to this disclosure. (See diagram for example 400 400 400 400 400 400 400 400 400 400 400 400 400 400 400 400 400 400 5 ...500 400 500 500 400 500 500 500 400 500 500 5 Figure 4 As shown, the transmitting device 405 and the receiving device 410 can communicate with each other. For example, the transmitting device 405 can send a MAC PDU 450 to the receiving device 410.

[0093] In some cases, transmitting device 405 may correspond to network node 110, receiving device 410 may correspond to UE 120, and transmitting device 405 may send communication to receiving device 410 via a downlink. In other cases, transmitting device 405 may correspond to UE 120, receiving device 410 may correspond to network node 110, and transmitting device 405 may send communication to receiving device 410 via an uplink.

[0094] Both transmitting device 405 and receiving device 410 may include an RLC layer 415 and a MAC / PHY layer 420 (e.g., including a MAC layer, a PHY layer, or both). Although not illustrated, transmitting device 405 and receiving device 410 may also include additional layers such as a PDCP layer, an RRC layer, and / or an SDAP layer. In example 400, the RLC 415-a of transmitting device 405 and the RLC layer 415-b of receiving device 410 may exchange RLC signaling 490. Additionally, the MAC / PHY layer 420-a of transmitting device 405 and the MAC / PHY layer 420-b of receiving device 410 may exchange MAC / PHY signaling 475.

[0095] In Example 400, the RLC layer 415-a of transmitting device 405 can receive RLCSDU 425 from the PDCP layer of transmitting device 405. RLC layers 415 (e.g., 415-a and 415-b) can have several different modes. Specifically, transmitting device 405 and receiving device 410 can operate RLC layer 415 in a transparent mode, an unacknowledged mode, or an acknowledged mode. In the example where RLC layer 415-a operates in transparent mode, receiving device 410 can pass RLC SDU 425 through RLC layer 415-a (e.g., from the PDCP layer of transmitting device 405 to the MAC layer) as RLC PDU 445 without additional processing by RLC layer 415-a. In another example of RLC layer 415-a operating in unacknowledged mode, transmitting device 405 may perform segmentation functionality (e.g., the segmentation functionality of segmentation and / or re-segmentation functionality 435 illustrated in example 400), but may not perform ARQ functionality 440. In another example of RLC layer 415-a operating in acknowledged mode, transmitting device 405 may perform both segmentation and / or re-segmentation functionality 435 and ARQ functionality 440.

[0096] When operating RLC layer 415-a according to the acknowledgment mode, transmitting device 405 may perform segmentation and / or resegmentation functionality 435 to adapt RLC SDU 425 to available resources (e.g., for transmission). For example, transmitting device 405 may segment RLC SDU 425 to generate multiple RLC SDU segments. Transmitting device 405 may perform resegmentation functionality (e.g., segmentation and / or resegmentation functionality 435) to support ARQ functionality 440, where the available payload size can be changed.

[0097] The RLC layer 415-a of transmitting device 405 can generate an RLC PDU 445 that may include an RLC SDU 425. In some cases, the RLC PDU 445 may include one or more RLC SDUs 425 or one or more RLC SDU segments associated with an RLC SDU 425 (e.g., generated by the segmentation functionality of segmentation and / or resegmentation functionality 435). Each RLC SDU segment in the RLC PDU 445 may include a header that includes a sequence number associated with the RLC SDU segment. The RLC layer 415-a may then provide the RLC PDU 445 to the MAC / PHY layer 420-a of the transmitting device, and the MAC / PHY layer 420-a may receive a MAC PDU 450.

[0098] MAC PDU 450 may correspond to a transport block (e.g., transmitted from transmitting device 405 to receiving device via MAC / PHY signaling 475). MAC PDU 450 may include one or more sub-PDUs 455 (e.g., MAC SDUs). Each sub-PDU 455 may include a MAC sub-header 460, an RLC header 465, and an RLC SDU or RLC SDU segment 470. In some examples, RLC PDU 445 may correspond to the RLC header 465 and RLC SDU or RLC SDU segment 470 in each sub-PDU 455. The RLC header 465 may include information related to the RLC SDU or RLC SDU segment 470. For example, the RLC header 465 may include a sequence number associated with the RLC SDU or RLCSDU segment 470, segmentation information associated with the RLC SDU or RLC SDU segment 470, and / or segmentation offset associated with the RLC SDU or RLC SDU segment 470.

[0099] The MAC / PHY layer 420-a of the transmitting device 405 can send MAC PDU 450 to the receiving device 410 via MAC / PHY signaling 475. The MAC / PHY layer 420-b of the receiving device 410 can provide MAC PDU 450 to the RLC layer 415-b of the receiving device 410. The receiving device 410 can perform a HARQ procedure associated with MAC PDU 450. For example, if the receiving device 410 successfully decodes MAC PDU 450, the receiving device 410 can send a HARQACK message to the transmitting device 405 via MAC / PHY signaling 475. Additionally, if the receiving device 410 fails to decode MAC PDU 450, the receiving device 410 can send a HARQ NACK message to the transmitting device 405 via MAC / PHY signaling 475. In response to receiving a HARQNACK message from the receiving device 410, the transmitting device 405 can perform a retransmission associated with MAC PDU 450. For example, transmitting device 405 may retransmit a portion of MAC PDU 450 (e.g., a portion selected based on the portion of MAC PDU 450 that receiving device 410 was unable to successfully decode). Upon receiving a retransmission from transmitting device 405, receiving device 410 may attempt to decode MAC PDU 450 using a combination of data received in the initial transmission of the transport block and data received in the retransmission.

[0100] In some cases, transmitting device 405 may continue transmitting retransmissions associated with MAC PDU 450 until transmitting device 405 receives a HARQ ACK message from receiving device 410 (e.g., indicating that the receiving device has successfully decoded MAC PDU 450). In response to receiving a HARQ ACK message from receiving device 410, transmitting device 405 may terminate the HARQ process. In other cases, transmitting device 405 may terminate the HARQ process without receiving a HARQ ACK message from receiving device 410. For example, transmitting device 405 may terminate the HARQ process after the number of retransmissions performed by transmitting device 405 meets (e.g., equal to or greater than) a threshold number associated with the number of retransmissions.

[0101] When the receiving device's RLC layer 415-b operates according to the acknowledgment mode, the receiving device 410 may additionally perform an ARQ procedure. For example, the receiving device 410's RLC layer 415-b may support ARQ functionality 440. Here, the receiving device 410's RLC layer 415-b may have hole detection functionality 480, which enables the receiving device 410 to detect holes (e.g., detect one or more RLC SDU segments 470 in the MAC PDU 450 that the receiving device 410 has failed to decode). In some cases, receiving device 410 can detect holes based on the sequence number associated with the RLC SDU or RLC SDU segment 470 (e.g., included in the RLC header 465), segmentation information associated with the RLC SDU or RLC SDU segment 470 (e.g., included in the RLC header 465, included in the MAC subheader 460), and / or the segmentation offset associated with the RLC SDU or RLC SDU segment 470 (e.g., included in the RLC header 465, included in the MAC subheader 460). In some cases, receiving device 410 can detect holes with or without assistance from a lower layer (e.g., the MAC / PHY layer 420-b of receiving device 410).

[0102] The receiving device 410 can be based on a timer (e.g., t-ReassemblyA timer is used to detect gaps associated with the transmission of MAC PDU 450. For example, receiving device 410 may identify one or more lost RLC SDUs or RLC SDU segments 470 based on a sequence number associated with an RLC SDU or RLC SDU segment 470 that has been successfully received and decoded. Receiving device 410 may start a timer in response to identifying one or more lost RLC SDUs or RLC SDU segments 470. If receiving device 410 successfully receives and decodes the one or more lost RLC SDUs or RLC SDU segments 470 before the timer expires (e.g., as part of a HARQ procedure associated with MAC PDU 450), receiving device 410 may reset the timer. Additionally, if receiving device 410 does not successfully receive and decode the one or more lost RLC SDUs or RLC SDU segments 470 before the timer expires, receiving device 410 may generate a status report 485 and send it to transmitting device 405.

[0103] In one example, the receiving device can detect a hole in the case of a HARQ NACK to HARQ ACK error as part of the RLC process. In this example, the receiving device 410 can send a HARQ NACK to the transmitting device 405, and the transmitting device 405 can interpret the HARQ NACK as a HARQ ACK. Therefore, the transmitting device 405 can terminate the HARQ process (e.g., stop HARQ transmission and / or retransmission for MAC PDU 450).

[0104] In Example 400, receiving device 410 can detect a NACK-ACK error before the timer associated with hole detection functionality 480 expires (e.g., before the t-Reassembly timer expires). Specifically, receiving device 410 can detect a NACK-ACK error based on the detection of an unsuccessful termination of the HARQ process associated with MAC PDU 450 (e.g., due to a NACK-ACK error). Receiving device 410 can then report the unsuccessful termination of the HARQ process associated with MAC PDU 450 to transmitting device 405. For example, receiving device 410 can detect and report a situation where MAC PDU 450 associated with a HARQ process identifier is not decoded and receiving device 410 receives another MAC PDU 450 associated with the same HARQ process identifier. Additionally, receiving device 410 can detect and report cases where a MAC PDU 450 associated with a HARQ identifier is associated with an NDI value that is different from the expected value (e.g., this could correspond to a case where receiving device 410 previously failed to receive or decode control information scheduling another MAC PDU 450 associated with the same HARQ identifier and that other MAC PDU 450).

[0105] The status report 485 can be used with a timer (e.g., t-StatusProhibit This is associated with a timer. Here, receiving device 410 may avoid sending status report 485 until the timer expires. In some cases, waiting until the timer expires to send status report 485 can reduce the periodicity associated with receiving device 410 transmitting status report 485. That is, after receiving device 410 transmits status report 485, receiving device 410 may reset and start (e.g., start) the timer, and may not transmit another status report 485 until the timer expires. Status report 485 may include RLC ACK and / or RLC NACK for certain sequence numbers (e.g., associated with MAC PDU 450).

[0106] Receiving device 410 may send a status report 485 in response to a polling request from transmitting device 405. For example, transmitting device 405 may include polling functionality 430 at RLC layer 415-a. In this example, the transmitting device may send a polling request to receiving device 410 (e.g., via RLC signaling 490, via MAC / PHY signaling 475), which triggers receiving device 410 to send status report 485 to transmitting device 405. Transmitting device 405 may send the polling request based on the number of MAC PDUs 450 sent to receiving device 410. For example, transmitting device 405 may send the polling request after sending a certain number of MAC PDUs 450 (e.g., as determined by variables such as...). pollPDU (As indicated by the variable). In another case, transmitting device 405 may send a polling request based on (e.g., via one or more MAC PDUs 450) the number of bytes sent to receiving device 410. For example, transmitting device 405 may send a polling request after sending a certain number of bytes (e.g., as indicated by a variable such as). pollByte (Indicated by the variable).

[0107] The receiving device 410 may send a status report 485 via MAC / PHY signaling 475 or, in some other cases, via RLC signaling 490. In response to receiving the status report 485, the transmitting device 405 may perform an ARQ procedure (e.g., using ARQ functionality 440 of RLC layer 415-a). For example, the transmitting device 405 may retransmit either the RLC SDU or RLC SDU segment 470 corresponding to the sequence number indicated in the status report 485 as having failed to be successfully received and decoded. In some cases, the transmitting device 405 may continue to retransmit any RLC SDU or RLC SDU segment 470 until the receiving device 410 indicates that the RLC SDU or RLC SDU segment 470 has been successfully received and decoded (e.g., via an RLC ACK for the sequence number associated with the RLC SDU or RLC SDU segment 470). Additionally or alternatively, the transmitting device 405 may retransmit more than a threshold number of times associated with the RLC SDU or RLC SDU segment 470 (e.g., maxRetxThreshold In cases where this is the case, avoid sending a retransmission of the RLC SDU or RLC SDU segment 470.

[0108] Figure 5 This is a diagram illustrating a wireless communication network 500 according to this disclosure. For example... Figure 5As shown, network node 110 and UE 120 can communicate with each other. In some cases, UE 120 can be configured to detect and report unsuccessful termination of a HARQ procedure, as described herein. For example, in the case where UE 120 identifies unsuccessful termination of a HARQ procedure associated with transport block 530, UE 120 can send an unsuccessful HARQ procedure termination indication 545 to network node 110. In some cases, transport block 530 may include aspects of MAC PDU 450.

[0109] UE 120 may optionally instruct network node 110 that UE 120 supports the UE capability 505 to detect and report the termination of an unsuccessful HARQ procedure.

[0110] Network node 110 can send and UE 120 can receive configuration 510. Specifically, network node 110 can send signaling to UE 120 instructing UE 120 to report the unsuccessful termination of the HARQ procedure to network node 110. If UE 120 sends UE capability 505, network node 110 can send configuration 510 to UE 120 in response to UE 120's report indicating via UE capability 505 that UE 120 can support the report of unsuccessful termination of the HARQ procedure.

[0111] Configuration 510 can instruct the UE to report unsuccessful HARQ procedure terminations based on each cell group. For example, configuration 510 can instruct UE 120 to report unsuccessful HARQ procedure terminations for each component carrier in the cell group and for each HARQ identifier associated with each component carrier. In another case, configuration 510 can instruct UE 120 to report unsuccessful HARQ procedure terminations based on each component carrier. For example, configuration 510 can instruct UE 120 to report unsuccessful HARQ procedure terminations for each HARQ identifier associated with one or more component carriers, and instruct UE 120 to avoid reporting unsuccessful HARQ procedure terminations for HARQ identifiers associated with one or more other component carriers.

[0112] In another scenario, configuration 510 may instruct UE 120 to report unsuccessful HARQ procedure terminations based on each subset of HARQ identifiers (e.g., for a subset of HARQ identifiers associated with a component carrier). Here, network node 110 may configure (e.g., via configuration 510 or via other configuration signaling) a subset of HARQ identifiers. For example, network node 110 may indicate a list of HARQ identifiers for each component carrier for which UE 120 is configured to report unsuccessful HARQ procedure terminations. Additionally or alternatively, network node 110 may enable or disable reporting of unsuccessful HARQ procedure terminations for each HARQ identifier and for each component carrier. In one example, network node 110 may use a first subset of HARQ identifiers in the component carriers (e.g., HARQ identifiers 0-7) for latency-sensitive services (e.g., for communications associated with Extended Reality (XR)). Here, network node 110 can instruct UE 120 via configuration 510 to report unsuccessful HARQ process termination associated with a first subset of HARQ identifiers in component carriers, and instruct UE 120 to avoid reporting unsuccessful HARQ process termination for a second subset of HARQ identifiers in component carriers or for HARQ identifiers associated with other component carriers.

[0113] Network node 110 can send configuration 510 via RRC signaling, MAC-CE, or DCI. In one example where network node 110 sends configuration 510 to UE 120 via DCI, configuration 510 and control information 515 can be carried by the same DCI message. That is, the DCI can carry both configuration 510 and control information 515 for scheduling transport block 530. In this example, network node 110 can dynamically enable or disable (e.g., via DCI signaling) UE reporting of unsuccessful HARQ procedure termination associated with a given HARQ identifier.

[0114] Network node 110 can send control information 515, and UE 120 can attempt to receive and decode the control information. In some cases, control information 515 can be sent via DCI signaling. Control information 515 can schedule the transmission of transport block 530. That is, control information 515 may include scheduling information for the transmission of one or more PDSCHs (e.g., for one or more transport blocks 530 transmitted via PDSCH). Specifically, control information 515 may indicate a set of resources (e.g., one or more time-domain resources, one or more frequency-domain resources) for UE 120 to monitor in order to detect subsequent transmissions of transport block 530. Control information 515 may also include indications of HARQ identifier 520 and NDI 525-a associated with the scheduled transport block 530.

[0115] Network node 110 may send transport block 530, and UE 120 may attempt to receive and decode the transport block (e.g., via PDSCH and according to control information 515). In some cases, UE 120 may fail to decode at least a portion of transport block 530. In one example, UE 120 may successfully receive and decode control information 515, and according to control information 515, may monitor the resource set associated with transport block 530. After monitoring the resource set, UE 120 may fail to successfully decode transport block 530. Here, UE 120 may send HARQ NACK 535 to network node 110. In another example, UE 120 may fail to successfully receive and decode control information 515. In this example, UE 120 may not monitor the resources associated with transport block 530, and therefore may not receive or decode transport block 530. Here, UE 120 may not send HARQ NACK 535 to network node 110. In some cases, UE 120 may not send any HARQ message associated with transport block 530 (e.g., UE 120 may not send HARQ ACK or HARQ NACK) to network node 110 to indicate that UE failed to decode transport block 530 (e.g., it may indicate the equivalent of HARQ NACK 535).

[0116] In Example 500, network node 110 may incorrectly interpret HARQ NACK 535 or UE 120's failure to send any HARQ feedback associated with transport block 530 as HARQ ACK. That is, if UE 120 fails to decode transport block 530, network node 110 may incorrectly determine that UE 120 successfully decoded transport block 530. This can be referred to as a NACK-to-ACK error. As a result of a NACK-to-ACK error, network node 110 may terminate the HARQ process associated with transport block 530 (e.g., and associated with HARQ identifier 520) and may not send any future retransmissions associated with transport block 530 as part of the HARQ process.

[0117] Following a NACK-ACK error associated with HARQ identifier 520, network node 110 may send additional control information 540 that schedules another transport block associated with the same HARQ identifier 520 as transport block 530 (which UE 120 failed to decode). Control information 540 may include information indicating the set of resources associated with subsequent PDSCH transmissions (e.g., another transport block), an indication that the other transport block is associated with the same HARQ identifier 520 as transport block 530, and an NDI 525-b associated with the other transport block. In some cases, NDI 525-b may be different from NDI 525-a. For example, NDI 525-a may be set to 0, while NDI 525-b is switched to 1, which may indicate that control information 540 is associated with a transport block different from transport block 530. That is, in the case where NDI 525-b is different from NDI 525-a, UE 120 can determine that control information 540 is scheduling a new transport block. Alternatively or additionally, NDI 525-b may be associated with the same indication control information 540 as NDI 525-a, which may be associated with transport block 530. For example, if NDI 525-b is the same as NDI 525-a, UE 120 may determine that control information 540 is scheduling a retransmission of transport block 530.

[0118] UE 120 can identify the termination of an unsuccessful HARQ procedure associated with HARQ identifier 520. For example, UE 120 can detect the termination of an unsuccessful HARQ procedure in response to receiving control information 540 scheduling a new transport block associated with the same HARQ identifier 520, while UE 120 has not yet successfully decoded a previously sent transport block 530. Specifically, if UE 120 receives control information 540 scheduling another transport block associated with the same HARQ identifier as transport block 530 but with an NDI 525-b different from NDI 525-a, while UE 120 has not yet successfully decoded transport block 530, then UE 120 can identify the unsuccessful termination of the HARQ procedure associated with transport block 530 and HARQ identifier 520.

[0119] In response to identifying an unsuccessful termination of a HARQ procedure and according to configuration 510, UE 120 may send an unsuccessful HARQ procedure termination indication 545 to network node 110. UE 120 may send the unsuccessful HARQ procedure termination indication 545 via UCI on PUCCH or PUSCH. If UE 120 sends the unsuccessful HARQ procedure termination indication 545 via UCI, network node 110 may reserve periodic resources (e.g., periodic PUCCH resources, periodic CG-PUSCH resources) for UE 120 to send the unsuccessful HARQ procedure termination indication 545. Additionally or alternatively, UE 120 may send a scheduling request to network node 110, which may, for example, indicate that UE 120 has identified an unsuccessful termination of a HARQ procedure and / or may indicate that UE 120 is requesting to send the unsuccessful HARQ procedure termination indication 545. In response to receiving a scheduling request, network node 110 can dynamically schedule the PUCCH or PUSCH transmission by UE 120 for the unsuccessful HARQ procedure termination indication 545. In some cases where UE 120 transmits the unsuccessful HARQ procedure termination indication 545 via UCI, UE 120 may not include timestamp information related to the unsuccessful HARQ procedure termination.

[0120] In another scenario, UE 120 may send a failed HARQ procedure termination indication 545 via a MAC-CE on the PUSCH. Here, the MAC-CE may have a fixed length or a variable length. Additionally, the MAC-CE carrying the failed HARQ procedure termination indication 545 may include a specific logical channel identifier (LCID).

[0121] In another scenario, UE 120 may send a failed HARQ procedure termination indication 545 via an RLC status report on the PUSCH. In some cases, the RLC status report may include a reference... Figure 4 The description covers various aspects of the status report 485. For example, UE 120 can send an unsuccessful HARQ procedure termination indication 545 via an RLC status report by reporting an RLC NACK (e.g., based on a lost sequence number) for an RLC SDU or SDU segment associated with transport block 530. Here, UE 120 can respond to the unsuccessful termination of the HARQ procedure before the timer associated with the status report transmission expires (e.g., before...). t-StatusProhibit Send an RLC status report before the timer expires.

[0122] If UE 120 sends an unsuccessful HARQ procedure termination indication 545 via an RLC status report, UE 120 may avoid sending an RLC status report including an RLC NACK associated with transport block 530, or UE 120 may additionally send an RLC status report including an RLC NACK associated with transport block 530. That is, in either case, UE 120 may send an RLC status report to report one or more RLC ACKs (e.g., allowing network node 110 to clear the Tx buffer). In one example, UE 120 may avoid sending an additional RLC status report associated with transport block 530 in response to a hole detection at UE 120. Conversely, UE 120 may send an RLC status report associated with the transport block in response to a poll from network node 110 (e.g., when network node 110 requests UE 120 to send an RLC status report).

[0123] In response to receiving a failed HARQ procedure termination indication 545, network node 110 may determine to send one or more ARQ retransmissions associated with transport block 530. If network node 110 sends control information 540 scheduling a transport block with the same HARQ identifier 520 as transport block 530 before UE 120 successfully decodes transport block 530 due to a NACK-ACK error, network node 110 may be triggered to perform the one or more ARQ retransmissions associated with transport block 530 in response to receiving the failed HARQ procedure termination indication 545. Additionally, if network node 110 sends control information 540 scheduling a transport block with the same HARQ identifier 520 as transport block 530 before UE 120 successfully decodes transport block 530 due to network node 110 abandoning the HARQ retransmission process associated with transport block 530 (e.g., because the number of retransmissions associated with transport block 530 meets a threshold), network node 110 may perform the one or more ARQ retransmissions independently of receiving the unsuccessful HARQ process termination indication 545.

[0124] Figure 6A and Figure 6B This is an illustration of example 600 of signaling exchanged between a transmitting device and a receiving device (e.g., between a network node and a UE) according to this disclosure.

[0125] Figure 6A and Figure 6B Example 600 illustrates a network node that has been configured with a threshold associated with the retransmission of transport block 630. Specifically, the network node can (e.g., via reference to...) Figure 5The described configuration 510) instructs the UE to avoid sending an unsuccessful HARQ procedure termination indication 645 if the number of retransmissions associated with transport block 630 has exceeded a threshold. That is, if the number of retransmissions associated with transport block 630 is less than (or in some cases equal to) the threshold and the UE identifies an unsuccessful termination of the HARQ procedure associated with that transport block, the UE may send an unsuccessful HARQ procedure termination indication 645. Additionally, if the number of retransmissions associated with transport block 630 is greater than (or in some cases equal to) the threshold and the UE identifies an unsuccessful termination of the HARQ procedure associated with that transport block, the UE may not send an unsuccessful HARQ procedure termination indication 645.

[0126] Network nodes can send signaling to the UE to configure a threshold number of times. For example, the network node can send (e.g., via RRC signaling, via as referenced) Figure 5 The described configuration 510) indicates the number of thresholds (e.g., max_HARQ_ReTx (Signaling).

[0127] If the number of retransmissions associated with transport block 630 is greater than (or equal to) a threshold, the UE avoids sending the unsuccessful HARQ procedure termination indication 645. This reduces the likelihood that the UE will send the unsuccessful HARQ procedure termination indication 645 when the network node has already given up on the HARQ retransmission procedure (e.g., instead of failing to terminate the HARQ procedure due to a NACK to ACK error). This, in turn, reduces the signaling overhead associated with the UE attempting to identify and report the unsuccessful HARQ procedure termination.

[0128] In Example 600-a, DCI 615-a can schedule the initial transmission of transport block 630-a and can indicate that transport block 630-a is associated with HARQ identifier 620-a and NDI 625-a. However, the UE may fail to successfully decode the initial transmission of transport block 630-a and may send HARQ NACK 635-a to the network node. The network node can schedule one or more retransmissions of transport block 630-b (e.g., via DCI 615-b, each DCI indicating the same HARQ identifier 620-a and NDI 625-a as the initial transmission of transport block 630-a). If the UE fails to successfully decode transport block 630 (e.g., using a combination of the initial transmission of transport block 630-a and one or more retransmissions of transport block 630-b), the UE can continue to send HARQ NACK 635-b associated with transport block 630.

[0129] If the UE receives a DCI 615-c for another transport block (e.g., different from transport block 630) that has the same HARQ identifier 620-a as transport block 630 but has a different NDI 625-b, the UE can identify the unsuccessful termination of the HARQ procedure associated with transport block 630. However, in example 600-a, the number of retransmissions associated with transport block 630 can be greater than or equal to a threshold. Accordingly, the UE can avoid sending the unsuccessful HARQ procedure termination indication 645-a. For example, the network node can send four retransmissions of transport block 630. If the threshold is four, the UE can avoid sending the unsuccessful HARQ procedure termination indication 645-a in response to the retransmission count (four) being equal to the count threshold (four).

[0130] In Example 600-b, DCI 615-d can schedule the initial transmission of transport block 630-d and can indicate that transport block 630-d is associated with HARQ identifier 620-b and NDI 625-c. However, the UE may fail to decode the initial transmission of transport block 630-d and may send HARQ NACK 635-d to the network node. The network node can schedule another retransmission of transport block 630-e (e.g., via DCI 615-e, each DCI indicating the same HARQ identifier 620-b and NDI 625-c as the initial transmission of transport block 630-d). If the UE fails to decode transport block 630 (e.g., using a combination of the initial transmission of transport block 630-d and a retransmission of transport block 630-e), the UE can send another HARQ NACK 635-e associated with transport block 630.

[0131] If the UE receives a DCI 615-f for another transport block (e.g., different from transport block 630) that has the same HARQ identifier 620-b as transport block 630 but has a different NDI 625-d, the UE can identify the unsuccessful termination of the HARQ procedure associated with transport block 630. Additionally, in example 600-b, the number of retransmissions associated with transport block 630 can be less than or equal to a threshold. Accordingly, the UE can send an unsuccessful HARQ procedure termination indication 645-b. For example, a network node can send two transmissions associated with transport block 630. If the threshold number is four, the UE can send the unsuccessful HARQ procedure termination indication 645-b in response to the number of transmissions (two) being less than the threshold (four).

[0132] In some cases, the UE may detect fewer retransmissions associated with transport block 630 than the network node has sent. For example, the UE may fail to receive or detect the DCI 615 that schedules a retransmission associated with transport block 630. Here, the UE may incorrectly determine that the number of retransmissions associated with transport block 630 is less than a threshold. Here, the UE may send a failed HARQ procedure termination indication 645.

[0133] Figure 7 This is an illustration of example 700 of signaling exchanged between a transmitting device and a receiving device (e.g., between a network node and a UE) according to this disclosure.

[0134] Figure 7 An example is illustrated by configuring a timer associated with a network node to identify a UE whose HARQ procedure has not been successfully terminated. Specifically, the network node can (e.g., via reference) Figure 5 The described configuration 510) instructs the UE to identify the termination of an unsuccessful HARQ procedure in response to the expiration of a timer. Specifically, the UE may start the timer in response to sending a HARQNACK 735 for transport block 730. The UE may identify the unsuccessful termination of the HARQ procedure associated with transport block 730 if the timer expires before the UE detects a retransmission associated with transport block 730 or before the UE detects a DCI 715 that schedules a new transport block associated with the same HARQ identifier 720 (such as a DCI 715 indicating the same HARQ identifier 720 but a different NDI 725).

[0135] Network nodes can send signaling to the UE to configure timer values. For example, a network node can send (e.g., via RRC signaling, via reference) Figure 5 The described configuration 510) is a signaling instruction that indicates the value of the timer.

[0136] In Example 700, DCI 715-a can schedule the initial transmission of transport block 730-a and can indicate that transport block 730-a is associated with HARQ identifier 720 and NDI 725-a. However, the UE may fail to successfully decode the initial transmission of transport block 730-a, and at time 705-a, a HARQ NACK 735-a can be sent to the network node and a timer can be started (e.g., initiated). At time 705-b, the network node can schedule a retransmission of transport block 730-b (e.g., via DCI 715-b, which indicates the same HARQ identifier 720 and NDI 725-a as the initial transmission of transport block 730-a). Additionally, if the UE receives DCI 715-b indicating the same HARQ identifier 720 (e.g., with the same or a different NDI 725), the UE can stop and reset the timer. Therefore, at time 705-b, the UE can stop and reset the timer based on DCI 715-b indicating the same HARQ identifier 720 as DCI 715-a. In example 700, the UE receives a retransmission of DCI 715-b for scheduled transport block 730-b before the timer expires. Therefore, the UE does not detect an unsuccessful termination of the HARQ procedure associated with transport block 730 between times 705-a and 705-b.

[0137] In Example 700, the UE cannot successfully decode transport block 730 using the combination of the initial transmission of transport block 730-a and the retransmission of transport block 730-b. Therefore, at time 705-c, the UE transmits another HARQ NACK 735-b associated with transport block 730 and starts (e.g., initiates) a timer.

[0138] At time 705-d, the timer may expire. In response to the timer expiring before the UE detects any retransmission of control information 715 associated with transport block 730, the UE can identify the termination of the unsuccessful HARQ procedure associated with transport block 730 and HARQ identifier 720. Therefore, the UE can send an unsuccessful HARQ procedure termination indication 745 to the network node.

[0139] In some cases, configuring the network node to identify unsuccessful HARQ procedure termination in response to timer expiration can reduce the latency associated with the UE detecting and reporting unsuccessful HARQ procedure termination. For example, the network node may not send another DCI 715-c scheduled for another transport block associated with the same HARQ identifier 720 and NDI 725-b (which may be different from NDI 725-a) for an extended period. In Example 700, if the UE is unable to detect or report the unsuccessful termination of the HARQ procedure associated with transport block 730 until it receives DCI 715-c, additional latency may be introduced as the network node initiates an ARQ procedure to retransmit one or more RLC SDUs or RLC SDU segments associated with transport block 730. In another example, the UE may fail to receive or decode DCI 715-c scheduled for another transport block with the same HARQ identifier 720 as transport block 730. Here, the UE may not be able to identify the unsuccessful termination of the HARQ procedure associated with transport block 730 without a timer.

[0140] Figure 8A and Figure 8B This is an illustration of example 800 of signaling exchanged between a transmitting device and a receiving device (e.g., between a network node and a UE) according to this disclosure.

[0141] Figure 8A and Figure 8B An example is illustrated where a UE fails to receive or decode control information (e.g., DCI 815-b and DCI 815-e) for a new transport block 840 associated with the same HARQ identifier 820 as the previously sent transport block 830. In this example, the UE can essentially report a HARQ NACK 835 to the network node associated with transport block 840. For example, the UE can send a HARQ NACK 835, or the UE can choose not to send any HARQ feedback associated with transport block 840. In either case, the UE can indicate to the network node that it was unable to successfully decode the new transport block 840. However, in the case of a NACK-to-ACK error, the network node can subsequently schedule another transport block 850 associated with the same HARQ identifier 820 (e.g., when the UE has not yet successfully decoded the new transport block 840).

[0142] When the NDI 825 associated with HARQ identifier 820 includes a single bit, the NDI 825 associated with the first transport block 850 (e.g., NDI 825-a and 825-d) can have the same value as the NDI 825 associated with the third transport block 830 (e.g., NDI 825-c and 825-f). If the NDI 825 associated with the first transport block 830 and the third transport block 850 have the same value and the UE fails to detect the DCI 815 scheduling the second transport block 840, the UE may not detect or report the unsuccessful termination of the HARQ procedure associated with the second transport block 840.

[0143] To enable the UE to identify the unsuccessful termination of the HARQ process even if the UE does not detect the DCI 815 of the scheduled transport block 840, the NDI 825 can be configured with more than one bit, and the UE can be configured to evaluate one or more additional conditions associated with the DCI 815 of the scheduled transport block, or both.

[0144] In Example 800-a, DCI 815-a can schedule the transmission of transport block 830-a and can indicate that transport block 830-a is associated with HARQ identifier 820 and NDI 825-a. The UE can successfully receive and decode transport block 830-a and can send a HARQ ACK 805 indicating successful decoding of transport block 830-a. The network node can then send DCI 815-b to schedule the transmission of another transport block 840-a and can indicate that transport block 840-a is associated with the same HARQ identifier 820 as the first transport block 830-a and a different NDI 825-b. However, the UE may fail to successfully detect, receive, or decode DCI 815-b. Therefore, the UE can indicate that it failed to successfully decode transport block 840-a (e.g., by sending HARQ NACK 835-a or by avoiding sending any HARQ signaling associated with transport block 840-a). However, in Example 800-a, a NACK-to-ACK error may exist associated with transport block 840-a, and the network node may subsequently schedule another transport block 850-a associated with the same HARQ identifier 820 (e.g., when the UE has not yet successfully decoded the new transport block 840-a). Additionally, the network node may fail to terminate the HARQ process associated with transport block 840-a based on the NACK-to-ACK error.

[0145] A network node can send DCI 815-c to schedule the transmission of a third transport block 850-a that is associated with the same HARQ identifier 820 as the first transport block 830-a and the second transport block 840-a, and is associated with NDI 825-c.

[0146] In some cases, the NDI 825 may include more than one bit (e.g., may include...). K Ones place, of which K >1). Here, the UE can identify a NACK to ACK error associated with transport block 840-a in response to a difference greater than one (e.g., two or greater) between the value of NDI 825-c and NDI 825-a. Specifically, a difference greater than one between NDI 825-a and NDI 825-c can indicate to the UE that when the UE receives another DCI 815-c scheduled for a third transport block 840-a associated with the same HARQ identifier 820, the UE has not yet successfully decoded at least one transport block 850 associated with the same HARQ identifier 820. Accordingly, the UE can send an unsuccessful HARQ procedure termination indication 845-a indicating the unsuccessful termination of the HARQ procedure associated with transport block 840-a.

[0147] In some other cases, NDI 825 may have a one-bit width. Here, NDI 825-a and NDI 825-c can be the same value (e.g., 1). Additionally, although NDI 825-b can be a different value (e.g., 0), a UE that fails to receive DCI 815-b may prevent the UE from identifying that NDI 825 associated with HARQ identifier 820 has been switched. Therefore, the UE may not be able to identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a based on the value of NDI 825. Here, the UE may identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a based on one or more other parameters associated with transport blocks 830 and 850.

[0148] For example, if the MCS indicated by DCI 815-c does not include a reserved value for the decoding rate used for the third transport block 850-a, the UE can identify the unsuccessful termination of the HARQ process associated with transport block 840-a. That is, if DCI 815-c is scheduling a retransmission of transport block 830-a, DCI 815-c can indicate the MCS via a reserved value for the decoding rate used for retransmission. Therefore, the UE can identify that DCI 815-c has not scheduled a retransmission of the first transport block 830-a based on the MCS indicated in DCI 815-c, and can also identify the unsuccessful termination of the HARQ process associated with transport block 840-a.

[0149] In another example, if the transport block size indicated by DCI 815-c is different from the transport block size associated with the first transport block 830-a, the UE can identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a. That is, while DCI 815-c is scheduling a retransmission of transport block 830-a, DCI 815-c can indicate the same transport block size as transport block 830-a. Therefore, the UE can identify that DCI 815-c has not scheduled a retransmission of the first transport block 830-a based on the difference between the transport block size indicated by DCI 815-c and the transport block size associated with transport block 830-a, and can also identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a.

[0150] In another example, if the redundancy version indicated by DCI 815-c is 0, the UE can identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a. That is, while DCI 815-c is scheduling a retransmission of transport block 830-a, DCI 815-c can indicate a redundancy version value other than 0 (e.g., this could indicate that transport block 850-a was not initially transmitted). Therefore, the UE can identify that DCI 815-c is not scheduling a retransmission of the first transport block 850-a based on a redundancy version of 0 indicated by DCI 815-c (which indicates that transport block 830-a is initially transmitted), and can also identify the unsuccessful termination of the HARQ procedure associated with transport block 840-a.

[0151] Based on the unsuccessful termination of the HARQ procedure associated with transport block 840-a, the UE can send an unsuccessful HARQ procedure termination indication 845-a. Additionally, the UE can avoid soft combining transport blocks 830-a and 850-a based on the indication that transport block 830-a is not a retransmission of transport block 850-a.

[0152] In Example 800-b, the UE may additionally fail to decode the first transport block 830-b and may send a HARQNACK 835-b to indicate to the network node that the UE failed to decode the first transport block 830-b. Additionally, in Example 800-b, there may be an ACK-to-NACK error associated with the HARQ NACK 835-b. Therefore, the network node may then fail to terminate the HARQ procedure associated with transport block 830-b and subsequently send a DCI 815-e to schedule the transmission of another transport block 840-b. The DCI 815-a may indicate that transport block 840-b is associated with the same HARQ identifier 820 as the first transport block 830-b and a different NDI 825-e. However, the UE may fail to detect, receive, or decode the DCI 815-e. Therefore, the UE can indicate that the UE failed to successfully decode transport block 840-b (e.g., by sending HARQ NACK 835-c or by avoiding sending any HARQ signaling associated with transport block 840-b).

[0153] However, in Example 800-b, a NACK-to-ACK error may exist associated with transport block 840-b, and the network node may subsequently schedule another transport block 850-b associated with the same HARQ identifier 820 (e.g., when the UE has not yet successfully decoded the new transport block 840-b or the first transport block 830-b). Additionally, the network node may fail to successfully terminate the HARQ process associated with transport block 840-b based on the NACK-to-ACK error.

[0154] A network node can send DCI 815-c to schedule the transmission of a third transport block 850-a that is associated with the same HARQ identifier 820 as the first transport block 830-a and the second transport block 840-a, and is associated with NDI 825-c.

[0155] In some cases, NDI 825 may include more than one bit. Here, the UE can base its decision on the difference between the values ​​of NDI 825-d and NDI825-f. k This is used to identify NACK-ACK errors associated with transport blocks 830-b and 840-b. For example, the value of NDI825-d can be 1, the value of NDI 825-e can be 2, and the value of NDI 825-f can be 3. In example 800-b, the UE can detect a difference of 2 in NDI 825 (e.g., k=2). In some cases, a difference greater than one between NDI 825-d and NDI 825-f can indicate to the UE that when the UE receives another DCI 815-c that schedules a third transport block 850-a associated with the same HARQ identifier 820, the UE has not yet successfully decoded at least one transport block 840 associated with the same HARQ identifier 820. Accordingly, the UE can send an unsuccessful HARQ procedure termination indication 845-b indicating the unsuccessful termination of the HARQ procedure associated with transport block 840-b.

[0156] In some cases, a UE can report more than one unsuccessful HARQ procedure termination via the Unsuccessful HARQ Procedure Termination Indication 845-b. For example, if the UE has already decoded transport block 830-b associated with a previously detected NDI 825-d (e.g., and sent a HARQ ACK instead of a HARQ NACK 835-b), the UE can report... k -1 failed HARQ procedure terminates, of which k This corresponds to the difference in the detected NDI 825 value. Additionally, if the UE has not yet decoded the transport block 830-b associated with the previously detected NDI 825-d (e.g., and HARQ NACK 835-b was sent), the UE may report... k The unsuccessful HARQ procedure is terminated here. k The termination of the second unsuccessful HARQ procedure can correspond to k-1 A lost NDI 825 and an earlier NDI 825-d that was not successfully decoded in transport block 830-b. In example 800-b, the UE can report two unsuccessful HARQ procedure terminations.

[0157] Figure 9A and Figure 9B This is a diagram illustrating example 900 of an unsuccessful HARQ process termination instruction according to this disclosure. In some cases, an unsuccessful HARQ process termination instruction may be referred to as a report of one or more unsuccessful HARQ termination events.

[0158] In Example 900-a, the reporting of the one or more unsuccessful HARQ termination events may include one or more blocks 915, wherein for each block 915, HARQ identifiers 920 and NDI 925 associated with the unsuccessfully terminated HARQ process are included. For example, block 915-a may include HARQ identifiers 920-a and NDI 925-a associated with a first unsuccessfully terminated HARQ process, block 915-b may include HARQ identifiers 920-b and NDI 925-b associated with a second unsuccessfully terminated HARQ process, and block 915-c may include HARQ identifiers 920-c and NDI 925-c associated with a third unsuccessfully terminated HARQ process.

[0159] When the UE is configured with multiple component carriers, the UE may also include a component carrier index (e.g., CC index 905) for each block 915. For example, block 915-a may include a first CC index 905-a associated with a first unsuccessfully terminated HARQ procedure, block 915-b may include a second CC index 905-b associated with a second unsuccessfully terminated HARQ procedure, and block 915-c may include a third CC index 905-c associated with a third unsuccessfully terminated HARQ procedure.

[0160] The report of one or more unsuccessful HARQ termination events may additionally include a timestamp 910 corresponding to the unsuccessful HARQ procedure associated with each block 915. For example, in the case of sending the report via MAC-CE, the report may include timestamp 910. Timestamp 910 may correspond to a slot number, subframe number, and / or system frame number.

[0161] In some cases, timestamp 910 may correspond to the time of sending or receiving control information for a transport block associated with an unsuccessfully terminated HARQ procedure, the time of sending or receiving a transport block associated with an unsuccessfully terminated HARQ procedure, the time of the UE sending a HARQ NACK associated with an unsuccessfully terminated HARQ procedure, the time of sending or receiving control information for another transport block associated with the same HARQ identifier 920 (e.g., received before the UE has successfully decoded the transport block associated with the unsuccessfully terminated HARQ procedure) (which may correspond to the time when the UE detects the unsuccessful termination of the HARQ procedure), and / or the time of the first indication (e.g., to a network node) of the unsuccessfully terminated HARQ procedure.

[0162] In Example 900-b, the report may include a bitmap 930 of HARQ identifiers, where each bit in the bitmap 930 indicates the state associated with the corresponding HARQ identifier. For example, if a bit in the bitmap 930 has a first value (e.g., 0), the bit may indicate that the UE has identified that the HARQ procedure associated with the HARQ identifier has been unsuccessfully terminated. Additionally, if a bit in the bitmap 930 has a second value (e.g., 1), the bit may indicate that the UE has not identified that the HARQ procedure associated with the HARQ identifier has been unsuccessfully terminated. In Example 900-b, the bitmap 930 may indicate that the UE has identified five unsuccessfully terminated HARQ procedures, and the mapping associated with the bitmap 930 may indicate five HARQ identifiers associated with each of the five unsuccessfully terminated HARQ procedures.

[0163] For each HARQ identifier indicated via bitmap 930 as being associated with a HARQ process that failed to terminate, the report may additionally include NDI 925 for the HARQ identifier associated with the HARQ process that failed to terminate. In example 900-b, the report may include a first NDI 925-d (e.g., corresponding to the first bit with a value of 0 in bitmap 930) associated with a first HARQ process identified as having failed to terminate successfully, a second NDI 925-e (e.g., corresponding to the second bit with a value of 0 in bitmap 930) associated with a second HARQ process identified as having failed to terminate successfully, a third NDI 925-f (e.g., corresponding to the third bit with a value of 0 in bitmap 930) associated with a third HARQ process identified as having failed to terminate successfully, a fourth NDI 925-g (e.g., corresponding to the fourth bit with a value of 0 in bitmap 930) associated with a fourth HARQ process identified as having failed to terminate successfully, and a fifth NDI 925-h (e.g., corresponding to the fifth bit with a value of 0 in bitmap 930) associated with a fifth HARQ process identified as having failed to terminate successfully.

[0164] Additionally or alternatively, the report may include a timestamp 910 associated with each of the unsuccessfully terminated HARQ processes identified in bitmap 930 (e.g., as described with reference to example 900-a).

[0165] When the UE is configured with multiple component carriers, the report may include a bitmap 930 associated with each component carrier. For example, the report may include a first bitmap 930 (and corresponding NDI 925 and timestamp 910) associated with a first component carrier configured for the UE, and a second different bitmap 930 (and corresponding NDI 925 and timestamp 910) associated with a second component carrier configured for the UE.

[0166] In some cases, the report illustrated in Example 900-b may be associated with lower signaling overhead, in cases where the UE identifies a number of HARQ procedures that failed to terminate successfully, compared to the report illustrated in Example 900-a.

[0167] In some other examples 900 of the report, the UE may use an enhanced Type 3 HARQ-ACK codebook to send signaling indicating one or more unsuccessful terminations of the HARQ process. For example, the HARQ-ACK codebook may include values ​​corresponding to HARQ ACK or HARQ NACK for multiple NDIs 925 associated with each HARQ identifier. For example, where a HARQ identifier is associated with two NDIs, the HARQ-ACK codebook may include values ​​indicating HARQ ACK or NACK for the two NDIs associated with that HARQ identifier.

[0168] Figure 10 This is a diagram illustrating example 1000 of signaling exchanged between network node 110 and UE 120 according to this disclosure. In some cases, network node 110 and UE 120 may implement aspects of other examples described herein.

[0169] At 1005, UE 120 may optionally send, and network node 110 may receive, a signaling instructing UE to report to network node 110 the ability to successfully terminate the HARQ procedure.

[0170] At 1010, network node 110 may optionally send and UE 120 may receive signaling indicating the configuration for UE 120 to report to network node 110 the unsuccessful termination of the HARQ procedure.

[0171] At 1015, network node 110 may send and UE 120 may optionally attempt to receive (e.g., by monitoring the resource set associated with the transmission of the second transport block) the second transport block associated with the HARQ identifier (e.g., via PDSCH).

[0172] At 1020, UE 120 may optionally attempt to decode the second transport block. At 1025, UE 120 may optionally send a HARQ NACK associated with the second transport block. For example, if UE 120 fails to decode the second transport block 1020 (e.g., and UE 120 knows that the second transport block was sent to UE 120 by network node 110), then UE 120 may send a HARQ NACK to network node 110.

[0173] At 1030, network node 110 can send and UE 120 can receive control information that schedules the first transport block and indicates that the first transport block has the same HARQ identifier as the second transport block.

[0174] At 1035, UE 120 may identify the unsuccessful termination of the HARQ procedure associated with the second transport block. For example, UE 120 may identify the unsuccessful termination of the HARQ procedure in response to receiving control information scheduling another transport block (e.g., the first transport block) while UE 120 has not yet successfully decoded a previously received transport block (e.g., the second transport block) associated with the same HARQ identifier. Additionally or alternatively, UE 120 may identify the unsuccessful termination of the HARQ procedure in response to an NDI associated with the first transport block (e.g., as indicated by the control information scheduling the first transport block) and the HARQ identifier being the same as the HARQ identifier associated with the second transport block.

[0175] At 1040, UE 120 can send, and network node 110 can receive, signaling indicating unsuccessful termination of the HARQ process associated with the second transport block. In some cases, the signaling indicating unsuccessful termination of the HARQ process associated with the second transport block can be sent via a report illustrated in Example 900, within an RLC status report, and / or via an enhanced type 3 HARQ-ACK codebook.

[0176] In some cases, network node 110 may initiate an ARQ procedure associated with retransmitting one or more RLC SDU or RLCSDU segments associated with the second transport block in response to receiving a signaling indicating unsuccessful termination of the HARQ procedure associated with the second transport block.

[0177] Figure 11 This is a flowchart illustrating an example procedure 1100 for supporting wireless communication, performed, for example, at a UE or a device of a UE, according to this disclosure. Example procedure 1100 is an example of a device or UE (e.g., UE 120) performing operations associated with identifying an unsuccessful termination of a HARQ procedure.

[0178] like Figure 11 As shown, in some aspects, process 1100 may include receiving control information from a network node to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block (box 1110). For example, the UE (such as by using...) Figure 13 The communication manager 140 or receiving component 1302 depicted above can receive control information from the network node to schedule the first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block, as described above.

[0179] like Figure 11 Further shown, in some aspects, process 1100 may include identifying the unsuccessful termination of the HARQ process associated with the second transport block in response to the UE's failure to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both (box 1120). For example, the UE (such as by using...) Figure 13 The communication manager 140 or identification component 1308 depicted above may identify the unsuccessful termination of the HARQ process associated with the second transport block in response to the UE's failure to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both.

[0180] like Figure 11 Further shown, in some aspects, process 1100 may include sending signaling to the network node indicating unsuccessful termination of the HARQ process associated with the second transport block (box 1130). For example, the UE (such as by using...) Figure 13 The communication manager 140 or transmitting component 1304 depicted in the diagram can send a signaling message to the network node indicating the unsuccessful termination of the HARQ process associated with the second transport block, as described above.

[0181] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0182] In a first additional aspect, the control information scheduling the first transport block indicates a change in the value of the NDI associated with the same HARQ identifier.

[0183] In a second additional aspect, either alone or in combination with the first aspect, sending a signaling indicating that the HARQ process was not successfully terminated is in response to the number of retransmissions associated with the second transport block being less than a threshold.

[0184] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, process 1100 includes receiving a second signaling from the network node indicating the threshold.

[0185] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, process 1100 includes sending a NACK associated with the second transport block to the network node before receiving the control information scheduling the first transport block.

[0186] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, process 1100 includes starting a timer in response to sending a HARQ NACK associated with the second transport block, wherein sending signaling indicating unsuccessful termination of the HARQ process is in response to the expiration of the timer.

[0187] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the sending of signaling indicating the unsuccessful termination of the HARQ process occurs before the control information is received from the network node.

[0188] In a seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, process 1100 includes resetting the timer in response to receiving second control information for scheduling the second transport block, wherein the timer is associated with the same HARQ identifier, and wherein resetting the timer also responds to receiving any control information for scheduling the transport block associated with the same HARQ identifier.

[0189] In the eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, process 1100 includes: receiving from the network node a third transport block having the same HARQ identifier as the first transport block; and sending an ACK or NACK associated with the third transport block to the network node before receiving the control information scheduling the first transport block, wherein an unsuccessful termination indicating the termination of the HARQ process also responds to a first NDI associated with the first transport block and a second NDI associated with the third transport block.

[0190] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, it is identified that the unsuccessful termination of the HARQ process is in response to the first NDI being different from the second NDI.

[0191] In the tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the first NDI and the second NDI each comprise two or more bits, and the difference between a first value associated with the first NDI and a second value associated with the second NDI is two or greater.

[0192] In the eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, process 1100 includes: in response to the UE failing to successfully decode the third transport block and the difference being two or greater, identifying a second unsuccessful termination of the second HARQ process associated with the third transport block; and sending a HARQ NACK associated with the third transport block to the network node, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates a second unsuccessful termination of the second HARQ process.

[0193] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, the HARQ process and the second HARQ process are associated with the same HARQ identifier.

[0194] In the thirteenth additional aspect, either alone or in combination with one or more of the first to twelfth aspects, identifying the unsuccessful termination of the HARQ process also responds to sending a HARQ ACK associated with the third transport block and the first NDI and the second NDI are the same.

[0195] In the fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, identifying the unsuccessful termination of the HARQ process also responds to: the first transport block size indicated by the control information being different from the second transport block size associated with the third transport block; the MCS indicated by the control information failing to include a reserved value for the decoding rate of the first transport block; the control information scheduling the initial transmission of the first transport block; or the control information indicating that the value of the redundant version of the first transport block is 0.

[0196] In the fifteenth additional aspect, either alone or in combination with one or more of the first to fourteenth aspects, the signaling indicating the unsuccessful termination of the HARQ process includes an identifier associated with the HARQ process and an NDI associated with the HARQ process.

[0197] In the sixteenth additional aspect, the signaling indicating the unsuccessful termination of the HARQ process, alone or in combination with one or more of the first to fifteenth aspects, also includes an index associated with the component carrier of the second transport block, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0198] In the seventeenth additional aspect, either alone or in combination with one or more of the first to sixteenth aspects, signaling indicating unsuccessful termination of the HARQ process includes a bitmap associated with a plurality of HARQ process identifiers, and the value of a bit in the bitmap associated with the HARQ process indicates the unsuccessful termination of the HARQ process.

[0199] In the eighteenth additional aspect, the signaling indicating the unsuccessful termination of the HARQ process, alone or in combination with one or more of the first to seventeenth aspects, also includes an NDI associated with the HARQ process, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0200] In the nineteenth additional aspect, either alone or in combination with one or more of the first to eighteenth aspects, the signaling indicating the unsuccessful termination of the HARQ process includes multiple bitmaps, each of which is associated with a different component carrier.

[0201] In the twentieth additional aspect, alone or in combination with one or more of the first to nineteenth aspects, the same HARQ identifier is associated with the first NDI and the second NDI, and the signaling indicating the unsuccessful termination of the HARQ process includes an acknowledgment (ACK) or a NACK for each of the first NDI and the second NDI.

[0202] In the twenty-first additional aspect, individually or in combination with one or more of the first to twentieth aspects, sending signaling indicating the unsuccessful termination of the HARQ process may include sending the signaling via uplink control information, MAC-CE, or radio link control status report.

[0203] In the twenty-second additional aspect, either alone or in combination with one or more of the first to twenty-first aspects, process 1100 includes receiving from the network node a signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process to the network node, wherein sending the signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process is in response to receiving the signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process.

[0204] In the twenty-third additional aspect, alone or in combination with one or more of the first to twenty-second aspects, process 1100 includes sending to the network node the capability of the UE to report to the network node the unsuccessful termination of the HARQ process, wherein receiving signaling instructing the UE to report the unsuccessful termination is in response to sending the capability of the UE.

[0205] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11 Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0206] Figure 12 This is a flowchart illustrating an example process 1200 performed, for example, at a network node or device supporting wireless communication, according to the present disclosure. Example process 1200 is an example of a device or network node (e.g., network node 110) performing operations associated with identifying an unsuccessful termination of a HARQ process.

[0207] like Figure 12As shown, in some aspects, process 1200 may include sending control information (block 1210) to the UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block. For example, the network node (such as by using...) Figure 14 The communication manager 150 or the transmitting component 1404 depicted above can send control information to the UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block, as described above.

[0208] like Figure 12 As further shown, in some aspects, process 1200 may include receiving from the UE signaling an indication of unsuccessful termination of a HARQ process associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both (block 1220). For example, the network node (such as by using the communication manager 150 or receiving component 1402 depicted in FIG. 1402) may receive from the UE signaling an indication of unsuccessful termination of a HARQ process associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both, as described above.

[0209] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0210] In a first additional aspect, the control information scheduling the first transport block indicates a change in the value of the NDI associated with the same HARQ identifier.

[0211] In a second additional aspect, either alone or in combination with the first aspect, receiving signaling indicating unsuccessful termination of the HARQ process also responds to the number of retransmissions associated with the second transport block being less than a threshold.

[0212] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, process 1200 includes sending a second signaling to the UE indicating the threshold.

[0213] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, process 1200 includes receiving a NACK associated with the second transport block from the UE before sending the control information scheduling the first transport block.

[0214] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, receiving a signal indicating unsuccessful termination of the HARQ process also responds to the expiration of a timer associated with the HARQ identifier.

[0215] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, receiving signaling indicating the unsuccessful termination of the HARQ procedure occurs before the control information is sent to the UE.

[0216] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, process 1200 includes: sending a third transport block to the UE having the same HARQ identifier as the first transport block; and receiving an ACK or NACK associated with the third transport block from the UE before sending the control information scheduling the first transport block, wherein receiving signaling indicating unsuccessful termination of the HARQ process also responds to a first NDI associated with the first transport block and a second NDI associated with the third transport block.

[0217] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, receiving a signal indicating the unsuccessful termination of the HARQ process also responds to the first NDI being different from the second NDI.

[0218] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the first NDI and the second NDI each comprise two or more bits, and the difference between a first value associated with the first NDI and a second value associated with the second NDI is two or greater.

[0219] In the tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, process 1200 includes receiving from the UE a HARQ NACK associated with the third transport block, wherein signaling indicating unsuccessful termination of the HARQ process also indicates a second unsuccessful termination of a second HARQ process associated with the third transport block, and wherein the signaling responds to the UE failing to successfully decode the third transport block and the difference being two or greater to indicate a second unsuccessful termination of the second HARQ process.

[0220] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, the HARQ process and the second HARQ process are associated with the same HARQ identifier.

[0221] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, receiving a signaling indicating the unsuccessful termination of the HARQ process also responds to a HARQ ACK associated with the third transport block, and the first NDI and the second NDI are the same.

[0222] In the thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, receiving a signaling indicating the unsuccessful termination of the HARQ process also responds to: the first transport block size indicated by the control information being different from the second transport block size associated with the third transport block; the MCS indicated by the control information failing to include a reserved value for the decoding rate of the first transport block; the control information scheduling the initial transmission of the first transport block; or the control information indicating that the value of the redundant version of the first transport block is 0.

[0223] In the fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, the signaling indicating the unsuccessful termination of the HARQ process includes an identifier associated with the HARQ process and an NDI associated with the HARQ process.

[0224] In the fifteenth additional aspect, either alone or in combination with one or more of the first to fourteenth aspects, the signaling indicating the unsuccessful termination of the HARQ process also includes an index associated with the component carrier of the second transport block, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0225] In the sixteenth additional aspect, either alone or in combination with one or more of the first to fifteenth aspects, signaling indicating unsuccessful termination of the HARQ process includes a bitmap associated with a plurality of HARQ process identifiers, and the value of a bit in the bitmap associated with the HARQ process indicates the unsuccessful termination of the HARQ process.

[0226] In the seventeenth additional aspect, either alone or in combination with one or more of the first to sixteenth aspects, the signaling indicating the unsuccessful termination of the HARQ process also includes an NDI associated with the HARQ process, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0227] In the eighteenth additional aspect, either alone or in combination with one or more of the first to seventeenth aspects, the signaling indicating the unsuccessful termination of the HARQ process includes multiple bitmaps, each of which is associated with a different component carrier.

[0228] In the nineteenth additional aspect, alone or in combination with one or more of the first to eighteenth aspects, the same HARQ identifier is associated with the first NDI and the second NDI, and the signaling indicating the unsuccessful termination of the HARQ process includes an ACK or NACK for each of the first NDI and the second NDI.

[0229] In the twentieth additional aspect, individually or in combination with one or more of the first to nineteenth aspects, receiving signaling indicating the unsuccessful termination of the HARQ process includes receiving the signaling via uplink control information, MAC-CE, or radio link control status report.

[0230] In the twenty-first additional aspect, alone or in combination with one or more of the first to twentieth aspects, process 1200 includes sending a signaling to the UE instructing the UE to report the unsuccessful termination of the HARQ process to the network node, wherein receiving the signaling instructing the UE to report the unsuccessful termination of the HARQ process is in response to sending the signaling instructing the UE to report the unsuccessful termination of the HARQ process.

[0231] In the twenty-second additional aspect, alone or in combination with one or more of the first to twenty-first aspects, process 1200 includes receiving from the UE the ability of the UE to report to the network node that the HARQ process was not successfully terminated, wherein sending the signaling instructing the UE to report the unsuccessful termination is in response to receiving the UE's ability.

[0232] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0233] Figure 13 This is a diagram of an example device 1300 for wireless communication that failed to terminate the HARQ process according to this disclosure. Device 1300 may be a UE, or a UE may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and a communication manager 140 that can communicate with each other (e.g., via one or more buses). As shown, device 1300 can use the receiving component 1302 and the transmitting component 1304 to communicate with another device 1306 (such as a UE, a network node, or another wireless communication device).

[0234] In some respects, device 1300 may be configured and / or capable of operating to perform the functions described herein. Figures 4 to 10One or more operations described herein. Additionally or alternatively, device 1300 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 11 The process 1100. In some aspects, the apparatus 1300 may include the above-described combination. Figure 2 One or more components of the UE as described.

[0235] Receiver 1302 may receive communications from device 1306, such as reference signals, control information, and / or data communications. Receiver 1302 may provide the received communications to one or more other components of device 1300, such as communication manager 140. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1302 may include the combinations described above. Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, and / or one or more memories.

[0236] Transmitting component 1304 can transmit communications (such as reference signals, control information, and / or data communications) to device 1306. In some aspects, communication manager 140 can generate communications and transmit the generated communications to transmitting component 1304 for transmission to device 1306. In some aspects, transmitting component 1304 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and transmit the processed signals to device 1306. In some aspects, transmitting component 1304 may include the above-described combinations. Figure 2 The described UE includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0237] Communication manager 140 may receive, or may cause receiving component 1302 to receive from, control information that schedules a first transport block and indicates that the first transport block has the same HARQ identifier as the second transport block. Communication manager 140 may identify the unsuccessful termination of the HARQ procedure associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. Communication manager 140 may send, or may cause sending component 1304 to send to the network node, signaling the unsuccessful termination of the HARQ procedure associated with the second transport block. In some aspects, communication manager 140 may perform one or more operations as described elsewhere herein by one or more components of communication manager 140.

[0238] Communication manager 140 may include the above-mentioned components. Figure 2 The described UE includes one or more controllers / processors and one or more memories. In some aspects, the communication manager 140 includes a set of components such as identification component 1308. Alternatively, this set of components may be separate from and different from the communication manager 140. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described UE may include one or more controllers / processors, one or more memories, or may be implemented within one or more controllers / processors or one or more memories of the UE. Additionally or alternatively, one or more components in this set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0239] The receiving component 1302 can receive control information from the network node that schedules a first transport block and indicates that the first transport block has the same HARQ identifier as the second transport block. The identifying component 1308 can identify the unsuccessful termination of the HARQ process associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block with the same HARQ identifier as the second transport block, or both. The transmitting component 1304 can send signaling to the network node indicating the unsuccessful termination of the HARQ process associated with the second transport block.

[0240] The receiving component 1302 can receive a second signaling indicating a threshold from the network node.

[0241] The transmitting component 1304 may send a NACK associated with the second transport block to the network node before receiving the control information that schedules the first transport block.

[0242] The timing component 1310 can start a timer in response to sending a HARQ NACK associated with the second transport block, wherein sending a signal indicating that the HARQ process has not been successfully terminated is in response to the expiration of the timer.

[0243] The timing component 1310 may reset the timer in response to receiving second control information scheduling the second transport block, wherein the timer is associated with the same HARQ identifier, and wherein resetting the timer also responds to receiving any control information scheduling the transport block associated with the same HARQ identifier.

[0244] The receiving component 1302 can receive a third transport block with the same HARQ identifier as the first transport block from the network node.

[0245] The transmitting component 1304 may send an ACK or NACK associated with the third transport block to the network node before receiving the control information scheduling the first transport block, wherein an unsuccessful termination indicating the termination of the HARQ process also responds to a first NDI associated with the first transport block and a second NDI associated with the third transport block.

[0246] The identification component 1308 may identify a second unsuccessful termination of the second HARQ process associated with the third transport block in response to the UE failing to successfully decode the third transport block and the difference being two or greater.

[0247] The transmitting component 1304 may send a HARQ NACK associated with the third transport block to the network node, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates a second unsuccessful termination of the second HARQ process.

[0248] The receiving component 1302 can receive from the network node a signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process to the network node, wherein sending the signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process is in response to receiving the signaling instruction instructing the UE to report the unsuccessful termination of the HARQ process.

[0249] The transmitting component 1304 can transmit to the network node the UE's ability to report the unsuccessful termination of the HARQ procedure, wherein receiving a signaling instructing the UE to report the unsuccessful termination is in response to transmitting the UE's ability.

[0250] Figure 13 The number and arrangement of components shown are provided as an example. In reality, with...Figure 13 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The collection of (one or more) components shown is executable and described as being composed of Figure 13 Another set of components shown performs one or more functions.

[0251] Figure 14 This is a diagram of an example device 1400 for wireless communication that failed to terminate the HARQ process according to this disclosure. Device 1400 may be a network node, or a network node may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and a communication manager 150 that can communicate with each other (e.g., via one or more buses). As shown, device 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another device 1406 (such as a UE, a network node, or another wireless communication device).

[0252] In some respects, device 1400 may be configured and / or capable of operating to perform the functions described herein. Figures 4 to 10 One or more operations described herein. Additionally or alternatively, the device 1400 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 12 The process 1200. In some aspects, the apparatus 1400 may include the above-described combination. Figure 2 One or more components of the network node described.

[0253] Receiver 1402 may receive communications, such as reference signals, control information, and / or data communications, from device 1406. Receiver 1402 may provide the received communications to one or more other components of device 1400, such as communication manager 150. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1402 may include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, and / or one or more memories.

[0254] Transmitting component 1404 can transmit communications (such as reference signals, control information, and / or data communications) to device 1406. In some aspects, communication manager 150 can generate communications and can send the generated communications to transmitting component 1404 for transmission to device 1406. In some aspects, transmitting component 1404 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to device 1406. In some aspects, transmitting component 1404 may include the above-described combinations. Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0255] Communication manager 150 may send, or may cause transmitting component 1404 to send to the UE, control information scheduling a first transport block and indicating that the first transport block has the same HARQ identifier as the second transport block. Communication manager 150 may receive, or may cause receiving component 1402 to receive from the UE, signaling indicating unsuccessful termination of a HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both. In some aspects, communication manager 150 may perform one or more operations as otherwise described herein as being performed by one or more components of communication manager 150.

[0256] Communication manager 150 may include the above-mentioned combination Figure 2 The described network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 150 may include the elements described above. Figure 2 The described network node may include, or may contain, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components of this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of that component.

[0257] The transmitting component 1404 can send control information to the UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as the second transport block. The receiving component 1402 can receive from the UE a signaling message indicating unsuccessful termination of a HARQ procedure associated with the second transport block, wherein receiving the signaling message is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

[0258] The transmitting component 1404 can send a second signaling indicating a threshold to the UE.

[0259] The receiving component 1402 can receive the NACK associated with the second transport block from the UE before sending the control information scheduling the first transport block.

[0260] The transmitting component 1404 can transmit a third transport block to the UE having the same HARQ identifier as the first transport block.

[0261] The receiving component 1402 may receive an ACK or NACK associated with the third transport block from the UE before sending the control information scheduling the first transport block, wherein receiving the signaling indicating the unsuccessful termination of the HARQ process also responds to the first NDI associated with the first transport block and the second NDI associated with the third transport block.

[0262] The receiving component 1402 can receive a HARQ NACK associated with the third transport block from the UE, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates a second unsuccessful termination of the second HARQ process associated with the third transport block, and wherein the signaling responds to the UE failing to successfully decode the third transport block and the difference being two or greater to indicate a second unsuccessful termination of the second HARQ process.

[0263] The transmitting component 1404 can send a signaling message to the UE instructing the UE to report the unsuccessful termination of the HARQ process to the network node, wherein receiving the signaling message instructing the UE to report the unsuccessful termination of the HARQ process is in response to sending the signaling message instructing the UE to report the unsuccessful termination of the HARQ process.

[0264] The receiving component 1402 can receive from the UE the ability of the UE to report the unsuccessful termination of the HARQ procedure to the network node, wherein sending a signaling instructing the UE to report the unsuccessful termination is in response to receiving the UE's ability.

[0265] Figure 14 The number and arrangement of components shown are provided as an example. In reality, with... Figure 14Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The collection of (one or more) components shown is executable and described as being composed of Figure 14 Another set of components shown performs one or more functions.

[0266] The following provides an overview of some aspects of this disclosure:

[0267] Aspect 1: A method for wireless communication by a UE, the method comprising: receiving from a network node control information that schedules a first transport block and indicates that the first transport block has the same HARQ identifier as a second transport block; identifying unsuccessful termination of a HARQ process associated with the second transport block in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both; and sending to the network node signaling the unsuccessful termination of the HARQ process associated with the second transport block.

[0268] Aspect 2: According to the method of aspect 1, wherein the control information scheduling the first transport block indicates a change in the value of the NDI associated with the same HARQ identifier.

[0269] Aspect 3: The method according to any one of Aspects 1 to 2, wherein sending the signaling indicating the unsuccessful termination of the HARQ process is in response to the number of retransmissions associated with the second transport block being less than a threshold.

[0270] Aspect 4: According to the method of aspect 3, the method further includes: receiving a second signaling indicating the threshold from the network node.

[0271] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: sending a NACK associated with the second transport block to the network node before receiving the control information for scheduling the first transport block.

[0272] Aspect 6: According to the method of aspect 5, the method further includes: starting a timer in response to sending the HARQ NACK associated with the second transport block, wherein sending the signaling indicating the unsuccessful termination of the HARQ process is in response to the expiration of the timer.

[0273] Aspect 7: According to the method of aspect 6, the sending of the signaling indicating the unsuccessful termination of the HARQ process occurs before the control information is received from the network node.

[0274] Aspect 8: The method according to aspect 6, the method further comprising: resetting the timer in response to receiving second control information for scheduling the second transport block, wherein the timer is associated with the same HARQ identifier, and wherein resetting the timer also responds to receiving any control information for scheduling the transport block associated with the same HARQ identifier.

[0275] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: receiving from the network node a third transport block having the same HARQ identifier as the first transport block; and sending an ACK or NACK associated with the third transport block to the network node before receiving the control information scheduling the first transport block, wherein the unsuccessful termination indicating the termination of the HARQ process is also in response to a first NDI associated with the first transport block and a second NDI associated with the third transport block.

[0276] Aspect 10: The method according to aspect 9, wherein the identification of the unsuccessful termination of the HARQ process is in response to the first NDI being different from the second NDI.

[0277] Aspect 11: The method according to aspect 10, wherein: the first NDI and the second NDI each comprise two or more bits; and the difference between a first value associated with the first NDI and a second value associated with the second NDI is two or greater.

[0278] Aspect 12: The method according to aspect 11, the method further comprising: identifying a second unsuccessful termination of a second HARQ process associated with the third transport block in response to the UE failing to successfully decode the third transport block and the difference being two or greater; and sending the HARQ NACK associated with the third transport block to the network node, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates the second unsuccessful termination of the second HARQ process.

[0279] Aspect 13: According to the method of aspect 12, wherein the HARQ process and the second HARQ process are associated with the same HARQ identifier.

[0280] Aspect 14: According to the method of aspect 9, wherein the failure to terminate the HARQ process also responds to sending the HARQ ACK associated with the third transport block and the first NDI and the second NDI are the same.

[0281] Aspect 15: According to the method of aspect 14, wherein the failure to terminate the HARQ process is identified in response to: the first transport block size indicated by the control information being different from the second transport block size associated with the third transport block; the MCS indicated by the control information failing to include a reserved value for the decoding rate of the first transport block; the control information scheduling the initial transmission of the first transport block; or the control information indicating a redundant version of the first transport block with a value of 0.

[0282] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the signaling indicating the unsuccessful termination of the HARQ process includes an identifier associated with the HARQ process and an NDI associated with the HARQ process.

[0283] Aspect 17: According to the method of aspect 16, the signaling indicating the unsuccessful termination of the HARQ process further includes an index associated with a component carrier of the second transport block, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0284] Aspect 18: The method according to any one of Aspects 1 to 17, wherein: the signaling indicating the unsuccessful termination of the HARQ process includes a bitmap associated with a plurality of HARQ process identifiers; and the value of a bit in the bitmap associated with the HARQ process indicates the unsuccessful termination of the HARQ process.

[0285] Aspect 19: According to the method of aspect 18, the signaling indicating the unsuccessful termination of the HARQ process further includes an NDI associated with the HARQ process, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0286] Aspect 20: According to the method of aspect 18, the signaling indicating the unsuccessful termination of the HARQ process includes a plurality of bitmaps, each of which is associated with a different component carrier.

[0287] Aspect 21: The method according to any one of Aspects 1 to 20, wherein: the same HARQ identifier is associated with a first NDI and a second NDI; and the signaling indicating the unsuccessful termination of the HARQ process includes an acknowledgment (ACK) or a NACK for each of the first NDI and the second NDI.

[0288] Aspect 22: The method according to any one of Aspects 1 to 21, wherein sending the signaling indicating the unsuccessful termination of the HARQ process includes sending the signaling via uplink control information, MAC-CE, or radio link control status report.

[0289] Aspect 23: The method according to any one of Aspects 1 to 22, the method further comprising: receiving from the network node a signaling instructing the UE to report the unsuccessful termination of the HARQ procedure to the network node, wherein sending the signaling instructing the unsuccessful termination of the HARQ procedure is in response to receiving the signaling instructing the UE to report the unsuccessful termination of the HARQ procedure.

[0290] Aspect 24: The method according to aspect 22, the method further comprising: sending to the network node the capability of the UE to report to the network node the unsuccessful termination of the HARQ procedure, wherein receiving the signaling indicating that the UE reported the unsuccessful termination is in response to sending the capability of the UE.

[0291] Aspect 25: A method for wireless communication by a network node, the method comprising: sending control information to a UE to schedule a first transport block and indicate that the first transport block has the same HARQ identifier as a second transport block; and receiving from the UE signaling an unsuccessful termination of a HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

[0292] Aspect 26: According to the method of aspect 25, wherein the control information scheduling the first transport block indicates a change in the value of the NDI associated with the same HARQ identifier.

[0293] Aspect 27: The method according to any one of Aspects 25 to 26, wherein receiving the signaling indicating the unsuccessful termination of the HARQ process also responds to the retransmission count associated with the second transport block being less than a threshold.

[0294] Aspect 28: The method according to aspect 27 further includes: sending a second signaling indicating the threshold to the UE.

[0295] Aspect 29: The method according to any one of Aspects 25 to 28, the method further comprising: receiving from the UE a NACK associated with the second transport block before transmitting the control information for scheduling the first transport block.

[0296] Aspect 30: According to the method of aspect 29, the receiving of the signaling indicating the unsuccessful termination of the HARQ process also responds to the expiration of a timer associated with the HARQ identifier.

[0297] Aspect 31: According to the method of aspect 30, the reception of the signaling indicating the unsuccessful termination of the HARQ procedure occurs before the control information is sent to the UE.

[0298] Aspect 32: The method according to any one of Aspects 25 to 31, the method further comprising: sending a third transport block to the UE having the same HARQ identifier as the first transport block; and receiving an ACK or NACK associated with the third transport block from the UE before sending the control information scheduling the first transport block, wherein receiving the signaling indicating the unsuccessful termination of the HARQ procedure also responds to a first NDI associated with the first transport block and a second NDI associated with the third transport block.

[0299] Aspect 33: According to the method of aspect 32, receiving the signaling indicating the unsuccessful termination of the HARQ process also responds to the first NDI being different from the second NDI.

[0300] Aspect 34: The method according to aspect 33, wherein: the first NDI and the second NDI each comprise two or more bits; and the difference between a first value associated with the first NDI and a second value associated with the second NDI is two or greater.

[0301] Aspect 35: The method according to aspect 34, the method further comprising: receiving from the UE the HARQ NACK associated with the third transport block, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates a second unsuccessful termination of a second HARQ process associated with the third transport block, and wherein the signaling indicates the second unsuccessful termination of the second HARQ process in response to the UE failing to successfully decode the third transport block and the difference being two or greater.

[0302] Aspect 36: According to the method of aspect 35, wherein the HARQ process and the second HARQ process are associated with the same HARQ identifier.

[0303] Aspect 37: According to the method of aspect 32, wherein receiving the signaling indicating the unsuccessful termination of the HARQ process also responds to the HARQ ACK associated with the third transport block and the first NDI and the second NDI are the same.

[0304] Aspect 38: According to the method of aspect 37, receiving the signaling indicating the unsuccessful termination of the HARQ process further responds to: the first transport block size indicated by the control information being different from the second transport block size associated with the third transport block; the MCS indicated by the control information failing to include a reserved value for the decoding rate of the first transport block; the control information scheduling the initial transmission of the first transport block; or the control information indicating a redundancy version of the first transport block with a value of 0.

[0305] Aspect 39: The method according to any one of Aspects 25 to 38, wherein the signaling indicating the unsuccessful termination of the HARQ process includes an identifier associated with the HARQ process and an NDI associated with the HARQ process.

[0306] Aspect 40: According to the method of aspect 39, the signaling indicating the unsuccessful termination of the HARQ process further includes an index associated with a component carrier of the second transport block, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0307] Aspect 41: The method according to any one of Aspects 25 to 40, wherein: the signaling indicating the unsuccessful termination of the HARQ process includes a bitmap associated with a plurality of HARQ process identifiers; and the value of a bit in the bitmap associated with the HARQ process indicates the unsuccessful termination of the HARQ process.

[0308] Aspect 42: According to the method of aspect 41, the signaling indicating the unsuccessful termination of the HARQ process further includes an NDI associated with the HARQ process, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

[0309] Aspect 43: According to the method of aspect 41, the signaling indicating the unsuccessful termination of the HARQ process includes a plurality of bitmaps, each of which is associated with a different component carrier.

[0310] Aspect 44: The method according to any one of Aspects 25 to 43, wherein: the same HARQ identifier is associated with a first NDI and a second NDI; and the signaling indicating the unsuccessful termination of the HARQ process includes an acknowledgment (ACK) or a NACK for each of the first NDI and the second NDI.

[0311] Aspect 45: The method according to any one of Aspects 25 to 44, wherein receiving the signaling indicating the unsuccessful termination of the HARQ process includes receiving the signaling via uplink control information, MAC-CE, or radio link control status report.

[0312] Aspect 46: The method according to any one of Aspects 25 to 45, the method further comprising: sending to the UE a signaling instruction to the UE to report the unsuccessful termination of the HARQ procedure to the network node, wherein receiving the signaling instruction indicating the unsuccessful termination of the HARQ procedure is in response to sending the signaling instruction to the UE to report the unsuccessful termination of the HARQ procedure.

[0313] Aspect 47: The method according to aspect 46, the method further comprising: receiving from the UE the capability of the UE to report to the network node that the HARQ procedure was not successfully terminated, wherein sending the signaling instructing the UE to report the failure to terminate is in response to receiving the capability of the UE.

[0314] Aspect 48: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to 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 according to one or more of aspects 1 to 47.

[0315] Aspect 49: 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 being configured to cause the device to perform the method according to one or more of aspects 1 to 47.

[0316] Aspect 50: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 47.

[0317] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 47.

[0318] Aspect 52: 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 according to one or more of aspects 1 to 47.

[0319] Aspect 53: A device for wireless communication, the device including a processing system comprising: one or more processors; and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 47.

[0320] Aspect 54: 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 being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 47.

[0321] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0322] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0323] As used in this article, depending on the context, "meeting the threshold" can mean a value 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, not equal to the threshold, etc.

[0324] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0325] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0326] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the UE to: Receive control information from the network node to schedule the first transport block and indicate that the first transport block has the same Hybrid Automatic Repeat Request (HARQ) identifier as the second transport block; In response to the UE failing to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both, to identify the unsuccessful termination of the HARQ process associated with the second transport block; as well as Send a signaling message to the network node indicating the unsuccessful termination of the HARQ process associated with the second transport block.

2. The UE of claim 1, wherein the control information scheduling the first transport block indicates a change in the value of a new data indicator associated with the same HARQ identifier.

3. The UE according to claim 1, wherein, In order for the UE to send the signaling indicating the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to send the signaling in response to the number of retransmissions associated with the second transport block being less than a threshold.

4. The UE of claim 3, wherein the processing system is further configured to cause the UE to: Receive a second signaling indicating the threshold from the network node.

5. The UE of claim 1, wherein the processing system is further configured to cause the UE to: Before receiving the control information for scheduling the first transport block, a HARQ negative acknowledgment (NACK) associated with the second transport block is sent to the network node.

6. The UE of claim 5, wherein the processing system is further configured to cause the UE to: In response to sending the HARQ NACK associated with the second transport block to start a timer, wherein in order for the UE to send the signaling indicating the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to send the signaling in response to the expiration of the timer.

7. The UE according to claim 6, wherein, In order for the UE to send the signaling indicating the unsuccessful termination of the HARQ procedure, the processing system is configured to cause the UE to send the signaling before receiving the control information from the network node.

8. The UE of claim 6, wherein the processing system is further configured to cause the UE to: In response to receiving second control information scheduling the second transport block, the timer is reset, wherein the timer is associated with the same HARQ identifier, and wherein, In order for the UE to reset the timer, the processing system is configured to cause the UE to reset the timer in response to receiving any control information scheduling a transport block associated with the same HARQ identifier.

9. The UE of claim 1, wherein the processing system is further configured to cause the UE to: Receive a third transport block from the network node having the same HARQ identifier as the first transport block; and Before receiving the control information for scheduling the first transport block, a HARQ acknowledgment (ACK) or HARQ negative ACK (NACK) associated with the third transport block is sent to the network node, wherein... In order for the UE to identify the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to identify the unsuccessful termination of the HARQ process in response to a first new data indicator associated with the first transport block and a second new data indicator associated with the third transport block.

10. The UE according to claim 9, wherein, In order for the UE to identify the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to identify the unsuccessful termination of the HARQ process in response to the first new data indicator being different from the second new data indicator.

11. The UE according to claim 10, wherein: The first new data indicator and the second new data indicator each comprise two or more bits; and The difference between the first value associated with the first new data indicator and the second value associated with the second new data indicator is two or greater.

12. The UE of claim 11, wherein the processing system is further configured to cause the UE to: In response to the UE failing to successfully decode the third transport block and the difference being two or greater, indicating a second unsuccessful termination of the second HARQ process associated with the third transport block; and Send the HARQ NACK associated with the third transport block to the network node, wherein the signaling indicating the unsuccessful termination of the HARQ process also indicates the second unsuccessful termination of the second HARQ process.

13. The UE of claim 12, wherein the HARQ procedure and the second HARQ procedure are associated with the same HARQ identifier.

14. The UE according to claim 9, wherein, In order for the UE to identify the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to identify the failure by sending the HARQ ACK associated with the third transport block and having the first new data indicator and the second new data indicator be the same.

15. The UE according to claim 14, wherein, In order for the UE to identify the unsuccessful termination of the HARQ procedure, the processing system is configured to cause the UE to identify the failure in response to the following: The first transport block size indicated by the control information is different from the second transport block size associated with the third transport block; The modulation and decoding scheme indicated by the control information failed to include a reserved value for the decoding rate for the first transmission block; The control information schedules the initial transmission of the first transmission block; or The control information indicates that the value of the redundant version of the first transport block is 0.

16. The UE of claim 1, wherein the signaling indicating the unsuccessful termination of the HARQ procedure includes an identifier associated with the HARQ procedure and a new data indicator associated with the HARQ procedure.

17. The UE of claim 16, wherein the signaling indicating the unsuccessful termination of the HARQ process further includes an index associated with a component carrier of the second transport block, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

18. The UE according to claim 1, wherein: The signaling indicating the unsuccessful termination of the HARQ procedure includes a bitmap associated with multiple HARQ procedure identifiers; and The value of a bit in the bitmap associated with the HARQ procedure indicates the unsuccessful termination of the HARQ procedure.

19. The UE of claim 18, wherein the signaling indicating the unsuccessful termination of the HARQ process further includes a new data indicator associated with the HARQ process, an indication of the time associated with the unsuccessful termination of the HARQ process, or both.

20. The UE of claim 18, wherein the signaling indicating the unsuccessful termination of the HARQ procedure comprises a plurality of bitmaps, each of the plurality of bitmaps being associated with a different component carrier.

21. The UE according to claim 1, wherein: The same HARQ identifier is associated with the first new data indicator and the second new data indicator; and The signaling indicating that the HARQ process was not successfully terminated includes an acknowledgment (ACK) or a non-acknowledgment (NACK) for each of the first new data indicator and the second new data indicator.

22. The UE according to claim 1, wherein, In order for the UE to send the signaling indicating the unsuccessful termination of the HARQ procedure, the processing system is configured to cause the UE to send the signaling via uplink control information, media access control control element, or radio link control status report.

23. The UE of claim 1, wherein the processing system is further configured to cause the UE to: The UE receives a signaling message from the network node instructing it to report the unsuccessful termination of the HARQ procedure to the network node, wherein... In order for the UE to send the signaling indicating the unsuccessful termination of the HARQ process, the processing system is configured to cause the UE to send the signaling indicating the unsuccessful termination of the HARQ process in response to receiving the signaling instructing the UE to report the unsuccessful termination of the HARQ process.

24. The UE of claim 23, wherein the processing system is further configured to cause the UE to: The ability of the UE to send a report to the network node regarding the unsuccessful termination of the HARQ procedure, wherein... In order for the UE to receive the signaling indicating that the UE reported unsuccessful termination, the processing system is configured to cause the UE to receive the signaling indicating the termination in response to the capability of the UE.

25. A network node for wireless communication, the network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the network node to: Control information is sent to the User Equipment (UE) to schedule the first transport block and indicate that the first transport block has the same Hybrid Automatic Repeat Request (HARQ) identifier as the second transport block; as well as The UE receives a signaling indicating unsuccessful termination of the HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

26. The network node of claim 25, wherein the control information scheduling the first transport block indicates a change in the value of a new data indicator associated with the same HARQ identifier.

27. The network node according to claim 25, wherein, In order for the network node to receive the signaling indicating the unsuccessful termination of the HARQ process, the processing system is configured to cause the network node to receive the signaling in response to the number of retransmissions associated with the second transport block being less than a threshold.

28. The network node of claim 27, wherein the processing system is further configured to cause the network node to: Send a second signaling indicating the threshold to the UE.

29. A method for wireless communication by a user equipment (UE), the method comprising: Receive control information from the network node to schedule the first transport block and indicate that the first transport block has the same Hybrid Automatic Repeat Request (HARQ) identifier as the second transport block; In response to the UE failing to successfully decode the second transport block, the control information scheduling of the first transport block having the same HARQ identifier as the second transport block, or both, to identify the unsuccessful termination of the HARQ process associated with the second transport block; as well as Send a signaling message to the network node indicating the unsuccessful termination of the HARQ process associated with the second transport block.

30. A method for wireless communication by network nodes, the method comprising: Control information is sent to the User Equipment (UE) to schedule the first transport block and indicate that the first transport block has the same Hybrid Automatic Repeat Request (HARQ) identifier as the second transport block; as well as The UE receives a signaling indicating unsuccessful termination of the HARQ procedure associated with the second transport block, wherein receiving the signaling is in response to the UE failing to successfully decode the second transport block, the control information scheduling the first transport block having the same HARQ identifier as the second transport block, or both.

Images