CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63/062,607, entitled “Number of BD and CCE for Cross-Carrier Scheduling from a S-Cell to a P-Cell” and filed on August 7, 2020, and U.S. Patent Application No. 17/356,458, entitled 'Number of BD and CCE for Cross-Carrier Scheduling from a S-Cell to a P-Cell" and filed on June 23, 2021, which are expressly incorporated by reference herein in their entirety.

TECHNICAL FIELD

[0002] The present disclosure relates generally to communication systems, and more particularly, to numbers of blind decodings (BDs) and control channel elements (CCEs) for cross-carrier scheduling from a secondary cell (SCell) to a primary cell (PCell)/primary-secondary cell (P SCell).

INTRODUCTION

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (rnMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In cross-carrier scheduling operations, data may be scheduled from a SCell to either a PCell or a PSCell. In some cases, cross-carrier scheduling may be associated with two scheduling cells that are configured to schedule data on a same PCell/P SCell. While such techniques may increase a number of physical downlink control channel (PDCCH) candidates that may schedule data on the PCell/P SCell, processing capabilities of a user equipment (UE) may limit the number of PDCCH candidates that the UE may be configured to process.

[0007] Accordingly, a total number of PDCCH candidates to be received from the SCell and the PCell/P SCell may need to be regulated based on the processing capabilities of the UE. In a first aspect, e.g., where the SCell and the PCell/PSCell use different numerologies, the maximum number of PDCCH candidates may be based on a predefined budget for the component carrier (CC) with the lowest subcarrier spacing (SCS). That is, the total budget across both CCs may not exceed the budget associated with the lowest SCS. In a second aspect, the maximum number of PDCCH candidates may be counted separately per cell. UE capability information reported to the network may indicate whether the UE is configured to process the number of PDCCH candidates associated with the respective CCs. [0008] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE that includes a memory and at least one processor coupled to the memory. The memory may include instructions that, when executed by the at least one processor, cause the at least one processor to monitor a first PDCCH on a first CC, the first PDCCH being configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC, the first PDCCH having a first subcarrier spacing, the first PDCCH in association with the scheduling of the at least one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs, the first PDCCH having a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs based on the first subcarrier spacing; and monitor a second PDCCH on a second CC different than the first CC concurrently with the monitoring of the first PDCCH, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH having a second subcarrier spacing less than or equal to the first subcarrier spacing, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC being associated with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs, the second PDCCH having a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing, where at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates is less than or equal to N times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs is less than or equal to TV times the second maximum number in association with the second number of non-overlapped CCEs.

[0009] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a base station that includes a memory and at least one processor coupled to the memory. The memory may include instructions that, when executed by the at least one processor, cause the at least one processor to configure a first PDCCH on a first CC for a UE, the first PDCCH being configured to schedule one of a first physical downlink shared channel (PDSCH) or a first PUSCH on a second CC, the first PDCCH having a first subcarrier spacing, the first PDCCH in association with the scheduling of the at least one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs, the first PDCCH having a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs based on the first subcarrier spacing; configure a second PDCCH on a second CC different than the first CC, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, the second PDCCH having a second subcarrier spacing less than or equal to the first subcarrier spacing, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC being associated with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs, the second PDCCH having a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing; and transmit, on at least one of the first PDCCH or the second PDCCH, downlink control information (DCI) scheduling one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC, the DCI being associated with at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates is less than or equal to N times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs is less than or equal to TV times the second maximum number in association with the second number of non-overlapped CCEs.

[0010] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0012] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0013] FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

[0014] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0015] FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

[0016] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0017] FIG. 4 is a call flow diagram illustrating communications between a UE and a base station.

[0018] FIG. 5 is a diagram illustrating cross-carrier scheduling from a secondary cell (SCell) to a primary cell (PCell).

[0019] FIGs. 6A-6B illustrate diagrams associated with determining a number of physical downlink control channel (PDCCH) blind decodings (BDs) and non-overlapping control channel elements (CCEs).

[0020] FIG. 7 is a flowchart of a method of wireless communication to be performed at a UE.

[0021] FIG. 8 is a flowchart of a method of wireless communication to be performed at a base station.

[0022] FIG. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0023] FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

[0024] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0025] 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, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0026] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure . One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0027] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0028] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

[0029] The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., SI interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

[0030] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple- in put and multiple -output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 / UEs 104 may use spectrum up to F MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Fx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respectto DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

[0031] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0032] The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0033] The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NRin an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

[0034] The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are often referredto as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0035] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include midband frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0036] A base station 102, whether a small cell 102' or a large cell (e.g., macro base station), may include and/or be referredto as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

[0037] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182". The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0038] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

[0039] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and aUser Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

[0040] The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, amultimedia device, a video device, adigital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referredto as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0041] Referring again to FIG. 1, in certain aspects, the UE 104 and/or the base station 180 may include a cross-carrier scheduling component 198 configured to monitor concurrently, on different CCs, a first and second PDCCH having different SCSs, each of the PDCCHs being configured to schedule PDSCH or PUSCH on a same CC and being associated with respective maximum numbers of PDCCH candidates or non-overlapped CCEs based on the different SCSs, a sum of respective numbers of PDCCH candidates or non-overlapped CCEs for the respective PDCCHs being less than or equal to N times the lower of the respective maximum numbers. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0042] FIG. 2 A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

[0043] Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC- FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies p 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology p, there are 14 symbols/slot and 2r slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2^ * 15 kHz, where g is the numerology 0 to 4. As such, the numerology p=0 has a subcarrier spacing of 15 kHz and the numerology p=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology p=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology.

[0044] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0045] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0046] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

[0047] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequencydependent scheduling on the UL.

[0048] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

[0049] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0050] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/ demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BP SK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate maybe derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.

[0051] At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

[0052] The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0053] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer ofupper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0054] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0055] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0056] The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. [0057] At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the cross-carrier scheduling component 198 of FIG. 1.

[0058] At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the cross carrier scheduling component 198 of FIG. 1.

[0059] Wireless communication systems may be configured to share available system resources and provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasts, etc.) based on multiple-access technologies such as CDMA systems, TDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, TD-SCDMA systems, etc. that support communication with multiple users. In many cases, common protocols that facilitate communications with wireless devices are adopted in various telecommunication standards. For example, communication methods associated with eMBB, rnMTC, and URLLC may be incorporated in the 5G NR telecommunication standard, while other aspects may be incorporated in the 4G LTE standard. As mobile broadband technologies are part of a continuous evolution, further improvements in mobile broadband remain useful to continue the progression of such technologies.

[0060] FIG. 4 is a call flow diagram 400 illustrating communications between a UE 402 and a base station 404. At 406, the UE 402 may transmit UE capability information to the base station 404. For example, the UE 402 may transmit an indication of processing capabilities of the UE 402 for a number of blind decodes (BDs) and/or a number of CCEs. The processing capabilities may be indicated based on N times a maximum number of PDCCH candidates (e.g., N= 1, N> 1, etc.).

[0061] At 410a, the base station 404 may configure a first PDCCH on a first component carrier (CC) for scheduling a first PDSCH or a first PUSCH on a second CC different from the first CC. At 410b, the base station 404 may similarly configure a second PDCCH on a second CC for scheduling the second PDSCH or the second PUSCH on the second CC. In examples, the base station 404 may configure the first PDCCH and the second PDCCH, at 410a-410b, after receiving the UE capability information, at 406.

[0062] At 408a, the UE 402 may monitor for the first PDCCH on the first CC. The first PDCCH may be configured to schedule the first PDSCH or the first PUSCH on the second CC. At 408b, concurrent with the monitoring of the first PDCCH, the UE 402 may monitor for the second PDCCH on the second CC different from the first CC. The second PDCCH may be similarly configured to schedule second PDSCH or second PUSCH on the second CC. At 412, the base station 404 may transmit DCI for scheduling the first/second PDSCH/PUSCH on the second CC, where a sum of PDCCH candidates or non-overlapping CCEs may be less than a predefined threshold.

[0063] FIG. 5 is a diagram 500 illustrating cross-carrier scheduling from a secondary cell (SCell) 504 to a primary cell (PCell) 502. In further configurations, the cross-carrier scheduling may be from the SCell 504 to a primary-secondary cell (P SCell).

[0064] Dynamic spectrum sharing (DSS) in frequency range 1 (FR1) may include PDCCH enhancements for cross-carrier scheduling including a first RAN and to a second RAN. For instance, PDCCH associated with the SCell 504 may be used for scheduling PDSCH or PUSCH, at 508 and 514, on the PCell 502 or on the P SCell. PDCCH scheduling of the PDSCH may occur on multiple cells via a single DCI. In examples, a DCI size may be decreased in association with limiting a number of cells that may be scheduled at a same time to 2 cells. A total PDCCH blind decoding (BD) allocation may not be changed as a result of such operations. Such enhancements are not specific to DSS and may be generally applicable to cross-carrier scheduling in carrier aggregation.

[0065] Operational frequency bands for DSS may be based on lower frequency bands for which an NR system may use a subcarrier spacing (SCS) of 15 kHz. Such carriers may be used as an “anchor” for both LTE UEs and NRUEs to ensure a threshold level of connectivity and coverage. In cases of carrier aggregation, the anchor carrier may correspond to the PCell 502. If the carrier corresponds to a DSS carrier, resource availability may be restricted. Given that an increased number of NR carriers on mid- bands/high bands may not use DSS, cross-carrier scheduling may be enabled from the SCell 504 on a mid-band/high band to the PCell 502. Since the carrier on the mid- band/high band may be based on, e.g., 30 kHz SCS, cross-carrier scheduling from the SCell 504 to the PCell 502/P SCell may correspond to different numerologies between the SCell 504 and the PCell 502/P SCell. Accordingly, cross-carrier scheduling from the SCell 504 to the PCell 502/PSCell may be configured for a SCS of 30 kHz or 15 kHz for the SCell 504 (e.g., the scheduling cell) and a SCS of 15 kHz for the PCell 502/PSCell (e.g., the scheduled cell). [0066] Some cross-carrier scheduling techniques may support different numerologies between the scheduling cell and the scheduled cell. That is, cross-carrier scheduling from the SCell 504 to the PCell 502/PSCell may be based on the different numerologies. In examples, cross-carrier scheduling from the SCell 504 to the PCell 502/PSCell may be used for non-fallback DCI with a carrier indication field (CIF) (e.g., CIF=0) that is monitored on a first UE-specific search space (USS) 510. The cross-carrier scheduling may use the CIF in the DCI to indicate which carrier the DCI may schedule the PDSCH/PUSCH, at 508. The UE may determine PDCCH candidates for the DCI scheduling from the SCell 504 to the PCell 502/PSCell based on a value of n_CI for a hash function unless, e.g., search space sharing is enabled based on UE capabilities and conditions. If the PDSCH of the PCell 502 and the PDCCH of the SCell 504 use different SCSs, a PDSCH preparation time may be provided.

[0067] In cases where there is one scheduling cell for each scheduled cell, common search spaces (CSS) 506 may be located on the PCell 502. Since the CSS 506 of the PCell 502/PSCell may be associated with functionalities such as system information, paging, random access, fallback operations, hypothetical block error rate (BLER) calculations for a radio link failure (RLF)/link recovery (LR) procedure, etc., maintaining the CSS 506 in the PCell 502/PSCell may provide improved functionality. While no more than one scheduling cell (e.g., SCell 504) may be needed for a given scheduled cell (e.g., PCell 502/PSCell), some NR systems may include more than one scheduling cell for the given scheduled cell. In instances where cross-carrier scheduling is configured for performing the DSS operation on the PCell 502/PSCell, one SCell 504 may still be configured as the scheduling cell for the PCell 502/PSCell.

[0068] If unicast data scheduling is available from both the scheduling cell (e.g., SCell 504) and the CSS 506 of the scheduled cell (e.g., PCell 502/PSCell), the UE may not be able to determine from which scheduling cell the UE receives a scheduling grant for PDSCH or PUSCH, at 508, at each scheduling instance. Therefore, the unicast data scheduling may solely be available from the SCell 504. In examples, the UE may be configured to process time -overlapping unicast PDSCH and system information (SI)- radio network temporary identifier (RNTI)(SI-RNTI) PDSCH during paging-RNTI (P-RNTI) triggered SI acquisition for FR1. CSS monitoring may be maintained on the PCell 502/PSCell, so that UE operations associated with system information reception, paging, fallback, RLF, etc. may remain unchanged. DCI with cell-RNTI (C-RNTI) on the CSS 506 of the PCell 502 may be used, e.g., not for unicast data, but for PDCCH ordering.

[0069] The diagram 500 shows an example of the cross-carrier scheduling from the SCell 504 to the PCell 502. More specifically, multiple PDCCH candidates (e.g., BDs) may be associated with both the PCell 502 and the SCell 504. Thus, the SCell 504 may schedule PDSCH or PUSCH, at 508, on the PCell 502 via cross-carrier scheduling. If the CSS 506 is moved to the SCell 504, the PCell 502 may have no associated PDCCH candidates. However, since the PCell 502 provides functionality for UE mobility and coverage, the CSS 506 may be maintained on the PCell 502. Thus, in the diagram 500, the CSS 506 may be maintained on the PCell 502, while the first USS 510 may be located on the SCell 504 for the cross-carrier scheduling. Therefore, PDCCH candidates of the PCell 502 and the SCell 504 may schedule PDSCH or PUSCH, at 508, on the PCell 502. For example, all 8 PDCCH candidates illustrated in the diagram 500 associated with the CSS 506 and the first USS 510 may be used for scheduling data on the PCell 502. A second USS 512 (e.g., with CIF=1) may be located on the SCell 504 for PDCCH candidates of the SCell 504 to schedule PDSCH or PUSCH, at 514, on the SCell 504. For example, the two PDCCH candidates illustrated in the diagram 500 as being associated with the second USS 512 may be used for scheduling data on the SCell 504.

[0070] A number of BDs and a number of CCEs that a UE may process at a same time may be based on certain limitations. For example, the UE may not process more BDs and/or CCEs at one time than a predefined threshold number. In instances where the UE supports the cross-carrier scheduling from the PCell 502 to the SCell 504, there may be one scheduling cell for a given scheduled cell. For example, for the PDSCH or PUSCH, at 514, on the SCell 504 in the diagram 500 there may be one scheduling cell (e.g., the PCell 502). However, for the PDSCH or PUSCH, at 508, on the PCell 502 in the diagram 500 there may be multiple scheduling cells (e.g., the PCell 502 and the SCell 504). Thus, the maximum number of BDs and non-overlapping CCEs may be regulated so that a PDCCH allocation is not exceeded.

[0071] FIGs. 6A-6B illustrate diagrams 600-650 associated with determining a number of PDCCH candidates (e.g., BDs) and a number of non-overlapping CCEs. If two scheduling cells are used for scheduling on the PCell/P SCell, a number of PDCCH BDs/CCEs may be determined based on a count/allocation. That is, the numbers of BDs/CCEs per span/slot may be limited for a given scheduled cell based on processing capabilities of the UE. In the diagram 600, a maximum number of BDs and non-overlapping CCEs may be determined based on a predefined allocation corresponding to the lower SCS (e.g., 15 kHz) of the component carriers (e.g., the lower of a first SCS for the SCell and a second SCS for the PCell/PSCell). In the diagram 650, a maximum number of BDs and non-overlapping CCEs may be determined based on allocations that are separately predefined for the PCell/PSCell and the SCell.

[0072] The two component carriers indicated in the diagrams 600-650 for the SCell and the PCell/PSCell may have different SCSs. For example, a first SCS of the SCell may be 60 kHz and a second SCS of the PCell/PSCell may be 15 kHz. Based on the different SCSs of the respective component carriers, the PDCCH monitoring occasions may be different for the first component carrier and the second component carrier. For example, the PCell/PSCell may be associated with one monitoring occasion per slot, whereas the SCell may be associated with four monitoring occasions per slot. The PDCCH monitoring occasions for the PCell/PSCell may be associated with PDCCH candidates received from the CSS and the PDCCH monitoring occasions for the SCell may be associated with PDCCH candidates received from the USS.

[0073] In the diagram 600, the numbers of BDs and non-overlapping CCEs per span/slot may be counted over the data scheduling cell for the PCell/PSCell. The counted number of BDs and non-overlapping CCEs may not be more than the predefined allocation per span/slot per component carrier (e.g., there may be no overscheduling of the PDCCH). In examples, a BD allocation per span/slot per component carrier may be up to 44 BDs for a 15 kHz carrier. As such, 44 BDs may be the BD allocation (e.g., the maximum number that may not be exceeded) over the carrier for the PCell/PSCell.

[0074] If the scheduling cell (e.g., SCell) and the scheduled cell (e.g., PCell/PSCell) use different numerologies, the per span/slot threshold may be determined based on the lower SCS (e.g., the per span/slot having the component carrier with the lower SCS). In the diagram 600, the per span/slot threshold of the component carrier with the lowest SCS may correspond to the 15 kHz carrier (e.g., the span/slot of the PDCCH monitoring occasion for the PCell/PSCell). The number of BDs across the PCell/PSCell and the SCell may not exceed the lower BD allocation of the multiple scheduling carriers. In this manner, the BD allocation may be capped based on a per cell budget, even though the number of BDs may extend across the multiple scheduling carriers. [0075] In the diagram 650, the number of BDs or non-overlapping CCEs may be defined per scheduling cell, including data scheduling on the PCell/PSCell. That is, the number of BDs or non-overlapping CCEs may be counted separately per cell. For example, the PDCCH monitoring occasion for the PCell/PSCell may have up to 44 PDCCH candidates (e.g., BDs) and the PDCCH monitoring occasion for the SCell may have up to 44 PDCCH candidates. The UE may report UE capability information to the network indicative of whether the UE is configured to process 88 PDCCH candidates (e.g., 44 + 44) or whether the UE is solely configured, e.g., to process up to 44 PDCCH candidates over all of the carriers.

[0076] Accordingly, the numbers of BDs and non-overlapping CCEs per span/slot may be counted per scheduling cell for scheduling the PCell/PSCell. The counted number of BDs and non-overlapping CCEs for a given scheduling cell per span/slot may not be more than a predefined allocation per span/slot per carrier. While the diagram 650 similarly indicates that there may be no PDCCH overscheduling, the per carrier allocation in the diagram 650 may be available for each of the scheduling cells. The UE may be configured to report UE capability information regarding the number of BD and non-overlapping CCEs per span/slot for the PCell/PSCell, such that configurations having the total number of BDs/non-overlapping CCEs over the carriers per span/slot for the PCell/PSCell may not exceed the predetermined allocations per span/slot per carrier.

[0077] The UE may report the processing capability of the UE to the network via capability signalling. In examples, if the UE reports the value N via the capability signalling where, e.g., A may be determined based on a hash function, the UE may support a total number of BDs/non-overlapping CCEs over the carriers per span/slot for the PCell/PSCell of up to A times the predetermined allocations per span/slot per carrier. For example, if the UE reports A=2, the UE may support 44 + 44 BDs/non- overlapping CCEs. If the UE reports A=l, the UE may support a total number of BDs/non-overlapping CCEs over the carriers per span/slot for the PCell/PSCell that is not more than the predetermined allocations per span/slot per carrier (e.g., 44 PDCCH candidates over the carriers).

[0078] FIG. 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a UE, e.g., the UE 104, which may include the memory 360 and which may be the entire UE 104 or a component of the UE 104, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359. [0079] At 701, the UE may transmit capability information in association with concurrent monitoring of a first PDCCH and a second PDCCH. For example, referring to FIG. 4, the UE 402 may transmit, at 406, UE capability information to the base station 404. The capability information may indicate a value for N, where N > 1.

[0080] At 702, the UE may monitor a first PDCCH on a first CC. For example, referring to FIG. 4, the UE 402 may monitor, at 408a, a first PDCCH on the first CC.

[0081] At 702a, the first PDCCH may be configured to schedule one of a first PDSCH or a first PUSCH on a second CC. For example, referring to FIG. 5, the PDCCH associated with the SCell may be configured to schedule PDSCH or PUSCH on the PCell.

[0082] At 702b, the first PDCCH may have a first subcarrier spacing. For example, referring to FIGs. 6A-6B, the SCS of the SCell may be 60 kHz.

[0083] At 702c, the first PDCCH in association with the scheduling of the at least one of the first PDSCH or the first PUSCH on the second CC may be associated with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs. For example, referring to FIGs. 5 and 6A-6B, the PDCCH associated with the cross-carrier scheduling of the PDSCH/PUSCH from the SCell to the PCell may be further associated with a number of BDs in a PDCCH monitoring occasion or a number of non-overlapping CCEs, as indicated in the diagrams 600-650.

[0084] At 702d, the first PDCCH may have a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of nonoverlapped CCEs based on the first subcarrier spacing. For example, referring to FIG. 6B, the diagram 650 indicates that the number of BDs and non-overlapping CCEs for the SCell may not exceed a defined budget of the SCell based on the SCS of 60 kHz.

[0085] At 704, the UE may monitor a second PDCCH on a second CC different than the first CC concurrently with the monitoring of the first PDCCH. For example, referring to FIG. 4, the UE 402 may monitor, at 408b, a second PDCCH on a second CC different from the first CC. The monitoring, at 408b, for the second PDCCH may be performed concurrently with the monitoring, at 408a, for the first PDCCH. As illustrated in the diagrams 600-650, the first CC may be associated with the SCell and the second CC may be associated with one of the PCell or the P SCell. In aspects, the first CC and the second CC may be in different frequency bands. For example, the first CC may be associated with a higher frequency range than the second CC. [0086] At 704a, the second PDCCH may be configured to schedule one of a second PDSCH or a second PUSCH on the second CC. For example, referring to FIG. 5, the PDCCH associated with the PCell may be configured to schedule PDSCH or PUSCH on the PCell.

[0087] At 704b, the second PDCCH may have a second subcarrier spacing less than or equal to the first subcarrier spacing. For example, referring to FIGs. 6A-6B, the SCS of the PCell may be 15 kHz, which is less than the SCS of the SCell (e.g., 60 kHz). That is, the second subcarrier spacing may be less than the first subcarrier spacing.

[0088] At 704c, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC may be associated with at least one of a second number of PDCCH candidates or a second number of nonoverlapped CCEs. For example, referring to FIGs. 5 and 6A-6B, the PDCCH associated with the PDSCH/PUSCH of the PCell may be further associated with a number of BDs in a PDCCH monitoring occasion or a number of non-overlapping CCEs, as indicated in the diagrams 600-650.

[0089] At 704d, the second PDCCH may have a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing. For example, referring to FIG. 6B, the diagram 650 indicates that the number of BDs and non-overlapping CCEs for the PCell may not exceed a defined budget of the PCell based on the SCS of 15 kHz.

[0090] At 706, a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates may be less than or equal to N times the second maximum number in association with the second number of PDCCH candidates. For example, if the maximum number of PDCCH candidates is 44, referring to FIGs. 6A-6B, N times the total number of PDCCH candidates associated with the PCell and the SCell may be less than 44. In aspects, the value of N may be A=l. As a result, the total number of PDCCH candidates associated with the PCell and the SCell may not be more than 44. Additionally or alternatively, at 706, a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs may be less than or equal to N times the second maximum number in association with the second number of non-overlapped CCEs.

[0091] FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a base station, e.g., the base station 102, which may include the memory 376 and which may be the entire base station 102 or a component of the base station 102, such as the TX processor 316, the RX processor 370, and/or the controller/processor 375.

[0092] At 801, the base station may receive, from a UE, capability information in association with configuration of a first PDCCH and a second PDCCH. For example, referring to FIG. 4, the base station 404 may receive, at 406, UE capability information from the UE 402. The capability information may indicate a value for TV, where N> 1.

[0093] At 802, the base station may configure a first PDCCH on a first CC for a UE. For example, referring to FIG. 4, the base station 404 may configure, at 410a, a first PDCCH on the first CC for the UE 402.

[0094] At 802a, the first PDCCH may be configured to schedule one of a PDSCH or a first PUSCH on a second CC. For example, referring to FIG. 5, the PDCCH associated with the SCell may be configured to schedule PDSCH or PUSCH on the PCell.

[0095] At 802b, the first PDCCH may have a first subcarrier spacing. For example, referring to FIGs. 6A-6B, the SCS of the SCell may be 60 kHz.

[0096] At 802c, the first PDCCH in association with the scheduling of the at least one of the first PDSCH or the first PUSCH on the second CC may be associated with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs. For example, referring to FIGs. 5 and 6A-6B, the PDCCH associated with the cross-carrier scheduling of the PDSCH/PUSCH from the SCell to the PCell may be further associated with a number of BDs in a PDCCH monitoring occasion or a number of non-overlapping CCEs, as indicated in the diagrams 600-650.

[0097] At 802d, the first PDCCH may have a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of nonoverlapped CCEs based on the first subcarrier spacing. For example, referring to FIG. 6B, the diagram 650 indicates that the number of BDs and non-overlapping CCEs for the SCell may not exceed a defined budget of the SCell based on the SCS of 60 kHz.

[0098] At 804, the base station may configure a second PDCCH on a second CC different than the first CC, the second PDCCH being concurrent with the first PDCCH. For example, referring to FIG. 4, the base station 404 may configure, at 410b, a second PDCCH on a second CC for the UE 402 for scheduling a second PDSCH/second PUSCH on the second CC. As illustrated in the diagrams 600-650, the first CC may be associated with the SCell and the second CC may be associated with one of the PCell or the P SCell. In aspects, the first CC and the second CC may be in different frequency bands. For example, the first CC may be associated with a higher frequency range than the second CC.

[0099] At 804a, the second PDCCH may be configured to schedule one of a second PDSCH or a second PUSCH on the second CC. For example, referring to FIG. 5, the PDCCH associated with the PCell may be configured to schedule PDSCH or PUSCH on the PCell.

[0100] At 804b, the second PDCCH may have a second subcarrier spacing less than or equal to the first subcarrier spacing. For example, referring to FIGs. 6A-6B, the SCS of the PCell may be 15 kHz, which is less than the SCS of the SCell (e.g., 60 kHz). That is, the second subcarrier spacing may be less than the first subcarrier spacing.

[0101] At 804c, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC may be associated with at least one of a second number of PDCCH candidates or a second number of nonoverlapped CCEs. For example, referring to FIGs. 5 and 6A-6B, the PDCCH associated with the PDSCH/PUSCH of the PCell may be further associated with a number of BDs in a PDCCH monitoring occasion or a number of non-overlapping CCEs, as indicated in the diagrams 600-650.

[0102] At 804d, the second PDCCH may have a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing. For example, referring to FIG. 6B, the diagram 650 indicates that the number of BDs and non-overlapping CCEs for the PCell may not exceed a defined budget of the PCell based on the SCS of 15 kHz.

[0103] At 806, the base station may transmit, on at least one of the first PDCCH or the second PDCCH, DCI scheduling one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC. For example, referring to FIG. 4, the base station 404 may transmit, at 412, DCI scheduling first/second PDSCH/PUSCH on the second CC. The sum of the PDCCH candidates and/or nonoverlapping CCEs transmitted, at 412, may be less than a predefined threshold.

[0104] At 808, the DCI may be associated with a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates, where the first sum may be less than or equal to N times the second maximum number in association with the second number of PDCCH candidates. For example, if the maximum number of PDCCH candidates is 44, referring to FIGs. 6A-6B, N times the total number of PDCCH candidates associated with the PCell and the SCell may be less than 44. In aspects, the value of N may be 7V=1. As a result, the total number of PDCCH candidates associated with the PCell and the SCell may not be more than 44. Additionally or alternatively, at 808, the DCI may be associated with a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs, where the second sum may be less than or equal to N times the second maximum number in association with the second number of non-overlapped CCEs.

[0105] FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902. The apparatus 902 is a UE and includes a cellular baseband processor 904 (also referred to as a modem) coupled to a cellular RF transceiver 922 and one or more subscriber identity modules (SIM) cards 920, an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910, a Bluetooth module 912, a wireless local area network (WLAN) module 914, a Global Positioning System (GPS) module 916, and a power supply 918. The cellular baseband processor 904 communicates through the cellular RF transceiver 922 with the UE 104 and/or BS 102/180. The cellular baseband processor 904 may include a computer-readable medium /memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 904, causes the cellular baseband processor 904 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor 904 when executing software. The cellular baseband processor 904 further includes a reception component 930, a communication manager 932, and a transmission component 934. The communication manager 932 includes the one or more illustrated components. The components within the communication manager 932 may be stored in the computer- readable medium / memory and/or configured as hardware within the cellular baseband processor 904. The cellular baseband processor 904 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 902 may be a modem chip and include just the baseband processor 904, and in another configuration, the apparatus 902 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 902. [0106] The communication manager 932 includes a monitor component 940 that is configured, e.g., as described in connection with 702 and 704, to monitor a first PDCCH on a first CC; and monitor a second PDCCH on a second CC different than the first CC concurrently with the monitoring of the first PDCCH. The transmission component 934 is configured, e.g., as described in connection with 701, to transmit capability information in association with the concurrent monitoring of the first PDCCH and the second PDCCH.

[0107] The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIG. 7. As such, each block in the aforementioned flowcharts of FIG. 7 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

[0108] In one configuration, the apparatus 902, and in particular the cellular baseband processor 904, includes means for monitoring a first physical downlink control channel (PDCCH) on a first component carrier (CC), the first PDCCH being configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC, the first PDCCH having a first subcarrier spacing, the first PDCCH in association with the scheduling of the one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first number of PDCCH candidates or a first number of nonoverlapped control channel elements (CCEs), the first PDCCH having a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs based on the first subcarrier spacing; and means for monitoring a second PDCCH on a second CC different than the first CC concurrently with the monitoring of the first PDCCH, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH having a second subcarrier spacing less than or equal to the first subcarrier spacing, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC being associated with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs, the second PDCCH having a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing, where at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates is less than or equal to N times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs is less than or equal to TV times the second maximum number in association with the second number of non-overlapped CCEs. The aforementioned means may be one or more of the aforementioned components of the apparatus 902 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 902 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

[0109] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1002. The apparatus 1002 is a BS and includes a baseband unit 1004. The baseband unit 1004 may communicate through a cellular RF transceiver with the UE 104. The baseband unit 1004 may include a computer-readable medium / memory. The baseband unit 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1004, causes the baseband unit 1004 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit 1004 when executing software. The baseband unit 1004 further includes a reception component 1030, a communication manager 1032, and a transmission component 1034. The communication manager 1032 includes the one or more illustrated components. The components within the communication manager 1032 may be stored in the computer- readable medium / memory and/or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

[0110] The communication manager 1032 includes a configuration component 1040 that is configured, e.g., as described in connection with 802 and 804, to configure a first PDCCH on a first CC for a UE; and configure a second PDCCH on a second CC different than the first CC. The transmission component 1034 is configured, e.g., as described in connection with 806, to transmit, on at least one of the first PDCCH or the second PDCCH, DCI scheduling one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC.

[0111] The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIG. 8. As such, each block in the aforementioned flowcharts of FIG. 8 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

[0112] In one configuration, the apparatus 1002, and in particular the baseband unit 1004, includes means for configuring a first physical downlink control channel (PDCCH) on a first component carrier (CC) for a user equipment (UE), the first PDCCH being configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC, the first PDCCH having a first subcarrier spacing, the first PDCCH in association with the scheduling of the one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first number of PDCCH candidates or a first number of nonoverlapped control channel elements (CCEs), the first PDCCH having a first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs based on the first subcarrier spacing; means for configuring a second PDCCH on a second CC different than the first CC, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, the second PDCCH having a second subcarrier spacing less than or equal to the first subcarrier spacing, the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC being associated with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs, the second PDCCH having a second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs based on the second subcarrier spacing; and means for transmitting, on at least one of the first PDCCH or the second PDCCH, downlink control information (DCI) scheduling one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC, the DCI being associated with at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates is less than or equal to TV times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs is less than or equal to N times the second maximum number in association with the second number of nonoverlapped CCEs. The aforementioned means may be one or more of the aforementioned components of the apparatus 1002 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 1002 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

[0113] Accordingly, a total number of PDCCH candidates to be received from the SCell and the PCell/P SCell may need to be regulated based on the processing capabilities of the UE. In a first aspect, e.g., where the SCell and the PCell/PSCell use different numerologies, the maximum number of PDCCH candidates may be based on a predefined budget for the CC with the lowest SCS. That is, the total budget across both CCs may not exceed the budget associated with the lowest SCS. In a second aspect, the maximum number of PDCCH candidates may be counted separately per cell. UE capability information reported to the network may indicate whether the UE is configured to process the number of PDCCH candidates associated with the respective CCs.

[0114] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented. [0115] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0116] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation. [0117] Aspect 1 is an apparatus for wireless communication to be performed at a UE including at least one processor coupled to a memory and configured to monitor a first PDCCH on a first CC, the first PDCCH being configured to schedule one of a first PDSCH or a first PUSCH on a second CC, the first PDCCH having a first maximum number in association with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs; and monitor a second PDCCH on a second CC different than the first CC concurrently with the monitoring of the first PDCCH, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH having a second maximum number in association with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs, at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates is less than or equal to N times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs is less than or equal to A times the second maximum number in association with the second number of non-overlapped CCEs.

[0118] Aspect 2 may be combined with aspect 1 and includes that the first PDCCH in association with the scheduling of the one of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs, and the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs.

[0119] Aspect 3 may be combined with any of aspects 1-2 and includes that the first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing that is less than or equal to the first subcarrier spacing.

[0120] Aspect 4 may be combined with any of aspects 1-3 and includes that the first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs is based on the first subcarrier spacing, and the second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs is based on the second subcarrier spacing. [0121] Aspect 5 may be combined with any of aspects 1-4 and includes that the first CC is associated with an SCell, and the second CC is associated with one of a PCell or a PSCell.

[0122] Aspect 6 may be combined with any of aspects 1-5 and includes that the first CC and the second CC are in different frequency bands.

[0123] Aspect 7 may be combined with any of aspects 1-6 and includes that the first CC is associated with a higher frequency range than the second CC.

[0124] Aspect 8 may be combined with any of aspects 1-7 and includes that A is a multiplier associated with a processing capability of the UE to process at least one of a total number of PDCCH candidates or a total number of non-overlapped CCEs, the total number of PDCCH candidates including the first number of PDCCH candidates and the second number of PDCCH candidates, the total number of non-overlapped CCEs including the first number of non-overlapped CCEs and the second number of nonoverlapped CCEs.

[0125] Aspect 9 may be combined with any of aspects 1-8 and includes that N = 1.

[0126] Aspect 10 may be combined with any of aspects 1-9 and includes that the at least one processor is further configured to transmit capability information in association with the concurrent monitoring of the first PDCCH and the second PDCCH, the capability information indicating a value for A, where N > 1.

[0127] Aspect 11 is an apparatus for wireless communication to be performed at a base station including at least one processor coupled to a memory and configured to configure a first PDCCH on a first CC for a UE, the first PDCCH being configured to schedule one of a first PDSCH or a PUSCH on a second CC, the first PDCCH having a first maximum number in association with at least one of a first number of PDCCH candidates or a first number of non-overlapped CCEs; configure a second PDCCH on a second CC different than the first CC, the second PDCCH being configured to schedule one of a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, the second PDCCH having a second maximum number in association with at least one of a second number of PDCCH candidates or a second number of non-overlapped CCEs; and transmit, on at least one of the first PDCCH or the second PDCCH, DCI scheduling one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC, the DCI associated with at least one of a first sum of the first number of PDCCH candidates and the second number of PDCCH candidates being less than or equal to N times the second maximum number in association with the second number of PDCCH candidates, or a second sum of the first number of non-overlapped CCEs and the second number of non-overlapped CCEs being less than or equal to N times the second maximum number in association with the second number of non-overlapped CCEs.

[0128] Aspect 12 may be combined with aspect 11 and includes that the first PDCCH in association with the scheduling of the one of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs, and the second PDCCH in association with the scheduling of the at least one of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs.

[0129] Aspect 13 may be combined with any of aspects 11-12 and includes that the first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing that is less than or equal to the first subcarrier spacing.

[0130] Aspect 14 may be combined with any of aspects 11-13 and includes that the first maximum number in association with the at least one of the first number of PDCCH candidates or the first number of non-overlapped CCEs is based on the first subcarrier spacing, and the second maximum number in association with the at least one of the second number of PDCCH candidates or the second number of non-overlapped CCEs is based on the second subcarrier spacing.

[0131] Aspect 15 may be combined with any of aspects 11-14 and includes that the first CC is associated with an SCell, and the second CC is associated with one of a PCell or a PSCell.

[0132] Aspect 16 may be combined with any of aspects 11-15 and includes that the first CC and the second CC are in different frequency bands.

[0133] Aspect 17 may be combined with any of aspects 11-16 and includes that the first CC is associated with a higher frequency range than the second CC.

[0134] Aspect 18 may be combined with any of aspects 11-17 and includes that A is a multiplier associated with a processing capability of the UE to process at least one of a total number of PDCCH candidates or a total number of non-overlapped CCEs, the total number of PDCCH candidates including the first number of PDCCH candidates and the second number of PDCCH candidates, the total number of non-overlapped CCEs including the first number of non-overlapped CCEs and the second number of non-overlapped CCEs.

[0135] Aspect 19 may be combined with any of aspects 11-18 and includes that N = 1.

[0136] Aspect 20 may be combined with any of aspects 11-19 and includes that the at least one processor is further configured to receive, from the UE, capability information in association with concurrent configuration of the first PDCCH and the second PDCCH, the capability information indicating a value for N, where N> 1.

[0137] Aspect 21 may be combined with any of aspects 1-20 and further includes that a transceiver is coupled to the at least one processor.

[0138] Aspect 22 is a method of wireless communication for implementing any of aspects 1- 21.

[0139] Aspect 23 is an apparatus for wireless communication including means for implementing any of aspects 1-21.

[0140] Aspect 24 is a computer-readable medium storing computer executable code, the code when executed by at least one processor causes the atleast one processor to implement any of aspects 1-21.