Number of BDs and CCEs for cross-carrier scheduling from S-CELL to P-CELL

Abstract

The present disclosure provides systems, devices, apparatuses, and methods, including computer programs encoded on storage media, for determining a number of BDs and CCEs for cross-carrier scheduling from an SCell to a PCell / PSCell. A UE can concurrently monitor a first PDCCH and a second PDCCH with different SCSs on different component carriers. The PDCCHs can each be configured to schedule a PDSCH or a PUSCH on a same component carrier of the different component carriers. Each of the PDCCHs can be associated with a respective number of PDCCH candidates or a respective number of non-overlapping CCEs, the respective numbers further associated with respective maximum numbers based on the different SCSs. A first sum of the respective numbers of PDCCH candidates or a second sum of the respective numbers of non-overlapping CCEs can be less than or equal to N times a lower one of the respective maximum numbers.

Description

[0001] Cross-references to related applications

[0002] This application claims the rights and priorities of the following applications: U.S. Provisional Application No. 63 / 062,607, filed August 7, 2020, entitled “Number of BD and CCE for Cross-Carrier Scheduling from a S-Cell to a P-Cell”, and U.S. Patent Application No. 17 / 356,458, filed June 23, 2021, entitled “Number of BD and CCE for Cross-Carrier Scheduling from a S-Cell to a P-Cell”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] In summary, this disclosure relates to communication systems, and more specifically, to the number of blind decoding (BD) and control channel elements (CCE) for cross-carrier scheduling from secondary cell (SCell) to primary cell (PCell) / primary-secondary cell (PSCell). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in the case of the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a general summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict 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 descriptions given later.

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

[0008] Therefore, it may be necessary to adjust the total number of PDCCH candidates to be received from the SCell and PCell / PSCell based on the UE's processing capabilities. In a first aspect, for example, when the SCell and PCell / PSCell use different digital schemes, the maximum number of PDCCH candidates can be based on a predefined budget for the component carrier (CC) with the lowest subcarrier spacing (SCS). That is, the total budget across the two CCs may not exceed the budget associated with the lowest SCS. In a second aspect, the maximum number of PDCCH candidates can be counted individually per cell. UE capability information reported to the network can indicate whether the UE is configured to process the number of PDCCH candidates associated with the corresponding CC.

[0009] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE, including a memory and at least one processor coupled to the memory. The memory may include instructions, when executed by the at least one processor, causing 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 associated with the scheduling of at least one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first PDCCH candidate number or a first non-overlapping CCE number, the first PDCCH having a first maximum number associated with the at least one of the first PDCCH candidate number or the first non-overlapping CCE number based on the first subcarrier spacing; and concurrently with monitoring the first PDCCH, monitoring a second PDCCH on a second CC different from the first CC, the second PDCCH being configured to schedule the second PDCCH. One of a second PDSCH or a second PUSCH on the CC, the second PDCCH having a second subcarrier spacing less than or equal to the first subcarrier spacing, the second PDCCH associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC being associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, the second PDCCH having a second maximum number associated with the at least one of the second PDCCH candidate number or the second non-overlapping CCE number based on the second subcarrier spacing, wherein at least one of the following conditions exists: a first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number, or a second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

[0010] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a base station including a memory and at least one processor coupled to the memory. The memory may include instructions, when executed by the at least one processor, causing the at least one processor to perform the following operations: Configure a first PDCCH for the UE on a first CC, the first PDCCH being configured to schedule either 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 associated with the scheduling of at least one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first PDCCH candidate number or a first non-overlapping CCE number, the first PDCCH having a first maximum number associated with the at least one of the first PDCCH candidate number or the first non-overlapping CCE number based on the first subcarrier spacing; Configure a second PDCCH on a second CC different from the first CC, the second PDCCH being configured to schedule either 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 associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number, the second PDCCH having a second maximum number associated with the at least one of the second PDCCH candidate number or the second non-overlapping CCE number based on the second subcarrier interval; and transmitting downlink control information (DCI) on at least one of the first PDCCH or the second PDCCH, the 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 the following: a first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number, or a second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0012] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A This is a schematic diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0014] Figure 2B This is a schematic diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is a schematic diagram illustrating an example of a second frame according to various aspects of this disclosure.

[0016] Figure 2D This is a schematic diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a schematic diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0018] Figure 4 This is a call flow diagram illustrating the communication between the UE and the base station.

[0019] Figure 5 This is a schematic diagram illustrating cross-carrier scheduling from the secondary cell (SCell) to the primary cell (PCell).

[0020] Figures 6A-6B A schematic diagram is shown that relates to the number of blind decoding (BD) and non-overlapping control channel elements (CCE) for determining the physical downlink control channel (PDCCH).

[0021] Figure 7 This is a flowchart of the wireless communication method to be performed at the UE.

[0022] Figure 8 This is a flowchart of a wireless communication method to be performed at a base station.

[0023] Figure 9 This is a schematic diagram illustrating an example of the hardware implementation used for the example device.

[0024] Figure 10This is a schematic diagram illustrating an example of the hardware implementation used for the example device. Detailed Implementation

[0025] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing only the configurations in which the concepts described herein can be implemented. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0026] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings, by way of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] For example, an element, or any part of an element, or any combination of elements, can 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, system-on-a-chip (SoCs), 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 functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

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

[0029] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0030] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0031] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to restricted groups referred to as closed subscriber groups (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth allocated to each carrier in carrier aggregation for transmission in each direction. Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0032] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0033] The wireless communication system may also include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, 5 GHz unlicensed spectrum. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0034] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0035] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0036] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

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

[0038] Base station 180 may transmit beamforming signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamforming signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 may receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0039] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for the provisioning and delivery of MBMS user services. The BM-SC 170 can act as an entry point for MBMS transmissions for content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0040] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0041] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver functional unit, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0042] Refer again Figure 1 In some aspects, UE 104 and / or base station 180 may include a cross-carrier scheduling component 198 configured to concurrently monitor a first PDCCH and a second PDCCH with different SCSs on different CCs. Each of these PDCCHs is configured to schedule a PDSCH or PUSCH on the same CC and is associated with a corresponding maximum number of PDCCH candidates or non-overlapping CCEs based on different SCSs, wherein the sum of the corresponding numbers of PDCCH candidates or non-overlapping CCEs for a corresponding PDCCH is less than or equal to N times the lower of the corresponding maximum numbers. Although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0043] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G NR frame structure. Figure 2B This is a schematic diagram 230 illustrating an example of a DL channel within a 5G NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2DThis is a schematic diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Multiplexing (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or Time Division Multiplexing (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , 2C In the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (with full UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0044] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μEach time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 2A-2D Examples are provided for slot configuration 0 with 14 symbols per slot and a digital scheme μ=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 μs. Within a frame set, one or more distinct bandwidth portions (BWPs) can exist that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme.

[0045] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which 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.

[0046] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0047] Figure 2BExamples of various DL channels within a subframe of a frame are shown. 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 comprising six RE Groups (REGs), each REG comprising 12 consecutive REs of an RB in an OFDM symbol. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on a CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) (which carries the Master Information Block (MIB)) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0048] like Figure 2C As shown, some REs in the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first one or two symbols before the PUSCH. PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0049] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0050] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), 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 functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0051] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived based on a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0052] At UE 350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on this information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. This data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

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

[0054] Similar to the functions described in the DL transmission performed in conjunction with base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0055] The TX processor 368 can use the channel estimate derived by the channel estimator 358 based on a reference signal or feedback transmitted by the base station 310 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

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

[0057] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection to support HARQ operation using ACK and / or NACK protocols.

[0058] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The cross-carrier scheduling component 198 relates to various aspects.

[0059] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The cross-carrier scheduling component 198 relates to various aspects.

[0060] Wireless communication systems can be configured to share available system resources and provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, TD-SCDMA, etc.). In many cases, common protocols that facilitate communication with wireless devices are adopted across various telecommunications standards. For example, communication methods associated with eMBB, mMTC, and URLLC can be incorporated into the 5G NR telecommunications standard, while others can be incorporated into the 4G LTE standard. As mobile broadband technology is part of continuous evolution, further improvements to mobile broadband remain useful for the continued development of such technologies.

[0061] Figure 4 This is a call flow diagram 400 illustrating communication between UE 402 and base station 404. At 406, UE 402 may send UE capability information to base station 404. For example, UE 402 may send an indication of its processing capacity for the number of blind decoding (BD) and / or CCE. The processing capacity may be indicated based on N times the maximum number of PDCCH candidates (e.g., N = 1, N ≥ 1, etc.).

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

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

[0064] Figure 5 This is a schematic diagram 500 illustrating cross-carrier scheduling from secondary cell (SCell) 504 to primary cell (PCell) 502. In a further configuration, cross-carrier scheduling can be from SCell 504 to primary and secondary cells (PSCell).

[0065] Dynamic Spectrum Sharing (DSS) in Frequency Range 1 (FR1) may include PDCCH enhancements for cross-carrier scheduling, including both the first and second RANs. For example, the PDCCH associated with SCell 504 may be used to schedule PDSCH or PUSCH on PCell 502 or PSCell (at 508 and 514). PDSCH PDCCH scheduling may occur across multiple cells via a single DCI. In various examples, the DCI size may be reduced in association with limiting the number of cells that can be scheduled simultaneously to two cells. The total PDCCH blind decoding (BD) allocation may not be altered as a result of such operations. This enhancement is not specific to DSS and can generally be applied to cross-carrier scheduling in carrier aggregation.

[0066] The operating frequency band used for DSS can be based on a lower frequency band, for which the NR system can use a 15kHz subcarrier spacing (SCS). Such a carrier can be used as an "anchor" for both LTE and NR UEs to ensure threshold-level connectivity and coverage. In the case of carrier aggregation, the anchor carrier can correspond to PCell 502. If this carrier corresponds to a DSS carrier, resource availability may be limited. Given that the increased number of NR carriers in the mid-band / high-band can operate without DSS, cross-carrier scheduling from SCell 504 to PCell 502 in the mid-band / high-band can be enabled. Since the carriers in the mid-band / high-band can be based on, for example, a 30kHz SCS, cross-carrier scheduling from SCell 504 to PCell 502 / PSCell can correspond to different digital schemes between SCell 504 and PCell 502 / PSCell. Therefore, cross-carrier scheduling from SCell 504 to PCell 502 / PSCell can be configured for a 30kHz or 15kHz SCS for SCell 504 (e.g., the scheduling cell) and a 15kHz SCS for PCell 502 / PSCell (e.g., the scheduled cell).

[0067] Some cross-carrier scheduling techniques can support different digital schemes between the scheduling cell and the scheduled cell. That is, cross-carrier scheduling from SCell 504 to PCell 502 / PSCell can be based on different digital schemes. In various examples, cross-carrier scheduling from SCell 504 to PCell 502 / PSCell can be used for non-back-off DCIs monitored on the first UE-specific search space (USS) 510 with a carrier indication field (CIF) (e.g., CIF = 0). Cross-carrier scheduling can use the CIF in the DCI to indicate which carrier's PDSCH / PUSCH (at 508) the DCI can schedule. The UE can determine the PDCCH candidates for DCI scheduling from SCell 504 to PCell 502 / PSCell based on the value of n_CI used for the hash function, unless, for example, search space sharing is enabled based on UE capabilities and conditions. If the PDSCH of PCell 502 and the PDCCH of SCell 504 use different SCSs, PDSCH preparation time can be provided.

[0068] With one scheduling cell per scheduled cell, the common search space (CSS) 506 can reside on PCell 502. Maintaining the CSS 506 in PCell 502 / PSCell can provide improved functionality because it can be associated with functions such as system information, paging, random access, backoff operations, and hypothetical block error rate (BLER) calculations for Radio Link Failure (RLF) / Link Recovery (LR) procedures. While no more than one scheduling cell (e.g., SCell 504) may be required for a given scheduled cell (e.g., PCell 502 / PSCell), some NR systems may include more than one scheduling cell for a given scheduled cell. Even when cross-carrier scheduling is configured to perform DSS operations on PCell 502 / PSCell, an SCell 504 can still be configured as a scheduling cell for PCell 502 / PSCell.

[0069] If unicast data scheduling is available from both the scheduling cell (e.g., SCell 504) and the scheduled cell (e.g., PCell 502 / PSCell) CSS 506, the UE may not be able to determine from which scheduling cell it receives scheduling permission for PDSCH or PUSCH (at 508) at each scheduling instance. Therefore, unicast data scheduling may be available only from SCell 504. In various examples, the UE may be configured to process time-overlapping unicast PDSCH and SI-Radio Network Temporary Identifier (RNTI) (SI-RNTI) PDSCH during system information (SI) acquisition triggered by a paging RNTI (P-RNTI) for FR1. CSS monitoring can be maintained on PCell 502 / PSCell so that UE operations associated with system information reception, paging, backoff, RLF, etc., can remain unchanged. The DCI with the cell RNTI (C-RNTI) on CSS 506 of PCell 502 may, for example, be used for PDCCH commands instead of unicast data.

[0070] Schematic diagram 500 illustrates an example of cross-carrier scheduling from SCell 504 to PCell 502. More specifically, multiple PDCCH candidates (e.g., BDs) can be associated with both PCell 502 and SCell 504. Therefore, SCell 504 can schedule either PDSCH or PUSCH on PCell 502 (at 508) via cross-carrier scheduling. If CSS 506 is moved to SCell 504, PCell 502 may not have an associated PDCCH candidate. However, since PCell 502 provides functionality for UE mobility and coverage, CSS 506 can be maintained on PCell 502. Therefore, in schematic diagram 500, CSS 506 can be maintained on PCell 502, while the first USS 510 can be located on SCell 504 for cross-carrier scheduling. Therefore, the PDCCH candidates of PCell 502 and SCell 504 can schedule PDSCH or PUSCH on PCell 502 (at 508). For example, all eight PDCCH candidates associated with CSS 506 and the first USS 510 shown in schematic diagram 500 can be used to schedule data on PCell 502. The second USS 512 (e.g., with CIF=1) can be located on SCell 504 to schedule PDSCH or PUSCH on SCell 504 (at 514) using the PDCCH candidates of SCell 504. For example, the two PDCCH candidates associated with the second USS 512 shown in schematic diagram 500 can be used to schedule data on SCell 504.

[0071] The number of BDs and CCEs that a UE can process simultaneously can be based on certain limitations. For example, a UE may not process more BDs and / or CCEs than a predefined threshold number at once. In cases where the UE supports cross-carrier scheduling from PCell 502 to SCell 504, one scheduling cell can exist for a given scheduled cell. For example, for the PDSCH or PUSCH on SCell 504 in diagram 500 (at 514), one scheduling cell (e.g., PCell 502) can exist. However, for the PDSCH or PUSCH on PCell 502 in diagram 500 (at 508), multiple scheduling cells (e.g., PCell 502 and SCell 504) can exist. Therefore, the maximum number of BDs and non-overlapping CCEs can be adjusted such that it does not exceed the PDCCH allocation.

[0072] Figures 6A-6BDiagrams 600-650 illustrate the relationship between determining the number of PDCCH candidates (e.g., BDs) and the number of non-overlapping CCEs. If two scheduled cells are used for scheduling on the PCell / PSCell, the number of PDCCH BDs / CCEs can be determined based on counts / allocations. That is, the number of BDs / CCEs per span / slot can be limited for a given scheduled cell based on the UE's processing capacity. In diagram 600, the maximum number of BDs and non-overlapping CCEs can be determined based on a predefined allocation corresponding to the lower SCS (e.g., 15 kHz) of the component carrier (e.g., the lower of the first SCS for the SCell and the second SCS for the PCell / PSCell). In diagram 650, the maximum number of BDs and non-overlapping CCEs can be determined based on predefined allocations separately for the PCell / PSCell and the SCell.

[0073] The two component carriers indicated in Figures 600-650 for SCell and PCell / PSCell can have different SCS. For example, the first SCS for SCell can be 60 kHz, while the second SCS for PCell / PSCell can be 15 kHz. Based on the different SCS of the corresponding component carriers, the PDCCH monitoring timing can be different for the first and second component carriers. For example, PCell / PSCell can be associated with one monitoring timing per time slot, while SCell can be associated with four monitoring timings per time slot. The PDCCH monitoring timing for PCell / PSCell can be associated with PDCCH candidates received from the CSS, while the PDCCH monitoring timing for SCell can be associated with PDCCH candidates received from the USS.

[0074] In schematic diagram 600, the number of BDs and non-overlapping CCEs per span / slot can be counted on the data scheduling cell for the PCell / PSCell. The counted number of BDs and non-overlapping CCEs can not exceed the predefined allocation per span / slot per component carrier (e.g., there may be no over-scheduling of the PDCCH). In various examples, for a 15kHz carrier, the BD allocation per span / slot per component carrier can be as high as 44 BDs. Thus, 44 BDs can be the BD allocation on the carrier used for the PCell / PSCell (e.g., the maximum number that cannot be exceeded).

[0075] If the scheduling cell (e.g., SCell) and the scheduled cell (e.g., PCell / PSCell) use different digital schemes, the per-span / slot threshold can be determined based on the lower SCS (e.g., per-span / slot including component carriers with the lower SCS). In schematic 600, the per-span / slot threshold for the component carrier with the lowest SCS can correspond to a 15kHz carrier (e.g., the span / slot for PDCCH monitoring timing of the PCell / PSCell). The number of BDs spanning the PCell / PSCell and SCell can not exceed the lower BD allocation of multiple scheduling carriers. In this way, BD allocation can be capped based on the per-cell budget, even if the number of BDs can extend across multiple scheduling carriers.

[0076] In diagram 650, the number of BDs or non-overlapping CCEs can be defined per scheduling cell, including data scheduling on PCell / PSCell. That is, the number of BDs or non-overlapping CCEs can be counted individually per cell. For example, a PDCCH monitoring opportunity for PCell / PSCell can have up to 44 PDCCH candidates (e.g., BDs), while a PDCCH monitoring opportunity for SCell can have up to 44 PDCCH candidates. The UE can report UE capability information to the network indicating whether the UE is configured to process 88 PDCCH candidates (e.g., 44+44), or whether the UE is individually configured to process up to 44 PDCCH candidates, for example, on all carriers.

[0077] Therefore, the number of BDs and non-overlapping CCEs per span / slot can be counted according to the scheduling cell used to schedule the PCell / PSCell. The counted number of BDs and non-overlapping CCEs per span / slot for a given scheduling cell can not exceed the predefined allocation per span / slot per carrier. Although schematic diagram 650 similarly indicates that PDCCH overscheduling may not exist, the per-carrier allocation in schematic diagram 650 can be for each scheduling cell available in the scheduling cells. The UE can be configured to report UE capability information regarding the number of BDs and non-overlapping CCEs per span / slot for the PCell / PSCell, such that the configuration having the total number of BDs / non-overlapping CCEs per span / slot on the carrier for the PCell / PSCell can not exceed the predetermined allocation per span / slot per carrier.

[0078] The UE can report its processing capabilities to the network via capability signaling. In various examples, if the UE reports a value N via capability signaling, where N can be determined, for example, based on a hash function, then the UE can support a total number of BD / non-overlapping CCEs per span / slot on the carrier for PCell / PSCell, which is up to N times the predetermined allocation per span / slot per carrier. For example, if the UE reports N=2, then the UE can support 44+44 BD / non-overlapping CCEs. If the UE reports N=1, then the UE can support a total number of BD / non-overlapping CCEs per span / slot on the carrier for PCell / PSCell, which does not exceed the predetermined allocation per span / slot per carrier (e.g., 44 PDCCH candidates on the carrier).

[0079] Figure 7 This is a flowchart 700 of a wireless communication method. The method can be performed by a UE (e.g., UE 104), which may include a memory 360 and may be the entire UE 104 or components of UE 104 (such as a TX processor 368, an RX processor 356, and / or a controller / processor 359).

[0080] At point 701, the UE can send capability information associated with concurrent monitoring of the first PDCCH and the second PDCCH. For example, refer to Figure 4 At point 406, UE 402 can send UE capability information to base station 404. The capability information can indicate the value of N, where N≥1.

[0081] At 702, the UE can monitor the first PDCCH on the first CC. For example, refer to... Figure 4 At 408a, UE 402 can monitor the first PDCCH on the first CC.

[0082] At 702a, the first PDCCH can be configured to schedule either the first PDSCH or the first PUSCH on the second CC. For example, see reference... Figure 5 The PDCCH associated with the SCell can be configured to schedule the PDSCH or PUSCH on the PCell.

[0083] At 702b, the first PDCCH may have a first subcarrier spacing. For example, refer to Figures 6A-6B The SCS of SCell can be 60kHz.

[0084] At 702c, the first PDCCH associated with the scheduling of at least one of the first PDSCH or the first PUSCH on the second CC can be associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number. For example, refer to Figure 5 and Figures 6A-6B The PDCCH associated with the cross-carrier scheduling of PDSCH / PUSCH from SCell to PCell can be further associated with the number of BDs or the number of non-overlapping CCEs in the PDCCH monitoring timing, as shown in Schematic Diagrams 600-650.

[0085] At 702d, the first PDCCH may have a first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, based on the first subcarrier spacing. For example, refer to Figure 6B Schematic diagram 650 indicates that the number of BDs and non-overlapping CCEs used for the SCell can not exceed the budget defined by the SCell based on the 60kHz SCS.

[0086] At position 704, concurrently monitoring the first PDCCH, the UE can monitor the second PDCCH on a second CC different from the first CC. For example, refer to Figure 4 At 408b, UE 402 can monitor a second PDCCH on a second CC different from the first CC. Monitoring the second PDCCH at 408b can be performed concurrently with monitoring the first PDCCH at 408a. As shown in diagrams 600-650, the first CC can be associated with a SCell, and the second CC can be associated with either a PCell or a PSCell. In various respects, the first CC and the second CC can be in different frequency bands. For example, the first CC can be associated with a frequency range higher than the second CC.

[0087] At 704a, the second PDCCH can be configured to schedule either the second PDSCH or the second PUSCH on the second CC. For example, see reference... Figure 5 The PDCCH associated with the PCell can be configured to schedule the PDSCH or PUSCH on the PCell.

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

[0089] At 704c, the second PDCCH associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC can be associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number. For example, refer to Figure 5 and Figures 6A-6B The PDCCH associated with the PDSCH / PUSCH of the PCell can be further associated with the number of BDs or the number of non-overlapping CCEs during the PDCCH monitoring time, as indicated in Schematic Diagrams 600-650.

[0090] At 704d, the second PDCCH may have a second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number, based on the second subcarrier spacing. For example, refer to Figure 6B Schematic diagram 650 indicates that the number of BDs and non-overlapping CCEs used for PCell can not exceed the budget defined by the PCell based on the 15kHz SCS.

[0091] At point 706, the first sum of the first and second PDCCH candidate numbers can be less than or equal to N times the second maximum number associated with the second PDCCH candidate number. For example, if the maximum number of PDCCH candidates is 44 (refer to...). Figures 6A-6B If the total number of PDCCH candidates associated with PCell and SCell is N times less than 44, then the value of N can be N = 1. As a result, the total number of PDCCH candidates associated with PCell and SCell can not exceed 44. Alternatively, at 706, the second sum of the first and second non-overlapping CCE numbers can be less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

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

[0093] At point 801, the base station can receive capability information associated with the configuration of the first PDCCH and the second PDCCH from the UE. For example, refer to Figure 4 At position 406, base station 404 can receive UE capability information from UE 402. The capability information can indicate the value of N, where N≥1.

[0094] At 802, the base station can configure the first PDCCH for the UE on the first CC. For example, refer to Figure 4 At 410a, base station 404 can configure the first PDCCH on the first CC for UE 402.

[0095] At 802a, the first PDCCH can be configured to schedule either the PDSCH on the second CC or the first PUSCH. For example, see reference... Figure 5 The PDCCH associated with the SCell can be configured to schedule the PDSCH or PUSCH on the PCell.

[0096] At 802b, the first PDCCH can have a first subcarrier spacing. For example, refer to Figures 6A-6B The SCS of SCell can be 60kHz.

[0097] At 802c, the first PDCCH associated with the scheduling of at least one of the first PDSCH or the first PUSCH on the second CC can be associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number. For example, refer to Figure 5 and Figures 6A-6B The PDCCH associated with the cross-carrier scheduling of PDSCH / PUSCH from SCell to PCell can be further associated with the number of BDs or the number of non-overlapping CCEs in the PDCCH monitoring timing, as indicated in schematic diagrams 600-650.

[0098] At 802d, the first PDCCH may have a first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, based on the first subcarrier spacing. For example, refer to Figure 6B Schematic diagram 650 indicates that the number of BDs and non-overlapping CCEs used for the SCell can not exceed the budget defined by the SCell based on the 60kHz SCS.

[0099] At point 804, the base station can configure a second PDCCH on a second CC different from the first PDCCH, and the second PDCCH is concurrent with the first PDCCH. For example, refer to Figure 4 At 410b, base station 404 can configure a second PDCCH for scheduling the second PDSCH / second PUSCH on the second CC for UE 402. As shown in diagrams 600-650, the first CC can be associated with a SCell, and the second CC can be associated with either a PCell or a PSCell. In various respects, the first CC and the second CC can be in different frequency bands. For example, the first CC can be associated with a frequency range higher than the second CC.

[0100] At 804a, the second PDCCH can be configured to schedule either the second PDSCH or the second PUSCH on the second CC. For example, see reference... Figure 5The PDCCH associated with the PCell can be configured to schedule the PDSCH or PUSCH on the PCell.

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

[0102] At 804c, the second PDCCH associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC can be associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number. For example, refer to Figure 5 and Figures 6A-6B The PDCCH associated with the PDSCH / PUSCH of the PCell can be further associated with the number of BDs or the number of non-overlapping CCEs during the PDCCH monitoring time, as indicated in Schematic Diagrams 600-650.

[0103] At 804d, the second PDCCH may have a second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number, based on the second subcarrier spacing. For example, refer to Figure 6B Schematic diagram 650 indicates that the number of BDs and non-overlapping CCEs used for PCell can not exceed the budget defined by the PCell based on the 15kHz SCS.

[0104] At point 806, the base station can transmit the DCI for scheduling one of the first PDSCH, first PUSCH, second PDSCH, or second PUSCH on the second CC on at least one of the first PDCCH or second PDCCH. For example, refer to Figure 4 At 412, base station 404 can transmit the DCI of the first / second PDSCH / PUSCH on the second CC. The sum of the PDCCH candidates and / or non-overlapping CCEs transmitted at 412 can be less than a predefined threshold.

[0105] At position 808, the DCI can be associated with a first sum of the first and second PDCCH candidate numbers, where the first sum can be less than or equal to N times the second maximum number associated with the second PDCCH candidate number. For example, if the maximum number of PDCCH candidates is 44 (refer to...). Figures 6A-6BIf the total number of PDCCH candidates associated with PCell and SCell is N times less than 44, then the value of N can be N = 1. As a result, the total number of PDCCH candidates associated with PCell and SCell can not exceed 44. Alternatively, at 808, the DCI can be associated with a second sum of the first and second non-overlapping CCE numbers, wherein the second sum can be less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

[0106] Figure 9 This is a schematic diagram 900 illustrating an example of a hardware implementation for device 902. Device 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 Module (SIM) cards 920; an application processor 906 coupled to a Secure Digital Card (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 with UE 104 and / or BS 102 / 180 via the cellular RF transceiver 922. The cellular baseband processor 904 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 904 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 904, the software causes the cellular baseband processor 904 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 904 during software execution. The cellular baseband processor 904 also includes a receiving component 930, a communication manager 932, and a transmitting component 934. The communication manager 932 includes one or more of the components shown. The components within the communication manager 932 can be stored in the computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 904. The cellular baseband processor 904 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 902 can be a modem chip and only include the baseband processor 904; in another configuration, the device 902 can be the entire UE (e.g., see [link to relevant documentation]). Figure 3 (350) and includes the additional modules discussed above for device 902.

[0107] The communication manager 932 includes a monitor component 940 configured (e.g., as described in conjunction with 702 and 704) to: monitor a first PDCCH on a first CC; and concurrently monitor a second PDCCH on a second CC different from the first CC. A transmitting component 934 is configured (e.g., as described in conjunction with 701) to: transmit capability information associated with the concurrent monitoring of the first and second PDCCHs.

[0108] The device may include execution Figure 7 The additional components of each box in the algorithm's flowchart above. Therefore, Figure 7 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0109] In one configuration, device 902 (and specifically, cellular baseband processor 904) includes: a unit for monitoring a first physical downlink control channel (PDCCH) on a first component carrier (CC), the first PDCCH being configured to schedule either 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 associated with scheduling said one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first PDCCH candidate number or a first non-overlapping control channel element (CCE) number, the first PDCCH having a first maximum number associated with said at least one of the first PDCCH candidate number or the first non-overlapping CCE number based on the first subcarrier spacing; and a unit for concurrently monitoring a second PDCCH on a second CC different from the first CC with the monitoring of the first PDCCH. The second PDCCH is configured to schedule either the second PDSCH or the second PUSCH on the second CC. The second PDCCH has a second subcarrier spacing less than or equal to the first subcarrier spacing. The second PDCCH associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number. The second PDCCH has a second maximum number associated with the at least one of the second PDCCH candidate number or the second non-overlapping CCE number based on the second subcarrier spacing, wherein at least one of the following conditions exists: the first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number; or the second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number. The aforementioned unit may be one or more of the aforementioned components of the device 902 configured to perform the functions described therein. As described above, the device 902 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned units may be TX processor 368, RX processor 356, and controller / processor 359, which are configured to perform the functions described in the aforementioned units.

[0110] Figure 10This is a schematic diagram 1000 illustrating an example of a hardware implementation for device 1002. Device 1002 is a BS and includes a baseband unit 1004. The baseband unit 1004 can communicate with a UE 104 via a cellular RF transceiver. The baseband unit 1004 may include computer-readable media / memory. The baseband unit 1004 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the baseband unit 1004, the software causes the baseband unit 1004 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the baseband unit 1004 when executing the software. The baseband unit 1004 also includes a receiving component 1030, a communication manager 1032, and a transmitting component 1034. The communication manager 1032 includes one or more of the components shown. The components within the communication manager 1032 may be stored in computer-readable media / 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 at least one of the TX processor 316, the RX processor 370 and the controller / processor 375 and / or the memory 376.

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

[0112] The device may include execution Figure 8 The additional components of each box in the algorithm's flowchart above. Therefore, Figure 8 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0113] In one configuration, apparatus 1002 (specifically, baseband unit 1004) includes: a unit for configuring a first physical downlink control channel (PDCCH) for a user equipment (UE) on a first component carrier (CC), the first PDCCH being configured to schedule either 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 associated with scheduling said one of the first PDSCH or the first PUSCH on the second CC being associated with at least one of a first PDCCH candidate number or a first non-overlapping control channel element (CCE) number, the first PDCCH having a first maximum number associated with said at least one of the first PDCCH candidate number or the first non-overlapping CCE number based on the first subcarrier spacing; and a unit for configuring a second PDCCH on a second CC different from the first CC, the second PDCCH being configured to schedule either a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, the second P... The DCCH has a second subcarrier spacing less than or equal to the first subcarrier spacing; the second PDCCH associated with the scheduling of at least one of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number; the second PDCCH has a second maximum number associated with the at least one of the second PDCCH candidate number or the second non-overlapping CCE number based on the second subcarrier spacing; and a unit for transmitting downlink control information (DCI) on at least one of the first PDCCH or the second PDCCH, the 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 the following: a first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number; or a second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number. The aforementioned unit may be one or more of the components of the device 1002 configured to perform the functions described therein. As described above, the device 1002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned unit may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the functions described therein.

[0114] Therefore, it may be necessary to adjust the total number of PDCCH candidates to be received from the SCell and PCell / PSCell based on the UE's processing capabilities. In a first aspect, for example, when the SCell and PCell / PSCell use different digital schemes, the maximum number of PDCCH candidates can be based on a predefined budget for the CC with the lowest SCS. That is, the total budget across the two CCs may not exceed the budget associated with the lowest SCS. In a second aspect, the maximum number of PDCCH candidates can be counted individually per cell. UE capability information reported to the network can indicate whether the UE is configured to process the number of PDCCH candidates associated with the corresponding CC.

[0115] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It is to be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of the boxes in the example order and are not intended to limit one to the given specific order or hierarchy.

[0116] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, references to singular elements are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the same time as” should be interpreted as “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The term “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 over or superior to other aspects. Unless expressly 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure that are known to or will be known later by one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., are not necessarily substitutes for the term “unit.” Therefore, no claim can be made that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

[0117] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0118] Aspect 1 is an apparatus for performing wireless communication at a UE, comprising: 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 associated with at least one of a first PDCCH candidate number or a first non-overlapping CCE number; and concurrently with monitoring the first PDCCH, monitoring a second PDCCH on a second CC different from 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 having a second maximum number associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, wherein at least one of the following conditions exists: a first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number, or a second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

[0119] Aspect 2 may be combined with aspect 1 and includes: the first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and wherein the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

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

[0121] Aspect 4 may be combined with any of aspects 1-3 and includes: the first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

[0122] Aspect 5 may be combined with any of aspects 1-4 and includes: the first CC is associated with SCell, and the second CC is associated with either PCell or PSCell.

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

[0124] Aspect 7 can be combined with any of aspects 1-6, and includes: the first CC is associated with a higher frequency range compared to the second CC.

[0125] Aspect 8 may be combined with any of aspects 1-7 and includes: N is a multiplier associated with the processing capacity of the UE to process at least one of the total number of PDCCH candidates or the total number of non-overlapping CCEs, the total number of PDCCH candidates including the first number of PDCCH candidates and the second number of PDCCH candidates, and the total number of non-overlapping CCEs including the first number of non-overlapping CCEs and the second number of non-overlapping CCEs.

[0126] Aspect 9 can be combined with any of aspects 1-8, and includes N=1.

[0127] Aspect 10 may be combined with any of aspects 1-9 and includes: the at least one processor is further configured to: send capability information associated with concurrent monitoring of the first PDCCH and the second PDCCH, the capability information indicating the value of N, where N≥1.

[0128] Aspect 11 is an apparatus for performing wireless communication at a base station, comprising: at least one processor coupled to a memory and configured to: configure a first PDCCH for a UE 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 associated with at least one of a first PDCCH candidate number or a first non-overlapping CCE number; configure a second PDCCH on a second CC different from 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 associated with at least one of a second PDCCH candidate number; A second maximum number associated with at least one of the second non-overlapping CCE numbers; and sending a DCI on at least one of the first PDCCH or the second PDCCH, the 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 the following: a first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number, or a second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number.

[0129] Aspect 12 may be combined with aspect 11 and includes: the first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

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

[0131] Aspect 14 may be combined with any of aspects 11-13 and includes: the first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

[0132] Aspect 15 may be combined with any of aspects 11-14 and includes: the first CC is associated with SCell, and the second CC is associated with either PCell or PSCell.

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

[0134] Aspect 17 may be combined with any of aspects 11-16 and includes: the first CC is associated with a higher frequency range compared to the second CC.

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

[0136] Aspect 19 can be combined with any of aspects 11-18, and includes N=1.

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

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

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

[0140] Aspect 23 is an apparatus for wireless communication, including units for implementing any aspect of aspects 1-21.

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

Claims

1. An apparatus for performing wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: The first physical downlink control channel (PDCCH) on a first component carrier (CC) associated with a secondary cell (SCell) is monitored. The first PDCCH is configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC associated with either a primary cell (PCell) or a primary-secondary cell (PSCell). The first PDCCH has a first maximum number associated with at least one of a first PDCCH candidate number or a first non-overlapping control channel element (CCE) number, wherein the first maximum number is defined for the first CC. Concurrently with monitoring the first PDCCH, monitoring a second PDCCH on the second CC, the second PDCCH being configured to schedule either a second PDSCH or a second PUSCH on the second CC, the second PDCCH having a second maximum number associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, wherein the second maximum number is defined for the second CC; and Downlink control information (DCI) is received via at least one of the first PDCCH or the second PDCCH, wherein the DCI schedules one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC. There exists at least one of the following situations: the first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number or N times the first maximum number associated with the first PDCCH candidate number; or the second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number or N times the first maximum number associated with the first non-overlapping CCE number, where N is a positive integer and where N is based on a hash function.

2. The apparatus according to claim 1, wherein, The first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and wherein the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

3. The apparatus according to claim 1, wherein, The first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing, the second subcarrier spacing being less than or equal to the first subcarrier spacing.

4. The apparatus according to claim 3, wherein, The first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and wherein the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

5. The apparatus according to claim 1, wherein, One of the PCell or the PSCell is associated with the first scheduling cell and the second scheduling cell.

6. The apparatus according to claim 5, wherein, The first CC and the second CC are in different frequency bands.

7. The apparatus according to claim 6, wherein, Compared to the second CC, the first CC is associated with a higher frequency range.

8. The apparatus according to claim 1, wherein, N is a multiplier associated with the UE's processing capacity for at least one of the total number of PDCCH candidates or the total number of non-overlapping CCEs, wherein the total number of PDCCH candidates includes the first number of PDCCH candidates and the second number of PDCCH candidates, and the total number of non-overlapping CCEs includes the first number of non-overlapping CCEs and the second number of non-overlapping CCEs.

9. The apparatus according to claim 8, wherein, N＝1。 10. The apparatus according to claim 1, wherein, The at least one processor is further configured to send capability information associated with concurrent monitoring of the first PDCCH and the second PDCCH, the capability information indicating the value of N, where N≥1.

11. An apparatus for performing wireless communication at a base station, comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: For a user equipment (UE), a first physical downlink control channel (PDCCH) is configured on a first component carrier (CC) associated with a secondary cell (SCell). The first PDCCH is configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC associated with either a primary cell (PCell) or a primary-secondary cell (PSCell). The first PDCCH has a first maximum number associated with at least one of a first number of PDCCH candidates or a first number of non-overlapping control channel elements (CCE), wherein the first maximum number is defined for the first CC. For the UE, a second PDCCH is configured on the second CC, the second PDCCH being configured to schedule either a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, and the second PDCCH having a second maximum number associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, wherein the second maximum number is defined for the second CC; and Downlink control information (DCI) is transmitted via at least one of the first PDCCH or the second PDCCH, the 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 the following: a first sum of the number of first PDCCH candidates and the number of second PDCCH candidates is less than or equal to N times the second maximum number associated with the number of second PDCCH candidates or N times the first maximum number associated with the number of first PDCCH candidates; or a second sum of the number of first non-overlapping CCEs and the number of second non-overlapping CCEs is less than or equal to N times the second maximum number associated with the number of second non-overlapping CCEs or N times the first maximum number associated with the number of first non-overlapping CCEs, where N is a positive integer and where N is based on a hash function.

12. The apparatus according to claim 11, wherein, The first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and wherein the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

13. The apparatus according to claim 11, wherein, The first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing, the second subcarrier spacing being less than or equal to the first subcarrier spacing.

14. The apparatus according to claim 13, wherein, The first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and wherein the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

15. The apparatus according to claim 11, wherein, One of the PCell or the PSCell is associated with the first scheduling cell and the second scheduling cell.

16. The apparatus according to claim 15, wherein, The first CC and the second CC are in different frequency bands.

17. The apparatus according to claim 16, wherein, Compared to the second CC, the first CC is associated with a higher frequency range.

18. The apparatus according to claim 11, wherein, N is a multiplier associated with the UE's processing capacity for at least one of the total number of PDCCH candidates or the total number of non-overlapping CCEs, wherein the total number of PDCCH candidates includes the first number of PDCCH candidates and the second number of PDCCH candidates, and the total number of non-overlapping CCEs includes the first number of non-overlapping CCEs and the second number of non-overlapping CCEs.

19. The apparatus according to claim 11, wherein, N＝1。 20. The apparatus according to claim 11, wherein, The at least one processor is further configured to receive capability information from the UE associated with concurrent configuration of the first PDCCH and the second PDCCH, the capability information indicating the value of N, where N≥1.

21. A method for performing wireless communication at a user equipment (UE), comprising: Monitoring a first physical downlink control channel (PDCCH) on a first component carrier (CC) associated with a secondary cell (SCell), 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 associated with either the primary cell (PCell) or the primary / secondary cell (PSCell), the first PDCCH having a first maximum number associated with at least one of a first PDCCH candidate number or a first non-overlapping control channel element (CCE) number, wherein the first maximum number is defined for the first CC; and Concurrently with monitoring the first PDCCH, monitoring a second PDCCH on the second CC, the second PDCCH being configured to schedule either a second PDSCH or a second PUSCH on the second CC, the second PDCCH having a second maximum number associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, wherein the second maximum number is defined for the second CC; and Downlink control information (DCI) is received via at least one of the first PDCCH or the second PDCCH, wherein the DCI schedules one of the first PDSCH, the first PUSCH, the second PDSCH, or the second PUSCH on the second CC. There exists at least one of the following situations: the first sum of the first PDCCH candidate number and the second PDCCH candidate number is less than or equal to N times the second maximum number associated with the second PDCCH candidate number or N times the first maximum number associated with the first PDCCH candidate number; or the second sum of the first non-overlapping CCE number and the second non-overlapping CCE number is less than or equal to N times the second maximum number associated with the second non-overlapping CCE number or N times the first maximum number associated with the first non-overlapping CCE number, where N is a positive integer and where N is based on a hash function.

22. The method according to claim 21, wherein, The first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and wherein the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

23. The method according to claim 21, wherein, The first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing, the second subcarrier spacing being less than or equal to the first subcarrier spacing.

24. The method according to claim 23, wherein, The first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and wherein the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

25. The method according to claim 21, wherein, One of the PCell or the PSCell is associated with the first scheduling cell and the second scheduling cell.

26. A method for performing wireless communication at a base station, comprising: For a user equipment (UE), a first physical downlink control channel (PDCCH) is configured on a first component carrier (CC) associated with a secondary cell (SCell). The first PDCCH is configured to schedule one of a first physical downlink shared channel (PDSCH) or a first physical uplink shared channel (PUSCH) on a second CC associated with either a primary cell (PCell) or a primary-secondary cell (PSCell). The first PDCCH has a first maximum number associated with at least one of a first number of PDCCH candidates or a first number of non-overlapping control channel elements (CCE), wherein the first maximum number is defined for the first CC. For the UE, a second PDCCH is configured on the second CC, the second PDCCH being configured to schedule either a second PDSCH or a second PUSCH on the second CC, the second PDCCH being concurrent with the first PDCCH, and the second PDCCH having a second maximum number associated with at least one of a second PDCCH candidate number or a second non-overlapping CCE number, wherein the second maximum number is defined for the second CC; and Downlink control information (DCI) is transmitted via at least one of the first PDCCH or the second PDCCH, the 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 the following: a first sum of the number of first PDCCH candidates and the number of second PDCCH candidates is less than or equal to N times the second maximum number associated with the number of second PDCCH candidates or N times the first maximum number associated with the number of first PDCCH candidates; or a second sum of the number of first non-overlapping CCEs and the number of second non-overlapping CCEs is less than or equal to N times the second maximum number associated with the number of second non-overlapping CCEs or N times the first maximum number associated with the number of first non-overlapping CCEs, where N is a positive integer and where N is based on a hash function.

27. The method according to claim 26, wherein, The first PDCCH associated with the scheduling of the first PDSCH or the first PUSCH on the second CC is associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number, and wherein the second PDCCH associated with the scheduling of the second PDSCH or the second PUSCH on the second CC is associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number.

28. The method according to claim 26, wherein, The first PDCCH includes a first subcarrier spacing, and the second PDCCH includes a second subcarrier spacing, the second subcarrier spacing being less than or equal to the first subcarrier spacing.

29. The method according to claim 28, wherein, The first maximum number associated with at least one of the first PDCCH candidate number or the first non-overlapping CCE number is based on the first subcarrier spacing, and wherein the second maximum number associated with at least one of the second PDCCH candidate number or the second non-overlapping CCE number is based on the second subcarrier spacing.

30. The method according to claim 26, wherein, One of the PCell or the PSCell is associated with the first scheduling cell and the second scheduling cell.

Images