Techniques for cross-carrier repetition

Abstract

Certain aspects of the present disclosure provide techniques for cross-carrier repetition. A method that may be performed by a user equipment (UE) includes: monitoring an initial transmission of data from a network at a first entity; receiving control information indicating a second entity for receiving retransmission repetitions of the data; and receiving retransmission repetitions of the data via the second entity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 16 / 904,394, filed on June 17, 2020, which claims priority to and the benefit of U.S. Provisional Application No. 62 / 867,655, filed on June 27, 2019, both of which are hereby assigned to the assignee of this application and are hereby expressly incorporated herein by reference 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 techniques for data repetition.

[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 at a first entity; receiving control information indicating a second entity for receiving retransmissions of the data, wherein one or more of the second entities is different from the first entity; and receiving the retransmissions of the data via the second entity.

[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) on a first entity; transmitting control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and transmitting the retransmission repetitions of the data via the second 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, receiving control information from a second entity indicating retransmission iterations for transmitting the data, wherein one or more of the second entities is different from the first entity, and transmitting the retransmission iterations of the data via the second entity in accordance with the control information.

[0013] Certain aspects relate to a method for wireless communication. The method generally includes receiving an initial transmission of data from a UE at a first entity, transmitting control information to a second entity indicating retransmissions of the data, wherein one or more of the second entities is different from the first entity, and receiving retransmissions of the data via the second 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 at a first entity; receive control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and receive the retransmission repetitions of the data via the second 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 at a first entity, means for receiving control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and means for receiving retransmission repetitions of the data via the second 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 receiving control information indicating a second entity to receive retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for receiving retransmission repetitions of the data via the second entity.

[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 UE on a first entity; transmit control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and transmit the retransmission repetitions of the data via the second 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 transmitting control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and means for transmitting retransmission repetitions of the data via the second 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 on a first entity; code for transmitting control information indicating a second entity to receive retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for transmitting the retransmission repetitions of the data via the second 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 at a first entity; receive control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and transmit the retransmission repetitions of the data via the second entity in accordance with the control information.

[0021] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes means for transmitting an initial transmission of data to a network at a first entity; means for receiving control information from a second entity indicating retransmission repetitions for transmitting the data, wherein one or more of the second entities is different from the first entity; and means for transmitting the retransmission repetitions of the data via the second entity in accordance with the control information.

[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 receiving control information from a second entity indicating retransmission repetitions for transmitting the data, wherein one or more of the second entities is different from the first entity; and code for transmitting the retransmission repetitions of the data via the second entity in accordance with the control information.

[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: receive an initial transmission of data from a UE on a first entity; transmit control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and receive retransmission repetitions of the data via the second entity.

[0024] Certain aspects relate to an apparatus for wireless communication. The apparatus generally includes means for receiving an initial transmission of data from a UE on a first entity, means for transmitting control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and means for receiving retransmission repetitions of the data via the second entity.

[0025] Certain aspects relate to a computer-readable medium. The computer-readable medium generally includes code for receiving an initial transmission of data from a UE at a first entity; code for transmitting control information to a second entity indicating retransmission repetitions for transmitting the data, wherein one or more of the second entities is different from the first entity; and code for receiving retransmission repetitions of the data via the second 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.

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

[0032] Figure 4 is 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] Figure 6 Cross-carrier repetition in accordance with certain aspects of the present disclosure is illustrated.

[0035] Figure 7 Various signaling aspects that may be implemented for cross-carrier data repetition are illustrated in accordance with certain aspects of the present disclosure.

[0036] Fig. 8A , 8B 8C illustrate cross-carrier data repetition utilizing multiple control and independent acknowledgement / negative acknowledgement (A / N) messages in accordance with certain aspects of the present disclosure.

[0037] Fig. 9A , 9B 9C illustrate cross-carrier data repetition implemented with a single control message and a common A / N message in accordance with certain aspects of the present disclosure.

[0038] Fig. 10A , 10B 10C illustrate cross-carrier data repetition utilizing a single control message and independent A / N messages in accordance with certain aspects of the present disclosure.

[0039] Fig.11A , 11B 11C illustrate cross-carrier data repetition utilizing multiple control messages and a common A / N message in accordance with certain aspects of the present disclosure.

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

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

[0042] Fig.14 Various signaling aspects that may be implemented for cross-carrier data repetition are illustrated in accordance with certain aspects of the present disclosure.

[0043] Fig.15A and 15B Illustrated is cross-carrier uplink data repetition implemented with multiple downlink control information (DCI), in accordance with certain aspects of the present disclosure.

[0044] Fig.16A and 16B Illustrated is cross-carrier uplink data repetition for scheduling repetitions at each repetition occasion implemented with a single control message in accordance with certain aspects of the present disclosure.

[0045] Fig.17 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.

[0046] Fig.18 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.

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

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

[0049] Detailed Description

[0050] Various aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for cross-carrier repetition. For example, multiple entities may be used to send repetitions of data transmissions. As used herein, the term "entity" generally refers to a frequency resource, a component carrier, or a cellular cell.

[0051] The data transmission may include uplink or downlink data transmission. For example, for downlink data transmission, if the decoding of the initial data transmission has failed, the user equipment (UE) may receive control information for scheduling data repetitions of the data. The repetitions of the data may be combined to facilitate decoding at the UE, as described in more detail herein. Similarly, for uplink data transmission, if the decoding of the initial uplink data transmission has failed at a base station (BS) (e.g., a next generation Node B (gNB)), the UE may receive control information for scheduling uplink data repetitions. In some cases, the control information may be carried in separate control messages, which may be independent or related. In other cases, the control information for scheduling various repetitions may be carried in a single control message.

[0052] In some cases, the control information may include various identifiers (such as a hybrid automatic request (HARQ) process identification (ID) and a HARQ anchor cell ID) that facilitate the transmission of data repetitions and the decoding of data repetitions, as described in more detail herein. In certain aspects, a separate or common acknowledgement / negative acknowledgement (A / N) message may be sent to indicate whether one or more of the data repetitions have been successfully decoded at the UE.

[0053] The following description provides an example of traffic burst perception 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 devices 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.

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

[0055] 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).

[0056] like Figure 1As 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.

[0057] According to certain aspects, BS 110 and UE 120 may be configured for cross-carrier repetition. 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 repetition. Figure 1 As shown in FIG. 1 , 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 repetition.

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

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

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

[0061] 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 can be part of the same FR. For example, CC1 can use a first FR (FR1) and CC2 can use a second FR (FR2). The configuration of each FR can be different. For example, FR1 can have a smaller bandwidth (BW) than FR2, but has fewer blocking issues. FR1 can have a lower subcarrier spacing (SCS) than FR2. For example, the SCS of FR1 is 60, while the SCS of FR2 is 120.

[0062] Example Techniques for Cross-Carrier Repetition

[0063] Certain aspects of the present disclosure generally relate to cross-carrier repetition. For example, several component carriers may be used to send repetitions of data transmission. Data transmission may include uplink or downlink data transmission. For downlink data transmission, repetitions of data may be combined to facilitate decoding at a user equipment (UE). Although various examples provided herein are described with respect to frequency resources, cellular cells, or component carriers to facilitate understanding, various aspects of the present disclosure may be implemented for any entity. As used herein, the term "entity" generally refers to a frequency resource, a cellular cell, or a component carrier (e.g., a frequency resource, a cellular cell, or a component carrier). Repetition of data transmission generally refers to retransmission of at least a portion of a data transmission (e.g., one or more transport blocks (TBs)) or different redundant versions of at least a portion of a data transmission. Data repetitions may be combined to facilitate decoding of data.

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

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

[0066] Operations 400 may begin at block 405 with the UE monitoring an initial transmission of data from a network at a first entity. At block 410, the UE receives control information indicating a second entity for receiving retransmission repetitions of the data. At block 415, the UE receives retransmission repetitions of the data via the second entity. In some aspects, one or more of the second entities may be different from the first entity. As used herein, the term "entity" generally refers to a frequency resource, a cell, or a component carrier.

[0067] In certain aspects, the control information may be received via separate control messages (e.g., separate physical downlink control channels (PDCCHs)), each of which is received prior to a corresponding one of the retransmissions of the data. Each of the control messages may indicate a second entity for receiving the retransmissions. In some cases, the control messages may be related. For example, at least one of the control messages may indicate resources allocated for receiving another of the control messages. Each of the control messages may indicate a corresponding one of the second entities.

[0068] In certain aspects, the control information may be received via a single control message indicating a second entity for receiving retransmission repetitions of data. In this case, the control information may include a retransmission allocation index indicating a second entity for receiving retransmission repetitions of data.

[0069] In certain aspects, repetitions of data may be combined to facilitate decoding at the UE. For example, the retransmission repetitions of data may include a first retransmission repetition of data and a second retransmission repetition of data. The UE may decode the first retransmission repetition by combining the first retransmission repetition of data and the initial transmission of data, and generate a first acknowledgment / negative acknowledgment (A / N) message indicating whether the decoding of the first retransmission repetition of data is successful. The UE may also decode the second retransmission repetition by combining the first retransmission repetition of data, the second retransmission repetition of data, and the initial transmission of data. The UE may then generate a second A / N message indicating whether the decoding of the second retransmission repetition of data is successful. The UE may transmit the first A / N message and the second A / N message to the network entity.

[0070] In some cases, the A / N bit position may be determined based on the data repetition position relative to an uplink (UL) feedback channel (e.g., a physical uplink control channel (PUCCH)). For example, a first A / N message may be carried in a first A / N codebook, and the bit position of the first A / N message in the first A / N codebook may correspond to one of the second entity associated with the first retransmission repetition. A second A / N message may be carried in a second A / N codebook, and the bit position of the second A / N message in the second A / N codebook may correspond to another of the second entity associated with the second retransmission repetition. In some cases, the first and second A / N messages may be carried by the same or different UL A / N feedback resources (e.g., the same or different PUCCH). Each of the different UL A / N feedback resources may be configured for each of the first and second entities for receiving each of the retransmission repetitions. In certain aspects, the same UL A / N feedback resource may be configured for all or one of the first and second entities receiving the retransmission repetitions.

[0071] In some aspects, a common A / N message may be used. For example, the retransmission repetition of the data may include a first retransmission repetition of the data and a second retransmission repetition of the data. The UE may decode the retransmission repetition by combining the first retransmission repetition of the data, the second retransmission repetition of the data, and the initial transmission of the data. The UE may then generate an A / N message indicating whether the decoding of the retransmission repetition of the data is successful, and transmit the A / N message to the network. In some aspects, the A / N message is carried in an A / N codebook, and the bit position of the A / N message in the A / N codebook is determined based on one of the retransmission repetitions for the data in the second entity. In some cases, the control information may indicate the one of the resources for transmitting the A / N message based on which the A / N message is determined in the second entity. In some aspects, the A / N message may be carried by the same or different UL A / N feedback resources. Each of the different UL A / N feedback resources may be configured for each of the first and second entities for receiving each retransmission repetition in the retransmission repetition. In some cases, the same UL A / N feedback resource may be configured for all or one of the first and second entities for receiving the retransmission repetition.

[0072] In some aspects, an initial transmission of data may be monitored during a transmission opportunity, and if the data is not successfully decoded during the transmission opportunity, a retransmission repetition of the data may be monitored during a retransmission time window. In some aspects, the control information may include a hybrid automatic repeat request (HARQ) process identifier (ID) indicating an initial transmission of data corresponding to the retransmission repetition. The control information may also include a HARQ anchor entity ID associated with the first entity. The HARQ process ID and the HARQ anchor entity ID may facilitate decoding of the retransmission repetition (combining).

[0073] 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 base station (BS), such as, for example, BS 110a in wireless communication network 100. Operations 500 may be operations performed by a BS that are complementary to operations 400 performed by a UE.

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

[0075] Operations 500 may begin with the BS transmitting an initial transmission of data to the UE on a first entity at block 505. At block 510, the BS transmits control information indicating a second entity for receiving retransmission repetitions of the data. At block 515, the BS transmits retransmission repetitions of the data via the second entity.

[0076] Figure 6 Cross-carrier repetition according to certain aspects of the present disclosure is illustrated. For example, if an initial downlink / uplink (DL) / (UL) transmission fails, retransmissions can be dynamically repeated on any available CC (or any entity, such as a cell, CC, or frequency resource), and if any repetition passes (e.g., successfully decoded), the retransmission is successful. When retransmissions are needed, reliability in tight timelines can be improved by opportunistically utilizing all available frequency resources. For example, Figure 6 As illustrated in FIG. 1 , an initial data transmission 602 (e.g., a physical downlink shared channel (PDSCH)) may be received on a CC (e.g., CC15). The initial data transmission 602 may be scheduled using semi-persistent scheduling (SPS). An uplink control message 604 (e.g., PUCCH) indicating a negative acknowledgment may be sent. A negative acknowledgment may indicate that the initial data transmission 602 was not successfully decoded. During a retransmission opportunity 614 (also referred to herein as a retransmission zone), a repetition of the initial data transmission 602 may be received. For example, data repetitions 606, 608, 610, 612 (also referred to herein as retransmission repetitions) may be sent during the retransmission opportunity. In some cases, downlink control messages 616, 618, 620, 622 (e.g., PDCCH) may be transmitted before the corresponding data repetitions 606, 608, 610, 612. In certain aspects, uplink control messages 624, 626 (PUCCH) may be sent, which may indicate whether the data repetitions were successfully decoded. As illustrated, an initial data transmission 602 may be sent over a first frequency range (FR1) and a second data repetition may be sent over a second frequency range (FR2) having a lower SCS than the first FR.

[0077] Figure 7Various signaling aspects 700 that can be implemented for cross-carrier PDSCH repetitions according to certain aspects of the present disclosure are explained. As explained, cross-carrier PDSCH repetitions can be implemented using multiple variants depending on signaling selections (including scheduling DCI, A / N messages for repetitions, and identification for the same repetition set). For example, repetitions can be scheduled by a single DCI or multiple DCIs with independent or related scheduling information. The A / N message for each repetition can be implemented using a common or independent A / N bit and a bit position in an A / N codebook carried by a UL feedback channel, as described herein. Repetitions with the same payload can be identified by an explicit repetition group ID or by a certain time window for UE combination. For example, data repetitions to be combined at the UE can indicate the same group ID, allowing the UE to identify the repetitions to be combined, or the UE can be configured to combine repetitions during a preconfigured time window. Various signaling aspects are described in more detail herein.

[0078] Fig. 8A , 8B 8C illustrate cross-carrier data repetition using multiple DCIs and independent A / N messages in accordance with certain aspects of the present disclosure. To provide diversity for both data and control, each PDSCH repetition may be scheduled by an individual DCI carried in a separate PDCCH, which may be on the same CC as the corresponding PDSCH repetition. Fig. 8A , each PDSCH repetition (e.g., data repetitions 606, 610) may be associated with a corresponding A / N message in a control message 624, 626 (e.g., PUCCH) carried by a PUCCH configured for the corresponding PDSCH recipient cell, respectively. As long as one repetition passes (e.g., is successfully decoded), the retransmission may be considered successful. In certain aspects, to facilitate combining the repetition with at least a previous data transmission, each downlink control message (e.g., DCI) may indicate a HARQ anchor cell ID and a HARQ process ID. The cell used to transmit the PUCCH may be the same or different for different PDSCH recipient cells depending on the configuration for cross-carrier repetitions. In other words, the PUCCH (e.g., control message 624) used to acknowledge the data repetition 606 may be on the same cell (e.g., CC) as the data repetition 606 or on a different cell (e.g., CC).

[0079] Figure 8BBS-side operations for cross-carrier data repetitions in accordance with certain aspects of the present disclosure are illustrated. For example, for the same HARQ anchor cell ID and HARQ process ID, if an acknowledgement (ACK) is not received before the end of the last expected A / N transmission opportunity (e.g., at the end of the first retransmission opportunity 830) for the previous PDSCH repetition (e.g., data repetitions 606, 610) (e.g., in an A / N message in a control message 624 (PUCCH)), the BS 110 retransmits the data repetitions 806, 808 (PDSCH). A downlink control message 802, 804 (PDCCH) may be included before each of the data repetitions 806, 808 that schedules resources for the data repetitions 806, 808. The BS 110 may schedule a new transmission after receiving the earliest ACK (e.g., in a control message 810 (PUCCH)) across all repetitions during the retransmission opportunity, and the resources for the remaining repetitions may be canceled or reassigned to other traffic / UEs. The control messages 810 , 812 (PUCCH) may be used to acknowledge the corresponding data repetitions 806 , 808 .

[0080] like Figure 8C , the UE 120 may attempt to decode the individual PDSCH repetitions by combining log-likelihood ratios (LLRs) stored from previous transmissions for the same TB / code block group (CBG) (data) indicated in the corresponding DCI. For example, the data repetitions 806 may be decoded by combining the data repetitions 806, 610, 606 and the initial data transmission 602, as illustrated. The downlink control message 804 may indicate a HARQ process ID and a HARQ anchor cell ID, allowing the UE to identify the data transmission for combining. As illustrated, the A / N in the control message 810 (PUCCH) may be generated based on the individual repetition decoding results.

[0081] Fig. 9A , 9B 9C illustrate cross-carrier data repetition using a single DCI and a common A / N message according to certain aspects of the present disclosure. Fig. 9A As illustrated in , all PDSCH repetitions for retransmission occasions may be scheduled by a single DCI in a control message (e.g., control message 620 (PDCCH)) and have a common A / N bit carried by a single control message 626 (PUCCH) configured for one of the PDSCH repetition recipient cells (e.g., the cell with the smallest SCS). The position of the A / N bit in the codebook may be based on one of the PDSCH repetition occasions (e.g., the last PDSCH repetition occasion, such as data repetition 606). A single DCI (e.g., control message) may indicate an allocation per PDSCH, or a preconfigured repetition allocation index corresponding to an allocation for an entity for PDSCH repetitions. As Fig. 9B As explained in , for the same HARQ anchor cell ID and HARQ process ID, if an ACK is not received on the only expected A / N transmission opportunity (e.g., in the control message 626 (PUCCH)) for the previous PDSCH repetition (e.g., in the retransmission opportunity 830), the BS retransmits the PDSCH repetition.

[0082] For the SCS of the repeating receiving cell, the time between each PDSCH repetition and the corresponding PUCCH should be at least N1 (eg, the minimum time gap). The minimum time gap will ensure that the UE can generate the corresponding decoding result before the PUCCH transmission time.

[0083] like Fig. 9C , after receiving the DCI, the UE attempts to decode each TB / CBG (e.g., data) by combining the LLRs of all scheduled PDSCH repetitions and the LLRs stored from the previous transmission(s) for the same TB / CBG. An A / N may be generated based on a single decoding result across all repetitions. In other words, data repetitions 808, 806, 610, 606 and initial data transmission 602 may be combined for decoding, and the decoding results may be used to generate an A / N message to be transmitted via a control message 810 (PUCCH).

[0084] Fig. 10A , 10B 10C illustrates cross-carrier data repetitions implemented with a single DCI and independent A / N messages in accordance with certain aspects of the present disclosure. As illustrated, PDSCH repetitions (e.g., data repetitions 606, 610) may be scheduled by a single DCI (e.g., carried in a control message 620 (e.g., PDCCH)) and associated with their own corresponding A / N messages carried in control messages 624, 626 (e.g., PUCCH) configured for the corresponding PDSCH receiving cell. In other words, the A / N message in the control message 624 (e.g., PUCCH) indicates whether the data repetition 606 is successfully decoded at the UE, while the A / N message in the control message 626 (e.g., PUCCH) indicates whether the data repetition 606 is successfully decoded at the UE. As long as one repetition passes (e.g., is successfully decoded), the retransmission (e.g., repetition) is considered successful. The single DCI in the control message 620 (PDCCH) may indicate an allocation per PDSCH or a preconfigured repetition allocation index, as described herein. The cell used to transmit the PUCCH may be the same or different for different PDSCH recipient cells depending on the configuration, as described herein.

[0085] As explained, in Fig. 10B, BS 110 may transmit a single DCI to schedule data repetitions for its corresponding retransmission occasions during each retransmission opportunity carried in control message 620 (e.g., PDCCH) and control message 804 (e.g., PDCCH). For the same HARQ anchor cell ID and HARQ process ID, if an acknowledgement (ACK) is not received before the end of the last expected A / N transmission opportunity for the previous PDSCH repetition (e.g., in control message 624 (PUCCH)), BS 110 retransmits the PDSCH repetition. The BS may schedule a new transmission after receiving the earliest A / N message (e.g., ACK carried in control message 810 (PUCCH)) across all repetitions. As Fig. 10C As explained in , the UE may attempt to decode individual PDSCH repetitions by combining LLRs stored from previous transmissions for the same TB / CBG indicated in the corresponding DCI, as described herein. The A / N messages carried in the control messages 810, 812 (PUCCH) are generated based on the individual repetition decoding results of the corresponding data repetitions 806, 808.

[0086] Fig.11A , 11B 11C and 11C illustrate cross-carrier data repetitions implemented using multiple DCIs and a common A / N message in accordance with certain aspects of the present disclosure. Each PDSCH repetition may be scheduled by an individual DCI (e.g., carried in control messages 616, 620 (PDCCH)), which may be on the same CC as the corresponding repetition. Data repetitions 606, 610 may be associated with a common A / N bit carried by a single control message 626 (PUCCH) configured for one of the PDSCH repetition receiving cells (e.g., the cell (CC0) with the smallest SCS). The position of the A / N bit in the codebook may be based on one of the PDSCH repetition occasions (e.g., the last PDSCH repetition occasion, such as a PDSCH repetition (e.g., data repetition 606)). Alternatively, the PDSCH repetition occasion that determines the position of the A / N bit may be signaled in each DCI (e.g., in control messages 616, 620 (PDCCH)) to avoid DCI misdetection. For example, the DCI in the control message 620 (eg, PDCCH) may indicate that the PDSCH repetitions (eg, data repetitions 610) are to be used to determine the location of the A / N bits in the control message 626 (eg, PUCCH).

[0087] like Fig. 11BAs explained in , for the same HARQ anchor cell ID and HARQ process ID, if an ACK is not received on the only expected A / N transmission opportunity for the previous PDSCH repetition, BS 110 retransmits the PDSCH repetition as described herein. For the SCS of the repetition receiving cell, the time between each PDSCH repetition and the PUCCH should be at least N1 (e.g., the minimum time gap).

[0088] like Fig. 11C As explained in , the UE attempts to decode individual PDSCH repetitions by combining LLRs stored from previous transmissions for the same TB / CBG indicated in the corresponding DCI. Each of the data repetitions may be assigned its own A / N message. After determining the A / N for all data repetitions using the detected DCI, a common A / N is calculated and sent via a single control message 810 (PUCCH). If at least one of the data repetitions is successfully decoded, the common A / N may be an ACK, otherwise, the common A / N is a negative acknowledgement (NACK).

[0089] Certain aspects of the present disclosure relate to cross-carrier physical uplink shared channel (PUSCH) repetition (eg, uplink data repetition). For example, once an initial PUSCH transmission fails, repetition of the PUSCH may be configured via a single or multiple PDCCHs, as described in more detail herein.

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

[0091] Operation 1200 may be implemented as a processor on one or more processors (e.g., Fig.19 In addition, signal transmission and reception by the UE in operation 1200 may be performed by one or more antennas (e.g., Fig.19 In some aspects, signal transmission and / or reception by the UE may be implemented via a bus interface of one or more processors (eg, controller / processor 1980) that obtain and / or output signals.

[0092] Operations 1200 may begin at block 1205 with the UE transmitting an initial transmission of data to a network at a first entity, and receiving control information of a second entity indicating retransmission repetitions for transmitting the data at block 1210. At block 1215, the UE may transmit retransmission repetitions of the data via the second entity in accordance with the control information. In some aspects, one or more of the second entities are different from the first entity.

[0093] In some aspects, the control information may be received via separate control messages, each of which is received prior to a corresponding one of the retransmissions of the data. For example, each of the control messages may indicate a second entity for transmitting the retransmissions. In some cases, the control messages may be related. For example, at least one of the control messages may indicate resources allocated for receiving another of the control messages. In some aspects, each of the control messages indicates a corresponding one of the second entities.

[0094] In some cases, the control information is received via a single control message indicating the second entity for retransmission repetitions of transmitting data. In this case, the control information may include a retransmission allocation index indicating the second entity for retransmission repetitions of transmitting data.

[0095] In some aspects, an initial transmission of data is transmitted during a transmission opportunity, and if the data is not successfully decoded during the transmission opportunity, a retransmission repetition of the data is transmitted during a retransmission time window. In some aspects, the control information may include a HARQ process ID indicating an initial transmission of data corresponding to the retransmission repetition, and a HARQ anchor entity ID associated with the first entity, as described herein. In some aspects, the retransmission repetition of data may include a repetition of the data or include a different redundant version of the data. In some cases, the first entity may be part of a first FR, and one or more of the second entities may be part of a second FR, the second FR having a lower SCS than the first FR. In some cases, the retransmission repetition of data may include the same group ID. In some cases, the initial transmission is configured using a CG.

[0096] Fig.13 13 is a flow diagram illustrating example operations 1300 for wireless communication in accordance with certain aspects of the present disclosure. Operations 1300 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 1200 performed by a UE.

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

[0098] Operations 1300 may begin at block 1305 with the BS receiving an initial transmission of data from a UE at a first entity and transmitting control information indicating a second entity for transmitting retransmissions of the data at block 1310. At block 1315, the BS may receive retransmissions of the data via the second entity.

[0099] Fig.14 Various signaling aspects 1400 that may be implemented for cross-carrier PUSCH repetitions in accordance with certain aspects of the present disclosure are illustrated. As illustrated, cross-carrier PUSCH repetitions may be implemented with a variety of variations depending on signaling selections, including scheduling DCIs and identification for the same repetition set. For example, repetitions may be scheduled by a single DCI or multiple DCIs with independent or related scheduling information. Repetitions with the same payload may be identified by an explicit repetition group ID or by a certain time window. Various signaling aspects are described in greater detail herein.

[0100] Fig.15A and 15B The present invention illustrates cross-carrier uplink data (PUSCH) repetitions using multiple DCIs in accordance with certain aspects of the present disclosure. To provide diversity for both data and control, each PUSCH repetition is scheduled by an individual DCI, which may be on the same CC as the corresponding PUSCH repetition. Fig.15A As illustrated in , each of the data (PUSCH) repetitions 1506, 1510 of the initial data transmission 1502 may be scheduled using corresponding control messages 1516, 1520 (e.g., PDCCH), respectively. As long as one repetition is successfully decoded by the BS 110, the retransmission may be considered successful. In certain aspects, to facilitate combining the repetition with at least the previous data transmission, each DCI may indicate a HARQ anchor cell ID and a HARQ process ID. Each DCI may also indicate the same TB / CBG for the UE to send on different repetitions. As shown in FIG. Fig. 15B , for the same HARQ anchor cell ID and HARQ process ID, if the PUSCH is not correctly received from the previous PUSCH repetition transmission (e.g., the repetition in the retransmission opportunity 1530), the BS 110 retransmits the data repetitions 1506, 1508 (PUSCH). For example, the BS 110 may schedule the data repetitions 1506, 1508 via the corresponding DCI carried in the corresponding PDCCH 1503, 1504. The BS may schedule a new transmission after receiving the earliest PUSCH (e.g., data repetition 1506) across all repetitions, and resources for the remaining one or more repetitions (e.g., data repetition 1508) may be canceled or reassigned to other traffic / UEs.

[0101] Fig.16A and16B Cross-carrier uplink data (e.g., PUSCH) repetitions for scheduling repetitions at each repetition opportunity using a single DCI in accordance with certain aspects of the present disclosure are illustrated. As illustrated, all data (PUSCH) repetitions 1506, 1510 are scheduled by a single DCI carried in a control message 1520 (PDCCH) at a retransmission opportunity 1530. The single DCI indicates an allocation per PUSCH repetition or a preconfigured repetition allocation index, as described herein. Fig. 16B , for the same HARQ anchor cell ID and HARQ process ID, if the PUSCH was not successfully decoded in the previous PUSCH repetition (e.g., in the retransmission opportunity 1530), the BS 110 may receive the PUSCH repetition. The BS 110 may schedule a new transmission after receiving the earliest PUSCH repetition (e.g., data repetition 1506) across all repetitions, and resources for the remaining repetitions (e.g., data repetition 1508) may be canceled / reallocated to other traffic / UEs.

[0102] Example aspects

[0103] In a first aspect, a method for wireless communication comprises: monitoring an initial transmission of data from a network on a first entity; receiving control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and receiving the retransmission repetitions of the data via the second entity.

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

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

[0106] In a fourth aspect, in combination with one or more of the first to third aspects, the control information is received via separate control messages, each of the control messages being received prior to a corresponding one of the retransmission repetitions of the data.

[0107] In a fifth aspect, in combination with the fourth aspect, each of the control messages indicates a second entity for receiving retransmission repetitions.

[0108] In a sixth aspect, in combination with the fifth aspect, at least one of the control messages indicates resources allocated for receiving another of the control messages.

[0109] In a seventh aspect, in combination with one or more of the fourth to sixth aspects, each of the control messages indicates a corresponding one of the second entities.

[0110] In an eighth aspect, in combination with one or more of the first to seventh aspects, the control information is received via a single control message instructing a second entity to receive retransmission repetitions of the data.

[0111] In a ninth aspect, in combination with the eighth aspect, the control information includes a retransmission allocation index indicating a second entity for receiving a retransmission repetition of the data.

[0112] In the tenth aspect, in combination with one or more of the first to ninth aspects, the retransmission repetitions of the data include a first retransmission repetition of the data and a second retransmission repetition of the data, and the method further includes: decoding the first retransmission repetition by combining the first retransmission repetition of the data and the initial transmission of the data; generating a first A / N message indicating whether the decoding of the first retransmission repetition of the data is successful; decoding the second retransmission repetition by combining the first retransmission repetition of the data, the second retransmission repetition of the data, and the initial transmission of the data; generating a second A / N message indicating whether the decoding of the second retransmission repetition of the data is successful; and transmitting the first A / N message and the second A / N message to the network.

[0113] In the eleventh aspect, in combination with the tenth aspect, the first A / N message is carried in a first A / N codebook, and the bit position of the first A / N message in the first A / N codebook corresponds to one associated with the first retransmission repetition in the second entity, and wherein the second A / N message is carried in a second A / N codebook, and the bit position of the second A / N message in the second A / N codebook corresponds to another associated with the second retransmission repetition in the second entity.

[0114] In a twelfth aspect, in combination with the eleventh aspect, the first and second A / N messages are carried by different uplink (UL) A / N feedback resources, wherein each of the different UL A / N feedback resources is configured to be used for each of the first and second entities for receiving each of the retransmission repetitions.

[0115] In the thirteenth aspect, in combination with one or more of the eleventh aspect and the twelfth aspect, the first and second A / N messages are carried by the same UL A / N feedback resource, wherein the same UL A / N feedback resource is configured to be used for one or more of receiving retransmission repetitions in the first and second entities.

[0116] In the fourteenth aspect, in combination with one or more of the first to thirteenth aspects, the retransmission repetitions of the data include a first retransmission repetition of the data and a second retransmission repetition of the data, and the method further includes: decoding the retransmission repetitions by combining the first retransmission repetition of the data, the second retransmission repetition of the data, and the initial transmission of the data; generating an A / N message indicating whether the decoding of the retransmission repetition of the data is successful; and transmitting the A / N message to the network.

[0117] In a fifteenth aspect, in combination with the fourteenth aspect, the A / N message is carried in an A / N codebook, and a bit position of the A / N message in the A / N codebook is determined based on one of the retransmission repetitions for data in the second entity.

[0118] In a sixteenth aspect, in combination with the fifteenth aspect, the control information indicates one of the second entities based on which resources for transmitting the A / N message are determined.

[0119] In the seventeenth aspect, in combination with one or more of the fifteenth aspect and the sixteenth aspect, the A / N message is carried by different UL A / N feedback resources, and each of the different UL A / N feedback resources is configured to be used for each of the first and second entities for receiving each of the retransmission repetitions.

[0120] In the eighteenth aspect, in combination with one or more of the fifteenth to seventeenth aspects, the A / N message is carried by the same UL A / N feedback resource, and wherein the same UL A / N feedback resource is configured to be used for one or more of the first and second entities for receiving retransmission repetitions.

[0121] In the nineteenth aspect, in combination with one or more of the first to eighteenth aspects, the initial transmission of the data is monitored during a transmission opportunity, and wherein in the event that the data is not successfully decoded during the transmission opportunity, the retransmission repetition of the data is monitored during a retransmission time window.

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

[0123] In a twenty-first aspect, in combination with one or more of the first to twentieth aspects, the retransmission repetition of the data comprises a repetition of the data.

[0124] In a twenty-second aspect, in combination with one or more of the first to twenty-first aspects, the retransmission repetitions of the data include retransmission repetitions of different redundant versions of the data.

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

[0126] In a twenty-fourth aspect, in combination with one or more of the first to twenty-third aspects, the retransmission repetitions of the data include the same group ID.

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

[0128] In aspect twenty-six, a method for wireless communication comprises: transmitting an initial transmission of data to a user equipment (UE) on a first entity; transmitting control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and transmitting retransmission repetitions of the data via the second entity.

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

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

[0131] In a twenty-ninth aspect, in combination with one or more of aspects twenty-six to twenty-eight, the control information is transmitted via separate control messages, each of the control messages being transmitted prior to a corresponding one of the retransmission repetitions of the data.

[0132] In a thirtieth aspect, in combination with the twenty-ninth aspect, each of the control messages indicates a second entity for receiving retransmission repetitions.

[0133] In the thirty-first aspect, in combination with the thirtieth aspect, at least one of the control messages indicates resources allocated for transmitting another of the control messages.

[0134] In a thirty-second aspect, in combination with one or more of aspects twenty-ninth to thirty-first, each of the control messages indicates a corresponding one of the second entities.

[0135] In a thirty-third aspect, in combination with one or more of aspects twenty-six to thirty-second, the control information is transmitted via a single control message instructing a second entity to receive retransmission repetitions of the data.

[0136] In a thirty-fourth aspect, in combination with the thirty-third aspect, the control information includes a retransmission allocation index indicating a second entity for receiving retransmission repetitions of the data.

[0137] In aspect thirty-fifth, in combination with one or more of aspects twenty-six to thirty-four, the retransmission repetition of the data includes a first retransmission repetition of the data and a second retransmission repetition of the data, and the method further includes: receiving a first confirmation / negative confirmation (A / N) message indicating whether the decoding of the first retransmission repetition of the data is successful; and receiving a second A / N message indicating whether the decoding of the second retransmission repetition of the data is successful.

[0138] In the thirty-sixth aspect, in combination with the thirty-fifth aspect, the first A / N message is carried in a first A / N codebook, and the bit position of the first A / N message in the first A / N codebook corresponds to one associated with the first retransmission repetition in the second entity, and wherein the second A / N message is carried in a second A / N codebook, and the bit position of the second A / N message in the second A / N codebook corresponds to another associated with the second retransmission repetition in the second entity.

[0139] In the thirty-seventh aspect, in combination with the thirty-sixth aspect, the first and second A / N messages are carried by different uplink (UL) A / N feedback resources, wherein each of the different UL A / N feedback resources is configured to be used for each of the first and second entities for transmitting each of the retransmission repetitions.

[0140] In aspect thirty-eight, in combination with one or more of aspects thirty-six and thirty-seven, the first and second A / N messages are carried by the same UL A / N feedback resource, wherein the same UL A / N feedback resource is configured to be used for one or more of the first and second entities for transmitting retransmission repetitions.

[0141] In aspect thirty-ninth, in combination with one or more of aspects thirty-six to thirty-eight, the retransmission repetition of the data includes a first retransmission repetition of the data and a second retransmission repetition of the data, and the method further includes: receiving an A / N message indicating whether the decoding of the retransmission repetition of the data is successful.

[0142] In the 40th aspect, in combination with the 39th aspect, the A / N message is carried in an A / N code book, and the bit position of the A / N message in the A / N code book is determined based on one of a first retransmission repetition for the data and a second retransmission repetition for the data in a second entity.

[0143] In the forty-first aspect, in combination with the fortieth aspect, the control information indicates one of the second entities based on which resources for transmitting the A / N message are determined.

[0144] In aspect 42, in combination with one or more of aspect 40 and aspect 41, the A / N message is carried by different UL A / N feedback resources, wherein each of the different UL A / N feedback resources is configured to be used for each of each of the retransmission repetitions in the first and second entities for transmitting the retransmission repetitions.

[0145] In aspect 43, in combination with one or more of aspects 40 to 42, the A / N message is carried by the same UL A / N feedback resource, wherein the same UL A / N feedback resource is configured to be used for one or more of the first and second entities for transmitting retransmission repetitions.

[0146] In aspect 44, in combination with one or more of aspects 26 to 43, an initial transmission of the data is transmitted during a transmission opportunity, and wherein, if the data is not successfully decoded during the transmission opportunity, a retransmission of the data is transmitted during a retransmission time window.

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

[0148] In a forty-sixth aspect, in combination with one or more of aspects twenty-six to forty-fifth, the retransmission repetition of the data comprises a repetition of the data.

[0149] In a 47th aspect, in combination with one or more of aspects 26 to 46, the retransmissions of the data include retransmissions of different redundant versions of the data.

[0150] In a 48th aspect, in combination with one or more of aspects 26 to 47, the first entity is part of a first FR, and one or more of the second entities is part of a second FR having a lower SCS than the first FR.

[0151] In a forty-ninth aspect, in combination with one or more of the twenty-sixth to forty-eighth aspects, the retransmissions of the data include the same group ID.

[0152] In a fiftieth aspect, in combination with one or more of aspects twenty-six to forty-ninth, the initial transmission is configured using SPS.

[0153] In a fifty-first aspect, a method for wireless communication comprises: transmitting an initial transmission of data to a network on a first entity; receiving control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and transmitting retransmission repetitions of the data via the second entity based on the control information.

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

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

[0156] In a fifty-fourth aspect, in combination with one or more of aspects fifty-one to fifty-three, the control information is received via separate control messages, each of the control messages being received prior to a corresponding one of the retransmissions of the data.

[0157] In a fifty-fifth aspect, in combination with the fifty-fourth aspect, each of the control messages indicates a second entity for transmitting retransmission repetitions.

[0158] In a fifty-sixth aspect, in combination with the fifty-fifth aspect, at least one of the control messages indicates resources allocated to receiving another of the control messages.

[0159] In a fifty-seventh aspect, in combination with one or more of the fifty-fourth to fifty-sixth aspects, each of the control messages indicates a corresponding one of the second entities.

[0160] In a fifty-eighth aspect, in combination with one or more of aspects fifty-one to fifty-seven, the control information is received via a single control message to a second entity indicating retransmission repetitions for transmitting the data.

[0161] In a fifty-ninth aspect, in combination with the fifty-eighth aspect, the control information includes a retransmission allocation index of a second entity indicating a retransmission repetition for transmitting the data.

[0162] In the sixtieth aspect, in combination with one or more of aspects fifty-first to fifty-ninth aspects, an initial transmission of the data is transmitted during a transmission opportunity, and wherein, if the data is not successfully decoded during the transmission opportunity, a retransmission of the data is transmitted during a retransmission time window.

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

[0164] In a sixty-second aspect, in combination with one or more of aspects fifty-first to sixty-first, the retransmission repetition of the data comprises repetition of the data.

[0165] In a sixty-third aspect, in combination with one or more of aspects fifty-first to sixty-second, the retransmissions of the data include retransmissions of different redundant versions of the data.

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

[0167] In a sixty-fifth aspect, in combination with one or more of the fifty-first to sixty-fourth aspects, the retransmissions of the data include the same group ID.

[0168] In a sixty-sixth aspect, in combination with one or more of aspects fifty-one to fifty-six, the initial transmission is configured using a configured grant (CG).

[0169] In aspect sixty-seven, a method for wireless communication comprises: receiving an initial transmission of data from a UE on a first entity; transmitting control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and receiving retransmission repetitions of the data via the second entity.

[0170] In a sixty-eighth aspect, in combination with the sixty-seventh aspect, each of the first entity and the second entity is a frequency resource.

[0171] In a sixty-ninth aspect, in combination with one or more of the sixty-seventh aspect and the sixty-eighth aspect, each of the first entity and the second entity is a cellular cell or a component carrier.

[0172] In the seventieth aspect, in combination with one or more of aspects sixty-seven to sixty-ninth, the control information is transmitted via separate control messages, each of the control messages being transmitted prior to a corresponding one of the retransmission repetitions of the data.

[0173] In the seventy-first aspect, in combination with the seventieth aspect, each of the control messages indicates a second entity for transmitting a retransmission repetition.

[0174] In a seventy-second aspect, in combination with one or more of the seventieth aspect and the seventy-first aspect, at least one of the control messages indicates resources allocated for transmitting another of the control messages.

[0175] In a seventy-third aspect, in combination with one or more of aspects seventieth to seventy-second, each of the control messages indicates a corresponding one of the second entities.

[0176] In a seventy-fourth aspect, in combination with one or more of aspects sixty-seventh to seventy-third, the control information is transmitted via a single control message indicating a second entity for retransmission repetitions of transmitting the data.

[0177] In a seventy-fifth aspect, in combination with the seventy-fourth aspect, the control information includes a retransmission allocation index of a second entity indicating a retransmission repetition for transmitting the data.

[0178] In aspect seventy-six, in combination with one or more of aspects sixty-seven to seventy-fif, an initial transmission of the data is received during a transmission opportunity, and wherein, in the event that the data is not successfully decoded during the transmission opportunity, a retransmission of the data is received during a retransmission time window.

[0179] In aspect seventy-seven, in combination with one or more of aspects sixty-seven to seventy-six, the control information includes a HARQ process ID indicating an initial transmission of data corresponding to a retransmission repetition, and wherein the control information further includes a HARQ anchor entity ID associated with the first entity.

[0180] In a seventy-eighth aspect, in combination with one or more of aspects sixty-seven to seventy-seven, the retransmission repetition of the data comprises a repetition of the data.

[0181] In a seventy-ninth aspect, in combination with one or more of aspects sixty-seventh to seventy-eighth, the retransmissions of the data include retransmissions of different redundant versions of the data.

[0182] In an eightieth aspect, in combination with one or more of aspects sixty-seven to seventy-ninth, the first entity is part of a first FR, and one or more of the second entities is part of a second FR having a lower SCS than the first FR.

[0183] In the eighty-first aspect, in combination with one or more of the sixty-seventh to eightieth aspects, the retransmission of the data includes the same group ID.

[0184] In an eighty-second aspect, in combination with one or more of aspects sixty-seven to eighty-first, the initial transmission is configured using SPS.

[0185] In an eighty-third 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: monitor an initial transmission of data from a network on a first entity; receive control information indicating a second entity for receiving retransmissions of the data, wherein one or more of the second entities is different from the first entity; and receive retransmissions of the data via the second entity.

[0186] In an eighty-fourth aspect, an apparatus for wireless communication comprises: means for monitoring an initial transmission of data from a network on a first entity; means for receiving control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and means for receiving retransmission repetitions of the data via the second entity.

[0187] In an eighty-fifth 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 at a first entity; code for receiving control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for receiving retransmission repetitions of the data via the second entity.

[0188] In an eighty-sixth 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; transmit control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and transmit retransmission repetitions of the data via the second entity.

[0189] In the eighty-seventh aspect, an apparatus for wireless communication comprises: a device for transmitting an initial transmission of data to a UE on a first entity; a device for transmitting control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and a device for transmitting retransmission repetitions of the data via the second entity.

[0190] In an eighty-eighth 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 transmitting control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for transmitting retransmission repetitions of the data via the second entity.

[0191] In an eighty-ninth 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 network on a first entity; receive control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and transmit retransmission repetitions of the data via the second entity based on the control information.

[0192] In the ninetieth aspect, an apparatus for wireless communication comprises: a device for transmitting an initial transmission of data to a network on a first entity; a device for receiving control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and a device for transmitting retransmission repetitions of the data via the second entity based on the control information.

[0193] In a ninety-first 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 receiving control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for transmitting retransmission repetitions of the data via the second entity based on the control information.

[0194] In a ninety-second 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: receive an initial transmission of data from a UE on a first entity; transmit control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities are different from the first entity; and receive retransmission repetitions of the data via the second entity.

[0195] In a ninety-third aspect, an apparatus for wireless communication comprises: a device for receiving an initial transmission of data from a UE on a first entity; a device for transmitting control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and a device for receiving retransmission repetitions of the data via the second entity.

[0196] In a ninety-fourth aspect, a computer-readable medium having stored thereon computer executable code for wireless communication comprises: code for receiving an initial transmission of data from a UE on a first entity; code for transmitting control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity; and code for receiving retransmission repetitions of the data via the second entity.

[0197] In a ninety-fifth aspect, an apparatus for wireless communication comprises: a processor, and a memory coupled to the processor, the processor and the memory being configured to execute a method as in any one of aspects one to eighty-second.

[0198] In a ninety-sixth aspect, an apparatus for wireless communication comprises at least one apparatus for performing a method as in any one of aspects one to eighty-second aspects.

[0199] In the ninety-seventh 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 the first to eighty-second aspects.

[0200] Fig.17 The description may include a method configured to perform operations for the techniques disclosed herein (such as Figure 4 and 12 1700 includes various components (e.g., corresponding to means-plus-function components) of the communication device 1700 and the operations explained in the foregoing. The communication device 1700 includes a processing system 1702 coupled to a transceiver 1708. The transceiver 1708 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1700 via an antenna 1710. The processing system 1702 may be configured to perform processing functions for the communication device 1700, including processing signals received and / or to be transmitted by the communication device 1700.

[0201] The processing system 1702 includes a processor 1704 coupled to a computer readable medium / memory 1712 via a bus 1706. In some aspects, the computer readable medium / memory 1712 is configured to store a program that, when executed by the processor 1704, causes the processor 1704 to execute Figure 4 and 12 1704 includes circuitry 1724 for monitoring; circuitry 1726 for receiving; circuitry 1728 for decoding; circuitry 1730 for generating; and circuitry 1732 for transmitting.

[0202] Fig.18 The description may include a method configured to perform operations for the techniques disclosed herein (such as Figure 5 and 13 1800 includes a communication device 1800 that includes various components (e.g., corresponding to means-plus-function components) of the operations illustrated in 1800. The communication device 1800 includes a processing system 1802 coupled to a transceiver 1808. The transceiver 1808 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1800 via an antenna 1810. The processing system 1802 may be configured to perform processing functions for the communication device 1800, including processing signals received and / or to be transmitted by the communication device 1800.

[0203] The processing system 1802 includes a processor 1804 coupled to a computer readable medium / memory 1812 via a bus 1806. In some aspects, the computer readable medium / memory 1812 is configured to store a program that, when executed by the processor 1804, causes the processor 1804 to execute Figure 5 and 13 1804 includes circuitry 1820 for transmitting; circuitry 1822 for receiving.

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

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

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

[0207] The techniques described herein may 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.

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

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

[0210] Fig.19Explains methods that can be used to implement various aspects of the present disclosure (e.g., Figure 1 1900 of example components 1900 of a BS 110a and a UE 120a in a wireless communication network 100.

[0211] At BS 110a, a transmit processor 1920 may receive data from a data source 1912 and control information from a controller / processor 1940. 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 1920 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 1920 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 1930 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to modulators (MODs) 1,932a-1,932t. Each modulator 1932 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 1932a-1932t may be transmitted via antennas 1934a-1934t, respectively.

[0212] At UE 120a, antennas 1952a-1952r may receive downlink signals from BS 110a and may provide received signals to demodulators (DEMODs) in transceivers 1954a-1954r, respectively. Each demodulator 1954 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 1956 may obtain received symbols from all demodulators 1954a-1954r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 1958 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 1960, and provide decoded control information to a controller / processor 1980.

[0213] On the uplink, at the UE 120a, a transmit processor 1964 may receive and process data from a data source 1962 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 1980 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 1964 may also generate reference symbols for a reference signal (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 1964 may be precoded by a TX MIMO processor 1966, if applicable, further processed by a demodulator 1954a-1954r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At BS 110a, the uplink signal from UE 120a may be received by antenna 1934, processed by modulator 1932, detected by MIMO detector 1936 if applicable, and further processed by receive processor 1938 to obtain decoded data and control information sent by UE 120a. Receive processor 1938 may provide decoded data to data sink 1939 and decoded control information to controller / processor 1940.

[0214] Memories 1942 and 1982 may store data and program codes for BS 110a and UE 120a, respectively.A scheduler 1944 may schedule UEs for data transmission on the downlink and / or uplink.

[0215] The controller / processor 1980 and / or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. Fig.19 As shown in FIG. 1 , the controller / processor 1940 of the BS 110a has a cross-carrier manager 112, which can be configured for cross-carrier repetition according to various aspects described herein. Fig.19 As shown in FIG. 1 , the controller / processor 1980 of the UE 120a has a cross-carrier manager 122 that can be configured for cross-carrier repetition in accordance with 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.

[0216] 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.8 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.

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

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

[0219] 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).

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

[0221] 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).

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

[0223] 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 those of ordinary skill 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 U.S.C. § 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...".

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

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

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

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

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

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

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

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

[0232] 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, at the first entity, an initial transmission of data from the network; receiving, via a separate control message during each retransmission opportunity, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is received via the second entity.

2. The method according to claim 1, wherein the retransmission repetition of the data comprises a first retransmission repetition of the data and a second retransmission repetition of the data, the method further comprising: decoding the first retransmission repetition of the data by combining the first retransmission repetition of the data with an initial transmission of the data; generating a first A / N message indicating whether decoding of a first retransmission of the data is successful; decoding the second retransmission repetition by combining a first retransmission repetition of the data, a second retransmission repetition of the data, and an initial transmission of the data; generating a second A / N message indicating whether decoding of a second retransmission of the data is successful; as well as The first A / N message and the second A / N message are transmitted to the network.

3. The method of claim 2, wherein the first A / N message is carried in a first A / N codebook, and a bit position of the first A / N message in the first A / N codebook corresponds to a third entity in the second entity, wherein the third entity is associated with the first retransmission repetition, wherein the second A / N message is carried in a second A / N codebook, and a bit position of the second A / N message in the second A / N codebook corresponds to a fourth entity in the second entity, and wherein the fourth entity is associated with the second retransmission repetition.

4. The method of claim 3 , wherein the first A / N message and the second A / N message are carried by different uplink (UL) A / N feedback resources, and wherein each of the different UL A / N feedback resources is configured for use by each of the first entity and the second entity for receiving each of the retransmission repetitions.

5. The method of claim 3, wherein the first A / N message and the second A / N message are carried by the same uplink (UL) A / N feedback resource, wherein the same UL A / N feedback resource is configured to be used for one or more of receiving retransmission repetitions in the first entity and the second entity.

6. The method according to claim 1, wherein the retransmission repetition of the data comprises a first retransmission repetition of the data and a second retransmission repetition of the data, the method further comprising: decoding the retransmission repetition by combining a first retransmission repetition of the data, a second retransmission repetition of the data, and an initial transmission of the data; generating an A / N message indicating whether decoding of a retransmission of the data is successful; as well as The A / N message is transmitted to the network.

7. The method of claim 6, wherein the A / N message is carried in an A / N codebook, and a bit position of the A / N message in the A / N codebook is determined based on one of the retransmission repetitions for the data in the second entity.

8. The method of claim 7, wherein the A / N message is carried by different UL A / N feedback resources, and wherein each of the different UL A / N feedback resources is configured for each of the first entity and the second entity for receiving each of the retransmission repetitions.

9. The method of claim 7, wherein the A / N message is carried by the same UL A / N feedback resource, and wherein the same UL A / N feedback resource is configured for one or more of the first entity and the second entity for receiving retransmission repetitions.

10. A method for wireless communication, comprising: transmitting, on a first entity, an initial transmission of data to a user equipment (UE); transmitting, via a separate control message during each retransmission opportunity, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions of the data and indicates the second entity for receiving the retransmission repetition; and Retransmission iterations of the data are transmitted via the second entity.

11. The method according to claim 10, wherein the retransmission repetition of the data comprises a first retransmission repetition of the data and a second retransmission repetition of the data, and the method further comprises: receiving a first acknowledgement / negative acknowledgement (A / N) message indicating whether decoding of a first retransmission iteration of the data was successful; as well as A second A / N message is received indicating whether decoding of a second retransmission of the data is successful.

12. The method of claim 11, wherein the first A / N message is carried in a first A / N codebook, and a bit position of the first A / N message in the first A / N codebook corresponds to a third entity in the second entity, wherein the third entity is associated with the first retransmission repetition, wherein the second A / N message is carried in a second A / N codebook, and a bit position of the second A / N message in the second A / N codebook corresponds to a fourth entity in the second entity, and wherein the fourth entity is associated with the second retransmission repetition.

13. The method of claim 12, wherein the first A / N message and the second A / N message are carried by different uplink (UL) A / N feedback resources, wherein each of the different UL A / N feedback resources is configured to be used for each of the first entity and the second entity for transmitting each of the retransmission repetitions.

14. The method of claim 12, wherein the first A / N message and the second A / N message are carried by the same uplink (UL) A / N feedback resource, wherein the same UL A / N feedback resource is configured to be used for one or more of the first entity and the second entity for transmitting retransmission repetitions.

15. The method according to claim 10, wherein the retransmission repetition of the data comprises a first retransmission repetition of the data and a second retransmission repetition of the data, the method further comprising: An A / N message is received indicating whether decoding of the retransmission iteration of the data is successful.

16. The method of claim 15, wherein the A / N message is carried in an A / N codebook, and a bit position of the A / N message in the A / N codebook is determined based on one of a first retransmission repetition for the data and a second retransmission repetition for the data in the second entity.

17. The method of claim 16, wherein the control information indicates the one of the second entities based on which resources for transmitting the A / N message are determined.

18. The method of claim 16, wherein the A / N message is carried by different UL A / N feedback resources, wherein each of the different UL A / N feedback resources is configured for each of the first entity and the second entity for transmitting each of the retransmission repetitions.

19. The method of claim 16, wherein the A / N message is carried by a same UL A / N feedback resource, wherein the same UL A / N feedback resource is configured for use by one or more of the first entity and the second entity for transmitting retransmission repetitions.

20. A method for wireless communication, comprising: transmitting, at the first entity, an initial transmission of data to the network; receiving, via a separate control message during each retransmission opportunity, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is transmitted via the second entity according to the control information.

21. A method for wireless communication, comprising: receiving, at a first entity, an initial transmission of data from a user equipment (UE); transmitting, via a separate control message during each retransmission opportunity, control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is received via the second entity.

22. The method of claim 21, wherein an initial transmission of the data is received during a transmission opportunity, and wherein a retransmission repetition of the data is received during a retransmission time window if the data is not successfully decoded during the transmission opportunity.

23. An apparatus 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, at the first entity, an initial transmission of data from the network; receiving, via a separate control message during each retransmission opportunity, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is received via the second entity.

24. A device for wireless communication, comprising: means for monitoring, at the first entity, an initial transmission of data from the network; means for receiving, during each retransmission opportunity, via a separate control message, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; as well as means for receiving, via the second entity, a retransmission repetition of the data.

25. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for monitoring, at a first entity, an initial transmission of data from a network; code for receiving, during each retransmission opportunity, via a separate control message, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and Code for receiving, via the second entity, a retransmission repetition of the data.

26. An apparatus 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); transmitting, via a separate control message during each retransmission opportunity, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and Retransmission iterations of the data are transmitted via the second entity.

27. 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 transmitting, during each retransmission opportunity, via a separate control message, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and means for transmitting, via the second entity, retransmission iterations of the data.

28. 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 transmitting, during each retransmission opportunity, via a separate control message, control information indicating a second entity for receiving retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and Code for transmitting, via the second entity, retransmission repetitions of the data.

29. An apparatus 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; receiving, via a separate control message during each retransmission opportunity, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is transmitted via the second entity according to the control information.

30. A device for wireless communication, comprising: means for transmitting an initial transmission of data to the network at the first entity; means for receiving, during each retransmission opportunity, via a separate control message, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; as well as means for transmitting, via the second entity, a retransmission repetition of the data according to the control information.

31. 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 receiving, during each retransmission opportunity, via a separate control message, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is received prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; as well as Code for transmitting, via the second entity, a retransmission repetition of the data according to the control information.

32. An apparatus 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: receiving, at a first entity, an initial transmission of data from a user equipment (UE); transmitting, via a separate control message during each retransmission opportunity, control information indicating a second entity for transmitting retransmission repetitions of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and A retransmission repetition of the data is received via the second entity.

33. A device for wireless communication, comprising: means for receiving, at a first entity, an initial transmission of data from a user equipment (UE); means for transmitting, during each retransmission opportunity, via a separate control message, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and means for receiving, via the second entity, a retransmission repetition of the data.

34. A computer readable medium having stored thereon computer executable code for wireless communication, comprising: code for receiving, at a first entity, an initial transmission of data from a user equipment (UE); code for transmitting, during each retransmission opportunity, via a separate control message, control information indicating a second entity for transmitting a retransmission repetition of the data, wherein one or more of the second entities is different from the first entity, and wherein each of the separate control messages is transmitted prior to a respective one of the retransmission repetitions and indicates the second entity for receiving the retransmission repetition; and Code for receiving, via the second entity, a retransmission repetition of the data.

Images