Adaptation techniques for hybrid automatic repeat request retransmission handling

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may obtain hybrid automatic repeat request (HARQ) information indicating whether a network node is configured to perform retransmission of decoded information before an end of a HARQ process associated with the network node. When complete decoding information for a transport block (TB) associated with the reserved MCS is unavailable, the UE may receive a retransmission of the TB for a HARQ process associated with downlink communications from the network node. The UE may perform an action to continue the HARQ process, restart the HARQ process, or terminate the HARQ process based on receiving the retransmission, wherein the action is based on whether the network node is configured to perform the retransmission of the indication of the MCS. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 585,031, filed September 25, 2023, entitled “TECHNIQUES FOR ADAPTATION OF HYBRID AUTOMATIC REPEAT REQUEST RETRANSMISSION HANDLING,” and U.S. Non-Provisional Patent Application No. 18 / 804,700, filed August 14, 2024, entitled “TECHNIQUES FOR ADAPTATION OF HYBRID AUTOMATIC REPEAT REQUEST RETRANSMISSION HANDLING,” both of which are assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication and to adaptation techniques and apparatus for Hybrid Automatic Repeat Request (HARQ) retransmission handling.

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0006] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0007] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, or global level. New Radio (NR) (also known as 5G) is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. Summary of the Invention

[0008] Some aspects described herein relate to a method for wireless communication performed by a user equipment (UE). The method may include: obtaining Hybrid Automatic Repeat Request (HARQ) information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an indication of a modulation and decoding scheme (MCS) before the end of a HARQ process associated with the network node. The method may include: receiving a retransmission of a transport block (TB) of downlink communication for a HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with a reserved MCS and complete decoding information for the TB is unavailable. The method may include: performing an action based on the received retransmission of the TB to continue the HARQ process, restart the HARQ process, or terminate the HARQ process, wherein the action is based on whether the network node is configured to retransmit the indication of the MCS before the end of each HARQ process.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to obtain HARQ information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an indication of an MCS before the end of a HARQ process associated with the network node. The one or more processors may be individually or collectively configured to receive a retransmission of a TB (Through-Terminal) of downlink communication for a HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with a retained MCS and complete decoding information for the TB is unavailable. The one or more processors may be individually or collectively configured to perform an action based on the received retransmission of the TB to continue the HARQ process, restart the HARQ process, or terminate the HARQ process, wherein the action is based on whether the network node is configured to retransmit the indication of the MCS before the end of each HARQ process.

[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 obtain HARQ information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an indication of an MCS before the end of a HARQ process associated with the network node. When executed by one or more processors of the UE, the set of instructions enables the UE to receive a retransmission of a TB (Through-of-Traffic) for a downlink communication associated with a HARQ process from the network node, wherein the retransmission is associated with a reserved MCS and complete decoding information for the TB is unavailable. When executed by one or more processors of the UE, the set of instructions enables the UE to perform actions based on the received retransmission of the TB to continue the HARQ process, restart the HARQ process, or terminate the HARQ process, wherein the action is based on whether the network node is configured to retransmit the indication of the MCS before the end of each HARQ process.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining HARQ information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an indication of an MCS before the end of a HARQ process associated with the network node. The apparatus may include components for receiving a retransmission of a TB (Through-Terminal) of downlink communication associated with a HARQ process from the network node, wherein the retransmission is associated with a retained MCS and complete decoding information for the TB is unavailable. The apparatus may include components for performing actions based on the received retransmission of the TB to continue the HARQ process, restart the HARQ process, or terminate the HARQ process, wherein the action is based on whether the network node is configured to retransmit the indication of the MCS before the end of each HARQ process.

[0012] Some aspects described herein relate to a method for wireless communication performed by a UE. This method may include: receiving a retransmission of a transport block (TB) of downlink communication for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS and complete decoding information for the TB is unavailable. The method may also include: sending a HARQ feedback communication to the network node based on the receipt of the retransmission, indicating that the complete decoding information is unavailable.

[0013] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to receive a retransmission of a TB (Through-Terminal) of downlink communication for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS (Mean Classification Sequence) and the complete decoding information for the TB is unavailable. The one or more processors may be individually or collectively configured to send a HARQ feedback communication to the network node indicating that the complete decoding information is unavailable based on the receipt of the retransmission.

[0014] 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 a retransmission of a TB (Through Block) of downlink communication associated with a HARQ process from a network node, wherein the retransmission is associated with a reserved MCS (Mechanical Classification), and the complete decoding information for the TB is unavailable. When executed by one or more processors of the UE, the set of instructions enables the UE to send a HARQ feedback communication to the network node indicating that the complete decoding information is unavailable based on the receipt of the retransmission.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a retransmission of a TB (Through-Terminal) of downlink communication in connection with a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS (Mean Class Sequence) and complete decoding information for the TB is unavailable. The apparatus may also include components for sending a HARQ feedback communication to the network node based on the receipt of the retransmission, indicating that the complete decoding information is unavailable.

[0016] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0017] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims. Attached Figure Description

[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network.

[0020] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

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

[0022] Figure 4 This is an illustration of an example of a redundant version of this disclosure.

[0023] Figure 5A and Figure 5B This is a diagram illustrating an example of an adaptation to Hybrid Automatic Repeat Request (HARQ) retransmission processing based on this disclosure.

[0024] Figure 6 This is a diagram illustrating an example process associated with the adaptation to HARQ operating mode according to this disclosure.

[0025] Figure 7 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0026] Figure 8 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0027] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0028] In a Hybrid Automatic Repeat Request (HARQ) process, an initial transmission associated with a first redundancy version of a transport block (TB) can be sent to the receiver, followed by one or more retransmissions associated with different redundancy versions (RVs) of the same TB. For example, the first redundancy version could be RV 0, and the different redundancy versions could be RV 2, RV 3, and RV 1, respectively. In some examples, the modulation and decoding scheme (MCS) can be indicated to the receiver via RV 0, so that the MCS is not re-indicated to the receiver via one or more retransmissions associated with RV 2, RV 3, and RV 1. Instead, different redundancy versions can be associated with a reserved MCS that corresponds to the same MCS used for RV 0 (e.g., to reduce the size of the different redundancy versions). However, if RV 0 is not successfully received by the receiver (e.g., lost and / or undetermined), the reserved MCS corresponding to the MCS of RV 0 may not be determined by the UE. Therefore, the UE may be unable to decode one or more different redundancy versions (such as RV 2, RV 3, and / or RV 1). Therefore, when one or more different redundant versions cannot be decoded by the receiver because RV 0 is not successfully received, continuing to retransmit one or more different redundant versions to the receiver unnecessarily consumes resources.

[0029] The receiver can be configured to send a HARQ acknowledgment (ACK) to the transmitter when a HARQ transmit / retransmission is successfully received and decoded by the receiver. The receiver can also be configured to send a negative acknowledgment (NACK) to the transmitter when a HARQ transmit / retransmission is not successfully received and decoded by the receiver. If the transmitter does not receive an ACK or NACK from the receiver, the transmitter can determine that a discontinuous transmission (DTX) has occurred and proceed with the retransmission of the next redundancy version (e.g., RV 2). Therefore, if the receiver expects to receive RV 0, but RV 0 is not successfully received, the receiver may unexpectedly receive RV 2. The unexpected reception of RV 2 can indicate to the receiver that RV 0 was lost, which can then cause the receiver to send a “forced” ACK to the transmitter. A forced ACK can terminate additional HARQ retransmissions associated with the remaining different redundancy versions of the TB, reducing potential resource waste due to the receiver's inability to decode additional HARQ retransmissions associated with the remaining different redundancy versions of the TB.

[0030] However, in some cases, if the transmitter detects that the number of NACK indications associated with the HARQ process meets a threshold, the transmitter can fall back to retransmitting information associated with decoding the TB, such as indications of MCS and / or Physical Resource Block (PRB) allocations. For example, if the transmitter detects a DTX and determines that the number of NACK indications associated with the HARQ process meets the threshold, the transmitter can fall back to retransmitting RV 0 (or another RV with information for decoding the TB). For example, the transmitter can send RV 0. The receiver may fail to detect, decode, or otherwise receive RV 0. The transmitter can detect a DTX and can send RV 2 with a reserved MCS, which can be received by the receiver. However, because the receiver cannot decode RV 2, the receiver can send a NACK (e.g., a HARQ NACK), and the transmitter can receive this NACK. The receiver can continue sending NACKs for subsequent RV reception. The transmitter can determine that the number of NACK indications meets the threshold. Therefore, the transmitter can send an RV (e.g., RV 0 or another RV) that includes information associated with decoding the RV (e.g., MCS and / or PRB allocation). This allows the receiver and / or transmitter to resume the HARQ process and decode the TB without requiring Radio Link Control (RLC) level retransmissions. Enabling the reception of the HARQ process and / or reducing the likelihood of RLC retransmissions can reduce latency and conserve resources associated with receiving the TB.

[0031] However, the receiver may not receive indication of the HARQ operation or configuration being used at the transmitter. For example, the receiver may not know whether the transmitter is configured to fall back to retransmitting indications for the MCS and / or other information after a given number of NACK indications. Therefore, in some cases, the receiver may not send a forced ACK, and the transmitter may not be configured to fall back to retransmitting indications for the MCS and / or other information after a given number of NACK indications, resulting in resource consumption associated with RVs that the receiver cannot decode. In other examples, the receiver may send a forced ACK, and the transmitter may be configured to fall back to retransmitting indications for the MCS and / or other information after a given number of NACK indications. However, the receiver may send a forced ACK before a given number of NACK indications are sent, resulting in a retransmission of the RLC for the TB, which might have otherwise been received and / or recovered during the HARQ process.

[0032] Various aspects relate to wireless communication as a whole, and more specifically to HARQ procedures. Some aspects relate more specifically to adaptive forced ACK transmission for HARQ procedures. For example, a receiver (e.g., a user equipment (UE) or network node) may obtain information associated with a transmitter's (e.g., a network node or UE) HARQ operation. For example, the receiver may execute one or more HARQ procedures together with the transmitter to obtain an indication. This information may indicate whether the HARQ operation includes an indication to retransmit the MCS (and / or other information associated with decoding operations at the receiver) before the end of each HARQ procedure. For example, this information may indicate whether the transmitter is associated with a NACK-based retransmission of the MCS during a given HARQ procedure. In some aspects, this information may include an indication of the number of NACK indications that trigger the transmitter to retransmit information associated with decoding operations at the receiver, such as MCS and / or PRB allocation, etc.

[0033] For example, during the “learning” phase, the receiver may perform one or more HARQ processes together with the transmitter to obtain information, as described in more detail elsewhere in this document. During the “adaptation” phase, the receiver may adapt one or more HARQ operations. For example, the receiver may adapt a forced ACK operation based on this information. For example, if the information indicates that the transmitter does not retransmit the indication to the MCS (and / or other information associated with the decoding operation at the receiver) before the end of each HARQ process, the receiver may send a forced ACK based on receiving an unexpected RV and / or based on receiving an RV with a reserved MCS before the receiver receives the indication to the MCS. If the information indicates that the transmitter does retransmit the indication to the MCS (and / or other information associated with the decoding operation at the receiver) before the end of each HARQ process, the receiver may adapt a forced ACK operation to send a forced ACK only after that number of NACK indications has been sent.

[0034] In some respects, the receiver may be based on, respond to, or otherwise associated with the detection of events transitioning between the learning and adaptation phases. For example, such events may include: receiving configuration information, detecting changes in cell information, detecting changes in the used subcarrier spacing (SCS), detecting that an MCS retransmission did not arrive as expected, performing a handover operation, receiving radio bearer configuration, receiving RLC configuration, detecting changes in quality of service (QoS) parameters, and / or detecting changes in Protocol Data Unit (PDU) session type, etc. Additionally or alternatively, the receiver may be based on, respond to, or otherwise associated with periodic scheduling transitions between the learning and adaptation phases. For example, the receiver may periodically switch between the learning and adaptation phases.

[0035] In some respects, the receiver can send HARQ feedback communication indicating that the complete decoding information for the TB is unavailable in the HARQ process. For example, the receiver can receive a retransmission of the TB, where the retransmission is associated with a reserved MCS. The receiver can determine that the complete decoding information for the TB is unavailable at the receiver. Therefore, the receiver can send HARQ feedback communication indicating that the complete decoding information for the TB is unavailable. For example, the HARQ feedback communication can be associated with a HARQ state indicating lost decoding information.

[0036] Several aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some aspects, by adapting the forced ACK transmission operation for the HARQ process, the receiver can be enabled to send a forced ACK to prematurely terminate the HARQ process based on the transmitter not being configured to retransmit the indication to the MCS during the HARQ process and / or only after the expected retransmission of the MCS. This can save processing and / or network resources that would otherwise be used to send and / or receive RVs that the receiver cannot decode during the HARQ process. Additionally, when the transmitter is configured to retransmit the indication to the MCS during the HARQ process, this can enable the receiver to receive and / or decode TBs during the HARQ process. This can reduce the likelihood of RLC retransmission for TBs, thereby reducing latency and saving resources (e.g., processing and / or network resources) that would otherwise be associated with RLC retransmission.

[0037] Additionally, by performing one or more operations associated with the learning phase, the receiver can be made to adapt the forced ACK transmission operation used in the HARQ process to the HARQ operation of the transmitter with which the receiver is communicating. By switching between the learning and adaptation phases (e.g., periodically and / or based on detected events), the accuracy of the information used for the transmitter's HARQ operation can be improved, thereby enhancing the effectiveness of the receiver's forced ACK transmission adaptation.

[0038] By sending HARQ feedback communication indicating that complete decoded information for a TB is unavailable (e.g., in response to receiving a retransmission of a TB associated with a retained MCS), the receiver can instruct the transmitter to request a retransmission of complete decoded information. This allows the transmitter to identify when the receiver has missed or lost complete decoded information for a given HARQ process. Therefore, the latency associated with TB communication can be reduced (e.g., because the receiver can quickly obtain complete decoded information after it has been missed). Furthermore, this can save network resources, processing resources, and / or power resources, etc., that would otherwise be associated with communication regarding the retransmission of TBs that cannot be decoded by the receiver and / or communication regarding one or more NACK feedback indications in response to the retransmission of TBs that cannot be decoded by the receiver.

[0039] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0040] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices 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 thereof. 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.

[0041] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0042] Figure 1This is an illustration of an example of a wireless network 100. Wireless network 100 can be a 5G (e.g., NR) network or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., LTE) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), one or more UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), or other entities. Network node 110 is an example of a network node communicating with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0043] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, network node 110 may include NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0044] In some examples, network node 110 may provide communication coverage for a given geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a residential area) and may allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0045] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

[0046] Wireless network 100 may include one or more relay stations. A relay station is a network node that receives data transmissions from an upstream node (e.g., network node 110 or UE 120) and transmits the data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. 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. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, or relay, etc.

[0047] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless 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).

[0048] Network controller 130 may be coupled to or communicate with a set of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0049] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be 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, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, or any other suitable device configured to communicate via wireless or wired media.

[0050] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, meters, monitors, or location markers that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0051] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a given RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology or air interface. A frequency can also be referred to as a carrier or frequency channel. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0052] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or a mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0053] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to in documents and articles as the “millimeter wave” band, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0054] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 into the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range designations 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). Each of these higher frequency bands falls within the EHF band.

[0055] In light of these examples, unless otherwise specifically stated, the term "below 6 GHz" used herein can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the term "millimeter wave" used herein can broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies within the EHF band. It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0056] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain HARQ information indicating whether a network node is configured to retransmit an indication of the MCS before the end of a HARQ process associated with the network node; retransmit a TB for receiving downlink communication in a HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with a reserved MCS and the full decoding information for the TB is unavailable; and perform actions to continue the HARQ process, restart the HARQ process, or terminate the HARQ process based on the received TB retransmission, wherein the actions are based on whether the network node is configured to retransmit an indication of the MCS before the end of each HARQ process. Additionally or alternatively, the communication manager 140 may receive a retransmission of a TB (Through Block) for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS (Multi-Channel System) and the complete decoding information for the TB is unavailable; and / or send HARQ feedback communication to the network node indicating that the complete decoding information is unavailable based on the receipt of the retransmission. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0058] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in wireless network 100. Network node 110 may be equipped with a set of antennas 234a to 234t, such as... T One antenna ( T ≥1). UE 120 may be equipped with an array of antennas 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0059] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use with UE 120 (or a set of UEs 120). Transmitting processor 220 can use one or more Channel Quality Indicators (CQIs) received from UE 120 to select one or more MCSs for that UE 120. Network node 110 can use the MCS selected for UE 120 to process (e.g., encode and modulate) the data for UE 120 and can provide data symbols to UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding, if applicable) on data symbols, control symbols, overhead symbols, or reference symbols, and can direct to a corresponding set of modems 232 (e.g., modems 232a to 232t) shown as modems 232a to 232t. T A set of output symbol streams (e.g., modems) is provided by a modem. T Each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can be transmitted via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., T (One downlink signal).

[0060] At UE 120, the set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110, and can transmit signals to the set of modems 254 (e.g., R Each modem (shown as modems 254a to 254r) provides a set of received signals (e.g., REach received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0061] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0062] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element collections, non-coplanar antenna element collections, or coupled to one or more transmitting or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

[0063] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information (e.g., reports including RSRP, RSSI, RSRQ, or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-decoded by TX MIMO processor 266 where applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or any combination of TX MIMO processor 266. The transceiver may be used by processor (e.g., controller / processor 280) and memory 282 to perform textual (e.g., reference) functions. Figure 5A , Figure 5B as well as Figures 6 to 8 ( ) describes any aspect of any process in the process described.

[0064] At network node 110, uplink signals from UE 120 or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted via UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). Figure 5A , Figure 5B as well as Figures 6 to 8 ( ) describes any aspect of any process in the process described.

[0065] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0066] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0067] In some respects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as network node 110). For example, the processing system of network node 110 may be a system that includes various other components or sub-components of network node 110.

[0068] The processing system of network node 110 can interface with one or more other components of network node 110, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of network node 110 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing network node 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing network node 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0069] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2 Any other component may perform one or more techniques associated with the adaptation of HARQ retransmission handling, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or... Figure 2 Any other component (or combination of components) can perform or instruct, for example Figure 7 The operation of process 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, one or more instructions may cause the one or more processors of network node 110 or UE 120, UE 120, or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 or UE 120 (e.g., directly executed, or executed after compilation, transformation, or interpretation). Figure 7 The operation of process 700 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0070] In some aspects, UE 120 includes components for obtaining HARQ information, wherein the HARQ information indicates whether a network node is configured to retransmit an indication of the MCS before the end of a HARQ process associated with the network node; components for retransmitting a TB of downlink communication for a HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with a reserved MCS and full decoding information for the TB is unavailable; and / or components for performing an action to continue the HARQ process, restart the HARQ process, or terminate the HARQ process based on the received TB retransmission, wherein the action is based on whether the network node is configured to retransmit an indication of the MCS before the end of each HARQ process. Additionally or alternatively, UE 120 includes components for receiving a retransmission of a TB (Through Transmission) of downlink communication for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS (Multi-Channel System) and the complete decoding information for the TB is unavailable; and / or for sending HARQ feedback communication to the network node indicating that the complete decoding information is unavailable based on the receipt of the retransmission. Components for enabling UE 120 to perform the operations described herein may include one or more of, for example, 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, and / or a memory 282, etc.

[0071] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0072] In some respects, individual processors can be described as performing all functions executed by the one or more processors. In other respects, the one or more processors can collectively perform a set of functions. For example, the processors of a first set (one or more) of the one or more processors can be described as performing a first function executed by the one or more processors, and the processors of a second set (one or more) of the one or more processors can be described as performing a second function executed by the 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 processors" should be understood as referring to a combination of processors. Figure 2Any one or more processors described. 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, a function 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.

[0073] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0074] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a converged or decomposed architecture. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5G NB, access points (APs), TRPs, or cells, etc.) or one or more units (or one or more components) that perform base station functions can be implemented as converged base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0075] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0076] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0077] In some respects, this document describes actions performed by network node 110 that can be performed by multiple different network nodes. For example, configuration actions can be performed by a first network node (e.g., CU or DU), and radio communication actions can be performed by a second network node (e.g., DU or RU).

[0078] As used herein, "outputting" or "transmitting" communication from network node 110 to UE 120 can refer to direct transmission (e.g., from network node 110 to UE 120) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to UE 120 may include the DU outputting or transmitting communication to an RU and the RU transmitting communication to UE 120, or may include causing the RU to transmit communication (e.g., triggering the transmission of a physical layer reference signal). Similarly, "transmitting" communication from UE 120 to network node 110 can refer to direct transmission (e.g., from UE 120 to network node 110) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to network node 110 may include UE 120 transmitting communication to an RU and the RU transmitting communication to the DU. Similarly, network node 110 “receiving” communication may refer to directly receiving a transmission carrying communication (e.g., from UE 120 to network node 110) or receiving communication (or information derived from receiving communication) via one or more other network nodes or devices.

[0079] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0080] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

[0081] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more 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 implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0082] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the RLC layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0083] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0084] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support 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 305 can be configured to 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. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0085] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical 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 actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

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

[0087] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0088] Figure 4 This is an illustration of Example 400, which illustrates a redundancy version according to this disclosure. UE 120 may cyclically apply the redundancy version to uplink communications (e.g., Physical Uplink Shared Channel (PUSCH) repetition) to transmit different redundant versions of PUSCH repetition at different transmission times. Additionally or alternatively, network node 110 may cyclically apply the redundancy version to downlink repetition to transmit different redundant versions of transmission at different transmission times (e.g., TB).

[0089] A repeated “redundant version” (RV) refers to a set of coded bits transmitted for that repeat. Using RV cycles, wireless communication devices (e.g., UE 120 and / or network node 110) can transmit different sets of coded bits in different repeats. For example, the wireless communication device can store bits for transmission (e.g., for one or more TBs) in a circular buffer 405 (e.g., stored in the memory of the wireless communication device). The circular buffer 405 can store information bits 410 (sometimes referred to as system bits) and parity bits 415 (sometimes referred to as parity check bits). Information bits 410 can include data to be transmitted, and parity bits 415 can include linear combinations of that data (e.g., of information bits 410). The wireless communication device can encode information bits 410, parity bits 415, or combinations of information bits 410 and parity bits 415 into a set of coded bits, and can transmit that set of coded bits. The given bits selected to be included in the set of coded bits used for the repeat can depend on the RV of the repeat (or can be defined by the RV).

[0090] As an example, the start bit positions can be defined by Table 440, such as for NRHARQ using low-density parity-check (LDPC) codes. Table 440 defines the start bit positions in the circular buffer 405 for a first basemap (BG1) and a second basemap (BG2). The basemap is a parameter used to determine the parity bits 415 used for transmission, at least in part, based on the TB size and the code rate (where BG1 is intended for TBs with a larger TB size, and BG2 is intended for TBs with a smaller TB size). Referring to this table, N cb This indicates the length of the circular buffer 405 (e.g., the number of bits included in the circular buffer 405), and Z c The lift size is indicated by the number of information bits 410 and the number of base map (BG) columns corresponding to the information bits 410.

[0091] For channel coding in wireless communication, wireless communication devices can perform multiple logical processes for TB, such as segmentation and / or cyclic redundancy check (CRC) concatenation, etc. In some examples, after preparing symbols / bits for coding, bits can be provided for sub-block interleaving 455a-c, bit collection 460, and bit selection 465 (e.g., as an intermediate process in physical layer processes). The turbo encoder can execute logic to generate / output information bits 410 (e.g., system bits), first parity bit 445, and second parity bit 450. These bits can withstand FEC mechanisms. First parity bit 445 and second parity bit 450 are provided as examples of parity bit 415. In some examples, the coding operation may include comparison... Figure 4 The parity bit depicted has more or fewer parity bits.

[0092] Wireless communication devices can generate data streams for corresponding sub-block interleavers. For example, a turbo encoder can output three separate data streams for sub-block interleaving 455a-c. After information bits 410 and parity bits (e.g., first parity bit 445 and second parity bit 450) are interleaved respectively, these bits can be received by a circular buffer 405 based on first providing all information bits 410 to the circular buffer 405, and then providing the first parity bit 445 and the second parity bit 450 to the circular buffer 405 in an alternating manner. For example, information bits 410 can be first provided to the circular buffer 405 based on scheme [S1, S2, …, Sk], followed by parity bits based on scheme [P1(1), P1(2), P2(1), P2(2), …, Pk(1), Pk(2)], such that the parity bits provided to the circular buffer 405 alternate between the first parity bit 445 and the second parity bit 450. Each data stream in the individually interleaved data stream can be held in a circular buffer 405 from which data can be retrieved for transmission.

[0093] The HARQ procedure can be used for packet transmission in the physical layer. More specifically, if a NACK is received in response to a packet transmission, the HARQ procedure can provide faster retransmission of packets compared to secondary retransmission. Repeated retransmission of the same packet can be referred to as append merging. When different patterns of transmitted bits are used for decoding previous symbols, this process can be referred to as incremental redundancy. For incremental redundancy, symbols (e.g., Physical Downlink Shared Channel (PDSCH) symbols) can be discarded without relying on unsuccessful decoding (e.g., by the UE 120 receiving the symbol). Symbols with the same HARQ bits can be retained for symbol recovery via FEC overlay. Therefore, the circular buffer 405 can provide enhanced performance with low implementation complexity.

[0094] Bit selection 465 can be used to extract consecutive bits from the circular buffer 405 to match the number of bits corresponding to a transmitted resource block (RB). For example, when scheduling downlink communication, a specific number of RBs, bits, and / or modulation characteristics can be assigned to the downlink communication. The number of bits that can be included in the corresponding resource allocation can then be selected and transmitted from the circular buffer 405. The exact set of bits to be extracted for transmission can depend on the RV, which can further depend on different starting positions from the circular buffer 405. For example, the bits selected from the circular buffer 405 can depend on the RV transmitted at that point in time (e.g., RV 0 and RV 1 can start and end at different positions associated with the circular buffer 405, respectively).

[0095] In some examples, the transmission of a TB may be based on four different RVs, which may correspond to RV 0 420, RV 1 425, RV 2 430, and RV 3 435. During transmission, the RVs may be selected by the scheduler and provided to the receiver based on signaling or a predefined sequence. The transmitted RVs may be configurable and / or dynamic. For example, UE 120 may execute commands for transmission in the uplink, but in the downlink, network node 110 may override these commands even if network node 110 executes a similar technique to UE 120. An example RV model may be associated with a sequence of RV 0, RV 2, RV 3, RV 1 (e.g., in this order). After transmitting RV 1, there may not be another RV for the TB, allowing the transmission of the next TB to be performed after RV 1. In some examples, the sequence for the RV model may be controlled by network node 110 via downlink control information (DCI).

[0096] If RV 0 is received in the downlink and the UE does not successfully decode the associated code block / symbol, the UE 120 may indicate a NACK to the network in the uplink. If RV 0 is not successfully received and / or decoded (e.g., HARQMAC TB 0 is sent but RV 0 is undetermined), the UE 120 may not be able to decode any subsequent RVs after RV 0 (e.g., for that HARQ process and / or for that TB). In other words, if RV 0 is not decoded in the downlink (e.g., due to a failed Physical Downlink Control Channel (PDCCH) that may not be scheduled for decoding, or due to tuning outage, Block Error Rate (BLER), and / or Connection Mode Discontinuous Receive (CDRX) configuration failure), the UE 120 may not indicate a HARQ feedback in the uplink, and the network may assume a DTX. More specifically, if the UE 120 does not provide an ACK or NACK, the network node 110 may determine that a DTX has occurred. In an example where UE 120 decodes the PDCCH but fails to decode the PDSCH, the PDSCH symbol can be retained for recovery techniques. If UE 120 fails to recover the PDSCH symbol, UE 120 can send a NACK. For both NACK / DTX scenarios, network node 110 can use other redundant versions (e.g., RV 2, RV 3, RV 1) in subsequent downlink transmissions to retransmit the MAC TB, thereby increasing the FEC opportunity to achieve HARQ-level recovery at the receiver.

[0097] If UE 120 completely omits RV 0 in the downlink (e.g., RV 0 is lost), even if other RVs (e.g., RV 2, RV 3, RV 1) are successfully decoded, UE 120 may still be unable to reliably decode the complete MAC TB due to the loss of information bit 410 in RV 0. Therefore, even if RV 0 can be recovered in some cases, UE 120 may abort the HARQ retransmission logic when RV 0 is determined to be lost based on configuration information. For example, after RV 0 is lost, it may be impractical for UE 120 and network node 110 to continue decoding / scheduling subsequent HARQ retransmissions for the MAC TB. In addition, continuing to perform such a process may lead to wasted resources in subsequent retransmissions, which reduces the overall capacity of the physical layer and / or causes delayed transmission of subsequent data from the MAC in subsequent instances of the HARQ process.

[0098] For example, RV 0 may include information associated with decoding a transmission (e.g., TB). For example, RV 0 may include an indication of the MCS associated with the TB (e.g., sometimes referred to as an "explicit" MCS), an indication of the RB allocation within a bandwidth or bandwidth portion (BWP) (e.g., may include an indication of the PRB associated with the TB), and / or other information associated with decoding the transmission. Other RVs (e.g., RV 1, RV 2, and / or RV 3) may not include information associated with decoding the transmission. For example, other RVs may indicate a reserved MCS. A "reserved MCS" refers to an MCS (or MCS index) that indicates a previously indicated (e.g., indicated via RV 0) MCS will be used to decode the transmission. For example, RV 1 may include a reserved MCS that indicates that RV 1 will be decoded using a previously indicated (e.g., indicated by RV 0) MCS. This can reduce the size of other RVs (e.g., those that include a reserved MCS), because a reserved MCS can have a smaller size (e.g., fewer bits can be used) than an indication of an MCS (e.g., an explicit MCS). However, if the receiver (e.g., UE 120 or network node 110) does not receive an RV that includes an indication of an MCS (e.g., RV 0), the receiver may be unable to decode subsequent RVs (e.g., even if subsequent RVs are received by the receiver), because the receiver may not know which MCS to use to decode the subsequent RVs.

[0099] In some examples, when the UE determines that RV 0 is lost for a given HARQ procedure or process, the UE can abort the HARQ retransmission request by indicating an ACK indication to network node 110. Such an ACK indication may be referred to as a “forced” ACK indication. A forced ACK indication allows network node 110 to continue with the next HARQ procedure to send the next MAC TB. In some aspects, if UE 120 is configured using RLC ARQ mode, the next HARQ procedure can be performed while recovering lost information used for the previous HARQ via RLC-level Automatic Repeat Request (ARQ). RLC can request packet retransmission at the RLC level, which reduces latency compared to waiting for MAC recovery. For certain decoding rates at the MAC TB level, UE 120 may be able to recover successfully. UE 120 can determine where a forced ACK can be provided to the network in the uplink based on the decoding rate, physical characteristics, and / or information indicated via DCI (e.g., MCS, RV instance, or other information).

[0100] When subsequent retransmissions (such as RV 2, RV 3, and RV 1) use a reserved MCS (e.g., when RV 0 is lost and the MCS is indicated by network node 110 via RV 0), UE 120 may send a forced ACK indication. For example, the MCS may be indicated to UE 120 based on the transmission of RV 0, and the MCS may not be re-indicated to UE 120 at the time of transmission of RV 2, RV 3, or RV 1. Instead, subsequent RVs may be associated with a reserved MCS that corresponds to the same MCS used for RV 0. However, if RV 0 is lost, UE 120 may not be able to determine the MCS used to decode RV 2, RV 3, and RV 1. Therefore, even if UE 120 successfully receives RV 2, RV 3, and / or RV 1, UE 120 may not have enough information to use the MCS for retransmission based on the failed decoding identifier of RV 0. Therefore, a decoding error in the initial transmission corresponding to RV 0 may prevent UE120 from decoding the remaining RV.

[0101] Even when successful retransmissions of RV 2, RV 3, and RV 1 are associated with the determined MCS, UE 120 may still be unable to decode the retransmissions due to the decoding rate. For example, the initial transmission may indicate MCS 15, and the retransmission may indicate a different MCS (e.g., MCS 10 or MCS 8), such that the retransmission includes the determined MCS. In such cases, there may not be a sufficient number of parity bits to perform decoding because the number of bits corresponding to different MCSs is reduced. Therefore, in some respects, successful decoding can depend on the code rate. A low decoding rate can provide an increased probability of successful decoding based on an increased number of parity bits, while a high decoding rate can provide a decreased probability of successful decoding based on a decreased number of parity bits. High decoding rates and additional delays can be avoided when the UE operates at or near its peak operating rate.

[0102] A lower decoding rate corresponds to more redundant bits in the channel decoding process, while a higher decoding rate corresponds to fewer redundant bits. In the example based on 16 HARQs, excessive retransmissions can delay the next transmission. For a full schedule that assumes each slot is scheduled consecutively, the next transmission / next MAC TB can be delayed by 32 slots (e.g., 16 HARQs × 2 wasted / excessive retransmissions). For a sparse schedule, 10% of the schedule can be allocated to the UE, where the next transmission / next MAC TB can be delayed by 320 slots (e.g., for every 10 slots, 16 HARQs × 2 wasted / excessive retransmissions per slot).

[0103] Layer 2 logic can be improved by reducing the time spent receiving the next MAC TB. Considering that the HARQ process may abruptly end in some cases, indicating an RLC PDU loss to the RLC can reduce latency of ARQ mechanisms or other fast NACK mechanisms. Some configurations can pause so that previous HARQs complete before triggering a retransmission. Therefore, the amount of time memory buffers are maintained at the MAC level can be reduced, which improves various aspects associated with memory management.

[0104] In some examples, when RV 0 is lost, network node 110 may assume DTX because no ACK / NACK for RV 0 is received from UE 120. However, if RV 2 is received by UE 120 but not as expected (e.g., because UE 120 did not successfully receive RV 0), retransmission of RV 3 and RV 1 may not be necessary because UE 120 may not be able to decode RV 3 and RV 1. Instead, UE 120 may send a forced ACK to network node 110, allowing the transmission / reception of the next MAC TB to proceed without any further delay from any remaining retransmissions of a given MAC TB. This reduces the delay between the time RV 0 is lost and the time the next MAC TB is received. In some examples, if one or more other RVs of the HARQ will be received before RV 0 is received, a forced ACK may not be sent until after the expected time for RV 0 (e.g., after RV 0 is lost).

[0105] However, in some cases, if network node 110 detects that the number of NACK indications associated with the HARQ process meets a threshold, network node 110 may fall back to retransmitting information associated with decoding the TB, such as indications for MCS and / or PRB allocation. For example, if network node 110 detects DTX and determines that the number of NACK indications associated with the HARQ process meets a threshold, network node 110 may fall back to retransmitting RV 0 (or another RV with information for decoding the TB). For example, network node 110 may send RV 0. UE 120 may fail to detect, decode, or otherwise receive RV 0. Network node 110 may send RV 2 with a reserved MCS, which can be received by UE 120. However, because UE 120 cannot decode RV 2, UE 120 may send a NACK (e.g., a HARQ NACK), and network node 110 may receive this NACK. UE 120 may continue sending NACKs for subsequent RV reception. Network node 110 can determine that the number of NACK indications meets a threshold. Therefore, network node 110 can send an RV (e.g., RV 0 or another RV) that includes information associated with decoding the RV (e.g., MCS and / or PRB allocation). This allows UE 120 and / or network node 110 to resume the HARQ process and decode the TB without requiring RLC-level retransmission. Enabling the reception of the HARQ process and / or reducing the likelihood of RLC retransmissions can reduce latency and save resources associated with receiving the TB.

[0106] However, UE 120 may not receive indications of HARQ operation or configuration at network node 110. For example, UE 120 may not know whether network node 110 is configured to fall back to retransmitting indications for MCS and / or other information after a given number of NACK indications. Therefore, in some cases, UE 120 may not send a forced ACK, and network node 110 may not be configured to fall back to retransmitting indications for MCS and / or other information after a given number of NACK indications, resulting in resource consumption associated with transmitting RVs that the UE cannot decode. In other examples, UE 120 may send a forced ACK, and the network node may be configured to fall back to retransmitting indications for MCS and / or other information after a given number of NACK indications. However, UE 120 may send a forced ACK before a given number of NACK indications are sent, resulting in a retransmission of RLC for TB, which might have been received and / or resumed during the HARQ process.

[0107] As indicated above, Figure 4 This is provided as an example. Other examples are available relative to... Figure 4 The examples described are different.

[0108] Figure 5A and Figure 5B This is a diagram illustrating an example 500 related to the adaptation for HARQ retransmission processing according to this disclosure. (See diagram 500 for example ... Figure 5A and Figure 5B As shown, one or more network nodes 110 (e.g., base stations, CUs, DUs, and / or RUs) can communicate with UE 120. In some aspects, network node 110 and UE 120 can be part of a wireless network (e.g., wireless network 100). UE 120 and network node 110 can... Figure 5A and Figure 5B The operation shown has been performed after a wireless connection has been established.

[0109] In Example 500, for one or more HARQ processes, UE 120 can be a receiver and network node 110 can be a transmitter. However, in other examples, in a manner similar to that described herein, for a HARQ process, UE 120 can be a transmitter and network node 110 can be a receiver. For example, if UE 120 is a transmitter and network node 110 is a receiver, then network node 110 can perform one or more operations described herein as being performed by UE 120 (e.g., for adapting HARQ operations). Additionally or alternatively, if UE 120 is a transmitter and network node 110 is a receiver, then UE 120 can perform one or more operations described herein as being performed by network node 110 (e.g., for adapting HARQ operations).

[0110] In some aspects, such as Figure 5A As shown and as indicated by reference numeral 505 in the attached figure, UE 120 can send a capability report, and network node 110 can receive the capability report. UE 120 can send the capability report via uplink communication, UE Assistive Information (UAI) communication, uplink control information (UCI) communication, uplink MAC control element (MAC-CE) communication, RRC communication, physical uplink control channel (PUCCH) and / or PUSCH, etc. The capability report can indicate one or more parameters associated with the corresponding capability of UE 120. One or more parameters can be indicated via the corresponding information element (IE) included in the capability report.

[0111] A capability report may indicate whether a UE supports a feature and / or one or more parameters associated with that feature. For example, a capability report may indicate the capabilities and / or parameters used to adapt the HARQ operation of UE 120 (e.g., information based on the HARQ operation of network node 110). As another example, a capability report may indicate the capabilities and / or parameters used to adapt the forced ACK operation of UE 120 to information based on the HARQ operation of network node 110. One or more operations described herein may be based on the capability information in the capability report. For example, a UE may perform communication based on the capability information, or may receive configuration information based on the capability information. In some aspects, a capability report may indicate that the UE supports the timing of the transmission of a forced ACK indication based on whether network node 110 is configured to retransmit decoded information (e.g., MCS, PRB allocation, or other decoded information) during a given HARQ process, as described in more detail elsewhere herein.

[0112] The capability report may indicate (e.g., sent by UE 120 for a given HARQ process) how several NACK indications should cause UE 120 to perform a forced ACK operation, as described in more detail elsewhere herein. Network node 110 may use the indication of the number of NACK indications to determine when to provide a retransmission of decoding information for a given HARQ process. In some aspects, UE 120 may send the capability report in response to a request from network node 110. For example, network node 110 may send a request for UE capabilities, and UE 120 may receive that request. UE 120 may then send the capability report in response to that request.

[0113] In some respects, the capability report can instruct UE 120 to support HARQ feedback indicating that control information or decoding information for a given HARQ process was missing. For example, UE 120 can send feedback indicating that it was received but could not be decoded because UE 120 did not receive the decoding information, instead of ACK or NACK. This HARQ feedback can enable network node 110 to retransmit the decoding information for the control information of a given HARQ process.

[0114] As shown by reference numeral 510 in the attached figure, network node 110 can send configuration information, and UE 120 can receive the configuration information. In some aspects, UE 120 can receive the configuration information via one or more of the following: system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB)), RRC signaling, one or more MAC-CEs and / or DCIs, etc.

[0115] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, these one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC-CE and / or one or more DCI messages, etc.

[0116] In some aspects, the configuration information may include HARQ configuration (e.g., HARQ process configuration). For example, the configuration information may indicate the number of HARQ processes and / or one or more configuration parameters for the HARQ processes. In some aspects, the configuration information may indicate whether the HARQ operation of network node 110 includes: retransmitting instructions for decoded information (e.g., MCS and / or PRB allocation) before the end of each HARQ process. For example, the configuration information may indicate whether the HARQ operation of network node 110 includes: NACK-based retransmission of MCS during a given HARQ process. For example, network node 110 may be configured to retransmit decoded information during the same HARQ process based on, in response to, or otherwise associated with network node 110 receiving a number of NACK instructions that meet a threshold (and / or based on detecting that DTX has occurred). For example, network node 110 may be configured to fall back to sending RV 0 based on, in response to, or otherwise associated with network node 110 receiving a number of NACK instructions that meet a threshold. For example, network node 110 may be configured to fall back to sending RV0 based on, in response to, or otherwise associated with HARQ feedback indicating that control information or decoding information for a given HARQ process was omitted. Configuration information may instruct network node 110 to support such operation. Additionally, configuration information may indicate one or more parameters for NACK-based retransmission. For example, configuration information may indicate the value of a threshold.

[0117] In some respects, the configuration information may instruct UE 120 to adapt its HARQ operations based on, in response to, or otherwise associated with HARQ operations of network node 110. For example, the configuration information may instruct UE 120 to analyze (e.g., “learn”) HARQ operations of network node 110 and adapt UE 120’s forced ACK operations based on or otherwise associated with HARQ operations of network node 110, as described in more detail elsewhere herein.

[0118] UE 120 can configure itself at least in part based on configuration information. In some respects, UE 120 can be configured to perform one or more of the operations described herein, at least in part based on configuration information.

[0119] In some aspects, the configuration information and / or capability report described in conjunction with reference to reference numeral 510 may include information transmitted via multiple communications. Additionally or alternatively, the network node may transmit the configuration information or communications including at least a portion of the configuration information before and / or after the UE transmits the capability report. For example, the network node may transmit a first portion of the configuration information before the capability report, the UE may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0120] UE 120 may operate in a learning phase or learning mode associated with analyzing and / or determining information related to HARQ operations associated with network node 110. During the learning phase or learning mode, UE 120 may avoid sending a forced ACK indication. For example, as shown by reference numeral 515, UE 120 may execute one or more HARQ processes (or HARQ procedures) together with network node 110. UE 120 may (e.g., without sending a forced ACK indication) execute one or more HARQ processes as configured by network node 110. For example, UE 120 may execute one or more HARQ processes as defined by wireless communication standards (such as 3GPP) or otherwise fixed. In some aspects, UE 120 may disable (or avoid executing) forced ACK operations while executing one or more HARQ processes. For example, network node 110 may send one or more RVs of TB (e.g., MAC TB), and UE 120 may receive the one or more RVs. UE 120 may send feedback information (e.g., HARQ ACK indication and / or HARQ NACK indication) based on whether the corresponding RV is successfully received and / or decoded by UE 120.

[0121] UE 120 may obtain HARQ information associated with HARQ operations of network node 110 by performing one or more HARQ procedures together with network node 110. As used herein, “HARQ information” may refer to information associated with one or more HARQ operations of a transmitter (such as network node 110). For example, HARQ information may indicate whether the HARQ operation of network node 110 includes a retransmission of indications for all decoding information for the HARQ process prior to the end of the HARQ process associated with network node 110. All decoding information required for the HARQ process may be referred to herein as “complete decoding information”. Complete decoding information may include MCS, RB allocation, MIMO layer and / or process identifier, etc. In other words, HARQ information may indicate whether network node 110 is configured to perform MCS and RB allocation during a given HARQ procedure, for example, based on receiving a NACK (i.e., a retransmission based on NACK) or based on receiving HARQ feedback indicating that control information or decoding information for a given HARQ process was omitted.

[0122] In some respects, UE 120 may obtain HARQ information via an AI / ML model. For example, UE 120 may provide information associated with HARQ operations of network node 110 (e.g., information obtained by executing one or more HARQ procedures) as input to the AI / ML model. UE 120 may obtain HARQ information as output from the AI / ML model. The AI / ML model may be deployed at UE 120, network node 110, another device (e.g., at a server or via a cloud-based device), and / or deployed in a distributed manner.

[0123] As shown by reference numeral 520, UE 120 can determine whether the HARQ operation of network node 110 includes the retransmission of all decoding information required during a given HARQ process or a given HARQ procedure. For example, UE 120 can determine whether, during one or more HARQ procedures (e.g., as depicted and described in conjunction with reference numeral 515), UE 120 receives a retransmission of decoding information during a given HARQ process or a given HARQ procedure. Complete decoding information may include MCS (e.g., explicit MCS), PRB allocation, and / or other information used by UE 120 to decode the RV of TB during a given HARQ process or a given HARQ procedure. For example, UE 120 can determine whether network node 110 sends a retransmission of RV 0 (or another RV) during a given HARQ process or a given HARQ procedure and whether UE 120 receives that retransmission.

[0124] In some respects, the HARQ information obtained by UE 120 can indicate a scheduling pattern associated with the HARQ operation of network node 110. For example, the scheduling pattern can indicate whether and / or when network node 110 is configured to retransmit decoded information during a given HARQ process or a given HARQ procedure. For example, network node 110 can be configured to receive [decoded information] during a given HARQ procedure. K Following a NACK indication, a retransmission of the decoded information is sent during a given HARQ procedure. The HARQ information obtained by UE 120 can indicate whether network node 110 should retransmit the decoded information during a given HARQ procedure. Additionally, the HARQ information obtained by UE 120 can indicate the number of NACK indications that trigger the retransmission of the decoded information (e.g., K For example, the scheduling pattern may indicate the number of NACK indications (e.g., causing network node 110 to retransmit decoded information during a given HARQ procedure, or causing network node 110 to fall back to sending RV 0 or another RV including decoded information) K Configuration () KThis can be specific to carrier ID, channel condition range, shared channel (SCH) spectral efficiency, signal-to-noise ratio (SNR), MCS, and / or one or more PDCCH parameters (such as aggregation factor or beam parameters), etc. This ensures K Suitable for a given channel. For example, if PDCCH loss is less likely than PDSCH decoding failure, then... K The chosen value may be higher. If the PDCCH channel is indicated as unreliable, then K The value may be larger.

[0125] For example, as shown by reference numeral 525, UE 120 can determine the number of NACK indications that trigger the retransmission of decoded information during a given HARQ procedure. For example, UE 120 can obtain HARQ information for one or more HARQ procedures and / or one or more HARQ processes. UE 120 can identify one or more HARQ procedures during which UE 120 sends one or more NACK indications. UE 120 can identify the number of NACK indications for one or more HARQ procedures during which UE 120 sends one or more NACK indications, after which network node 110 sends a retransmission of decoded information. For example, UE 120 can identify the number of NACK communications for HARQ operations between the initial retransmission of a TB with reserved MCS() and the retransmission of indications for all necessary information for decoding a SCH including MCS(). This allows UE 120 to identify the scheduling pattern of HARQ operations at network node 110. UE 120 may adapt or adjust its forced ACK operation based on, in response to, or otherwise associated with a scheduling style.

[0126] For example, as shown by reference numeral 530 in the attached figure, UE 120 can adapt its HARQ operation. For example, UE 120 can adapt its forced ACK operation based on the HARQ information obtained by UE 120. For example, if the HARQ information indicates that the HARQ operation of network node 110 does not include the retransmission of the indication to the MCS before the end of each HARQ process (e.g., based on the number of NACK indications meeting a threshold), then when no previous complete decoded information including the MCS has been received, UE 120 can adapt its forced ACK operation so that UE 120 sends a forced ACK after receiving the DCI indicating the reserved MCS. In other words, if network node 110 is not configured to fall back to retransmitting the complete decoded information, including the MCS, during a given HARQ process or procedure, UE 120 may configure its HARQ operation to send a forced ACK communication based on the detection of a DCI that includes partial decoded information insufficient to decode the shared channel, or the detection that an RV0 in a given HARQ process or procedure is lost or not successfully received. For example, if the learning phase does not indicate or suggest that network node 110 falls back to sending decoded information during a given HARQ procedure, UE 120 may adapt its HARQ operation to send a forced ACK communication based on, in response to, or otherwise associated with the detection of a lost or unsuccessfully received RV0 (or another RV that includes or indicates decoded information).

[0127] For example, if the HARQ information indicates that the HARQ operation of network node 110 does indeed include retransmission of fully decoded information before the end of each HARQ process (e.g., based on the number of NACK indications meeting a threshold, or other methods), then UE 120 can adapt a forced ACK operation so that UE 120 only sends a forced ACK after UE 120 has already sent that number of NACK indications. For example, UE 120 can adapt its forced ACK operation so that UE 120 only sends a forced ACK after sending that number of NACK indications. K A forced ACK communication is sent after a NACK indication (e.g., if the next HARQ control message does not include decoding information, then after sending...). K A forced ACK communication is sent in response to the next HARQ retransmission after a NACK indication. For example, if the learning phase indication is in... K After the HARQ retransmission, if network node 110 is falling back to sending complete decoded information, UE 120 can adapt or modify its forced ACK operation to only apply it to a given cell associated with (or supported by) network node 110. K A forced ACK communication is sent only after the HARQ retransmission.

[0128] Additionally or alternatively, the adaptation of the forced ACK operation may be based on one or more communication parameters indicated during the learning phase or via configuration from network node 110. One or more communication parameters may include MCS, throughput, CQI, channel state information (CSI) parameters, and / or another communication parameter. For example, HARQ information may indicate one or more indices of the MCS used for one or more HARQ processes. UE 120 may determine whether one or more indices satisfy an MCS threshold (e.g., indicating a high MCS). For example, if one or more indices satisfy the MCS threshold, UE 120 may adapt the forced ACK operation so that UE 120 sends a forced ACK after receiving the RV of the TB using the reserved MCS and before receiving the RV of the TB indicating the MCS. For example, in the case of a high MCS and no RV 0, the number of lost information bits may be so large that HARQ retransmission may not result in successful decoding of the TB. Therefore, UE 120 may send forced ACK communication for a higher MCS because decoding operations for the TB may not succeed in the case of limited retransmissions. MCS-based adaptation can explore how many retransmissions were performed by network node 110 for a given MCS and / or HARQ failure pattern (e.g., the actions taken by network node 110 in response to a HARQ failure). For example, HARQ information can indicate the number of retransmissions typically performed by network node 110 for a given MCS.

[0129] Additionally or alternatively, UE 120 may determine the throughput associated with the communication link between UE 120 and network node 110. The throughput may be downlink throughput. For example, UE 120 may determine whether the throughput meets a throughput threshold. If the downlink throughput meets the throughput threshold, one or more actions performed by UE 120 (e.g., as described in more detail elsewhere herein) may cause the UE to terminate the HARQ process in the absence of received decoding information (e.g., in the case of RV 0 loss). If the downlink throughput does not meet the throughput threshold, one or more actions performed by UE 120 (e.g., as described in more detail elsewhere herein) may cause the UE to continue the HARQ process even without received decoding information (e.g., if RV 0 is lost), such as by following procedures or operations defined by the wireless communication standard for the HARQ process. For example, if the downlink throughput does not meet the throughput threshold, UE 120 may disable (or avoid performing) forced ACK operations. If the downlink throughput meets the throughput threshold, UE 120 may perform a forced ACK operation and / or adapt to a forced ACK operation, as described elsewhere in this document. Alternatively, UE 120 may adapt the forced ACK operation based on the service and / or application performed on UE 120. For example, for services or applications associated with low latency and / or high reliability, UE 120 may adapt the forced ACK operation to have a higher value than the threshold that would cause UE 120 to send a forced ACK (e.g., increasing the likelihood of a successful HARQ operation). For example, for voice (e.g., with RLC unacknowledged mode (UM) configured), UE 120 may use a higher value than the threshold for forced ACK (e.g., increasing the likelihood of a successful HARQ operation). K This increases the chances of a successful HARQ operation.

[0130] like Figure 5B As shown and as indicated by reference numeral 535 in the accompanying drawings, network node 110 may transmit a redundant version of the information for downlink communication (e.g., a TB for downlink communication). For example, network node 110 may transmit a DCI indicating complete decoding information for the HARQ process. In some aspects, RV may include decoding information for the TB. In some aspects, network node 110 may transmit RV 0 for the MAC TB. UE 120 may not successfully receive the complete decoding information. For example, RV 0 may be lost and / or not received by UE 120.

[0131] As shown by reference numeral 540, network node 110 can determine that a DTX has occurred based on the absence of an ACK or NACK received in response to a transmission associated with RV 0 for MAC TB. For example, because UE 120 has not received and / or detected RV0, UE 120 may not send HARQ feedback information for RV0. Because network node 110 has not received HARQ feedback information for RV0, network node 110 can detect or determine that a DTX has occurred. Therefore, as shown by reference numeral 540, network node 110 may send a different RV (such as RV 2) for MAC TB. UE 120 may receive and / or detect a different RV (e.g., RV 2) for MAC TB.

[0132] As shown by reference numeral 550 in the accompanying figure, UE 120 may determine that complete decoding information is lost or has not been successfully received based on receiving different RVs (e.g., RV 2). UE 120 may determine (e.g., detect) decoding errors in the PDCCH associated with MAC TB. In some aspects, UE 120 may determine that complete decoding information (e.g., MCS and / or PRB allocation, or other decoding information) has not been successfully received for MAC TB. For example, RV 2 may be received unexpectedly by UE 120, which may have expected to receive RV 0 from network node 110. For example, different RVs (e.g., RV 2) may not be provided with complete decoding information for MAC TB. UE 120 may expect the first RV received for a given MAC TB to include complete decoding information (e.g., MCS, PRB allocation, and / or other decoding information) for that MAC TB. If the first RV received for a given MAC TB (e.g., for a given HARQ process) includes a reserved MCS (e.g., excluding decoding information), then UE 120 can determine that the RV carrying the decoding information is lost (e.g., not successfully detected or received by UE 120).

[0133] In some aspects, as indicated by reference numeral 555, UE 120 may send one or more NACK communications for a corresponding RV associated with the MAC TB, and network node 110 may receive such one or more NACK communications. For example, network node 110 may send one or more RVs (e.g., RV 2, RV 1, or RV 3) that are not provided with complete decoding information, and UE 120 may receive such one or more RVs. Because UE 120 has not yet received the decoding information for the MAC TB, UE 120 may not be able to decode one or more RVs. Therefore, UE 120 may send one or more NACK communications for a corresponding RV among the one or more RVs. In some aspects, UE 120 may send one or more NACK communications based on HARQ information indicating that the HARQ operation of network node 110 does indeed include retransmission of the indication to the MCS before the end of each HARQ process (e.g., based on the number of NACK indications meeting a threshold). For example, as described elsewhere in this document, the forced ACK operation of UE 120 can be adapted or modified to send a forced ACK communication only after a given number of NACK communications and / or after a given number of retransmissions of RV or MAC TB. Alternatively, UE 120 may send HARQ feedback indicating that complete decoding information for the HARQ process has not been received.

[0134] As shown by reference numeral 560 in the attached figure, UE 120 may determine whether to terminate retransmissions associated with the remaining RV of MAC TB (e.g., based on determining complete decoding information and / or the loss of RV 0). The determination to terminate retransmissions associated with the remaining RV may be based on the fact that UE 120 is unable to decode the remaining RV due to unreceived decoding information included in the lost transmission. For example, if the lost RV transmission indicates complete decoding information (e.g., MCS and / or PRB allocation), and subsequent HARQ retransmissions (such as RV 2, RV 3, and / or RV 1) indicate a reserved MCS (e.g., MCS 31 or another reserved MCS as defined by a wireless communication standard (such as 3GPP) or otherwise fixed), UE 120 may be unable to decode subsequent HARQ retransmissions based on the reserved MCS, which indicates that UE 120 will reuse the decoding information (e.g., MCS) indicated by RV 0 (e.g., its loss) to decode the HARQ retransmission.

[0135] UE 120 may determine whether to terminate retransmissions associated with the remaining RV of MAC TB based on the HARQ information obtained by UE 120 (e.g., in combination with...). Figure 5A(As described). For example, UE 120 may determine whether to terminate retransmissions associated with the remaining RVs of the MAC TB based on whether network node 110 is configured to retransmit decoded information (e.g., MCS and / or PRB allocation) during a given HARQ process or HARQ process. For example, if the HARQ information indicates that network node 110 is not configured to perform retransmissions of the MCS (e.g., decoded information) before the end of a given HARQ process (e.g., based on the number of NACK indications during a given HARQ process), then UE 120 may perform one or more actions to terminate the HARQ process. For example, if the HARQ information indicates that network node 110 (e.g., based on the number of NACK indications during a given HARQ process) is not configured to perform retransmissions of the MCS (e.g., decoded information) before the end of a given HARQ process, then UE 120 may determine to terminate retransmissions associated with the remaining RVs of the MAC TB.

[0136] If the HARQ information instructs network node 110 (e.g., based on the number of NACK indications during a given HARQ process) to perform a retransmission of the MCS (e.g., decoded information) before the end of a given HARQ process, UE 120 may perform one or more actions to continue the HARQ process. For example, if the HARQ information instructs network node 110 (e.g., based on the number of NACK indications during a given HARQ process) to perform a retransmission of the MCS (e.g., decoded information) before the end of a given HARQ process, UE 120 may determine not to terminate retransmissions associated with the remaining RV of the MAC TB (e.g., because one or more retransmissions may include decoded information to enable UE 120 to decode the MAC TB). For example, as described elsewhere herein, UE 120 may adapt its forced ACK operation to send forced ACK communication only after a given number of received retransmissions and / or a given number of sent NACK indications.

[0137] For example, as shown by reference numeral 565, network node 110 may determine that the number of NACKs for the HARQ process associated with MAC TB (e.g., the number of NACK indications sent by UE 120 and / or received by network node 110) meets a threshold. For example, as described elsewhere herein, UE 120 may adapt its HARQ operation to not terminate the HARQ process in response to determining that decoding information (e.g., RV0) for the HARQ process is lost (e.g., based on network node 110 being configured to retransmit indications to the decoding information, as indicated by the HARQ information, before the HARQ process ends). Therefore, as shown by reference numeral 555, UE 120 may send a NACK indication (also referred to as NACK communication) for the corresponding retransmission (e.g., the corresponding RV) sent by network node 110 for MAC TB. Network node 110 may determine that the number of NACK indications meets a threshold. Alternatively, network node 110 may receive HARQ feedback indicating that complete decoding information for the HARQ process has not been received, and network node 110 (e.g., in response to receiving HARQ feedback) performs a similar action as described above. Network node 110 retransmitting the indication for complete decoding information in response to receiving HARQ feedback indicating that complete decoding information for the HARQ process has not been received (e.g., the complete decoding information is unavailable) may be referred to herein as “restarting” the HARQ process. For example, receiving HARQ feedback communication indicating that complete decoding information for the TB is unavailable may cause network node 110 to “restart” the HARQ process by sending a retransmission of the complete decoding information (e.g., via DCI and / or RV of the TB).

[0138] Therefore, as shown by reference numeral 570, network node 110 may transmit a retransmission of the MAC TB (e.g., transmit RV), which includes decoding information associated with the MAC TB. Additionally, network node 110 may fall back to transmitting RV 0 based on a threshold satisfied by the number of NACK indications for the HARQ process. As shown by reference numeral 575, UE 120 may obtain the TB (e.g., the MAC TB) based on decoding information (e.g., based on received decoding information). For example, UE 120 may obtain decoding information retransmitted by network node 110 (e.g., MCS and / or PRB allocation) (e.g., as shown by reference numeral 570). UE 120 may use the decoding information to decode and / or combine one or more received retransmissions to obtain the TB.

[0139] For example, UE 120 may additionally store baseband samples (e.g., in-phase (I) and quadrature (Q) (I / Q) samples) associated with one or more retransmissions of the TB (e.g., one or more retransmissions received by UE 120 before receiving decoded information) (such as one or more retransmissions as indicated by reference numeral 545) based on network node 110 being configured to perform a retransmission of the indication to the MCS before the end of each HARQ process. For example, the samples may be associated with the full bandwidth size and / or BWP size. In other words, because UE 120 has not yet received decoded information, UE 120 may not know the location of the retransmissions in the bandwidth and / or BWP. Therefore, UE 120 may store all I / Q samples for the bandwidth or BWP (e.g., for combination after UE 120 receives the retransmissions of decoded information).

[0140] UE 120 may receive another RV for the TB, which includes a retransmission of an indication of the decoded information (e.g., as shown by reference numeral 570). UE 120 may obtain the TB based on the decoded information, the other RV, and the retransmission of the TB. For example, UE 120 may extract relevant information from stored I / Q samples based on the PRB allocation indicated by the decoded information. UE 120 may use the extracted I / Q samples, MCS, and / or any other received RV or retransmission to obtain the TB (e.g., using soft combining). Network node 110 may transmit a DCI including complete decoded information for the current transmission and for previous transmissions, and UE 120 may receive the DCI. For example, network node 110 may determine one or more RVs that have been transmitted for a given HARQ process and / or for a given TB. Network node 110 may determine the complete decoded information based on the transmitted RVs. For example, the first transmission may be RV 0 for the TB, and the previous transmission may be RV 1 for the TB. UE 120 may use the complete decoded information to appropriately combine the RVs. In other examples, UE 120 may assume that previously (stored) transmissions are associated with a specific RV based on a known sequence. UE 120 may also perform blind decoding under all possible RV assumptions. UE may also perform blind decoding using only the most recently received data.

[0141] In some other aspects, as indicated by reference numeral 580, UE 120 may send a forced ACK communication, and network node 110 may receive such a forced ACK communication (e.g., to terminate the HARQ process and / or terminate retransmissions associated with the HARQ process). For example, UE 120 may perform one or more actions to terminate the HARQ process. In some aspects, UE 120 may send the forced ACK operation based on (e.g., according to HARQ information) determining that network node 110 is not configured to perform or send retransmissions of decoded information during a given HARQ process or procedure. For example, UE 120 may determine that UE 120 is unable to decode the remaining RV due to the lack of received complete decoded information. Because the HARQ information indicates that network node 110 is not configured to retransmit decoded information during the HARQ process, UE 120 may send a forced ACK communication to cause network node 110 to terminate retransmissions for the HARQ process (e.g., to save resources that would otherwise be used to send transmissions or RVs that cannot be decoded by UE 120).

[0142] Additionally or alternatively, UE 120 may send a forced ACK communication based on the number of NACK indications sent for a HARQ process and / or the number of retransmissions received satisfying a termination threshold. The termination threshold may be based on HARQ information. For example, as described elsewhere herein, HARQ information may indicate the number of NACK communications between an initial retransmission of a TB with a reserved MCS and a retransmission of an indication to the MCS. In other words, HARQ information may indicate the number of NACK communications that cause (or trigger) network node 110 to retransmit decoded information during a given HARQ process. The termination threshold may be based on the number of NACK communications. For example, the termination threshold may be (e.g., may be equal to) the number of NACK communications. UE 120 may determine that the number of NACK indications sent for a HARQ process and / or the number of retransmissions received satisfy the termination threshold. Therefore, UE 120 may send a forced ACK communication for the HARQ process (e.g., to cause the HARQ process and / or retransmissions for the HARQ process to be terminated or discarded).

[0143] As shown by reference numeral 585, network node 110 can terminate retransmissions associated with the remaining RVs of the MAC TB based on receiving a forced ACK communication. As shown by reference numeral 590, network node 110 can send a different RV associated with the next MAC TB, and UE 120 can receive this different RV. Therefore, the latency associated with transitioning to a HARQ process with the next MAC TB can be reduced (e.g., because network node 110 does not send all transmissions or RVs for the HARQ process before entering the next MAC TB). This allows UE 120 to recover (e.g., associated with the terminated HARQ process) the MAC TB via one or more RLC operations (e.g., RLC retransmission). Additionally, this can improve downlink channel throughput by reducing the likelihood of the downlink channel being used for transmissions that cannot be successfully decoded by UE 120.

[0144] As indicated above, Figure 5A and Figure 5B This is provided as an example. Other examples are available relative to... Figure 5A and Figure 5B The examples described are different.

[0145] Figure 6 This is a diagram of an example process 600 associated with an adaptation to HARQ operating mode according to this disclosure. Process 600 may be executed by a receiver such as UE 120 or network node 110 (e.g., a receiver of communications associated with one or more HARQ processes).

[0146] like Figure 6 As shown, process 600 may include performing one or more learning phase operations (block 605). For example, a receiver may perform one or more learning phase operations. One or more learning phase operations may include obtaining HARQ information associated with a transmitter (e.g., a transmitter of communications associated with one or more HARQ processes, such as network node 110 or UE 120) in a manner similar to that described elsewhere herein. For example, one or more learning phase operations may include, as in combination with... Figure 5A The operations described by reference numerals 515, 520, 525 and / or 530, etc.

[0147] A receiver that performs one or more learning phase operations may be referred to as a receiver operating in “learning” mode. For example, as described elsewhere in this document, a receiver may perform one or more learning phase operations to obtain HARQ information. The receiver may use the HARQ information to determine one or more operations supported by the transmitter and / or the scheduling pattern of the HARQ process associated with the transmitter. For example, the receiver may determine whether the transmitter is configured to retransmit the complete decoded information during a given HARQ process, as described in more detail elsewhere in this document.

[0148] Process 600 may include: determining a HARQ operating mode (block 610). For example, a receiver may determine a HARQ operating mode. The receiver may determine the HARQ operating mode based on HARQ information. The HARQ operating mode may include a forced ACK mode, an adapted forced ACK mode, and / or a normal HARQ mode. A forced ACK mode may include: the receiver sending a forced ACK communication based on or in response to determining that decoded information for the HARQ process has been lost (e.g., based on determining that decoded information has not been detected by the receiver and / or successfully received). For example, a forced ACK mode may include: the receiver sending a forced ACK in response to receiving an RV including a retained MCS or a retransmission (such as RV 2) (e.g., before the receiver obtains decoded information for the HARQ process).

[0149] The adapted forced ACK mode can be associated with the adapted timing of forced ACK transmission by the receiver. For example, HARQ information (e.g., HARQ information acquired during the learning phase) can instruct the transmitter to be configured to retransmit decoded information after a given number of NACK indications during a given HARQ process. The adapted forced ACK mode can be associated with the receiver sending forced ACK communication only after a given number of NACK indications have been sent during a given HARQ process. The normal HARQ mode can be associated with the receiver performing HARQ operations as defined by wireless communication standards (such as 3GPP) or otherwise fixed. For example, the normal HARQ mode can be associated with the receiver disabling (or avoiding) forced ACK communication.

[0150] The receiver can determine the HARQ operation mode based on HARQ information. For example, the receiver can determine the HARQ operation mode based on whether the transmitter is configured to retransmit the indication of the decoded information before the end of a given HARQ process. If the HARQ information indicates that the transmitter is not configured to retransmit the indication of the decoded information before the end of a given HARQ process, the receiver can determine that the HARQ operation mode is the forced ACK mode. If the HARQ information indicates that the transmitter is configured to retransmit the indication of the decoded information before the end of a given HARQ process, the receiver can determine that the HARQ operation mode is the adapted forced ACK mode or the normal HARQ mode.

[0151] In some respects, HARQ feedback modes can be associated with a “third” HARQ feedback state (e.g., in addition to ACK and NACK HARQ feedback states). A third HARQ feedback state can be associated with lost decoded information. For example, a receiver can be configured to send HARQ feedback communication indicating that the complete decoded information for a TB is unavailable at the receiver (e.g., has not yet been received by the receiver) based on a received retransmission of the TB using a reserved MCS. A transmitter can be configured to send a retransmission of the complete decoded information in response to receiving HARQ feedback associated with a third HARQ feedback state. For example, communication based on HARQ feedback communication indicating that the complete decoded information is unavailable at the receiver can send a retransmission of the complete decoded information for the TB, and the receiver can receive this retransmission. As described elsewhere in this document, this can be referred to as “restarting” the HARQ process of the TB. The receiver can use the complete decoded information of the TB and any received retransmissions (e.g., RVs) to decode the TB (e.g., where the retransmission may be received before and / or after the complete decoded information is received).

[0152] In some respects, the receiver can determine the HARQ operating mode based on one or more communication parameters, such as MCS, downlink throughput, and / or another communication parameter. For example, if downlink communication from the transmitter is associated with a high MCS (e.g., an MCS index that meets a threshold), the receiver can determine that the HARQ operating mode is a forced ACK mode (e.g., even if the HARQ information indicates that the transmitter is configured to perform retransmissions of instructions for decoding information), because the receiver may not be able to decode the TB with a limited number of (remaining) retransmissions under a high MCS. As another example, if the downlink throughput meets a throughput threshold, the receiver can determine that the HARQ operating mode is a forced ACK mode or an adapted forced ACK mode (e.g., to maintain high throughput). If the downlink throughput does not meet the throughput threshold, the receiver can determine that the HARQ operating mode is a normal HARQ mode or an adapted forced ACK mode (e.g., to achieve the lowest possible error rate and / or the highest reliability).

[0153] Determining the HARQ operating mode allows the receiver to customize the HARQ mode for the transmitter's operation. For example, if the transmitter is configured to retransmit the indication of the decoded information before the end of a given HARQ process, the receiver can use an adapted forced ACK mode (e.g., sending a forced ACK communication only after a given number of NACK indications have been sent during a given HARQ process). This increases the likelihood of decoding the TB during a given HARQ process, thereby reducing the likelihood of one or more RLC retransmissions and reducing the latency associated with the receiver obtaining the TB. Additionally, when ordered delivery is configured, all traffic following the TB is delayed, requiring buffering at the receiver. Avoiding RLC retransmissions reduces the likelihood of buffering subsequent traffic, thus saving the receiver's processing and / or memory resources. If the transmitter is not configured to retransmit the indication of the decoded information before the end of a given HARQ process, the receiver can use a forced ACK mode to save time and / or resources (e.g., network or processing resources) that would otherwise be used to transmit one or more RVs that the receiver cannot decode.

[0154] Process 600 may include executing one or more HARQ processes using a determined HARQ operating mode (box 615). For example, a receiver may execute one or more HARQ processes using a determined HARQ operating mode. A receiver that executes one or more HARQ processes using a determined HARQ operating mode may be referred to as a receiver operating in "adaptive" mode or "adaptive" mode.

[0155] Process 600 may include: determining whether to switch to the learning phase (box 620). For example, the receiver may determine whether to switch to the learning phase. For example, the receiver may determine whether to switch from operating in adaptation mode to operating in learning mode. If the receiver determines to switch to the learning phase (box 620 - Yes), the receiver may return to performing one or more learning phase operations (box 605). If the receiver determines not to switch to the learning phase (box 620 - No), the receiver may continue to perform the HARQ process in the determined HARQ operating mode (box 615).

[0156] In some respects, the receiver may periodically switch to a learning phase. For example, the receiver may operate in learning mode according to a periodic schedule (e.g., to acquire HARQ information according to a periodic schedule). Additionally or alternatively, the receiver may switch to the learning phase based on the detection of an event. For example, the receiver may detect an event that triggers the receiver to switch to the learning phase (e.g., to acquire HARQ information). For example, the receiver may switch between operating in learning mode and operating in adaptation mode based on transmitter behavior that may change over time (e.g., based on network behavior).

[0157] For example, events may include receiving cell configuration and / or detecting that the cell configuration has changed. For example, the receiver may switch between operating in learning mode and operating in adaptation mode based on cell information such as coverage information, capacity information, terrestrial information (e.g., whether the network is a terrestrial network or a non-terrestrial network (NTN)), parameter set information (e.g., SCS), operating frequency band (e.g., sub-6 GHz band or millimeter wave band), etc.

[0158] For example, an event could include detecting a failure to receive a retransmission of decoded information (e.g., an indication to the MCS) when expected. For instance, as described above, HARQ information could instruct the transmitter to retransmit decoded information after a given number of NACK indications. If the receiver detects no retransmission of decoded information after a given number of NACK indications for one or more HARQ processes, the receiver can determine to switch to the learning phase.

[0159] For example, events could include receiving RRC configuration or reconfiguration. For instance, the receiver could be based on events such as those performed during the learning phase. NFollowing a HARQ operation, an RB configuration (or another RRC) is received to switch between learning and adaptation modes. Alternatively, events may include the number of HARQ processes executed that meet a threshold (e.g., within a defined HARQ operation mode). Events may also include receiving an RLC configuration or radio bearer configuration. For example, a receiver may switch between learning and adaptation modes based on an RLC mode (e.g., RLC Acknowledgment Mode (AM) or RLC UM). Events may also include receiving a Quality of Service (QoS) configuration. For example, a receiver may switch between learning and adaptation modes based on the QoS requirements of a flow associated with one or more HARQ processes. For instance, if the QoS parameters of a given flow change, the receiver may switch to the learning phase to obtain HARQ information for the changed QoS parameters.

[0160] For example, events may include switching PDU session types. For instance, a receiver may switch between learning and adaptation modes based on PDU session type and / or network slicing information, etc. Events may also include detecting or receiving a handover command. For instance, a receiver may switch to the learning phase upon receiving a handover command (or performing a handover) to obtain HARQ information for a new transmitter (e.g., the transmitter to which the receiver is handed over).

[0161] For example, the switching between learning and adaptation modes and / or one or more parameters of the adapted forced ACK mode (such as thresholds associated with sending forced ACK communication) may be based on the type of radio bearer configuration (e.g., AM or UM), the type of QoS requirement, the PDU session type, and / or network slicing information, etc. Additionally or alternatively, the switching between learning and adaptation modes and / or one or more parameters of the adapted forced ACK mode may be based on the output of a machine learning model. For example, the receiver may deploy a machine learning model. The input to the machine learning model may include HARQ information. The output of the machine learning model may include whether to switch between learning and adaptation modes, one or more parameters of the forced ACK mode, and / or an indication of which HARQ operating mode the receiver should use, etc. For example, the switching between learning and adaptation modes and / or one or more parameters of the adapted forced ACK mode may be based on filtered historical HARQ information (e.g., using a machine learning model to filter historical HARQ information).

[0162] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 600 may be executed in parallel.

[0163] Figure 7 This is a diagram illustrating an example process 700 executed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which a device or UE (e.g., UE 120) performs operations associated with an adaptation technique for HARQ retransmission handling.

[0164] like Figure 7 As shown, in some aspects, process 700 may include: obtaining HARQ information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an instruction to the MCS before the HARQ process associated with the network node ends (box 710). For example, the UE (e.g., using...) Figure 9 The described receiving component 902 and / or communication manager 906 can obtain HARQ information associated with the network node, wherein the HARQ information indicates whether the network node is configured to retransmit the instruction to the MCS before the HARQ process associated with the network node ends, as described above.

[0165] In some aspects, process 700 may include: detecting, for example, the unsuccessful transmission of the RV of the downlink communication TB for the HARQ process associated with downlink communication from the network node. For instance, the UE (e.g., using...) Figure 9 The described communication manager 906 can detect unsuccessful transmission of the RV of the downlink communication TB for the HARQ process associated with downlink communication from the network node, as described above.

[0166] like Figure 7 Further, as shown, in some aspects, process 700 may include: receiving a retransmission of the TB of downlink communication for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS, and complete decoding information for the TB is unavailable (box 720). For example, the UE (e.g., using...) Figure 9 The described receiving component 902 and / or communication manager 906 can receive retransmissions of the TB of downlink communication for the HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with the reserved MCS and the full decoding information for the TB is unavailable, as described above.

[0167] like Figure 7 Further, in some aspects, process 700 may include: performing actions such as continuing the HARQ process, restarting the HARQ process, or terminating the HARQ process based on the received retransmission of the TB, wherein the actions are based on whether the network node is configured to retransmit the instruction to the MCS before the end of each HARQ process (box 730). For example, the UE (e.g., using...) Figure 9The described communication manager 906 can perform actions such as continuing the HARQ process, restarting the HARQ process, or terminating the HARQ process based on the received retransmission of TB, wherein the actions are based on whether the network node is configured to retransmit the instruction to MCS before the end of each HARQ process, as described above.

[0168] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0169] In a first aspect, process 700 includes: in response to a retransmission of the TB associated with the corresponding RV and any subsequent retransmission, sending one or more NACK communications to the network node for the HARQ process, and performing actions including: based on the network node being configured to retransmit an indication to the MCS before the end of each HARQ process, sending HARQ ACK communications to terminate the HARQ process based on the number of one or more NACK communications satisfying a threshold, wherein the threshold is based on HARQ information.

[0170] In the second aspect, either alone or in combination with the first aspect, obtaining HARQ information includes identifying a threshold based on the number of NACK communications between the initial retransmission of a TB with a reserved MCS and the retransmission of an indication to the MCS.

[0171] In the third aspect, either alone or in combination with one or more of the first and second aspects, the threshold is the number of NACK communications.

[0172] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the action includes: in response to receiving a retransmission and based on the fact that the network node is not configured to perform an instruction to the MCS before the end of each HARQ process, sending a HARQ ACK communication (e.g., a forced ACK communication) to terminate the HARQ process.

[0173] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the HARQ information indicates that the index of the MCS meets the MCS threshold, and the action performed includes: in response to receiving a retransmission and based on the index of the MCS meeting the MCS threshold, sending HARQ ACK communication (e.g., forced ACK communication) to terminate the HARQ process.

[0174] In the sixth aspect, obtaining HARQ information, either alone or in combination with one or more of the first to fifth aspects, includes obtaining HARQ information based on periodic scheduling.

[0175] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 700 includes: detecting an event that triggers the acquisition of HARQ information.

[0176] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the event includes at least one of the following: receiving cell configuration, handing over SCS, failing to receive a retransmission of an instruction for MCS, receiving RRC configuration, the number of HARQ processes performed meeting a threshold, receiving RLC configuration, receiving radio bearer configuration, receiving QoS configuration, or handing over PDU session type.

[0177] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the actions include: based on the network node being configured to retransmit the indication to the MCS before the end of each HARQ process, storing samples associated with the retransmission of the TB, wherein the samples are associated with the full bandwidth size; in response to the retransmission of the TB associated with the corresponding RV and any subsequent retransmission, sending one or more NACK communications to the network node for the HARQ process; receiving another RV of the TB from the network node, the other RV including the retransmission of the indication to the MCS; and obtaining the TB based on the MCS, the other RV, and the retransmission of the TB.

[0178] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the HARQ information indicates the downlink throughput, and the action is based on whether the downlink throughput meets the throughput threshold.

[0179] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the downlink throughput does not meet the throughput threshold, and an action is performed to make the UE continue the HARQ process.

[0180] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the downlink throughput meets the throughput threshold, and an action is performed to terminate the HARQ process for the UE.

[0181] In the thirteenth aspect, the action performed alone or in combination with one or more of the first to twelfth aspects includes: sending a HARQ feedback communication to a network node, the HARQ feedback communication indicating that the complete decoding information for the TB is not available for restarting the HARQ process.

[0182] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 700 includes: receiving instructions from a network node for complete decoding information in relation to the HARQ process based on sending HARQ feedback communication.

[0183] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0184] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs operations associated with an adaptation technique for hybrid automatic repeat request retransmission handling.

[0185] like Figure 8 As shown, in some aspects, process 800 may include: receiving a retransmission of the TB of downlink communication for a HARQ process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved MCS and complete decoding information for the TB is unavailable (box 810). For example, the UE (e.g., using...) Figure 9 The described receiving component 902 and / or communication manager 906 can receive retransmissions of the TB of downlink communication for the HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with the reserved MCS and the full decoding information for the TB is unavailable, as described above.

[0186] like Figure 8 Further, in some aspects, process 800 may include: sending HARQ feedback communication (block 820) to the network node based on the received retransmission, indicating that complete decoded information is unavailable. For example, the UE (e.g., using...) Figure 9 The described transmitting component 904 and / or communication manager 906 can send HARQ feedback communication to the network node indicating that complete decoded information is unavailable based on the receipt of a retransmission, as described above.

[0187] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0188] In a first aspect, process 800 includes: receiving an indication of complete decoding information based on sending HARQ feedback communication.

[0189] In the second aspect, either alone or in combination with the first aspect, HARQ feedback communication is associated with HARQ states for lost decoded information.

[0190] although Figure 8An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0191] Figure 9 This is a diagram of an example device 900 for wireless communication according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 906 is combined with... Figure 1 The described communication manager 140. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0192] In some respects, device 900 can be configured to perform the functions described herein. Figure 5A , Figure 5B and / or Figure 6 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 7 Process 700 and / or Figure 8 Process 800 or a combination thereof. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the 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 executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0193] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 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 of device 900. In some aspects, receiver 902 may include combinations of... 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 receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0194] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 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 transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... 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, one or more memories, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in one or more transceivers.

[0195] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0196] The receiving component 902 can obtain HARQ information indicating whether the network node is configured to retransmit decoded information (e.g., an indication of MCS) before the HARQ process associated with the network node ends. The communication manager 906 can detect unsuccessful transmission of the RV of the downlink communication TB for the HARQ process associated with downlink communication from the network node. The receiving component 902 can receive a retransmission of the TB from the network node, where the retransmission is associated with a reserved MCS. The communication manager 906 can perform an action to continue or terminate the HARQ process based on the received TB retransmission, where the action is based on whether the network node is configured to retransmit decoded information before the end of each HARQ process.

[0197] The transmitting component 904 may send one or more NACK communications to the network node in response to a retransmission of the TB associated with the corresponding RV and any subsequent retransmissions, in response to the HARQ process.

[0198] The Communication Manager 906 can detect events that trigger the acquisition of HARQ information.

[0199] The receiving component 902 can receive a retransmission of the TB (Through Block) of downlink communication for a HARQ process associated with the downlink communication, wherein the retransmission is associated with a reserved MCS (Multi-Channel System) and the complete decoding information for the TB is unavailable. The transmitting component 904 can send HARQ feedback communication indicating that the complete decoding information is unavailable based on the received retransmission. The receiving component 902 can receive an indication of complete decoding information based on sending the HARQ feedback communication.

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

[0201] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: obtaining Hybrid Automatic Repeat Request (HARQ) information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an indication of a modulation and decoding scheme (MCS) before the end of a HARQ process associated with the network node; receiving a retransmission of a TB of downlink communication for a HARQ process associated with downlink communication from the network node, wherein the retransmission is associated with a reserved MCS and complete decoding information for the TB is unavailable; and performing an action to continue the HARQ process, restart the HARQ process, or terminate the HARQ process based on the retransmission of the TB, wherein the action is based on whether the network node is configured to retransmit the indication of the MCS before the end of each HARQ process.

[0202] Aspect 2: According to the method of Aspect 1, the method further includes: in response to the retransmission and any subsequent retransmission of the TB associated with the corresponding RV, sending one or more negative acknowledgment (NACK) communications to the network node for the HARQ process; and wherein performing the action includes: based on the network node being configured to perform the retransmission of the indication to the MCS before the end of each HARQ process, sending HARQ acknowledgment (ACK) communications to terminate the HARQ process based on the number of the one or more NACK communications meeting a threshold, wherein the threshold is based on the HARQ information. The action further includes: based on the network node being configured to perform the retransmission of the indication to the MCS before the end of each HARQ process, sending HARQ acknowledgment (ACK) communications to terminate the HARQ process based on the number of the one or more NACK communications meeting a threshold, wherein the threshold is based on the HARQ information.

[0203] Aspect 3: According to the method of aspect 2, wherein obtaining the HARQ information includes identifying the threshold based on the number of NACK communications between the initial retransmission of the TB with the reserved MCS and the retransmission of the indication to the MCS.

[0204] Aspect 4: According to the method of aspect 3, the threshold is the number of NACK communications.

[0205] Aspect 5: The method according to any one of Aspects 1 to 4, wherein performing the action comprises: in response to receiving the retransmission and based on the fact that the network node is not configured to perform the retransmission to the MCS before the end of each HARQ process, sending HARQ acknowledgment (ACK) communication to terminate the HARQ process.

[0206] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the HARQ information indicates that the index of the MCS satisfies the MCS threshold, and wherein performing the action includes: in response to receiving the retransmission and based on the index of the MCS satisfying the MCS threshold, sending HARQ acknowledgment (ACK) communication to terminate the HARQ process.

[0207] Aspect 7: The method according to any one of Aspects 1 to 6, wherein obtaining the HARQ information comprises: obtaining the HARQ information according to a periodic schedule.

[0208] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: detecting an event that triggers the acquisition of the HARQ information.

[0209] Aspect 9: According to the method of aspect 8, the event includes at least one of the following: receiving cell configuration; switching subcarrier spacing (SCS); failing to receive the retransmission of the indication to the MCS; receiving radio resource control (RRC) configuration; the number of HARQ processes performed meeting a threshold; receiving radio link control (RLC) configuration; receiving radio bearer configuration; receiving quality of service (QoS) configuration; or switching protocol data unit (PDU) session type.

[0210] Aspect 10: The method according to any one of Aspects 1 to 9, wherein performing the action comprises: based on the network node being configured to perform the retransmission of the indication to the MCS before the end of each HARQ process, storing a sample associated with the retransmission of the TB, wherein the sample is associated with a full bandwidth size; in response to the retransmission of the TB associated with the corresponding RV and any subsequent retransmission, sending one or more negative acknowledgment (NACK) communications to the network node for the HARQ process; receiving another RV of the TB from the network node, the other RV including the retransmission of the indication to the MCS; and obtaining the TB based on the MCS, the other RV, and the retransmission of the TB.

[0211] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the HARQ information indicates downlink throughput, and wherein the action is based on whether the downlink throughput meets a throughput threshold.

[0212] Aspect 12: According to the method of aspect 11, wherein the downlink throughput does not meet the throughput threshold, and wherein the action is performed to cause the UE to continue the HARQ process.

[0213] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the downlink throughput satisfies the throughput threshold, and wherein the action is performed to cause the UE to terminate the HARQ process.

[0214] Aspect 14: The method according to any one of Aspects 1 to 13, wherein performing the action comprises: sending a HARQ feedback communication to the network node, the HARQ feedback communication indicating that the complete decoding information for the TB is not available for restarting the HARQ process.

[0215] Aspect 15: The method according to aspect 14, the method further comprising: receiving an indication of the complete decoding information from the network node for the HARQ process based on sending the HARQ feedback communication.

[0216] Aspect 16: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a retransmission of a transport block (TB) of a downlink communication in response to a Hybrid Automatic Repeat Request (HARQ) process associated with downlink communication from a network node, wherein the retransmission is associated with a reserved modulation and decoding scheme (MCS) and complete decoding information for the TB is unavailable; and sending a HARQ feedback communication to the network node based on receiving the retransmission, indicating that the complete decoding information is unavailable.

[0217] Aspect 17: The method according to aspect 16 further includes: receiving an indication of the complete decoding information based on sending the HARQ feedback communication.

[0218] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the HARQ feedback communication is associated with the HARQ state for lost decoding information.

[0219] Aspect 19: 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 18.

[0220] Aspect 20: 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 18.

[0221] Aspect 21: 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 18.

[0222] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 18.

[0223] Aspect 23: 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 18.

[0224] Aspect 24: A device for wireless communication, the device comprising: a processing system including 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 18.

[0225] Aspect 25: 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 one or more of the methods according to aspects 1 to 18.

[0226] 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.

[0227] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on". As used herein, depending on the context, "meeting a threshold" can refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. As used herein, the phrase referring to "at least one of" a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0228] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more”. Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more”. If only one item is desired, the phrase “only one” or similar terms will be used. Moreover, as used herein, the terms “having” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, as used herein, the term “or” when used in a sequence is intended to be inclusive and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in conjunction with “either of” or “only one of”).

[0229] The various exemplary logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various exemplary components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0230] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be executed by circuitry dedicated to a given function.

[0231] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by or control of the operation of a data processing apparatus.

[0232] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The process of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, with communication media including any medium capable of transferring a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection may be properly referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of media described herein should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0233] Various modifications to the aspects described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0234] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positioning on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0235] Some features described in the context of an independent aspect in this specification may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented individually or in any suitable sub-combination in multiple aspects. Furthermore, although features may be described as functioning in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0236] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of various system components in the described aspects should not be construed as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Obtain Hybrid Automatic Repeat Request (HARQ) information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an instruction to a modulation and decoding scheme (MCS) before the HARQ process associated with the network node ends; For HARQ processes associated with downlink communication from the network node, retransmission of transport blocks (TBs) of the downlink communication is received, wherein the retransmission is associated with a reserved MCS, and wherein complete decoding information for the TB is unavailable; and Based on the retransmission received from the TB, the action of continuing the HARQ process, restarting the HARQ process, or terminating the HARQ process is performed, wherein the action is based on whether the network node is configured to perform the retransmission of the instruction to the MCS before the end of each HARQ process.

2. The method according to claim 1, further comprising: In response to the retransmission of the TB and any subsequent retransmission, one or more negative acknowledgment (NACK) communications are sent to the network node for the HARQ process; and The actions described include: Based on the network node being configured to retransmit the instruction to the MCS before the end of each HARQ process, HARQ acknowledgment (ACK) communications are sent to terminate the HARQ process based on the number of one or more NACK communications meeting a threshold, wherein the threshold is based on the HARQ information.

3. The method according to claim 2, wherein obtaining the HARQ information comprises: The threshold is identified based on the number of NACK communications between the initial retransmission of the TB with the reserved MCS and the retransmission of the indication to the MCS.

4. The method of claim 1, wherein performing the action comprises: In response to receiving the retransmission and based on the fact that the network node is not configured to perform the instruction to the MCS before the end of each HARQ process, a HARQ acknowledgment (ACK) communication is sent to terminate the HARQ process.

5. The method of claim 1, wherein the HARQ information indicates that the index of the MCS satisfies the MCS threshold, and wherein performing the action comprises: In response to receiving the retransmission and the index based on the MCS satisfying the MCS threshold, a HARQ acknowledgment (ACK) communication is sent to terminate the HARQ process.

6. The method according to claim 1, wherein obtaining the HARQ information comprises: The HARQ information is obtained based on periodic scheduling.

7. The method according to claim 1, further comprising: The event that triggers the acquisition of the HARQ information is detected.

8. The method of claim 1, wherein performing the action comprises: Based on the network node being configured to perform the retransmission of the instruction to the MCS before the end of each HARQ process, a sample associated with the retransmission of the TB is stored, wherein the sample is associated with the full bandwidth size; In response to the retransmission and any subsequent retransmission of the TB associated with the corresponding RV, one or more negative acknowledgment (NACK) communications are sent to the network node for the HARQ process; Receive another RV of the TB from the network node, the other RV including the retransmission of the indication of the MCS; and The TB is obtained based on the retransmission of the MCS, the other RV, and the TB.

9. The method of claim 1, wherein the HARQ information indicates downlink throughput, and wherein the action is based on whether the downlink throughput meets a throughput threshold.

10. The method of claim 9, wherein the downlink throughput does not meet the throughput threshold, and wherein the action is performed to cause the UE to continue the HARQ process.

11. The method of claim 9, wherein the downlink throughput satisfies the throughput threshold, and wherein performing the action causes the UE to terminate the HARQ process.

12. The method of claim 1, wherein performing the action comprises: A HARQ feedback communication is sent to the network node, indicating that the complete decoding information for the TB is not available to restart the HARQ process.

13. The method according to claim 12, further comprising: Based on sending the HARQ feedback communication, an instruction for receiving the complete decoding information from the network node is received for the HARQ process.

14. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; 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 UE to: Obtain Hybrid Automatic Repeat Request (HARQ) information associated with a network node, wherein the HARQ information indicates whether the network node is configured to retransmit an instruction to a modulation and decoding scheme (MCS) before the HARQ process associated with the network node ends; For HARQ processes associated with downlink communication from the network node, retransmission of transport blocks (TBs) of the downlink communication is received, wherein the retransmission is associated with a reserved MCS, and wherein complete decoding information for the TB is unavailable; and Based on the retransmission received from the TB, the action of continuing the HARQ process, restarting the HARQ process, or terminating the HARQ process is performed, wherein the action is based on whether the network node is configured to perform the retransmission of the instruction to the MCS before the end of each HARQ process.

15. The apparatus of claim 14, wherein the one or more processors are further configured to cause the UE to: In response to the retransmission and any subsequent retransmission of the TB associated with the corresponding RV, one or more negative acknowledgment (NACK) communications are sent to the network node for the HARQ process; and In order for the UE to perform the action, the one or more processors are configured to cause the UE to: Based on the network node being configured to retransmit the instruction to the MCS before the end of each HARQ process, HARQ acknowledgment (ACK) communications are sent to terminate the HARQ process based on the number of one or more NACK communications meeting a threshold, wherein the threshold is based on the HARQ information.

16. The apparatus of claim 15, wherein, in order for the UE to obtain the HARQ information, the one or more processors are configured to cause the UE to: The threshold is identified based on the number of NACK communications between the initial retransmission of the TB with the reserved MCS and the retransmission of the indication to the MCS.

17. The apparatus of claim 16, wherein the threshold is the number of NACK communications.

18. The apparatus of claim 14, wherein, in order for the UE to perform the action, the one or more processors are configured to cause the UE to: In response to receiving the retransmission and based on the fact that the network node is not configured to perform the instruction to the MCS before the end of each HARQ process, a HARQ acknowledgment (ACK) communication is sent to terminate the HARQ process.

19. The apparatus of claim 14, wherein the HARQ information indicates that the index of the MCS satisfies an MCS threshold, and wherein, in order for the UE to perform the action, the one or more processors are configured to cause the UE to: In response to receiving the retransmission and the index based on the MCS satisfying the MCS threshold, a HARQ acknowledgment (ACK) communication is sent to terminate the HARQ process.

20. The apparatus of claim 14, wherein the one or more processors are further configured to cause the UE to: The event that triggers the acquisition of the HARQ information is detected.

21. The apparatus of claim 20, wherein the event includes at least one of the following: Receive cell configuration, Switching subcarrier spacing (SCS). The retransmission of the instruction to the MCS was not received. Receive Radio Resource Control (RRC) configuration, The number of HARQ processes executed meets the threshold. Receive Radio Link Control (RLC) configuration. Receive radio bearer configuration, Receive Quality of Service (QoS) configuration, or Switch Protocol Data Unit (PDU) session type.

22. The apparatus of claim 14, wherein, in order for the UE to perform the action, the one or more processors are configured to cause the UE to: Based on the network node being configured to perform the retransmission of the instruction to the MCS before the end of each HARQ process, a sample associated with the retransmission of the TB is stored, wherein the sample is associated with the full bandwidth size; In response to the retransmission and any subsequent retransmission of the TB associated with the corresponding RV, one or more negative acknowledgment (NACK) communications are sent to the network node for the HARQ process; Receive another RV of the TB from the network node, the other RV including the retransmission of the indication of the MCS; and The TB is obtained based on the retransmission of the MCS, the other RV, and the TB.

23. The apparatus of claim 14, wherein the HARQ information indicates downlink throughput, and wherein the action is based on whether the downlink throughput meets a throughput threshold.

24. The apparatus of claim 14, wherein, in order for the UE to perform the action, the one or more processors are configured to cause the UE to: A HARQ feedback communication is sent to the network node, indicating that the complete decoding information for the TB is not available to restart the HARQ process.

25. The apparatus of claim 24, wherein the one or more processors are further configured to cause the UE to: Based on sending the HARQ feedback communication, an instruction for receiving the complete decoding information from the network node is received for the HARQ process.

26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the UE to: The Hybrid Automatic Repeat Request (HARQ) process receives retransmissions of transport blocks (TBs) of downlink communication associated with downlink communication from network nodes, wherein the retransmissions are associated with a reserved modulation and decoding scheme (MCS), and complete decoding information for the TB is unavailable; and Based on the received retransmission, a HARQ feedback communication is sent to the network node indicating that the complete decoded information is unavailable.

27. The apparatus of claim 26, wherein the one or more processors are further configured to cause the UE to: Based on sending the HARQ feedback communication to receive an indication of the complete decoding information.

28. The apparatus of claim 26, wherein the HARQ feedback communication is associated with a HARQ state for lost decoded information.

29. A method for wireless communication performed by a user equipment (UE), the method comprising: The Hybrid Automatic Repeat Request (HARQ) process receives retransmissions of transport blocks (TBs) of downlink communication associated with downlink communication from network nodes, wherein the retransmissions are associated with a reserved modulation and decoding scheme (MCS), and complete decoding information for the TB is unavailable; and Based on the received retransmission, a HARQ feedback communication is sent to the network node indicating that the complete decoded information is unavailable.

30. The method according to claim 29, further comprising: Based on sending the HARQ feedback communication to receive an indication of the complete decoding information.

Images