Cross-carrier retransmission technology

Abstract

Certain aspects of the present disclosure provide cross-carrier retransmission techniques. A method that can be performed by a user equipment (UE) includes: monitoring an initial transmission of data from a network on a first entity; generating a negative acknowledgement message indicating that the initial transmission of the data was not decoded successfully; transmitting the negative acknowledgement message; and monitoring a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 16 / 904,207, filed on June 17, 2020, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 867,645, filed on June 27, 2019, both of which are assigned to the assignee of the present application and are hereby expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes.

[0003] introduction

[0004] Aspects of the present disclosure relate to wireless communications, and more particularly, to data retransmission techniques.

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

[0008] Overview

[0009] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes.Without limiting the scope of the disclosure as expressed by the following claims, some features will now be discussed briefly.

[0010] Certain aspects relate to a method for wireless communication. The method generally includes: monitoring an initial transmission of data from a network on a first entity; generating a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting the negative acknowledgement message; and monitoring a retransmission of the data on a second entity, the second entity being different from the first entity, after the transmission of the negative acknowledgement message.

[0011] Certain aspects relate to a method for wireless communication. The method generally includes: transmitting an initial transmission of data to a user equipment (UE) at a first entity; receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; and transmitting a retransmission of the data at a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0012] Certain aspects relate to a method for wireless communication. The method generally includes transmitting an initial transmission of data to a network at a first entity, generating a retransmission of the data, and transmitting the retransmission of the data at a second entity, the second entity being different from the first entity.

[0013] Certain aspects relate to a method for wireless communication. The method generally includes monitoring an initial transmission of data from a UE at a first entity; and receiving a retransmission of the data at a second entity, the second entity being different from the first entity.

[0014] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: a memory; and one or more processors coupled to the memory, the one or more processors and the memory configured to: monitor an initial transmission of data from a network on a first entity; generate a negative acknowledgement message indicating that the initial transmission of the data was unsuccessfully decoded; transmit the negative acknowledgement message; and monitor a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0015] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: means for monitoring an initial transmission of data from a network on a first entity; means for generating a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; means for transmitting the negative acknowledgement message; and means for monitoring a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0016] Certain aspects relate to a computer-readable medium. The computer-readable medium generally includes code for monitoring an initial transmission of data from a network at a first entity; code for generating a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; code for transmitting the negative acknowledgment message; and code for monitoring a retransmission of the data at a second entity, the second entity being different from the first entity, after the transmission of the negative acknowledgment message.

[0017] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: a memory; and one or more processors coupled to the memory, the one or more processors and the memory configured to: transmit an initial transmission of data to a user equipment (UE) on a first entity; receive a negative acknowledgement message indicating that the initial transmission of the data was unsuccessfully decoded; and transmit a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0018] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: means for transmitting an initial transmission of data to a UE on a first entity; means for receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; and means for transmitting a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0019] Certain aspects relate to a computer-readable medium. The computer-readable medium generally includes code for transmitting an initial transmission of data to a UE at a first entity; code for receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; and code for transmitting a retransmission of the data at a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0020] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: a memory; and one or more processors coupled to the memory, the one or more processors and the memory configured to: transmit an initial transmission of data to a network on a first entity; generate a retransmission of the data; and transmit the retransmission of the data on a second entity, the second entity being different from the first entity.

[0021] Certain aspects relate to an apparatus for wireless communications. The apparatus generally includes means for transmitting an initial transmission of data to a network at a first entity, means for generating a retransmission of the data, and means for transmitting the retransmission of the data at a second entity, the second entity being different from the first entity.

[0022] Certain aspects relate to a computer-readable medium. The computer-readable medium generally includes code for transmitting an initial transmission of data to a network at a first entity, code for generating a retransmission of the data, and code for transmitting the retransmission of the data at a second entity, the second entity being different from the first entity.

[0023] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes: a memory; and one or more processors coupled to the memory, the one or more processors and the memory configured to: monitor an initial transmission of data from a UE on a first entity; and receive a retransmission of the data on a second entity, the second entity being different from the first entity.

[0024] Certain aspects relate to an apparatus for wireless communications. The apparatus generally includes means for monitoring an initial transmission of data from a UE on a first entity and means for receiving a retransmission of the data on a second entity, the second entity being different from the first entity.

[0025] Certain aspects relate to a computer-readable medium. The computer-readable medium generally includes code for monitoring an initial transmission of data from a UE at a first entity; and code for receiving a retransmission of the data at a second entity, the second entity being different from the first entity.

[0026] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0029] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0030] Figure 2 is a diagram showing an example of a frame format 200 .

[0031] Figure 3 Example operations for cross-carrier scheduling are illustrated.

[0032] Figure 4is a flow diagram illustrating example operations for wireless communications by a user equipment (UE), in accordance with certain aspects of the present disclosure.

[0033] Figure 5 is a flow diagram illustrating example operations for wireless communications by a base station (BS), in accordance with certain aspects of the present disclosure.

[0034] Fig. 6A and 6B

[0013] Illustrated are cross-carrier retransmissions of downlink data in accordance with certain aspects of the present disclosure.

[0035] Figure 7 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

[0036] Figure 8 is a flow diagram illustrating example operations for wireless communications by a BS in accordance with certain aspects of the present disclosure.

[0037] Fig. 9A and 9B Uplink data cross-carrier retransmissions in accordance with certain aspects of the present disclosure are illustrated.

[0038] Fig.10 Illustrated is preconfiguration of uplink or downlink data retransmission on a different CC than the initial data transmission, in accordance with certain aspects of the present disclosure.

[0039] Fig.11 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0040] Fig.12 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0041] Fig.13 is a block diagram conceptually illustrating designs of an example BS and UE in accordance with certain aspects of the present disclosure.

[0042] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation.

[0043] Detailed Description

[0044] Various aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for cross-carrier retransmission. For example, initial data transmission may be scheduled on a first entity using semi-persistent scheduling (SPS) or configured grant (CG). As used herein, the term "entity" generally refers to a frequency resource, a cellular cell, or a component carrier (CC). When decoding of a data transmission (e.g., at a user equipment) on a first entity (e.g., a first CC) fails, retransmission of the data may be configured on a second entity (e.g., another CC) that is different from the first entity. In some cases, control information may be sent (e.g., on a first entity or a second entity) to a user equipment (UE) that schedules data retransmission. In other aspects, data retransmission may be preconfigured. In other words, the UE may automatically implement data retransmission on a second entity when decoding of the initial transmission fails.

[0045] The following description provides an example of traffic burst awareness in a communication system, but does not limit the scope, applicability or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such equipment or methods practiced using other structures, functionalities, or structures and functionalities as supplements to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or explanation". Any aspect described as "exemplary" herein need not be interpreted as being superior to or superior to other aspects.

[0046] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, a 5G NR RAT network may be deployed.

[0047] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may be a NR system (e.g., a 5G NR network).

[0048] like Figure 1 As illustrated in , the wireless communication network 100 may include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a particular geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of mobile BS 110. In some examples, BS 110 may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. Figure 1 In the example shown in , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for a pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. The BS may support one or more cells. BS 110 communicates with user equipment (UE) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in the wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.

[0049] According to certain aspects, BS 110 and UE 120 may be configured for cross-carrier retransmission. Figure 1 As shown in FIG. 1 , BS 110a includes a cross-carrier manager 112. According to aspects of the present disclosure, the cross-carrier manager 112 may be configured to perform cross-carrier retransmission. Figure 1 As shown in , UE 120a includes a cross-carrier manager 122. According to aspects of the present disclosure, the cross-carrier manager 122 may be configured to configure cross-carrier retransmissions. For example, the cross-carrier manager 112 may transmit an initial transmission of data to a user equipment (UE) on a first entity; receive a negative acknowledgement message indicating that the initial transmission of the data was decoded unsuccessfully; and transmit a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity. In certain aspects, the cross-carrier manager 122 at the UE may monitor an initial transmission of data from a network on a first entity; generate a negative acknowledgement message indicating that the initial transmission of the data was decoded unsuccessfully; transmit the negative acknowledgement message; and monitor the retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0050] The wireless communication network 100 may also include a relay station (e.g., relay station 110r) (also referred to as a relay, etc.), which receives transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and sends transmissions of data and / or other information to a downstream station (e.g., UE 120 or BS 110), or which relays transmissions between UEs 120 to facilitate communication between the devices.

[0051] A network controller 130 may couple to a set of BSs 110 and provide coordination and control for the BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0052] Figure 2 is a diagram showing an example of a frame format 200. The transmission timeline of each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol period in each slot. A mini slot (which may be referred to as a subslot structure) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols). In certain aspects, the subframes of the frame format 200 may be implemented using cross-carrier scheduling, as described in more detail herein.

[0053] Figure 3 Example operations of cross-carrier scheduling are illustrated. As illustrated, a first component carrier (CC1) may include a physical downlink control channel (PDCCH) 302, which includes control information applicable to CC1 and a second component carrier (CC2). For example, CC1 may schedule resources for data transmission in CC1 and CC2. CC1 may be referred to as a scheduling CC and CC2 may be referred to as a scheduled CC. Each component carrier is associated with a cellular cell. Although Figure 3 Only two CCs are illustrated in the figure, but any number of CCs can be implemented, each CC is associated with a frequency range (FR). In some cases, multiple CCs may be part of the same FR. For example, CC1 may use a first FR (FR1) and CC2 may use a second FR (FR2). The configuration of each FR may be different. For example, FR1 may have a smaller bandwidth (BW) than FR2, but have fewer blocking issues. FR1 may have a lower subcarrier spacing (SCS) than FR2. For example, the SCS of FR1 may be 60, while the SCS of FR2 may be 120.

[0054] Cross-carrier retransmission example technology

[0055] In Release 15 and Release 16 of the 3rd Generation Partnership Project (3GPP), each hybrid automatic repeat request (HARQ) process is implemented per cell, and a transmission (TB) cannot be retransmitted on a cell that is different from the original cell of the TB. TB generally refers to the payload (or data) of the physical layer. In certain aspects of the present disclosure, a physical downlink shared channel (PDSCH) (e.g., data) that fails to be transmitted on a frequency range (e.g., FR2) can be retransmitted on a different FR (e.g., FR1) to improve communication robustness. For example, data retransmission can be implemented on FR1 via cross-carrier scheduling from FR2 to FR1. For example, control information on FR2 can be used to schedule resources for retransmitting PDSCH on FR1. As another example, in order to improve control signaling robustness, retransmission can be performed on FR1 via self-carrier scheduling on FR1, as described in more detail herein.

[0056] Figure 4 4 is a flow diagram illustrating example operations 400 for wireless communications in accordance with certain aspects of the present disclosure. Operations 400 may be performed, for example, by a UE, such as UE 120a in wireless communication network 100, for example.

[0057] Operation 400 may be implemented as a processor on one or more processors (e.g., Fig.13 In addition, signal transmission and reception by the UE in operation 400 may be performed by one or more antennas (e.g., Fig.13 In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 1380).

[0058] Operations 400 may begin at block 405 with the UE monitoring an initial transmission of data from a network on a first entity (e.g., a first frequency resource, CC, or cell), and at block 410, generating a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful. As used herein, the term "entity" generally refers to a frequency resource, a cell, or a component carrier (CC). At block 415, the UE may transmit the negative acknowledgement message; and at block 420, after the transmission of the negative acknowledgement message, monitoring for retransmissions of the data on a second entity (e.g., a second frequency resource, CC, or cell), the second entity being different from the first entity.

[0059] In certain aspects, UE 120 may also receive (e.g., from BS 110) control information indicating that the second entity is to be monitored for receiving the retransmission of the data. For example, control information (e.g., for cross-carrier scheduling) may be received via the first entity, as described with reference to Fig. 6A As another example, control information (eg, for self-carrier scheduling) may be received via a second entity, as described in more detail below. Figure 6B Described in more detail.

[0060] In certain aspects, the control information may include: a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and a HARQ anchor entity ID associated with the HARQ process ID. In this case, the UE may decode the data by combining the data and the retransmission of the data based on the HARQ process ID and the HARQ anchor entity ID, as described in more detail herein. In other words, the UE may use the HARQ process ID and the HARQ anchor entity ID to identify the initial transmission of the data to be combined with the retransmission of the data.

[0061] In some cases, the UE may generate an acknowledgement / negative acknowledgement (A / N) message indicating whether the retransmission of the data was successfully decoded; and transmit the A / N message to the network. The A / N message may be transmitted via a third entity. The third entity may be configured for the first entity. In some aspects, the third entity may be configured for the second entity. For example, the third entity may be a physical uplink control channel (PUCCH) transmission cell configured for a first cell (first entity) receiving an initial transmission of PDSCH on FR2, or a PUCCH transmission cell configured for a second cell (second entity) receiving a retransmission of PDSCH on FR1.

[0062] In some aspects, the UE may be preconfigured to monitor the second entity to receive the retransmission of the data after the transmission of the negative acknowledgement message. In some cases, the UE may receive (e.g., from BS 110) an indication of a coordination entity on which the retransmission of the data may be received, the coordination entity including the second entity. In some aspects, the first entity may be part of an unlicensed spectrum and the second entity may be part of a licensed spectrum.

[0063] In certain aspects, the UE may monitor the first entity for one or more other transmissions after monitoring the retransmission of the data. In this case, the UE may receive an indication at the second entity of when to begin monitoring the first entity for the one or more other transmissions. In some cases, monitoring the first entity for the one or more other transmissions may begin upon expiration of a timer. The timer may be started after the initial transmission or after switching to the second entity for monitoring the retransmission of the data. In some cases, the retransmission of the data may be received during a retransmission cycle, and monitoring the first entity for the one or more other transmissions may begin at the end of the retransmission cycle.

[0064] Figure 5 5 is a flow diagram illustrating example operations 500 for wireless communications in accordance with certain aspects of the present disclosure. Operations 500 may be performed, for example, by a BS, such as BS 110a in wireless communication network 100, for example. Operations 500 may be operations performed by a BS that are complementary to operations 400 performed by a UE.

[0065] Operation 500 may be implemented as a processor on one or more processors (e.g., Fig.13 In addition, signal transmission and reception by the BS in operation 500 may be performed by, for example, one or more antennas (e.g., Fig.13 In some aspects, the transmission and / or reception of signals by the BS may be implemented via a bus interface of one or more processors (eg, controller / processor 1340) that obtain and / or output signals.

[0066] Operations 500 may begin by transmitting an initial transmission of data to a UE at a first entity at block 505, and receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful at block 510. At block 515, the BS may transmit a retransmission of the data at a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0067] Fig. 6A and 6B The present disclosure illustrates downlink data cross-carrier retransmission according to certain aspects of the present disclosure. Fig. 6AAs illustrated, cross-carrier retransmissions may be implemented using cross-carrier scheduling. For example, PDSCH 602 may be transmitted on FR2. PDSCH 602 may be scheduled using semi-persistent scheduling (SPS). In certain aspects, PUCCH 604 may be transmitted on FR2. PUCCH 604 may include A / N signaling indicating whether PDSCH 602 was successfully decoded. As illustrated, decoding of PDSCH 602 may have failed. Therefore, PUCCH 604 may indicate a negative acknowledgement.

[0068] In certain aspects, a physical downlink control channel (PDCCH) 606 may be received on the same FR (FR2) as the initial data transmission (e.g., PDSCH 602). The PDCCH may schedule resources for retransmissions of PDSCH 602 (e.g., data retransmissions 608) on FR1. FR1 may have a lower subcarrier spacing (SCS) than FR2. For example, the SCS for FR1 may be 60, while the SCS for FR2 may be 120.

[0069] In certain aspects, another A / N message (e.g., PUCCH 610) indicating whether the data retransmission 608 has been successfully decoded may be transmitted, as illustrated. Figure 6B As illustrated, cross-carrier retransmissions may be implemented using self-carrier scheduling. In other words, PDCCH 612 may be received on the same FR (FR1) as the data retransmission. For example, PDCCH 612 on FR1 may schedule resources on FR1 for use in PDSCH (data retransmission 608).

[0070] Although some of the examples provided herein have described cross-carrier retransmission of downlink data to facilitate understanding, cross-carrier retransmission can be used to retransmit uplink data. For example, a physical uplink shared channel (PUSCH) can be retransmitted on a different entity than the initial transmission of the PUSCH, as described in more detail herein.

[0071] Figure 7 7 is a flow diagram illustrating example operations 700 for wireless communications in accordance with certain aspects of the present disclosure. Operations 700 may be performed, for example, by a UE, such as UE 120a in wireless communication network 100, for example.

[0072] Operation 700 may be implemented as a processor on one or more processors (e.g., Fig.13 In addition, signal transmission and reception by the UE in operation 700 may be performed by one or more antennas (e.g., Fig.13In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 1380).

[0073] Operations 700 may begin with an initial transmission of data transmitted by a UE to a network on a first entity at block 705, and generating a retransmission of the data at block 710. At block 715, the UE may transmit the retransmission of the data on a second entity, the second entity being different from the first entity.

[0074] In some aspects, the UE may receive control information indicating that the second entity is to be used to transmit the retransmission of the data. In some cases, the control information may be received via the first entity. As another example, the control information may be received via the second entity.

[0075] In certain aspects, the control information may include a HARQ process ID indicating an initial transmission of the data corresponding to the retransmission. The control information may also include a HARQ anchor entity ID associated with the HARQ process ID. In certain aspects, the UE may be preconfigured to transmit retransmissions of the data via a second entity. In certain aspects, the UE may receive an indication of coordination entities over which the retransmissions of the data may be transmitted, the coordination entities including the second entity. In some cases, the first entity may be part of an unlicensed spectrum and the second entity may be part of a licensed spectrum.

[0076] Figure 8 8 is a flow diagram illustrating example operations 800 for wireless communications in accordance with certain aspects of the present disclosure. Operations 800 may be performed, for example, by a BS, such as BS 110a in wireless communication network 100, for example. Operations 800 may be operations performed by a BS that are complementary to operations 700 performed by a UE.

[0077] Operation 800 may be implemented as a processor on one or more processors (e.g., Fig.13 In addition, signal transmission and reception by the BS in operation 800 may be performed by one or more antennas (e.g., Fig.13 In some aspects, transmission and / or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller / processor 1340) that obtain and / or output signals. Operations 800 may begin, at block 805, with monitoring, by the BS, an initial transmission of data from a UE on a first entity, and, at block 810, with receiving a retransmission of the data on a second entity that is different from the first entity.

[0078] Fig. 9Aand 9B The present disclosure illustrates uplink data cross-carrier retransmission according to certain aspects of the present disclosure. Fig. 9A As illustrated, cross-carrier uplink data retransmissions may be implemented using cross-carrier scheduling. PUSCH 902 (e.g., initial data transmission) may be transmitted on FR2. PUSCH 902 may be scheduled using a configured grant (CG). As illustrated, decoding of PUSCH 902 at the BS may have failed. In certain aspects, PDCCH 606 ​​may be received on the same FR (FR2) as the initial data transmission (e.g., PUSCH 902). PDCCH 606 ​​may schedule resources for retransmitting PUSCH 902 (e.g., data retransmission (PUSCH 908)) on FR1. As illustrated, PUSCH 902 may be transmitted on FR2. PUSCH 902 may be scheduled using a configured grant (CG). As illustrated, decoding of PUSCH 902 at the BS may have failed. In certain aspects, PDCCH 606 ​​may be received on the same FR (FR2) as the initial data transmission (e.g., PUSCH 902). PDCCH 606 ​​may schedule resources for retransmitting PUSCH 902 (e.g., data retransmission (PUSCH 908)) on FR1. Fig. 9B As illustrated, cross-carrier retransmissions may be implemented using self-carrier scheduling. In other words, PDCCH 612 may be received on the same FR (FR1) as data retransmissions (e.g., PUSCH 908). For example, PDCCH 612 on FR1 may schedule resources on FR1 for use with PUSCH 908 (data retransmissions).

[0079] Fig.10 The preconfiguration of uplink or downlink data retransmissions on a different CC (or FR) than the initial data transmission according to certain aspects of the present disclosure is explained. For example, retransmissions may be preconfigured on a different CC than the initial data transmission. For example, the initial transmission may be on FR2 (e.g., CC 15 of FR2). If the initial transmission fails, the UE automatically switches to (e.g., starts listening to) FR1 to receive or transmit data retransmissions. For example, the initial data transmission 1002 may be on CC15, as illustrated. Once it is determined that the initial data transmission 1002 has failed, the UE automatically starts monitoring CC6 to receive data retransmissions 1006 for the downlink or transmits data retransmissions 1006 for the uplink on CC6. In certain aspects, the PDCCH 1004 may be received on the same CC (e.g., CC6) as the data retransmission 1006.

[0080] In some aspects, the initial transmission cell (e.g., CC15) can be on an unlicensed spectrum, while the retransmission cell (e.g., CC6) can be on a licensed spectrum. In some aspects, the time to switch back to the initial transmission cell (e.g., to monitor other transmissions) can be indicated via the retransmission cell (e.g., CC6). In some aspects, the time to switch back to the initial transmission cell can be indicated by a timer. The timer can be started after switching to the retransmission cell (e.g., CC6) or after the initial transmission. In some aspects, the time to switch back to the initial transmission cell can be a preconfigured time (e.g., at the end of each cycle). For example, the time to switch back to the initial transmission cell can be at the end of the retransmission zone 1012.

[0081] In certain aspects, the HARQ anchor cell ID may be used to facilitate data retransmissions. For example, to allow combining of data transmissions with the same HARQ ID, the downlink control information (DCI) (e.g., PDCCH 612) scheduling DL / UL cross-carrier retransmissions may indicate the cell ID (e.g., HARQ anchor cell ID) that originally owned the HARQ ID. In other words, the DCI (e.g., PDCCH 612) may include a HARQ ID indicating an initial data retransmission associated with the data retransmission, and a HARQ anchor cell ID corresponding to the cell on which the initial transmission was sent. For the downlink, the UE may combine initial data transmissions and retransmissions with the same HARQ anchor cell ID and HARQ ID across different PDSCH receiving cells. For the uplink, the UE may transmit (retransmit) the same TB (e.g., data or payload) with the same HARQ anchor cell ID and HARQ ID across different PUSCH transmitting cells.

[0082] In certain aspects, a PUCCH group may be implemented for cross-carrier retransmissions. For example, for DL ​​cross-carrier retransmissions, the corresponding A / N message may use the PUCCH group configured for the PDSCH receiving cell. For example, if a PDSCH is received on a FR1 cell (e.g., data retransmission 608), the PUCCH group configured for the FR1 cell may be used for A / N message transmission (e.g., PUCCH 610). That is, the A / N message transmission may also be transmitted on the FR1 cell. Alternatively, the PUCCH group configured for the HARQ anchor cell may be used. For example, the A / N message may be transmitted on FR2 (e.g., PDSCH 602) used for initial data transmission.

[0083] In certain aspects, coordinated cells may be implemented for cross-carrier retransmissions, as described herein. For a given HARQ anchor cell, the BS may indicate a group of coordinated cells for potential DL / UL cross-carrier retransmissions. The indication of coordinated cells may allow the UE to establish an internal path to distribute TBs (data) between the retransmitting cell and the anchor cell.

[0084] Example aspects

[0085] In a first aspect, a method for wireless communication comprises: monitoring an initial transmission of data from a network on a first entity; generating a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting the negative acknowledgment message; and monitoring a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0086] In a second aspect, in combination with the first aspect, each of the first entity and the second entity is a frequency resource.

[0087] In a third aspect, in combination with one or more of the first and second aspects, each of the first entity and the second entity is a cell or a component carrier.

[0088] In a fourth aspect, in combination with one or more of the first to third aspects, the method further comprises receiving control information indicating that the second entity is to be monitored for receiving the retransmission of the data.

[0089] In a fifth aspect, in combination with the fourth aspect, the control information is received via the first entity.

[0090] In a sixth aspect, in combination with one or more of the fifth and fourth aspects, the control information is received via the second entity.

[0091] In a seventh aspect, in combination with one or more of aspects 4 to 6, the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID.

[0092] In an eighth aspect, in combination with the seventh aspect, the method further comprises decoding the data by combining the data and the retransmission of the data based on the HARQ process ID and the HARQ anchor entity ID.

[0093] In a ninth aspect, in combination with one or more of the first to eighth aspects, the method further comprises: generating an acknowledgement / negative acknowledgement (A / N) message indicating whether the retransmission of the data is successfully decoded; and transmitting the A / N message to the network.

[0094] In a tenth aspect, in combination with the ninth aspect, the A / N message is transmitted via a third entity.

[0095] In an eleventh aspect, in combination with the tenth aspect, the third entity is configured for the first entity.

[0096] In a twelfth aspect, in combination with one or more of the eleventh and tenth aspects, the third entity is configured for the second entity.

[0097] In a thirteenth aspect, in combination with one or more of the tenth to twelfth aspects, the third entity is a frequency resource.

[0098] In a fourteenth aspect, in combination with one or more of the tenth to thirteenth aspects, the third entity is a cellular cell or a component carrier.

[0099] In a fifteenth aspect, in combination with one or more of the first to fourteenth aspects, the method is performed by a user equipment (UE) that is preconfigured to monitor the second entity to receive the retransmission of the data after the transmission of the negative acknowledgement message.

[0100] In a sixteenth aspect, in combination with one or more of the first to fifteenth aspects, the method further comprises receiving an indication of a coordination entity on which the retransmission of the data may be received, the coordination entity comprising the second entity.

[0101] In a seventeenth aspect, in combination with one or more of the first to sixteenth aspects, the first entity is part of an unlicensed spectrum and wherein the second entity is part of a licensed spectrum.

[0102] In an eighteenth aspect, in combination with one or more of the first to seventeenth aspects, the method further comprises, after monitoring the retransmission of the data, monitoring the first entity for one or more other transmissions.

[0103] In a nineteenth aspect, in combination with the eighteenth aspect, the method further comprises receiving, at the second entity, an indication of when to begin monitoring the first entity for the one or more other transmissions.

[0104] In a twentieth aspect, in combination with one or more of the eighteenth and nineteenth aspects, monitoring the first entity for the one or more other transmissions begins upon expiration of a timer.

[0105] In a twenty-first aspect, in combination with the twentieth aspect, the timer is started after the initial transmission or after switching to the second entity for monitoring the retransmission of the data.

[0106] In a twenty-second aspect, in combination with one or more of aspects eighteen to twenty-first, the retransmission of the data is received during a retransmission cycle, and wherein the first entity is monitored to find the one or more other transmissions starting at the end of the retransmission cycle.

[0107] In a twenty-third aspect, in combination with one or more of the first to twenty-second aspects, the initial transmission is configured using semi-persistent scheduling (SPS).

[0108] In the twenty-fourth aspect, in combination with one or more of the first to twenty-third aspects, the first entity is part of a first frequency range (FR) and the second entity is part of a second frequency range (FR), the second FR having a lower subcarrier spacing (SCS) than the first FR.

[0109] In aspect twenty-fifth, a method for wireless communication comprises: transmitting an initial transmission of data to a UE on a first entity; receiving a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; and transmitting a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0110] In a twenty-sixth aspect, in combination with the twenty-fifth aspect, each of the first entity and the second entity is a frequency resource.

[0111] In a twenty-seventh aspect, in combination with one or more of the twenty-fifth and twenty-sixth aspects, each of the first entity and the second entity is a cellular cell or a component carrier.

[0112] In a twenty-eighth aspect, in combination with one or more of aspects twenty-fifth to twenty-seventh, the method further comprises transmitting control information indicating that the second entity is to be monitored for receiving the retransmission of the data.

[0113] In a twenty-ninth aspect, in combination with the twenty-eighth aspect, the control information is transmitted via the first entity.

[0114] In the thirtieth aspect, in combination with one or more of the twenty-eighth and twenty-ninth aspects, the control information is transmitted via the second entity.

[0115] In the thirty-first aspect, in combination with one or more of aspects 28 to 30, the control information includes a HARQ process ID indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID.

[0116] In a thirty-second aspect, in combination with one or more of aspects twenty-fifth to thirty-first, further comprising receiving an A / N message indicating whether the retransmission of the data was successfully decoded.

[0117] In a thirty-third aspect, in combination with the thirty-second aspect, the A / N message is received via a third entity.

[0118] In a thirty-fourth aspect, in combination with the thirty-third aspect, the third entity is configured for the first entity.

[0119] In a thirty-fifth aspect, in combination with one or more of the thirty-third and thirty-fourth aspects, the third entity is configured for the second entity.

[0120] In a thirty-sixth aspect, in combination with one or more of aspects twenty-fifth to thirty-fifth, the method further comprises transmitting an indication of coordination entities on which the retransmission of the data may be received, the coordination entities comprising the second entity.

[0121] In a thirty-seventh aspect, in combination with one or more of aspects twenty-fifth to thirty-sixth, the first entity is part of an unlicensed spectrum and wherein the second entity is part of a licensed spectrum.

[0122] In a thirty-eighth aspect, in combination with one or more of aspects twenty-fifth to thirty-seventh, further comprising transmitting one or more other transmissions on the first entity after the retransmission of the data.

[0123] In a thirty-ninth aspect, in combination with the thirty-eighth aspect, the method further comprises transmitting, on the second entity, an indication of when to begin monitoring the first entity for the one or more other transmissions.

[0124] In a fortieth aspect, in combination with one or more of the twenty-fifth to thirty-ninth aspects, the initial transmission is configured using SPS.

[0125] In the forty-first aspect, in combination with one or more of the twenty-fifth to fortieth aspects, the first entity is part of a first FR, and the second entity is part of a second FR having a lower SCS than the first FR.

[0126] In a 42nd aspect, a method for wireless communication comprises: transmitting an initial transmission of data to a network on a first entity; generating a retransmission of the data; and transmitting the retransmission of the data on a second entity, the second entity being different from the first entity.

[0127] In a forty-third aspect, in combination with the forty-second aspect, each of the first entity and the second entity is a frequency resource.

[0128] In a 44th aspect, in combination with one or more of the 42nd and 43rd aspects, each of the first entity and the second entity is a cellular cell or a component carrier.

[0129] In a 45th aspect, in combination with one or more of aspects 42 to 44, the method further includes receiving control information indicating that the second entity is to be used to transmit the retransmission of the data.

[0130] In a forty-sixth aspect, in combination with the forty-fourth aspect, the control information is received via the first entity.

[0131] In a forty-seventh aspect, in combination with one or more of the forty-fifth and forty-sixth aspects, the control information is received via the second entity.

[0132] In aspect 48, in combination with one or more of aspects 45 to 47, the control information includes a HARQ process ID indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID.

[0133] In a 49th aspect, in combination with one or more of aspects 42 to 48, the method is performed by a UE that is preconfigured to transmit the retransmission of the data via the second entity.

[0134] In a fiftieth aspect, in combination with one or more of aspects 42 to 49, the method further comprises receiving an indication of a coordination entity over which the retransmission of the data may be transmitted, the coordination entity comprising the second entity.

[0135] In the fifty-first aspect, in combination with one or more of the forty-second to fiftieth aspects, the first entity is part of an unlicensed spectrum and wherein the second entity is part of a licensed spectrum.

[0136] In a fifty-second aspect, in combination with one or more of aspects forty-second to fifty-first, the initial transmission is configured using a configured grant (CG).

[0137] In a fifty-third aspect, in combination with one or more of aspects forty-second to fifty-second, the first entity is part of a first FR, and the second entity is part of a second FR having a lower SCS than the first FR.

[0138] In a fifty-fourth aspect, a method for wireless communication comprises: monitoring an initial transmission of data from a UE on a first entity; and receiving a retransmission of the data on a second entity, the second entity being different from the first entity.

[0139] In a fifty-fifth aspect, in combination with the fifty-fourth aspect, each of the first entity and the second entity is a frequency resource.

[0140] In a fifty-sixth aspect, in combination with one or more of the fifty-fourth aspect and the fifty-fifth aspect, each of the first entity and the second entity is a cellular cell or a component carrier.

[0141] In a fifty-seventh aspect, in combination with one or more of aspects fifty-four to fifty-six, the method further comprises transmitting control information indicating that the second entity is to be used to transmit the retransmission of the data.

[0142] In a fifty-eighth aspect, in combination with the fifty-seventh aspect, the control information is transmitted via the first entity.

[0143] In a fifty-ninth aspect, in combination with one or more of the fifty-seventh aspect and the fifty-eighth aspect, the control information is transmitted via the second entity.

[0144] In the sixtieth aspect, in combination with one or more of aspects fifty-seven to fifty-ninth aspects, the control information includes a HARQ process ID indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID.

[0145] In the sixty-first aspect, in combination with one or more of the fifty-fourth to sixty-first aspects, the method further includes transmitting an indication of a coordination entity on which the retransmission of the data may be transmitted, the coordination entity including the second entity.

[0146] In a sixty-second aspect, in combination with one or more of aspects fifty-four to sixty-one, the first entity is part of an unlicensed spectrum and wherein the second entity is part of a licensed spectrum.

[0147] In a sixty-third aspect, in combination with one or more of aspects fifty-four to sixty-second, the initial transmission is configured using a CG.

[0148] In a sixty-fourth aspect, in combination with one or more of the fifty-fourth to sixty-third aspects, the first entity is part of a first FR and the second entity is part of a second FR having a lower SCS than the first FR.

[0149] In the sixty-fifth aspect, a device for wireless communication comprises: a memory; and one or more processors coupled to the memory, the one or more processors and the memory being configured to: monitor an initial transmission of data from a network on a first entity; generate a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; transmit the negative acknowledgment message; and monitor a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0150] In the sixty-sixth aspect, an apparatus for wireless communication comprises: a device for monitoring an initial transmission of data from a network on a first entity; a device for generating a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; a device for transmitting the negative acknowledgment message; and a device for monitoring a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0151] In a sixty-seventh aspect, a computer-readable medium having stored thereon computer executable code for wireless communication comprises: code for monitoring an initial transmission of data from a network on a first entity; code for generating a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; code for transmitting the negative acknowledgment message; and code for monitoring a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0152] In a sixty-eighth aspect, an apparatus for wireless communication comprises: a memory; and one or more processors coupled to the memory, the one or more processors and the memory being configured to: transmit an initial transmission of data to a UE on a first entity; receive a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; and transmit a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity. In a sixty-ninth aspect, an apparatus for wireless communication comprises: means for transmitting an initial transmission of data to a UE on a first entity; means for receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; and means for transmitting a retransmission of the data on a second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

[0153] In the seventieth aspect, a computer-readable medium having stored thereon computer executable code for wireless communication comprises: code for transmitting an initial transmission of data to a UE on a first entity; code for receiving a negative acknowledgment message indicating that decoding of the initial transmission of the data was unsuccessful; and code for transmitting a retransmission of the data on a second entity after the transmission of the negative acknowledgment message, the second entity being different from the first entity.

[0154] In the seventy-first aspect, a device for wireless communication comprises: a memory; and one or more processors coupled to the memory, the one or more processors and the memory being configured to: transmit an initial transmission of data to a network on a first entity; generate a retransmission of the data; and transmit the retransmission of the data on a second entity, the second entity being different from the first entity.

[0155] In aspect seventy-second, an apparatus for wireless communications comprises: means for transmitting an initial transmission of data to a network on a first entity; means for generating a retransmission of the data; and means for transmitting the retransmission of the data on a second entity, the second entity being different from the first entity.

[0156] In a seventy-third aspect, a computer-readable medium having stored thereon computer executable code for wireless communication comprises: code for transmitting an initial transmission of data to a network on a first entity; code for generating a retransmission of the data; and code for transmitting the retransmission of the data on a second entity, the second entity being different from the first entity.

[0157] In a seventy-fourth aspect, a device for wireless communication comprises: a memory; and one or more processors coupled to the memory, the one or more processors and the memory being configured to: monitor an initial transmission of data from a user equipment UE on a first entity; and receive a retransmission of the data on a second entity, the second entity being different from the first entity.

[0158] In a seventy-fifth aspect, an apparatus for wireless communication comprises: means for monitoring an initial transmission of data from a UE on a first entity; and means for receiving a retransmission of the data on a second entity, the second entity being different from the first entity.

[0159] In a seventy-sixth aspect, a computer-readable medium having stored thereon computer executable code for wireless communication comprises: code for monitoring an initial transmission of data from a UE on a first entity; and code for receiving a retransmission of the data on a second entity, the second entity being different from the first entity.

[0160] In the seventy-seventh aspect, a device for wireless communication comprises: a processor, and a memory coupled to the processor, wherein the processor and the memory are configured to: execute the method of any one of the first aspect to the sixty-fourth aspect.

[0161] In a seventy-eighth aspect, an apparatus for wireless communication comprises at least one device for performing the method of any one of aspects one to sixty-four.

[0162] In the seventy-ninth aspect, a non-transitory computer-readable medium storing code for wireless communication comprises: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform a method as in any one of aspects 1 to 64.

[0163] Fig.11 The following describes operations that may include being configured to perform the techniques disclosed herein (such as Figure 4 and 7 1100 includes a communication device 1100 that includes various components (e.g., corresponding to means-plus-function components) of the operations illustrated in the foregoing. The communication device 1100 includes a processing system 1102 coupled to a transceiver 1108. The transceiver 1108 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1100 via an antenna 1110. The processing system 1102 may be configured to perform processing functions for the communication device 1100, including processing signals received and / or to be transmitted by the communication device 1100.

[0164] The processing system 1102 includes a processor 1104 coupled to a computer readable medium / memory 1112 via a bus 1106. In some aspects, the computer readable medium / memory 1112 is configured to store a program that, when executed by the processor 1104, causes the processor 1104 to execute Figure 4 and 7 1104 may include instructions (e.g., computer executable code) for performing the operations illustrated in , or other operations for various techniques for cross-carrier retransmission discussed herein. In some aspects, the computer-readable medium / memory 1112 stores code 1114 for monitoring; code 1116 for generating; and code 1118 for transmitting. In some aspects, the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium / memory 1112. The processor 1104 includes circuitry 1120 for monitoring; circuitry 1122 for generating; and circuitry 1124 for transmitting.

[0165] Fig.12 The following describes operations that may include being configured to perform the techniques disclosed herein (such as Figure 5 and8 1200 includes a communication device 1200 that includes various components (e.g., corresponding to means-plus-function components) of the operations illustrated in the foregoing. The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208. The transceiver 1208 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1200 via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.

[0166] The processing system 1202 includes a processor 1204 coupled to a computer readable medium / memory 1212 via a bus 1206. In some aspects, the computer readable medium / memory 1212 is configured to store a program that, when executed by the processor 1204, causes the processor 1204 to execute Figure 5 and 8 1204 may include instructions (e.g., computer executable code) for performing the operations illustrated in , or other operations for various techniques for cross-carrier retransmission discussed herein. In some aspects, the computer-readable medium / memory 1212 stores code 1214 for monitoring; code 1216 for receiving; and code 1218 for transmitting. In some aspects, the processor 1204 has circuitry configured to implement the code stored in the computer-readable medium / memory 1212. The processor 1204 includes circuitry 1220 for monitoring; circuitry 1222 for receiving; and circuitry 1224 for transmitting.

[0167] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2, although unlike the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0168] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "sub-6 GHz" and the like can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used in this article, the term "millimeter wave" and the like can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0169] The techniques described herein may be used for various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR is an emerging wireless communication technology under development.

[0170] The techniques described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations.

[0171] In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B (NB) and / or a NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and BS, next-generation Node B (gNB or g B Node), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. The BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0172] UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0173] Fig.131 and 120a (eg, in the example embodiment of the present invention) that can be used to implement various aspects of the present disclosure. Figure 1 Example components of the wireless communication network 100).

[0174] At BS 110a, a transmit processor 1320 may receive data from a data source 1312 and control information from a controller / processor 1340. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a PDCCH, a group common PDCCH (GC PDCCH), etc. The data may be for a PDSCH, etc. The processor 1320 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 1320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 1330 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide output symbol streams to modulators (MODs) 1,332a-1,332t. Each modulator 1332 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 1,332a-1,332t may be transmitted via antennas 1,334a-1,334t, respectively.

[0175] At UE 120a, antennas 1352a-1352r may receive downlink signals from BS 110a and may provide received signals to demodulators (DEMODs) in transceivers 1354a-1354r, respectively. Each demodulator 1354 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1356 may obtain received symbols from all demodulators 1354a-1354r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 1358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 1360, and provide decoded control information to a controller / processor 1380.

[0176] On the uplink, at the UE 120a, a transmit processor 1364 may receive and process data (e.g., for PUSCH) from a data source 1362 and control information (e.g., for PUCCH) from a controller / processor 1380. The transmit processor 1364 may also generate reference symbols for a reference signal (e.g., SRS). The symbols from the transmit processor 1364 may be precoded by a TX MIMO processor 1366, if applicable, further processed by a demodulator 1354a-1354r in a transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signal from the UE 120a may be received by an antenna 1334, processed by a modulator 1332, detected by a MIMO detector 1336, if applicable, and further processed by a receive processor 1338 to obtain decoded data and control information sent by the UE 120a. The receive processor 1338 may provide decoded data to a data sink 1339 and decoded control information to a controller / processor 1340 .

[0177] Memories 1342 and 1382 may store data and program codes for BS 110a and UE 120a, respectively.A scheduler 1344 may schedule UEs for data transmission on the downlink and / or uplink.

[0178] The controller / processor 1380 and / or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. Fig.13 As shown in FIG. 1 , the controller / processor 1340 of BS 110a has a cross-carrier manager 112, which can be configured for cross-carrier retransmissions according to various aspects described herein. Fig.13 As shown in FIG. 1 , the controller / processor 1380 of the UE 120a has a cross-carrier manager 122 that can be configured for cross-carrier retransmissions according to various aspects described herein. Although shown at the controller / processor, other components of the UE 120a and the BS 110a can also be used to perform the operations described herein.

[0179] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 RBs), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0180] NR can utilize OFDM with CP on the uplink and downlink and includes support for half-duplex operation using TDD. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16...time slots), depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. In some examples, the MIMO configuration in the DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. In some examples, multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

[0181] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication between some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may be used as a scheduling entity, and resources for one or more subordinate entities (e.g., one or more other UEs) may be scheduled, and other UEs may use resources scheduled by the UE for wireless communications. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

[0182] In some examples, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

[0183] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be changed without departing from the scope of the claims.

[0184] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0185] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0186] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to ordinary technicians in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 USC§112(f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for..."

[0187] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0188] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0189] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0190] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0191] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0192] Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0193] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein, such as instructions for performing the operations described herein.

[0194] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0195] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication, comprising: monitoring an initial transmission of data from a network at a first entity; generating a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting the negative acknowledgement message; receiving control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as The retransmission of the data on the second entity is monitored after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

2. The method of claim 1, wherein each of the first entity and the second entity is a frequency resource. 3 . The method of claim 1 , wherein each of the first entity and the second entity is a cellular cell or a component carrier. The method of claim 1 , wherein the control information is received via the first entity. The method of claim 1 , wherein the control information is received via the second entity.

6. The method of claim 1, further comprising decoding the data by combining the data and the retransmission of the data based on the HARQ process ID and the HARQ anchor entity ID.

7. The method of claim 1, further comprising: generating an acknowledgement / non-acknowledgement (A / N) message indicating whether the retransmission of the data was successfully decoded; as well as The A / N message is transmitted to the network. The method of claim 7 , wherein the A / N message is transmitted via a third entity.

9. The method of claim 8, wherein the third entity is configured for the first entity.

10. The method of claim 8, wherein the third entity is configured for the second entity. The method of claim 8 , wherein the third entity is a frequency resource.

12. The method of claim 8, wherein the third entity is a cellular cell or a component carrier.

13. The method of claim 1, wherein the method is performed by a user equipment (UE) preconfigured to monitor the second entity to receive the retransmission of the data after the transmission of the negative acknowledgement message.

14. The method of claim 1, further comprising receiving an indication of a coordination entity at which the retransmission of the data may be received, the coordination entity comprising the second entity.

15. The method of claim 1, wherein the first entity is part of an unlicensed spectrum, and wherein the second entity is part of a licensed spectrum.

16. The method of claim 1, further comprising, after monitoring the retransmission of the data, monitoring the first entity for one or more other transmissions.

17. The method of claim 16, further comprising receiving, at the second entity, an indication of when to begin monitoring the first entity for the one or more other transmissions.

18. The method of claim 16, wherein monitoring the first entity for the one or more other transmissions is initiated upon expiration of a timer.

19. The method of claim 18, wherein the timer is started after the initial transmission or after a switch to the second entity for monitoring the retransmission of the data.

20. The method of claim 16, wherein the retransmission of the data is received during a retransmission cycle, and wherein the first entity is monitored for the one or more other transmissions to begin at an end of the retransmission cycle.

21. The method of claim 1, wherein the initial transmission is configured using semi-persistent scheduling (SPS).

22. The method of claim 1, wherein the first entity is part of a first frequency range (FR) and the second entity is part of a second frequency range (FR), the second FR having a lower subcarrier spacing (SCS) than the first FR.

23. A method for wireless communication, comprising: transmitting, on a first entity, an initial transmission of data to a user equipment (UE); receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as The retransmission of the data is transmitted on the second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

24. The method of claim 23, wherein each of the first entity and the second entity is a frequency resource.

25. The method of claim 23, wherein each of the first entity and the second entity is a cell or a component carrier.

26. The method of claim 23, wherein the control information is transmitted via the first entity.

27. The method of claim 23, wherein the control information is transmitted via the second entity.

28. The method of claim 23, further comprising: An acknowledgement / non-acknowledgement (A / N) message is received indicating whether the retransmission of the data was successfully decoded.

29. The method of claim 28, wherein the A / N message is received via a third entity.

30. The method of claim 29, wherein the third entity is configured for the first entity.

31. The method of claim 29, wherein the third entity is configured for the second entity.

32. The method of claim 23, further comprising transmitting an indication of a coordination entity at which the retransmission of the data may be received, the coordination entity comprising the second entity.

33. The method of claim 23, wherein the first entity is part of an unlicensed spectrum, and wherein the second entity is part of a licensed spectrum.

34. The method of claim 23, further comprising transmitting one or more other transmissions on the first entity after the retransmission of the data.

35. The method of claim 34, further comprising transmitting, at the second entity, an indication of when to begin monitoring the first entity for the one or more other transmissions.

36. The method of claim 23, wherein the initial transmission is configured using semi-persistent scheduling (SPS).

37. The method of claim 23, wherein the first entity is part of a first frequency range (FR) and the second entity is part of a second frequency range (FR), the second FR having a lower subcarrier spacing (SCS) than the first FR.

38. A method for wireless communication, comprising: transmitting, at the first entity, an initial transmission of data to the network; generating a retransmission of the data; receiving control information indicating that a second entity is to be used to transmit the retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; and The retransmission of the data is transmitted on the second entity, the second entity being different from the first entity.

39. The method of claim 38, wherein each of the first entity and the second entity is a frequency resource.

40. The method of claim 38, wherein each of the first entity and the second entity is a cell or a component carrier.

41. The method of claim 38, wherein the control information is received via the first entity.

42. The method of claim 38, wherein the control information is received via the second entity.

43. The method of claim 38, wherein the method is performed by a user equipment (UE), the UE being preconfigured to transmit the retransmission of the data via the second entity.

44. The method of claim 38, further comprising receiving an indication of a coordination entity over which the retransmission of the data may be transmitted, the coordination entity comprising the second entity.

45. The method of claim 38, wherein the first entity is part of an unlicensed spectrum, and wherein the second entity is part of a licensed spectrum.

46. ​​The method of claim 38, wherein the initial transmission is configured using a configured grant (CG).

47. The method of claim 38, wherein the first entity is part of a first frequency range (FR) and the second entity is part of a second frequency range (FR), the second FR having a lower subcarrier spacing (SCS) than the first FR.

48. A method for wireless communication, comprising: monitoring an initial transmission of data from a user equipment (UE) on a first entity; transmitting control information indicating that a second entity is to be used to transmit a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as The retransmission of the data on the second entity is received, the second entity being different from the first entity.

49. The method of claim 48, wherein each of the first entity and the second entity is a frequency resource.

50. The method of claim 48, wherein each of the first entity and the second entity is a cell or a component carrier.

51. The method of claim 48, wherein the control information is transmitted via the first entity.

52. The method of claim 48, wherein the control information is transmitted via the second entity.

53. The method of claim 48, further comprising transmitting an indication of a coordination entity over which the retransmission of the data may be transmitted, the coordination entity comprising the second entity.

54. The method of claim 48, wherein the first entity is part of an unlicensed spectrum, and wherein the second entity is part of a licensed spectrum.

55. The method of claim 48, wherein the initial transmission is configured using a configured grant (CG).

56. The method of claim 48, wherein the first entity is part of a first frequency range (FR) and the second entity is part of a second frequency range (FR), the second FR having a lower subcarrier spacing (SCS) than the first FR.

57. A device for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors and the memory being configured to: monitoring an initial transmission of data from a network at a first entity; generating a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting the negative acknowledgement message; receiving control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier indicating the initial transmission of the data corresponding to the retransmission (ID), and wherein the control information further includes The HARQ anchor entity ID associated with the ID; and The retransmission of the data on the second entity is monitored after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

58. A device for wireless communication, comprising: means for monitoring an initial transmission of data from a network at a first entity; means for generating a negative acknowledgement message indicating that decoding of said initial transmission of said data was unsuccessful; means for transmitting said negative acknowledgement message; means for receiving control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as means for monitoring the retransmission of the data on the second entity after transmission of the negative acknowledgement message, the second entity being different from the first entity.

59. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for monitoring an initial transmission of data from a network at a first entity; code for generating a negative acknowledgement message indicating that decoding of said initial transmission of said data was unsuccessful; a code for transmitting said negative acknowledgement message; code for receiving control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as Code for monitoring the retransmission of the data at the second entity after transmission of the negative acknowledgment message, the second entity being different than the first entity.

60. A device for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors and the memory being configured to: transmitting, on a first entity, an initial transmission of data to a user equipment (UE); receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; transmitting control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier indicating the initial transmission of the data corresponding to the retransmission (ID), and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as The retransmission of the data is transmitted on the second entity after the transmission of the negative acknowledgement message, the second entity being different from the first entity.

61. A device for wireless communication, comprising: means for transmitting an initial transmission of data to a user equipment (UE) at a first entity; means for receiving a negative acknowledgement message indicating that decoding of said initial transmission of said data was unsuccessful; means for transmitting control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as Means for transmitting the retransmission of the data on the second entity after transmission of the negative acknowledgement message, the second entity being different from the first entity.

62. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for transmitting an initial transmission of data to a user equipment (UE) at a first entity; code for receiving a negative acknowledgement message indicating that decoding of the initial transmission of the data was unsuccessful; code for transmitting control information indicating that a second entity is to be monitored for receiving a retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as Code for transmitting the retransmission of the data on the second entity after transmission of the negative acknowledgment message, the second entity being different from the first entity.

63. A device for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors and the memory being configured to: transmitting, at the first entity, an initial transmission of data to the network; generating a retransmission of the data; receiving control information indicating that a second entity is to be used to transmit the retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier indicating the initial transmission of the data corresponding to the retransmission (ID), and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; and The retransmission of the data is transmitted on the second entity, the second entity being different from the first entity.

64. A device for wireless communication, comprising: means for transmitting an initial transmission of data to the network at the first entity; means for generating a retransmission of said data; means for receiving control information indicating that a second entity is to be used to transmit the retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as Means for transmitting the retransmission of the data on the second entity, the second entity being different from the first entity.

65. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for transmitting an initial transmission of data to a network at a first entity; code for generating a retransmission of said data; code for receiving control information indicating that a second entity is to be used to transmit the retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as Code for transmitting the retransmission of the data on the second entity, the second entity being different than the first entity.

66. A device for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors and the memory being configured to: monitoring an initial transmission of data from a user equipment (UE) on a first entity; transmitting control information indicating that a second entity is to be used to transmit a retransmission of the data, wherein the control information includes a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further includes a HARQ anchor entity ID associated with the HARQ process ID; as well as The retransmission of the data on the second entity is received, the second entity being different from the first entity.

67. A device for wireless communication, comprising: means for monitoring an initial transmission of data from a user equipment (UE) on a first entity; means for transmitting control information indicating that a second entity is to be used to transmit a retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as Means for receiving the retransmission of the data on the second entity, the second entity being different than the first entity.

68. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for monitoring an initial transmission of data from a user equipment (UE) at a first entity; code for transmitting control information indicating that a second entity is to be used to transmit a retransmission of the data, wherein the control information comprises a hybrid automatic repeat request (HARQ) process identifier (ID) indicating the initial transmission of the data corresponding to the retransmission, and wherein the control information further comprises a HARQ anchor entity ID associated with the HARQ process ID; as well as Code for receiving the retransmission of the data at the second entity, the second entity being different than the first entity.

Images