Multi-carrier scheduling for downlink and uplink

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment can receive a configuration to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) for physical downlink shared channel (PDSCH) communications on each carrier included in a set of scheduled carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications on one or more carriers. The UE can monitor the one or more PDCCHs for the DCI according to the configuration. The UE can receive, based at least in part on the monitoring, the DCI scheduling the PUSCH communications on the one or more carriers. A number of other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This Patent Application claims priority to U.S. Provisional Patent Application No. 63 / 061,861, filed August 6, 2020, entitled “MULTI-COMPONENT CARRIER SCHEDULING FOR DOWNLINK AND UPLINK,” and U.S. Nonprovisional Patent Application No. 17 / 444,452, filed August 4, 2021, entitled “MULTI-CARRIER SCHEDULING FOR DOWNLINK AND UPLINK,” which are expressly incorporated by reference herein in their entirety. TECHNICAL FIELD

[0003] Aspects of the disclosure relate generally to wireless communications, and to techniques and apparatuses for multi-carrier scheduling for downlink and uplink communications. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include 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 Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A UE can communicate with a BS via the downlink and uplink. “Downlink” (or “forward link”) refers to the communication from the BS to the UE, and “uplink” (or “reverse link”) refers to the communication from the UE to the BS. As will be described in more detail, a BS can be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, and / or the like.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate on a municipal, national, regional, and even global level. NR, which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, using new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP- OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes receiving a configuration to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) for physical downlink shared channel (PDSCH) communications on each carrier included in a set of scheduled carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications on one or more carriers; monitoring the one or more PDCCHs for the DCI according to the configuration; and receiving the DCI scheduling the PUSCH communications on the one or more carriers based at least in part on the monitoring.

[0008] In some aspects, a method of wireless communication performed by a base station includes determining a configuration for a UE to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) for physical downlink shared channel (PDSCH) communications on each carrier included in a set of scheduled carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications on one or more carriers; transmitting the configuration to the UE; and transmitting one or more DCIs to the UE scheduling the PUSCH communications on the one or more carriers according to the configuration.

[0009] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory. For example, the one or more processors can be operatively, electronically, communicatively, or otherwise coupled to the memory. The memory can include instructions executable by the one or more processors to cause the UE to receive a configuration for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, monitor the one or more PDCCHs for DCI according to the configuration, and receive DCI scheduling PUSCH communications on the one or more carriers based at least in part on the monitoring.

[0010] In some aspects, a base station for wireless communication includes a memory and one or more processors coupled to the memory. For example, the one or more processors can be operatively, electronically, communicatively, or otherwise coupled to the memory. The memory can include instructions executable by the one or more processors to cause the base station to determine a configuration for a UE for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, transmit the configuration to the UE, and transmit one or more DCIs to the UE scheduling PUSCH communications on the one or more carriers according to the configuration.

[0011] In some aspects, a non-transitory computer-readable medium stores one or more instructions for wireless communication that, when executed by one or more processors of a UE, cause the UE to receive a configuration for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, monitor the one or more PDCCHs for DCI according to the configuration, and receive DCI scheduling PUSCH communications on the one or more carriers based at least in part on the monitoring.

[0012] In some aspects, a non-transitory computer-readable medium storing one or more instructions for wireless communication that, when executed by one or more processors of a base station, cause the base station to determine a configuration for a UE, the configuration being for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, transmit, to the UE, the configuration, and transmit, to the UE in accordance with the configuration, one or more DCIs scheduling PUSCH communications on the one or more carriers.

[0013] In some aspects, an apparatus for wireless communication includes means for receiving a configuration for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, means for monitoring the one or more PDCCHs for DCI in accordance with the configuration, and means for receiving, based at least in part on the monitoring, DCI scheduling PUSCH communications on the one or more carriers.

[0014] In some aspects, an apparatus for wireless communication includes means for determining a configuration for a UE, the configuration being for monitoring one or more PDCCHs for DCI for PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, means for transmitting, to the UE, the configuration, and means for transmitting, to the UE in accordance with the configuration, one or more DCIs scheduling PUSCH communications on the one or more carriers.

[0015] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0016] So that the manner in which the above-recited features and advantages of the disclosed examples can be understood in detail, a brief description of a specific implementation is summarized above. Additional features and advantages will be disclosed in the following detailed description of the application, which is understood to form a part of this specification. The disclosed concept and specific examples can be readily utilized as bases upon which the other structures can be

[0017] While various aspects of the disclosure are illustrated by description of some examples in the present disclosure, it will be understood by those skilled in the art that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments, or other non-module- component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of the claimed and described aspects. For example, transmission and reception of wireless signals can include a number of components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or adders). It is intended that aspects described herein can be practiced in a wide variety of different devices, components, systems, distributed arrangements, or end-user devices of varying size, shape, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0018] For a more complete understanding of the above-described features of the present disclosure, reference is made to the detailed description being taken in connection with the accompanying drawings in which certain typical aspects are shown by way of illustration. It is to be noted, however, that the drawings are merely schematic and that they are not to be construed as limiting the scope of the disclosure as described herein. Like references in different drawings can identify the same or similar elements.

[0019] Figure 1 FIG. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 FIG. 2 is a diagram illustrating an example of a base station in communication with a UE in a wireless network, in accordance with the present disclosure.

[0021] Figure 3 FIG. 3 is a diagram of an example resource structure for wireless communication, in accordance with the present disclosure.

[0022] Figure 4 FIG. 4 is a diagram illustrating an example of carrier aggregation, in accordance with the present disclosure.

[0023] Figures 5-8 FIG. 5 is a diagram illustrating a graph associated with multi-carrier scheduling for downlink and uplink communications, in accordance with the present disclosure.

[0024] Figures 9-10FIG. 1 is a diagram illustrating an example of a wireless communications system that supports multi-carrier scheduling for downlink and uplink communications in accordance with aspects of the present disclosure.

[0025] Figures 11-12 FIG. 1 is a diagram illustrating an example of a wireless communications system that supports multi-carrier scheduling for downlink and uplink communications in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0026] Various aspects of the disclosure are more fully described herein with reference to the figures. However, the disclosure can be implemented in various different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of, or combined with, any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using, in addition to or in place of the techniques explicitly disclosed herein, any of the other techniques disclosed throughout this document. It should be understood that any of the aspects disclosed herein can be embodied by one or more elements of a claim.

[0027] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0028] It should be noted that while aspects can be described using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0029] Figure 1is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 can be or include elements of a 5G (NR) network and / or an LTE network, among other examples. The wireless network 100 can include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and can also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), or the like. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0030] BSs can be referred to as macro BS, small cell BS, a femtocell BS, a pico BS, or the like. A BS can be located in a home, a small business, an enterprise business, a local area network (LAN), or the like. A BS can be configured to provide service to a limited (e.g., home) or large area. In some aspects, a BS can be configured to communicate with a UE using one or more components of 5G NR, LTE, Wi-Fi, or the like. In some aspects, the wireless network 100 can include one or more devices configured to operate as an IAB node, an IAB donor, an IAB relay, an IAB child, or the like. Figure 1 In the example shown, the BS 110a can be a macro BS for the macro cell 102a; the BS 110b can be a small cell BS for the small cell 102b; and BS 110c can be a small cell BS for the small cell 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0031] In some aspects, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile BS. In some aspects, a BS can be interconnected to one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transmission network, such as a direct physical connection or a virtual network.

[0032] The wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs.Figure 1 In the illustrated example, the relay BS 1 lOd can communicate with the macro BS 110a and the UE 120d in order to facilitate communication between the BS 110a and the UE 120d. A relay BS can also be referred to as a relay station, a relay base station, a relay, or the like.

[0033] Wireless network 100 can be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 Watts), whereas pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 Watts).

[0034] A network controller 130 can couple to a set of BSs and can provide coordination and control for these BSs. Network controller 130 can be

[0035] UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like. A UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0036] Some UEs can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, e.g., robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet-of-Things (IoT) devices, and / or can be implemented as NB-IoT (narrowband internet of things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included in a housing that houses components of UE 120 such as processor components and / or memory components. In some aspects, the processor components and the memory components can be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0037] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, and / or the like. Frequencies can also be referred to as carriers, frequency channels, and / or the like. Each frequency can 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 can be deployed.

[0038] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein. In this case, the communication link between UEs 120 can be called a sidelink

[0039] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided, based on frequency or wavelength, into various classes, bands, channels, and / or the like. For example, devices of wireless network 100 can communicate using an operating band having a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz; and / or can communicate using an operating band having a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” frequency band. Similarly, FR2 is often referred to as a “millimeter wave” frequency band despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is also referred to as a “millimeter wave” band by the International Telecommunications Union (ITU). Thus, unless specifically stated otherwise, the term “sub-6 GHz” or the like means frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz), as appropriate. Similarly, unless specifically stated otherwise, the term “millimeter wave” or the like means frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz), as appropriate. It is contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0040] As described above, there is provided Figure 1 by way of example. Other examples can differ from that described. Figure 1 described examples.

[0041] Figure 2 FIG. 1 is a diagram illustrating an example 100 of a wireless network, in accordance with the present disclosure. The wireless network (e.g., the 5G network) includes a number of base stations 110 (e.g., gNBs) and other network entities. An access network 100 can include one or more base stations 110, each simultaneously supporting communication for multiple user equipment devices, such as user equipment devices 120. A base station can communicate with the core network 130, e.g., via one or more interfaces. Each of the base stations 110 can provide communication coverage for a respective geographic area 110a, 110b, and 110c. A base station can

[0042] At base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively.

[0043] At the UE 120, the antennas 252a-252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, receive signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or channel quality indicator (CQI) parameters, among other examples. In some aspects, one or more components of UE 120 can be included in a housing.

[0044] The network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0045] Antennas (e.g., antennas 234a-234t and / or antennas 252a-252r) can be included in or can encompass antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among other examples. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays can include one or more antenna elements. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays can include sets of co-planar antenna elements and / or sets of non-co-planar antenna elements. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays can include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays can include one or more antenna elements coupled to one or more transmit and / or receive components, such as one or more components of Figure 2

[0046] ​On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 254) of the UE 120 can be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modulators and / or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, with reference to Figures 5-10 described).

[0047] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. Base station 110 can include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 can include a scheduler 246 to schedule UEs 120 for downlink and / or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 232) of the base station 110 can be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver can include any combination of antenna 234, modulators and / or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, with reference to Figures 5-10 described).

[0048] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or any other component(s) of Fig. 2 can perform one or more techniques described herein to determine a set of resources for a UE to use for a transmission.Figure 2 Any other components may perform one or more techniques associated with multi-carrier scheduling for downlink and uplink communication. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 9 The process 900 Figure 10 The process 1000 operates and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 9 The process 900 Figure 10 The operation of process 1000 and / or other processes as described herein. In some aspects, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0049] In some aspects, UE 120 may include: a unit for monitoring one or more physical downlink control channels (PDCCHs) by receiving downlink control information (DCI) for physical downlink shared channel (PDSCH) communication on each carrier included in the set of scheduled carriers and DCI for physical uplink shared channel (PUSCH) communication on one or more carriers; a unit for monitoring one or more PDCCHs according to the configuration of the DCI; a unit for receiving DCI for scheduling PUSCH communication on one or more carriers at least in part based on monitoring, and so on. In some aspects, such a unit may include a combination of Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0050] In some aspects, base station 110 can include means for determining a configuration for the UE, the configuration being for monitoring one or more PDCCHs for DCI scheduling PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers, means for transmitting, to the UE, the configuration, means for transmitting, to the UE in accordance with the configuration, one or more DCIs scheduling PUSCH communications on one or more carriers, and / or the like. In some aspects, such means can include one or more components of base station 110 described in connection with FIG. 2, such as antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, and / or the like. Figure 2 One or more components of the base station 110 described above, such as antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, and / or the like.

[0051] Although Figure 2 the blocks in FIG. 14 are illustrated in a particular order, this order is an example and the functionality of the blocks can be implemented in a different order.

[0052] As described above, provide Figure 2 as examples. Other examples can differ from what is described in Figure 2 connection with FIG. 14.

[0053] Figure 3 is a diagram of an example resource structure 300 for wireless communication in accordance with the present disclosure. The resource structure 300 illustrates examples of various resource groups described herein. As shown, the resource structure 300 can include subframes 305. The subframes 305 can include a number of slots 310. Although the resource structure 300 is shown including 2 slots per subframe, a different number of slots (e.g., 4 slots, 8 slots, 16 slots, 32 slots, etc.) can be included in a subframe. In some aspects, different types of transmission time intervals (TTIs) can be used in addition to or instead of subframes and / or slots. The slots 310 can include a number of symbols 315, such as 7 symbols or 14 symbols per slot.

[0054] The potential control region of the slot 310 can be referred to as a control resource set (CORESET) 320 and can be structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources of the CORESET 320 for one or more PDCCH, one or more PDSCH, and / or the like. In some aspects, the CORESET 320 can occupy the first symbol 315 of the slot 310, the first two symbols 315 of the slot 310, or the first three symbols 315 of the slot 310. Thus, the CORESET 320 can include a number of resource blocks (RBs) in the frequency domain, and one, two, or three symbols 315 in the time domain. In 5G, the number of resources included in the CORESET 320 can be flexibly configured, such as by using radio resource control (RRC) signaling to indicate a frequency domain region (e.g., number of resource blocks) and / or a time domain region (e.g., number of symbols) for the CORESET 320.

[0055] As shown, the symbol 315 including the CORESET 320 can include one or more control channel elements (CCEs) 325, shown as two CCEs 325 as an example, spanning a portion of the system bandwidth. The CCEs 325 can include downlink control information (DCI) to provide control information for wireless communications. The base station can transmit the DCI during a number of CCEs 325 (as shown), where the number of CCEs 325 used to transmit the DCI represents an aggregation level (AL) used by the BS to transmit the DCI. In Figure 3 As an example, an aggregation level of 2 is shown, corresponding to two CCEs 325 in the slot 310. In some aspects, different aggregation levels can be used, such as 1, 4, 8, 16, and / or the like.

[0056] Each CCE 325 can include a fixed number of resource element groups (REGs) 330, shown as four REGs 330, or can include a variable number of REGs 330. In some aspects, the number of REGs 330 included in the CCE 325 can be specified by a REG bundling size. The REGs 330 can include one resource block, which can include 12 resource elements (REs) 335 within a symbol 315. The resource elements 335 can occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0057] A search space can include all possible locations (e.g., in time and / or frequency) where a PDCCH can be located. A CORESET 320 can include one or more search spaces, such as a UE-specific search space, a group common search space, and / or a common search space. A search space can indicate a set of CCE locations where a UE can find a PDCCH that can potentially be used to transmit control information to the UE. The possible locations of a PDCCH can depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group common PDCCH (e.g., for multiple UEs), the aggregation level being used, and / or the like. The possible locations (e.g., in time and / or frequency) of a PDCCH can be referred to as a PDCCH candidate, and the set of all possible PDCCH locations can be referred to as a search space. For example, the set of all possible PDCCH locations for a particular UE can be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations across all UEs can be referred to as a common search space. The set of all possible PDCCH locations for a particular group of UEs can be referred to as a group common search space.

[0058] A CORESET 320 can be interleaved or non-interleaved. An interleaved CORESET 320 can have a mapping of CCEs to REGs such that adjacent CCEs are mapped to dispersed REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to consecutive REG bundles of the CORESET 320). A non-interleaved CORESET 320 can have a mapping of CCEs to REGs such that all CCEs are mapped to consecutive REG bundles of the CORESET 320 (e.g., in the frequency domain).

[0059] As described above, providing Figure 3 by way of example. Other examples can differ from those described Figure 3 without departing from the spirit of the described examples.

[0060] Figure 4 FIG. 4 is a diagram illustrating an example 400 of carrier aggregation, in accordance with the present disclosure.

[0061] Carrier aggregation is a technique that enables two or more component carriers (CCs), which can be referred to as carriers, to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. A “carrier” can include and / or can be referred to as a “component carrier.” For example, “carrier” and “component carrier” can be used interchangeably herein. As illustrated, carriers can be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers can be combined. A base station 110 can configure a UE 120 with carrier aggregation, e.g., in a radio resource control (RRC) message, a DCI message, and / or the like.

[0062] As shown by reference number 405, in some aspects, carrier aggregation can be configured as an intra-band contiguous mode, in which the aggregated carriers are contiguous to each other and in the same frequency band. As shown by reference number 410, in some aspects, carrier aggregation can be configured as an intra-band non-contiguous mode, in which the aggregated carriers are non-contiguous to each other and in the same frequency band. In some aspects, the aggregated carriers in the same frequency band (e.g., contiguous and non-contiguous) can use the same subcarrier spacing (SCS). As shown by reference number 415, in some aspects, carrier aggregation can be configured as an inter-band non-contiguous mode, in which the aggregated carriers are non-contiguous to each other and in different frequency bands. In some aspects, the aggregated carriers in different frequency bands can use different SCSs.

[0063] In carrier aggregation, a UE 120 can be configured with a primary carrier and one or more secondary carriers. In some aspects, the primary carrier can carry control information (e.g., downlink control information, scheduling information, and / or the like) for scheduling data communications on one or more secondary carriers, which can be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) can carry control information for scheduling data communications on the carrier, which can be referred to as self-carrier scheduling or carrier self-scheduling.

[0064] As described above, provide Figure 4 by way of example. Other examples can differ from that described. Figure 4 described examples.

[0065] Carrier aggregation provides a mechanism for cross-carrier scheduling, in which a single carrier can schedule communications on multiple carriers (e.g., multi-carrier scheduling). In some aspects, in addition to scheduling PDSCH or PUSCH on a serving cell or not scheduling PDSCH or PUSCH on a serving cell, a PDCCH of the serving cell can carry DCI that schedules communications (e.g., physical downlink shared channel (PDSCH) communications or physical uplink shared channel (PUSCH) communications) on another serving cell. For example, a PDCCH of a secondary cell (SCell) can schedule communications on a primary cell (PCell) or a primary secondary cell (PSCell). As another example, a PDCCH of a serving cell (e.g., a PCell, a PSCell, or a SCell) can schedule PDSCH on multiple cells (e.g., multiple carriers) using a single DCI. Additionally, when a UE is configured to support carrier aggregation, a PDCCH can schedule communications on each aggregated carrier using a single DCI. In some aspects, a UE can be configured for multi-carrier scheduling of downlink communications (e.g., PDSCH communications). However, scheduling multiple carriers using a single DCI for downlink communications while also scheduling uplink communications (e.g., PUSCH communications) can increase the size of the DCI and increase the blind decoding complexity of the PDCCH, which offsets some of the benefits of multi-carrier scheduling and uses a large amount of computational and communication resources of the UE.

[0066] Some techniques and apparatuses described herein implement multi-carrier scheduling for downlink and uplink communications. For example, a UE can be configured with multi-carrier scheduling for PDSCH communications. The configuration can indicate that the UE is to use multi-carrier scheduling for PUSCH communications, is to use self-scheduling for PUSCH communications, is to use cross-scheduling for PUSCH communications, and / or the like. For example, in cases where a set of carriers for downlink communications (e.g., a set of carriers) is the same as a set of carriers for uplink communications (e.g., a set of carriers), a UE can be configured with multi-carrier scheduling for both PDSCH communications and PUSCH communications (e.g., using the same set of PDCCH candidates or a different set of PDCCH candidates). In some aspects, a UE can be configured with multi-carrier scheduling for PDSCH communications and single-carrier and self-carrier scheduling for PUSCH communications (e.g., each cell can schedule PDSCH communications for the cell). In some aspects, a UE can be configured with multi-carrier scheduling for PDSCH communications and single-carrier and cross-carrier scheduling for PUSCH communications (e.g., a single cell can schedule PDSCH communications for the cell and one or more other cells on a single carrier basis).

[0067] Accordingly, the UE is able to utilize multi-carrier scheduling for PDSCH communications, while also enabling the UE to schedule PUSCH communications (e.g., using multi-carrier scheduling or single-carrier scheduling) without increasing the DCI size or blind decoding complexity of PDCCHs as the UE is configured to use multi-carrier scheduling DCI for PUSCH communications or single-carrier scheduling DCI for PUSCH communications.

[0068] Figure 5 is a diagram illustrating an example 500 associated with multi-carrier scheduling for downlink and uplink communications, in accordance with the present disclosure. As shown, the example 500 includes communications between a base station 110 and a UE 120. In some aspects, the base station 110 and the UE 120 can be included in a wireless network, such as the wireless network 100. The base station 110 and the UE 120 can communicate on a wireless access link, which can include uplink and downlink. Figure 5

[0069] In some aspects, the UE 120 can communicate with one or more base stations 110. For example, the UE 120 can operate in a dual connectivity mode (e.g., an evolved universal mobile telecommunications system terrestrial radio access (E-UTRA)-NR dual connectivity (ENDC) mode, an NR-E-UTRA dual connectivity (NEDC) mode, an NR dual connectivity (NRDC) mode, or other dual connectivity mode). For example, the UE 120 can communicate with a first base station 110 associated with a first serving cell (e.g., a master cell group, a secondary cell group, a PCell, a PSCell, a Scell, etc.). The UE 120 can communicate with a second base station 110 associated with a second serving cell (e.g., a master cell group, a secondary cell group, a PCell, a PSCell, a Scell, etc.).

[0070] As shown by reference number 505, the base station 110 can determine a configuration for the UE 120 to monitor one or more PDCCHs for DCI scheduling PDSCH communications on carriers included in a set of carriers and DCI scheduling PUSCH communications on one or more carriers (e.g., either included in the set of carriers or different carriers).

[0071] ​In some aspects, the set of carriers can be associated with a set of serving cells serving the UE 120. For example, the UE 120 can be served by three serving cells (e.g., a first serving cell, a second serving cell, and a third serving cell). Each serving cell can be associated with a carrier (e.g., the first serving cell can be associated with CC1, the second serving cell can be associated with CC2, and the third serving cell can be associated with CC3). A set of carriers can include CC1 and CC2, another set of carriers can include CC1 and CC3, another set of carriers can include CC2 and CC3, another set of carriers can include CC1, CC2, and CC3, and so on. Thus, as referred to herein, “multi-carrier scheduling” can refer to multi-cell scheduling (e.g., in which a single DCI schedules communications on multiple serving cells of the UE 120).

[0072] The base station 110 can determine a set of PDCCH candidates for DCI scheduling PDSCH communications on each carrier included in the set of carriers (e.g., DCI capable of multi-carrier scheduling for PDSCH), and one or more other sets of PDCCH candidates for DCI scheduling PDSCH communications on one or more other sets of carriers. In some aspects, the set of PDCCH candidates for DCI scheduling PDSCH communications on multiple carriers and the set of PDCCH candidates for DCI scheduling PUSCH communications are the same set of PDCCH candidates. In some aspects, the set of PDCCH candidates for DCI scheduling PDSCH communications on multiple carriers and the set of PDCCH candidates for DCI scheduling PUSCH communications are different sets of PDCCH candidates.

[0073] The base station 110 can determine a configuration for DCI utilizing multi-carrier scheduling for PDSCH. In some aspects, the base station 110 can determine that a set of carriers is associated with a set of PDCCH candidates for DCI scheduling PDSCH communications on the set of carriers. The base station 110 can determine a configuration for the set of PDCCH candidates, the configuration including a search space configuration, a carrier indicator field (CIF), a payload size associated with DCI transmitted using the set of PDCCH candidates, a DCI format transmitted using the set of PDCCH candidates, and / or the like.

[0074] In some aspects, the base station 110 can determine a configuration for a plurality of sets of PDCCH candidates. For example, the base station 110 can transmit DCI using a first set of PDCCH candidates (according to a first configuration) to schedule PDSCH communications on a first set of carriers. The base station 110 can transmit DCI using a second set of PDCCH candidates (according to a second configuration) to schedule PDSCH communications on a second set of carriers. In this way, the UE 120 can be able to distinguish between DCI scheduling PDSCH communications on the first set of carriers and DCI scheduling PDSCH communications on the second set of carriers.

[0075] The base station 110 can determine a set of PDCCH candidates for DCI scheduling PUSCH communications on one or more carriers. In some aspects, if the UE 120 supports uplink carrier aggregation such that the uplink carriers of the UE 120 are the same carriers as the downlink carriers of the UE 120 (e.g., a set of carriers are used for both uplink and downlink communications), the set of PDCCH candidates for DCI scheduling PUSCH communications at the UE 120 can be the same as the set of PDCCH candidates for DCI scheduling PDSCH communications on a plurality of carriers (e.g., on a set of carriers). That is, the configuration can indicate that PUSCH communications on a set of carriers are to be scheduled by DCI capable of multi-carrier uplink scheduling (e.g., where a single DCI communication schedules multiple PUSCH communications on each carrier included in the set of carriers). The PDCCH supporting multi-carrier scheduling for both uplink and downlink communications is depicted and described in greater detail below with respect to Figure 6 The PDCCH supporting multi-carrier scheduling for both uplink and downlink communications is depicted and described in greater detail below with respect to

[0076] As described above, when the UE 120 is capable of supporting multi-carrier scheduling for downlink and uplink communications (e.g., in cases where the UE 120 supports uplink carrier aggregation), the base station 110 can determine a single set of PDCCH candidates for transmitting DCI to the UE 120. The base station 110 can determine a search space configuration for the set of PDCCH candidates. In some aspects, the base station 110 can indicate a DCI payload size for downlink DCI and a DCI payload size for uplink DCI (e.g., to enable the UE 120 to distinguish between DCI for scheduling PDSCH communications on a set of carriers and DCI for scheduling PUSCH communications on a set of carriers).

[0077] In some aspects, a DCI payload size of the downlink DCI can be the same as a payload size of the uplink DCI. In that case, the base station 110 can determine that a field in the DCI is to be used to distinguish between the downlink DCI and the uplink DCI. For example, the configuration can indicate that the identifier is to be used by the UE 120 to distinguish between the downlink DCI and the uplink DCI. If the base station 110 transmits the DCI to schedule PDSCH communications on multiple carriers (e.g., a set of carriers), the DCI is to include the identifier associated with the downlink DCI. If the base station 110 transmits the DCI to schedule PUSCH communications on multiple carriers (e.g., a set of carriers), the DCI is to include the identifier associated with the uplink DCI.

[0078] In some aspects, when the UE 120 is capable of supporting multi-carrier scheduling for downlink communications and uplink communications (e.g., in a case that the UE 120 supports uplink carrier aggregation), the base station 110 can determine a first set of PDCCH candidates for downlink DCI and a second set of PDCCH candidates for uplink DCI. The base station 110 can determine a first search space configuration for the first set of PDCCH candidates and a second search space configuration for the second set of PDCCH candidates.

[0079] In some aspects, if the base station 110 determines that the UE 120 does not support uplink carrier aggregation or if the base station 110 determines that an uplink carrier for the UE 120 is different from a downlink carrier for the UE 120, the base station 110 can determine that the UE 120 is to be configured with single-carrier scheduling DCI for PUSCH communications. For example, the base station 110 can determine that PUSCH scheduling for the UE 120 is to be performed using a DCI format for scheduling PUSCH communications on a single carrier (e.g., DCI format 0 0, 0 1, 0 2, etc.). The configuration can indicate a set of PDCCH candidates for each uplink carrier for the UE 120. In some aspects, the base station 110 can determine a configuration (e.g., a search space configuration, a CIF value, a DCI payload size, etc.) for each set of PDCCH candidates for each uplink carrier for the UE 120.

[0080] In some aspects, the base station 110 can determine that downlink data is to be scheduled at the UE 120 using multi-carrier scheduling (e.g., using a single DCI to schedule PDSCH communications on multiple carriers) and that uplink data is to be scheduled at the UE 120 using single-carrier scheduling. In some aspects, the single-carrier scheduling can be self-carrier scheduling. “Self-carrier scheduling” can refer to transmitting a DCI on a PDCCH associated with a carrier (or serving cell) on which a PUSCH communication is to be scheduled. The base station 110 can determine a set of PDCCH candidates for a DCI scheduling downlink data on multiple carriers, and a set of PDCCH candidates for a DCI scheduling uplink data on a carrier associated with the base station 110 (e.g., on a serving cell associated with the base station 110). In some aspects, another base station 110 can determine a set of PDCCH candidates for a DCI scheduling uplink data on a carrier associated with the other base station 110 (e.g., on another serving cell associated with the other base station 110). The following is directed to Figure 7 PDCCHs supporting multi-carrier scheduling for downlink data and single-carrier / self-carrier scheduling for uplink data are depicted and described in further detail.

[0081] In some aspects, the single-carrier scheduling can be cross-carrier scheduling. “Cross-carrier scheduling” can refer to transmitting a DCI on a PDCCH associated with a scheduling carrier. That is, the UE 120 is configured to monitor a scheduling carrier for a DCI scheduling a PUSCH communication in a single-carrier manner (e.g., on the scheduling carrier or on another carrier). In some aspects, the base station 110 can determine a set of PDCCH candidates associated with each uplink carrier (e.g., the base station 110 can determine a set of PDCCH candidates for a DCI scheduling uplink data on a first carrier, a set of PDCCH candidates for a DCI scheduling uplink data on a second carrier, and so on). In some aspects, the base station 110 can determine a CIF value associated with each set of PDCCH candidates associated with a DCI scheduling uplink data. The following is directed to Figure 8 PDCCHs supporting multi-carrier scheduling for downlink data and single-carrier / cross-carrier scheduling for uplink data are depicted and described in further detail.

[0082] In some aspects, when the base station 110 determines that downlink data is to be scheduled using multi-carrier scheduling and uplink data is to be scheduled using single-carrier scheduling, the UE 120 can be configured to monitor for downlink DCI and uplink DCI on the same carrier (e.g., on the same serving cell, etc.). In some aspects, a set of PDCCH candidates for DCI scheduling downlink data in a multi-carrier manner can be the same as a set of PDCCH candidates for DCI scheduling uplink data in a single-carrier manner. For example, the base station 110 can determine a search space configuration for the set of PDCCH candidates.

[0083] In some aspects, the configuration can indicate that the UE 120 is to differentiate between downlink DCI (scheduling downlink data in a multi-carrier manner) and uplink DCI (scheduling uplink data in a single-carrier manner) based at least in part on a payload size of the DCI. In some aspects, if the payload size of the downlink DCI is the same as the payload size of the uplink DCI, the configuration can indicate that the UE 120 is to differentiate between the downlink DCI and the uplink DCI based at least in part on an identifier indicated in the DCI. For example, an identifier in the DCI can indicate that the DCI is scheduling downlink data. Similarly, an identifier in the DCI can indicate that the DCI is scheduling uplink data.

[0084] In some aspects, a set of PDCCH candidates for DCI scheduling downlink data in a multi-carrier manner can be different than a set of PDCCH candidates for DCI scheduling uplink data in a single-carrier manner. For example, the base station 110 can determine a first search space configuration for a first set of PDCCH candidates of DCI scheduling downlink data in a multi-carrier manner and a second search space configuration for a second set of PDCCH candidates of DCI scheduling uplink data in a single-carrier manner. In some aspects, the base station 110 can determine that each set of PDCCH candidates is associated with a different CIF value. For example, if the UE 120 is associated with two carriers (e.g., CC1 and CC2), the base station 110 can determine that a set of PDCCH candidates for scheduling uplink data on CC1 (e.g., in a single-carrier manner) is associated with a first CIF value, a set of PDCCH candidates for scheduling uplink data on CC2 (e.g., in a single-carrier manner) is associated with a second CIF value, and a set of PDCCH candidates for scheduling downlink data on CC1 and CC2 (e.g., in a multi-carrier manner) is associated with a third CIF value.

[0085] As shown by reference number 510, the base station 110 can transmit a configuration for PDCCH monitoring to the UE 120. The base station 110 can transmit the configuration using upper layer (or higher layer) signaling. For example, the base station 110 can transmit the configuration using RRC signaling. In some aspects, other types of signaling can be used to transmit the configuration, such as medium access control (MAC) signaling, DCI signaling, and / or the like. The UE 120 can receive the configuration from the base station 110 and identify the configuration and one or more sets of PDCCH candidates to monitor. In some aspects, the UE 120 can receive a first configuration from a first base station 110 (e.g., identifying a configuration for monitoring PDCCHs associated with the first base station 110) and can receive a second configuration from a second base station 110 (e.g., identifying a configuration for monitoring PDCCHs associated with the second base station 110).

[0086] As shown by reference number 515, the UE 120 can monitor one or more PDCCHs for DCI in accordance with the configuration. For example, the UE 120 can monitor a PDCCH (e.g., monitor a set of PDCCH candidates) for DCI scheduling PDSCH communications on multiple carriers associated with the UE 120. In some aspects, when the configuration indicates that multi-carrier scheduling is to be used for uplink data, the UE 120 can monitor a PDCCH (e.g., monitor a set of PDCCH candidates) for DCI scheduling PUSCH communications on multiple carriers associated with the UE 120.

[0087] In some aspects, the UE 120 can monitor a first set of PDCCH candidates for DCI scheduling PDSCH communications on multiple carriers associated with the UE 120 and a second set of PDCCH candidates for DCI scheduling PUSCH communications on multiple carriers associated with the UE 120. For example, the UE 120 can monitor the first set of PDCCH candidates in a first search space configured by a first search space configuration for DCI scheduling PDSCH communications on each of a set of carriers associated with the UE 120. The UE 120 can monitor the second set of PDCCH candidates in a second search space configured by a second search space configuration for DCI scheduling PUSCH communications on each of the set of carriers.

[0088] In some aspects, when the configuration indicates that single-carrier scheduling is to be used for uplink data, UE 120 can monitor for DCI on each uplink carrier associated with UE 120 or on a scheduling carrier associated with UE 120. In some aspects, UE 120 can monitor a plurality of sets of PDCCH candidates for DCI scheduling uplink data on uplink carriers of UE 120 (e.g., can monitor a first set of PDCCH candidates for DCI scheduling uplink data on a first uplink carrier, can monitor a second set of PDCCH candidates for DCI scheduling uplink data on a second uplink carrier, and so on).

[0089] As shown by reference number 520, base station 110 can transmit, and UE 120 can receive, DCI scheduling downlink data in a multi-carrier manner and / or DCI scheduling uplink data (e.g., in a multi-carrier manner or in a single-carrier manner). The DCI can schedule downlink communications on multiple carriers of UE 120. In some aspects, the DCI can schedule uplink communications on multiple carriers of UE 120. In some aspects, the DCI can schedule uplink communications on a single carrier of UE 120.

[0090] For example, UE 120 can receive the DCI and determine (e.g., based at least in part on a configuration, an identifier included in the DCI, a search space in which the DCI is transmitted, a set of PDCCH candidates used to transmit the DCI, a payload size of the DCI, a format type of the DCI, and / or the like) that the DCI is a downlink DCI scheduling PDSCH communications on multiple carriers of UE 120. UE 120 can reserve resources indicated by the DCI for the PDSCH communications on each of the multiple carriers. In some aspects, UE 120 can receive the DCI and determine (e.g., based at least in part on a configuration, an identifier included in the DCI, a search space in which the DCI is transmitted, a set of PDCCH candidates used to transmit the DCI, a payload size of the DCI, a format type of the DCI, and / or the like) that the DCI is an uplink DCI scheduling one or more PUSCH communications. UE 120 can determine that the DCI is a multi-carrier scheduling DCI and can schedule PUSCH communications on multiple carriers. UE 120 can determine that the DCI is a single-carrier scheduling DCI and can schedule PUSCH communications on a single carrier.

[0091] As shown by reference number 525, the base station 110 (or base stations 110) and the UE 120 can perform scheduled PDSCH communications and / or scheduled PUSCH communications. For example, the UE 120 can receive a first PDSCH communication on a first carrier and a second PDSCH communication on a second carrier (e.g., scheduled using multi-carrier scheduling). The UE 120 can transmit one or more scheduled PUSCH communications (e.g., scheduled using multi-carrier scheduling or single-carrier scheduling).

[0092] Thus, the UE 120 is able to utilize multi-carrier scheduling for PDSCH communications while also being able to schedule PUSCH communications by the UE (e.g., using multi-carrier scheduling or single-carrier scheduling) without increasing the DCI size or the blind decoding complexity of PDCCHs as the UE 120 is configured to use multi-carrier scheduling DCI for PUSCH communications or single-carrier scheduling DCI for PUSCH communications.

[0093] As described above, providing Figure 5 as an example. Other examples can differ from what is described Figure 5 with respect to the examples described.

[0094] Figure 6 is a diagram illustrating an example 600 associated with multi-carrier scheduling for downlink and uplink communications, in accordance with the present disclosure. As Figure 6 indicated, the UE 120 can be served by a first serving cell and a second serving cell. In some aspects, the first serving cell can be associated with a first carrier (e.g., a first carrier) and the second serving cell can be associated with a second carrier (e.g., a second carrier). In some aspects, the first carrier and the second carrier can be aggregated for downlink data communications (e.g., for PDSCH communications). In some aspects, the first serving cell can be a primary cell (e.g., a PCell) and the second serving cell can be a secondary cell (e.g., a PSCell, a SCell, etc.). In some aspects, the first serving cell can be a secondary cell and the second serving cell can be a primary cell.

[0095] The example 600 depicts a UE 120 that can be configured with multi-carrier scheduling for PDSCH communications and multi-carrier scheduling for PUSCH communications. For example, the UE 120 can support carrier aggregation for uplink carriers (e.g., the first carrier and the second carrier can be aggregated for uplink as well as downlink).

[0096] The UE 120 can be configured to monitor a set of PDCCH candidates for DCI scheduling PDSCH communications on multiple carriers and for DCI scheduling PUSCH communications on multiple carriers. For example, as Figure 6As shown, the set of PDCCH candidates can be associated with the first serving cell. Thus, DCI transmitted using PDCCH candidates associated with the first serving cell can schedule communications (e.g., PDSCH communications or PUSCH communications) on the first serving cell (e.g., on the first carrier) and on the second serving cell (e.g., on the second carrier). The UE 120 can be configured with search spaces for monitoring the set of PDCCH candidates within the PDCCH of the first serving cell.

[0097] As shown by reference number 605, the base station 110 associated with the first serving cell can transmit DCI for scheduling PDSCH communications on the first serving cell and for scheduling PDSCH on the second serving cell. The UE 120 can receive the DCI based at least in part on monitoring the PDCCH candidates in the search spaces. In some aspects, the UE 120 can determine that the DCI is scheduling PDSCH communications based at least in part on a payload size of the DCI, an identifier indicated in the DCI, and / or the like. The UE 120 can reserve or allocate resources (e.g., indicated by the DCI) for PDSCH communications on the first serving cell and can reserve or allocate resources (e.g., indicated by the DCI) for PDSCH communications on the second serving cell.

[0098] As shown by reference number 610, the base station 110 associated with the first serving cell can transmit DCI for scheduling PUSCH communications on the first serving cell and for scheduling PUSCH on the second serving cell. In some aspects, the UE 120 can determine that the DCI is scheduling PUSCH communications based at least in part on a payload size of the DCI, an identifier indicated in the DCI, and / or the like. The UE 120 can reserve or allocate resources (e.g., indicated by the DCI) for PUSCH communications on the first serving cell and can reserve or allocate resources (e.g., indicated by the DCI) for PUSCH communications on the second serving cell.

[0099] In some aspects, the UE 120 can be configured to monitor a first set of PDCCH candidates in a first search space for DCI scheduling PDSCH communications on the first serving cell and the second serving cell, and monitor a second set of PDCCH candidates in a second search space for DCI scheduling PUSCH communications on the first serving cell and the second serving cell. The base station 110 associated with the first serving cell can transmit DCI for scheduling PDSCH communications on the first serving cell and for scheduling PDSCH communications on the second serving cell using the first set of PDCCH candidates. The base station 110 associated with the first serving cell can transmit DCI for scheduling PUSCH communications on the first serving cell and for scheduling PUSCH communications on the second serving cell using the second set of PDCCH candidates. In some aspects, the UE 120 can determine whether the DCI is scheduling a PDSCH communication or a PUSCH communication based at least in part on the set of PDCCH candidates used to transmit the DCI. This can conserve resources and improve network efficiency, as a serving cell can schedule multiple PDSCH communications using a single DCI, and can schedule multiple PUSCH communications using a single DCI, while also not increasing the blind PDCCH decoding complexity associated with the UE 120 receiving the DCI.

[0100] Additionally, this can conserve network resources, as DCI for multiple serving cells can be transmitted on a single serving cell. For example, a carrier for the second serving cell can operate with dynamic spectrum sharing (DSS) and can have limited available resources due to resource sharing between multiple RATs. Thus, resources associated with transmitting DCI for the UE 120 can be allocated to the first serving cell, which can not operate with DSS and can have more available resources. As a result, the network can improve efficiency by transmitting DCI for both the first serving cell and the second serving cell on the first serving cell.

[0101] As described above, providing Figure 6 as an example. Other examples can vary from those described Figure 6 without departing from the spirit or scope of the examples.

[0102] Figure 7 is a diagram illustrating an example 700 associated with multi-carrier scheduling for downlink and uplink communications, in accordance with the present disclosure. As Figure 7As shown, the UE 120 can be served by a first serving cell and a second serving cell. In some aspects, the first serving cell can be associated with a first carrier and the second serving cell can be associated with a second carrier. In some aspects, the first carrier and the second carrier can be aggregated for downlink data communications (e.g., for PDSCH communications). In some aspects, the first serving cell can be a primary cell (e.g., a PCell) and the second serving cell can be a secondary cell (e.g., a PSCell, a SCell, etc.). In some aspects, the first serving cell can be a secondary cell and the second serving cell can be a primary cell.

[0103] The example 700 depicts a UE 120 that can be configured with multi-carrier scheduling for PDSCH communications and single-carrier scheduling for PUSCH communications. As Figure 7 As shown, the single-carrier scheduling can be self-carrier scheduling (e.g., the first serving cell can transmit DCI for scheduling PUSCH communications on the first serving cell, and the second serving cell can transmit DCI for scheduling PUSCH communications on the second serving cell). In some aspects, the UE 120 can support carrier aggregation for uplink carriers (e.g., the first carrier and the second carrier can be aggregated for uplink as well as downlink). In some aspects, the UE 120 can not support carrier aggregation for uplink carriers.

[0104] The UE 120 can be configured to monitor a set of PDCCH candidates for DCI for scheduling PDSCH communications on the first serving cell and the second serving cell (e.g., for multi-carrier scheduling DCI), monitor the set of PDCCH candidates for DCI for scheduling PUSCH communications on the first serving cell (e.g., for single-carrier scheduling DCI), and monitor the set of PDCCH candidates for DCI for scheduling PUSCH communications on the second serving cell (e.g., for single-carrier scheduling DCI). The UE 120 can monitor each set of PDCCH candidates in a search space associated with each set of PDCCH candidates.

[0105] In some aspects, the UE 120 can be configured to monitor a same serving cell (e.g. Figure 7downlink DCI (e.g., multi-carrier scheduling DCI) and uplink DCI (e.g., single-carrier scheduling DCI) on the same carrier. In some aspects, the set of PDCCH candidates associated with the first serving cell for the downlink DCI can be the same as the set of PDCCH candidates associated with the first serving cell for the uplink DCI. In some aspects, the set of PDCCH candidates associated with the first serving cell for the downlink DCI can be different than the set of PDCCH candidates associated with the first serving cell for the uplink DCI (e.g., as shown in FIG. 7). Figure 7

[0106] As shown in FIG. 7, the base station 110 associated with the first serving cell can transmit a single DCI for scheduling PDSCH communications on the first serving cell (e.g., on the first carrier) and for scheduling PDSCH communications on the second serving cell (e.g., on the second carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates associated with the DCI in a search space. If the set of PDCCH candidates associated with the first serving cell for the downlink DCI is the same as the set of PDCCH candidates associated with the first serving cell for the uplink DCI, the UE 120 can determine that the DCI is scheduling PDSCH communications on both the first serving cell and the second serving cell based at least in part on a payload size of the DCI, an identifier indicated by the DCI, and / or the like. In some aspects, if the set of PDCCH candidates associated with the first serving cell for the downlink DCI is different than the set of PDCCH candidates associated with the first serving cell for the uplink DCI, the UE 120 can determine that the DCI is scheduling PDSCH communications on both the first serving cell and the second serving cell based at least in part on the set of PDCCH candidates used to transmit the DCI.

[0107] ​As shown by reference number 710, the base station 110 associated with the first serving cell can transmit a DCI for scheduling a PUSCH communication on the first serving cell (e.g., on the first carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates associated with the DCI in a search space. If the set of PDCCH candidates associated with the first serving cell for downlink DCI and the set of PDCCH candidates associated with the first serving cell for uplink DCI are the same, the UE 120 can determine that the DCI is scheduling a PUSCH communication on the first serving cell based at least in part on a payload size of the DCI, an identifier indicated by the DCI, and / or the like. In some aspects, if the set of PDCCH candidates associated with the first serving cell for downlink DCI and the set of PDCCH candidates associated with the first serving cell for uplink DCI are different, the UE 120 can determine that the DCI is scheduling a PUSCH communication on the first serving cell based at least in part on the set of PDCCH candidates used to transmit the DCI.

[0108] As shown by reference number 715, the base station 110 associated with the second serving cell (which can be the same base station 110 as associated with the first serving cell or a different base station 110) can transmit a DCI for scheduling a PUSCH communication on the second serving cell (e.g., on the second carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates associated with the DCI in a search space. Since the UE 120 can not be configured to monitor for downlink DCI in the second serving cell (e.g., on the second carrier), the UE 120 can determine that the DCI is scheduling a PUSCH communication on the second serving cell based at least in part on the set of PDCCH candidates used to transmit the DCI, the base station 110 that transmitted the DCI, and / or the like.

[0109] As described above, the UE 120 can monitor for uplink DCI at each carrier (e.g., because the UE 120 is configured to use single-carrier scheduling DCI for PUSCH communications). However, the UE 120 can not monitor for downlink DCI at each carrier (e.g., because the UE 120 is configured to use multi-carrier scheduling DCI for PDSCH communications). This can conserve resources and improve network efficiency, as the UE 120 can use a single DCI to schedule multiple PDSCH communications while also not increasing blind PDCCH decoding complexity associated with the UE 120 receiving the DCI.

[0110] Additionally, this can conserve network resources, as DCI for multiple serving cells can be transmitted on a single serving cell. For example, a carrier for a second serving cell can operate with a DSS and can have limited available resources due to resource sharing between multiple RATs. Thus, resources associated with transmitting DCI scheduling PDSCH communications for the UE 120 can be allocated to the first serving cell (which can not operate with a DSS and can have more available resources). As a result, the network can improve efficiency by transmitting DCI for both the first serving cell and the second serving cell on the first serving cell.

[0111] As described above, there is provided Figure 7 by way of example. Other examples can differ from Figure 7 the examples described.

[0112] Figure 8 is a diagram illustrating an example 800 associated with multi-carrier scheduling for downlink and uplink communications, in accordance with the present disclosure. As Figure 8 indicated, the UE 120 can be served by a first serving cell and a second serving cell. In some aspects, the first serving cell can be associated with a first carrier and the second serving cell can be associated with a second carrier. In some aspects, the first carrier and the second carrier can be aggregated for downlink data communications (e.g., for PDSCH communications). In some aspects, the first serving cell can be a primary cell (e.g., a PCell) and the second serving cell can be a secondary cell (e.g., a PSCell, a SCell, etc.). In some aspects, the first serving cell can be a secondary cell and the second serving cell can be a primary cell.

[0113] The example 800 depicts a UE 120 that can be configured with multi-carrier scheduling for PDSCH communications and single-carrier scheduling for PUSCH communications. As Figure 8 indicated, the single-carrier scheduling can be cross-carrier scheduling (e.g., the first serving cell can transmit DCI for scheduling PUSCH communications on the first serving cell and the first serving cell can transmit DCI for scheduling PUSCH communications on the second serving cell). In some aspects, the UE 120 can support carrier aggregation for uplink carriers (e.g., the first carrier and the second carrier can be aggregated for uplink as well as downlink). In some aspects, the UE 120 can not support carrier aggregation for uplink carriers.

[0114] The UE 120 can be configured to monitor a set of PDCCH candidates for DCI scheduling PDSCH communications on the first serving cell and the second serving cell (e.g., for multi-carrier scheduling DCI), monitor a set of PDCCH candidates for DCI scheduling PUSCH communications on the first serving cell (e.g., for single-carrier scheduling DCI), and monitor a set of PDCCH candidates for DCI scheduling PUSCH communications on the second serving cell (e.g., for single-carrier scheduling DCI). The UE 120 can monitor each set of PDCCH candidates in a search space associated with each set of PDCCH candidates. As shown in Figure 8 each set of PDCCH candidates can be associated with the first serving cell. For example, a first carrier associated with the first serving cell can be a scheduling carrier.

[0115] In some aspects, the set of PDCCH candidates for DCI scheduling PUSCH communications on the first serving cell can be associated with a first CIF value, and the set of PDCCH candidates for DCI scheduling PUSCH communications on the second serving cell can be associated with a second CIF value. As a result, the UE 120 can determine whether the DCI is scheduling PUSCH communications on the first serving cell or the second serving cell based at least in part on the CIF value indicated by the DCI.

[0116] In some aspects, the set of PDCCH candidates for DCI scheduling PDSCH communications on the first serving cell can be the same as the set of PDCCH candidates for DCI scheduling PUSCH communications on the first serving cell (e.g., when the set of PDCCH candidates for DCI scheduling PDSCH communications on the first serving cell and the second serving cell is associated with the first serving cell). That is, a PDCCH candidate for multi-carrier scheduling of PDSCH communications on a carrier can be the same as a PDCCH candidate for single- / self-carrier scheduling of PUSCH on the same carrier. In some aspects, if the set of PDCCH candidates for DCI scheduling PDSCH communications on the first serving cell is the same as the set of PDCCH candidates for DCI scheduling PUSCH communications on the first serving cell, the set of PDCCH candidates for DCI scheduling PDSCH communications on the first serving cell and the second serving cell can be associated with a third CIF value.

[0117] As shown by reference number 805, the base station 110, associated with the first serving cell, can transmit a single DCI for scheduling PDSCH communications on the first serving cell (e.g., on the first carrier) and for scheduling PDSCH communications on the second serving cell (e.g., on the second carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates, associated with the DCI, in a search space. If the set of PDCCH candidates for the DCI scheduling PDSCH communications on the first serving cell is the same as the set of PDCCH candidates for the DCI scheduling PUSCH communications on the first serving cell, the UE 120 can determine, based at least in part on a payload size of the DCI, an identifier indicated by the DCI, and / or the like, that the DCI is scheduling PDSCH communications on both the first serving cell and the second serving cell. In some aspects, the UE 120 can determine, based at least in part on a CIF value indicated by the DCI (e.g., if the DCI indicates a third CIF value), that the DCI is scheduling PDSCH communications on both the first serving cell and the second serving cell. In some aspects, if the set of PDCCH candidates for the DCI scheduling PDSCH communications on the first serving cell is different than the set of PDCCH candidates for the DCI scheduling PUSCH communications on the first serving cell, the UE 120 can determine, based at least in part on the set of PDCCH candidates used to transmit the DCI, that the DCI is scheduling PDSCH communications on both the first serving cell and the second serving cell.

[0118] As shown by reference number 810, the base station 110, associated with the first serving cell, can transmit a DCI for scheduling PUSCH communications on the first serving cell (e.g., on the first carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates, associated with the DCI, in a search space. If the set of PDCCH candidates for the DCI scheduling PDSCH communications on the first serving cell is the same as the set of PDCCH candidates for the DCI scheduling PUSCH communications on the first serving cell, the UE 120 can determine, based at least in part on a payload size of the DCI, an identifier indicated by the DCI, and / or the like, that the DCI is scheduling PUSCH communications on the first serving cell. In some aspects, the UE 120 can determine, based at least in part on a CIF value indicated by the DCI (e.g., if the DCI indicates a first CIF value), that the DCI is scheduling PUSCH communications on the first serving cell. In some aspects, if the set of PDCCH candidates for the DCI scheduling PDSCH communications on the first serving cell is different than the set of PDCCH candidates for the DCI scheduling PUSCH communications on the first serving cell, the UE 120 can determine, based at least in part on the set of PDCCH candidates used to transmit the DCI, that the DCI is scheduling PUSCH communications on the first serving cell.

[0119] As shown by reference number 815, the base station 110, associated with the first serving cell, can transmit DCI scheduling a PUSCH communication on the second serving cell (e.g., on a second carrier). The UE 120 can receive the DCI based at least in part on monitoring a set of PDCCH candidates associated with the DCI in a search space. In some aspects, the UE 120 can determine that the DCI is scheduling a PUSCH communication on the second serving cell based at least in part on a CIF value indicated by the DCI (e.g., if the DCI indicates a second CIF value). In some aspects, the UE 120 can determine that the DCI is scheduling a PUSCH communication on the second serving cell based at least in part on a set of PDCCH candidates used to transmit the DCI.

[0120] As described above, the UE 120 can monitor for uplink DCI at a scheduling carrier for single carrier scheduling DCI (e.g., a first carrier of the first serving cell as shown by reference number 810). The UE 120 can not monitor for downlink DCI at each carrier (e.g., because the UE 120 is configured to use multi-carrier scheduling DCI for PDSCH communications). This can conserve resources and improve network efficiency because the UE 120 can use a single DCI to schedule multiple PDSCH communications while also not increasing blind PDCCH decoding complexity associated with the UE 120 receiving the DCI. Figure 8

[0121] Additionally, this can conserve network resources because DCI for multiple serving cells can be transmitted on a single serving cell. For example, a carrier of the second serving cell can operate with DSS and can have limited available resources due to resource sharing between multiple RATs. Thus, resources associated with transmitting DCI for the UE 120 can be allocated to the first serving cell (which can not operate with DSS and can have more available resources). As a result, the network can improve efficiency by transmitting DCI for both the first serving cell and the second serving cell on the first serving cell.

[0122] As described above, providing Figure 8 as an example. Other examples can differ from what is described Figure 8 without departing from the spirit of the disclosure.

[0123] Figure 9 FIG. 9 is a diagram illustrating an example process 900 performed, for example, by a UE, in accordance with the present disclosure. Example process 900 is an example of a process for performing operations associated with multi-carrier scheduling for downlink and uplink, performed by a UE (e.g., UE 120).

[0124] As Figure 9 ​As shown, in some aspects, process 900 may include receiving configuration for monitoring one or more PDCCHs (block 910) for DCIs of PDSCH communications on each carrier included in the scheduling carrier set and for DCIs of PUSCH communications on one or more carriers. For example, a UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, and / or memory 282) may receive configuration for monitoring one or more PDCCHs for DCIs of PDSCH communications on each carrier included in the scheduling carrier set and for DCIs of PUSCH communications on one or more carriers, as described above.

[0125] like Figure 9 Additionally, as shown, in some aspects, process 900 may include: monitoring the one or more PDCCHs for DCI according to the configuration (block 920). For example, the UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280 and / or memory 282) may monitor the one or more PDCCHs for DCI according to the configuration, as described above.

[0126] like Figure 9 Additionally, as shown, in some aspects, process 900 may include: receiving and scheduling DCIs of PUSCH communications on the one or more carriers at least in part based on the monitoring (block 930). For example, the UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, controller / processor 280, and / or memory 282) may receive and schedule DCIs of PUSCH communications on the one or more carriers at least in part based on the monitoring, as described above.

[0127] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0128] In a first aspect, the carrier set includes a first carrier associated with a first serving cell and a second carrier associated with a second serving cell.

[0129] In a second aspect, either alone or in combination with the first aspect, the configuration indicates a set of PDCCH candidates for scheduling the DCI for PDSCH communication on each carrier included in the carrier set, and one or more other sets of PDCCH candidates for scheduling the DCI for PDSCH communication on one or more other carrier sets.

[0130] In a third aspect, alone or in combination with one or more of the first and second aspects, the configuration indicates at least one of a search space configuration for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a CIF value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0131] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the configuration indicates that a downlink carrier is included in the set of carriers and that an uplink carrier is included in the set of carriers.

[0132] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring a PDCCH for DCI scheduling PUSCH communications on each carrier included in the set of carriers, and receiving the DCI scheduling the PUSCH communications on the one or more carriers includes receiving the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0133] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the set of carriers includes a first carrier associated with a first serving cell and a second carrier associated with a second serving cell, and monitoring the PDCCH for DCI scheduling the PUSCH communications on the set of carriers includes monitoring a PDCCH of the first cell for the DCI scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier, or monitoring a PDCCH of the second cell for the DCI scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier.

[0134] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the DCI scheduling the PUSCH communications on each carrier included in the set of carriers is a multi-carrier scheduling type DCI.

[0135] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the configuration indicates the DCI used to schedule PDSCH communications on each carrier included in the set of carriers, and a set of PDCCH candidates for DCI used to schedule PUSCH communications on each carrier included in the set of carriers.

[0136] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the configuration indicates a search space configuration for the set of PDCCH candidates.

[0137] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the configuration indicates an identifier associated with the DCI used to schedule PDSCH communications on each carrier included in the set of carriers, and an identifier associated with the DCI used to schedule PUSCH communications on each carrier included in the set of carriers.

[0138] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a payload size of the DCI used to schedule PDSCH communications on each carrier included in the set of carriers is the same as a payload size of the DCI used to schedule PUSCH communications on each carrier included in the set of carriers.

[0139] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, receiving the DCI scheduling the PUSCH communications on the one or more carriers includes receiving a DCI indicating the identifier associated with the DCI used to schedule PUSCH communications on each carrier included in the set of carriers, and determining, based at least in part on receiving the DCI indicating the identifier associated with the DCI used to schedule PUSCH communications on each carrier included in the set of carriers, that the DCI is scheduling PUSCH communications on each carrier included in the set of carriers.

[0140] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the configuration indicates a first set of PDCCH candidates for the DCI used to schedule PDSCH communications on each carrier included in the set of carriers, and a second set of PDCCH candidates for the DCI used to schedule PUSCH communications on each carrier included in the set of carriers.

[0141] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the configuration indicates a first search space configuration for the first set of PDCCH candidates, and a second search space configuration for the second set of PDCCH candidates.

[0142] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring the first set of PDCCH candidates in a first search space configured by the first search space configuration for DCI scheduling PDSCH communications on each carrier included in the set of carriers and monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration for DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0143] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the configuration indicates that a downlink carrier includes the set of carriers and the uplink carrier includes a subset of carriers of the set of carriers.

[0144] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring a PDCCH for DCI scheduling PUSCH communications on a carrier in the subset of carriers, and receiving the DCI scheduling the PUSCH communications on the one or more carriers includes receiving DCI scheduling PUSCH communications on a carrier in the subset of carriers.

[0145] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the carriers in the subset of carriers are associated with a first serving cell, and monitoring the PDCCH for DCI scheduling the PUSCH communications on the carriers in the subset of carriers includes monitoring a PDCCH of a first serving cell for DCI scheduling the PUSCH communications on the carriers in the subset of carriers or monitoring a PDCCH of a second serving cell for DCI scheduling the PUSCH communications on the carriers in the subset of carriers.

[0146] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the DCI scheduling the PUSCH communications on the one or more carriers is a single-carrier scheduling type DCI.

[0147] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring a PDCCH associated with a first serving cell for DCI scheduling PDSCH communications on each carrier included in the set of carriers, monitoring the PDCCH associated with the first serving cell for DCI scheduling PUSCH communications on a carrier associated with the first serving cell, and monitoring a PDCCH associated with a second serving cell for DCI scheduling PUSCH communications on a carrier associated with the second serving cell.

[0148] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring a PDCCH associated with a first carrier included in the set of carriers for DCI scheduling PDSCH communications on each carrier included in the set of carriers, and monitoring the PDCCH associated with the first carrier for DCI scheduling PUSCH communications on a single carrier included in the set of carriers.

[0149] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the configuration indicates a set of PDCCH candidates associated with the first carrier, and the set of PDCCH candidates is associated with DCI scheduling PDSCH communications on each carrier included in the set of carriers and DCI scheduling PUSCH communications on the single carrier.

[0150] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the configuration indicates a search space configuration associated with the set of PDCCH candidates.

[0151] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, the configuration indicates an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and an identifier associated with the DCI scheduling PUSCH communications on the single carrier.

[0152] In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, a payload size of the DCI scheduling PDSCH communications on each carrier included in the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on the single carrier.

[0153] In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, receiving the DCI scheduling the PUSCH communications on the one or more carriers includes receiving a DCI indicating the identifier associated with the DCI scheduling the PUSCH communications on the single carrier, and determining, based at least in part on receiving the DCI indicating the identifier associated with the DCI scheduling the PUSCH communications on the single carrier, that the DCI is scheduling the PUSCH communications on the single carrier.

[0154] In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the configuration indicates a first set of PDCCH candidates associated with DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and a second set of PDCCH candidates associated with DCIs scheduling PUSCH communications on the single carrier.

[0155] In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the configuration indicates a first search space configuration associated with the first set of PDCCH candidates, and a second search space configuration associated with the second set of PDCCH candidates.

[0156] In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring the first set of PDCCH candidates in a first search space configured by the first search space configuration for DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration for DCIs scheduling PUSCH communications on the single carrier.

[0157] In a thirtieth aspect, alone or in combination with one or more of the first through twenty-ninth aspects, the single carrier is a first carrier.

[0158] In a thirty-first aspect, alone or in combination with one or more of the first through thirtieth aspects, the single carrier is a second carrier included in the set of carriers.

[0159] In a thirty-second aspect, alone or in combination with one or more of the first through thirty-first aspects, monitoring the one or more PDCCHs for DCI in accordance with the configuration includes monitoring a PDCCH associated with a first carrier included in the set of carriers for DCI scheduling a PDSCH communication on each carrier included in the set of carriers, monitoring the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the first carrier, and monitoring the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on a second carrier included in the set of carriers.

[0160] In a thirty-third aspect, alone or in combination with one or more of the first through thirty-second aspects, the configuration indicates a first carrier indicator field (CIF) value associated with DCI scheduling a PUSCH communication on the first carrier and a second CIF value associated with the DCI scheduling a PUSCH communication on the second carrier.

[0161] In a thirty-fourth aspect, alone or in combination with one or more of the first through thirty-third aspects, the configuration indicates a third CIF value associated with the DCI scheduling a PDSCH communication on each carrier included in the set of carriers.

[0162] In a thirty-fifth aspect, alone or in combination with one or more of the first through thirty-fourth aspects, the first carrier is a scheduling carrier.

[0163] Although Figure 9 Example blocks of the process 900 are illustrated, but in some aspects, the process 900 can include Figure 9 Additional blocks can be added, some of the blocks can be removed, some of the blocks can be combined, and / or some of the blocks can be performed in a different order than that shown in the example process 900. Additionally or alternatively, two or more of the blocks of the process 900 can be performed in parallel.

[0164] Figure 10 FIG. 10 is a diagram illustrating an example process 1000 performed, for example, by a base station, in accordance with the present disclosure. Example process 1000 is an example of a process for a base station (e.g., base station 110) to perform operations associated with multi-carrier scheduling for downlink and uplink.

[0165] As Figure 10As shown, in some aspects, process 1000 can include determining a configuration for the UE to monitor one or more PDCCHs for DCI scheduling PDSCH communications on each carrier included in a set of carriers and for DCI scheduling PUSCH communications on one or more carriers (block 1010). For example, the base station (e.g., using transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, and / or scheduler 246) can determine a configuration for the UE to monitor one or more PDCCHs for DCI scheduling PDSCH communications on each carrier included in a set of carriers and for DCI scheduling PUSCH communications on one or more carriers, as described above.

[0166] As further shown in Figure 10 As further shown in

[0167] As further shown in Figure 10 As further shown in

[0168] Process 1000 can include additional aspects, such as any single aspect or any combination of aspects described in connection with one or more other processes described elsewhere herein.

[0169] In a first aspect, the base station is associated with a carrier included in the set of carriers.

[0170] In a second aspect, alone or in combination with the first aspect, determining the configuration includes determining a set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers and one or more other sets of PDCCH candidates for DCI scheduling PDSCH communications on one or more other sets of carriers.

[0171] In a third aspect, alone or in combination with one or more of the first and second aspects, determining the configuration comprises determining at least one of: a search space configuration for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a CIF value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0172] In a fourth aspect, alone or in combination with one or more of the first through third aspects, determining the configuration comprises determining that a downlink carrier of the UE comprises the set of carriers and an uplink carrier of the UE comprises the set of carriers.

[0173] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting DCIs scheduling PUSCH communications on each carrier included in the set of carriers.

[0174] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the base station is associated with a first serving cell and the set of carriers includes a first carrier associated with the first serving cell and a second carrier associated with a second serving cell, and transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting DCIs scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier in a PDCCH of the first cell.

[0175] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the DCI scheduling the PUSCH communications on each carrier included in the set of carriers is a multi-carrier scheduling type DCI.

[0176] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, determining the configuration comprises determining the DCI for scheduling PDSCH communications on each carrier included in the set of carriers and a set of PDCCH candidates for DCIs for scheduling PUSCH communications on each carrier included in the set of carriers.

[0177] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, determining the configuration includes determining a search space configuration for the set of PDCCH candidates.

[0178] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, determining the configuration includes determining an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and determining an identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0179] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a payload size of the DCI scheduling PDSCH communications on the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on the set of carriers.

[0180] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes transmitting a DCI indicating the identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0181] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, determining the configuration includes determining a first set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and determining a second set of PDCCH candidates for the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0182] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the determining the configuration includes determining a first search space configuration for the first set of PDCCH candidates, and determining a second search space configuration for the second set of PDCCH candidates.

[0183] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes: transmitting, for a DCI scheduling a PDSCH communication on each carrier included in the set of carriers, the DCI using the first set of PDCCH candidates of the first search space configured by the first search space configuration; and transmitting, for a DCI scheduling a PUSCH communication on each carrier included in the set of carriers, the DCI using monitoring the second set of PDCCH candidates in the second search space configured by the second search space configuration.

[0184] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, determining the configuration includes determining that a downlink carrier of the UE includes the set of carriers and an uplink carrier of the UE includes a subset of carriers of the set of carriers.

[0185] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes transmitting a DCI scheduling a PUSCH communication on the carriers in the subset of carriers.

[0186] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the base station is associated with a first serving cell, and transmitting the DCI scheduling the PUSCH communications on the carriers in the subset of carriers includes: transmitting, in a PDCCH of the first serving cell, the DCI scheduling the PUSCH communications on carriers associated with the first serving cell; or transmitting, in a PDCCH of the first serving cell, the DCI scheduling PUSCH communications on carriers associated with a second serving cell.

[0187] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the DCI scheduling the PUSCH communications on the one or more carriers is a single carrier scheduling type DCI.

[0188] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes: transmitting, on a PDCCH associated with the base station, a DCI scheduling a PDSCH communication on each carrier included in the set of carriers; and transmitting, on the PDCCH associated with the base station, a DCI scheduling a PUSCH communication on a carrier associated with the base station.

[0189] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes: transmitting, in a PDCCH associated with the base station, DCIs scheduling PDSCH communications on each carrier included in the set of carriers; and transmitting, in the PDCCH associated with the base station, a DCI scheduling a PUSCH communication on a single carrier included in the set of carriers.

[0190] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, determining the configuration includes: determining a set of PDCCH candidates associated with the PDCCH associated with the base station; and determining that the set of PDCCH candidates is associated with DCIs scheduling PDSCH communications on each carrier included in the set of carriers and a DCI scheduling a PUSCH communication on the single carrier.

[0191] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, determining the configuration includes: determining a search space configuration associated with the set of PDCCH candidates.

[0192] In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, determining the configuration includes: determining an identifier associated with the DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and determining an identifier associated with the DCI scheduling a PUSCH communication on the single carrier.

[0193] In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, a payload size of the DCIs scheduling PDSCH communications on each carrier included in the set of carriers is the same as a payload size of the DCI scheduling a PUSCH communication on the single carrier.

[0194] In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes: transmitting a DCI indicating the identifier associated with the DCI scheduling a PUSCH communication on the single carrier to schedule a PUSCH communication on the single carrier; and transmitting a DCI indicating the identifier associated with DCIs scheduling PDSCH communications on each carrier included in the set of carriers to schedule PDSCH communications on each carrier included in the set of carriers.

[0195] In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, determining the configuration includes determining a first set of PDCCH candidates associated with DCI scheduling PDSCH communications on each carrier included in the set of carriers, and determining a second set of PDCCH candidates associated with DCI scheduling PUSCH communications on the single carrier.

[0196] In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, determining the configuration includes determining a first search space configuration associated with the first set of PDCCH candidates, and determining a second search space configuration associated with the second set of PDCCH candidates.

[0197] In a twenty-ninth aspect, alone or in combination with one or more of the first through twenty-eighth aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes transmitting DCI for DCI scheduling PDSCH communications on the set of carriers using the first set of PDCCH candidates of a first search space configured by the first search space configuration; and transmitting DCI for DCI scheduling PUSCH communications on the single carrier using monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration.

[0198] In a thirtieth aspect, alone or in combination with one or more of the first through twenty-ninth aspects, the single carrier is a carrier associated with the base station.

[0199] In a thirty-first aspect, alone or in combination with one or more of the first through thirtieth aspects, the single carrier is a carrier associated with another base station.

[0200] In a thirty-second aspect, alone or in combination with one or more of the first through thirty-first aspects, transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers includes transmitting DCI scheduling PDSCH communications on each carrier included in the set of carriers in a PDCCH associated with the base station; transmitting DCI scheduling PUSCH communications on the carrier associated with the base station in the PDCCH associated with the base station; and transmitting DCI scheduling PUSCH communications on another carrier associated with another base station in the PDCCH associated with the base station.

[0201] In the thirty-third aspect, determining the configuration, either alone or in combination with one or more of the first to thirty-second aspects, includes: determining a first CIF value associated with the DCI of PUSCH communication scheduled on the carrier associated with the base station; and determining a second CIF value associated with the DCI of PUSCH communication scheduled on another carrier associated with another base station.

[0202] In the thirty-fourth aspect, determining the configuration, either alone or in combination with one or more of the first to thirty-third aspects, includes determining a third CIF value associated with the DCI for scheduling PDSCH communication on each carrier included in the carrier set.

[0203] Although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include... Figure 10 The blocks shown are those that are additional, fewer, different, or arranged differently compared to other blocks. Additionally or alternatively, two or more blocks in process 1000 can be executed in parallel.

[0204] Figure 11 This is a block diagram of an example device 1100 for wireless communication. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1302 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 1100 may include one or more channel monitoring components 1108, and other examples.

[0205] In some respects, device 1100 can be configured to perform the functions described herein. Figures 5-8 One or more operations described herein. Additionally or alternatively, device 1100 may be configured to perform one or more processes described herein (e.g., Figure 9 The process 900) or a combination thereof. In some respects, Figure 11 The device 1100 and / or one or more components shown may include the elements described above. Figure 2 One or more components of the user equipment described. Additionally or alternatively, Figure 11 One or more components shown can be combined with the above. Figure 2implementation within one or more components described herein. Additionally or alternatively, one or more components of the set of components can be implemented at least partially as software stored in a memory and executable by a controller or a processor. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0206] The reception component 1102 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106. The reception component 1102 can provide received communications to one or more other components of the apparatus 1100. In some aspects, the reception component 1102 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1106. In some aspects, the reception component 1102 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the user equipment described above in connection with Fig. 2. Figure 2 The reception component 1102 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106. The reception component 1102 can provide received communications to one or more other components of the apparatus 1100. In some aspects, the reception component 1102 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1106. In some aspects, the reception component 1102 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the user equipment described above in connection with Fig. 2.

[0207] The transmission component 1104 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106. In some aspects, one or more other components of the apparatus 1106 can generate communications and can provide the generated communications to the transmission component 1104 for transmission to the apparatus 1106. In some aspects, the transmission component 1104 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 1106. In some aspects, the transmission component 1104 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the user equipment described above in connection with Fig. 2. In some aspects, the transmission component 1104 can be co-located with the reception component 1102 in a transceiver of the apparatus 1106. Figure 2 The transmission component 1104 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106. In some aspects, one or more other components of the apparatus 1106 can generate communications and can provide the generated communications to the transmission component 1104 for transmission to the apparatus 1106. In some aspects, the transmission component 1104 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 1106. In some aspects, the transmission component 1104 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the user equipment described above in connection with Fig. 2. In some aspects, the transmission component 1104 can be co-located with the reception component 1102 in a transceiver of the apparatus 1106.

[0208] The reception component 1102 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106. The reception component 1102 can provide received communications to one or more other components of the apparatus 1100. In some aspects, the reception component 1102 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1106. In some aspects, the reception component 1102 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the user equipment described above in connection with Fig. 2. Figure 2The one or more antennas, demodulators, MIMO detector, receive processor, modulators, transmit MIMO processor, transmit processor, controller / processor, memory, or combination thereof, of the described user equipment. The reception component 1102 can receive, based at least in part on monitoring, DCI scheduling a PUSCH communication on one or more carriers.

[0209] Provided are Figure 11 The number and arrangement of components shown in FIG. 10 are Figure 11 There can be additional components, fewer components, different components, or differently arranged components in FIG. 10 than are shown in FIG. 10. Additionally or alternatively, two or more components shown in FIG. 10 can be implemented within a single component, or a single component shown in FIG. 10 can be implemented as multiple, distributed components. Additionally or alternatively, a group of components (one or more components) shown in FIG. 10 can be Figure 11 implemented to perform one or more functions described as being performed by another group of components shown in FIG. 10. Figure 11 Figure 11 Figure 11

[0210] Figure 12 FIG. 12 is a block diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 can be a base station, or a base station can include the apparatus 1200. In some aspects, the apparatus 1200 includes a reception component 1202 and a transmission component 1204, which can be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 1200 can communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the reception component 1202 and the transmission component 1204. As further shown, the apparatus 1200 can include one or more determination components 1208 and other examples.

[0211] In some aspects, the apparatus 1200 can be configured to perform one or more operations described herein in connection with Figures 5-8 one or more processes described herein. Additionally, or alternatively, the apparatus 1200 can be configured to perform one or more processes described herein (for example, process 1000 of FIG. 10), or a combination thereof. In some aspects, the apparatus 1200 and / or one or more components thereof can include one or more components of the base station described above in connection with Figure 10 FIG. 11. Additionally or alternatively, one or more components shown in FIG. 12 can be implemented in Figure 12 connection with one or more components of the base station described above in connection with Figure 2 FIG. 11. Additionally or alternatively, one or more components shown in FIG. 12 can be implemented in Figure 12 connection with one or more components of the base station described above in connection with Figure 2 ​​​implementation within one or more components described herein. Additionally or alternatively, one or more components of the set of components can be implemented at least partially as software stored in a memory and executable by a controller or a processor. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0212] The reception component 1202 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206. The reception component 1202 can provide received communications to one or more other components of the apparatus 1200. In some aspects, the reception component 1202 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1206. In some aspects, the reception component 1202 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the base station described above. Figure 2 The reception component 1202 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206. The reception component 1202 can provide received communications to one or more other components of the apparatus 1200. In some aspects, the reception component 1202 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1206. In some aspects, the reception component 1202 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the base station described above.

[0213] The transmission component 1204 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206. In some aspects, one or more other components of the apparatus 1206 can generate communications and can provide the generated communications to the transmission component 1204 for transmission to the apparatus 1206. In some aspects, the transmission component 1204 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 1206. In some aspects, the transmission component 1204 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the base station described above. In some aspects, the transmission component 1204 can be co-located with the reception component 1202 in a transceiver of the apparatus 1206. Figure 2 The transmission component 1204 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206. In some aspects, one or more other components of the apparatus 1206 can generate communications and can provide the generated communications to the transmission component 1204 for transmission to the apparatus 1206. In some aspects, the transmission component 1204 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 1206. In some aspects, the transmission component 1204 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the base station described above. In some aspects, the transmission component 1204 can be co-located with the reception component 1202 in a transceiver of the apparatus 1206.

[0214] The determination component 1208 can determine a configuration for the UE to monitor one or more PDCCHs for DCI scheduling PDSCH communications on each carrier included in a set of scheduled carriers and for DCI scheduling PUSCH communications on one or more carriers. In some aspects, the determination component 1208 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above. Figure 2The described receive processor of a base station, transmit MIMO processor, transmit processor, controller / processor, memory, or combination thereof. Transmit component 1204 can transmit a configuration to a UE. Transmit component 1204 can transmit one or more DCIs scheduling PUSCH communications on one or more carriers to the UE according to the configuration.

[0215] Provided are Figure 12 The number and arrangement of components shown in FIG. 12 are Figure 12 There can be additional components, fewer components, different components, or differently arranged components in FIG. 12 than those shown in FIG. 12. Additionally or alternatively, Figure 12 Two or more components illustrated in FIG. 12 can be implemented within a single component, or Figure 12 A single component illustrated in FIG. 12 can be implemented as multiple, distributed components. Additionally or alternatively, Figure 12 A set of one or more components illustrated in FIG. 12 can perform one or more functions described as being performed by another set of one or more components illustrated in FIG. 12. Figure 12

[0216] The following provides an overview of some aspects of the disclosure:

[0217] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) for physical downlink shared channel (PDSCH) communications on each carrier included in a set of scheduled carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications on one or more carriers; monitoring the one or more PDCCHs for DCI according to the configuration; and receiving, based at least in part on the monitoring, DCI scheduling PUSCH communications on the one or more carriers.

[0218] Aspect 2: The method of aspect 1, wherein the set of carriers includes a first carrier associated with a first serving cell and a second carrier associated with a second serving cell.

[0219] Aspect 3: The method of any of aspects 1-2, wherein the configuration indicates a set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers and one or more other sets of PDCCH candidates for DCI scheduling PDSCH communications on one or more other sets of carriers.

[0220] ​Aspect 4: The method of any of aspects 1-3, wherein the configuration indicates at least one of: a search space configuration for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a carrier indicator field (CIF) value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0221] Aspect 5: The method of any of aspects 1-4, wherein the configuration indicates that a downlink carrier is included in the set of carriers and an uplink carrier is included in the set of carriers.

[0222] Aspect 6: The method of aspect 5, wherein monitoring the one or more PDCCHs for DCI in accordance with the configuration comprises monitoring a PDCCH for DCI scheduling PUSCH communications on each carrier included in the set of carriers, and wherein receiving the DCI scheduling the PUSCH communications on the one or more carriers comprises receiving the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0223] Aspect 7: The method of aspect 6, wherein the set of carriers includes a first carrier associated with a first serving cell and a second carrier associated with a second serving cell, and wherein monitoring the PDCCH for DCI scheduling the PUSCH communications on the set of carriers comprises monitoring a PDCCH of the first cell for the DCI scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier, or monitoring a PDCCH of the second cell for the DCI scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier.

[0224] Aspect 8: The method of aspect 6, wherein the DCI scheduling the PUSCH communications on each carrier included in the set of carriers is a multi-carrier scheduling type DCI.

[0225] Aspect 9: The method of any of aspects 5-8, wherein the configuration indicates the DCI for scheduling PDSCH communications on each carrier included in the set of carriers and a set of PDCCH candidates for DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0226] Aspect 10: The method of aspect 9, wherein the configuration indicates a search space configuration for the set of PDCCH candidates.

[0227] Aspect 11 : The method of any of aspects 9-10, wherein the configuration indicates an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and an identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0228] Aspect 12: The method of aspect 11, wherein a payload size of the DCI scheduling PDSCH communications on each carrier included in the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0229] Aspect 13: The method of any of aspects 11-12, wherein receiving the DCI scheduling the PUSCH communications on the one or more carriers comprises receiving a DCI indicating the identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers, and determining, based at least in part on receiving the DCI indicating the identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers, that the DCI is scheduling PUSCH communications on each carrier included in the set of carriers.

[0230] Aspect 14: The method of any of aspects 5-13, wherein the configuration indicates a first set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and a second set of PDCCH candidates for the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0231] Aspect 15: The method of aspect 14, wherein the configuration indicates a first search space configuration for the first set of PDCCH candidates, and a second search space configuration for the second set of PDCCH candidates.

[0232] Aspect 16: The method of aspect 15, wherein monitoring the one or more PDCCHs for DCI according to the configuration comprises monitoring the first set of PDCCH candidates in a first search space configured by the first search space configuration for DCI scheduling PDSCH communications on each carrier included in the set of carriers, and monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration for DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0233] Aspect 17: The method of any of aspects 1-16, wherein the configuration indicates that a downlink carrier is included in the set of carriers and an uplink carrier is included in a subset of carriers of the set of carriers.

[0234] Aspect 18: The method of aspect 17, wherein monitoring the one or more PDCCHs for DCI according to the configuration comprises monitoring a PDCCH for DCI scheduling PUSCH communications on a carrier in the subset of carriers, and receiving the DCI scheduling the PUSCH communications on the one or more carriers comprises receiving DCI scheduling PUSCH communications on a carrier in the subset of carriers.

[0235] Aspect 19: The method of aspect 18, wherein the carrier in the subset of carriers is associated with a first serving cell, and monitoring the PDCCH for DCI scheduling the PUSCH communications on the carrier in the subset of carriers comprises monitoring a PDCCH of a first serving cell for DCI scheduling the PUSCH communications on the carrier in the subset of carriers, or monitoring a PDCCH of a second serving cell for DCI scheduling the PUSCH communications on the carrier in the subset of carriers.

[0236] Aspect 20: The method of any of aspects 17-19, wherein the DCI scheduling the PUSCH communications on each carrier included in the set of carriers is a single-carrier scheduling type DCI.

[0237] Aspect 21 : The method of any of aspects 1-20, wherein monitoring the one or more PDCCHs for DCI in accordance with the configuration comprises monitoring a PDCCH associated with a first serving cell for DCI scheduling PDSCH communications on each carrier included in the set of carriers, monitoring the PDCCH associated with the first serving cell for DCI scheduling PUSCH communications on a carrier associated with the first serving cell, and monitoring a PDCCH associated with a second serving cell for DCI scheduling PUSCH communications on a carrier associated with the second serving cell.

[0238] Aspect 22: The method of any of aspects 1-21, wherein monitoring the one or more PDCCHs for DCI in accordance with the configuration comprises monitoring a PDCCH associated with a first carrier included in the set of carriers for DCI scheduling PDSCH communications on each carrier included in the set of carriers, and monitoring the PDCCH associated with the first carrier for DCI scheduling PUSCH communications on a single carrier included in the set of carriers.

[0239] Aspect 23: The method of aspect 22, wherein the configuration indicates a set of PDCCH candidates associated with the first carrier, wherein the set of PDCCH candidates is associated with DCI scheduling PDSCH communications on each carrier included in the set of carriers, and DCI scheduling PUSCH communications on the single carrier.

[0240] Aspect 24: The method of aspect 23, wherein the configuration indicates a search space configuration associated with the set of PDCCH candidates.

[0241] Aspect 25: The method of any of aspects 23-24, wherein the configuration indicates an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and an identifier associated with the DCI scheduling PUSCH communications on the single carrier.

[0242] Aspect 26: The method of aspect 25, wherein a payload size of the DCI scheduling PDSCH communications on each carrier included in the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on the single carrier.

[0243] Aspect 27: The method of any of aspects 25-26, wherein receiving the DCI scheduling the PUSCH communication on the one or more carriers comprises: receiving a DCI indicating the identifier associated with the DCI scheduling a PUSCH communication on the single carrier; and determining, based at least in part on receiving the DCI indicating the identifier associated with the DCI scheduling a PUSCH communication on the single carrier, that the DCI is scheduling a PUSCH communication on the single carrier.

[0244] Aspect 28: The method of any of aspects 22-27, wherein the configuration indicates a first set of PDCCH candidates associated with the DCI scheduling a PDSCH communication on each carrier included in the set of carriers, and a second set of PDCCH candidates associated with the DCI scheduling a PUSCH communication on the single carrier.

[0245] Aspect 29: The method of aspect 28, wherein the configuration indicates a first search space configuration associated with the first set of PDCCH candidates, and a second search space configuration associated with the second set of PDCCH candidates.

[0246] Aspect 30: The method of aspect 29, wherein monitoring the one or more PDCCHs for DCI in accordance with the configuration comprises: monitoring the first set of PDCCH candidates in a first search space configured by the first search space configuration for DCI scheduling a PDSCH communication on each carrier included in the set of carriers; and monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration for DCI scheduling a PUSCH communication on the single carrier.

[0247] Aspect 31: The method of any of aspects 22-30, wherein the single carrier is a first carrier.

[0248] Aspect 32: The method of aspects 22-30, wherein the single carrier is a second carrier included in the set of carriers.

[0249] Aspect 33: The method of any of aspects 1-32, wherein monitoring the one or more PDCCHs for DCI in accordance with the configuration comprises monitoring a PDCCH associated with a first carrier included in the set of carriers for DCI scheduling PDSCH communications on each carrier included in the set of carriers; monitoring the PDCCH associated with the first carrier for DCI scheduling PUSCH communications on the first carrier; and monitoring the PDCCH associated with the first carrier for DCI scheduling PUSCH communications on a second carrier included in the set of carriers.

[0250] Aspect 34: The method of aspect 33, wherein the configuration indicates a first carrier indicator field (CIF) value associated with DCI scheduling PUSCH communications on the first carrier and a second CIF value associated with the DCI scheduling PUSCH communications on the second carrier.

[0251] Aspect 35: The method of aspect 34, wherein the configuration indicates a third CIF value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0252] Aspect 36: The method of any of aspects 33-35, wherein the first carrier is a scheduling carrier.

[0253] Aspect 37: A method of wireless communication performed by a base station, comprising: determining a configuration for a user equipment (UE) for monitoring one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) scheduling physical downlink shared channel (PDSCH) communications on each carrier included in a set of carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications on one or more carriers; transmitting the configuration to the UE; and transmitting one or more DCIs to the UE scheduling PUSCH communications on the one or more carriers in accordance with the configuration.

[0254] Aspect 38: The method of aspect 37, wherein the base station is associated with a carrier included in the set of carriers.

[0255] Aspect 39: The method of any of aspects 37-38, wherein determining the configuration comprises determining a set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers and one or more other sets of PDCCH candidates for DCI scheduling PDSCH communications on one or more other sets of carriers.

[0256] Aspect 40: The method of any of aspects 37-39, wherein determining the configuration comprises determining at least one of: a search space configuration for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a carrier indicator field (CIF) value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0257] Aspect 41 : The method of any of aspects 37-40, wherein determining the configuration comprises determining that a downlink carrier of the UE comprises the set of carriers and an uplink carrier of the UE comprises the set of carriers.

[0258] Aspect 42: The method of aspect 41, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting DCIs scheduling PUSCH communications on each carrier included in the set of carriers.

[0259] Aspect 43: The method of aspect 42, wherein the base station is associated with a first serving cell and the set of carriers comprises a first carrier associated with the first serving cell and a second carrier associated with a second serving cell, and wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting DCIs scheduling PUSCH communications on the first carrier and scheduling PUSCH communications on the second carrier in a PDCCH of the first cell.

[0260] Aspect 44: The method of aspect 43, wherein the DCIs scheduling the PUSCH communications on each carrier included in the set of carriers are multi-carrier scheduling type DCIs.

[0261] Aspect 45: The method of any of aspects 41 -44, wherein determining the configuration comprises determining the DCIs for scheduling PDSCH communications on each carrier included in the set of carriers and a set of PDCCH candidates for the DCIs for scheduling PUSCH communications on each carrier included in the set of carriers.

[0262] Aspect 46: The method of aspect 45, wherein determining the configuration comprises determining a search space configuration for the set of PDCCH candidates.

[0263] Aspect 47: The method of any of aspects 45-46, wherein determining the configuration comprises determining an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers and determining an identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0264] Aspect 48: The method of aspect 47, wherein a payload size of the DCI scheduling PDSCH communications on the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on the set of carriers.

[0265] Aspect 49: The method of any of aspects 47-48, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting a DCI indicating the identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0266] Aspect 50: The method of any of aspects 41-49, wherein determining the configuration comprises determining a first set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers and determining a second set of PDCCH candidates for the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

[0267] Aspect 51: The method of aspect 50, wherein determining the configuration comprises determining a first search space configuration for the first set of PDCCH candidates and determining a second search space configuration for the second set of PDCCH candidates.

[0268] Aspect 52: The method of aspect 51, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting, for DCI scheduling PDSCH communications on each carrier included in the set of carriers, DCI using the first set of PDCCH candidates of a first search space configured by the first search space configuration; and transmitting, for DCI scheduling PUSCH communications on each carrier included in the set of carriers, DCI using monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration.

[0269] Aspect 53: The method of any of aspects 37-52, wherein determining the configuration comprises determining that a downlink carrier of the UE comprises the set of carriers and that an uplink carrier of the UE comprises a subset of carriers of the set of carriers.

[0270] Aspect 54: The method of Aspect 53, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting DCIs scheduling PUSCH communications on the carriers in the subset of carriers.

[0271] Aspect 55: The method of Aspect 54, wherein the base station is associated with a first serving cell, and wherein transmitting DCIs scheduling PUSCH communications on the carriers in the subset of carriers comprises transmitting, in a PDCCH of the first serving cell, the DCIs scheduling the PUSCH communications on the carriers associated with the first serving cell, or transmitting, in a PDCCH of the first serving cell, the DCIs scheduling PUSCH communications on the carriers associated with a second serving cell.

[0272] Aspect 56: The method of any of Aspects 53-55, wherein the DCIs scheduling the PUSCH communications on each carrier included in the set of carriers are single-carrier scheduling DCIs.

[0273] Aspect 57: The method of any of Aspects 37-56, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting, on a PDCCH associated with the base station, DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and transmitting, on the PDCCH associated with the base station, DCIs scheduling PUSCH communications on carriers associated with the base station.

[0274] Aspect 58: The method of any of Aspects 37-57, wherein transmitting the one or more DCIs scheduling PUSCH communications on the one or more carriers comprises transmitting, in a PDCCH associated with the base station, DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and transmitting, in the PDCCH associated with the base station, DCIs scheduling PUSCH communications on a single carrier included in the set of carriers.

[0275] Aspect 59: The method of Aspect 58, wherein determining the configuration comprises determining a set of PDCCH candidates associated with the PDCCH associated with the base station, and determining that the set of PDCCH candidates is associated with DCIs scheduling PDSCH communications on each carrier included in the set of carriers, and DCIs scheduling PUSCH communications on the single carrier.

[0276] Aspect 60: The method of aspect 59, wherein determining the configuration comprises determining a search space configuration associated with the set of PDCCH candidates.

[0277] Aspect 61 : The method of any of aspects 59-60, wherein determining the configuration comprises determining an identifier associated with the DCI scheduling PDSCH communications on each of the set of carriers, and determining an identifier associated with the DCI scheduling PUSCH communications on the single carrier.

[0278] Aspect 62: The method of aspect 61, wherein a payload size of the DCI scheduling PDSCH communications on each of the set of carriers is the same as a payload size of the DCI scheduling PUSCH communications on the single carrier.

[0279] Aspect 63: The method of any of aspects 61 -62, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises transmitting a DCI indicating the identifier associated with the DCI scheduling PUSCH communications on the single carrier to schedule PUSCH communications on the single carrier, and transmitting a DCI indicating the identifier associated with DCIs scheduling PDSCH communications on each of the set of carriers to schedule PDSCH communications on each of the set of carriers.

[0280] Aspect 64: The method of any of aspects 58-63, wherein determining the configuration comprises determining a first set of PDCCH candidates associated with the DCI scheduling PDSCH communications on each of the set of carriers, and determining a second set of PDCCH candidates associated with the DCI scheduling PUSCH communications on the single carrier.

[0281] Aspect 65: The method of aspect 64, wherein determining the configuration comprises determining a first search space configuration associated with the first set of PDCCH candidates, and determining a second search space configuration associated with the second set of PDCCH candidates.

[0282] Aspect 66: The method of aspect 65, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises: transmitting DCI using the first set of PDCCH candidates of a first search space configured by the first search space configuration for DCI scheduling PDSCH communications on the set of carriers; and transmitting DCI using monitoring the second set of PDCCH candidates in a second search space configured by the second search space configuration for DCI scheduling PUSCH communications on the single carrier.

[0283] Aspect 67: The method of aspects 58-66, wherein the single carrier is a carrier associated with the base station.

[0284] Aspect 68: The method of aspects 58-66, wherein the single carrier is a carrier associated with another base station.

[0285] Aspect 69: The method of any of aspects 37-68, wherein transmitting the one or more DCIs scheduling the PUSCH communications on the one or more carriers comprises: transmitting DCI scheduling PDSCH communications on each carrier included in the set of carriers in a PDCCH associated with the base station; transmitting DCI scheduling PUSCH communications on the carrier associated with the base station in the PDCCH associated with the base station; and transmitting DCI scheduling PUSCH communications on another carrier associated with another base station in the PDCCH associated with the base station.

[0286] Aspect 70: The method of aspect 69, wherein determining the configuration comprises: determining a first carrier indicator field (CIF) value associated with the DCI scheduling PUSCH communications on the carrier associated with the base station; and determining a second CIF value associated with the DCI scheduling PUSCH communications on another carrier associated with another base station.

[0287] Aspect 71: The method of aspect 70, wherein determining the configuration comprises: determining a third CIF value associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

[0288] Aspect 72: An apparatus for wireless communication at a device, comprising a processor, memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-36.

[0289] Aspect 73: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute a method in accordance with one or more aspects of aspects 1-36.

[0290] Aspect 74: An apparatus for wireless communication, comprising at least one means for performing a method in accordance with one or more aspects of aspects 1-36.

[0291] Aspect 75: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method in accordance with one or more aspects of aspects 1-36.

[0292] Aspect 76: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform a method in accordance with one or more aspects of aspects 1-36.

[0293] Aspect 77: An apparatus for wireless communication at a device, comprising a processor, memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method in accordance with one or more aspects of aspects 37-71.

[0294] Aspect 78: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute a method in accordance with one or more aspects of aspects 37-71.

[0295] Aspect 79: An apparatus for wireless communication, comprising at least one means for performing a method in accordance with one or more aspects of aspects 37-71.

[0296] Aspect 80: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method in accordance with one or more aspects of aspects 37-71.

[0297] Aspect 81: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform a method in accordance with one or more aspects of aspects 37-71.

[0298] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made in light of the above disclosure or can be acquired from practice of the aspects.

[0299] As used in this document, the terms "component" and "system" are intended to refer broadly to hardware and / or a combination of hardware and software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used in this document, a processor is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0300] As used in this document, satisfying a threshold can refer to being greater than the threshold, being greater than or equal to the threshold, being less than the threshold, being less than or equal to the threshold, being equal to the threshold, not being equal to the threshold, and / or the like depending on the context.

[0301] Although features can be described or claimed in particular combinations, each combination is not intended to limit the disclosure to that combination. The described features can be combined in ways not listed in order to achieve additional advantages. Although each dependent claim listed below can stand on its own as further applications of the subject matter recited in the main claim, the disclosure is not limited to each and every combination of the dependent claims. The phrase “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any pair or triplet of the same. As another example, “at least one of a, b, or c, or of x, y, or z” is intended to cover a, b, c, x, y, z, a-b, a-c, a-x, a-y, a-z, b-c, b-x, b-y, b-z, c-x, c-y, and c-z, as well as any pair or triplet of the same.

[0302] No element, act or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items unless otherwise clearly indicated by context. Also, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or any variant thereof, are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series relating to items (e.g., “a, b, or c” or “a, b, and c”) unless otherwise indicated by context. In addition, where “or” is used in a list of elements or items, it is intended to mean an inclusive “and / or” unless the context clearly dictates otherwise.

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) capable of scheduling physical downlink shared channel (PDSCH) communications on each carrier included in a set of carriers with multi-carrier scheduling and for DCI scheduling physical uplink shared channel (PUSCH) communications, the configuration indicating a first carrier indicator field (CIF) value corresponding to a first carrier included in the set of carriers, a second CIF value corresponding to a second carrier included in the set of carriers, and a third CIF value corresponding to the first carrier and the second carrier; monitoring, for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a PDCCH associated with the first carrier; and receiving, based at least in part on the monitoring, the DCI scheduling the PUSCH communications.

2. The method of claim 1, wherein, the configuration indicates at least one of: a search space configuration for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers.

3. The method of claim 1, wherein, the configuration indicates that a downlink carrier is included in the set of carriers and an uplink carrier is included in the set of carriers.

4. The method of claim 3, further comprising: monitoring, for the DCI scheduling PUSCH communications on the first carrier and on the second carrier, a PDCCH of a serving cell associated with the second carrier, and wherein receiving the DCI scheduling the PUSCH communications comprises: receiving the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

5. The method of claim 3, wherein, the configuration indicates a set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers and for DCI scheduling PUSCH communications on each carrier included in the set of carriers.

6. The method of claim 5, wherein, the configuration indicates: an identifier associated with the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and an identifier associated with the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

7. The method of claim 3, wherein, the configuration indicates: a first set of PDCCH candidates for the DCI scheduling PDSCH communications on each carrier included in the set of carriers, and a second set of PDCCH candidates for the DCI scheduling PUSCH communications on each carrier included in the set of carriers.

8. The method of claim 1, wherein, The configuration indicates that a downlink carrier comprises the set of carriers and an uplink carrier comprises a subset of carriers of the set of carriers.

9. The method of claim 8, further comprising: monitoring a PDCCH for DCI scheduling a PUSCH communication on a carrier of the subset of carriers, and wherein receiving the DCI scheduling the PUSCH communication comprises: receiving DCI scheduling a PUSCH communication on the carrier of the subset of carriers.

10. The method of claim 1, further comprising: monitoring a PDCCH associated with a first serving cell for DCI scheduling a PUSCH communication on a carrier associated with the first serving cell; and monitoring a PDCCH associated with a second serving cell for DCI scheduling a PUSCH communication on a carrier associated with the second serving cell.

11. The method of claim 1, further comprising: monitoring the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on a single carrier included in the set of carriers.

12. The method of claim 11, wherein, the configuration indicates a set of PDCCH candidates associated with the first carrier, wherein the set of PDCCH candidates is associated with DCI scheduling a PDSCH communication on each carrier included in the set of carriers and DCI scheduling a PUSCH communication on the single carrier.

13. The method of claim 11, wherein, the configuration indicates: a first set of PDCCH candidates associated with DCI scheduling a PDSCH communication on each carrier included in the set of carriers, and a second set of PDCCH candidates associated with DCI scheduling a PUSCH communication on the single carrier.

14. The method of claim 1, further comprising: monitoring the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the first carrier; and monitoring the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the second carrier.

15. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: receive a configuration for monitoring one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) capable of being scheduled with multi-carrier scheduling to schedule a physical downlink shared channel (PDSCH) communication on each carrier included in a set of carriers and for DCI scheduling a physical uplink shared channel (PUSCH) communication, the configuration indicating a first carrier indicator field (CIF) value corresponding to a first carrier included in the set of carriers, a second CIF value corresponding to a second carrier included in the set of carriers, and a third CIF value corresponding to the first carrier and the second carrier; ​ monitor a PDCCH associated with the first carrier for DCI scheduling PDSCH communications on each of the set of carriers; and receive DCI scheduling PUSCH communications based at least in part on the monitoring.

16. The UE of claim 15, wherein, The configuration indicates at least one of: a search space configuration for the DCI scheduling PDSCH communications on each of the set of carriers, a payload size associated with the DCI scheduling PDSCH communications on each of the set of carriers, or a DCI format associated with the DCI scheduling PDSCH communications on each of the set of carriers.

17. The UE of claim 15, wherein, The configuration indicates that a downlink carrier comprises the set of carriers and an uplink carrier comprises the set of carriers.

18. The UE of claim 17, wherein, The instructions are executable to further cause the UE to: monitor a PDCCH associated with the second carrier for DCI scheduling PUSCH communications on the first carrier and on the second carrier, and wherein receiving the DCI scheduling the PUSCH communications comprises: receiving DCI scheduling PUSCH communications on each of the set of carriers.

19. The UE of claim 17, wherein, The configuration indicates a set of PDCCH candidates for the DCI scheduling PDSCH communications on each of the set of carriers and for DCI scheduling PUSCH communications on each of the set of carriers.

20. The UE of claim 19, wherein, The configuration indicates: an identifier associated with the DCI scheduling PDSCH communications on each of the set of carriers, and an identifier associated with the DCI scheduling PUSCH communications on each of the set of carriers.

21. The UE of claim 17, wherein, The configuration indicates: a first set of PDCCH candidates for the DCI scheduling PDSCH communications on each of the set of carriers, and a second set of PDCCH candidates for the DCI scheduling PUSCH communications on each of the set of carriers.

22. The UE of claim 15, wherein, The configuration indicates that a downlink carrier comprises the set of carriers and an uplink carrier comprises a subset of carriers of the set of carriers.

23. The UE of claim 22, wherein, The instructions are executable to further cause the UE to: monitor a PDCCH for DCI scheduling PUSCH communications on a carrier in the subset of carriers, and wherein receiving the DCI scheduling the PUSCH communications comprises: receiving DCI scheduling PUSCH communications on the carrier in the subset of carriers.

24. The UE of claim 15, wherein, The instructions are executable to further cause the UE to: monitor a PDCCH associated with a first serving cell for DCI scheduling PUSCH communications on a carrier associated with the first serving cell; and monitor a PDCCH associated with a second serving cell for DCI scheduling PUSCH communications on a carrier associated with the second serving cell.

25. The UE of claim 15, wherein, The instructions are executable to further cause the UE to: monitor the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the single carrier included in the set of carriers.

26. The UE of claim 25, wherein, The configuration indicates a set of PDCCH candidates associated with the first carrier, where the set of PDCCH candidates are associated with DCI scheduling PDSCH communications on each carrier included in the set of carriers and DCI scheduling a PUSCH communication on the single carrier.

27. The UE of claim 25, wherein, The configuration indicates: a first set of PDCCH candidates associated with DCI scheduling PDSCH communications on each carrier included in the set of carriers, and a second set of PDCCH candidates associated with DCI scheduling a PUSCH communication on the single carrier.

28. The UE of claim 15, wherein, The instructions are executable to further cause the UE to: monitor the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the first carrier; and monitor the PDCCH associated with the first carrier for DCI scheduling a PUSCH communication on the second carrier.

29. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions, when executed by one or more processors of a user equipment (UE), cause the UE to: receive a configuration for monitoring one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) capable of being scheduled with multi-carrier scheduling to schedule physical downlink shared channel (PDSCH) communications on each carrier included in a set of carriers and for DCI scheduling physical uplink shared channel (PUSCH) communications, the configuration indicating a first carrier indicator field (CIF) value corresponding to a first carrier included in the set of carriers, a second CIF value corresponding to a second carrier included in the set of carriers, and a third CIF value corresponding to the first carrier and the second carrier; monitor the PDCCH associated with the first carrier for DCI scheduling PDSCH communications on each carrier included in the set of carriers; and receive, based at least in part on the monitoring, DCI scheduling a PUSCH communication.

30. An apparatus for wireless communication, comprising: means for receiving a configuration to monitor one or more physical downlink control channels (PDCCHs) for downlink control information (DCI) capable of scheduling a physical downlink shared channel (PDSCH) communication on each carrier included in a set of carriers with multi-carrier scheduling, and DCI scheduling a physical uplink shared channel (PUSCH) communication, the configuration indicating a first carrier indicator field (CIF) value corresponding to a first carrier included in the set of carriers, a second CIF value corresponding to a second carrier included in the set of carriers, and a third CIF value corresponding to the first carrier and the second carrier; means for monitoring a PDCCH associated with the first carrier for the DCI scheduling a PDSCH communication on each carrier included in the set of carriers; and means for receiving the DCI scheduling the PUSCH communication based at least in part on the monitoring.

Images