Resource allocation and hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback for multi-cell scheduling

Abstract

Certain aspects of the present disclosure provide techniques for resource allocation and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback for multi-cell scheduling. A method that can be performed by a user equipment (UE) includes receiving, from a base station (BS), a configuration for a plurality of carriers, receiving, from the BS, control information indicating whether resources for a data channel are allocated in a concatenated carrier pair of the plurality of carriers, and communicating with the BS on the data channel based on the control information.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Application No. 17 / 451,068, filed October 15, 2021, and U.S. Provisional Application No. 63 / 094,690, filed October 21, 2020, which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety, as fully set forth below, and for all applicable purposes. Background Technology Technical Field

[0003] This disclosure relates to wireless communication, and more specifically, to techniques for multi-cell scheduling.

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3GPP Long Term Evolution (LTE) systems, 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, among others.

[0006] These diverse access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. New radios (e.g., 5G NR) are examples of emerging telecommunications standards. NR is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on both the downlink (DL) and uplink (UL). Therefore, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] As the demand for mobile broadband access continues to increase, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0008] The systems, methods, and apparatus of this disclosure each have several aspects, wherein no single aspect is solely responsible for its desired properties. Upon consideration of this discussion, and specifically upon reading the section entitled "Detailed Description," it will be understood how the features of this disclosure provide advantages including improved resource allocation for multi-cell scheduling and Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) feedback.

[0009] Certain aspects of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a user equipment (UE). This method typically includes: receiving configuration information from a base station (BS) for multiple carriers; receiving control information from the BS indicating whether resources for a data channel are allocated in concatenated carrier pairs among the multiple carriers; and communicating with the BS on the data channel based on the control information.

[0010] Certain aspects of the subject matter described in this disclosure can be implemented in a method for wireless communication performed by a BS. This method typically includes: sending a configuration for multiple carriers to a UE; sending control information to the UE indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers; and communicating with the UE on the data channel based on the control information.

[0011] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication performed by a UE. The apparatus typically includes: a memory; and one or more processors coupled to the memory, the memory and the processors being configured to: receive configuration from a BS for multiple carriers, receive control information from the BS indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicate with the BS on the data channel based on the control information.

[0012] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication by a BS. The apparatus typically includes: a memory; and one or more processors coupled to the memory, the memory and the processors being configured to: transmit configuration information to a UE for multiple carriers, transmit control information to the UE indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicate with the UE on the data channel based on the control information.

[0013] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication performed by a UE. The apparatus typically includes: components for receiving from a BS the configuration of multiple carriers; components for receiving from the BS control information indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers; and components for communicating with the BS on the data channel based on the control information.

[0014] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication performed by a BS. The apparatus typically includes: components for transmitting to a UE configuration for multiple carriers; components for transmitting to the UE control information indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers; and components for communicating with the UE on the data channel based on the control information.

[0015] Certain aspects of the subject matter described in this disclosure may be implemented in a computer-readable medium having instructions stored thereon, which instruct the UE to: receive from the BS configuration for multiple carriers, receive from the BS control information indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicate with the BS on the data channel based on the control information.

[0016] Certain aspects of the subject matter described in this disclosure may be implemented in a computer-readable medium having instructions stored thereon, the instructions causing the BS to: send configuration information to the UE for multiple carriers, send control information to the UE indicating whether resources for the data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicate with the UE on the data channel according to the control information.

[0017] To accomplish the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings detail certain illustrative features of one or more aspects. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0018] To gain a more detailed understanding of the foregoing features of this disclosure, a more specific description of the aspects briefly outlined above can be obtained by referring to the various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings illustrate only certain typical aspects of this disclosure and should therefore not be construed as limiting the scope of this disclosure, as the description may allow for other equivalent aspects.

[0019] Figure 1 It is a block diagram that conceptually illustrates an example wireless communication network according to certain aspects of this disclosure.

[0020] Figure 2This is a block diagram illustrating an example base station (BS) and an example user equipment (UE) according to certain aspects of this disclosure.

[0021] Figure 3 This is an example frame format for New Radio (NR) based on certain aspects of this disclosure.

[0022] Figure 4A and Figure 4B The figure illustrates example scheduling options for multiple cells in a dynamic spectrum sharing (DSS) arrangement according to certain aspects of this disclosure.

[0023] Figure 5 The figure illustrates an example table comparing the Physical Downlink Shared Channel (PDSCH) for each cell with the PDSCH across multiple cells, according to certain aspects of this disclosure.

[0024] Figure 6 This is a flowchart illustrating an example operation of wireless communication performed by a UE according to certain aspects of this disclosure.

[0025] Figure 7 This is a flowchart illustrating an example operation of wireless communication performed by a BS according to certain aspects of this disclosure.

[0026] Figure 8A and Figure 8B The figure illustrates a PDSCH with transport blocks (TBs) per carrier, scheduled on multiple carriers according to certain aspects of this disclosure.

[0027] Figure 9 The figure illustrates an example of hybrid automatic repeat request (HARQ) and block group-based (CBG-based) retransmission when the PDSCH scheduled on multiple carriers has a TB for each carrier, according to certain aspects of this disclosure.

[0028] Figure 10A and Figure 10B The figure illustrates a PDSCH with a single TB scheduled on multiple carriers according to certain aspects of this disclosure.

[0029] Figure 11 The figure illustrates an example HARQ and CBG-based retransmission when a PDSCH scheduled on multiple carriers has a single TB, according to certain aspects of this disclosure.

[0030] Figure 12 The diagram illustrates a communication device that, according to aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0031] Figure 13The diagram illustrates a communication device that, according to aspects of this disclosure, may include various components configured to perform operations using the techniques disclosed herein.

[0032] For ease of understanding, the same reference numerals have been used where possible to designate common elements in the figures. Unless otherwise stated, elements disclosed in one aspect are expected to be usefully used in other aspects. Detailed Implementation

[0033] This disclosure provides apparatus, methods, processing systems, and computer-readable media for multi-cell scheduling. For example, aspects provide enhanced techniques for resource allocation and Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) feedback when scheduling multiple cells.

[0034] The downlink control information (DCI) format in the physical downlink control channel (PDCCH) can be designed to schedule multiple cells. Using a single DCI to schedule multiple cells can reduce downlink (DL) overhead. In some aspects, the DCI format in a cell's PDCCH can schedule two physical downlink shared channels (PDSCHs) (or two physical uplink shared channels (PUSCHs)) on two scheduled cells. In other aspects, the DCI format in a cell's PDCCH can schedule one PDSCH (or one PUSCH) on multiple (e.g., two) scheduled cells.

[0035] In cases where the DCI format in a cell's PDCCH is used to schedule a single PDSCH (or PUSCH) across multiple scheduled cells, different resource allocation mechanisms and HARQ retransmissions can be considered for different aspects. For example, in some aspects, a PDSCH (or PUSCH) scheduled across multiple cells can have a TB for each cell and implement HARQ retransmission for each cell. In other aspects, a PDSCH (or PUSCH) scheduled across multiple cells can have a single TB for each cell pair and implement HARQ retransmission for each cell pair.

[0036] The following description provides examples of multi-cell scheduling in a communication system, but is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and individual steps may be added, omitted, or combined. Similarly, features described with respect to certain examples may be combined into certain other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover apparatuses or methods practiced using additional structures, functionalities, or structures and functionalities, either as supplements to or other than the various aspects set forth herein. It should be understood that any aspect of this disclosure may be embodied by one or more elements of the claims. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0037] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs.

[0038] The techniques described herein can be used in a variety of wireless networks and radio technologies. Although terms commonly associated with 3G, 4G, and / or newer radio technologies (e.g., 5G NR) may be used to describe aspects herein, the aspects of this disclosure can be applied to communication systems based on other generations.

[0039] NR access (e.g., 5G NR) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidths (e.g., 80 MHz or higher), millimeter wave (mmW) for high carrier frequencies (e.g., 25 GHz or higher), massive machine-type communication (mMTC) for non-backward-compatible MTC technologies, and / or mission-critical ultra-reliable low-latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Furthermore, these services can coexist in the same time-domain resources (e.g., time slots or subframes) or frequency-domain resources (e.g., component carriers (CC)). NR supports beamforming, and beam direction can be dynamically configured.

[0040] Precoded multiple-input multiple-output (MIMO) transmission can also be supported. MIMO configuration in the downlink (DL) can support up to 8 transmit antennas, with up to 8 streams in multi-layer DL transmission and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE is supported. Aggregation of multiple cells across up to 8 serving cells is supported.

[0041] Example wireless communication network

[0042] Figure 1 The figure illustrates an example wireless communication network 100 in which aspects of this disclosure may be implemented. For example, as... Figure 1 As shown, the wireless communication network 100 may include components configured to perform... Figure 6 The user equipment (UE) 120a of operation 600 is configured to perform Figure 7 The operation of the 700 base station (BS) 110a is to support multi-cell scheduling.

[0043] like Figure 1 As shown, BS 110a includes a multi-cell scheduling manager 112. According to certain aspects of this disclosure, the multi-cell scheduling manager 112 can be configured to send control information to UE 120a indicating whether resources for a data channel are allocated in a cascaded carrier pair across multiple carriers, and to communicate with UE 120a on the data channel according to the control information. Similarly, as Figure 1 As shown, UE 120a includes a multi-cell scheduling manager 122. According to certain aspects of this disclosure, the multi-cell scheduling manager 122 can be configured to receive control information from BS 110a indicating whether resources for a data channel are allocated in a cascaded carrier pair among multiple carriers, and to communicate with BS 110a on the data channel based on the control information.

[0044] The wireless communication network 100 can be a new radio (NR) system (e.g., a 5G NR network). For example... Figure 1 As shown, the wireless communication network 100 can communicate with the core network 132. The core network 132 can communicate with one or more BS 110s and / or UEs 120 in the wireless communication network 100 via one or more interfaces.

[0045] In addition, such as Figure 1 As shown, the wireless communication network 100 may include several BSs 110a-110z (each also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. BS 110 may provide communication coverage for a specific geographic area, sometimes referred to as a "cell," which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless communication network 100 using any suitable transport network and through various types of backhaul interfaces (e.g., direct physical connection, wireless connection, virtual network, etc.). Figure 1 In the example shown, BS 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BS 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. BS 110 can support one or more cells. Network controller 130 can be coupled to a set of BS 110 and provide coordination and control for these BS 110s. Network controller 130 can communicate with BS 110s via backhaul. BS 110s can also communicate with each other via wireless or wired backhaul (e.g., directly or indirectly).

[0046] In the wireless communication network 100, BS 110 communicates with UEs 120a-120y (each of which is also individually referred to as UE120 or collectively as UE 120 herein). UEs 120 (e.g., 120x, 120y, etc.) may be distributed throughout the wireless communication network 100, and each UE 120 may be fixed or mobile.

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

[0048] Figure 2 The diagram illustrates BS 110a and UE 120a (e.g., in...). Figure 1 A block diagram of example components in a wireless communication network 100, which can be used to implement aspects of this disclosure.

[0049] At BS 110a, the transmitting processor 220 can receive data from the data source 212 and control information from the controller / processor 240. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. The Media Access Control (MAC)-Control Element (MAC-CE) is a MAC layer communication structure that can be used for exchanging control commands between wireless nodes. The MAC-CE can be carried in shared channels (such as the Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), or Physical Sidelink Shared Channel (PSSCH)).

[0050] Transmit processor 220 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. Transmit processor 220 can also generate reference symbols, such as those for primary synchronization signals (PSS), secondary synchronization signals (SSS), and channel state information reference signals (CSI-RS). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide output symbol streams to modulators (MODs) in transceivers 232a-232t. Each modulator in transceivers 232a-232t can process its corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM), etc.) to obtain an output sample stream. Each modulator can further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink (DL) signal. The DL signal from the modulator in transceivers 232a-232t can be transmitted via antennas 234a-234t respectively.

[0051] At UE 120a, antennas 252a-252r can receive DL signals from BS 110a and can provide the received signals to demodulators (DEMODs) in transceivers 254a-254r respectively. Each demodulator in transceivers 254a-254r can modulate (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 can process the detected symbols (e.g., demodulate, deinterleave, and decode), provide decoded data for UE 120a to data sink 260, and provide decoded control information to controller / processor 280.

[0052] On the uplink (UL), at UE 120a, the transmit processor 264 can receive and process data from data source 262 (e.g., for PUSCH) and control information from controller / processor 280 (e.g., for Physical Uplink Control Channel (PUCCH)). The transmit processor 264 can also generate reference symbols for reference signals (RS) (e.g., for sounding reference signals (SRS)). Symbols from the transmit processor 264 can be pre-encoded by the TX MIMO processor 266 where applicable, further processed by modulators (MODs) in transceivers 254a-254r (e.g., for single-carrier frequency division multiplexing (SC-FDM), etc.), and transmitted to BS 110a. At BS 110a, the UL signal from UE 120a can be received by antenna 234, processed by modulator 432 in transceivers 232a-232t, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120a. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240.

[0053] Memory 242 and 282 can store data and program code for BS 110a and UE 120a, respectively. Scheduler 244 can schedule the UE for data transmission on DL and / or UL.

[0054] Antenna 252, processors 266, 258, 264 and / or controller / processor 280 of UE 120a, and / or antenna 234, processors 220, 230, 238 and / or controller / processor 240 of BS 110a can be used to perform the various techniques and methods described herein. For example, such as Figure 2 As shown, according to certain aspects described herein, the controller / processor 240 of BS 110a has a multi-cell scheduling manager 112, which can be configured to send control information to UE 120a indicating whether resources for the data channel are allocated in a cascaded carrier pair across multiple carriers, and to communicate with UE 120a on the data channel according to the control information. Figure 2 As shown, according to certain aspects described herein, the controller / processor 280 of UE 120a has a multi-cell scheduling manager 122, which can be configured to receive control information from BS 110a indicating whether resources for a data channel are allocated in a cascaded carrier pair across multiple carriers, and to communicate with BS 110a on the data channel based on the control information. Although shown at the controller / processor, other components of UE 120a and BS 110a can be used to perform the operations described herein.

[0055] NR can utilize OFDM with a cyclic prefix (CP) on both UL and DL. NR can support half-duplex operation using Time Division Duplex (TDD). OFDM and SC-FDM divide the system bandwidth into multiple orthogonal subcarriers, which are often referred to as frequency modulation, frequency bands, etc. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers can depend on the system bandwidth. The minimum resource allocation, called a resource block (RB), can be 12 consecutive subcarriers. The system bandwidth can also be divided into subbands. For example, a subband can cover multiple RBs. NR can support a basic subcarrier spacing (SCS) of 15 kHz, and other SCSs can be defined relative to the basic SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.).

[0056] Figure 3This is a diagram illustrating an example of a frame format 300 for certain wireless communication networks (e.g., NR) according to certain aspects of this disclosure. The transmission timeline for each of DL and UL can be divided into units of radio frames. Each radio frame can have a predetermined duration (e.g., 10 milliseconds (ms)) and can be divided into 10 subframes, each 1 ms long, with indices from 0 to 9. Depending on the SCS, each subframe can include a variable number of time slots (e.g., 1, 2, 4, 8, 16, ...). Depending on the SCS, each time slot can include a variable number of symbol periods (e.g., 7 or 14 symbols). The symbol periods in each time slot can be assigned an index. A micro-time slot, which may be referred to as a sub-time slot structure, refers to a transmission time interval (TTI) having a duration less than that of a time slot (e.g., 2, 3, or 4 symbols). Each symbol in a time slot can indicate the link direction for data transmission (e.g., DL, UL, or flexible), and the link direction for each subframe can be dynamically switched. The link direction can be based on the time slot format. Each time slot can include DL / UL data and DL / UL control information.

[0057] Dynamic Spectrum Sharing (DSS) allows existing LTE carriers to operate simultaneously for 5G NR and LTE. DSS can be based on a smart scheduler algorithm that improves performance as the mix of 4G and 5G devices in the network changes over time. DSS enables the deployment of a first carrier (such as an NR carrier) and a second carrier (such as a DSS carrier) in a DSS arrangement for DL ​​(or UL) communications. In a DSS arrangement, resource sharing between NR and DSS carriers is based on Time Division Multiplexing (TDM) and Frequency Division Multiplexing (FDM) modes.

[0058] Downlink Control Information (DCI), carried by the Physical Downlink Control Channel (PDCCH), carries control information for scheduling user data, such as the PDSCH on the DL and the Physical Uplink Shared Channel (PUSCH) on the UL. The DCI indicates the time and frequency location of the data scheduled for transmission, the modulation and decoding scheme (MCS) used, the number of antenna ports or layers, and other aspects such as Hybrid Automatic Repeat Request (HARQ). A UE that receives the DCI can decode it before it can decode the DL data or transmit the UL data.

[0059] In a DSS deployment, the DCI format can be designed to schedule multiple cells. In some aspects, a DCI format in a cell's PDCCH can schedule two PDSCHs on two scheduled cells. In other aspects, a DCI format in a cell's PDCCH can schedule one PDSCH on two scheduled cells.

[0060] Figure 4A and 4B The diagram illustrates scheduling options for multiple cells in a DSS arrangement 400 according to certain aspects of this disclosure. For example... Figure 4A As shown, the DSS arrangement 400 illustrates the deployment of a first cell operating in a first carrier 402 and a second cell operating in a second carrier 404 on the same frequency band. In some cases, the first carrier 402 and the second carrier 404 are NR-only carriers. In other cases, the first carrier 402 and the second carrier 404 are DSS carriers. In still other cases, one of the first carrier 402 or the second carrier 404 is an NR-only carrier and the other is a DSS carrier.

[0061] DSS deployment 400 uses the following scheduling options, wherein a DCI format in PDCCH 406 is used to schedule PDSCH 408 for cells operating in the first carrier 402 and PDSCH 410 for cells operating in the second carrier 404.

[0062] Similar to Figure 4A ,like Figure 4B As shown, DSS arrangement 420 illustrates the deployment of a cell operating in the first carrier 422 and a cell operating in the second carrier 424 on the same frequency band. In some cases, the first carrier 422 and the second carrier 424 are NR-only carriers. In other cases, the first carrier 422 and the second carrier 424 are both DSS carriers. In still other cases, one of the first carrier 422 or the second carrier 424 is an NR-only carrier and the other is a DSS carrier.

[0063] DSS arrangement 420 uses the following scheduling options, wherein a DCI format in PDCCH 426 is used to schedule both the scheduled cell operating in the first carrier 402 and the scheduled cell operating in the second carrier 404 in a PDSCH 428.

[0064] Multi-cell PDSCH scheduling can be considered for multiple UE configurations. In some aspects, multi-cell PDSCH scheduling can be designed for UEs configured with inter-band carrier aggregation (CA), where the primary cell (Pcell) and secondary cells (Scell) are aggregated for the UE. The Pcell used for the UE operates on a DSS carrier (e.g., the same carrier is also used to serve LTE users). In some examples, the SCS used for the Pcell and Scell ​​can be different. In some examples, the SCS used for the Pcell and Scell ​​can be the same. In some examples, in-band CA can involve multiple serving cells with the same SCS (where all cells operate on non-DSS carriers). In some examples, in-band CA can involve a Pcell and multiple Scells (where at least one Scell ​​operates on a non-DSS carrier).

[0065] While DSS supports dynamic allocation of resources between 5G and LTE subscribers in existing low-band LTE service areas, DSS deployment can negatively impact spectral efficiency due to the additional management overhead required by DSS. Accordingly, there is a need for techniques and apparatus for designing PDCCH formats that reduce downlink overhead and improve the spectral efficiency of DSS carriers. Although some examples regarding DSS carriers are described for ease of understanding, the aspects described herein can be applied to reduce overhead for any suitable carrier.

[0066] Example resource allocation and Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) feedback for multi-cell scheduling

[0067] This disclosure provides apparatus, methods, processing systems, and computer-readable media for multi-cell scheduling. For example, some aspects provide enhanced techniques for resource allocation and hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) feedback (e.g., in HARQ messages) when scheduling multiple cells (or carriers). A cell typically refers to the coverage area of ​​a carrier.

[0068] As described above, the downlink control information (DCI) format can be designed to schedule multiple carriers. In some aspects, a DCI format in the physical downlink control channel (PDCCH) of a carrier can schedule two physical downlink shared channels (PDSCH) (or physical uplink shared channels (PUSCH)) on two scheduled carriers. In other aspects, a DCI format in the PDCCH of a carrier can schedule one PDSCH (or PUSCH) on two scheduled carriers. The user equipment (UE) can receive a DCI from the base station (BS) indicating whether resources for a data channel (e.g., PDSCH or PUSCH) are allocated among multiple carriers, and use this DCI to communicate with the BS on that data channel.

[0069] Figure 5 Example Table 500 illustrates a comparison between scheduling PDSCH (or PUSCH) for each cell and scheduling PDSCH (or PUSCH) across multiple cells, according to certain aspects of this disclosure. Figure 5 As shown in Table 500, scheduling PDSCH / PUSCH for each cell using a DCI format (for any number of cells) may include fields for each of the scheduled cells or fields applicable to cell bundles (also referred to herein as cell pairs or cell sets). While some examples are described herein for cell pairs for ease of understanding, aspects of this disclosure apply to any number of cells equal to or greater than two cells. Furthermore, many options can be considered when scheduling PDSCH / PUSCH over multiple cells. For example, PDSCH / PUSCH may carry two transport blocks (TBs) over two cells, where each TB is for each cell, or PDSCH / PUSCH may carry only one TB for the cell pair. As shown in Table 500, options for other fields in PDSCH / PUSCH may include modulation and decoding schemes (MCS) and hybrid automatic repeat request (HARQ) / retransmission code block group (CBG) transmission information (TI) or CBG flushing information (FI).

[0070] Figure 6 This is a flowchart illustrating an example operation 600 for wireless communication performed by a UE according to certain aspects of this disclosure. Operation 600 can be performed, for example, by a UE 120a in a wireless communication network 100.

[0071] Operation 600 can be implemented in one or more processors (e.g., Figure 2 The software components that execute and run on the controller / processor 280. Furthermore, in operation 600, the UE's transmission and reception of signals can be, for example, via one or more antennas (e.g., Figure 2 This is achieved via antenna 252. In some aspects, the UE's transmission and / or reception of signals may be achieved via a bus interface of one or more processors (e.g., controller / processor 280) that acquires and / or outputs signals.

[0072] Operation 600 can begin at block 605 by the UE receiving configuration information for multiple carriers from the BS. At block 610, the UE receives control information from the BS indicating whether resources for the data channel (e.g., PUSCH or PDSCH) are allocated in a cascaded carrier pair across the multiple carriers. At block 615, the UE communicates with the BS on the data channel based on the control information.

[0073] While certain operations of this disclosure are described with respect to carriers, the aspects described herein can be applied to any frequency band, such as cascaded bandwidth portion (BWP) pairs. For example, at block 610, the UE can receive control information from the BS indicating whether resources for data channels (e.g., PUSCH or PDSCH) are allocated in cascaded BWP pairs among the multiple BWPs of the carrier.

[0074] Figure 7 This is a flowchart illustrating an example operation 700 for wireless communication performed by a BS according to certain aspects of this disclosure. Operation 700 can be performed, for example, by a BS 110a in a wireless communication network 100. Operation 700 can be an operation performed by the BS that is complementary to operation 600 performed by the UE.

[0075] Operation 700 can be implemented in one or more processors (e.g., Figure 2 The software components that execute and run on the controller / processor 240. Furthermore, in operation 700, the BS can transmit and receive signals via, for example, through one or more antennas (e.g., Figure 2 This is achieved via antenna 234. In some aspects, the BS can transmit and / or receive signals via a bus interface of one or more processors (e.g., controller / processor 240) that acquires and / or outputs signals.

[0076] Operation 700 can be initiated at block 705 by the BS sending a configuration for multiple carriers (or any frequency band, such as BWP) to the UE. At block 710, the BS sends control information to the UE indicating whether resources for the data channel (e.g., PDSCH or PUSCH) are allocated in a cascaded carrier pair across the multiple carriers. At block 715, the BS communicates with the UE on the data channel based on the control information.

[0077] The diagrams illustrating multi-cell PDSCH scheduling can be referenced separately. Figure 8A, Figure 8B , Figure 9 , Figure 10A , Figure 10B and Figure 11 Use figures 800, 810, 900, 1000, 1010, and 1100 to understand. Figure 6 and Figure 7 Operations 600 and 700. Regarding... Figure 8A , Figure 8B , Figure 9 , 10A , Figure 10B and Figure 11 The aspects described also apply to multi-cell PUSCH scheduling.

[0078] In some respects, scheduling PDSCH (or PUSCH) on multiple carriers can generate TB for each carrier and HARQ retransmission for each carrier.

[0079] Figure 8A and Figure 8B The diagram illustrates a PDSCH scheduled on multiple carriers, each with a TB, according to certain aspects of this disclosure. For example... Figure 8A As shown, in some cases, frequency domain resource allocation can result in scheduling PDSCH (e.g., PDSCH 804) on multiple carriers. More specifically, a DCI format in PDCCH 802 can schedule PDSCH 804 across a first carrier (carrier 1) and a second carrier (carrier 2). Although deployed on the same frequency band, frequency gaps may exist between the two carriers. The UE can identify cascaded carrier pairs based on the configuration for multiple carriers received from the BS (e.g., higher-layer configuration).

[0080] In some respects, when the PDSCH spans two carriers, the UE can determine that the first TB (e.g., TB 806) is generated on carrier 1 based on PDSCH 804 spanning carrier 1, and determine that the second TB (e.g., TB 808) is generated on carrier 2 based on PDSCH 804 spanning carrier 2.

[0081] The UE can determine the size of each of the first TB and the second TB. This determination can be based on several factors, including the amount of resources allocated for the data channel in carrier 1 and carrier 2 respectively, and the MCS for each cell. In some examples, the MCS for each carrier can be common to multiple carriers. In some examples, the MCS for each carrier can be different.

[0082] In some respects, while the UE can identify concatenated carrier pairs based on configuration from the BS, the UE may not know which carrier contains the highest resource block (RB) and which carrier contains the lowest RB for RB indexing. Accordingly, the UE can determine the order of the carriers in the concatenated pair (also referred to herein as "carrier order") to identify the high RB and low RB. In some respects, the UE can determine the carrier order associated with the concatenated carrier pair based on an index associated with the serving cell, an identifier of the bandwidth portion (BWP), or configuration received from the BS.

[0083] In some respects, the UE (and BS) can perform interleaving operations for the data channel based on the interleaving configuration specific to each carrier in the cascaded carrier pair (e.g., physical resource block to virtual resource block (PRB to VRB) mapping). Interleaving can be performed on each carrier in which it is enabled.

[0084] Figure 8B The diagram illustrates frequency domain resource allocation resulting from scheduling a PDSCH only for one carrier, according to certain aspects of this disclosure. More specifically, a DCI format in PDCCH 812 can schedule PDSCH 814 only for the second carrier (carrier 2) (and not for the first carrier (carrier 1)). Accordingly, the BS can generate only one TB on carrier 2, for example, a second TB (TB 816). For example, the BS can generate a first TB of size zero on carrier 1.

[0085] In addition to determining the size of each of the first TB and the second TB, the UE can communicate HARQ ACK or negative acknowledgment (NACK) indications for each of the first TB and the second TB. Frequency domain resource allocation can result in PDSCH being scheduled on two carriers or only one carrier in a concatenated carrier pair. Based on the resource allocation for PDSCH, the UE can use a semi-static HARQ codebook to generate HARQ NACK indications for PDSCH on carriers considered unscheduled. When the UE fails to detect the DCI format, the UE may not know whether the DCI format is scheduling PDSCH on both carriers or only on one carrier. Accordingly, in a semi-static HARQ codebook design, the UE can generate ACK / NACK bits for the first TB and the second TB, and continue generating ACK / NACK bits for both carrier 1 and carrier 2 when it is possible for PDSCH to continue across two carriers. In other words, even if PDSCH is received on one of the carriers, the UE can generate a separate HARQ indication for each carrier in the concatenated carrier pair. For example, the UE may receive the TB on only one carrier in the cascaded carrier pair, and the communication may be a separate HARQ indication for each carrier in the cascaded carrier pair.

[0086] When using a dynamic HARQ-ACK codebook, the downlink (DL) assignment index (e.g., the counter downlink assignment (C-DAI)) can be incremented by one or two bits depending on the number of carriers on which the PDSCH is mapped. In other words, the UE can communicate with the BS a HARQ message with a DAI that increments by one or two after each data channel transmission based on whether the resources used for data channel transmission are allocated to one or both carriers in a cascaded carrier pair.

[0087] In some respects, HARQ retransmissions can be per-cell. More specifically, retransmissions of a TB for a carrier can occur on the same carrier used for the initial transmission (where the HARQ information is for the carrier it was sent). Cross-carrier HARQ retransmissions may not be supported in some implementations. For example, the DCI can indicate retransmissions of either of two TBs on their corresponding carriers or retransmissions of two TBs on two different carriers via a frequency domain resource allocation field. Accordingly, if a PDSCH retransmission occurs within a single carrier, the retransmission only occurs on that carrier.

[0088] Furthermore, code block group (CBG) based retransmissions can be configurable for each carrier in a concatenated carrier pair. For example, a single DCI format can schedule retransmissions of one or two TBs of CBGs on a PDSCH mapped on two carriers. TB CBG retransmissions can occur on the same carrier used for the initial transmission. For example, the UE can receive additional control information that allocates resources in a first carrier for retransmissions of one or more first CBGs of a first TB transmitted on the first carrier and resources in a second carrier for retransmissions of one or more second CBGs of a second TB transmitted on the second carrier.

[0089] Figure 9 Figure 900 illustrates an example of HARQ and CBG-based retransmission when a PDSCH scheduled on multiple carriers has a TB for each carrier, according to certain aspects of this disclosure. Figure 9 As shown in Figure 8, frequency domain resource allocation can result in PDSCH 904 being scheduled across multiple cells. In other words, a DCI format in PDCCH 902 can schedule PDSCH 904 across a first carrier (carrier 1) and a second carrier (carrier 2). Although deployed on the same frequency band, frequency gaps may exist between the two carriers. The UE can identify concatenated carrier pairs based on the configuration (e.g., higher-layer configuration) for multiple carriers received from the BS. If the first transport block (e.g., TB 906) is generated on carrier 1 and the second transport block (e.g., TB 908) is generated on carrier 2, and both are generated incorrectly, the UE can use a codebook-based approach to send NACK feedback.

[0090] In some respects, retransmitting the entire first TB (TB 906) or the entire second TB (TB 908) may not be important; therefore, it is possible to retransmit only portions of the first TB and the second TB (i.e., retransmitting CGB). For example, as in Figure 9 As shown, only a portion of TB 906 of CBG 916 can be retransmitted, and only a portion of TB 908 of CBG 918 can be retransmitted. According to certain aspects of this disclosure, the retransmission of CBG 916 and CBG 918 can be performed on the same carrier as the carrier used for the initial transmission.

[0091] In some respects, scheduling PDSCH on multiple carriers can generate a single TB for each carrier pair and a HARQ retransmission for each carrier pair.

[0092] Figure 10A and Figure 10B The diagram illustrates a PDSCH with a single TB scheduled across multiple carriers according to certain aspects of this disclosure. For example... Figure 10A As shown, and similar to Figure 8A Frequency domain resource allocation can result in scheduling PDSCH (e.g., PDSCH 1004) on multiple carriers. More specifically, a DCI format in PDCCH 1002 can schedule PDSCH 1004 across a first carrier (carrier 1) and a second carrier (carrier 2). As described herein, although deployed on the same frequency band, frequency gaps may exist between the two carriers. The UE can identify concatenated carrier pairs based on configurations received from the BS for multiple cells (e.g., higher-layer configurations).

[0093] However, with Figure 8A In some respects, the PDSCH can carry only one TB. Accordingly, in the case where PDSCH 1004 spans two carriers, the UE can determine that a single TB scheduled by the DCI format (e.g., TB 1006) is generated across multiple carriers (e.g., TB 1006 spans carrier 1 and carrier 2).

[0094] The UE can determine the TB size for the scheduled PDSCH. This determination can be based on several factors, including the total amount of resources allocated for the data channel and the MCS for the carrier.

[0095] In some respects, the MCS used for each carrier in a cascaded carrier pair can be common. In other words, a single MCS can be indicated in the DCI used for two carriers. When a single MCS exists for a PDSCH across carriers, the MCS indicated in the DCI can be used to derive the TB size for the scheduled PDSCH.

[0096] In some respects, the MCS used for each carrier in a cascaded carrier pair can be different. That is, the DCI can indicate a different MCS for each carrier in the carrier pair. If the MCS used for the PDSCH is different across cells, the TB size can be derived for each carrier of the PDSCH using the indicated MCS.

[0097] In some respects, the UE (and BS) can perform interleaving operations for the data channel based on the interleaving configuration specific to each carrier in the cascaded carrier pair (e.g., PRB to VRB mapping). Interleaving can be performed on each carrier in which it is enabled.

[0098] Figure 10B The diagram illustrates the frequency domain resource allocation that results in scheduling a PDSCH for only one carrier. More specifically, a DCI format in PDCCH 1012 can schedule PDSCH 1014 for only the second carrier (carrier 2) (but not for the first carrier (carrier 1)). Accordingly, the BS can generate a single TB (e.g., TB 1016) for each carrier pair on carrier 2. In addition to determining the size of the TB, the UE can also provide HARQ ACK / NACK feedback for communicating multi-cell PDSCHs to the BS.

[0099] In some aspects, when using a semi-static HARQ codebook, all carriers within a concatenated carrier pair can be treated as if they were a single carrier. Accordingly, the UE can communicate HARQ indications for the TBs in the concatenated carrier pair. Assuming that PDSCHs are not simultaneously scheduled on the carriers, the UE can generate a set of bits for each carrier, corresponding to the appropriate PDSCH timing. In some aspects, when using a dynamic HARQ-ACK codebook, the C-DAI can be counted based on the number of PDCCHs scheduling the PDSCHs.

[0100] In some respects, HARQ retransmissions can be per carrier pair. More specifically, retransmissions can occur on one carrier or on both carriers in a concatenated carrier pair. Whether cross-carrier HARQ retransmissions can be supported depends on frequency domain resource allocation. Furthermore, CBG-based retransmissions can be configurable per carrier pair. For example, a single DCI format can schedule CBG retransmissions of a TB on a single PDSCH mapped across two carriers.

[0101] Figure 11 The diagram illustrates HARQ and CBG-based retransmission when a PDSCH scheduled on multiple carriers has a single TB, according to certain aspects of this disclosure. Figure 11 As shown, similar to Figure 10AIn some cases, frequency domain resource allocation can result in scheduling PDSCHs (e.g., PDSCH 1104) on multiple carriers. More specifically, a DCI format in PDCCH 1102 can schedule PDSCH 1104 across a first carrier (carrier 1) and a second carrier (carrier 2). The UE can identify concatenated carrier pairs based on a configuration (e.g., a higher-layer configuration) received from the BS for multiple carriers. If there is an error in the generation of a single TB (such as TB 1106), the UE can send a NACK feedback. In some aspects, retransmitting the entire TB 1106 may not be important, so only a portion of the TB can be retransmitted. For example, instead of retransmitting the entire TB 1106, CBG 1116, as a part of TB 1106, can be retransmitted. According to certain aspects of this disclosure, a single DCI format can schedule the retransmission of CBG 1116 on a single PDSCH mapped on two carriers.

[0102] Example wireless communication device

[0103] Figure 12 The illustration shows a communication device 1200 that may include various components (e.g., corresponding to means-plus-function components) operable for, configured for, or adapted to perform operations using the techniques disclosed herein, such as Figure 6 The operation is shown. In some examples, the communication device 1200 may be a user equipment (UE), such as regarding... Figure 1 and Figure 2 The UE 120a is described.

[0104] Communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or receiver). Transceiver 1208 is configured to transmit and receive signals for communication device 1200, such as the various signals described herein, via antenna 1210. Processing system 1202 may be configured to perform processing functions for communication device 1200, including processing signals received and / or to be transmitted by communication device 1200.

[0105] Processing system 1202 includes processor 1204, which is coupled to computer-readable medium / memory 1212 via bus 1206. In some aspects, computer-readable medium / memory 1212 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1204, cause processor 1204 to perform... Figure 6 The operations shown, or other operations used to perform the various techniques for multi-cell scheduling discussed in this article.

[0106] In some aspects, the computer-readable medium / memory 1212 stores code 1214 (example component) for receiving (e.g., for receiving from the BS configuration for multiple carriers, and for receiving from the BS control information indicating whether resources for the data channel are allocated in a cascaded carrier pair among the multiple carriers), and code 1216 (example component) for communicating (e.g., for communicating with the BS on the data channel based on the control information).

[0107] In some aspects, processor 1204 has circuitry configured to implement code stored in computer-readable medium / memory 1212. Processor 1204 includes circuitry 1224 (example component) for receiving (e.g., receiving from the BS configuration for multiple carriers, and receiving from the BS control information indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers), and circuitry 1226 (example component) for communicating (e.g., communicating with the BS on the data channel based on the control information).

[0108] In some cases, Figure 6 The operations shown, as well as other operations described herein, can be implemented by one or more components plus functional components. For example, in some cases, such operations can be implemented by components for receiving and components for communicating.

[0109] Components used for communication may include components for receiving and components for sending. Components for receiving or acquiring may include... Figure 2 The UE 120a shown includes a receiver (such as a receiver processor 258) or an antenna 252. Components for transmitting or for output may include... Figure 2 The transmitter (such as the transmit processor 264) or antenna 252 of UE 120a shown in the figure.

[0110] Transceiver 1208 may provide components for receiving or transmitting information. Information may be transmitted to other components of communication device 1200. Antenna 1210 may correspond to a single antenna or an array of antennas. Transceiver 1208 may provide components for transmitting signals generated by other components of communication device 1200.

[0111] Notice, Figure 12 This is just one example, and many other examples and configurations of the communication device 1200 are possible.

[0112] Figure 13 The figure illustrates a communication device 1300 that may include various components (e.g., corresponding to component plus functional components) that are operable for, configured for, or adapted to perform operations using the techniques disclosed herein, such as Figure 7The operation is shown. In some examples, the communication device 1300 may be a BS, such as regarding Figure 1 and Figure 2 The description is BS 110a.

[0113] Communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or receiver). Transceiver 1308 is configured to transmit and receive signals for communication device 1300, such as the various signals described herein, via antenna 1310. Processing system 1302 may be configured to perform processing functions for communication device 1300, including processing signals received and / or to be transmitted by communication device 1300.

[0114] Processing system 1202 includes processor 1304, which is coupled to computer-readable medium / memory 1312 via bus 1306. In some aspects, computer-readable medium / memory 1312 is configured to store instructions (e.g., computer-executable code) that, when executed by processor 1304, cause processor 1304 to perform... Figure 7 The operations shown, or other operations used to perform the various techniques for multi-cell scheduling discussed in this article.

[0115] In some aspects, the computer-readable medium / memory 1312 stores code 1314 (example component) for transmission (e.g., for transmitting to the UE configuration for multiple carriers, and for transmitting to the UE control information indicating whether resources for the data channel are allocated in a cascaded carrier pair among the multiple carriers), and code 1316 for communication (e.g., for communicating with the UE on the data channel based on the control information).

[0116] In some aspects, processor 1304 has circuitry configured to implement code stored in computer-readable medium / memory 1312. Processor 1304 includes circuitry 1324 (example component) for transmitting (e.g., for transmitting to the UE configuration for multiple carriers, and for transmitting to the UE control information indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers), and circuitry 1326 (example component) for communicating (e.g., for communicating with the UE on the data channel based on the control information).

[0117] In some cases, Figure 6 The operations shown, as well as other operations described herein, can be implemented by one or more components plus functional components. For example, in some cases, such operations can be implemented by a component for sending and a component for communicating.

[0118] Components used for communication may include components for receiving and components for sending. Components for receiving or acquiring may include... Figure 2 The receiver (such as receiver processor 238) or antenna 234 of BS 110a shown herein. Components for transmitting or for output may include... Figure 2 The transmitter (such as the transmitter processor 220) or antenna 234 of BS 110a shown in the figure.

[0119] Transceiver 1308 may provide components for receiving or transmitting information. Information may be transmitted to other components of communication device 1300. Antenna 1310 may correspond to a single antenna or an array of antennas. Transceiver 1308 may provide components for transmitting signals generated by other components of communication device 1300.

[0120] Notice, Figure 13 This is just one example, and many other examples and configurations of the communication device 1300 are possible.

[0121] According to the examples disclosed herein, multi-cell scheduler 122 and multi-cell scheduler 112 can support wireless communication.

[0122] Multi-cell scheduler 122 and multi-cell scheduler 112 may be examples of components used to perform the various aspects described herein. Multi-cell scheduler 122 and multi-cell scheduler 112, or subcomponents thereof, may be implemented in hardware (e.g., in uplink (UL) resource management circuitry). The circuitry may include processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.

[0123] In another implementation, the multi-cell scheduler 122 and the multi-cell scheduler 112, or their sub-components, may be implemented in processor-executable code (e.g., as configuration management software or firmware) or any combination thereof. If implemented in processor-executable code, the functionality of the multi-cell scheduler 122 and the multi-cell scheduler 112, or their sub-components, may be executed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device.

[0124] In some examples, multi-cell scheduler 122 and multi-cell scheduler 112 can be configured to use or otherwise cooperate with transceiver 1208 or 1308 to perform various operations (e.g., receive, confirm, send / transmit).

[0125] Multi-cell scheduler 122 and multi-cell scheduler 112, or their sub-components, may be physically located in various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, multi-cell scheduler 122 and multi-cell scheduler 112, or their sub-components, may be separate and distinct components. In some examples, according to various aspects of this disclosure, multi-cell scheduler 122 and multi-cell scheduler 112, or their sub-components, may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0126] Example

[0127] Implementation examples are described in the following numbered aspects:

[0128] Aspect 1: A method for wireless communication performed by a user equipment (UE), comprising: receiving configuration for multiple carriers from a base station (BS), receiving control information from the BS indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicating with the BS on the data channel based on the control information.

[0129] Aspect 2: The method of aspect 1, wherein the data channel includes a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH).

[0130] Aspect 3: The method of aspect 1 or 2, wherein the resources for configuring the data channel are allocated to the cascaded carrier pairs therein.

[0131] Aspect 4: The method of any of Aspects 1-3 further includes: determining the carrier order associated with the concatenated carrier pair based on an index associated with the serving cell, an identifier of the bandwidth portion (BWP), or a configuration received from the BS, wherein one or more transport blocks (TBs) of the data channel are communicated based on the carrier order.

[0132] Aspect 5: The method of aspect 4, wherein the resources for the data channel include one or more TBs of RBs from the lowest resource block (RB) of one carrier in the cascaded carrier pair to the highest RB of another carrier in the cascaded carrier pair, according to the carrier order.

[0133] Aspect 6: The method of any one of Aspects 1-6, wherein the data channel includes a first transport block (TB) in a first carrier of a concatenated carrier pair; and a second TB in a second carrier of a concatenated carrier pair.

[0134] Aspect 7: The method of aspect 6 further includes: determining the size of each of the first TB and the second TB based on the amount of resources allocated for the data channel in the first carrier and the second carrier, respectively, wherein communication of the data channel is based on the size of each of the first TB and the second TB.

[0135] Aspect 8: The method of aspect 7, wherein the retransmission of the first TB is on the first carrier, and wherein the retransmission of the second TB is on the second carrier.

[0136] Aspect 9: The method of any one of Aspects 6-8 further includes: receiving additional control information that allocates resources in the first carrier for retransmission of one or more first code block groups (CBGs) of the first TB and resources in the second carrier for retransmission of one or more second CBGs of the second TB.

[0137] Aspect 10: The method of any one of Aspects 1-9, wherein communicating on the data channel includes receiving a TB on one of the carriers in the cascaded carrier pair, and the method further includes communicating a separate Hybrid Automatic Repeat Request (HARQ) indication for each carrier in the cascaded carrier pair.

[0138] Aspect 11: The method of any one of Aspects 1-10 further includes: communicating with the BS a HARQ message having a downlink assignment index (DAI), which increments by one or two after each data channel transmission based on whether the resources used for data channel transmission are allocated in one or two carriers of a cascaded carrier pair.

[0139] Aspect 12: The method of any one of Aspects 1-11, wherein the data channel comprises a transport block (TB) in a concatenated carrier pair.

[0140] Aspect 13: The method of aspect 12 further includes: receiving additional control information that allocates resources for retransmission of one or more code block groups (CBGs) of a cascaded carrier pair.

[0141] Aspect 14: The method of aspect 12 or 13 further includes: determining the size of TB based on the amount of resources allocated for the data channel in the cascaded carrier pair, wherein communication of the data channel is based on the size of TB.

[0142] Aspect 15: The method of any one of Aspects 12-14 further includes: communicating a Hybrid Automatic Repeat Request (HARQ) indication for a TB in a cascaded carrier pair.

[0143] Aspect 16: The method of any one of Aspects 12-15 further includes: receiving additional control information that allocates resources for retransmission of TB on one or both carriers of the cascaded carrier pair.

[0144] Aspect 17: The method of any one of Aspects 1-16 further includes: determining a modulation and decoding scheme (MCS) for each carrier in a cascaded carrier pair, wherein the data channel is communicated according to the determined MCS.

[0145] Aspect 18: The method of any one of Aspects 1-17 further includes: determining a common MCS for cascaded carrier pairs, wherein the data channel is communicated according to the determined MCS.

[0146] Aspect 19: The method of any one of Aspects 1-18 further includes: performing an interleaving operation for the data channel based on the interleaving configuration specific to each carrier in the cascaded carrier pair.

[0147] Aspect 20: A method for wireless communication by a base station (BS), comprising: sending configuration for multiple carriers to a user equipment (UE), sending control information to the UE indicating whether resources for a data channel are allocated in a cascaded carrier pair among the multiple carriers, and communicating with the UE on the data channel according to the control information.

[0148] Aspect 21: The method of aspect 20, wherein the data channel includes a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH).

[0149] Aspect 22: The method of aspect 20 or 21, wherein the resources for configuring the data channel are allocated to the cascaded carrier pairs therein.

[0150] Aspect 23: The method of any one of Aspects 20-22 further includes: determining the carrier order associated with the concatenated carrier pair based on an index associated with the serving cell, an identifier of the bandwidth portion (BWP), or a configuration received from the BS, wherein one or more transport blocks (TBs) of the data channel are communicated based on the carrier order.

[0151] Aspect 24: The method of aspect 23, wherein the resources for the data channel include one or more TBs of RBs from the lowest resource block (RB) of one carrier in the cascaded carrier pair to the highest RB of another carrier in the cascaded carrier pair, according to the carrier order.

[0152] Aspect 25: The method of any one of Aspects 20-24, wherein the data channel includes a first transport block (TB) in a first carrier of a cascaded carrier pair and a second TB in a second carrier of a cascaded carrier pair.

[0153] Aspect 26: The method of aspect 25, wherein the size of each of the first TB and the second TB is based on the amount of resources allocated for the data channel in the first carrier and the second carrier, respectively, wherein communication of the data channel is based on the size of each of the first TB and the second TB.

[0154] Aspect 27: The method of aspect 26, wherein the retransmission of the first TB is on the first carrier, and wherein the retransmission of the second TB is on the second carrier.

[0155] Aspect 28: The method of any one of Aspects 25-27 further includes: transmitting additional control information that allocates resources in the first carrier for retransmission of one or more first code block groups (CBGs) of the first TB and resources in the second carrier for retransmission of one or more second CBGs of the second TB.

[0156] Aspect 29: The method of any one of Aspects 20-28, wherein communicating on the data channel includes receiving a TB on one of the carriers in the cascaded carrier pair, and the method further includes communicating a separate Hybrid Automatic Repeat Request (HARQ) indication for each carrier in the cascaded carrier pair.

[0157] Aspect 30: The method of any one of Aspects 20-29 further includes: communicating with the UE a HARQ message having a downlink assignment index (DAI), the DAI being incremented by one or two after each data channel transmission based on whether the resources used for data channel transmission are allocated in one or two carriers of a cascaded carrier pair.

[0158] Aspect 31: The method of any one of Aspects 20-30, wherein the data channel comprises a transport block (TB) in a concatenated carrier pair.

[0159] Aspect 32: The method of aspect 31 further includes: transmitting additional control information that allocates resources for retransmission of one or more code block groups (CBGs) of a cascaded carrier pair.

[0160] Aspect 33: The method of aspects 31 or 32, wherein the size of TB is based on the amount of resources allocated for the data channel in the cascaded carrier pair, wherein communication of the data channel is based on the size of TB.

[0161] Aspect 34: The method of any one of aspects 31-33 further includes: communicating a Hybrid Automatic Repeat Request (HARQ) indication for a TB in a cascaded carrier pair.

[0162] Aspect 35: The method of any one of aspects 31-34 further includes: transmitting additional control information that allocates resources for retransmission of TB on one or both carriers of the cascaded carrier pair.

[0163] Aspect 36: The method of any one of Aspects 20-35 further includes: determining a modulation and decoding scheme (MCS) for each carrier in a cascaded carrier pair, wherein the data channel is communicated according to the determined MCS.

[0164] Aspect 37: The method of any one of Aspects 20-36 further includes: determining a common MCS for cascaded carrier pairs, wherein the data channel is communicated according to the determined MCS.

[0165] Aspect 38: The method of any one of Aspects 20-37 further includes: performing an interleaving operation for the data channel based on the interleaving configuration specific to each carrier in the cascaded carrier pair.

[0166] Additional considerations

[0167] The techniques described in this article can be used in various wireless communication technologies, such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE Advanced (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 generally used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can 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, and Flash-OFDMA. UTRA and E-UTRA are parts of the 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 called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). NR is an emerging wireless communication technology under development.

[0168] In 3GPP, depending on the context in which the terminology is used, the term "cell" can refer to the coverage area of ​​a Node B (NB) and / or the NB subsystem serving this coverage area. In NR systems, the term "cell" and BS, Next Generation Node B (gNB or gNodeB), Access Point (AP), Distributed Unit (DU), Carrier, or Transmitter / Receiver Point (TRP) can be used interchangeably. A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow limited access for UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in a home, etc.). A BS used for a macrocell can be referred to as a macro BS. A BS used for a picocell can be referred to as a pico BS. A BS used for a femtocell can be called a femtocell BS or a home BS.

[0169] A UE can also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, 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 devices such as smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets, etc.), entertainment devices (e.g., music devices, video devices, satellite radios, etc.), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, GPS equipment, or any other suitable device configured to communicate via wireless or wired media. Some UEs can 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., that can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity, for example, to or to a network (e.g., a wide area network such as the Internet or cellular networks), via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

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

[0171] The methods disclosed herein include one or more steps or actions for implementing the method. The method steps and / or actions may be interchanged 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 a particular step and / or action may be modified without departing from the scope of the claims.

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

[0173] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, computation, processing, derivation, investigation, searching (e.g., looking in a table, database, or other data structure), probing, etc. Similarly, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Likewise, "determine" can include parsing, selecting, choosing, building, etc.

[0174] The preceding 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are intended to be given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, references to elements in the singular are not intended to mean “one and only one”, but “one or more”. Unless specifically stated otherwise, the term “some” refers to one or more. All structural and functional equivalents of elements throughout the various aspects described herein that are known or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, the contents of this disclosure are not intended to be exclusive to the public, whether or not such disclosure is expressly stated in the claims. No claim element is to be interpreted under 35 U.SC §112(f) unless the element is expressly stated using the phrase “for a component of”, or, in the case of a method claim, the element is stated using the phrase “for a step of”.

[0175] The various operations described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, in the cases where operations are illustrated in the accompanying drawings, those operations may have corresponding matching components with similar numbering, plus functional components.

[0176] The various illustrative logic blocks, modules, and circuits described in connection with this disclosure may be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), 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. The general-purpose processor may be a microprocessor, but alternatively, it may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

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

[0178] If implemented in software, functionality can be stored or transmitted as one or more instructions or code on a computer-readable medium. 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 otherwise. Computer-readable media includes both computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general-purpose processing, including executing software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to it. Alternatively, the storage medium may be integrated into the processor. For example, a machine-readable medium may include a transmit line, a carrier wave modulated by data, and / or a separate computer-readable storage medium containing instructions, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium, or any portion thereof, may be integrated into the processor, such as in cases where a cache and / or general-purpose register file may be present. Examples of machine-readable storage media may include, for example, 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, disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0179] Software modules may include a single instruction or multiple instructions, and may be distributed across several different code segments, within different programs, and across multiple storage media. Computer-readable media may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. Software modules may include sending modules and receiving modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, a software module may be loaded from a hard drive into RAM when a triggering event occurs. During the execution of a software module, the processor may load some of the instructions into a cache to improve access speed. One or more cache lines may then be loaded into a general-purpose register file for processor execution. It will be understood, when referring to the functionality of the following software module, that such functionality is implemented by the processor when executing the instructions from this software module.

[0180] Similarly, any connection is appropriately referred to as computer-readable medium. For example, if coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave are used to send software from a website, server, or other remote source, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. The disks and optical discs used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and... Disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. Therefore, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the foregoing should also be included within the scope of computer-readable media.

[0181] Therefore, certain aspects may include computer program products for performing the operations described herein. For example, such computer program products may include computer-readable media on which instructions are stored (and / or encoded) that can be executed by one or more processors to perform the operations described herein, such as those for performing the operations described herein. Figure 6 and / or Figure 7 The instructions for the operation shown are as follows.

[0182] Furthermore, it should be understood that modules and / or other suitable components for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device may be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein may be provided via storage components (e.g., RAM, ROM, physical storage media such as compact discs (CDs) or floppy disks), such that the user terminal and / or base station can obtain the various methods when the storage components are coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device may be utilized.

[0183] It will be understood that the claims are not limited to the precise configuration and components shown in the figures above. Various modifications, alterations, and variations may be made to 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 by a user equipment (UE), comprising: receiving, from a network node, a configuration for a plurality of carriers; receiving, from the network node, control information comprising a single downlink control information (DCI) format indicating whether resources for a data channel are allocated in a concatenated pair of carriers of the plurality of carriers, wherein the data channel comprises a first transport block (TB) in a first carrier of the concatenated pair of carriers and a second TB in a second carrier of the concatenated pair of carriers; determining a size of each of the first TB and the second TB based on an amount of resources in the first carrier and the second carrier, respectively, allocated for the data channel; and communicating with the network node on the data channel based on the control information and based on the size of each of the first TB and the second TB.

2. The method of claim 1, wherein the configuration identifies the concatenated pair of carriers in which the resources for the data channel are allocated. determining a carrier order associated with the concatenated pair of carriers based on an index associated with a serving cell, an identifier of a bandwidth part (BWP), or the configuration received from the network node, wherein two or more TBs of the data channel comprising the first TB and the second TB are communicated based on the carrier order.

3. The method of claim 1, further comprising:

4. The method of claim 3, wherein the resources for the data channel comprise resource blocks (RBs) of the two or more TBs starting from a lowest RB of one carrier of the concatenated pair of carriers to a highest RB of another carrier of the concatenated pair of carriers according to the carrier order.

5. The method of claim 1, wherein a retransmission of the first TB is on the first carrier, and wherein a retransmission of the second TB is on the second carrier.

6. The method of claim 1, further comprising receiving other control information allocating: resources in the first carrier for retransmission of one or more first code block groups (CBGs) of the first TB; and resources in the second carrier for retransmission of one or more second CBGs of the second TB.

7. The method of claim 1, wherein communicating on the data channel comprises receiving at least one of the first TB or the second TB on one carrier of the concatenated pair of carriers, the method further comprising communicating a separate hybrid automatic repeat request (HARQ) indication for each carrier of the concatenated pair of carriers. communicating with the network node a HARQ message having a downlink assignment index (DAI) that is incremented by one or two after each data channel transmission based on whether resources for the data channel transmission are allocated in one or two carriers of the concatenated pair of carriers.

8. The method of claim 1, further comprising: receiving other control information allocating resources for retransmission of one or more code block groups (CBGs) of at least one of the first TB or the second TB of the concatenated pair of carriers.

9. The method of claim 1, further comprising: ​ 10. The method of claim 1, further comprising: determining a size of the TB based on an amount of resources allocated for the data channel in the pair of concatenated carriers, wherein the communication of the data channel is based on the size of at least one of the first TB or the second TB.

11. The method of claim 1, further comprising: communicating a hybrid automatic repeat request (HARQ) indication for at least one of the first TB or the second TB of the pair of concatenated carriers.

12. The method of claim 1, further comprising: receiving other control information allocating resources for retransmission of at least one of the first TB or the second TB on one or both of the pair of concatenated carriers.

13. The method of claim 1, further comprising: determining a modulation and coding scheme (MCS) for each carrier in the pair of concatenated carriers, wherein the data channel is communicated according to the determined MCS.

14. The method of claim 1, further comprising: determining a common MCS for the pair of concatenated carriers, wherein the data channel is communicated according to the determined MCS.

15. The method of claim 1, further comprising: performing interleaving operations for the data channel based on an interleaving configuration specific to each carrier in the pair of concatenated carriers.

16. The method of claim 1, wherein the size of the first TB is further determined based on a modulation and coding scheme (MCS) of the first carrier, and wherein the size of the second TB is further determined based on a MCS of the second carrier.

17. A method for wireless communications by a network node, comprising: transmitting, to a user equipment (UE), a configuration for a plurality of carriers; transmitting, to the UE, control information including a single downlink control information (DCI) format indicating whether resources for a data channel are allocated in a pair of concatenated carriers of the plurality of carriers, wherein the data channel includes a first transport block (TB) in a first carrier of the pair of concatenated carriers and a second TB in a second carrier of the pair of concatenated carriers, and wherein a size of each of the first TB and the second TB is based on an amount of resources allocated for the data channel in the first carrier and the second carrier, respectively; and communicating with the UE on the data channel in accordance with the control information.

18. The method of claim 17, wherein the configuration identifies the pair of concatenated carriers in which the resources for the data channel are allocated.

19. The method of claim 17, further comprising: determining a carrier order associated with the pair of concatenated carriers based on an index associated with a serving cell, an identifier of a bandwidth part (BWP), or the configuration received from the network node, wherein two or more transport blocks (TBs) of the data channel including the first TB and the second TB are communicated based on the carrier order.

20. The method of claim 19, wherein the resources for the data channel include resource blocks (RBs) of the two or more TBs starting from a lowest RB of one carrier of the pair of concatenated carriers to a highest RB of another carrier of the pair of concatenated carriers according to the carrier order.

21. The method of claim 17, further comprising transmitting other control information allocating: resources in the first carrier for retransmission of one or more first code block groups (CBGs) of the first TB; and resources in the second carrier for retransmission of one or more second CBGs of the second TB.

22. The method of claim 17, wherein communicating on the data channel comprises receiving at least one of the first TB or the second TB on one carrier of the pair of cascaded carriers, the method further comprising communicating a separate hybrid automatic repeat request (HARQ) indication for each carrier of the pair of cascaded carriers.

23. The method of claim 17, further comprising: communicating with the UE a HARQ message having a downlink assignment index (DAI) that is incremented by one or two after each data channel transmission based on whether resources for the data channel transmission are allocated in one or both of the pair of cascaded carriers.

24. The method of claim 17, wherein the size of the first TB is further based on a modulation and coding scheme (MCS) of the first carrier, and wherein the size of the second TB is further based on a MCS of the second carrier.

25. An apparatus for wireless communication by a user equipment (UE), comprising: at least one memory including instructions; and at least one processor configured to execute the instructions to cause the apparatus to perform the method of any of claims 1-16.

26. An apparatus for wireless communication by a network node, comprising: at least one memory including instructions; and at least one processor configured to execute the instructions to cause the apparatus to perform the method of any of claims 17-24.

27. A computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1-16.

28. A computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the method of any of claims 17-24.

29. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1-16.

30. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method of any of claims 17-24.

Images