Conditional hybrid automatic repeat request retransmission across carriers

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, a user equipment (UE) and a network entity may support conditional cross-carrier hybrid automatic repeat request (HARQ) retransmission. The UE may send a capability message to the network entity to indicate the capability of the UE to support the cross-carrier HARQ retransmissions. The UE or the network entity may transmit a message on a first component carrier. The UE or the network entity may retransmit the message on a second component carrier based on availability of resources for retransmitting the message, based on the capabilities of the UE, and based on one or more conditions associated with communications by the UE satisfying a threshold condition for cross-carrier HARQ retransmission. For uplink communications, the UE may perform the transmission and conditional retransmission. For downlink communications, the network entity may perform the transmission and conditional retransmission.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 296,313, filed April 5, 2023, entitled “CONDITIONAL HYBRID AUTOMATIC REPEAT REQUEST RETRANSMISSION ACROSS CARRIERS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following discussion pertains to wireless communications, including cross-carrier conditional hybrid automatic repeat request (HARQ) retransmission. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE).

[0005] In some systems, the UE and network entities can support Hybrid Automatic Repeat Request (HARQ) retransmissions, in which the device can retransmit the message based on the failure of the first transmission. HARQ retransmissions can be performed for uplink communication, downlink communication, or both. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting conditional hybrid automatic repeat request (HARQ) retransmissions across carriers. For example, the described technology provides user equipment (UE) and network entities that support conditional cross-carrier HARQ retransmissions. The UE can send a capability message to the network entity to indicate its capability to support these cross-carrier HARQ retransmissions. This capability message may indicate that the UE is capable of sending uplink cross-carrier HARQ retransmissions or receiving downlink cross-carrier HARQ retransmissions, or both. As an example, the UE or network entity may send an initial message on a first component carrier that may not have been received at another device. The UE or network entity may retransmit the message on a second component carrier, different from the first component carrier, based on the availability of resources for retransmitting the message, based on the UE's capabilities, and based on one or more conditions associated with the communication performed by the UE satisfying a threshold condition for cross-carrier HARQ retransmission. If available resources exist on the second component carrier for the retransmission, and if the UE supports cross-carrier HARQ retransmission capability, and if these conditions meet the threshold condition, cross-carrier HARQ retransmission can be enabled or supported. If no available resources exist on the second component carrier for the retransmission, and if the UE does not support cross-carrier HARQ retransmission capability, or if these conditions do not meet the threshold condition, the UE or network entity can avoid retransmission on the second component carrier and may instead retransmit the message on the first component carrier. For uplink communication, the UE can perform this transmission and conditional retransmission. For downlink communication, the network entity can perform this transmission and conditional retransmission.

[0007] A method for performing wireless communication at a UE is described. The method may include: transmitting a capability message indicating that the UE supports cross-carrier HARQ retransmission; transmitting a message on a first component carrier; and retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: transmit a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission; transmit a message on a first component carrier; and retransmit the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for transmitting a capability message indicating that the UE supports cross-carrier HARQ retransmission; components for transmitting a message on a first component carrier; and components for retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0010] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: transmit a capability message indicating that the UE supports cross-carrier HARQ retransmission; transmit a message on a first component carrier; and retransmit the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0011] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second message indicating whether the remaining uplink delay budget meets the threshold uplink delay budget based on a comparison of the UE's remaining uplink delay budget with a threshold uplink delay budget.

[0012] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: retransmitting the message on the second component carrier; or indicating, based on the second message, that the remaining uplink delay budget meets the threshold uplink delay budget.

[0013] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting via the capability message an indication of a time period associated with preparing for retransmission of the message on the second component carrier, wherein retransmission of the message may be based on the time period being less than a threshold time period.

[0014] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending an indication via the capability message of the processing time associated with a retransmission performed by the UE.

[0015] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting auxiliary information indicating one or more parameters associated with these communications performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the auxiliary information.

[0016] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more parameters include the processing time associated with a retransmission performed by the UE, the state associated with the HARQ buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

[0017] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the auxiliary information may include operations, features, components, or instructions for transmitting a radio resource control (RRC) message that indicates one or more parameters associated with these communications performed by the UE.

[0018] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending an uplink control information (UCI) message or a media access control-control element (MAC-CE) indicating one or more parameters associated with these communications performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the UCI message or the MAC-CE.

[0019] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting auxiliary information including a request to enable these cross-carrier HARQ retransmissions based on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein retransmission of the message on the second component carrier may be based on the request.

[0020] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: comparing the uplink packet data convergence protocol (PDCP) queuing delay of the UE with a threshold PDCP queuing delay; based on the comparison, transmitting a UCI indicating that the uplink PDCP queuing delay meets the threshold PDCP queuing delay, the UCI being multiplexed with the message on the first component carrier; and receiving an grant on the first component carrier, the grant indicating an opportunity for retransmission of the message on the second component carrier, wherein retransmission of the message may be based on the grant and the uplink PDCP queuing delay meeting the threshold PDCP queuing delay.

[0021] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving an grant based on the capability of the UE and the satisfaction of one or more conditions of the threshold condition, the grant indicating a timing for retransmission of the message on the second component carrier, wherein the message may be retransmitted based on the grant via the timing of transmission on the second component carrier.

[0022] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a control message that configures a set of configuration-granted resources for HARQ retransmission on the first component carrier and the second component carrier, the set of configuration-granted resources including at least a first resource on the first component carrier for transmitting the message and a second resource on the second component carrier for at least one retransmission of the message. In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, retransmitting the message may include operations, features, components, or instructions for performing: retransmitting the message via the second resource in the set of configuration-granted resources based on the capability of the UE and that one or more conditions satisfy the threshold condition.

[0023] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a control message configured for switching between the first component carrier and the second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier may be based on the semi-static switching mode.

[0024] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving downlink control information (DCI) based on sending the message, the downlink control information (DCI) indicating a request to retransmit the message, wherein retransmission of the message may be based on the request, and wherein the carrier indication field in the DCI includes information for the UE that may differ from the carrier indication based on the semi-static handover mode.

[0025] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more conditions include the packet error rate (PER), the reference signal received power (RSRP), or both, measured by the UE.

[0026] A method for wireless communication at a UE is described. The method may include: transmitting a capability message indicating that the UE supports cross-carrier HARQ retransmission; transmitting a message on a first component carrier; and receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0027] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: transmit a capability message indicating that the UE supports cross-carrier HARQ retransmission; receive a message on a first component carrier; and receive a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0028] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for transmitting a capability message indicating that the UE supports cross-carrier HARQ retransmission; components for transmitting a message on a first component carrier; and components for receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0029] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: send a capability message indicating that the UE supports cross-carrier HARQ retransmission; receive a message on a first component carrier; and receive a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0030] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending an indication via the capability message of the processing time associated with a retransmission performed by the UE.

[0031] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the auxiliary information.

[0032] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more parameters include the processing time associated with a retransmission performed by the UE, the state associated with the HARQ buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

[0033] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the auxiliary information may include operations, features, components, or instructions for transmitting an RRC message indicating one or more parameters associated with these communications performed by the UE.

[0034] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending a UCI message or MAC-CE indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the UCI message or MAC-CE.

[0035] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting auxiliary information including a request to enable these cross-carrier HARQ retransmissions based on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of receiving the message on the second component carrier may be based on the request.

[0036] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving an grant based on one or more conditions satisfying the threshold condition, the grant scheduling the timing of the retransmission of the message on the second component carrier, wherein the retransmission of the message may be received based on the grant via the timing of the transmission on the second component carrier.

[0037] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a control message configured for switching between the first component carrier and the second component carrier for at least one retransmission in a semi-static switching mode, wherein the retransmission of which the message is received on the second component carrier may be based on the semi-static switching mode.

[0038] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a DCI based on the message, the DCI indicating the retransmission of the message, wherein receiving the retransmission of the message may be based on the DCI, and wherein the carrier indication field in the downlink control information includes information for the UE that may differ from a carrier indication based on the semi-static handover mode.

[0039] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more conditions include PER, RSRP, or both measured by the UE.

[0040] A method for wireless communication at a network entity is described. The method may include: receiving a capability message indicating that a UE supports cross-carrier HARQ retransmission; receiving a message on a first component carrier; and receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0041] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: receive a capability message indicating that a UE supports cross-carrier HARQ retransmission; receive a message on a first component carrier; and receive a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0042] Another apparatus for wireless communication at a network entity is described. The apparatus may include: components for receiving a capability message indicating that a UE supports cross-carrier HARQ retransmission; components for receiving the message on a first component carrier; and components for receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0043] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by a processor to: receive a capability message indicating that a UE supports cross-carrier HARQ retransmissions; receive the message on a first component carrier; and receive a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support these cross-carrier HARQ retransmissions, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0044] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: transmitting a control message indicating a threshold uplink delay budget; and receiving a second message indicating whether the remaining uplink delay budget of the UE satisfies the threshold uplink delay budget, wherein the retransmission of receiving the message on the second component carrier may be based on the second message indicating that the remaining uplink delay budget satisfies the threshold uplink delay budget.

[0045] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving via the capability message an indication of a time period associated with the retransmission of the message prepared by the UE on the second component carrier, the time period being based on a processing time associated with the retransmission performed by the UE, wherein the retransmission of the message may be based on the time period being less than a threshold time period.

[0046] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving auxiliary information indicating one or more parameters associated with these communications performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the auxiliary information.

[0047] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more parameters include the processing time associated with a retransmission performed by the UE, the state associated with the HARQ buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

[0048] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the auxiliary information may include operations, features, components, or instructions for receiving an RRC message that indicates one or more parameters associated with these communications performed by the UE.

[0049] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a UCI message or MAC-CE that indicates one or more parameters associated with communication performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the UCI message or MAC-CE.

[0050] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving auxiliary information, including a request to enable these cross-carrier HARQ retransmissions, based on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message received on the second component carrier may be based on the request.

[0051] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a UCI indicating that the uplink PDCP queuing delay of the UE meets a threshold PDCP queuing delay, the UCI being multiplexed with the message on the first component carrier; and transmitting an grant on the first component carrier, the grant indicating the timing of transmission for the retransmission of the message on the second component carrier, wherein the retransmission of the message may be received based on the grant and the uplink PDCP queuing delay meeting the threshold PDCP queuing delay.

[0052] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting an grant based on the capability of the UE and the satisfaction of one or more conditions of the threshold condition, the grant indicating the timing of transmission of the message retransmission on the second component carrier, wherein the retransmission of the message may be received based on the grant via the timing of transmission on the second component carrier.

[0053] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: transmitting a control message that configures a set of configuration-granted resources for HARQ retransmission on the first component carrier and the second component carrier, the set of configuration-granted resources including at least a first resource on the first component carrier for transmitting the message and a second resource on the second component carrier for at least one retransmission of the message, wherein the retransmission of the message may be received via the second resource in the set of configuration-granted resources based on the UE’s capability and the satisfaction of one or more conditions of the threshold condition.

[0054] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: transmitting a control message configured for switching between the first component carrier and the second component carrier for at least one retransmission in a semi-static switching mode, wherein the retransmission of which the message is received on the second component carrier may be based on the semi-static switching mode.

[0055] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: sending a DCI based on receiving the message, the DCI indicating a request for retransmission of the message, wherein the retransmission of the message may be based on the request, and wherein the carrier indication field in the DCI includes information for the UE that differs from the carrier indication based on the semi-static handover mode.

[0056] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more conditions include PER, RSRP, or both measured by the UE.

[0057] A method for wireless communication at a network entity is described. The method may include: receiving a capability message indicating that a UE supports cross-carrier HARQ retransmission; transmitting a message on a first component carrier; and retransmitting the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0058] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: receive a capability message indicating that a UE supports the capability of cross-carrier HARQ retransmission; transmit a message on a first component carrier; and retransmit the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0059] Another apparatus for wireless communication at a network entity is described. The apparatus may include: components for receiving a capability message indicating that a UE supports cross-carrier HARQ retransmission; components for transmitting a message on a first component carrier; and components for retransmitting the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE supporting this cross-carrier HARQ retransmission capability and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0060] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by a processor to: receive a capability message indicating that a UE supports cross-carrier HARQ retransmission; transmit a message on a first component carrier; and retransmit the message on a second component carrier different from the first component carrier, wherein the retransmission on the second component carrier is based on the UE's capability to support these cross-carrier HARQ retransmissions and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for these cross-carrier HARQ retransmissions.

[0061] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, via the capability message, an indication of the processing time associated with a retransmission performed by the UE.

[0062] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the auxiliary information.

[0063] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more parameters include the processing time associated with a retransmission performed by the UE, the state associated with the HARQ buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

[0064] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the auxiliary information may include operations, features, components, or instructions for receiving an RRC message that indicates one or more parameters associated with these communications performed by the UE.

[0065] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: receiving a UCI message or MAC-CE that indicates one or more parameters associated with communication performed by the UE, wherein the one or more conditions may be based on the one or more parameters indicated via the UCI message or MAC-CE.

[0066] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving auxiliary information, including a request to enable these cross-carrier HARQ retransmissions, based on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein retransmission of the message on the second component carrier may be based on the request.

[0067] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting an grant based on one or more conditions satisfying the threshold condition, the grant scheduling a transmission timing on the second component carrier for retransmission of the message, wherein the message may be retransmitted based on the grant via the transmission timing on the second component carrier.

[0068] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing: transmitting a control message configured to switch between the first component carrier and the second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier may be based on the semi-static switching mode.

[0069] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: transmitting a DCI based on the message, the DCI instructing the retransmission of the message, wherein the retransmission of the message may be based on the DCI, and wherein the carrier indication field in the DCI includes information for the UE that differs from the carrier indication based on the semi-static handover mode.

[0070] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more conditions include PER, RSRP, or both measured by the UE. Attached Figure Description

[0071] Figure 1 An example of a wireless communication system supporting cross-carrier conditional hybrid automatic repeat request (HARQ) retransmission is shown in accordance with one or more aspects of this disclosure.

[0072] Figure 2 Examples of wireless communication systems supporting cross-carrier conditional HARQ retransmission are illustrated according to one or more aspects of this disclosure.

[0073] Figure 3 An example of a HARQ transmission timeline supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated.

[0074] Figure 4 An example of a HARQ transmission timeline supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated.

[0075] Figure 5 Examples of process flows supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure are illustrated.

[0076] Figure 6 Examples of process flows supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure are illustrated.

[0077] Figure 7 and Figure 8 A block diagram illustrating an apparatus that supports cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0078] Figure 9 A block diagram illustrating a communication manager supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0079] Figure 10 A diagram illustrating a system including a device supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0080] Figure 11 and Figure 12 A block diagram illustrating an apparatus that supports cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0081] Figure 13 A block diagram illustrating a communication manager supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0082] Figure 14 A diagram illustrating a system including a device supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown.

[0083] Figures 15 to 19 A flowchart illustrating a method for supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown. Detailed Implementation

[0084] Some systems support Hybrid Automatic Repeat Request (HARQ) feedback. For example, a User Equipment (UE) may receive a downlink message from a network entity and, in response to the downlink message, send a feedback message (e.g., HARQ feedback) to indicate feedback. If the downlink message is not received correctly, the UE may send a negative acknowledgment (NACK) to the network entity, and the network entity may perform a retransmission of the downlink message (e.g., HARQ retransmission). In some systems, the network entity may transmit the downlink message on a first component carrier and may retransmit the downlink message on a second component carrier different from the first component carrier. For example, the network entity may retransmit the downlink message in the most recent available downlink transmission opportunity, which may be on a component carrier different from the first component carrier used for the initial transmission. For uplink communication, if the network entity fails to receive an uplink message from the UE, the network entity may send an uplink grant that grants resources for retransmission of the uplink message on the same carrier or a different carrier as the original uplink message. However, compared to systems that transmit HARQ retransmissions via the same component carrier as the corresponding initial transmission, cross-carrier HARQ retransmissions may increase complexity and processing by the equipment.

[0085] The technologies, systems, and devices described herein define conditions or rules for determining when cross-carrier HARQ retransmissions can be enabled or permitted. These conditions or rules can provide devices with reduced latency to support retransmissions while maintaining reduced complexity and processing in certain scenarios. A message can be retransmitted on a different component carrier than its initial transmission if the UE receiving or transmitting a retransmission is capable of receiving or transmitting cross-carrier retransmissions and if at least one condition associated with communication between the UE and another device satisfies a threshold condition. This condition can be, for example, the delay between the packet arrival delay convergence protocol (PDCP) layer and the transmitted packet, a reliability measurement (e.g., packet error rate (PER)), reference signal received power (RSRP), or any combination thereof. The UE may send a capability message indicating whether the UE is capable of supporting cross-carrier retransmissions. The UE may send one or more other messages, such as UE assistance information (UAI) or uplink control information (UCI), or both, indicating the condition or used to measure or determine one or more parameters of the condition.

[0086] The described technology can be applied to both uplink and downlink communications. For downlink communications, the network entity can retransmit downlink messages on different component carriers if the network entity receives a NACK from the UE in response to the initial transmission of a downlink message, if the UE supports cross-carrier retransmission, and if at least one condition is met. For uplink communications, the UE can similarly retransmit uplink messages on different component carriers if the UE determines that the condition is met. The UE can receive an uplink grant or some other indication that triggers the retransmission. Time and frequency resources on different component carriers can be allocated for cross-carrier retransmission via dynamic granting, configuration granting, or periodic scheduling modes.

[0087] The various aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects of this disclosure are described with reference to HARQ transmission timelines and process flows. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to cross-carrier conditional HARQ retransmission.

[0088] Figure 1 An example of a wireless communication system 100 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0089] Network entity 105 may be distributed across a geographical area to form wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other names. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support a coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support signal communication according to one or more radio access technologies (RATs).

[0090] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs 115 or network entities 105 as shown.

[0091] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0092] In some examples, network entity 105 may communicate with core network 130 or with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0093] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, self-contained) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0094] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105 (such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0095] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU160 can connect to one or more DU 165s or RU 170s, and the one or more DU 165s or RU 170s can host lower protocol layers, such as Layer 1 (L1) (e.g., the Physical (PHY) layer) or L2 (e.g., the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by the CU 160. Additionally or alternatively, a protocol stack functional split can be employed between the DU 165 and RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 that communicate via these communication links.

[0096] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0097] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0098] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may be relayed for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0099] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0100] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support conditional HARQ retransmission across carriers as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0101] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0102] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0103] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0104] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0105] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0106] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0107] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0108] One or more parameter sets for a carrier can be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of the UE 115 can be constrained to one or more active BWPs.

[0109] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period T. s =1 / (Δf) max ·N f ) seconds, where Δf max This can represent the supported subcarrier spacing, while N f The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0110] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N) symbols. f The duration of a symbol period is associated with a ( ) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0111] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a Transmission Time Interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0112] Physical channels can be multiplexed using various techniques to enable communication using carriers. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via downlink carriers. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set in UE 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0113] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0114] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and can operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 associated with a user in a home or office). Network entity 105 can support one or more cells and can also use one or more component carriers to support communication via one or more cells.

[0115] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0116] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0117] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0118] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0119] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, a reduced peak rate can be used to perform half-duplex communication. Other power-saving techniques for UE 115s include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0120] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0121] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by network entity 105. In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0122] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may use signal notifications to communicate information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0123] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which can provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0124] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0125] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) ranging from 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted for transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0126] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands (e.g., LAA) in a carrier aggregation-based configuration. Operations using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0127] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0128] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0129] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0130] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) the beam direction for later transmission or reception by network entity 105.

[0131] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0132] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured beam set across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoded matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0133] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signals according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signals according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array, any of which may refer to “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined by listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0134] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer can map transport channels to physical channels.

[0135] UE 115 and network entity 105 may support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0136] Therefore, HARQ technology can be used to further increase the reliability of communication between communication devices. HARQ technology may include retransmitting negative acknowledgments (or unacknowledged signals) using different modulation and / or decoding techniques. In such cases, the receiving device may store undecoded communications (which may be referred to as the initial transmission) and combine undecoded communications with one or more retransmissions, for example, until the data in the communication is successfully decoded. The HARQ process may support a set of HARQ communications (initial retransmission and one or more retransmissions). In some examples, multiple HARQ processes may support multiple sets of HARQ communications between communication devices. For example, one HARQ process may be used to communicate a first set of data to the device, and another HARQ process may be used to communicate a second set of data to the device, for example, to increase the data rate of communication between the communication devices. In some examples, the acknowledgment feedback used to support the HARQ process may be referred to as HARQ feedback. For downlink transmissions, the HARQ process associated with the transmission and the status of the data included in the transmission may be included in a scheduling message (e.g., a DCI message). For uplink transmissions, the HARQ procedure associated with the transmission and the status of the data included in the transmission can be included in the uplink grant (e.g., DCI message).

[0137] For downlink transmissions, ACK / NACK resources can be used to report HARQ feedback to network entity 105. In some examples, codebook reporting is used to report HARQ feedback for multiple downlink transmissions, and different types of codebook reporting techniques can be configured. In some examples, semi-static reporting (or Type 1 HARQ feedback reporting) can be used to report feedback for a configured number of transport blocks. In some examples, dynamic reporting (or Type 2 HARQ feedback reporting) can be used to report feedback for the number of transport blocks indicated in the downlink control information (e.g., using a downlink assignment indicator). Both Type 1 and Type 2 HARQ feedback reports can report HARQ feedback on a transport block (or code group) basis. In some examples, the ordering of HARQ feedback in the codebook can be based on the timing of the transport blocks. In some examples, one-time reporting (or Type 3 HARQ feedback reporting) can be used to report feedback for all HARQ procedures configured for UE 115. Therefore, the ordering of HARQ feedback in the codebook can be based on the index of the HARQ procedure identifier.

[0138] In some examples, ACK / NACK resources can be scheduled based on downlink shared channel resources used by downlink transmissions. For example, ACK / NACK resources can occur for a specified duration after the end of the downlink shared channel resources. In some examples, the specified duration is based on a higher-layer parameter, which may be referred to as the K1 timing parameter. For communication using a 120kHz interval, K1 may correspond to 20 or 24 symbols. For uplink transmissions, HARQ feedback can be transmitted during the uplink shared channel resources scheduled by uplink grant. In some examples, the uplink shared channel resources can occur for a specified duration after the end of the uplink grant. In some examples, the specified duration is given by a second higher-layer parameter, which may be referred to as the K2 timing parameter. For communication using a 120kHz interval, K2 may correspond to 36 symbols.

[0139] Wireless communication system 100 may support conditional HARQ retransmission across carriers. For example, the described techniques provide that UE 115 or network entity 105, or both, support conditional cross-carrier HARQ retransmission. In some aspects, UE 115 may send a capability message to network entity 105 to indicate that UE 115 supports the capability of cross-carrier HARQ retransmission. The capability message may indicate that UE 115 is capable of sending uplink cross-carrier HARQ retransmission, receiving downlink cross-carrier HARQ retransmission, or both. UE 115 or network entity 105 may send an initial message on a first component carrier. UE 115 or network entity 105 may retransmit the message on a second component carrier, different from the first component carrier, based on the availability of resources for retransmitting the message, based on the capability of UE 115, and based on the satisfaction of a threshold condition for cross-carrier HARQ retransmission by one or more conditions associated with the communication performed by UE 115. If available resources exist on the second component carrier for the retransmission, and if UE 115 supports cross-carrier HARQ retransmission capability, and if these conditions meet the threshold conditions, cross-carrier HARQ retransmission may be enabled or supported. If no available resources exist on the second component carrier for the retransmission, and if UE 115 does not support cross-carrier HARQ retransmission capability, or if these conditions do not meet the threshold conditions, or any combination thereof, the device may avoid retransmission on the second component carrier and may instead retransmit the message on the first component carrier. For uplink communication, UE 115 may perform transmission and conditional retransmission. For downlink communication, network entity 105 may perform transmission and conditional retransmission.

[0140] Figure 2 An example of a wireless communication system 200 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated. Wireless communication system 200 may implement, or be implemented by, aspects of wireless communication system 100. For example, wireless communication system 200 includes network entity 105-a and UE 115-a, which may be represented as referenced... Figure 1 Examples of network entity 105 and UE 115 described herein. Network entity 105-a and UE 115-a may communicate within a geographic coverage area 110-a and via one or more communication links 220 and 225, which may represent examples of component carriers or cells in some examples herein. In this example, network entity 105-a and UE 115-a may utilize one or more rules or procedures to determine when to perform cross-carrier HARQ retransmission.

[0141] Wireless communication system 200 may support HARQ feedback and data retransmission to increase the likelihood of successful data reception. HARQ may include a combination of error detection (e.g., using CRC), FEC, and retransmission. For example, network entity 105-a may send message 240 (e.g., a downlink message) to UE 115-a via communication link 220. UE 115-a may monitor message 240. UE 115-a may send a feedback message 250 in response to message 240. Feedback message 250 may be a HARQ feedback message indicating whether downlink message 240 has been correctly received and decoded by UE 115-a. If feedback message 250 indicates ACK, message 240 may have been received and decoded by UE 115-a. If feedback message 250 indicates NACK, message 240 may not have been received and / or decoded by UE 115-a. Network entity 105-a may send a retransmission 245 of message 240 based on feedback message 250. For example, NACK can trigger or indicate a request to resend message 240.

[0142] HARQ retransmission can be similarly applied to uplink communication. For example, UE 115-a may send message 240 to network entity 105-a. If network entity 105-a does not receive or decode message 240, network entity 105-a may send feedback in the form of an uplink grant or other message indicating the resources scheduled for retransmission 245 of message 240. Therefore, UE 115-a may send retransmission 245.

[0143] In some examples, a retransmission 245 of message 240 may be performed on the same component carrier or the same cell as the initial transmission of message 240. For example, UE 115-a may transmit message 240 via communication link 220 (e.g., the primary cell (PCell)) and may also transmit retransmission 245 via the same communication link 220. In such cases, the device may wait for the next available or unused transmission opportunity on the component carrier to perform retransmission 245, which may increase latency and reduce communication throughput and reliability. That is, the TDD mode used for HARQ retransmission 245 may increase latency, which may impair latency and reliability (e.g., for key performance indicators (KPIs) in some scenarios such as extended reality communications and applications).

[0144] To shorten the retransmission time of HARQ retransmission 245, some devices can support HARQ retransmission 245 on different component carriers. In such cases, the device can utilize the nearest or earliest uplink opportunity (e.g., available transmission opportunity) for uplink transmission on any carrier and the nearest or earliest downlink opportunity (e.g., available transmission opportunity) for downlink transmission on any carrier to reduce latency. The initial message 240 can be transmitted on the first component carrier. In cases where the next available transmission opportunity is on a different component carrier, in some examples, the associated HARQ retransmission 245 can be transmitted on the different component carriers to reduce latency (e.g., to avoid waiting for the next available transmission opportunity on the first carrier). Figure 2 In the example, UE 115-a may transmit message 240 (e.g., first physical uplink shared channel (PUSCH)) on the first communication link 220 (e.g., first component carrier or PCell) and may transmit a retransmission 245 of message 240 on the second communication link 225 (e.g., second component carrier or secondary cell (SCell), or some other type of cell).

[0145] In some cases, generating and transmitting retransmissions 245 on component carriers different from the initial transmission can increase complexity, processing, and power consumption. For example, cross-carrier retransmissions 245 can affect modem firmware because, for some devices and communication systems, HARQ-related operations can be specified according to component carriers. Additionally or alternatively, the time period used to construct or generate a transmission (e.g., PUSCH processing and preparation time, or Physical Downlink Shared Channel (PDSCH) processing and preparation time) and HARQ buffer limitations can be relatively large for cross-carrier retransmissions compared to retransmissions on the same carrier. In some examples, implementations by receiving devices (such as network entity 105 in the case of uplink communication) can be affected by cross-carrier retransmissions 245 due to, for example, combining soft values ​​on different component carriers. Therefore, constant cross-carrier retransmissions 245 can negatively impact communication throughput, reliability, and efficiency.

[0146] The technologies, systems, and devices described herein provide conditions and protocols for defining when cross-carrier HARQ retransmission 245 can be performed. This allows devices to achieve reduced latency in some scenarios by using cross-carrier retransmission 245, while maintaining an average reduction in processing complexity and power consumption across multiple communication scenarios. As described herein, granting retransmission 245 can be granted for the same cell or different cells based on the capabilities of UE 115-a, the availability of resources for retransmission 245, and one or more conditions associated with communication performed by UE 115-a as indicated via UE assistance information 235 and other UE feedback, satisfying corresponding threshold conditions.

[0147] UE 115-a may support cross-carrier HARQ retransmission capability 255, which indicates that UE 115-a can transmit and / or receive retransmissions of message 240 on a different component carrier than the component carrier used for transmitting and / or receiving message 240. Cross-carrier HARQ retransmission capability 255 may be based on the configuration of UE 115-a (e.g., it may be predefined or configured during manufacturing). UE 115-a may send a capability message 230 to network entity 105-a, indicating whether UE 115-a supports cross-carrier HARQ retransmission capability 255. In some examples, for uplink communication, UE 115-a may report via capability message 230 how quickly UE 115-a can build up the PUSCH retransmission capability 245 on different component carriers. For example, the auxiliary information element (IE) in capability message 230 (e.g., UEinformationCapabilityIE, or some other IE) can be configured to indicate the uplink transmission preparation period supported by UE 115-a, and can assist network entity 105-a in determining or deciding whether to enable cross-carrier retransmission 245 or schedule a handover between component carriers for retransmission 245 performed by UE 115-a.

[0148] UE 115-a may send UE assistance information 235 to network entity 105-a to indicate one or more parameters associated with communications performed by UE 115-a. These parameters may include processing time associated with retransmissions performed by UE 115-a (e.g., processing time for constructing PUSCH retransmission 245 on different component carriers), the status associated with UE 115-a's HARQ buffer (e.g., HARQ buffer limits), the number of loops loaded at UE 115-a, the number of processors loaded at UE 115-a, one or more other parameters, or any combination thereof. In some examples, assistance information 235 may additionally or alternatively indicate a request to enable cross-carrier HARQ retransmission 245. That is, UE 115-a may explicitly request the enabling or disabling of the HARQ cross-carrier retransmission feature based on one or more parameters or metrics at UE 115-a (such as internal processor load at UE 115-a, or some other parameter). UE assistance information 235 can be transmitted via RRC signaling, via UCI, via MAC-CE, or any combination thereof. In some examples, parameters associated with communications performed by UE 115-a can change relatively quickly (e.g., processing load, uplink packet latency, etc.). In such cases, MAC-CE or UCI transmission of assistance information 235 can help reduce the latency of reporting parameters.

[0149] In some examples, UE 115-a may determine its uplink Packet Data Convergence Protocol (PDCP) queuing delay, which may correspond to the delay between packet arrival at the PDCP layer and uplink granting for packet transmission. UE 115-a may compare the uplink PDCP queuing delay with a threshold PDCP queuing delay. Network entity 105-a may send control signaling configuring the threshold uplink PDCP queuing delay for cross-carrier retransmission 245. UE 115-a may send a UCI to network entity 105-a to indicate whether the uplink PDCP queuing delay exceeds the threshold. In some examples, the UCI may include or represent an example of auxiliary information 235 (e.g., the UCI may be multiplexed on the same initial PUSCH or Physical Uplink Control Channel (PUCCH) to indicate UE feedback).

[0150] If the uplink PDCP queuing delay exceeds a threshold, an uplink grant may be conditionally granted to UE 115-a on the component carrier used for the handover of HARQ retransmission 245 (e.g., if the condition is true, UE feedback may favor component carrier handover). For example, if packets have been in UE 115-a's buffer for a relatively long period, network entity 105-a may send an uplink grant to UE 115-a on the serving cell to indicate the earliest transmission timing, which may be the transmission timing for retransmission 245 on the second component carrier (e.g., communication link 225). If the uplink PDCP queuing delay does not exceed the threshold, network entity 105-a may schedule retransmission 245 on the same component carrier as the initial transmission of message 240 (e.g., if the condition is false, UE feedback may be unfavorable to handover between component carriers).

[0151] In some examples, network entity 105-a may send control messages or other signaling to UE 115-a to configure a threshold uplink delay budget (e.g., a delay limit threshold) for cross-carrier retransmission 245. UE 115-a may dynamically (e.g., at one or more periodic or semi-periodic time intervals) compare the remaining uplink delay budget at UE 115-a with the threshold uplink delay budget. UE 115-a may send an indication to network entity 105-a indicating whether the remaining uplink delay budget exceeds the threshold. This indication may be delivered via UE assistance information 235 or some other message sent by UE 115-a (e.g., a one-bit indication indicating whether the threshold uplink delay budget is satisfied). If the threshold uplink delay budget is satisfied, the conditions may favor cross-carrier HARQ retransmission 245. For example, if UE 115-a indicates that the remaining uplink delay budget at UE 115-a exceeds a threshold, network entity 105-a may send an uplink grant that schedules a retransmission 245 during the earliest available transmission opportunity to reduce latency, which may be on a different component carrier.

[0152] Therefore, if the earliest available transmission opportunity is on a different component carrier, if one or more configuration conditions at UE 115-a are met, and if UE 115-a supports cross-carrier HARQ retransmission capability 255, then network entity 105-a can send a dynamic grant that schedules the retransmission 245 of message 240 performed by UE 115-a on a different component carrier. If all these conditions are met, cross-carrier retransmission 245 can reduce latency and improve communication reliability. If the conditions are not met, or if UE 115-a does not support cross-carrier HARQ retransmission capability 255, then cross-carrier retransmission 245 may not contribute to communication reliability, and network entity 105-a may instead schedule retransmission 245 on the same carrier as the initial message 240.

[0153] In some examples, network entity 105-a may send control signaling to UE 115-a to configure one or more configuration grants. A configuration grant may indicate resources allocated on one or more cells for transmissions and retransmissions 245 performed by UE 115-a. UE 115-a may autonomously perform retransmissions 245 at the earliest available transmission opportunity, including the configuration grant resources. If the earliest opportunity is on a different component carrier than the initial transmission, UE 115-a may determine whether to switch to a different component carrier based on UE capabilities and one or more conditions, as described in further detail elsewhere herein, including references. Figure 4 .

[0154] For downlink communication, network entity 105-a may determine whether to retransmit message 240 on a different component carrier based on parameters indicated via capability message 230 and UE assistance information 235 compared to the threshold parameters described herein, based on UE capabilities, and based on the availability of resources for cross-carrier retransmission. If the earliest available transmission opportunity is on a different component carrier, if one or more configuration conditions at UE 115-a are met, and if UE 115-a supports cross-carrier HARQ retransmission capability 255, then network entity 105-a may send a dynamic grant that schedules the retransmission 245 of message 240 performed by network entity 105-a on a different component carrier. If all these conditions are met, cross-carrier retransmission 245 can reduce latency and improve communication reliability. If the conditions are not met, or if UE 115-a does not support cross-carrier HARQ retransmission capability 255, then cross-carrier retransmission 245 may not contribute to communication reliability, and network entity 105-a may instead schedule retransmission 245 on the same carrier as the initial message 240.

[0155] In some examples, network entity 105-a may indicate a semi-static handover mode for switching between component carriers. This mode may indicate, for example, the number of retransmissions 245 that can be performed for a given message 240, and the pattern of component carriers that can be followed when performing retransmissions 245. In such cases, UE 115-a and network entity 105-a may switch between carriers used for retransmissions 245 according to this mode, as described in further detail elsewhere herein, including references to... Figure 3 .

[0156] Therefore, for both uplink and downlink communications, UE 115-a and network entity 105-a can support conditional cross-carrier HARQ retransmission 245. By following the described protocol for determining whether and when to switch component carriers for retransmission, the devices can balance reduced latency with reduced processing complexity and power consumption to improve communication throughput and reliability.

[0157] Figure 3 Examples of HARQ transmission timelines 300 supporting cross-carrier conditional HARQ retransmissions according to one or more aspects of this disclosure are illustrated. In some examples, the HARQ transmission timeline 300 may implement, or be implemented by, aspects of wireless communication systems 100 and 200. For example, the HARQ transmission timeline 300 illustrates a timeline for HARQ retransmissions across different component carriers or cells (e.g., PCell 320 and SCell 325). The HARQ transmission timeline 300 may be applicable to uplink communication, downlink communication, or both between UE 115 and network entity 105, which may represent, as referenced... Figure 1and Figure 2 Examples of UE 115 and network entity 105 as described.

[0158] In applications such as uplink communication Figure 3 In this example, UE 115 may communicate with network entity 105 via one or more cells (including PCell 320 and SCell 325). UE 115 may receive control messages or grants via the Physical Downlink Control Channel (PDCCH) 310-a on PCell 320. Network entity 105 may send uplink grants or some other control message via PDCCH 310-a. PDCCH 310-a may indicate the transmission timing 305 for the transmission of message 315 by UE 115. Transmission timing 305 may represent a set of one or more time and frequency resources allocated or reserved on PCell 320 for the transmission of message 315. In this example, message 315 may fail. For example, network entity 105 may not receive message 315, or message 315 may be corrupted due to interference or other factors. Based on the failure of message 315, network entity 105 may send a second PDCCH 310-b, which carries a second uplink grant or other control message allocating time and frequency resources for HARQ retransmission 330 within a second transmission timing 305. As part of the HARQ procedure, UE 115 may retransmit message 315 as HARQ retransmission 330 based on PDCCH 310-b to improve throughput and reliability.

[0159] In some cases, such as reference Figure 2As described, UE 115 may retransmit message 315 on PCell 320 (e.g., on the same cell or component carrier). If transmission opportunity 305 is available on a different cell (such as SCell 325) and is earlier than the available transmission opportunity 305 on PCell 320, UE 115 may reduce latency when switching carriers to perform retransmission. However, cross-carrier HARQ retransmission 330 may increase processing and preparation latency, may increase complexity and power consumption, and may reduce reliability. For example, in some examples, cross-carrier HARQ retransmission 330 may increase UE complexity, may increase the delay in constructing or generating PUSCH or PDSCH messages, and may increase HARQ buffer limitations. Additionally or alternatively, in some examples, considering that HARQ-related operations can be specified according to component carriers, cross-carrier HARQ retransmission 330 may affect the modem firmware at UE 115, network entity 105, or both. In some examples, cross-carrier HARQ retransmissions 330 may affect the implementation at network entity 105 (e.g., gNB implementation) due to the combination of soft values ​​on different carriers, for example, at network entity 105. Therefore, reducing cross-carrier HARQ retransmissions 330 to balance reduced latency with improved reliability and throughput and reduced processing complexity can be beneficial.

[0160] The technologies, systems, and devices described herein define the conditions and protocols for performing cross-carrier or cross-cell HARQ retransmission 330. As described herein, if a UE 115, which is receiving or transmitting a message, supports the capability for cross-carrier HARQ retransmission, and if one or more conditions associated with the communication performed by the UE 115 meet threshold conditions, and based on the availability of resources for cross-carrier retransmission, uplink or downlink messages can be retransmitted on different component carriers. UE capabilities and feedback may represent examples of capability message 230, auxiliary information 235, and one or more other messages, as described in further detail elsewhere herein, including references to Figure 2 UE 115 may send capability messages and auxiliary information before or at the same time as PDCCH 310-a, message 315, PDCCH 310-b or any combination thereof.

[0161] For uplink communication, UE 115 may transmit a first message 315 as an uplink message on PCell 320 (e.g., a first component carrier). The first message 315 may be sent to network entity 105 via a scheduled transmission timing 305, which may be a set of time and frequency resources allocated for the transmission of message 315. Message 315 may be scheduled by an uplink grant transmitted via PDCCH 310-a (e.g., a previous transmission timing 305).

[0162] If the first message 315 fails (e.g., if network entity 105 does not receive and / or decode message 315), UE 115 may send a HARQ retransmission 330. Figure 3 In the example, HARQ retransmission 330 can be transmitted on a different component carrier than the initial message 315. For example, message 315 can be transmitted on PCell 320, and retransmission 330 can be transmitted on SCell 325. UE115 can perform cross-carrier HARQ retransmission based on UE115's ability to support cross-carrier retransmission, based on UE feedback indicating that one or more conditions associated with communication performed by UE115 meet threshold conditions, and based on the availability of uplink resources or transmission timing 305.

[0163] In some examples, UE 115 may be conditionally granted an uplink grant on the carrier used for the handover to HARQ retransmission 330. Network entity 105 may determine that the conditions for cross-carrier retransmission are met and may send the uplink grant via PDCCH 310-b, which schedules or allocates the set of time and frequency resources in transmission opportunity 305 for retransmission 330 on SCell 325. In some examples, transmission opportunity 305 on SCell 325 may be the most recent or earliest available transmission opportunity. For example, the next consecutive transmission opportunity after PDCCH 310-b on PCell 320 may not be available, and network entity 105 may determine to schedule cross-carrier retransmission 330 to reduce latency. Network entity 105 may determine that a condition is met based on capability messages received from UE 115, auxiliary information received from UE 115, one or more other messages received from UE 115 indicating conditions associated with communication at UE 115, and a set of threshold conditions configured for cross-carrier retransmission.

[0164] In some other examples, network entity 105 may be configured with a set of configuration grant resources for transmissions made by UE 115. In such cases, UE 115 may autonomously perform cross-carrier retransmissions during the configuration grant resource period based on the satisfaction of conditions for cross-carrier retransmissions, as described in further detail elsewhere herein, including references to Figure 4 .

[0165] For downlink communication, network entity 105 may transmit a first message 315 as a downlink message on PCell 320 (e.g., a first component carrier). The first message 315 may be transmitted to UE 115 via a scheduled transmission timing 305, which may be a set of time and frequency resources allocated for the transmission of message 315. Message 315 may be scheduled by dynamic granting via PDCCH 310-a (e.g., a previous transmission timing 305).

[0166] If the first message 315 fails (e.g., if UE 115 does not fully receive and / or decode message 315), network entity 105 may send a HARQ retransmission 330. Figure 3 In some examples, HARQ retransmission 330 may be sent on a different component carrier than the initial message 315. For example, message 315 may be sent on PCell 320, and retransmission 330 may be sent on SCell 325. Network entity 105 may perform cross-carrier HARQ retransmission based on UE 115's ability to support cross-carrier retransmission, based on UE feedback indicating that one or more conditions associated with communication performed by UE 115 meet threshold conditions, and based on the availability of uplink resources or transmission timing 305. In some examples, UE 115 may respond to message 315 by sending a NACK or other feedback message indicating that message 315 was not correctly received and / or decoded. NACK may be used to prompt network entity 105 to perform retransmission 330.

[0167] Network entity 105 may conditionally grant resources on SCell 325 for cross-carrier HARQ retransmission 330. Network entity 105 may determine that the conditions for cross-carrier retransmission are met and may send a dynamic grant (e.g., DCI) via PDCCH 310-b, which schedules or allocates a set of time and frequency resources in transmission opportunity 305 on SCell 325 for retransmission 330. In some examples, transmission opportunity 305 on SCell 325 may be the most recent or earliest available transmission opportunity. For example, the next consecutive transmission opportunity after PDCCH 310-b on PCell 320 may be unavailable, and network entity 105 may determine to schedule cross-carrier retransmission 330 to reduce latency. Network entity 105 may determine that a condition is met based on capability messages received from UE 115, auxiliary information received from UE 115, one or more other messages received from UE 115 indicating conditions associated with communication at UE 115, and a set of threshold conditions configured for cross-carrier retransmission.

[0168] In some examples, the number of retransmissions 330 performed by network entity 105 for downlink communication, by UE 115 for uplink communication, or both may be limited (e.g., for communication flows with relatively tight delay budgets, such as extended reality). In such cases, network entity 105 may send control signaling to UE 115 configuring a semi-static handover mode for the initial transmission of retransmissions 330 and message 315. For example, if the packet delay budget is ten milliseconds, a single retransmission 330 may be performed in addition to the initial transmission, and the semi-static handover mode may be PCell 320 to SCell 325 (e.g., PCC-SCC). In some other examples, multiple retransmissions 330 may be permitted, and the semi-static handover mode may indicate the mode for one or more different cells for each transmission. Figure 3 In the example, network entity 105 may configure a semi-static handover mode (e.g., via RRC signaling or some other type of signaling) before sending PDCCH310-a. The semi-static handover mode may be PCell 320 to SCell 325, such that the initial message 315 is sent on PCell 320, and UE 115 knows to switch to SCell 325 to perform a retransmission 330 for uplink communication or to monitor a retransmission 330 for downlink communication.

[0169] If network entity 105 is configured with a semi-static handover mode for cross-carrier HARQ retransmission 330, network entity 105 may repurpose one or more fields or bits in PDCCH 310-b. For example, a DCI transmitted via PDCCH 310-b may indicate that retransmission 330 will occur, but may not indicate the carrier used for retransmission 330, because UE 115 may know that the carrier is SCell 325 based on the semi-static handover mode. Therefore, one or more bits configured for carrier indication (e.g., the “carrier indicator” field) may be repurposed for some other indication or information. For example, network entity 105 may include additional bits for one or more other fields in the DCI, such as additional time-domain resource allocation information, additional frequency-domain resource allocation information, or some other type of information for UE 115.

[0170] As described herein, network entity 105 and UE 115 can thus perform conditional cross-carrier HARQ retransmission 330. By defining threshold conditions and protocols for when to perform cross-carrier HARQ retransmission 330, the device can perform cross-carrier HARQ retransmission for latency-reduced communications or communication flows associated with relatively low latency and / or high priority, and in other scenarios, the device can reduce processing complexity and power consumption by performing HARQ retransmission on the same carrier.

[0171] Figure 4 An example of a HARQ transmission timeline 400 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated. The HARQ transmission timeline 400 can be implemented as described in the reference... Figures 1 to 3 The described wireless communication systems 100 and 200 and HARQ transmission timeline 300 are aspects of, or implemented by, these aspects. For example, HARQ transmission timeline 400 illustrates a timeline for HARQ retransmissions across different component carriers or cells (e.g., PCell 420 and SCell 425). HARQ transmission timeline 400 can be applied to uplink communication between UE 115 and network entity 105, which can be represented as shown in reference. Figures 1 to 3 Examples of UE 115 and network entity 105 as described.

[0172] In this example, network entity 105 may send a control message, such as RRC configuration or some other type of control signaling, that configures one or more configuration grant resources 410 across one or more of PCell 420 and SCell 425. The configuration grant resource 410 may be time and frequency resources allocated for uplink transmissions performed by UE 115 in one or more transmission times 405. The control message may instruct UE 115 on the time and frequency resource allocation for the configuration grant resource 410.

[0173] If UE 115 receives an indication to grant configuration resource 410, UE 115 may autonomously perform transmission and retransmission based on one or more conditions and / or capabilities of UE 115 (e.g., whether a dynamic grant has been received or not received from network entity 105 via DCI or other PDCCH). For example, UE 115 may transmit message 415 (e.g., first message 415) via a first available transmission opportunity 405 including the configuration grant resource 410. In this example, the first message 415 may be transmitted on PCell 420. If the first message fails (e.g., is not correctly transmitted, received, or decoded), UE 115 may transmit a HARQ retransmission 430 in the next available transmission opportunity 405.

[0174] exist Figure 4In the example, the next available transmission opportunity 405 following the first message 415, including the configuration grant resource 410, may be on SCell 425 (e.g., the transmission opportunity 405 on PCell 420 may be reserved for other communications or otherwise unavailable for configuration grant resource 410). As described herein, if one or more conditions for cross-carrier HARQ retransmission 430 are met, UE 115 may autonomously determine to perform cross-carrier retransmission 430 via the next or earliest available configuration grant resource 410 on SCell 425.

[0175] If UE 115 does not support cross-carrier HARQ retransmission capability, UE 115 may not perform cross-carrier HARQ retransmission 430, and UE 115 may instead wait until the next available transmission opportunity 405, including configuration grant resource 410, occurs on PCell 420. However, if UE 115 does support cross-carrier HARQ retransmission capability, UE 115 may compare one or more parameters indicating the conditions for communication at UE 115 with one or more thresholds for cross-carrier HARQ retransmission. These conditions may be, for example, UE 115's uplink delay limits, UE 115's retransmission preparation timing capability, the processing time supported by UE 115, HARQ buffer state, the number of loaded loops or processors at UE 115, PDCP queuing delay at UE 115, or any combination thereof. If UE 115 determines that one or more of the conditions meet the corresponding threshold conditions, and UE 115 supports cross-carrier HARQ retransmission capability, then UE 115 may switch to SCell 425 to send HARQ retransmission 430 via configuration grant resource 410. UE 115 may receive control signaling indicating or configuring these conditions and corresponding thresholds, as described in further detail elsewhere herein, including references to Figure 2 .

[0176] UE 115 can thus autonomously determine, based on UE capabilities and one or more conditions as described herein, whether to retransmit the message on the same component carrier as the initial transmission or on a different component carrier. By limiting or reducing cross-carrier retransmissions, UE 115 can reduce processing complexity and power consumption, while still supporting cross-carrier retransmissions when beneficial for relatively low-latency communications.

[0177] Figure 5 An example of a process flow 500 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated. Process flow 500 can be implemented as described in the reference. Figures 1 to 4The described wireless communication systems 100 and 200 and HARQ transmission timelines 300 and 400 are aspects of, or implemented by, these aspects. For example, process flow 500 illustrates communication between UE 115-b and network entity 105-b, which can be represented as shown in reference. Figures 1 to 4 An example of UE 115 and network entity 105 is described. In this example, UE 115-b may retransmit the message to network entity 105-b on a different component carrier than the initial transmission of the message, based on the capabilities of UE 115-b and one or more conditions associated with the communication performed by UE 115-b.

[0178] In the following description of process flow 500, the operations between UE 115-b and network entity 105-b may be performed in a different order or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although UE 115-b and network entity 105-b are shown as performing the operations of process flow 500, some aspects of some operations may also be performed by one or more other wireless devices.

[0179] At position 505, UE 115-b may send a capability message to network entity 105-b. This capability message indicates that UE 115-b supports cross-carrier HARQ retransmission capability. In this example, UE 115-b may support retransmission of messages on different component carriers (e.g., retransmission on a component carrier different from the one used for the initial transmission). This capability message may represent, as referenced... Figure 2 Example of the described capability message 230. In some examples, the capability message may convey an indication of the time period associated with the retransmission of the preparation message on a different component carrier, or an indication of the processing time associated with the retransmission performed by UE 115-b on a different component carrier, or both.

[0180] At 510, in some examples, UE 115-b may send auxiliary information to network entity 105-b. This auxiliary information may indicate one or more parameters associated with communication performed by UE 115-b (e.g., communication between UE 115-b and network entity 105-b, or communication between UE 115-b and one or more other devices). These parameters may include, for example, processing time associated with retransmissions performed by UE 115-b, the state associated with the HARQ buffer at UE 115-b, the number of loops loaded at UE 115-b, the number of processors loaded at UE 115-b, or any combination thereof. This auxiliary information may be sent, for example, via an RRC message. Additionally or alternatively, these parameters may be sent via UCI, via MAC-CE, or any combination thereof. In some examples, the parameters or criteria may change relatively quickly. Therefore, UCI or MAC-CE can be relatively faster (e.g., more frequent) than RRC messages, which can reduce the latency associated with notifying network entity 105-b of the conditions at UE115-b.

[0181] At position 515, UE 115-b may transmit a message to network entity 105-b on the first component carrier. This message may be an uplink message. In some examples, the first component carrier may be associated with a first cell (such as PCell) or some other type of cell. UE 115-b may transmit the message via a transmission timing, which may be a set of time and frequency resources allocated for message transmission. This transmission timing may be scheduled or allocated by uplink grants received from network entity 105-b (e.g., DCI received via PDCCH), as referenced. Figure 3 As described. Additionally or alternatively, the timing of this transmission may be scheduled by some other configuration of periodic or semi-periodic resources granted or allocated for transmissions performed by UE 115-b, as referenced. Figure 3 and Figure 4 As described.

[0182] At 520, in some examples, UE 115-b may receive an uplink grant from network entity 105-b. This uplink grant may indicate a failure of the message transmitted on the first component carrier and may indicate a second set of time and frequency resources for retransmission of the message by UE 115-b. In some examples, network entity 105-b may send the uplink grant and schedule the retransmission of the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, based on UE 115-b's ability to support cross-carrier HARQ retransmission, and based on one or more conditions associated with the communication by UE 115-b satisfying threshold conditions for cross-carrier HARQ retransmission. For example, if each of the above conditions and thresholds is satisfied, network entity 105-b may schedule the retransmission of the message on a different (second) component carrier. If any or more of the conditions are not satisfied, network entity 105-b may schedule the retransmission on the same (first) component carrier.

[0183] At 525, UE 115-b may retransmit the message to network entity 105-b on a second component carrier, different from the first component carrier, based on the satisfaction of conditions for cross-carrier retransmission. Conditions for cross-carrier retransmission may include the availability of resources for retransmitting the message, UE 115-b's ability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by UE 115-b satisfying threshold conditions for cross-carrier HARQ retransmission. In some examples, UE 115-b may retransmit the message on the second component carrier based on an uplink grant received at 520. Additionally or alternatively, UE 115-b may receive control messages, such as RRC messages or some other type of control message, that allocate multiple configuration grant resources for transmission and retransmission performed by UE 115-b, as referenced. Figure 3 and Figure 4 As described. In such cases, UE 115-b may proactively determine to retransmit the message on the second component carrier based on the available configuration, the granted resource set, and the satisfaction of conditions for cross-carrier retransmission. In some other examples, network entity 105-b may send a control message indicating a semi-static handover mode for the initial transmission and retransmission of uplink messages. UE 115-b may proactively determine to retransmit the message on the second component carrier based on the semi-static handover mode and the satisfaction of one or more conditions.

[0184] Threshold conditions for cross-carrier HARQ retransmission may include a threshold uplink delay budget, a retransmission preparation time threshold, a processing time threshold, a threshold HARQ buffer state, a threshold number of cycles loaded at UE 115-b, a threshold number of processors loaded at UE 115-b, one or more other threshold conditions, or any combination thereof. UE 115-b may indicate the conditions at UE 115-b to network entity 105-b via a capability message, via auxiliary information, or via one or more other uplink messages. Network entity 105-b, UE 115-b, or both may compare these conditions with threshold conditions to determine whether the threshold conditions are met.

[0185] The techniques described herein enable UE 115-b to perform cross-carrier HARQ retransmission when one or more conditions are met, otherwise perform retransmission on the same carrier. By utilizing the defined conditions for cross-carrier HARQ retransmission, UE 115-b can support retransmissions with reduced latency in some scenarios where they are beneficial, while balancing reduced complexity and power consumption with improved overall reliability.

[0186] Figure 6 An example of a process flow 600 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is illustrated. Process flow 600 can be implemented as described in the references. Figures 1 to 4 The described wireless communication systems 100 and 200 and HARQ transmission timelines 300 and 400 are aspects of, or implemented by, these aspects. For example, process flow 600 illustrates communication between UE 115-c and network entity 105-c, which can be represented as shown in reference. Figures 1 to 5 An example of UE 115 and network entity 105 is described. In this example, network entity 105-c may retransmit the message to UE 115-c on a different component carrier than the initial transmission of the message, based on the capabilities of UE 115-c and one or more conditions associated with the communication performed by the device.

[0187] In the following description of process flow 600, the operations between UE 115-c and network entity 105-c may be performed in a different order or at different times. Some operations may also be excluded from process flow 600, or other operations may be added. Although UE 115-c and network entity 105-c are shown as performing the operations of process flow 600, some aspects of some operations may also be performed by one or more other wireless devices.

[0188] At position 605, UE 115-c can send a capability message indicating that UE 115-c supports cross-carrier HARQ retransmission. In this example, UE 115-c can support retransmission of messages on different component carriers. This capability message can be represented as shown in the reference. Figure 2 The described capability message 230 and reference Figure 5 Examples of the described capability messages. In some examples, the capability message may convey an indication of the time period associated with the retransmission of the prepared message on a different component carrier, or an indication of the processing time associated with the retransmission on a different component carrier, or both.

[0189] At 610, in some examples, UE 115-c may send auxiliary information to network entity 105-c. This auxiliary information may indicate one or more parameters associated with communication performed by UE 115-c (e.g., communication between UE 115-c and network entity 105-c, or communication between UE 115-c and one or more other devices). These parameters may include, for example, processing time associated with retransmissions performed by UE 115-c, the state associated with the HARQ buffer at UE 115-c, the number of loops loaded at UE 115-c, the number of processors loaded at UE 115-c, or any combination thereof. This auxiliary information may be sent via RRC messages, via UCI, via MAC-CE, or any combination thereof. In some examples, the parameters or criteria may change relatively quickly. UCI or MAC-CE may be faster than RRC messages, which can reduce the latency associated with notifying network entity 105-c of the conditions at UE 115-c.

[0190] At point 615, network entity 105-c may send a message to UE 115-c on the first component carrier. This message may be a downlink message. In some examples, the first component carrier may be associated with a first cell (such as PCell) or some other type of cell. Network entity 105-c may send the message via a transmission timing, which may be a set of time and frequency resources allocated for message transmission. This transmission timing may be scheduled or allocated by dynamic grants (e.g., DCI received via PDCCH) from network entity 105-c to UE 115-c, as referenced. Figure 3 As described. Additionally or alternatively, the timing of this transmission may be scheduled by control signaling indicating some other configuration of periodic or semi-periodic resources allocated for transmissions performed by network entity 105-c, as referenced. Figure 3 and Figure 4 As described.

[0191] In some examples, UE 115-c may send a feedback message to network entity 105-c in response to the message on the first component carrier. For example, UE 115-c may monitor the message but may not receive it, or UE 115-c may fail to accurately receive or decode the message. In such cases, UE 115-c may send a NACK indicating the failure of the message. The NACK may implicitly indicate a request for retransmission of the message.

[0192] At 620, in some examples, network entity 105-c may send an grant (e.g., a dynamic grant) to UE 115-c. A dynamic grant may indicate a second set of time and frequency resources for retransmission of the message by network entity 105-c. In some examples, network entity 105-c may send a dynamic grant and schedule the retransmission of the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, based on UE 115-c's ability to support cross-carrier HARQ retransmission, and based on one or more conditions associated with the communication by UE 115-c satisfying threshold conditions for cross-carrier HARQ retransmission. For example, if each of the above conditions and thresholds is satisfied, network entity 105-c may schedule the retransmission of the message on a different (second) component carrier. If any one or more of the conditions are not satisfied, network entity 105-c may schedule the retransmission on the same (first) component carrier. In some examples, network entity 105-c may send an grant based on or in response to feedback indicating NACK from UE 115-c.

[0193] At 625, network entity 105-c may retransmit the message to UE 115-c on a second component carrier different from the first component carrier based on the satisfaction of conditions for cross-carrier retransmission. Conditions for cross-carrier retransmission may include the availability of resources for retransmitting the message, the ability of UE 115-c to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by UE 115-c satisfying threshold conditions for cross-carrier HARQ retransmission. In some examples, network entity 105-c may retransmit the message on the second component carrier via a transmission timing based on a dynamic grant sent at 520 or allocated by such dynamic grant. Additionally or alternatively, network entity 105-c may (e.g., before transmitting the message on the first component carrier) send a control message to UE 115-c, such as an RRC message or some other type of control message, indicating a semi-static handover mode for the initial transmission and retransmission of downlink messages, as referenced. Figure 3 and Figure 4As described. In such cases, UE 115-c can autonomously determine whether to monitor the retransmission of this message on the second component carrier based on the satisfaction of the conditions for cross-carrier retransmission and the semi-static handover mode.

[0194] Threshold conditions for cross-carrier HARQ retransmission may include a threshold uplink delay budget, a retransmission preparation time threshold, a processing time threshold, a threshold HARQ buffer state, a threshold number of cycles loaded at UE 115-c, a threshold number of processors loaded at UE 115-c, one or more other threshold conditions, or any combination thereof. UE 115-c may indicate the conditions at UE 115-c to network entity 105-c via a capability message, via auxiliary information, or via one or more other uplink messages. Network entity 105-c, UE 115-c, or both may compare these conditions with threshold conditions to determine whether the threshold conditions are met.

[0195] The techniques described herein enable network entity 105-c to perform cross-carrier HARQ retransmission when one or more conditions are met, otherwise perform retransmission on the same carrier. By utilizing the defined conditions for cross-carrier HARQ retransmission, network entity 105-c and UE 115-c can support retransmission with reduced latency in some scenarios where it is beneficial, while balancing reduced complexity and power consumption with improved overall reliability.

[0196] Figure 7 A block diagram 700 illustrates an apparatus 705 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. Apparatus 705 may be an example of various aspects of UE 115 as described herein. Apparatus 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Apparatus 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0197] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier conditional HARQ retransmission). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0198] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier conditional HARQ retransmission). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0199] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0200] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0201] Additionally or alternatively, in some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0202] In some examples, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0203] Based on the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured as, or otherwise support, a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 720 may be configured as, or otherwise support, a component for transmitting a message on a first component carrier. The communication manager 720 may be configured as, or otherwise support, a component for retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability of cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0204] Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured as or otherwise support a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 720 may be configured as or otherwise support a component for receiving a message on a first component carrier. The communication manager 720 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0205] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720, or a combination thereof or a processor otherwise coupled thereto) can support techniques for reducing processing, lowering power consumption, and utilizing communication resources more efficiently.

[0206] Figure 8A block diagram 800 illustrates a device 805 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. Device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0207] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier conditional HARQ retransmission). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0208] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to cross-carrier conditional HARQ retransmission). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0209] Device 805 or its various components may be examples of parts for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, communication manager 820 may include cross-carrier HARQ capability component 825, HARQ component 830, HARQ cross-carrier retransmission component 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0210] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. A cross-carrier HARQ capability component 825 may be configured as or otherwise support a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. A HARQ component 830 may be configured as or otherwise support a component for transmitting a message on a first component carrier. A HARQ cross-carrier retransmission component 835 may be configured as or otherwise support a component for retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0211] Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. A cross-carrier HARQ capability component 825 may be configured as or otherwise support a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. A HARQ component 830 may be configured as or otherwise support a component for receiving a message on a first component carrier. A HARQ cross-carrier retransmission component 835 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0212] Figure 9 A block diagram 900 illustrates a communication manager 920 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, the communication manager 920 may include a cross-carrier HARQ capability component 925, a HARQ component 930, a HARQ cross-carrier retransmission component 935, an uplink delay budget component 940, a retransmission preparation component 945, a processing time component 950, an auxiliary information component 955, a parameter indication component 960, a PDCP queuing delay component 965, an awarding component 970, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0213] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The cross-carrier HARQ capability component 925 may be configured as, or otherwise support, a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The HARQ component 930 may be configured as, or otherwise support, a component for transmitting a message on a first component carrier. The HARQ cross-carrier retransmission component 935 may be configured as, or otherwise support, a component for retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0214] In some examples, the uplink delay budget component 940 may be configured as, or otherwise support, a component for receiving a control message indicating a threshold uplink delay budget. In some examples, the uplink delay budget component 940 may be configured as, or otherwise support, a component for sending a second message indicating whether the remaining uplink delay budget meets the threshold uplink delay budget based on a comparison of the UE's remaining uplink delay budget with the threshold uplink delay budget. In some examples, the message is retransmitted on a second component carrier based on the second message indicating that the remaining uplink delay budget meets the threshold uplink delay budget.

[0215] In some examples, the retransmission preparation component 945 may be configured as or otherwise support a component for transmitting via a capability message an indication of a time period associated with the retransmission of the message on the preparation second component carrier, wherein the retransmission of the message is based on the time period being less than a threshold time period.

[0216] In some examples, the processing time component 950 may be configured as or otherwise support a component for sending an indication of the processing time associated with a retransmission performed by the UE via a capability message.

[0217] In some examples, the auxiliary information component 955 may be configured as, or otherwise support, a component for transmitting auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the auxiliary information. In some examples, the one or more parameters include processing time associated with retransmission performed by the UE, state associated with the HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0218] In some examples, to support the transmission of auxiliary messages, the auxiliary information component 955 may be configured as or otherwise support a component for transmitting RRC messages that indicate one or more parameters associated with communication performed by the UE.

[0219] In some examples, the parameter indication component 960 may be configured as or otherwise support a component for sending a UCI message or MAC-CE that indicates one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the UCI message or MAC-CE.

[0220] In some examples, the auxiliary information component 955 may be configured as or otherwise support a component for transmitting auxiliary information, including a request to enable cross-carrier HARQ retransmission, based on a state state associated with one or more processors of the UE that satisfies a threshold processor state, wherein the message is retransmitted on a second component carrier based on the request.

[0221] In some examples, the PDCP queuing delay component 965 may be configured as or otherwise supported as a component for comparing the UE's uplink PDCP queuing delay with a threshold PDCP queuing delay. In some examples, the PDCP queuing delay component 965 may be configured as or otherwise supported as a component for transmitting uplink control information based on the comparison, the uplink control information indicating that the uplink PDCP queuing delay meets the threshold PDCP queuing delay, the uplink control information being multiplexed with the message on a first component carrier. In some examples, the grant component 970 may be configured as or otherwise supported as a component for receiving an grant on a first component carrier, the grant indicating the timing for retransmitting the message on a second component carrier, wherein the retransmission of the message is based on the grant and that the uplink PDCP queuing delay meets the threshold PDCP queuing delay.

[0222] In some examples, granting component 970 may be configured as or otherwise support a component for receiving grants based on the UE’s capability and one or more conditions satisfying a threshold condition, the grant indicating the timing of transmission on a second component carrier for retransmitting the message, wherein the message is retransmitted based on the grant via the timing of transmission on the second component carrier.

[0223] In some examples, granting component 970 may be configured as or otherwise support a component for receiving control messages configured to grant a set of configuration resources for HARQ retransmission on a first component carrier and a second component carrier. This set of configuration resources includes at least a first resource on the first component carrier for transmitting the message and a second resource on the second component carrier for at least one retransmission of the message. In some examples, HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for retransmitting the message via a second resource in the configuration granting resource set based on the UE's capabilities and one or more conditions satisfying a threshold condition.

[0224] In some examples, the HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for receiving control messages configured to switch between a first component carrier and a second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier is based on the semi-static switching mode.

[0225] In some examples, the HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for receiving a DCI based on the transmission of the message, the DCI indicating a request to retransmit the message, wherein the retransmission of the message is based on the request, and wherein the carrier indication field in the DCI includes UE-specific information that differs from the carrier indication based on the semi-static handover mode.

[0226] In some examples, one or more conditions include PER, RSRP, or both, as measured by the UE.

[0227] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. In some examples, the cross-carrier HARQ capability component 925 may be configured as or otherwise support a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. In some examples, the HARQ component 930 may be configured as or otherwise support a component for receiving a message on a first component carrier. In some examples, the HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0228] In some examples, the processing time component 950 may be configured as or otherwise support a component for sending an indication of the processing time associated with a retransmission performed by the UE via a capability message.

[0229] In some examples, the auxiliary information component 955 may be configured as, or otherwise support, a component for transmitting auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the auxiliary information. In some examples, the one or more parameters include processing time associated with retransmission performed by the UE, state associated with the HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0230] In some examples, to support the transmission of auxiliary messages, the auxiliary information component 955 may be configured as or otherwise support a component for transmitting RRC messages that indicate one or more parameters associated with communication performed by the UE.

[0231] In some examples, the parameter indication component 960 may be configured as or otherwise support a component for sending a UCI message or MAC-CE that indicates one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the UCI message or MAC-CE.

[0232] In some examples, the auxiliary information component 955 may be configured as or otherwise support a component for transmitting auxiliary information, including a request to enable cross-carrier HARQ retransmission, based on a state state associated with one or more processors of the UE that satisfies a threshold processor state, wherein retransmission of the message received on a second component carrier is based on the request.

[0233] In some examples, granting component 970 may be configured as or otherwise support a component for receiving grants based on one or more conditions that satisfy a threshold condition, the grant scheduling a transmission timing on a second component carrier for retransmission of the message, wherein the retransmission of the message is based on the grant being received via a transmission timing on the second component carrier.

[0234] In some examples, the HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for receiving control messages configured to switch between a first component carrier and a second component carrier for at least one retransmission in a semi-static switching mode, wherein retransmission of the message received on the second component carrier is based on the semi-static switching mode.

[0235] In some examples, the HARQ cross-carrier retransmission component 935 may be configured as or otherwise support a component for receiving a DCI based on the message, the DCI indicating a retransmission of the message, wherein receiving the retransmission of the message is based on the DCI, and wherein the carrier indication field in the DCI includes UE-specific information that differs from the carrier indication based on the semi-static handover mode.

[0236] In some examples, one or more conditions include the packet error rate, RSRP, or both, as measured by the UE.

[0237] Figure 10 A diagram illustrating a system 1000 including device 1005 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1045).

[0238] The I / O controller 1010 manages the input and output signals of the device 1005. The I / O controller 1010 can also manage peripheral devices not integrated into the device 1005. In some cases, the I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1010 may utilize an operating system, such as... Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of a processor (such as processor 1040). In some cases, a user may interact with device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0239] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired or wireless links, as described herein. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1025 for transmission, and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0240] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035, including instructions that, when executed by processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by processor 1040, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0241] Processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1040 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting cross-carrier conditional HARQ retransmission). For example, device 1005 or components of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, processor 1040 and memory 1030 being configured to perform the various functions described herein.

[0242] Based on the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. For example, the communication manager 1020 may be configured as, or otherwise support, a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1020 may be configured as, or otherwise support, a component for transmitting a message on a first component carrier. The communication manager 1020 may be configured as, or otherwise support, a component for retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0243] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. For example, the communication manager 1020 may be configured as or otherwise support a component for transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1020 may be configured as or otherwise support a component for receiving a message on a first component carrier. The communication manager 1020 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0244] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, and improving coordination between devices.

[0245] In some examples, the communication manager 1020 may be configured to use or otherwise coordinate with the transceiver 1015, one or more antennas 1025, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by the processor 1040 to cause the device 1005 to perform various aspects of cross-carrier conditional HARQ retransmission as described herein, or the processor 1040 and memory 1030 may be otherwise configured to perform or support such operations.

[0246] Figure 11 A block diagram 1100 illustrates a device 1105 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0247] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0248] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0249] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0250] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs, or other programmable logic devices, microcontrollers, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0251] Additionally or alternatively, in some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0252] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0253] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a network entity. For example, the communication manager 1120 may be configured as, or otherwise support, a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1120 may be configured as, or otherwise support, a component for receiving a message on a first component carrier. The communication manager 1120 may be configured as, or otherwise support, a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0254] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at a network entity. For example, the communication manager 1120 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1120 may be configured as or otherwise support a component for transmitting a message on a first component carrier. The communication manager 1120 may be configured as or otherwise support a component for transmitting the message on a second component carrier different from the first component carrier, wherein transmitting the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0255] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof or a processor otherwise coupled thereto) can support techniques for reducing processing, lowering power consumption, and utilizing communication resources more efficiently.

[0256] Figure 12 A block diagram 1200 illustrates a device 1205 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0257] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0258] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0259] Device 1205 or its various components may be examples of parts for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, communication manager 1220 may include cross-carrier HARQ capability component 1225, HARQ component 1230, HARQ cross-carrier retransmission component 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0260] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a network entity. A cross-carrier HARQ capability component 1225 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. A HARQ component 1230 may be configured as or otherwise support a component for receiving a message on a first component carrier. A HARQ cross-carrier retransmission component 1235 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0261] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at a network entity. A cross-carrier HARQ capability component 1225 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. A HARQ component 1230 may be configured as or otherwise support a component for transmitting a message on a first component carrier. A HARQ cross-carrier retransmission component 1235 may be configured as or otherwise support a component for transmitting the message on a second component carrier different from the first component carrier, wherein transmitting the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0262] Figure 13 A block diagram 1300 illustrates a communication manager 1320 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure. The communication manager 1320 may be an example of aspects of the communication manager 1120, communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of cross-carrier conditional HARQ retransmission as described herein. For example, the communication manager 1320 may include a cross-carrier HARQ capability component 1325, a HARQ component 1330, a HARQ cross-carrier retransmission component 1335, an uplink delay budget component 1340, a retransmission preparation component 1345, an auxiliary information component 1350, a parameter indication component 1355, a PDCP queuing delay component 1360, an awarding component 1365, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between the protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0263] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a network entity. A cross-carrier HARQ capability component 1325 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. A HARQ component 1330 may be configured as or otherwise support a component for receiving a message on a first component carrier. A HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0264] In some examples, the uplink delay budget component 1340 may be configured as or otherwise support a component for transmitting a control message indicating a threshold uplink delay budget. In some examples, the uplink delay budget component 1340 may be configured as or otherwise support a component for receiving a second message indicating whether the UE's remaining uplink delay budget meets the threshold uplink delay budget, wherein a retransmission of the message received on a second component carrier is based on the second message indicating that the remaining uplink delay budget meets the threshold uplink delay budget.

[0265] In some examples, the retransmission preparation component 1345 may be configured as or otherwise support a component for receiving via a capability message an indication of a time period associated with the retransmission of the message prepared by the UE on a second component carrier, the time period being based on the processing time associated with the retransmission performed by the UE, wherein the retransmission of the message is received based on the time period being less than a threshold time period.

[0266] In some examples, the auxiliary information component 1350 may be configured as, or otherwise support, a component for receiving auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the auxiliary information. In some examples, the one or more parameters include processing time associated with retransmission performed by the UE, state associated with the HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0267] In some examples, to support the reception of auxiliary messages, the auxiliary information component 1350 may be configured as or otherwise support a component for receiving RRC messages that indicate one or more parameters associated with communications performed by the UE.

[0268] In some examples, parameter indicating component 1355 may be configured as or otherwise support a component for receiving a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the UCI message or the MAC-CE.

[0269] In some examples, the auxiliary information component 1350 may be configured as or otherwise support a component for receiving auxiliary information, including a request to enable cross-carrier HARQ retransmission, based on a state state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message received on a second component carrier is based on the request.

[0270] In some examples, the PDCP queuing delay component 1360 may be configured as, or otherwise support, a component for receiving uplink control information indicating that the uplink PDCP queuing delay of the UE meets a threshold PDCP queuing delay, the uplink control information being multiplexed with the message on a first component carrier. In some examples, the PDCP queuing delay component 1360 may be configured as, or otherwise support, a component for transmitting an grant on a first component carrier, the grant indicating the timing of transmission for retransmission of the message on a second component carrier, wherein the retransmission of the message is received based on the grant and the uplink PDCP queuing delay meeting the threshold PDCP queuing delay.

[0271] In some examples, granting component 1365 may be configured as or otherwise support a component for transmitting grants based on the UE’s capabilities and one or more conditions satisfying a threshold condition, the grant indicating the timing of transmission for message retransmission on a second component carrier, wherein the message retransmission is received based on the grant via the transmission timing on the second component carrier.

[0272] In some examples, granting component 1365 may be configured as or otherwise support a component for transmitting control messages configured for HARQ retransmission on a first component carrier and a second component carrier. The configuration granting resource set includes at least a first resource on the first component carrier for transmitting the message and at least one second resource on the second component carrier for retransmission of the message, wherein the retransmission of the message is received via the second resource in the configuration granting resource set based on the UE's capability and one or more conditions satisfying a threshold condition.

[0273] In some examples, the HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for transmitting control messages configured to switch between a first component carrier and a second component carrier for at least one retransmission in a semi-static switching mode, wherein retransmission of the message received on the second component carrier is based on the semi-static switching mode.

[0274] In some examples, the HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for transmitting a DCI based on receiving the message, the DCI indicating a request to retransmit the message, wherein the retransmission of the message is based on the request, and wherein the carrier indication field in the DCI includes UE-specific information that differs from the carrier indication based on the semi-static handover mode.

[0275] In some examples, one or more conditions include the packet error rate, RSRP, or both, as measured by the UE.

[0276] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1320 may support wireless communication at a network entity. In some examples, the cross-carrier HARQ capability component 1325 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. In some examples, the HARQ component 1330 may be configured as or otherwise support a component for transmitting a message on a first component carrier. In some examples, the HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for transmitting the message on a second component carrier different from the first component carrier, wherein transmitting the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0277] In some examples, parameter indication component 1355 may be configured as or otherwise support a component for receiving an indication of the processing time associated with a retransmission performed by the UE via a capability message.

[0278] In some examples, the auxiliary information component 1350 may be configured as, or otherwise support, a component for receiving auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the auxiliary information. In some examples, the one or more parameters include processing time associated with retransmission performed by the UE, state associated with the HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0279] In some examples, to support the reception of auxiliary messages, the auxiliary information component 1350 may be configured as or otherwise support a component for receiving RRC messages that indicate one or more parameters associated with communications performed by the UE.

[0280] In some examples, parameter indicating component 1355 may be configured as or otherwise support a component for receiving a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based on the one or more parameters indicated via the UCI message or the MAC-CE.

[0281] In some examples, the auxiliary information component 1350 may be configured as or otherwise support a component for receiving auxiliary information, including a request to enable cross-carrier HARQ retransmission, based on a state state associated with one or more processors of the UE that satisfies a threshold processor state, wherein the message is retransmitted on a second component carrier based on the request.

[0282] In some examples, granting component 1365 may be configured as or otherwise support a component for sending an grant based on one or more conditions that satisfy a threshold condition, the grant scheduling a timing of transmission for retransmission of the message on a second component carrier, wherein the message is retransmitted based on the grant via a timing of transmission on the second component carrier.

[0283] In some examples, the HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for transmitting control messages configured to switch between a first component carrier and a second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier is based on the semi-static switching mode.

[0284] In some examples, the HARQ cross-carrier retransmission component 1335 may be configured as or otherwise support a component for transmitting a DCI based on the message, the DCI indicating the retransmission of the message, wherein the retransmission of the message is based on the DCI, and wherein the carrier indication field in the DCI includes UE-specific information that differs from the carrier indication based on the semi-static handover mode.

[0285] In some examples, one or more conditions include the packet error rate, RSRP, or both, as measured by the UE.

[0286] Figure 14A diagram illustrating a system 1400 including device 1405 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and acquisition of communication, such as a communication manager 1420, transceiver 1410, antenna 1415, memory 1425, code 1430, and processor 1435. These components may communicate electronically via one or more buses (e.g., bus 1440) or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0287] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1410 may also include a modem for modulating signals, providing modulated signals for transmission (e.g., via one or more antennas 1415, via a wired transmitter), receiving modulated signals (e.g., from one or more antennas 1415, from a wired receiver), and demodulating signals. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processor or memory components or be configured to couple to said one or more processor or memory components, said one or more processor or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processor or memory components (e.g., processor 1435 or memory 1425 or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, the transceiver may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0288] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430, including instructions that, when executed by processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, memory 1425 may also contain a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices.

[0289] Processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, processor 1435 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting cross-carrier conditional HARQ retransmission). For example, device 1405 or components of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, wherein processor 1435 and memory 1425 are configured to perform the various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container example) that can (e.g., by executing code 1430) host functions to perform the functions of device 1405. Processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within memory 1425). In some specific implementations, processor 1435 may be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components of device 1405, for example). For example, the processing system of device 1405 may refer to a system that includes various other components or sub-components of device 1405 (such as processor 1435, or transceiver 1410, or communication manager 1420, or other components or combinations of components of device 1405). The processing system of device 1405 can interface with other components of device 1405 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information or for receiving information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, and other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, allowing device 1405 to transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, allowing device 1405 to receive information or signal input, and such information may be transmitted to the processing system.Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0290] In some examples, bus 1440 may support protocol layer (e.g., within a protocol layer) communication of a protocol stack. In some examples, bus 1440 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or partitioned between the different components).

[0291] In some examples, the communication manager 1420 can manage various aspects of communication with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1420 can manage the delivery of data communications by client devices (such as one or more UEs 115). In some examples, the communication manager 1420 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1420 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0292] Based on the examples disclosed herein, the communication manager 1420 may support wireless communication at a network entity. For example, the communication manager 1420 may be configured as, or otherwise support, a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1420 may be configured as, or otherwise support, a component for receiving a message on a first component carrier. The communication manager 1420 may be configured as, or otherwise support, a component for receiving a retransmission of the message on a second component carrier different from the first component carrier, based on the availability of resources for retransmitting the message, the UE's capability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0293] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1420 may support wireless communication at a network entity. For example, the communication manager 1420 may be configured as or otherwise support a component for receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The communication manager 1420 may be configured as or otherwise support a component for transmitting a message on a first component carrier. The communication manager 1420 may be configured as or otherwise support a component for transmitting the message on a second component carrier different from the first component carrier, wherein transmitting the message on the second component carrier is based on the UE's capability to support cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission.

[0294] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, and improving coordination between devices.

[0295] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, processor 1435, memory 1425, code 1430, or any combination thereof. For example, code 1430 may include instructions that can be executed by the processor 1435 to cause the device 1405 to perform various aspects of cross-carrier conditional HARQ retransmission as described herein, or the processor 1435 and memory 1425 may be otherwise configured to perform or support such operations.

[0296] Figure 15 A flowchart illustrating a method 1500 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0297] At point 1505, the method may include: sending a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The operation of point 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of point 1505 may be provided by reference to [reference needed]. Figure 9 The described cross-carrier HARQ capability component 925 is implemented.

[0298] At 1510, the method may include: transmitting a message on a first component carrier. The operation of 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 9 The HARQ component 930 described is executed.

[0299] At 1515, the method may include: retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's ability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying a threshold condition for cross-carrier HARQ retransmission. The operation of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 9 The HARQ cross-carrier retransmission component 935 described is implemented.

[0300] Figure 16 A flowchart illustrating a method 1600 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0301] At 1605, the method may include: sending a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 9 The described cross-carrier HARQ capability component 925 is implemented.

[0302] At 1610, the method may include: receiving a control message indicating a threshold uplink delay budget. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 9 The described uplink delay budget component 940 is executed.

[0303] At 1615, the method may include: sending a second message indicating whether the remaining uplink delay budget meets the threshold uplink delay budget based on a comparison of the UE's remaining uplink delay budget with a threshold uplink delay budget. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 9 The described uplink delay budget component 940 is executed.

[0304] At 1620, the method may include: transmitting a message on a first component carrier. The operation of 1620 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1620 may be derived from references... Figure 9 The HARQ component 930 described is executed.

[0305] At 1625, the method may include: retransmitting the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's ability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying a threshold condition for cross-carrier HARQ retransmission. The operation of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1625 may be derived from references... Figure 9 The HARQ cross-carrier retransmission component 935 described is implemented.

[0306] Figure 17 A flowchart illustrating a method 1700 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be performed by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0307] At 1705, the method may include: sending a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 9 The described cross-carrier HARQ capability component 925 is implemented.

[0308] At 1710, the method may include: receiving a message on a first component carrier. The operation of 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 9The HARQ component 930 described is executed.

[0309] At 1715, the method may include: receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein receiving the retransmission of the message on the second component carrier is based on the UE's ability to support cross-carrier HARQ retransmission and one or more conditions associated with the communication performed by the UE satisfying threshold conditions for cross-carrier HARQ retransmission. The operation of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 9 The HARQ cross-carrier retransmission component 935 described is implemented.

[0310] Figure 18 A flowchart illustrating a method 1800 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. The operation of method 1800 can be implemented by a network entity or its components as described herein. For example, the operation of method 1800 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the functions described. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0311] At 1805, the method may include: receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be derived from references... Figure 13 The described cross-carrier HARQ capability component 1325 is implemented.

[0312] At 1810, the method may include: receiving a message on a first component carrier. The operation of 1810 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 13 The described HARQ component 1330 is executed.

[0313] At 1815, the method may include: receiving a retransmission of the message on a second component carrier different from the first component carrier based on the availability of resources for retransmitting the message, the UE's ability to support cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying a threshold condition for cross-carrier HARQ retransmission. The operation of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1815 may be derived from references... Figure 13 The HARQ cross-carrier retransmission component 1335 described herein is implemented.

[0314] Figure 19 A flowchart illustrating a method 1900 supporting cross-carrier conditional HARQ retransmission according to one or more aspects of this disclosure is provided. The operation of method 1900 may be implemented by a network entity or its components as described herein. For example, the operation of method 1900 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the functions described. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0315] At 1905, the method may include: receiving a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission. The operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be derived from references... Figure 13 The described cross-carrier HARQ capability component 1325 is implemented.

[0316] At 1910, the method may include: transmitting a message on a first component carrier. The operation at 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1910 may be derived from references... Figure 13 The described HARQ component 1330 is executed.

[0317] At 1915, the method may include: retransmitting the message on a second component carrier, different from the first component carrier, wherein the retransmission of the message on the second component carrier is based on the UE's ability to support cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for cross-carrier HARQ retransmission. The operation at 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1915 may be derived from references... Figure 13 The HARQ cross-carrier retransmission component 1335 described herein is implemented.

[0318] The following provides an overview of the various aspects of this disclosure:

[0319] Aspect 1: A method for wireless communication at a UE, the method comprising: transmitting a capability message indicating that the UE supports cross-carrier HARQ retransmission; transmitting a message on a first component carrier; and retransmitting the message on a second component carrier different from the first component carrier, based at least in part on the availability of resources for retransmitting the message, the UE's capability to support the cross-carrier HARQ retransmission, and one or more conditions associated with communication performed by the UE satisfying a threshold condition for the cross-carrier HARQ retransmission.

[0320] Aspect 2: According to the method of aspect 1, the method further includes: receiving a control message indicating a threshold uplink delay budget; and sending a second message indicating whether the remaining uplink delay budget satisfies the threshold uplink delay budget, based at least in part on comparing the remaining uplink delay budget of the UE with the threshold uplink delay budget.

[0321] Aspect 3: According to the method of aspect 2, wherein retransmitting the message on the second component carrier is at least in part based on the second message indicating that the remaining uplink delay budget meets the threshold uplink delay budget.

[0322] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: transmitting via the capability message an indication of a time period associated with preparing for retransmission of the message on the second component carrier, wherein the retransmission of the message is based at least in part on the time period being less than a threshold time period.

[0323] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: sending an indication via the capability message of a processing time associated with a retransmission performed by the UE.

[0324] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: transmitting auxiliary information indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

[0325] Aspect 7: According to the method of aspect 6, wherein the one or more parameters include processing time associated with retransmission performed by the UE, state associated with HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0326] Aspect 8: The method according to any one of Aspects 6 to 7, wherein sending the auxiliary information comprises: sending an RRC message indicating one or more parameters associated with the communication performed by the UE.

[0327] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: sending a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the UCI message or the MAC-CE.

[0328] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: transmitting auxiliary information including a request to enable the cross-carrier HARQ retransmission based at least in part on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message on the second component carrier is based at least in part on the request.

[0329] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: comparing the uplink PDCP queuing delay of the UE with a threshold PDCP queuing delay; transmitting a UCI indicating that the uplink PDCP queuing delay meets the threshold PDCP queuing delay based at least in part on the comparison, the UCI being multiplexed with the message on the first component carrier; and receiving an grant on the first component carrier, the grant indicating an opportunity for retransmission of the message on the second component carrier, wherein the retransmission of the message is based at least in part on the grant and the uplink PDCP queuing delay meeting the threshold PDCP queuing delay.

[0330] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: receiving an grant at least in part based on the capability of the UE and the satisfaction of the threshold condition by one or more conditions, the grant indicating a timing for retransmission of the message on the second component carrier, wherein the message is retransmitted at least in part based on the grant via the timing for retransmission on the second component carrier.

[0331] Aspect 13: The method according to any one of Aspects 1 to 11, the method further comprising: receiving a control message, the control message configuring a set of configuration-granted resources for HARQ retransmission on the first component carrier and the second component carrier, the set of configuration-granted resources including at least a first resource on the first component carrier for transmitting the message and at least one second resource on the second component carrier for retransmission of the message, wherein retransmitting the message comprises: retransmitting the message via the second resource in the set of configuration-granted resources based at least in part on the capability of the UE and the one or more conditions satisfying the threshold condition.

[0332] Aspect 14: The method according to any one of Aspects 1 to 11, the method further comprising: receiving a control message configured to switch between a first component carrier and a second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier is at least partially based on the semi-static switching mode.

[0333] Aspect 15: The method according to aspect 14, the method further comprising: receiving a DCI at least in part based on sending the message, the DCI indicating a request to retransmit the message, wherein retransmitting the message is at least in part based on the request, and wherein the carrier indication field in the DCI includes information for the UE that is different from a carrier indication at least in part based on the semi-static handover mode.

[0334] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the one or more conditions include PER, RSRP or both measured by the UE.

[0335] Aspect 17: A method for wireless communication at a UE, the method comprising: transmitting a capability message indicating that the UE supports the capability of cross-carrier HARQ retransmission; receiving a message on a first component carrier; and receiving a retransmission of the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based at least in part on the UE's capability of supporting the cross-carrier HARQ retransmission and one or more conditions associated with communication performed by the UE satisfying threshold conditions for the cross-carrier HARQ retransmission.

[0336] Aspect 18: The method according to aspect 17, the method further comprising: sending an indication via the capability message of a processing time associated with a retransmission performed by the UE.

[0337] Aspect 19: The method according to any one of Aspects 17 to 18, the method further comprising: transmitting auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

[0338] Aspect 20: According to the method of aspect 19, wherein the one or more parameters include processing time associated with retransmission performed by the UE, state associated with HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0339] Aspect 21: The method according to any one of Aspects 19 to 20, wherein sending the auxiliary information comprises: sending an RRC message indicating one or more parameters associated with the communication performed by the UE.

[0340] Aspect 22: The method according to any one of Aspects 17 to 21, the method further comprising: sending a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the UCI message or the MAC-CE.

[0341] Aspect 23: The method according to any one of Aspects 17 to 22, the method further comprising: transmitting auxiliary information including a request to enable the cross-carrier HARQ retransmission based at least in part on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message received on the second component carrier is at least in part based on the request.

[0342] Aspect 24: The method according to any one of aspects 17 to 23, the method further comprising: receiving an grant at least in part based on the satisfaction of the threshold condition based on one or more of the conditions, the grant scheduling a transmission timing on the second component carrier for the retransmission of the message, wherein the retransmission of the message is received at least in part based on the grant via the transmission timing on the second component carrier.

[0343] Aspect 25: The method according to any one of Aspects 17 to 23, the method further comprising: receiving a control message configured for switching between a first component carrier and a second component carrier for at least one retransmission semi-static switching mode, wherein the retransmission of which the message is received on the second component carrier is at least partially based on the semi-static switching mode.

[0344] Aspect 26: The method according to aspect 25, the method further comprising: receiving a DCI at least in part based on the message, the DCI indicating the retransmission of the message, wherein receiving the retransmission of the message is at least in part based on the DCI, and wherein the carrier indication field in the DCI includes information for the UE that is different from a carrier indication at least in part based on the semi-static handover mode.

[0345] Aspect 27: The method according to any one of Aspects 17 to 26, wherein the one or more conditions include PER, RSRP or both measured by the UE.

[0346] Aspect 28: A method for wireless communication at a network entity, the method comprising: receiving a capability message indicating that a UE supports cross-carrier HARQ retransmission; receiving a message on a first component carrier; and receiving a retransmission of the message on a second component carrier different from the first component carrier, based at least in part on the availability of resources for retransmitting the message, the UE's capability to support the cross-carrier HARQ retransmission, and one or more conditions associated with communication between the network entity and the UE satisfying a threshold condition for the cross-carrier HARQ retransmission.

[0347] Aspect 29: The method according to aspect 28, the method further comprising: sending a control message indicating a threshold uplink delay budget; and receiving a second message indicating whether the remaining uplink delay budget of the UE satisfies the threshold uplink delay budget, wherein the retransmission of receiving the message on the second component carrier is at least in part based on the second message indicating that the remaining uplink delay budget satisfies the threshold uplink delay budget.

[0348] Aspect 30: The method according to any one of Aspects 28 to 29, the method further comprising: receiving via the capability message an indication of a time period associated with retransmission of the message prepared by the UE on the second component carrier, the time period being at least partially based on a processing time associated with retransmission performed by the UE, wherein the retransmission of the message being received is at least partially based on the time period being less than a threshold time period.

[0349] Aspect 31: The method according to any one of Aspects 28 to 30, the method further comprising: receiving auxiliary information indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

[0350] Aspect 32: According to the method of aspect 31, wherein the one or more parameters include processing time associated with retransmission performed by the UE, state associated with HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0351] Aspect 33: The method according to any one of aspects 31 to 32, wherein receiving the auxiliary information includes: receiving an RRC message indicating one or more parameters associated with the communication performed by the UE.

[0352] Aspect 34: The method according to any one of Aspects 28 to 33, the method further comprising: receiving a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the UCI message or the MAC-CE.

[0353] Aspect 35: The method according to any one of Aspects 28 to 34, the method further comprising: receiving auxiliary information including a request to enable the cross-carrier HARQ retransmission based at least in part on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message received on the second component carrier is at least in part based on the request.

[0354] Aspect 36: The method according to any one of Aspects 28 to 35, the method further comprising: receiving a UCI indicating that the uplink PDCP queuing delay of the UE meets a threshold PDCP queuing delay, the UCI being multiplexed with the message on the first component carrier; and transmitting an grant on the first component carrier, the grant indicating the timing of transmission for the retransmission of the message on the second component carrier, wherein the retransmission of the message is received at least in part based on the grant and the uplink PDCP queuing delay meeting the threshold PDCP queuing delay.

[0355] Aspect 37: The method according to any one of Aspects 28 to 36, the method further comprising: transmitting an grant at least in part based on the capability of the UE and the satisfaction of the threshold condition by one or more conditions, the grant indicating a timing of transmission for the retransmission of the message on the second component carrier, wherein the retransmission of the message is received at least in part based on the grant via the timing of transmission on the second component carrier.

[0356] Aspect 38: The method according to any one of Aspects 28 to 36, the method further comprising: transmitting a control message, the control message configuring a configuration grant resource set for HARQ retransmission on the first component carrier and the second component carrier, the configuration grant resource set including at least a first resource on the first component carrier for transmitting the message and a second resource on the second component carrier for at least one retransmission of the message, wherein the retransmission of the message is received via the second resource in the configuration grant resource set based at least in part on the capability of the UE and the one or more conditions satisfying the threshold condition.

[0357] Aspect 39: The method according to any one of Aspects 28 to 36, the method further comprising: transmitting a control message configured for switching between a first component carrier and a second component carrier for at least one retransmission semi-static switching mode, wherein the retransmission of which the message is received on the second component carrier is at least partially based on the semi-static switching mode.

[0358] Aspect 40: The method according to aspect 39, the method further comprising: sending a DCI at least in part based on receiving the message, the DCI indicating a request for retransmission of the message, wherein the retransmission of receiving the message is at least in part based on the request, and wherein the carrier indication field in the DCI includes information for the UE that is different from a carrier indication at least in part based on the semi-static handover mode.

[0359] Aspect 41: The method according to any one of Aspects 28 to 40, wherein the one or more conditions include PER, RSRP or both measured by the UE.

[0360] Aspect 42: A method for wireless communication at a network entity, the method comprising: receiving a capability message indicating that a UE supports the capability of cross-carrier HARQ retransmission; transmitting a message on a first component carrier; and retransmitting the message on a second component carrier different from the first component carrier, wherein the retransmission of the message on the second component carrier is based at least in part on the UE supporting the capability of the cross-carrier HARQ retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for the cross-carrier HARQ retransmission.

[0361] Aspect 43: The method according to aspect 42 further includes: receiving, via the capability message, an indication of a processing time associated with a retransmission performed by the UE.

[0362] Aspect 44: The method according to any one of aspects 42 to 43, the method further comprising: receiving auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

[0363] Aspect 45: According to the method of aspect 44, wherein the one or more parameters include processing time associated with retransmission performed by the UE, state associated with HARQ buffer at the UE, number of loops loaded at the UE, number of processors loaded at the UE, or any combination thereof.

[0364] Aspect 46: The method according to any one of Aspects 44 to 45, wherein receiving the auxiliary information includes: receiving an RRC message indicating one or more parameters associated with the communication performed by the UE.

[0365] Aspect 47: The method according to any one of Aspects 42 to 46, the method further comprising: receiving a UCI message or MAC-CE, the UCI message or the MAC-CE indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the UCI message or the MAC-CE.

[0366] Aspect 48: The method according to any one of Aspects 42 to 47, the method further comprising: receiving auxiliary information including a request to enable the cross-carrier HARQ retransmission based at least in part on a state associated with one or more processors of the UE satisfying a threshold processor state, wherein the retransmission of the message on the second component carrier is based at least in part on the request.

[0367] Aspect 49: The method according to any one of aspects 42 to 48, the method further comprising: transmitting an grant at least in part based on the satisfaction of the threshold condition based on one or more of the conditions, the grant scheduling a transmission timing on the second component carrier for retransmission of the message, wherein the message is retransmitted at least in part based on the grant via the transmission timing on the second component carrier.

[0368] Aspect 50: The method according to any one of Aspects 42 to 48, the method further comprising: transmitting a control message configured to switch between a first component carrier and a second component carrier for at least one semi-static switching mode for retransmission, wherein retransmission of the message on the second component carrier is at least partially based on the semi-static switching mode.

[0369] Aspect 51: The method according to aspect 50, the method further comprising: transmitting a DCI at least in part based on the message, the DCI indicating retransmission of the message, wherein retransmission of the message is at least in part based on the DCI, and wherein the carrier indication field in the DCI includes information for the UE that is different from a carrier indication at least in part based on the semi-static handover mode.

[0370] Aspect 52: The method according to any one of aspects 42 to 51, wherein the one or more conditions include PER, RSRP or both measured by the UE.

[0371] Aspect 53: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 16.

[0372] Aspect 54: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 16.

[0373] Aspect 55: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0374] Aspect 56: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 17 to 27.

[0375] Aspect 57: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 17 to 27.

[0376] Aspect 58: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform a method according to any one of aspects 17 to 27.

[0377] Aspect 59: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 28 to 41.

[0378] Aspect 60: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 28 to 41.

[0379] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by a processor to perform the method according to any one of aspects 28 to 41.

[0380] Aspect 62: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 42 to 52.

[0381] Aspect 63: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 42 to 52.

[0382] Aspect 64: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by a processor to perform the method according to any one of aspects 42 to 52.

[0383] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0384] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0385] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0386] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0387] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, these functions can be stored as one or more instructions or code on a computer-readable medium, or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in different locations, including portions distributed such that the functions are implemented in different physical locations.

[0388] Computer-readable media includes both non-transitory computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, while optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0389] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0390] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), and ascertainment. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Additionally, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0391] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0392] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0393] The description provided herein is intended to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Send a capability message indicating that the UE supports the capability of cross-carrier hybrid automatic repeat request retransmission; Send the message on the first component carrier; as well as The message is retransmitted on a second component carrier different from the first component carrier, based at least in part on the availability of resources for retransmitting the message, the UE's ability to support the cross-carrier hybrid automatic repeat request retransmission, and one or more conditions associated with the communication performed by the UE satisfying a threshold condition for the cross-carrier hybrid automatic repeat request retransmission.

2. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Receive control messages indicating the uplink delay budget threshold; and A second message indicating whether the remaining uplink delay budget meets the threshold uplink delay budget is sent, at least in part based on comparing the UE's remaining uplink delay budget with the threshold uplink delay budget.

3. The apparatus of claim 2, wherein retransmitting the message on the second component carrier is at least in part based on the second message indicating that the remaining uplink delay budget satisfies the threshold uplink delay budget.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The capability message sends an indication of a time period associated with preparing to retransmit the message on the second component carrier, wherein the retransmission of the message is based at least in part on the time period being less than a threshold time period.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The capability message sends an indication of the processing time associated with the retransmission performed by the UE.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Sending auxiliary information, the auxiliary information indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

7. The apparatus of claim 6, wherein one or more parameters include processing time associated with retransmissions performed by the UE, a state associated with a hybrid automatic repeat request buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

8. The apparatus of claim 6, wherein the instruction for transmitting the auxiliary information is executable by the processor to cause the apparatus to: Send a radio resource control message that indicates one or more parameters associated with the communication performed by the UE.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Send an uplink control information message or a media access control-control element, the uplink control information message or the media access control-control element indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated by the uplink control information message or the media access control-control element.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The auxiliary information, including a request to enable the cross-carrier hybrid automatic repeat request retransmission, is transmitted based at least in part on a state that is satisfied with a threshold processor state associated with one or more processors of the UE, wherein the message is retransmitted on the second component carrier at least in part based on the request.

11. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The uplink packet data convergence protocol (PDCP) queuing delay of the UE is compared with the threshold PDCP queuing delay; Uplink control information indicating that the uplink PDCP queuing delay meets the threshold PDCP queuing delay is transmitted at least in part based on the comparison, the uplink control information being multiplexed with the message on the first component carrier; as well as An grant is received on the first component carrier, the grant indicating the timing for retransmitting the message on the second component carrier, wherein the retransmission of the message is based at least in part on the grant and the uplink PDCP queuing delay satisfying the threshold PDCP queuing delay.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The grant is received at least in part based on the UE’s capabilities and the satisfaction of one or more conditions of the threshold condition, the grant indicating the timing of transmission on the second component carrier for retransmitting the message, wherein the message is retransmitted at least in part based on the grant via the timing of transmission on the second component carrier.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The device receives a control message configuring a set of configuration-granted resources for hybrid automatic repeat request (ARRP) on the first and second component carriers. The configuration-granted resource set includes at least a first resource on the first component carrier for transmitting the message and at least one second resource on the second component carrier for retransmitting the message. The instruction can be further executed by the processor to cause the device to: The message is retransmitted via the second resource in the resource set via the configuration, based at least in part on the UE’s capabilities and the satisfaction of one or more conditions of the threshold condition.

14. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received, the control message configuring a semi-static handover mode for switching between a first component carrier and a second component carrier for at least one retransmission, wherein the retransmission of the message on the second component carrier is at least partially based on the semi-static handover mode.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: The receiving of downlink control information is based at least in part on sending the message, the downlink control information indicating a request to retransmit the message, wherein the retransmission of the message is based at least in part on the request, and wherein the carrier indication field in the downlink control information includes information for the UE that is different from the carrier indication based at least in part on the semi-static handover mode.

16. The apparatus of claim 1, wherein the one or more conditions include a packet error rate, a reference signal received power, or both, measured by the UE.

17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Send a capability message indicating that the UE supports the capability of cross-carrier hybrid automatic repeat request retransmission; Messages are received on the first component carrier. as well as Retransmission of the message is received on a second component carrier, which is different from the first component carrier, wherein the retransmission of the message is received on the second component carrier at least in part based on the UE’s ability to support the cross-carrier hybrid automatic repeat request retransmission and one or more conditions associated with the communication performed by the UE satisfying the threshold conditions for the cross-carrier hybrid automatic repeat request retransmission.

18. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: The capability message sends an indication of the processing time associated with the retransmission performed by the UE.

19. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: Sending auxiliary information indicating one or more parameters associated with communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated via the auxiliary information.

20. The apparatus of claim 19, wherein one or more parameters include processing time associated with retransmissions performed by the UE, a state associated with a hybrid automatic repeat request buffer at the UE, the number of loops loaded at the UE, the number of processors loaded at the UE, or any combination thereof.

21. The apparatus of claim 19, wherein the instruction for transmitting the auxiliary information is executable by the processor to cause the apparatus to: Send a radio resource control message that indicates one or more parameters associated with the communication performed by the UE.

22. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: Send an uplink control information message or a media access control-control element, the uplink control information message or the media access control-control element indicating one or more parameters associated with the communication performed by the UE, wherein the one or more conditions are based at least in part on the one or more parameters indicated by the uplink control information message or the media access control-control element.

23. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: The auxiliary information, including a request to enable the cross-carrier hybrid automatic repeat request retransmission, is transmitted based at least in part on a state that is satisfied with a threshold processor state associated with one or more processors of the UE, wherein the retransmission of the message received on the second component carrier is at least in part based on the request.

24. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: An grant is received at least in part based on the satisfaction of the threshold condition under one or more of the conditions, the grant scheduling the timing of the retransmission of the message on the second component carrier, wherein the retransmission of the message is received at least in part based on the grant via the timing of the transmission on the second component carrier.

25. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received, the control message configuring a semi-static handover mode for switching between a first component carrier and a second component carrier for at least one retransmission, wherein the retransmission of which the message is received on the second component carrier is at least partially based on the semi-static handover mode.

26. The apparatus of claim 25, wherein the instructions are further executable by the processor to cause the apparatus to: The downlink control information is received at least in part based on the message, the downlink control information indicating the retransmission of the message, wherein the retransmission of the message is received at least in part based on the downlink control information, and wherein the carrier indication field in the downlink control information includes information for the UE that is different from the carrier indication based at least in part on the semi-static handover mode.

27. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Receive capability message, the capability message indicating that the user equipment (UE) supports the capability of cross-carrier hybrid automatic repeat request repeat; Messages are received on the first component carrier. as well as The message is retransmitted on a second component carrier different from the first component carrier, based at least in part on the availability of resources for retransmitting the message, the UE's ability to support the cross-carrier hybrid automatic repeat request (ACRP), and one or more conditions associated with communication between the network entity and the UE satisfying a threshold condition for the ACRP.

28. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: Send a control message indicating the threshold uplink delay budget; and A second message indicating whether the remaining uplink delay budget of the UE satisfies the threshold uplink delay budget is received, wherein the retransmission of the message received on the second component carrier is at least in part based on the second message indicating that the remaining uplink delay budget satisfies the threshold uplink delay budget.

29. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; A memory coupled to the processor; and Instructions, which are stored in the memory and can be executed by the processor, to cause the device to: Receive capability message, the capability message indicating that the user equipment (UE) supports the capability of cross-carrier hybrid automatic repeat request repeat; Transmit the message on the first component carrier; and The message is retransmitted on a second component carrier, which is different from the first component carrier, wherein the retransmission of the message on the second component carrier is based at least in part on the UE’s ability to support the cross-carrier hybrid automatic repeat request retransmission and one or more conditions associated with communication between the network entity and the UE satisfying threshold conditions for the cross-carrier hybrid automatic repeat request retransmission.

30. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: The capability message receives an indication of the processing time associated with the retransmission performed by the UE.

Images