Patent Description:
A wireless multiple-access communications system may include a number of base stations (BSs), each simultaneously supporting communications for multiple communication devices, which may be otherwise known as user equipment (UE).

To meet the growing demands for expanded mobile broadband connectivity, wireless communication technologies are advancing from the long-term evolution (LTE) technology to a next generation new radio (NR) technology, which may be referred to as <NUM>th Generation (<NUM>). For example, NR is designed to provide a lower latency, a higher bandwidth or a higher throughput, and a higher reliability than LTE. NR is designed to operate over a wide array of spectrum bands, for example, from low-frequency bands below about <NUM> gigahertz (GHz) and mid-frequency bands from about <NUM> to about <NUM>, to high-frequency bands such as millimeter wave (mmWave) bands. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrums to dynamically support high-bandwidth services. Spectrum sharing can extend the benefit of NR technologies to operating entities that may not have access to a licensed spectrum.

Dynamic spectrum sharing (DSS) allows the LTE technology and NR technology to operate in the same frequency band and share the same frequency spectrum. DSS also allows operators to dynamically allocate the frequency spectrum based on need. This means that a frequency band of an NR cell that operates using DSS may be allocated to an LTE cell and vice versa. Accordingly, there is a need to provide cross-carrier scheduling techniques that facilitate the efficient use of resources, while providing the flexibility to schedule data communications over one or multiple cells.

US <CIT>, relates to supporting communication in a wireless communication system. <CIT>, relates to power control in a multi-carrier wireless communication network. <CIT>, relates to a system and method for resource allocation.

Aspects of the present disclosure provide mechanisms for scheduling data using cross-carrier scheduling and/or multi-carrier (or joint-carrier) scheduling. In cross-carrier scheduling, a scheduling cell uses the downlink control information (DCI) of the scheduling cell to schedule data on a channel (e.g., PDSCH or a PUSCH) of a scheduled cell. The scheduling cell can be a primary cell (P Cell), a primary secondary (P(S) Cell), and/or a secondary cell (S Cell). Likewise, the scheduled cell can be a P Cell, a P(S) Cell, and/or an S Cell. In a multi-carrier scheduling scheme, the scheduling cell can use a single DCI to schedule data for data transmissions on multiple cells, where the scheduling cell may be a P Cell, a P(S) Cell, or an S Cell, and each of the scheduled cells may be a P Cell, a P(S) Cell, or an S Cell.

In some instances, a different DCI format can be utilized to schedule single-carrier data transmissions as compared to multi-carrier data transmissions. That is, a first DCI format can be used for single-carrier scheduling and a second, different DCI format can be used for multi-carrier scheduling. In this regard, a UE may determine whether data is scheduled for transmission over a single carrier or multiple carriers based on the format of the received DCI.

In some instances, a common DCI format can be utilized to schedule both single-carrier data transmissions and multi-carrier data transmissions. That is, the same DCI format that is used for single-carrier scheduling can be used for multi-carrier scheduling. In this regard, one or more aspects of the DCI (e.g., the search space in which the DCI is received, the value(s) of one or more fields of the DCI, etc.) can indicate whether the scheduled data is to be communicated over a single carrier or multiple carriers.

In some instances, the DCI includes separate hybrid automatic repeat request (HARQ) process IDs for each carrier of a multi-carrier data transmission. Having separate HARQ process IDs can allow retransmissions to be scheduled on each carrier separately. This can facilitate scheduling, via a single DCI, retransmission of data associated with a first HARQ process on a first carrier and retransmission of data associated with a second HARQ process on a second, different carrier, which can improve efficiency and reduce latency.

Aspects of the present disclosure provide several benefits. As an initial matter, the cross-carrier and multi-carrier scheduling techniques of the present disclosure provide improved spectral efficiency. For example, using a single DCI to schedule communications over multiple carriers is more efficient and reduces the signaling requirements compared to existing techniques that require multiple DCIs for multi-carrier scheduling. Also, using a common DCI format for both single-carrier and cross-carrier scheduling can provide a simplified and consistent processing of the DCI at the UE, avoiding the need to have separate dedicated DCI formats (and associated processing techniques/algorithms at the UE) for single-carrier scheduling and multi-carrier scheduling. Further, aspects of the present disclosure allow cross-carrier scheduling from an S Cell to a P(S) Cell (and/or a P Cell), which can free up PDCCH resources of the P(S) Cell (and/or the P(S) Cell). Further still, in a dynamic spectrum sharing (DSS) environment, a non-DSS cell can use a single DCI to schedule data on a DSS cell and/or the non-DSS cell. While aspects of the present disclosure have particular benefits in the context of DSS, it is understood that the concepts can be applied in a similar manner to cross-carrier scheduling for carrier aggregation.

In an aspect of the disclosure, a method of wireless communication performed by a user equipment includes receiving a downlink control information (DCI) message having a DCI format, the DCI message scheduling a downlink data communication over a single component carrier or multiple component carriers; determining, based on the received DCI message, whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers; and receiving, based on the determining, the downlink data communication over the single component carrier or the multiple component carriers.

In an additional aspect of the disclosure, a method of wireless communication performed by a base station includes transmitting a first downlink control information (DCI) message having a DCI format, the first DCI message scheduling a first downlink data communication over a single component carrier; transmitting the first downlink data communication over the single component carrier; transmitting a second DCI message having the DCI format, the second DCI message scheduling a second downlink data communication over multiple component carriers; and transmitting the second downlink data communication over the multiple component carriers.

In an additional aspect of the disclosure, a user equipment includes a transceiver configured to receive a downlink control information (DCI) message having a DCI format, the DCI message scheduling a downlink data communication over a single component carrier or multiple component carriers; and a processor in communication with the transceiver, the processor configured to determine, based on the received DCI message, whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers, wherein the transceiver is further configured to receive, based on the determination of the processor, the downlink data communication over the single component carrier or the multiple component carriers.

In an additional aspect of the disclosure, a base station includes a transceiver configured to: transmit a first downlink control information (DCI) message having a DCI format, the first DCI message scheduling a first downlink data communication over a single component carrier; transmit the first downlink data communication over the single component carrier; transmit a second DCI message having the DCI format, the second DCI message scheduling a second downlink data communication over multiple component carriers; and transmit the second downlink data communication over the multiple component carriers.

In an additional aspect of the disclosure, a user equipment includes means for receiving a downlink control information (DCI) message having a DCI format, the DCI message scheduling a downlink data communication over a single component carrier or multiple component carriers; means for determining, based on the received DCI message, whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers; and means for receiving, based on the determining, the downlink data communication over the single component carrier or the multiple component carriers.

In an additional aspect of the disclosure, a base station includes means for transmitting a first downlink control information (DCI) message having a DCI format, the first DCI message scheduling a first downlink data communication over a single component carrier; means for transmitting the first downlink data communication over the single component carrier; means for transmitting a second DCI message having the DCI format, the second DCI message scheduling a second downlink data communication over multiple component carriers; and means for transmitting the second downlink data communication over the multiple component carriers.

In an additional aspect of the disclosure, a non-transitory computer-readable medium has program code recorded thereon for wireless communication by a user equipment, the program code including code for causing the user equipment to receive a downlink control information (DCI) message having a DCI format, the DCI message scheduling a downlink data communication over a single component carrier or multiple component carriers; code for causing the user equipment to determine, based on the received DCI message, whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers; and code for causing the user equipment to receive, based on the determining, the downlink data communication over the single component carrier or the multiple component carriers.

In an additional aspect of the disclosure, a non-transitory computer-readable medium has program code recorded thereon for wireless communication by a base station, the program code including code for causing the base station to transmit a first downlink control information (DCI) message having a DCI format, the first DCI message scheduling a first downlink data communication over a single component carrier; code for causing the base station to transmit the first downlink data communication over the single component carrier; code for causing the base station to transmit a second DCI message having the DCI format, the second DCI message scheduling a second downlink data communication over multiple component carriers; and code for causing the base station to transmit the second downlink data communication over the multiple component carriers.

This disclosure relates generally to wireless communications systems, also referred to as wireless communications networks. In various embodiments, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, <NUM>th Generation (<NUM>) or new radio (NR) networks, as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably.

An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) <NUM>, IEEE <NUM>, IEEE <NUM>, flash-OFDM and the like. UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS). 3GPP long term evolution (LTE) is a 3GPP project which was aimed at improving the UMTS mobile phone standard.

In particular, <NUM> networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. In order to achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for <NUM> NR networks. The <NUM> NR will be capable of scaling to provide coverage (<NUM>) to a massive Internet of things (IoTs) with a ULtra-high density (e.g., ~<NUM> nodes/km<NUM>), ultra-low complexity (e.g., ~<NUM> of bits/sec), ultra-low energy (e.g., ~<NUM>+ years of battery life), and deep coverage with the capability to reach challenging locations; (<NUM>) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ~<NUM>% reliability), ultra-low latency (e.g., ~ <NUM>), and users with wide ranges of mobility or lack thereof; and (<NUM>) with enhanced mobile broadband including extreme high capacity (e.g., ~ <NUM> Tbps/km<NUM>), extreme data rates (e.g., multi-Gbps rate, <NUM>+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.

The <NUM> NR may be implemented to use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI); having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in <NUM> NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than <NUM> FDD/TDD implementations, subcarrier spacing may occur with <NUM>, for example over <NUM>, <NUM>, <NUM>, and the like bandwidth (BW). For other various outdoor and small cell coverage deployments of TDD greater than <NUM>, subcarrier spacing may occur with <NUM> over <NUM>/<NUM> BW. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the <NUM> band, the subcarrier spacing may occur with <NUM> over a <NUM> BW. Finally, for various deployments transmitting with mmWave components at a TDD of <NUM>, subcarrier spacing may occur with <NUM> over a <NUM> BW.

These and other aspects of the present disclosure can provide several benefits. As an initial matter, the cross-carrier and multi-carrier scheduling techniques of the present disclosure provide improved spectral efficiency. For example, using a single DCI to schedule communications over multiple carriers is more efficient and reduces the signaling requirements compared to existing techniques that require multiple DCIs for multi-carrier scheduling. Also, using a common DCI format for both single-carrier and cross-carrier scheduling can provide a simplified and consistent processing of the DCI at the UE, avoiding the need to have separate dedicated DCI formats (and associated processing techniques/algorithms at the UE) for single-carrier scheduling and multi-carrier scheduling. Further, aspects of the present disclosure allow cross-carrier scheduling from an S Cell to a P(S) Cell (and/or a P Cell), which can free up PDCCH resources of the P(S) Cell (and/or the P(S) Cell). Further still, in a dynamic spectrum sharing (DSS) environment, a non-DSS cell can use a single DCI to schedule data on a DSS cell and/or the non-DSS cell. While aspects of the present disclosure have particular benefits in the context of DSS, it is understood that the concepts can be applied in a similar manner to cross-carrier scheduling for carrier aggregation. Additional features and benefits of the present disclosure are set forth in the following description.

<FIG> illustrates a wireless communication network <NUM> according to some embodiments of the present disclosure. The network <NUM> may be a <NUM> network. The network <NUM> includes a number of base stations (BSs) <NUM> (individually labeled as 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities. A BS <NUM> may be a station that communicates with UEs <NUM> and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each BS <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to this particular geographic coverage area of a BS <NUM> and/or a BS subsystem serving the coverage area, depending on the context in which the term is used.

The UEs <NUM> are dispersed throughout the wireless network <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like. A UE <NUM> may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like. In one aspect, a UE <NUM> may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, the UEs <NUM> that do not include UICCs may also be referred to as IoT devices or internet of everything (IoE) devices. The UEs 115a-115d are examples of mobile smart phone-type devices accessing network <NUM>. A UE <NUM> may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs 115e-<NUM> are examples of various machines configured for communication that access the network <NUM>. A UE <NUM> may be able to communicate with any type of the BSs, whether macro BS, small cell, or the like. In <FIG>, a lightning bolt (e.g., communication links) indicates wireless transmissions between a UE <NUM> and a serving BS <NUM>, which is a BS designated to serve the UE <NUM> on the downlink and/or uplink, or desired transmission between BSs, and backhaul transmissions between BSs.

The BSs <NUM> may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs <NUM> (e.g., which may be an example of a gNB or an access node controller (ANC)) may interface with the core network through backhaul links (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communication with the UEs <NUM>. In various examples, the BSs <NUM> may communicate, either directly or indirectly (e.g., through core network), with each other over backhaul links (e.g., X1, X2, etc.), which may be wired or wireless communication links.

The network <NUM> may also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such as the UE 115e, which may be a drone. Redundant communication links with the UE 115e may include links from the macro BSs 105d and 105e, as well as links from the small cell BS 105f. Other machine type devices, such as the UE 115f (e.g., a thermometer), the UE <NUM> (e.g., smart meter), and UE <NUM> (e.g., wearable device) may communicate through the network <NUM> either directly with BSs, such as the small cell BS 105f, and the macro BS 105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as the UE 115f communicating temperature measurement information to the smart meter, the UE <NUM>, which is then reported to the network through the small cell BS 105f. The network <NUM> may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V).

In some implementations, the network <NUM> utilizes OFDM-based waveforms for communications. An OFDM-based system may partition the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, or the like. Each subcarrier may be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system BW. The system BW may also be partitioned into subbands. In other instances, the subcarrier spacing and/or the duration of TTIs may be scalable.

In an embodiment, the BSs <NUM> can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RB)) for downlink (DL) and uplink (UL) transmissions in the network <NUM>. DL refers to the transmission direction from a BS <NUM> to a UE <NUM>, whereas UL refers to the transmission direction from a UE <NUM> to a BS <NUM>. The communication can be in the form of radio frames. A radio frame may be divided into a plurality of subframes or slots, for example, about <NUM>. Each slot may be further divided into mini-slots. In a FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In a TDD mode, UL and DL transmissions occur at different time periods using the same frequency band. For example, a subset of the subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions and another subset of the subframes (e.g., UL subframes) in the radio frame may be used for UL transmissions.

The DL subframes and the UL subframes can be further divided into several regions. For example, each DL or UL subframe may have pre-defined regions for transmissions of reference signals, control information, and data. Reference signals are predetermined signals that facilitate the communications between the BSs <NUM> and the UEs <NUM>. For example, a reference signal can have a particular pilot pattern or structure, where pilot tones may span across an operational BW or frequency band, each positioned at a pre-defined time and a pre-defined frequency. For example, a BS <NUM> may transmit cell specific reference signals (CRSs) and/or channel state information - reference signals (CSI-RSs) to enable a UE <NUM> to estimate a DL channel. Similarly, a UE <NUM> may transmit sounding reference signals (SRSs) to enable a BS <NUM> to estimate a UL channel. Control information may include resource assignments and protocol controls. Data may include protocol data and/or operational data. In some embodiments, the BSs <NUM> and the UEs <NUM> may communicate using self-contained subframes. A self-contained subframe may include a portion for DL communication and a portion for UL communication. A self-contained subframe can be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL communication than for UL communication. A UL-centric subframe may include a longer duration for UL communication than for UL communication.

In an embodiment, the network <NUM> may be an NR network deployed over a licensed spectrum. The BSs <NUM> can transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network <NUM> to facilitate synchronization. The BSs <NUM> can broadcast system information associated with the network <NUM> (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, the BSs <NUM> may broadcast the PSS, the SSS, and/or the MIB in the form of synchronization signal block (SSBs) over a physical broadcast channel (PBCH) and may broadcast the RMSI and/or the OSI over a physical downlink shared channel (PDSCH).

In an embodiment, a UE <NUM> attempting to access the network <NUM> may perform an initial cell search by detecting a PSS from a BS <NUM>. The PSS may enable synchronization of period timing and may indicate a physical layer identity value. The UE <NUM> may then receive a SSS. The SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The PSS and the SSS may be located in a central portion of a carrier or any suitable frequencies within the carrier.

After receiving the PSS and SSS, the UE <NUM> may receive a MIB. The MIB may include system information for initial network access and scheduling information for RMSI and/or OSI. After decoding the MIB, the UE <NUM> may receive RMSI and/or OSI. The RMSI and/or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

After obtaining the MIB, the RMSI and/or the OSI, the UE <NUM> can perform a random access procedure to establish a connection with the BS <NUM>. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE <NUM> may transmit a random access preamble and the BS <NUM> may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, a UL grant, a temporary cell-radio network temporary identifier (C-RNTI), and/or a backoff indicator. Upon receiving the random access response, the UE <NUM> may transmit a connection request to the BS <NUM> and the BS <NUM> may respond with a connection response. The connection response may indicate a contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response can be referred to as a message <NUM> (MSG <NUM>), a message <NUM> (MSG <NUM>), a message <NUM> (MSG <NUM>), and a message <NUM> (MSG <NUM>), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE <NUM> may transmit a random access preamble and a connection request in a single transmission and the BS <NUM> may respond by transmitting a random access response and a connection response in a single transmission. The combined random access preamble and connection request in the two-step random access procedure may be referred to as a message A (MSG A). The combined random access response and connection response in the two-step random access procedure may be referred to as a message B (MSG B).

After establishing a connection, the UE <NUM> may initiate an initial network attachment procedure with the network <NUM>. When the UE <NUM> has no active data communication with the BS <NUM> after the network attachment, the UE <NUM> may return to an idle state (e.g., RRC idle mode). Alternatively, the UE <NUM> and the BS <NUM> can enter an operational state or active state, where operational data may be exchanged (e.g., RRC connected mode). For example, the BS <NUM> may schedule the UE <NUM> for UL and/or DL communications. The BS <NUM> may transmit UL and/or DL scheduling grants to the UE <NUM> via a PDCCH. The BS <NUM> may transmit a DL communication signal to the UE <NUM> via a PDSCH according to a DL scheduling grant. The UE <NUM> may transmit a UL communication signal to the BS <NUM> via a PUSCH and/or PUCCH according to a UL scheduling grant. In some embodiments, the BS <NUM> and the UE <NUM> may employ hybrid automatic request (HARQ) techniques for communications to improve reliability. Additionally, the UE <NUM> and/or the BS <NUM> can utilize DRX (e.g., during RRC idle mode), including connected mode DRX (C-DRX) (e.g., during RRC connected mode), and/or DTX operating modes.

In an embodiment, the network <NUM> may operate over a system BW or a component carrier (CC) BW. The network <NUM> may partition the system BW into multiple BWPs (e.g., portions). A BS <NUM> may dynamically assign a UE <NUM> to operate over a certain BWP (e.g., a certain portion of the system BW). The assigned BWP may be referred to as the active BWP. The UE <NUM> may monitor the active BWP for signaling information from the BS <NUM>. The BS <NUM> may schedule the UE <NUM> for UL or DL communications in the active BWP. In some instances, a BS <NUM> may assign a pair of BWPs within the CC to a UE <NUM> for UL and DL communications. For example, the BWP pair may include one BWP for UL communications and one BWP for DL communications. In some instances, the BS <NUM> may dynamically switch the UE <NUM> from one BWP to another BWP, for example, from a wideband BWP to a narrowband BWP for power savings or from a narrowband BWP to a wideband BWP for communication.

The BS <NUM> may additionally configure the UE <NUM> with one or more CORESETs in a BWP. A CORESET may include a set of frequency resources spanning a number of symbols in time. The BS <NUM> may configure the UE <NUM> with one or more search spaces for PDCCH monitoring based on the CORESETS. The UE <NUM> may perform blind decoding in the search spaces to search for DL control information from the BS. The BS <NUM> may configure the UE <NUM> with various different CORSETs and/or search spaces for different types of PDCCH monitoring (e.g., DL/UL schedules and/or wake-up information). In an example, the BS <NUM> may configure the UE <NUM> with the BWPs, the CORESETS, and/or the PDCCH search spaces via RRC configurations.

In an embodiment, the BS <NUM> may establish a RRC connection with the UE <NUM> in a primary cell (PCell) (e.g., over a primary frequency carrier) and may subsequently configure the UE <NUM> to communicate over a secondary cell (SCell) (e.g., over a secondary frequency carrier). In an embodiment, the BS <NUM> may trigger the UE <NUM> to report channel information based on channel-state-information-reference signal (CSI-RS) transmitted by the BS <NUM>. In some instances, the triggering may be aperiodic, which may be referred to as aperiodic-CSI-RS (A-CSI-RS) triggering.

The network <NUM> may operate over a shared frequency band or an unlicensed frequency band, for example, at about <NUM> gigahertz (GHz), sub-<NUM> or higher frequencies in the mmWave band. The network <NUM> may partition a frequency band into multiple channels, for example, each occupying about <NUM> megahertz (MHz). The BSs <NUM> and the UEs <NUM> may be operated by multiple network operating entities sharing resources in the shared communication medium and may acquire channel occupancy time (COT) in the share medium for communications. A COT may be noncontinuous in time and may refer to an amount of time a wireless node can send frames when it has won contention for the wireless medium. Each COT may include a plurality of transmission slots. A COT may also be referred to as a transmission opportunity (TXOP).

<FIG> illustrates a cross-carrier scheduling technique <NUM> according to some aspects of the present disclosure. In this regard, aspects of the present disclosure provide mechanisms for scheduling data using cross-carrier scheduling. In cross-carrier scheduling, a scheduling cell uses the downlink control information (DCI) <NUM> of the scheduling cell to schedule downlink data <NUM> on a channel (e.g., PDSCH or a PUSCH) of a scheduled cell. The scheduling cell can be a primary cell (P Cell), a primary secondary (P(S) Cell), and/or a secondary cell (S Cell). Likewise, the scheduled cell can be a P Cell, a P(S) Cell, and/or an S Cell. <FIG> illustrates the cross-carrier scheduling technique <NUM> between a P(S) Cell <NUM> and an S Cell <NUM>. In some instances, the P(S) Cell <NUM> is a dynamic spectrum sharing (DSS) cell. In some instances, the S Cell <NUM> is a non-DSS cell. As shown, a DCI <NUM>-a transmitted over a control channel (e.g., PDCCH) of the S Cell <NUM> is utilized to schedule downlink data <NUM>-a over a data channel (e.g., PDSCH) of the P(S) Cell <NUM>. While <FIG> illustrates an example of cross-carrier scheduling, the present disclosure is broadly applicable to other cross-carrier scheduling situations.

<FIG> illustrates a multi-carrier scheduling technique <NUM> according to some aspects of the present disclosure. In this regard, aspects of the present disclosure provide mechanisms for scheduling data using multi-carrier scheduling. In a multi-carrier scheduling scheme, the scheduling cell can use a single DCI to schedule data for data transmissions on multiple cells. The scheduling cell may be a P Cell, a P(S) Cell, or an S Cell, and each of the scheduled cells may be a P Cell, a P(S) Cell, or an S Cell. <FIG> illustrates the multi-carrier scheduling technique <NUM> between a P(S) Cell <NUM> and an S Cell <NUM>. In some instances, the P(S) Cell <NUM> is a dynamic spectrum sharing (DSS) cell. In some instances, the S Cell <NUM> is a non-DSS cell. As shown, a DCI <NUM>-b transmitted over a control channel (e.g., PDCCH) of the S Cell <NUM> is utilized to schedule downlink data <NUM>-b over a data channel (e.g., PDSCH) of the P(S) Cell <NUM> and downlink data <NUM>-b over a data channel (e.g., PDSCH) of the S Cell <NUM>. In some instances, the data <NUM>-b transmitted over the P(S) Cell <NUM> may be the same, or at least partially the same, as the downlink data <NUM>-b transmitted over the S Cell <NUM>. In some instances, the data <NUM>-b transmitted over the P(S) Cell <NUM> may be different, or at least partially different, from the downlink data <NUM>-b transmitted over the S Cell <NUM> (e.g., for frequency diversity purposes). While <FIG> illustrates an example of multi-carrier scheduling, the present disclosure is broadly applicable to other multi-carrier scheduling situations.

<FIG> illustrates a DCI format <NUM> for multi-carrier scheduling according to some aspects of the present disclosure. The DCI format <NUM> includes two separate DCIs, DCI <NUM> for a first component carrier (CC1) and DCI <NUM> for a second component carrier (CC2). Each of DCI <NUM> and DCI <NUM> includes fields, and associated field values, applicable for the particular component carrier. The particular fields included in DCI <NUM> and/or DCI <NUM> can be based on the DCI format utilized, which may be an existing DCI format (e.g., 1_0, 1_1, 1_2, etc.) or a future DCI format, including DCI formats implementing aspects of the present disclosure. The DCI format <NUM> can be utilized for cross-carrier and/or multi-carrier scheduling in accordance with the present disclosure.

<FIG> illustrates a DCI format <NUM> for multi-carrier scheduling according to some aspects of the present disclosure. The DCI format <NUM> includes a single DCI <NUM> for CC1 and CC2. The DCI <NUM> includes individual fields, and associated field values, applicable for each component carrier. In the illustrated example, the fields are grouped based on the associated component carrier (i.e., all of the fields for CC1 are grouped together and all of the fields for CC2 are grouped together). Even though DCI <NUM> includes the same fields as DCI <NUM> and DCI <NUM> collectively, having a single DCI <NUM> instead of two separate DCIs (e.g., DCI <NUM> and DCI <NUM>) can save CRC bits, which can improve the spectral efficiency and/or reduce processing requirements. The DCI format <NUM> can be utilized for cross-carrier and/or multi-carrier scheduling in accordance with the present disclosure.

<FIG> illustrates a DCI format <NUM> for multi-carrier scheduling according to some aspects of the present disclosure. The DCI format <NUM> includes a single DCI <NUM> for CC1 and CC2. The DCI <NUM> includes individual fields, and associated field values, applicable for each component carrier. In the illustrated example, the fields are grouped based on field type (i.e., a field for CC1 is positioned adjacent to the corresponding field for CC2). Similar to DCI <NUM>, even though DCI <NUM> includes the same fields as DCI <NUM> and DCI <NUM> collectively, having a single DCI <NUM> instead of two separate DCIs (e.g., DCI <NUM> and DCI <NUM>) can save CRC bits, which can improve the spectral efficiency and/or reduce processing requirements. The DCI format <NUM> can be utilized for cross-carrier and/or multi-carrier scheduling in accordance with the present disclosure.

<FIG> illustrates a DCI format <NUM> for multi-carrier scheduling according to some aspects of the present disclosure. The DCI format <NUM> includes a single DCI <NUM> for CC1 and CC2. The DCI <NUM> includes individual fields, and associated field values, applicable for each component carrier for some field types and joint fields, and associated field values, applicable for both component carriers for other field types. In the illustrated example, "Field <NUM>" and "Field <NUM>" are individual fields, while "Field <NUM>," "Field <NUM>," and "Field <NUM>" are joint fields. By including one or more joint fields, the size of the DCI <NUM> can be reduced as compared to other DCI formats, allowing the DCI to be communicated using less resources. The DCI may organize or group the fields based on component carrier, field type, and/or combinations thereof. The DCI format <NUM> can be utilized for cross-carrier and/or multi-carrier scheduling in accordance with the present disclosure.

In some instances, DCI formats of the present disclosure can include one or more of a new data indicator (NDI) field, a redundancy version (RV) field, a HARQ process ID field, a modulation and coding scheme (MCS) field, a frequency domain resource allocation (FDRA) field. Further, each of these fields may be an individual field or a joint field. In some instances, the MCS, NDI, and/or RV fields are individual fields such that each component carrier has an associated field value. In some instances, having individual fields allows scheduling of up to four layers over two component carriers or more than four layers over a single component carrier (e.g., for some MIMO applications). For example, the two sets of field values may be used for one codeword on each of two component carriers or two codewords on a single component carrier. In some instances, two sets of the MCS, NDI, and/or RV fields are provided for each component carrier, which can allow for more than four layers to be scheduled on two component carriers in a single DCI. In some instances, the RV field is a single bit.

<FIG> is a block diagram of an exemplary UE <NUM> according to aspects of the present disclosure. The UE <NUM> may be a UE <NUM> as discussed above in <FIG>. As shown, the UE <NUM> may include a processor <NUM>, a memory <NUM>, a downlink scheduling and control module <NUM>, a transceiver <NUM> including a modem subsystem <NUM> and a radio frequency (RF) unit <NUM>, and one or more antennas <NUM>. These elements may be in direct or indirect communication with each other, for example via one or more buses.

The memory <NUM> may include a cache memory (e.g., a cache memory of the processor <NUM>), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid state memory device, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In an embodiment, the memory <NUM> includes a non-transitory computer-readable medium. The memory <NUM> may store, or have recorded thereon, instructions <NUM>. The instructions <NUM> may include instructions that, when executed by the processor <NUM>, cause the processor <NUM> to perform the operations described herein with reference to the UEs <NUM> in connection with aspects of the present disclosure, for example, aspects of <FIG>, <FIG>, and <FIG>. Instructions <NUM> may also be referred to as program code. The program code may be for causing a wireless communication device (or specific component(s) of the wireless communication device) to perform these operations, for example by causing one or more processors (such as processor <NUM>) to control or command the wireless communication device (or specific component(s) of the wireless communication device) to do so. The terms "instructions" and "code" should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms "instructions" and "code" may refer to one or more programs, routines, sub-routines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

The downlink scheduling and control module <NUM> may be implemented via hardware, software, or combinations thereof. For example, downlink scheduling and control module <NUM> may be implemented as a processor, circuit, and/or instructions <NUM> stored in the memory <NUM> and executed by the processor <NUM>. In some examples, the downlink scheduling and control module <NUM> can be integrated within the modem subsystem <NUM>. For example, the downlink scheduling and control module <NUM> can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem <NUM>.

The downlink scheduling and control module <NUM> may be used for various aspects of the present disclosure, for example, aspects of <FIG>, <FIG>, <FIG>, and <FIG>. The downlink scheduling and control module <NUM> is configured to communicate with other components of the UE <NUM> to receive a DCI configuration, process the DCI configuration, monitor for DCI based on the DCI configuration, determine whether the downlink communications will be transmitted over a single carrier or multiple carriers based on the DCI, monitor for one or more downlink communication(s) from a base station based on the DCI, perform PDCCH monitoring, perform PDSCH monitoring, determine whether a timer has expired, cancel a timer, determine whether a condition has occurred or is met, and/or perform other functionalities related to the power saving configurations and associated wireless communication techniques of a UE described in the present disclosure.

As shown, the transceiver <NUM> may include the modem subsystem <NUM> and the RF unit <NUM>. The transceiver <NUM> can be configured to communicate bi-directionally with other devices, such as the BSs <NUM>. The modem subsystem <NUM> may be configured to modulate and/or encode the data from the memory <NUM>, and/or the downlink scheduling and control module <NUM> according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit <NUM> may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data (e.g., UL control information, UL data) from the modem subsystem <NUM> (on outbound transmissions) or of transmissions originating from another source such as a UE <NUM> or a BS <NUM>. The RF unit <NUM> may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver <NUM>, the modem subsystem <NUM> and the RF unit <NUM> may be separate devices that are coupled together at the UE <NUM> to enable the UE <NUM> to communicate with other devices.

The RF unit <NUM> may provide the modulated and/or processed data (e.g., data packets or, more generally, data messages that may contain one or more data packets and other information) to the antennas <NUM> for transmission to one or more other devices. The antennas <NUM> may further receive data messages transmitted from other devices. The antennas <NUM> may provide the received data messages for processing and/or demodulation at the transceiver <NUM>. The transceiver <NUM> may provide the demodulated and decoded data (e.g., PDCCH signals, radio resource control (RRC) signals, media access control (MAC) control element (CE) signals, PDSCH signals, DL/UL scheduling grants, DL data, etc.) to the downlink scheduling and control module <NUM> for processing. The antennas <NUM> may include multiple antennas of similar or different designs in order to sustain multiple transmission links. The RF unit <NUM> may configure the antennas <NUM>. The RF unit <NUM> and/or the transceiver <NUM> may include components and/or circuitries that can be powers on and/or off dynamically for power savings. Additionally, or alternatively, the RF unit <NUM> and/or the transceiver <NUM> may include components and/or circuitries with multiple power states that can be configured to transition from one power state (e.g., a higher-power state) to another power state (e.g., a lower-power state) for power savings.

In an embodiment, the UE <NUM> can include multiple transceivers <NUM> implementing different RATs (e.g., NR and LTE). In an embodiment, the UE <NUM> can include a single transceiver <NUM> implementing multiple RATs (e.g., NR and LTE). In an embodiment, the transceiver <NUM> can include various components, where different combinations of components can implement different RATs.

<FIG> is a block diagram of an exemplary BS <NUM> according to aspects of the present disclosure. The BS <NUM> may be a BS <NUM> as discussed above in <FIG>. As shown, the BS <NUM> may include a processor <NUM>, a memory <NUM>, a downlink scheduling and control module <NUM>, a transceiver <NUM> including a modem subsystem <NUM> and a RF unit <NUM>, and one or more antennas <NUM>. These elements may be in direct or indirect communication with each other, for example via one or more buses.

In some instances, the memory <NUM> may include a non-transitory computer-readable medium. The instructions <NUM> may include instructions that, when executed by the processor <NUM>, cause the processor <NUM> to perform operations described herein, for example, aspects of <FIG>, <FIG>, <FIG>, <FIG>, and <FIG>.

The downlink scheduling and control module <NUM> may be implemented via hardware, software, or combinations thereof. For example, the downlink scheduling and control module <NUM> may be implemented as a processor, circuit, and/or instructions <NUM> stored in the memory <NUM> and executed by the processor <NUM>. In some examples, the downlink scheduling and control module <NUM> can be integrated within the modem subsystem <NUM>. For example, the downlink scheduling and control module <NUM> can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem <NUM>.

The downlink scheduling and control module <NUM> may be used for various aspects of the present disclosure, for example, aspects of <FIG>, <FIG>, <FIG>, and <FIG>. The downlink scheduling and control module <NUM> can be configured to determine a DCI configuration for one or more UEs, transmit the DCI configuration to the one or more UEs, perform downlink data scheduling over one or more carriers, including cross-carrier and/or multi-carrier scheduling, generate DCI base on the downlink scheduling and/or the DCI configuration, transmit DCI, transmit one or more downlink communication(s) from based on the DCI, transmit PDCCH communications, transmit PDSCH communications, determine whether a timer has expired, cancel a timer, determine whether a condition has occurred or is met, and/or perform other functionalities related to the power saving configurations and associated wireless communication techniques of a base station described in the present disclosure.

As shown, the transceiver <NUM> may include the modem subsystem <NUM> and the RF unit <NUM>. The transceiver <NUM> can be configured to communicate bi-directionally with other devices, such as the UEs <NUM> and/or <NUM> and/or another core network element. The modem subsystem <NUM> may be configured to modulate and/or encode data according to a MCS (e.g., a LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit <NUM> may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data (e.g., PDCCH signals, RRC signals, MAC CE signals, PDSCH signals, etc.) from the modem subsystem <NUM> (on outbound transmissions) or of transmissions originating from another source, such as a UE <NUM> or <NUM>. The RF unit <NUM> may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver <NUM>, the modem subsystem <NUM> and/or the RF unit <NUM> may be separate devices that are coupled together at the BS <NUM> to enable the BS <NUM> to communicate with other devices.

The RF unit <NUM> may provide the modulated and/or processed data, (e.g., data packets or, more generally, data messages that may contain one or more data packets and other information) to the antennas <NUM> for transmission to one or more other devices. This may include, for example, transmission of information to a UE <NUM> or <NUM> according to aspects of the present disclosure. The antennas <NUM> may further receive data messages transmitted from other devices and provide the received data messages for processing and/or demodulation at the transceiver <NUM>. The transceiver <NUM> may provide the demodulated and decoded data (e.g., RACH message(s), ACK/NACKs for PDCCH signals, UL data, ACK/NACKs for DL data, etc.) to the downlink scheduling and control module <NUM> for processing. The antennas <NUM> may include multiple antennas of similar or different designs in order to sustain multiple transmission links.

In an embodiment, the BS <NUM> can include multiple transceivers <NUM> implementing different RATs (e.g., NR and LTE). In an embodiment, the BS <NUM> can include a single transceiver <NUM> implementing multiple RATs (e.g., NR and LTE). In an embodiment, the transceiver <NUM> can include various components, where different combinations of components can implement different RATs.

<FIG> illustrates a scheduling/transmission configuration <NUM> of a wireless communication method according to some aspects of the present disclosure. The scheduling/transmission configuration <NUM> illustrates multi-carrier scheduling between a P(S) Cell <NUM> and an S Cell <NUM>. In some instances, the P(S) Cell <NUM> is a dynamic spectrum sharing (DSS) cell. In some instances, the S Cell <NUM> is a non-DSS cell. As shown, a DCI <NUM>-a transmitted over a control channel (e.g., PDCCH) of the S Cell <NUM> is utilized to schedule downlink data <NUM>-a over a data channel (e.g., PDSCH) of the P(S) Cell <NUM> and downlink data <NUM>-a over a data channel (e.g., PDSCH) of the S Cell <NUM>. In some instances, the data <NUM>-a transmitted over the P(S) Cell <NUM> may be the same, or at least partially the same, as the downlink data <NUM>-a transmitted over the S Cell <NUM>. In some instances, the data <NUM>-a transmitted over the P(S) Cell <NUM> may be different, or at least partially different, from the downlink data <NUM>-a transmitted over the S Cell <NUM>.

In some instances, a DCI message can include a first hybrid automatic repeat request (HARQ) process ID associated with a first component carrier and a second HARQ process ID associated with a second component carrier. For example, <FIG> illustrates DCI <NUM>-a having HARQ process IDs for each of the P(S) Cell <NUM> and the S Cell <NUM>. In particular, DCI <NUM>-a shows both the P(S) Cell <NUM> and the S Cell <NUM> having the same value (e.g., HPID#<NUM>). Similarly, <FIG> shows a DCI <NUM>-a-with associated downlink data <NUM>-b scheduled over the P(S) Cell <NUM> and the S Cell <NUM>-having HARQ process IDs for each of the P(S) Cell <NUM> and the S Cell <NUM>. In particular, DCI <NUM>-a shows both the P(S) Cell <NUM> and the S Cell <NUM> having the same value (e.g., HPID#<NUM>), but a different value than DCI <NUM>-a.

In some instances, a UE may not receive, be able to decode, and/or otherwise have issues receiving scheduled downlink data that results in the UE transmitting a negative acknowledgement (NACK) to the base station indicating that the scheduled downlink data was not properly received by the UE. In some instances, the NACK is part of a HARQ process for a component carrier, which may be at least partially defined by the HARQ process ID included in the DCI. For example, <FIG> illustrates a situation where downlink data <NUM>-a is not properly received over the data channel of the S Cell <NUM> (as indicated by <NUM>-a) and downlink data <NUM>-b is not properly received over the data channel of the P(S) Cell <NUM> (as indicated by <NUM>-b). In accordance with the present disclosure, a single DCI (e.g., DCI <NUM>-c) can be utilized to schedule retransmission of the downlink data <NUM>-a over the S Cell <NUM> and the downlink data <NUM>-b over the P(S) Cell <NUM>. That is, the downlink data scheduled by the DCI <NUM>-c can include a first retransmission associated with a first HARQ process ID (e.g., downlink data <NUM>-a associated with HPID#<NUM> for the S Cell <NUM>) and a second retransmission associated with a different HARQ process ID (e.g., downlink data <NUM>-b associated with HPID#<NUM> for the S Cell <NUM>). Having separate HARQ process IDs for each component carrier in the DCI can allow retransmissions to be scheduled on each carrier separately. This can facilitate scheduling, via a single DCI, retransmission of data associated with a first HARQ process on a first carrier and retransmission of data associated with a second HARQ process on a second, different carrier. This can improve efficiency and reduce latency for the associated data communications.

<FIG> illustrates a scheduling/transmission configuration <NUM> of a wireless communication method according to some aspects of the present disclosure. The scheduling/transmission configuration <NUM> illustrates multi-carrier and/or cross-carrier scheduling between a P(S) Cell <NUM> and an S Cell <NUM>. In some instances, the P(S) Cell <NUM> is a dynamic spectrum sharing (DSS) cell. In some instances, the S Cell <NUM> is a non-DSS cell. As shown, a DCI <NUM>-a transmitted over a control channel (e.g., PDCCH) of the S Cell <NUM> schedules downlink data <NUM>-a over a data channel (e.g., PDSCH) of the P(S) Cell <NUM> and downlink data <NUM>-a over a data channel (e.g., PDSCH) of the S Cell <NUM>. In some instances, the data <NUM>-a transmitted over the P(S) Cell <NUM> may be the same, or at least partially the same, as the downlink data <NUM>-a transmitted over the S Cell <NUM>. In some instances, the data <NUM>-a transmitted over the P(S) Cell <NUM> may be different, or at least partially different, from the downlink data <NUM>-a transmitted over the S Cell <NUM>.

In some instances, at least one field of the DCI <NUM>-a indicates whether the downlink data <NUM>-a is scheduled over a single component carrier or multiple component carriers. In some instances, the DCI includes a first field associated with a first component carrier (e.g., P(S) Cell <NUM>) and a second field associated with a second component carrier (e.g., S Cell <NUM>). The values of the first and second fields can indicate that the downlink data communication is scheduled over multiple component carriers. For example, the value of a field may indicate that data is scheduled for transmission over that component carrier. Accordingly, when the values of the first and second fields each indicate that data is scheduled for transmission, the DCI indicates that the downlink data is scheduled over multiple component carriers. For example, <FIG> illustrates an example where DCI <NUM>-a includes a field value for the S Cell <NUM> (e.g., Field Value X) that indicates downlink data <NUM>-a will be transmitted over the S Cell <NUM> and a field value for the P(S) Cell <NUM> (e.g., Field Value Y) that indicates downlink data <NUM>-a will be transmitted over the P(S) Cell <NUM>. In some instances, the UE can determine the downlink data communication is scheduled over multiple component carriers based on the first field and the second field having values that are assigned for a primary purpose of the first and second fields. For example, a field may be associated with a frequency domain resource allocation (FDRA) and the value may be associated with a data transmission (e.g., one or more "one" values in a bitmap for RA Type <NUM>, one or more "zero" values for RC Type <NUM>, etc.).

In some instances, the value of the field can indicate that no data is scheduled for transmission over the associated component carrier. Accordingly, when the value one of the first or second fields indicates that data is not scheduled for transmission, the DCI indicates that the downlink data is scheduled over a single component carrier. For example, in some instances a DCI indicates the downlink data communication is scheduled over a single component carrier based on at least one of the first field or the second field having a value that is not assigned for a primary purpose of the field. For example, a field may be associated with a frequency domain resource allocation (FDRA) and the value may not be assigned to or have an associated FDRA (e.g., all zeros for RA Type <NUM>, all ones for RC Type <NUM>, etc.). A value that is not assigned for a primary purpose of the field may include a value that is outside of the defined range of available values for the field, a value that does not have meaning in the context of the field, a value for an unused field, and/or is a value otherwise distinguishable from the values used for the primary purpose of the field.

<FIG> illustrates this approach of using a value that is not assigned for a primary purpose of a field. For example, DCI <NUM>-b includes a field value for the S Cell <NUM> (e.g., Field Value N/A) that indicates downlink data will not be transmitted over the S Cell <NUM> and a field value for the P(S) Cell <NUM> (e.g., Field Value X) that indicates downlink data <NUM>-a will be transmitted over the P(S) Cell <NUM>. In this manner, the DCI <NUM>-b indicates single-carrier scheduling over P(S) cell <NUM>. As another example, DCI <NUM>-c includes a field value for the S Cell <NUM> (e.g., Field Value Y) that indicates downlink data <NUM>-c will be transmitted over the S Cell <NUM> and a field value for the P(S) Cell <NUM> (e.g., Field Value N/A) that indicates downlink data will not be transmitted over the P(S) Cell <NUM>. In this manner, the DCI <NUM>-c indicates single-carrier scheduling over S cell <NUM>.

In some instances, the search space in which the DCI <NUM>-a is transmitted indicates whether the downlink data <NUM>-a is scheduled over a single component carrier or multiple component carriers. In this regard, a first search space can be associated with the single component carrier and a second search space can associated with the multiple component carriers. If the DCI is transmitted in the first search space associated with the single component carrier, then a UE receiving the DCI can determine the associated downlink data is scheduled over the single component carrier and monitor for the data accordingly. Similarly, if the DCI message is transmitted in the second search space associated with the multiple component carriers, then a UE receiving the DCI can determine the associated downlink data is scheduled over the multiple component carriers and monitor for the data accordingly. The first search space (associated with the single component carrier) and the second search space (associated with multiple component carriers) may be completely separate or partially overlap. Further, in some instances separate search spaces may be assigned for each single component carrier such that a UE can determine which single component carrier the downlink data will be transmitted on based on the search space in which a single-carrier DCI is received. In some instances, a UE receives information regarding the assigned search space(s) and any association of the search space(s) to single-carrier and/or multi-carrier scheduling via an RRC communication (e.g., RRC configuration).

In the example of <FIG>, DCI <NUM>-a is transmitted in a search space <NUM> that is associated with multi-carrier scheduling. The DCI <NUM>-a may include a carrier indicator field (CIF) value that indicates the downlink data <NUM>-a is scheduled for multi-carrier transmission. As shown, the DCI <NUM>-a is transmitted in the multi-carrier search space <NUM> and schedules downlink data <NUM>-a on both the P(S) Cell <NUM> and the S Cell <NUM>. DCI <NUM>-b is transmitted in a search space <NUM> that is associated with single-carrier scheduling. The DCI <NUM>-b may include CIF value that indicates the downlink data <NUM>-b is scheduled for single-carrier transmission. As shown, the DCI <NUM>-b is transmitted in the single-carrier search space <NUM> and schedules downlink data <NUM>-a only on the P(S) Cell <NUM>. Similarly, DCI <NUM>-c is transmitted in the single-carrier search space <NUM> and schedules downlink data <NUM>-a only on the S Cell <NUM>. The DCI <NUM>-c may also include a CIF value that indicates the downlink data <NUM>-c is scheduled for single-carrier transmission.

<FIG> illustrates a signal diagram illustrating a cross-carrier and/or multi-carrier scheduling technique <NUM> between a base station <NUM>-a and a UE <NUM>-a according to the claimed invention. As shown, at step <NUM> the base station <NUM>-a may transmit a radio resource control (RRC) configuration to the UE <NUM>-a. In some instances, the RRC configuration may include DCI configuration information. For example, the DCI configuration may provide information regarding the search space(s) in which DCI may be transmitted (including any association of the search space(s) to single-carrier and/or multi-carrier scheduling), DCI format(s) and/or field(s), and/or other information to facilitate the UE <NUM>-a monitoring for and receiving DCI from the base station <NUM>-a.

At step <NUM>, the base station <NUM>-a schedules downlink communication(s). The base station <NUM>-a may schedule the downlink communication(s) using single-carrier, multi-carrier, and/or cross-carrier scheduling in accordance with aspects of the present disclosure (see, e.g., <FIG>, <FIG>, <FIG>, and <FIG>).

At step <NUM>, the base station <NUM>-a transmits DCI to the UE <NUM>-a in accordance with aspects of the present disclosure (see, e.g., <FIG>, <FIG>, <FIG>, and <FIG>).

At step <NUM>, the UE <NUM>-a monitors for the DCI from the base station <NUM>-a in accordance with aspects of the present disclosure (see, e.g., <FIG>, <FIG>, <FIG>, and <FIG>). In some instances, the UE <NUM>-a monitors for the DCI over a control channel (e.g., PDCCH) based on the DCI configuration information received in the RRC configuration at step <NUM>.

At step <NUM>, the UE <NUM>-a processes the received DCI in accordance with aspects of the present disclosure (see, e.g., <FIG>, <FIG>, <FIG>, and <FIG>). In this regard, the UE <NUM>-a may process the DCI to determine whether downlink data communications will be transmitted over a single carrier or multiple carriers. For example, as described in various aspects of the present disclosure, the UE <NUM>-a may utilize the DCI format, the search space in which the DCI is received, one or more field values of the DCI, one or more other characteristics of the DCI, and/or combinations thereof to determine whether the downlink data communications associated with the DCI will be transmitted over a single carrier or multiple carriers.

At step <NUM>-a, the UE <NUM>-a monitors for downlink data over a first component carrier (CC1) based on the DCI received at step <NUM>. Accordingly, if the DCI indicates that data is to be transmitted over CC1, then the UE <NUM>-a will actively monitor the data channel (PDSCH) of CC1 for the downlink data communication during step <NUM>-a. However, if the DCI indicates that data will not be transmitted over CC1, then the UE <NUM>-a will not monitor the data channel (PDSCH) of CC1 during step <NUM>-a. Similarly, at step <NUM>-b, the UE <NUM>-a monitors for downlink data over a second component carrier (CC2) based on the DCI received at step <NUM>. If the DCI indicates that data is to be transmitted over CC2, then the UE <NUM>-a will actively monitor the data channel (PDSCH) of CC2 for the downlink data communication during step <NUM>-a. However, if the DCI indicates that data will not be transmitted over CC2, then the UE <NUM>-a will not monitor the data channel (PDSCH) of CC2 during step <NUM>-a. Steps <NUM>-a and <NUM>-b may be performed separately, simultaneously, and/or partially overlapping.

At step <NUM>-a, the base station <NUM>-a transmits downlink data over the first component carrier (CC1) in accordance with the DCI transmitted at step <NUM>. Accordingly, if the DCI indicates that data is to be transmitted over CC1, then the base station <NUM>-a will transmit the downlink communication over the data channel (PDSCH) of CC1 during step <NUM>-a. However, if the DCI indicates that data will not be transmitted over CC1, then the base station <NUM>-a will not transmit any data over the data channel (PDSCH) of CC1 during step <NUM>-a. Similarly, at step <NUM>-b, the base station <NUM>-a transmits downlink data over the second component carrier (CC2) in accordance with the DCI transmitted at step <NUM>. If the DCI indicates that data is to be transmitted over CC2, then the base station <NUM>-a will transmit the downlink communication over the data channel (PDSCH) of CC2 during step <NUM>-b. However, if the DCI indicates that data will not be transmitted over CC2, then the base station <NUM>-a will transmit the downlink communication over the data channel (PDSCH) of CC2 during step <NUM>-b. Steps <NUM>-a and <NUM>-b may be performed separately, simultaneously, and/or partially overlapping.

<FIG> is a flow diagram of a communication method <NUM> according to the claimed invention. Method <NUM> is executed by a wireless communication device, such as the UEs <NUM> and/or <NUM> utilizing one or more components, such as the processor <NUM>, the memory <NUM>, the downlink scheduling and control module <NUM>, the transceiver <NUM>, the modem <NUM>, the one or more antennas <NUM>, and various combinations thereof. As illustrated, the method <NUM> includes a number of enumerated steps, but the method <NUM> may include additional steps before, after, and in between the enumerated steps. For example, in some instances one or more aspects of techniques <NUM>, <NUM>, and/or <NUM>; DCI formats <NUM>, <NUM>, <NUM>, and/or <NUM>; scheduling/transmission configurations <NUM>, <NUM>, and/or <NUM> may be implemented as part of method <NUM>. In some instances, one or more of the enumerated steps may be omitted or performed in a different order.

At step <NUM>, the method <NUM> includes receiving a downlink control information (DCI) message having a DCI format, the DCI message scheduling a downlink data communication over a single component carrier or multiple component carriers. The DCI message may be received over a control channel (e.g., PDCCH) of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, the DCI message is utilized for cross-carrier scheduling. For example, a scheduling cell (e.g., P Cell, a P(S) Cell, and/or an S Cell) uses the DCI transmitted over the control channel (e.g., PDCCH) of the scheduling cell to schedule data on a data channel (e.g., PDSCH) of a different cell (e.g., P Cell, a P(S) Cell, and/or an S Cell). In some instances, the DCI message is utilized for multi-carrier scheduling. For example, a single DCI transmitted over the PDCCH of the scheduling cell can be used to schedule data for data transmissions on multiple cells, including the scheduling cell and a different cell. In some instances, the DCI message is utilized for cross-carrier and multi-carrier scheduling. Also, the cross-carrier and/or multi-carrier scheduling of the DCI received at step <NUM> can be utilized in the context of DSS. For example, a non-DSS cell can use a single DCI to schedule data on a DSS cell and/or the non-DSS cell. The cross-carrier and/or multi-carrier scheduling of the DCI received at step <NUM> can also be utilized in the context of cross-carrier scheduling for carrier aggregation.

At step <NUM>, the method <NUM> includes determining, based on the received DCI message, whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers. In this regard, the UE may utilize one or more characteristics of the DCI message (e.g., field value(s), search space(s), format, etc.) to determine whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers.

In some instances, determining whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers at step <NUM> includes determining whether the DCI message has a first format associated with the single component carrier or a second format associated with the multiple component carriers. That is, a first DCI format can be used for single-carrier scheduling and a second, different DCI format can be used for multi-carrier scheduling. In this regard, the UE may determine, at step <NUM>, whether data is scheduled for transmission over a single carrier or multiple carriers based on the format of the received DCI.

In some instances, determining whether the downlink data communication is scheduled on the single component carrier or the multiple component carriers at step <NUM> includes determining whether the received DCI message was received in a first search space associated with the single component carrier or a second search space associated with the multiple component carriers (see, e.g., <FIG>). If the DCI message is received in the first search space associated with the single component carrier, then the UE can determine the associated data is scheduled over the single component carrier and monitor for the data accordingly. Similarly, if the DCI message is received in the second search space associated with the multiple component carriers, then the UE can determine the associated data is scheduled over the multiple component carriers and monitor for the data accordingly. The first search space (associated with the single component carrier) and the second search space (associated with multiple component carriers) may be completely separate or partially overlap.

In some instances, determining whether the downlink data communication is scheduled over the single component carrier or the multiple component carriers at step <NUM> includes determining whether at least one field of the DCI message indicates the downlink data communication is scheduled over the single component carrier or the multiple component carriers (see, e.g., <FIG>). In some instances, the DCI includes a first field associated with a first component carrier and a second field associated with a second component carrier. The UE may determine the downlink data communication is scheduled over the single component carrier based on a value of the first field or the second field. For example, the value of the field may indicate to the UE that no data is scheduled for transmission over that component carrier. In some instances, the UE may determine the downlink data communication is scheduled over the single component carrier based on at least one of the first field or the second field having a value that is not assigned for a primary purpose of the field. For example, a field may be associated with a frequency domain resource allocation (FDRA) and the value may not be assigned to or have an associated FDRA (e.g., all zeros for RA Type <NUM>, all ones for RC Type <NUM>, etc.).

Similarly, the UE may determine the downlink data communication is scheduled over multiple component carriers based on the values of the first and second fields. For example, the value of the field may indicate to the UE that data is scheduled for transmission over that component carrier. Accordingly, when the values of the first and second fields each indicate that data is scheduled for transmission, the UE can determine that the data is scheduled over multiple component carriers. In some instances, the UE may determine the downlink data communication is scheduled over multiple component carriers based on the first field and the second field having values that are assigned for a primary purpose of the first and second fields.

The DCI message includes a first hybrid automatic repeat request (HARQ) process ID associated with a first component carrier and a second HARQ process ID associated with a second component carrier (see, e.g., <FIG>). In this regard, the downlink data communication scheduled by the DCI message can include a first retransmission associated with the first HARQ process ID and a second retransmission associated with the second HARQ process ID. Having separate HARQ process IDs for each component carrier can allow retransmissions to be scheduled on each carrier separately. This can facilitate scheduling, via a single DCI, retransmission of data associated with a first HARQ process on a first carrier and retransmission of data associated with a second HARQ process on a second, different carrier. This can improve efficiency and reduce latency for the associated data communications. In some instances, the DCI message includes a HARQ process ID associated with both the first component carrier and the second component carrier. That is, a single HARQ process ID can be used for both the first and second component carriers. Having a common HARQ process ID can reduce the size of the DCI by having a joint field instead of two separate fields in the DCI (see, e.g., <FIG>).

At step <NUM>, the method <NUM> includes receiving, based on the determining, the downlink data communication over the single component carrier or the multiple component carriers. The downlink data communication may be received over a PDSCH of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, the downlink data communication is received over the data channel of a cell that is different than the cell over which the DCI message was received (at step <NUM>). In some instances, the downlink data communication is received over both a data channel of the cell over which the DCI message was received and a data channel of a different cell. In some instances, the downlink data communication is received over a DSS cell. In some instances, the DCI message is received over a physical downlink control channel (PDCCH) of a secondary cell and at least a first part of the downlink data communication signal is received over a physical downlink shared channel (PDSCH) of a primary cell (e.g., a P Cell and/or a P(S) Cell). A second part of the downlink data communication (e.g., for multi-carrier scheduling) may be received over a PDSCH of the secondary cell.

<FIG> is a flow diagram of a communication method <NUM> according to some aspects of the present disclosure. Aspects of the method <NUM> can be executed by a wireless communication device, such as the BSs <NUM> and/or <NUM> utilizing one or more components, such as the processor <NUM>, the memory <NUM>, the downlink scheduling and control module <NUM>, the transceiver <NUM>, the modem <NUM>, the one or more antennas <NUM>, and various combinations thereof. As illustrated, the method <NUM> includes a number of enumerated steps, but the method <NUM> may include additional steps before, after, and in between the enumerated steps. For example, in some instances one or more aspects of techniques <NUM>, <NUM>, and/or <NUM>; DCI formats <NUM>, <NUM>, <NUM>, and/or <NUM>; scheduling/transmission configurations <NUM>, <NUM>, and/or <NUM> may be implemented as part of method <NUM>. In some instances, one or more of the enumerated steps may be omitted or performed in a different order.

At step <NUM>, the method <NUM> includes transmitting a first downlink control information (DCI) message having a DCI format, the first DCI message scheduling a first downlink data communication over a single component carrier. The DCI message may be transmitted, at step <NUM>, over a control channel (e.g., PDCCH) of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, the DCI message is utilized by the base station for cross-carrier scheduling. For example, the base station may use a scheduling cell (e.g., P Cell, a P(S) Cell, and/or an S Cell) to transmit the DCI over the control channel (e.g., PDCCH) of the scheduling cell to schedule data on a data channel (e.g., PDSCH) of a different cell (e.g., P Cell, a P(S) Cell, and/or an S Cell). The base station can utilize the cross-carrier scheduling of the DCI transmitted at step <NUM> in the context of DSS. For example, the base station may transmit a single DCI over a non-DSS cell to schedule data on a DSS cell. The cross-carrier scheduling of the DCI transmitted at step <NUM> can also be utilized in the context of cross-carrier scheduling for carrier aggregation.

In some instances, the base station utilizes different DCI formats to indicate single-carrier scheduling versus multi-carrier scheduling. For example, a first format of the DCI message can be associated with a single component carrier and a second format of the DCI message can be associated with multiple component carriers. That is, a first DCI format can be used for single-carrier scheduling and a second, different DCI format can be used for multi-carrier scheduling. Accordingly, the base station can determine and/or generate the format for the DCI message that will be transmitted at step <NUM> based on the scheduled data transmission (e.g., single carrier format versus multi-carrier format). In some instances, the format of the DCI message transmitted at step <NUM> can be used by the receiving UE to determine the scheduled data will be transmitted over a single carrier.

In some instances, the first DCI message is transmitted, at step <NUM>, in a first search space associated with the single component carrier. In this regard, the base station may utilize different search spaces to transmit the DCI to indicate single-carrier scheduling versus multi-carrier scheduling (see, e.g., <FIG>). For example, a first search space may be associated with a single component carrier and a second search space associated with multiple component carriers. Accordingly, when data is scheduled for transmission over a single carrier the base station can transmit the DCI message in the first search space associated with the single component carrier. The UE can determine, based on receiving the DCI message in the first search space, that the associated data is scheduled over the single component carrier and monitor for the data accordingly. Similarly, when data is scheduled for transmission over multiple carriers the base station can transmit the DCI message in the second search space associated with the multiple component carriers. The UE can determine, based on receiving the DCI message in the second search space, that the associated data is scheduled over the multiple component carriers and monitor for the data accordingly. The first search space (associated with the single component carrier) and the second search space (associated with multiple component carriers) may be completely separate or partially overlap.

In some instances, the first DCI message includes at least one field indicating the first downlink data communication is scheduled over the single component carrier. For example, the DCI may include a first field associated with a first component carrier and a second field associated with a second component carrier. The base station may indicate the downlink data communication is scheduled over the single component carrier based on a value of the first field or the second field. For example, the base station may set the value of the field to indicate to the UE that no data is scheduled for transmission over that component carrier. In some instances, the base station may indicate that a downlink data communication is scheduled over a single component carrier based on at least one of the first field or the second field having a value that is not assigned for a primary purpose of the field. For example, a field may be associated with a frequency domain resource allocation (FDRA) and the value used by the base station may not be assigned to or have an associated FDRA (e.g., all zeros for RA Type <NUM>, all ones for RC Type <NUM>, etc.). Accordingly, in some instances, when the first field or the second field has a value that is not assigned for a primary purpose of the field, the DCI transmitted at step <NUM> indicates that the downlink data communication is scheduled over the single component carrier.

At step <NUM>, the method <NUM> includes transmitting the first downlink data communication over the single component carrier. The downlink data communication may be transmitted over a PDSCH of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, the downlink data communication is transmitted over the data channel of a cell that is different than the cell over which the DCI message was transmitted (at step <NUM>). In some instances, the downlink data communication is transmitted over a DSS cell. In some instances, the DCI message is transmitted (at step <NUM>) over a physical downlink control channel (PDCCH) of a secondary cell and the downlink data communication signal is transmitted (at step <NUM>) over a physical downlink shared channel (PDSCH) of a primary cell (e.g., a P Cell and/or a P(S) Cell).

At step <NUM>, the method <NUM> includes transmitting a second DCI message, the second DCI message scheduling a second downlink data communication over multiple component carriers. The DCI message may be transmitted, at step <NUM>, over a control channel (e.g., PDCCH) of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, the DCI message transmitted at step <NUM> is transmitted over the same cell as the DCI message transmitted at step <NUM>. In some instances, the DCI message is utilized by the base station for multi-carrier scheduling. For example, a single DCI transmitted, at step <NUM>, over the control channel (e.g., PDCCH) of a scheduling cell can be used to schedule data for data transmissions on multiple cells, including the scheduling cell and a different cell. In some instances, the DCI message transmitted at step <NUM> is utilized by the base station for cross-carrier and multi-carrier scheduling. Also, the cross-carrier and/or multi-carrier scheduling of the DCI transmitted at step <NUM> can be utilized in the context of DSS. For example, the base station may utilize a non-DSS cell to transmit a single DCI, at step <NUM>, to schedule data on a DSS cell and the non-DSS cell.

In some instances, the DCI message transmitted at step <NUM> has the same DCI format as the DCI message transmitted at step <NUM>. That is, the same DCI format can be utilized by the base station for both single-carrier scheduling and multi-carrier scheduling. In other instances, DCI message transmitted at step <NUM> has a different DCI format than the DCI message transmitted at step <NUM>. For example, the base station can utilize different DCI formats to indicate single-carrier scheduling versus multi-carrier scheduling. Accordingly, the base station can determine and/or generate the format for the DCI message that will be transmitted at step <NUM> based on the scheduled data transmission (e.g., single carrier format versus multi-carrier format). Accordingly, in some instances the format of the DCI message transmitted at step <NUM> can be used by the receiving UE to determine the scheduled data will be transmitted over multiple carriers.

In some instances, the second DCI message includes transmitting the second DCI message in a second search space associated with the multiple component carriers. As discussed above, the base station may utilize different search spaces to indicate single-carrier scheduling versus multi-carrier scheduling (see, e.g., <FIG>). For example, a first search space may be associated with a single component carrier and a second search space associated with multiple component carriers. Accordingly, when data is scheduled for transmission over multiple carriers the base station can transmit the DCI message in the second search space associated with the multiple component carriers. The UE can determine, based on receiving the DCI message in the second search space, that the associated data is scheduled over the multiple component carriers and monitor for the data accordingly. The first search space (associated with the single component carrier) and the second search space (associated with multiple component carriers) may be completely separate or partially overlap.

In some instances, the second DCI message includes at least one field indicating the second downlink data communication is scheduled over the multiple component carriers. For example, the DCI may include a first field associated with a first component carrier and a second field associated with a second component carrier. The base station may indicate the downlink data communication is scheduled over multiple component carriers based on a value of the first field and/or the second field. For example, the base station may set the value of the field to indicate to the UE that data is scheduled for transmission over that component carrier. In some instances, the base station may utilize a value that is assigned for a primary purpose of the field to indicate that data will be transmitted over the carrier. For example, a field may be associated with a frequency domain resource allocation (FDRA) and the value may be assigned to or have an associated FDRA. Accordingly, in some instances, when the first field and the second field each has a value that is assigned for a primary purpose of the field, the DCI transmitted at step <NUM> indicates that the second downlink data communication is scheduled over the multiple component carriers.

At step <NUM>, the method <NUM> includes transmitting the second downlink data communication over the multiple component carriers. The downlink data communication may be transmitted over a PDSCH of a P Cell, a P(S) Cell, and/or an S Cell. In some instances, at least a portion of the downlink data communication is transmitted over the data channel of a cell that is different than the cell over which the DCI message was transmitted (at step <NUM>). In some instances, at least a portion of the downlink data communication is transmitted over a DSS cell. In some instances, the DCI message is transmitted (at step <NUM>) over a physical downlink control channel (PDCCH) of a secondary cell and the downlink data communication signal is transmitted (at step <NUM>) on the multiple component carriers, including at least a first part over a physical downlink shared channel (PDSCH) of a primary cell and at least a second part over a PDSCH of the secondary cell.

In some instances, the DCI message transmitted at step <NUM> includes a first hybrid automatic repeat request (HARQ) process ID associated with a first component carrier and a second HARQ process ID associated with a second component carrier. In this regard, the second downlink data communication transmitted at step <NUM> can include a first retransmission associated with the first HARQ process ID and a second retransmission associated with the second HARQ process ID. In this manner, the base station can schedule, via a single DCI, retransmission of data associated with a first HARQ process on a first carrier and retransmission of data associated with a second HARQ process on a second, different carrier. This can improve efficiency and reduce latency for the associated data communications. In some instances, the DCI message transmitted at step <NUM> includes a HARQ process ID associated with both the first component carrier and the second component carrier. That is, the base station can utilize a single HARQ process ID in the DCI for both the first and second component carriers. Utilizing a common HARQ process ID can reduce the size of the DCI by having a joint field instead of two separate fields in the DCI (see, e.g., <FIG>).

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment (<NUM>, <NUM>), the method comprising:
receiving (<NUM>, <NUM>, <NUM>), from a base station, a downlink control information, DCI, message (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) having a DCI format (<NUM>, <NUM>, <NUM>), the DCI message (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) scheduling a downlink data (<NUM>, <NUM>, <NUM>, <NUM>) communication over a single component carrier or multiple component carriers, wherein the DCI message (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) includes a first hybrid automatic repeat request, HARQ, process identifier, ID, associated with a first component carrier and a second HARQ process ID associated with a second component carrier, and the second HARQ process ID is different from the first HARQ process ID;
determining (<NUM>, <NUM>), based on the received DCI message (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>), whether the downlink data (<NUM>, <NUM>, <NUM>, <NUM>) communication is scheduled over the single component carrier or the multiple component carriers; and
receiving (<NUM>, <NUM>), based on the determining, the downlink data (<NUM>, <NUM>, <NUM>, <NUM>) communication, from the base station, over the single component carrier or the multiple component carriers.