CN112425109A

CN112425109A - Multi-carrier scheduling and search space activation

Info

Publication number: CN112425109A
Application number: CN201980047556.7A
Authority: CN
Inventors: W.南; T.罗; J.塞尚
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2018-07-20
Filing date: 2019-07-20
Publication date: 2021-02-26
Also published as: US20200029317A1; WO2020018976A1; EP3824585A1

Abstract

Certain aspects of the present disclosure provide techniques for multi-carrier scheduling and search space activation.

Description

Multi-carrier scheduling and search space activation

Requirement for priority pursuant to 35U.S.C. § 119

This application claims priority from us application serial No. 16/517,221 filed on 7/19/2019, priority from us provisional patent application serial No. 62/701,415 filed on 7/20/2018, and the benefit of that application, both assigned to the present assignee and hereby expressly incorporated herein by reference.

Technical Field

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for communicating (covey) command or allocation information for multiple Component Carriers (CCs).

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, and so on. These wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmission power, etc.). Examples of such multiple-access systems include third generation partnership project (3GPP) Long Term Evolution (LTE) systems, LTE-advanced (LTE-a) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and the like.

In some examples, a wireless multiple-access communication system may include multiple Base Stations (BSs) that are each capable of simultaneously supporting communication for multiple communication devices, also referred to as User Equipment (UE). In an LTE or LTE-a network, a set of one or more base stations may define an enodeb (enb). In other examples (e.g., in a next generation, New Radio (NR), or 5G network), a wireless multiple-access communication system may include a plurality of Distributed Units (DUs) (e.g., Edge Units (EUs), Edge Nodes (ENs), Radio Heads (RHs), intelligent radio heads (SRHs), Transmission Reception Points (TRPs), etc.) in communication with a number of Central Units (CUs) (e.g., Central Nodes (CNs), Access Node Controllers (ANCs), etc.), where a set of one or more distributed units in communication with a central unit may define an access node (e.g., which may be referred to as a base station, a 5G NB, a next generation NodeB (gNB or gNB), a TRP, etc.). A base station or distributed unit may communicate with a set of UEs on downlink channels (e.g., for transmissions from the base station to the UEs) and uplink channels (e.g., for transmissions from the UEs to the base station or distributed unit).

These multiple access technologies have been used in various telecommunications standards to provide common protocols that enable different wireless devices to communicate on a city, country, region, or even global level. New Radios (NR) (e.g., 5G) are an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3 GPP. It is designed to better support mobile broadband internet access by improving spectral efficiency, reducing cost, improving service, using new spectrum, and better integrating with other open standards by using OFDMA with Cyclic Prefix (CP) on Downlink (DL) and Uplink (UL). For this reason, NR supports beamforming, Multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues to increase, there is a need for further improvements in NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access techniques and telecommunications standards employing these techniques.

Disclosure of Invention

The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the claims which follow, certain features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "detailed description of certain embodiments" one will understand how the features of this disclosure provide advantages that include: improved communication between an access point and a station in a wireless network.

Certain aspects provide a method for wireless communications by a User Equipment (UE). The method generally includes: receiving Downlink Control Information (DCI) having one or more fields for conveying commands or allocation information for a plurality of Component Carriers (CCs); and taking at least one action related to the plurality of CCs according to the command or the assignment information.

Certain aspects provide a method for wireless communications by a network entity. The method generally includes: generating Downlink Control Information (DCI) having one or more fields for conveying order or allocation information for a plurality of Component Carriers (CCs); and transmitting the DCI to a User Equipment (UE) to configure the UE to communicate in a plurality of CCs according to the command or allocation information.

Certain aspects of the present disclosure also provide various apparatuses, components, and computer-readable media configured to perform (or cause a processor to perform) the operations described herein.

To the accomplishment of the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the above briefly summarized above may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

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

Fig. 2 is a block diagram illustrating an example logical architecture of a distributed Radio Access Network (RAN) in accordance with certain aspects of the present disclosure.

Fig. 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

Fig. 4 is a block diagram conceptually illustrating a design of an example Base Station (BS) and User Equipment (UE) in accordance with certain aspects of the present disclosure.

Fig. 5 is a block diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

Fig. 6 illustrates an example of a frame format for a New Radio (NR) system in accordance with certain aspects of the present disclosure.

Fig. 7 illustrates an example of dynamic resource set activation in accordance with certain aspects of the present disclosure.

Fig. 8 illustrates example operations for wireless communications by a user equipment in accordance with certain aspects of the present disclosure.

Fig. 9 illustrates example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure.

Fig. 10 illustrates an example Downlink Control Information (DCI) format in accordance with certain aspects of the present disclosure.

Fig. 11-14 illustrate examples of scheduling and search space activation for multiple Component Carriers (CCs) in accordance with certain aspects of the present disclosure.

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

Detailed Description

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for communicating order or allocation information for a plurality of Component Carriers (CCs).

The following description provides examples, but does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various programs or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined into some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Moreover, the scope of the disclosure is intended to cover apparatuses or methods practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the present disclosure may be embodied by one or more elements of a claim. 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.

The techniques described herein may be used for various wireless communication technologies such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and the like. UTRA encompasses wideband CDMA (wcdma) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDMA. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS).

New Radios (NR) are emerging wireless communication technologies developed with the 5G technology forum (5 GTF). 3GPP Long Term Evolution (LTE) and LTE-advanced (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A and GSM are described in documents from an organization named "third Generation partnership project" (3 GPP). cdma2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although aspects may be described herein using terms commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure may be applied in other generation-based communication systems, such as 5G and beyond, including NR technologies.

New Radio (NR) access (e.g., 5G technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidths (e.g., 80MHz or higher), millimeter wave (mmW) for high carrier frequencies (e.g., 25GHz or higher), massive Machine Type Communication (MTC) for non-backward compatible MTC technologies, and/or critical tasks for 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 may coexist in the same subframe.

Exemplary Wireless communication System

Fig. 1 illustrates an exemplary wireless communication network 100 in which aspects of the disclosure may be performed. For example, base station 120 may send DCI with commands or allocation information for multiple Component Carriers (CCs) to configure one or more UEs 120 to communicate in multiple CCs.

The wireless communication network 100 may be a New Radio (NR) or 5G network. As illustrated in fig. 1, wireless network 100 may include a plurality of Base Stations (BSs) 110 and other network entities. A BS may be a station that communicates with User Equipment (UE). Each BS 110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a Node B (NB) and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and next generation nodeb (gnb), new radio base station (NR BS), 5G NB, Access Point (AP) or Transmission Reception Point (TRP) may be interchanged. In some examples, the cells may not necessarily be fixed, and the geographic area of the cells may move according to the location of the mobile BS. In some examples, the base stations may be interconnected with each other and/or with one or more other base stations or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces: such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. Frequencies may also be referred to as carriers, subcarriers, frequency channels, tones (tones), subbands, and so on. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

A Base Station (BS) may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). The BS for the macro cell may be referred to as a macro BS. The BS for the pico cell may be referred to as a pico BS. The BS for the femto cell may be referred to as a femto BS or a home BS. In the example shown in fig. 1,

BSs

110a, 110b, and 110c may be macro BSs for

macro cells

102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102 x.

BSs

110y and 110z may be femto BSs for

femtocells

102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

The wireless communication network 100 may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of data and/or other information to a downstream station (e.g., a UE or a BS). The relay station may also be a UE that relays transmissions for other UEs. In the example shown in fig. 1, relay station 110r may communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120 r. The relay station may also be referred to as a relay BS, a relay, etc.

Wireless network 100 may be a heterogeneous network including different types of BSs, such as: macro BS, pico BS, femto BS, relay, etc. These different types of BSs may have different transmission power levels, different coverage areas, and different effects on interference in wireless network 100. For example, a macro BS may have a high transmission power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmission power level (e.g., 1 watt).

The wireless communication network 100 may support synchronous operation or asynchronous operation. For synchronous operation, BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, BSs may have different frame timings, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operations.

Network controller 120 may couple to a set of BSs and provide coordination and control for these BSs.

Network controller 130 may communicate with BS 110 via a backhaul. BSs 110 may also communicate with each other (e.g., directly or indirectly) via a wireless or wired backhaul.

UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, Customer Premises Equipment (CPE), a cellular phone, a smartphone, a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a cordless phone, a Wireless Local Loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smartwatch, a smart garment, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium . Some UEs may be considered Machine Type Communication (MTC) devices or evolved MTC (emtc) devices. MTC and eMTC UEs include, for example, a robot, drone, remote device, sensor, meter, monitor, location tag, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node may provide connectivity, e.g., for or to a network (e.g., a wide area network such as the internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered internet of things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

Some wireless networks, such as LTE, utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins (bins), and so on. Each subcarrier may be modulated with data. Typically, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing of the subcarriers may be 15kHz, and the minimum resource allocation (referred to as a "resource block" (RB)) may be 12 subcarriers (or 180 kHz). Thus, for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal Fast Fourier Transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into sub-bands. For example, a sub-band may cover 1.08MHz (i.e., 6 resource blocks), so that for a system bandwidth of 1.25, 2.5, 5, 10, or 20MHz, there may be 1, 2, 4, 8, or 16 sub-bands, respectively.

Although aspects of the examples described herein may be associated with LTE technology, aspects of the disclosure may be applicable to other wireless communication systems, such as NR. NR may utilize OFDM with CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configuration in DL may support up to 8 transmit antennas with up to 8 streams and up to 2 streams per UE for multi-layer DL transmission. Multi-layer transmission may be supported with up to 2 streams per UE. Aggregation of multiple cells with up to 8 serving cells may be supported.

In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication between some or all of the devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may serve as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, the UE may be used 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 the scheduling entity, the UEs may also communicate directly with each other.

In fig. 1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designed to serve the UE on the downlink and/or uplink. The thin dashed line with double arrows indicates the interfering transmission between the UE and the BS.

Fig. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN)200, which distributed radio access network 200 may be implemented in the wireless communication network 100 illustrated in fig. 1. The 5G access node 206 may include an Access Node Controller (ANC) 202. ANC 202 may be a Central Unit (CU) of distributed RAN 200. The backhaul interface to the next generation core network (NG-CN)204 may terminate at ANC 202. The backhaul interface to the neighboring next generation access node (NG-AN)210 may terminate at ANC 202. ANC 202 may include one or more Transmission Reception Points (TRPs) 208 (e.g., cells, BSs, gbss, etc.).

TRP 208 may be a Distributed Unit (DU). The TRP 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), AND service specific AND deployments, the TRP 208 may be connected to more than one ANC. TRPs 208 may each include one or more antenna ports. TRP 208 may be configured to serve traffic (traffic) for a UE individually (e.g., dynamic selection) or jointly (e.g., joint transmission).

The logical architecture of the distributed RAN 200 may support a fronthaul (frontaul) solution across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).

The logical architecture of the distributed RAN 200 may share features and/or components with LTE. For example, a next generation access node (NG-AN)210 may support dual connectivity with NRs and may share a common fronthaul for LTE and NRs.

The logical architecture of the distributed RAN 200 may allow cooperation between and within the TRPs 208, such as cooperation within the TRP and/or cooperation across the TRP via the ANC 202. The inter-TRP interface may not be used.

The logical functions may be dynamically distributed in the logical architecture of the distributed RAN 200. As will be described in more detail with reference to fig. 5, a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer may be appropriately placed at a DU (e.g., TRP 208) or a CU (e.g., ANC 202).

Fig. 3 illustrates an example physical architecture of a distributed Radio Access Network (RAN)300 in accordance with aspects of the present disclosure. A centralized core network unit (C-CU)302 may host core network functions. C-CUs 302 may be centrally deployed. To handle peak capacity, the C-CU 302 functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)).

A centralized RAN unit (C-RU)304 may host one or more ANC functions. Alternatively, C-RU 304 may host the core network functions locally. C-RU 304 may have a distributed deployment. The C-RU 304 may be near the edge of the network.

DU 306 may host one or more TRPs (edge node (EN), Edge Unit (EU), Radio Head (RH), Smart Radio Head (SRH), etc.). The DUs may be located at the edge of a network with Radio Frequency (RF) functionality.

Fig. 4 illustrates example components of BS 110 and UE 120 (shown in fig. 1) that may be used to implement aspects of the present disclosure. For example, antennas 452,

processors

466, 458, 464, and/or controller/processor 480 of UE 120, and/or antennas 434,

processors

420, 430, 438, and/or controller/processor 440 of BS 110 may be used to perform various techniques and methods described herein.

At BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be for the following: a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), a group common PDCCH (GC PDCCH), and the like. The data may be for a Physical Downlink Shared Channel (PDSCH), etc. Processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Processor 420 may also generate reference symbols, e.g., for Primary Synchronization Signals (PSS), Secondary Synchronization Signals (SSS), and cell-specific reference signals (CRS). A Transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to Modulators (MODs) 432a through 432 t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

At UE 120, antennas 452a through 452r may receive downlink signals from base station 110 and may provide received signals to demodulators (DEMODs) 454a through 454r, respectively, in the transceivers. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.

On the uplink, at UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a Physical Uplink Shared Channel (PUSCH)) and control information from a controller/processor 480 (e.g., for a Physical Uplink Control Channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal (e.g., for a Sounding Reference Signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r in the transceivers (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At BS 110, the uplink signals from UE 120 may be received by antennas 434, processed by modulators 432, detected by a MIMO detector 436, if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller/processor 440.

Controllers/

processors

440 and 480 may direct the operation at base station 110 and UE 120, respectively. Processor 440 and/or other processors and modules at BS 110 may perform or direct the performance of processes for the techniques described herein.

Memories

442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.

Fig. 5 illustrates a block diagram 500 showing an example for implementing a communication protocol stack in accordance with aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a wireless communication system, such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, the layers of the protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated (collocated) devices connected by a communication link, or various combinations thereof. The implementations of co-location and non-co-location may be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and/or DU) or UE.

A first option 505-a illustrates a split implementation of a protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., ANC 202 in fig. 2) and a distributed network access device (e.g., DU 208 in fig. 2). In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, while the RLC layer 520, the MAC layer 525 and the PHY layer 530 may be implemented by DUs. In various examples, the CU and DU may be co-located or non-co-located. The first option 505-a may be useful in a macrocell, microcell, or picocell deployment.

A second option 505-b illustrates a unified implementation of a protocol stack, wherein the protocol stack is implemented in a single network access device. In a second option, the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 may all be implemented by AN. The second option 505-b may be useful in, for example, a femtocell deployment.

Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530) as shown at 505-c.

In LTE, the basic Transmission Time Interval (TTI), or packet duration, is a 1ms subframe. In NR, the subframe is still 1ms, but the basic TTI is called a slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16 … time slots) depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15KHz and other subcarrier spacings may be defined relative to the base subcarrier spacing, e.g., 30KHz, 60KHz, 120KHz, 240KHz, etc. The symbol and slot lengths are proportional to the subcarrier spacing. The CP length also depends on the subcarrier spacing.

Fig. 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10ms) and may be divided into 10 subframes, each 1ms, with an index of 0 to 9. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing. The symbol periods in each slot may be assigned an index. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible direction) for data transmission, and the link direction for each subframe may be dynamically switched. The link direction may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information.

In NR, a Synchronization Signal (SS) block is transmitted. The SS block includes PSS, SSs, and two symbols PBCH. The SS blocks may be transmitted in fixed slot positions such as symbols 0-3 shown in fig. 6. The PSS and SSS may be used by the UE for cell search and acquisition. The PSS may provide half-frame timing and the SS may provide CP length and frame timing. The PSS and SSS may provide cell identification. The PBCH carries some basic system information such as downlink system bandwidth, timing information within a radio frame, SS burst set periodicity (SS burst set periodicity), system frame number, etc. SS blocks may be organized into SS bursts to support beam sweeping (beam sweeping). Further system information such as Remaining Minimum System Information (RMSI), System Information Blocks (SIBs), Other System Information (OSI) may be sent on the Physical Downlink Shared Channel (PDSCH) in certain subframes. SS blocks may be transmitted up to sixty-four times, e.g., up to sixty-four different beam directions for mmW. Up to sixty-four transmissions of an SS block is referred to as an SS burst set.

In some cases, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications for such sidelink communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, internet of everything (IoE) communications, IoT communications, mission critical networks, and/or various other suitable applications. In general, sidelink signals may refer to signals that are passed from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying such communications through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using licensed spectrum (different from wireless local area networks that typically use unlicensed spectrum).

The UE may operate in various radio resource configurations including configurations associated with transmitting pilots using a dedicated set of resources (e.g., a Radio Resource Control (RRC) dedicated state, etc.), or configurations associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a set of dedicated resources for transmitting pilot signals to the network. When operating in the RRC common state, the UE may select a set of common resources for transmitting pilot signals to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices, such as AN or DU or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on a set of common resources and also receive and measure pilot signals transmitted on a set of dedicated resources allocated to the UE if the network access device is a member of a monitoring set of network access devices for the UE. A CU receiving one or more of the network access devices, or a measurement to which the network access device(s) sent a pilot signal, may use the measurement to identify the serving cell of the UE, or initiate a change to the serving cell of one or more UEs.

A set of control resources (CORESET) for an OFDMA system (e.g., a communication system that transmits PDCCH using an OFDMA waveform) may include one or more sets of control resources (e.g., time and frequency resources) configured to communicate PDCCH within a system bandwidth. Within each CORESET, one or more search spaces (e.g., Common Search Spaces (CSSs), UE-specific search spaces (USSs), etc.) may be defined for a given UE. According to aspects of the present disclosure, CORESET is a set of time and frequency domain resources defined in units of Resource Element Groups (REGs). Each REG may include a fixed number (e.g., twelve) of tones in one symbol period (e.g., the symbol period of a slot), where one tone in one symbol period is referred to as a Resource Element (RE). A fixed number of REGs may be included in a Control Channel Element (CCE). The set of CCEs may be used to transmit a new radio PDCCH (NR-PDCCH), where different numbers of CCEs in the set used to transmit the NR-PDCCH use different aggregation levels. Multiple CCE sets may be defined as a search space of the UE, and thus, a NodeB or other base station may transmit NR-PDCCH to the UE by transmitting the NR-PDCCH in a CCE set defined as decoding candidates within the search space of the UE, and the UE may receive NR-PDCCH by searching in the search space of the UE and decode the NR-PDCCH transmitted by the NodeB.

Exemplary scheduling and search space activation for multiple CCs

Aspects of the present disclosure provide techniques for communicating order and/or allocation information for a plurality of Component Carriers (CCs). For example, a network entity (e.g., a gNB) may transmit Downlink Control Information (DCI) for scheduling transmissions and/or activating search spaces for a plurality of Component Carriers (CCs). In some cases, the DCI may carry commands for power adaptation in one or more of the multiple CCs (e.g., commands for the UE to adjust the transmission power for transmissions from the UE in the one or more of the multiple CCs).

In some cases, it may be beneficial to dynamically control the UE to monitor what search spaces. For example, for power saving operation of the UE, the BS may dynamically change and indicate the number of search space sets that the UE should monitor for control channel (PDCCH) decoding. Because control channel monitoring is associated with the number of blind decodes, reducing the number of CCs used for control channel monitoring may save the base band processing power of the UE.

Fig. 7 illustrates an example of dynamic search space control in accordance with certain aspects of the present disclosure. In the illustrated example, a Primary Component Carrier (PCC) may contain an anchor (anchor) search space set, while a Secondary Component Carrier (SCC) contains a non-anchor search space set. In some cases, the Scell search space set may be activated via MAC-CE, but initially the Scell contains only the inactive search space set.

Instead of activation via MAC-CE, DCI signaling may be preferred as a method of delivering search space set activation commands due to the shorter latency. Aspects of the present disclosure provide a format for DCI that may allow, for example, for communicating commands or allocation information for multicarrier scheduling and search space activation.

Fig. 8 illustrates example operations 800 for wireless communications by a UE in accordance with aspects of the present disclosure. Operation 800 may be performed, for example, by UE 120 of fig. 1, to receive, from a base station, an ongoing DCI conveying a command or allocation information for communicating in multiple CCs.

According to aspects, a UE may include one or more components as illustrated in fig. 4, which may be configured to perform the operations described herein. For example, the operations 800 of fig. 8 may be performed by the antenna 452, the demodulator/modulator 454, the controller/processor 480, and/or the memory 482 as illustrated in fig. 4.

The operations 800 begin at 802 by receiving Downlink Control Information (DCI) having one or more fields for activating search spaces in a plurality of Component Carriers (CCs). At 804, the UE monitors search spaces in the plurality of CCs for control channel transmissions.

Fig. 9 illustrates example operations 900 for wireless communications by a network entity (e.g., base station/gNB) in accordance with aspects of the present disclosure. Operation 900 may be performed, for example, by base station 110 of fig. 1 to configure UE 120 for communication in multiple CCs.

According to aspects, a BS may include one or more components as illustrated in fig. 4, which may be configured to perform the operations described herein. For example, the operations 900 of fig. 9 may be performed by the antenna 434, the demodulator/modulator 432, the controller/processor 440, and/or the memory 442 as illustrated in fig. 4.

Operations 900 begin at 902 by generating Downlink Control Information (DCI) having one or more fields for conveying commands or allocation information for a plurality of Component Carriers (CCs). At 904, the network entity sends the DCI to a User Equipment (UE) to configure the UE to communicate in the plurality of CCs according to the command or allocation information.

As described above, the BS may transmit DCI for multi-carrier scheduling, search space activation, and/or adaptation of transmission power in one of a corresponding plurality of carriers. For example, fig. 10 illustrates an example DCI format that may be defined to deliver commands and/or allocation information for multiple cells (carriers) simultaneously. The DCI format may be associated with a set of cells based on a configuration (e.g., sent via RRC signaling).

As illustrated in fig. 10, the type of DCI used to convey the command and/or allocation information (e.g., for multi-carrier scheduling, search space activation, and/or adaptation of transmission power in one of the corresponding multiple carriers) may contain one or more common information fields and one or more dedicated information fields. The common information field may carry information applicable to all associated cells. The dedicated information fields may carry information applicable only to the corresponding cell (e.g., each dedicated information field may be mapped to the corresponding cell).

The DCI may be used to deliver SS set activation (and/or transmission power) commands for other cells. For example, the proposed DCI may be transmitted within an anchor search space. The dedicated information field may contain an activation (or deactivation) command/status for the set of SSs in the other cell. Additionally or alternatively, the common information field may contain activation (or deactivation) commands/status for the entire set of search spaces in other cells.

There may be various types of activation use cases that may or may not also involve the same carrier (self-scheduling, which refers to scheduling in the same carrier as the carrier in which the DCI is transmitted) or cross-carrier scheduling, which refers to scheduling in a different carrier than the carrier in which the DCI is transmitted.

FIG. 11 illustrates one example option for a search space set activation command only. As illustrated, DCI sent in a primary CC (CC0) activates search spaces in multiple CCs (e.g., CC1-CC 7). In this example, DCI is used only for SS set activation, and scheduling grant (scheduling grant) for DL/UL data is not included in DCI.

After receiving this type of DCI, the UE may send feedback to the BS to make the determination. This search space may be used to convey PDCCH for scheduling DL/UL data in a cell after the set of SSs in the same cell is activated.

FIG. 12 illustrates another example option for a search space set activation command and self-scheduling. As in fig. 11, DCI sent in CC0 activates search spaces in multiple CCs. However, in this example, the DCI is used for both search space set activation and scheduling DL/UL data. In this example, since DL/UL data is scheduled in the same cell as the cell in which the DCI is transmitted, the scheduling is referred to as self-scheduling. In this case, HARQ feedback for the scheduled data may be considered as an acknowledgement from the UE to receive the search space set activation command.

Fig. 13 illustrates another example for a search space set activation command and multi-cell scheduling. As illustrated, in this case, the DCI is used for SS set activation and DL/UL data is scheduled in all cells for which the DCI activates an SS.

In some cases, the scheduling grant may be the same for all cells (and may be carried in a common information field). On the other hand, the scheduling grants may be different for all cells (and these grants may be carried in corresponding dedicated information fields). In this case, HARQ feedback for the scheduled data may be considered a determination from the UE to receive a search space set activation command.

As illustrated in fig. 14, DCI may also be used for search space set deactivation. For deactivation, similar DCI types and options as described above with reference to fig. 11-13 may be used. As illustrated, the DCI may deactivate SSs in CC1-CC7 while scheduling DL/UL data in CC 0.

The methods disclosed herein comprise one or more steps or actions for achieving the method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of the same elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other order of a, b, and c).

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

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The terms "a", "an", and "the" mean "one or more", unless specifically stated otherwise. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. Any claim element is not to be construed in accordance with the provisions of 35u.s.c. § 112(f), unless the element is explicitly recited using the phrase "means for … …", or in the case of method claims, the element is recited using the phrase "step for … …".

The various operations of the methods described above may be performed by any suitable means that can perform the corresponding functions. The components may include various hardware and/or software component(s) and/or module(s), including but not limited to a circuit, an Application Specific Integrated Circuit (ASIC), or a processor. Generally, where operations are illustrated in the figures, those operations may have corresponding means-plus-function components (means-plus-function components) with similar numbering.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of: a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description languages, or others. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and overall processing, including the execution of software modules stored on the machine-readable storage medium. A computer readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The machine-readable medium may include, for example, a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium separate from the wireless node having instructions stored thereon, all of which may be accessed by the processor through a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into a processor, such as may be the case with a cache and/or a general register file. Examples of a machine-readable storage medium 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, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

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

Also, any connection is properly termed a computer-readable medium. For example, if coaxial cable, fiber optic cable are usedCable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, microwave to transmit software from a website, server, or other remote source, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and

disks, where magnetic disks usually reproduce data magnetically, while optical disks reproduce data optically with lasers. Thus, in some aspects, computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). Further, for other aspects, the computer-readable medium may comprise a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

Accordingly, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such computer program products may include a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executed by one or more processors to perform the operations described herein. For example, the instructions are for performing the operations described herein and illustrated in fig. 8 and 9.

Further, it should be appreciated that modules and/or other suitable means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device may be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein may be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a Compact Disc (CD) or floppy disk, etc.), such that the user terminal and/or base station may obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device may be utilized.

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

Claims

1. A method of wireless communication by a User Equipment (UE), comprising:

receiving Downlink Control Information (DCI) having one or more fields for conveying commands or allocation information for a plurality of Component Carriers (CCs); and

taking at least one action related to the plurality of CCs according to the command or allocation information.

2. The method of claim 1, wherein:

the one or more fields convey a command to activate a search space in the plurality of CCs; and

taking the action includes monitoring a search space in the plurality of CCs for control channel information.

3. The method of claim 2, wherein the DCI further schedules one or more transmissions in at least one of the plurality of CCs.

4. The method of claim 3, wherein the DCI is received in a first cell and used to activate a search space in at least one other cell.

5. The method of claim 2, wherein the DCI comprises:

one or more common information fields for carrying information applicable to each of the plurality of CCs; and

one or more dedicated information fields for carrying information applicable only to a corresponding one of the plurality of CCs.

6. The method of claim 5, wherein at least one of the dedicated information fields indicates an activation or deactivation status of a set of search spaces in a corresponding cell.

7. The method of claim 5, wherein at least one of the common information fields indicates an activation or deactivation status of all search space sets in other cells.

8. The method of claim 2, wherein:

the DCI is used for search space set activation or deactivation and scheduling grant in a cell in which the DCI is transmitted.

9. The method of claim 8, further comprising sending feedback acknowledging the scheduled data, wherein the feedback also serves as an acknowledgement from the UE of the activation of the set of search spaces received via the DCI.

10. The method of claim 2, wherein:

the DCI is used for search space set activation or deactivation and scheduling grants in a plurality of cells in which the search space set is activated.

11. The method of claim 10, wherein the scheduling grant is the same for each of the plurality of cells.

12. The method of claim 10, wherein the scheduling grant is different for at least some of the plurality of cells.

13. The method of claim 10, sending feedback acknowledging the scheduled data, wherein the feedback also serves as an acknowledgement of receipt of the search space set activation via the DCI.

14. The method of claim 1, wherein:

the one or more fields convey a command to adjust a transmission power of transmissions in one or more of the plurality of CCs from the UE; and

taking the action comprises adjusting a transmission power of the transmission in accordance with the command.

15. A method of wireless communication by a network entity, comprising:

generating Downlink Control Information (DCI) having information for conveying commands or assignments for a plurality of Component Carriers (CCs); and

transmitting the DCI to a User Equipment (UE) to configure the UE to communicate in the plurality of CCs according to the command or allocation information.

16. The method of claim 15, wherein:

the one or more fields convey a command to activate a search space in the plurality of CCs.

17. The method of claim 16, wherein the DCI further schedules one or more transmissions in at least one of the plurality of CCs.

18. The method of claim 16, wherein the DCI is transmitted in a first cell and is used to activate a search space in at least one other cell.

19. The method of claim 16, wherein the DCI comprises:

20. The method of claim 19, wherein at least one of the dedicated information fields indicates an activation or deactivation status of a set of search spaces in a corresponding cell.

21. The method of claim 19, wherein at least one of the common information fields indicates an activation or deactivation status of all search space sets in other cells.

22. The method of claim 16, wherein:

23. The method of claim 22, considering feedback from the UE acknowledging the scheduled data as an acknowledgement from the UE of the activation of the set of search spaces received via the DCI.

24. The method of claim 16, wherein:

25. The method of claim 24, wherein the scheduling grant is the same for each of the plurality of cells.

26. The method of claim 24, wherein the scheduling grant is different for at least some of the plurality of cells.

27. The method of claim 24, considering feedback from the UE acknowledging the scheduled data as an acknowledgement from the UE of the activation of the set of search spaces received via the DCI.

28. The method of claim 15, wherein:

the one or more fields convey a command to adjust a transmission power of transmissions in one or more of the plurality of CCs from the UE.

29. An apparatus for wireless communications by a User Equipment (UE), comprising:

means for receiving Downlink Control Information (DCI) having one or more fields for conveying command or allocation information for a plurality of Component Carriers (CCs); and

means for taking at least one action related to the plurality of CCs according to the command or allocation information.

30. An apparatus for wireless communications by a network entity, comprising:

means for generating Downlink Control Information (DCI) having one or more fields for conveying command or allocation information for a plurality of Component Carriers (CCs); and

means for transmitting the DCI to a User Equipment (UE) to configure the UE to communicate in the plurality of CCs according to the command or allocation information.