Managing deactivation or dormancy of component carriers in cross-component carrier or multi-component carrier scheduling

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can monitor for a first downlink control information (DCI) format using a first physical downlink control channel (PDCCH) monitoring behavior, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC. The UE can monitor for a second DCI format using a second PDCCH monitoring behavior based at least in part on a determination that a PDCCH monitoring behavior switching condition is satisfied. Numerous other aspects are provided.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to the following applications: U.S. Provisional Patent Application No. 62 / 706,250, filed August 6, 2020, entitled “MANAGING DEACTIVATION ORDORMANCY OF A COMPONENT CARRIER IN CROSS COMPONENT CARRIER OR MULTIPLE COMPONENT CARRIER SCHEDULING”; and U.S. Non-Provisional Patent Application No. 17 / 444,032, filed July 29, 2021, entitled “MANAGING DEACTIVATION ORDORMANCY OF A COMPONENT CARRIER IN CROSS COMPONENT CARRIER OR MULTIPLE COMPONENT CARRIER SCHEDULING”, which are expressly incorporated herein by reference. Technical Field

[0003] In summary, various aspects of this disclosure relate to wireless communication and to techniques and apparatus for managing the deactivation or dormancy of CCs in cross-component carrier (CC) or multi-CC scheduling. 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 (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / Improved LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs) capable of supporting communication for multiple user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, while an "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. NR (which can also be referred to as 5G) is an enhancement set of the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), thereby better supporting mobile broadband internet access, as well as beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: receiving a configuration indicating a first downlink control information (DCI) format and a second DCI format; monitoring the first DCI format using a first physical downlink control channel (PDCCH) monitoring behavior, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC; and monitoring the second DCI format using a second PDCCH monitoring behavior based at least in part on a determination regarding conditions for satisfying the PDCCH monitoring behavior switching.

[0008] In some aspects, a method of wireless communication performed by a base station includes: transmitting a first PDSCH communication to a UE using a first plurality of physical downlink shared channel (PDSCH) resources, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; and transmitting a second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions.

[0009] In some aspects, a UE for wireless communication includes: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: receive a configuration indicating a first DCI format and a second DCI format; monitor for the first DCI format using a first PDCCH monitoring action, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC; and monitor for the second DCI format using a second PDCCH monitoring action based at least in part on a determination regarding the satisfaction of PDCCH monitoring action switching conditions.

[0010] In some aspects, a base station for wireless communication includes: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: transmit a first PDSCH communication to a UE using a first plurality of PDSCH resources, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; and transmit a second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration indicating a first DCI format and a second DCI format; monitor for the first DCI format using a first PDCCH monitoring action, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC; and monitor for the second DCI format using a second PDCCH monitoring action based at least in part on a determination regarding the satisfaction of PDCCH monitoring action switching conditions.

[0012] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: transmit a first PDSCH communication to a UE using a first plurality of PDSCH resources, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of a cross-CC schedule or a multi-CC schedule associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; and transmit a second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions.

[0013] In some aspects, an apparatus for wireless communication includes: a unit for receiving a configuration indicating a first DCI format and a second DCI format; a unit for monitoring the first DCI format using a first PDCCH monitoring behavior, the first DCI format indicating a set of resources associated with at least one of a cross-CC schedule or a multi-CC schedule associated with a first CC and a second CC; and a unit for monitoring the second DCI format using a second PDCCH monitoring behavior based at least in part on a determination of conditions for satisfying a PDCCH monitoring behavior switching.

[0014] In some aspects, an apparatus for wireless communication includes: a unit for transmitting a first PDSCH communication to a UE using a first plurality of PDSCH resources, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of a cross-CC schedule or a multi-CC schedule associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; and a unit for transmitting a second DCI communication having a second DCI format based at least in part on a determination regarding a handover condition for satisfying PDCCH monitoring behavior.

[0015] In general, the aspects include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems as fully described herein with reference to the accompanying drawings and description and as shown by the accompanying drawings and description.

[0016] The foregoing has provided a fairly broad overview of the features and technical advantages of examples according to this disclosure in order to better understand the following detailed description. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and their associated advantages will be better understood when considered in conjunction with the accompanying drawings, based on the following description. Each drawing in the accompanying drawings is provided for illustrative and descriptive purposes and is not intended to define a limitation of the claims.

[0017] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The innovations described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or AI-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and enforcement of the claimed and described aspects. For example, the transmission and reception of wireless signals may include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers). The aspects described herein are intended to be implemented in a variety of devices, components, systems, distributed arrangements, or end-user devices with different sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly summarized above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit the scope of the disclosure, as other equally valid aspects are permissible under this description. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0020] Figure 2 This is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figures 3-6 This is a diagram illustrating examples of cross-component carrier (CC) scheduling and multi-CC scheduling according to this disclosure.

[0022] Figure 7 This is a diagram illustrating an example of the deactivation or hibernation of a CC in a cross-CC or multi-CC scheduling process, in accordance with the present disclosure.

[0023] Figures 8-13 This is a diagram illustrating an example of deactivating or hibernating a CC in a cross-CC or multi-CC scheduling process according to this disclosure.

[0024] Figure 14 and Figure 15 This is a diagram illustrating an example process associated with the deactivation or hibernation of CCs in a cross-CC or multi-CC scheduling, according to the present disclosure.

[0025] Figure 16 and Figure 17 This is a block diagram of an example device for wireless communication based on the present disclosure. Detailed Implementation

[0026] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, an apparatus or a method may be implemented using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings, through various frames, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0028] It should be noted that while this document may use terms commonly associated with 5G or New Radio (NR) Radio Access Technology (RAT) to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0029] Figure 1This is a diagram illustrating an example of a wireless network 100 according to this disclosure. Wireless network 100 may be or may include elements of a 5G (NR) network and / or a Long Term Evolution (LTE) network, as well as other examples. Wireless network 100 may include multiple base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NRBS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0030] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed User Group (CSG)). A BS used for macrocells can be referred to as a macro BS. A BS used for picocells can be referred to as a pico BS. A BS used for femtocells can be referred to as a femtocell BS or a home BS. Figure 1 In the examples shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0031] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0032] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and transmit the data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, repeater, etc.

[0033] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0034] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. BSs can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0035] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet device, camera, gaming device, netbook, smartbook, ultrabook, medical device or apparatus, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music or video device, or satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0036] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing housing the components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0037] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0038] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication with each other). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.) and / or mesh networks. In this case, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0039] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1) (which can span from 410 MHz to 7.125 GHz), and / or can communicate using an operating band with a second frequency range (FR2) (which can span from 24.25 GHz to 52.6 GHz). The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency (IF) bands. Although a portion of FR1 is greater than 6 GHz, FR1 is generally referred to as the "below 6 GHz" band. Similarly, FR2 is generally referred to as the "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise explicitly stated, it should be understood that the terms "below 6 GHz" and the like (if used herein) can broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., above 7.125 GHz). Similarly, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., below 24.25 GHz). It is anticipated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0040] As pointed out above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0041] Figure 2 This is a diagram illustrating an example of communication between a base station 110 and a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein generally, T ≥ 1 and R ≥ 1.

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

[0043] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine the Reference Signal Received Power (RSRP) parameter, Received Signal Strength Indicator (RSSI) parameter, Reference Signal Received Quality (RSRQ) parameter, and / or CQI parameter, as well as other examples. In some aspects, one or more components of the UE 120 may be included in the housing 284.

[0044] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0045] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within the following: one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, and other examples. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements coupled to one or more transmitting and / or receiving components (such as...) Figure 2 One or more antenna elements (one or more components in the process).

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

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

[0048] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other components may perform one or more techniques associated with the deactivation or dormancy of CCs in cross-component carrier (CC) or multi-CC scheduling, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 14 Process 1400 Figure 15 The operation of process 1500 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 14 Process 1400 Figure 15 The operation of process 1500 and / or other processes as described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions and / or interpretation instructions, and other examples.

[0049] In some aspects, UE 120 may include: a unit for monitoring a first downlink control information (DCI) format using a first physical downlink control channel (PDCCH) monitoring action, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC; a unit for monitoring a second DCI format using a second PDCCH monitoring action based at least in part on a determination regarding the satisfaction of PDCCH monitoring action switching conditions; and so on. In some aspects, such a unit may include a combination of Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TXMIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0050] In some aspects, base station 110 may include: a unit for transmitting first PDSCH communication to a UE using a first plurality of physical downlink shared channel (PDSCH) resources, wherein the first plurality of resources are indicated by first DCI communication having a first DCI format, wherein the first DCI communication is used to indicate a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; a unit for transmitting second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions; and so on. In some aspects, such a unit may include a combination of Figure 2 One or more components of the described base station 110, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.

[0051] Although Figure 2 The boxes in the diagram are shown as different components, but the functions described above with respect to these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by or under the control of controller / processor 280.

[0052] As pointed out above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0053] Figure 3 This is a diagram illustrating examples of cross-CC scheduling 300 and multi-CC scheduling 310 according to this disclosure. As shown, UE 120 and base station 110 (shown as "BS") can communicate with each other using carrier aggregation, where two or more CCs can be used to carry control communications, data communications, etc.

[0054] As indicated by reference numeral 300 in the accompanying figure, the first CC may include a scheduling CC, and the second CC may include a scheduled CC. As shown, the CC can be implemented as a cell and used for, for example, general carrier aggregation scenarios, dynamic spectrum sharing (DSS), etc. In some aspects, the CC may include one or more carriers. In some aspects, the carrier may include one or more CCs. In a typical scenario, UE 120 may connect to a primary cell (shown as "PCell"). UE 120 can maintain a connection to the primary cell, which can provide functions such as initial access, random access, paging, etc.

[0055] In some aspects, a secondary cell (shown as "SCell") can be activated. As shown in the figure, for the purposes of the concepts described herein, both shown CCs can be secondary CCs, or one CC can be a primary CC. In some aspects, the primary and secondary cells can be provided by the same BS 110. In some aspects, the primary and secondary cells can be provided by different BS 110s. In some aspects, for example, a secondary cell can be activated to handle increased traffic. In some aspects, more than one secondary cell can be activated.

[0056] In typical cases, a primary cell can be used to schedule data communications on the primary cell and / or secondary cells. Data communications may include PDSCH communications, Physical Uplink Shared Channel (PUSCH) communications, etc. In some cases, as shown in the figure, a secondary cell can be used to schedule data communications for the secondary cell, another secondary cell, and / or the primary cell. For example, as indicated by reference numeral 300, in cross-CC scheduling, DCI communications 315 transmitted using a secondary cell (scheduling CC) can be used to schedule PDSCH and / or PUSCH communications 320 on the primary cell or another secondary cell (scheduled CC). As indicated by reference numeral 310, in multi-CC scheduling, a secondary cell can be used to transmit DCI communications 325 to schedule PDSCH communications 330 within the same cell and PDSCH communications 335 in the primary cell or another secondary cell.

[0057] Each cell can be associated with one or more corresponding Bandwidth Parts (BWP) configurations. UE 120 can be associated with one or more active BWPs. For example, an active BWP can be associated with a cell. An active BWP can use a BWP configuration for the associated cell. In some aspects, two cells can be associated with corresponding active BWPs. In some aspects, only the scheduling cell can be associated with an active BWP. In some aspects, only the primary cell can be associated with an active BWP.

[0058] Each BWP configuration can be associated with a corresponding search space configuration. The search space configuration can identify the configuration used for the search space (e.g., aggregation level, number of candidates, monitoring period, monitoring symbols within a time slot, DCI format to be monitored, associated control resource set (CORESET), etc.), where the UE will use the configuration used for the search space to receive information when a BWP configuration is used for an active BWP. The search space configuration can be associated with CORESETs included in the BWP configuration. In some aspects, multiple BWP configurations can be associated with a single CORESET. For example, a single CORESET can be included in multiple overlapping BWPs.

[0059] As pointed out above, Figure 3This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0060] Figure 4 This is a diagram illustrating example 400 of cross-CC scheduling according to this disclosure. As shown, a pair of CCs can be configured for cross-CC scheduling.

[0061] like Figure 4 As shown, the primary cell (shown as "PCell") and the secondary cell (shown as "SCell") may include corresponding PDCCH candidates and scheduled data. The primary cell may include a common search space (CSS) containing PDCCH candidates 410 for scheduling data communications 420 (shown as "PDSCH" or "PUSCH") on the primary cell. In some aspects, existing cross-carrier scheduling frameworks for scheduling data communications on the secondary cell using PDCCH candidates on the primary cell may be adapted to schedule data communications on the primary cell using PDCCH candidates on the secondary cell. In some aspects, for example, cross-CC scheduling from the secondary cell to the primary cell may be used for non-back-off DCI with a carrier indicator field (CIF) on a UE-specific search space (USS).

[0062] In some aspects, the UE (e.g., UE 120) can identify PDCCH candidates for DCI scheduling from the secondary cell to the primary cell based on CIF values ​​(e.g., the n_CI variable of a hash function). For example, as shown, a PDCCH candidate 430 on the secondary cell configured to schedule data communications 420 on the primary cell can indicate a CIF value that matches the CIF value associated with the primary cell (e.g., CIF = 0). Similarly, a PDCCH candidate 440 on the secondary cell configured to schedule data communications 450 on the secondary cell can indicate a CIF value that matches the CIF value associated with the secondary cell (e.g., CIF = 1). In some aspects, if the primary cell PDSCH and the secondary cell PDCCH use different subcarrier spacings (SCS), a PDSCH preparation time can be provided to account for timing differences.

[0063] In some aspects, during cross-CC scheduling and / or data communication, the UE can continue to monitor the CSS on the primary cell to maintain UE behavior regarding scenarios such as broadcast, fallback, and radio link failure (RLF). Therefore, in some aspects, the UE can monitor PDCCH candidates 410 and 430 on the two cells used for scheduling primary cell data communication. In some aspects, the UE may not be required to process time-overlapping Cell Radio Network Temporary Identifier (C-RNTI) PDSCHs scheduled by the primary and secondary cells on the primary cell. In some aspects, the UE is able to process time-overlapping unicast PDSCH communications and SI RNTI PDSCH communications during system information (SI) acquisition triggered by paging RNTIs (P-RNTIs) for frequency range 1 (FR1).

[0064] As pointed out above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0065] Figure 5 This is a diagram illustrating examples of cross-CC and multi-CC scheduling according to this disclosure. As shown, a unified DCI format 500 can be provided to schedule data communication 510 (e.g., PDSCH communication) on a first CC (shown as "CC1") and a second CC (shown as "CC2"), wherein CC1 and CC2 are in different frequency bands (shown as "band A" and "band B" respectively). In some aspects, CC1 and CC2 may use different SCS.

[0066] like Figure 5 As shown, a unified DCI format 520 can be provided to schedule data communication 530 on CC1 and CC2, where CC1 and CC2 are in the same frequency band (band A) and use the same SCS. As shown, DCI formats 500 and 520 may include a set of dedicated fields for scheduling data communication on CC1, a set of dedicated fields for scheduling communication on CC2, and a set of combined or common (shown as "combined / common") fields for scheduling CC1 and CC2. As shown, DCI format 520 for scheduling on CC1 and CC2 in the same frequency band may include fewer data fields compared to DCI format 500 for scheduling on CCs in different frequency bands. The combined / common fields enable a reduction in DCI payload, while the dedicated fields promote flexibility.

[0067] As pointed out above, Figure 5 This is provided as an example. Other examples may differ from the one provided. Figure 5 The example described.

[0068] Figure 6 This is a diagram illustrating an example 600 of multi-CC scheduling according to the present disclosure. As shown, the primary cell (“PCell”) can be used to schedule data communications (e.g., PDSCH communications) on the primary cell and secondary cells.

[0069] In some aspects, a DCI for scheduling PDSCHs on multiple CCs can be supported. In some aspects, the UE can identify PDCCH candidates for scheduling a set of CCs, at least in part, based on the DCI. For example, in some aspects, the set of CCs can be configured for scheduling and can be associated with a search space (“SS”) or a specific DCI format. In some aspects, as shown, the primary cell can include a CSS with PDCCH candidates 610 for primary cell functions and an SS with a set of PDCCH candidates 620 for multi-CC scheduling. PDCCH candidates 620 can be indicated, for example, as configured for scheduling data communications (e.g., PDSCH communications) 630 on the primary cell and data communications (e.g., PDSCH communications) 640 on the secondary cell. In some aspects, PDCCH candidates can be indicated in the DCI for multi-CC scheduling. The DCI can include, for example, a bitmap indicating whether a particular PDCCH candidate is configured for scheduling on “CC1”, “CC2”, or “CC1+CC2”. By providing this indication, the network can reduce its reliance on monitoring traditional DCI formats. The conventional format is a format that already existed at the time of filing this application. The conventional format may be, for example, a format defined by a wireless communication standard.

[0070] As pointed out above, Figure 6 This is provided as an example. Other examples may differ from the one provided. Figure 6 The example described.

[0071] In some cases, secondary cells can be activated and / or deactivated based on Media Access Control (MAC) Control Element (MAC-CE) indications, deactivation timers, etc. In some cases, the secondary cell's BWP can be a dormant BWP, in which case the UE may not need to monitor the PDCCH used for the secondary cell. For in Figure 4 In the cross-CC scheduling scenario shown, if the secondary cell is deactivated or the secondary cell's BWP is a dormant BWP, the UE may not receive the DCI format of unicast data (PDSCH and / or PUSCH) on the primary cell.

[0072] For in Figure 6As shown in the multi-CC scheduling diagram, even if the secondary cell is deactivated or its BWP is dormant, the DCI used for multi-CC scheduling can still be used to schedule data on the primary cell. However, many DCI fields may be useless (e.g., fields for the secondary cell), thus unnecessarily increasing control signaling overhead. In some cases, if the DCI used for multi-CC scheduling is used for data scheduling on both the primary and secondary cells, and if DCI is monitored on the secondary cell, then: if the secondary cell is deactivated or its BWP is dormant, the UE may not be able to receive the DCI format for scheduling unicast data (PDSCH and / or PUSCH) on the primary cell. For example, in Figure 6 If multiple CC PDCCH candidates 620 are on a secondary cell, and the secondary cell is deactivated or the BWP associated with the secondary cell is a dormant BWP, the UE may be unable to identify any PDCCH candidates used to schedule data communication on the primary cell. This can lead to service interruptions, lower throughput, less flexibility, and lower reliability.

[0073] The techniques and apparatus described herein can provide alternative UE behaviors for PDCCH monitoring, which are at least partially based on the secondary cell activation / deactivation state and / or whether the secondary cell's BWP is a dormant BWP. In some aspects, the UE can use a first PDCCH monitoring behavior to monitor for a first DCI format, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC. The UE can determine that PDCCH monitoring behavior handover conditions are met, and based at least partially on the determination of meeting the PDCCH monitoring behavior handover conditions, the UE can use a second PDCCH monitoring behavior to monitor for a second DCI format. In some aspects, for example, the UE can determine that PDCCH monitoring behavior handover conditions are met based at least partially on determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, determining that the active downlink BWP meets BWP handover conditions (wherein the active downlink BWP is associated with at least one of the first CC or the second CC), etc.

[0074] In some aspects, the DCI format content of the second DCI format may differ from that of the first DCI format. Therefore, the DCI format content may depend on the secondary cell's activation / deactivation state and / or whether the secondary cell's BWP is a dormant BWP. In this way, data scheduling is still possible in multi-CC scheduling scenarios when a non-scheduled CC is deactivated or its BWP is a dormant BWP. In some aspects, the DCI format size and content may depend on the cell's activation / deactivation state or whether the secondary cell's BWP is a dormant BWP. In this way, data scheduling is still possible in multi-CC scheduling scenarios where a non-scheduled CC is deactivated or its BWP is a dormant BWP. In some aspects, the DCI format type and / or location (e.g., where the DCI format CC is monitored) may depend on the cell's activation / deactivation state or whether the secondary cell's BWP is a dormant BWP. In this way, data scheduling is still possible in cross-CC or multi-CC scheduling scenarios where a scheduling CC is deactivated or its BWP is a dormant BWP. Therefore, the aspects of the techniques described in this paper can help maintain PDCCH candidates for scheduling data when a CC is unable to carry data or DCI, resulting in less service interruption, more throughput, more flexibility and more reliability.

[0075] Figure 7 This is a diagram illustrating an example 700 associated with the deactivation or hibernation of a CC in cross-CC or multi-CC scheduling according to this disclosure. As shown, a base station (e.g., base station 110) and a UE (e.g., UE 120) can communicate with each other. In some aspects, the base station can communicate using two or more different CCs (e.g., a primary cell and one or more secondary cells). In some aspects, the base station may include multiple base stations that can communicate with the UE using multiple CCs.

[0076] As indicated by reference numeral 710 in the accompanying drawings, the base station can transmit and the UE can receive configuration. In some aspects, the configuration may indicate a first DCI format and a second DCI format. In some aspects, the configuration may indicate a cross-CC scheduling scheme, a USS identifier, a CIF value corresponding to a CC, a CIF value corresponding to a PDCCH candidate, PDSCH resources, PUSCH resources, etc.

[0077] As indicated by reference numeral 720, the UE may use a first PDCCH monitoring action to monitor a first DCI format. In some aspects, the first DCI format may indicate a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC. In some aspects, monitoring using the first PDCCH monitoring action may include: monitoring the first PDCCH associated with the first CC.

[0078] As indicated by reference numeral 730, the base station can transmit and the UE can receive first DCI communication. In some aspects, the first DCI communication may include a first DCI format. As indicated by reference numeral 740, the base station can transmit and the UE can receive a BWP handover indication for indicating that the active BWP of the cell is handing over to a BWP that is acting as a dormant BWP. In some aspects, the base station can transmit and the UE can receive an indication that a CC has been deactivated.

[0079] As indicated by reference numeral 750 in the attached figure, the UE can determine that the PDCCH behavior handover conditions are met. In some aspects, the UE can determine that the PDCCH behavior handover conditions are met based at least in part on receiving an indication for BWP handover, an indication for CC deactivation, etc. In some aspects, the UE can determine that the PDCCH monitoring behavior handover conditions are met based at least in part on determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, or determining that the active downlink BWP meets the BWP handover conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC. In some aspects, the UE can determine that the PDCCH monitoring behavior handover conditions are met based at least in part on the expiration of a deactivation timer.

[0080] In some aspects, the UE can determine whether the PDCCH monitoring behavior handover conditions are met, at least in part, based on the determination that the active downlink BWP meets the BWP handover conditions. In some aspects, the UE can determine whether the active downlink BWP meets the BWP handover conditions by determining that the bandwidth of the active downlink BWP meets a bandwidth threshold, determining that the achievable downlink data rate associated with the active downlink BWP meets a threshold, determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP, etc.

[0081] In some aspects, the achievable downlink data rate may be based at least in part on the SCS associated with the active downlink BWP, the number of resource blocks associated with the active downlink BWP, the number of layers associated with the active downlink BWP, the maximum MCS value associated with the active downlink BWP, the overhead factor associated with the active downlink BWP, etc.

[0082] In some aspects, the UE may receive (e.g., from a base station) a list of unscheduled BWPs. The UE can determine that a BWP identifier is identified as an unscheduled BWP by determining that the BWP identifier associated with the active downlink BWP is included in that list. In some aspects, when an active downlink BWP is associated with a scheduling CC that is a secondary cell, the UE can determine that the BWP identifier associated with the active downlink BWP is identified as an unscheduled BWP by determining that the active downlink BWP is a dormant BWP.

[0083] As indicated by reference numeral 760, the UE may use a second PDCCH monitoring action to monitor a second DCI format, at least in part, based on a determination of conditions for satisfying the PDCCH monitoring action switching. In some aspects, monitoring using a second PDCCH monitoring action may include monitoring a second PDCCH associated with a second CC.

[0084] As indicated by reference numeral 770, the base station can transmit and the UE can receive second DCI communication. In some aspects, the second DCI communication may include a configured second DCI format. The second DCI format may differ from the first DCI format. In some aspects, at least one characteristic of the second DCI format may be based at least in part on determining that the PDCCH monitoring behavior handover conditions are met. At least one characteristic of the second DCI format may include the content set of the second DCI format, the size of the second DCI format, the format type corresponding to the second DCI format, etc.

[0085] In some respects, a format type corresponding to a second DCI format can match a format type corresponding to a first DCI format. If a format type is the same as or similar to another format type, these format types can be matched. In some respects, format types can match if the DCI formats include the same data fields. In some respects, the data fields of matching format types can have different sizes.

[0086] In some aspects, the UE can be configured to monitor the first DCI format of the PDSCH on more than one CC. The UE can identify the content and fields of the DCI format based on whether the CC scheduled via the DCI format is active or deactivated. In some aspects, the UE can identify the content and fields of the DCI format based on whether the BWP of the CC scheduled via the DCI format is a non-dormant BWP or a dormant BWP.

[0087] For example, in some aspects, the first CC can be used to transmit first DCI communication with a first DCI format that schedules data communication associated with the first CC and the second CC. The UE and / or base station can determine whether the PDCCH monitoring behavior handover conditions are met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP. The first DCI format may include a set of dedicated data fields associated with the second CC, and in the first DCI format, the set of dedicated data fields associated with the second CC may include PDSCH scheduling information corresponding to the second CC. The set of dedicated data fields associated with the second CC may indicate frequency domain resource allocation, time domain resource allocation, MCS, Hybrid Automatic Repeat Request (HARQ) process identifier (ID), redundancy version (RV), transmit precoding matrix indicator (TPMI), antenna port, etc.

[0088] Based at least in part on determining that the PDCCH monitoring behavior handover conditions are met, the base station may send a second DCI communication to the UE. The second DCI communication may include a second DCI format. In some aspects, the second DCI format may include a set of dedicated data fields associated with the second CC, and in the second DCI format, the set of dedicated data fields associated with the second CC may not include PDSCH scheduling information.

[0089] In some aspects, the set of dedicated data fields associated with the second CC in the second DCI format can be fixed to specific values ​​(e.g., all 1s or all 0s). In some aspects, the payload size of the first DCI format can be equal to the payload size of the second DCI format. In this way, the UE can easily identify the second DCI format because the structure will be the same as the first DCI format. However, due to the unused nature of some fields, signaling overhead may increase in all aspects.

[0090] In some aspects, the UE can identify the content and / or fields and size of the DCI format based on whether the CC scheduled via the DCI format is active or deactivated, whether the BWP of the CC scheduled via the DCI format is a non-dormant BWP or a dormant BWP, etc. For example, in some aspects, at least one characteristic of the second DCI format may include the content set of the second DCI format and the size of the second DCI format. The first DCI format may include a set of dedicated data fields associated with the second CC (as described above), and in the first DCI format, the set of dedicated data fields associated with the second CC may include PDSCH scheduling information corresponding to the second CC. Conversely, the second DCI format may not include the set of dedicated data fields associated with the second CC. In some aspects, the first DCI format has a first payload size, and the second DCI format has a second payload size smaller than the first payload size. In this way, control signaling overhead can be reduced. A trade-off may be that the UE's detection of the second DCI format is less reliable.

[0091] In some aspects, the first DCI format may have a first format type, and the second DCI format may have a second format type. For example, in some aspects, the first format type may correspond to multi-CC scheduling, and the second format type may correspond to single-CC scheduling. In some aspects, for example, the second format type may include DCI format 1_0 (which may alternatively be referred to as conventional DCI format 1_0), DCI format 1_1 (which may alternatively be referred to as conventional DCI format 1_1), or DCI format 1_2 (which may alternatively be referred to as conventional DCI format 1_2). In some aspects, the UE can monitor the first DCI format by monitoring a first PDCCH for the first DCI format, thereby using a first PDCCH monitoring action, where the first PDCCH corresponds to the second CC. The UE can monitor the second DCI format by monitoring a second PDCCH for the second DCI format, thereby using a second PDCCH monitoring action, where the second PDCCH corresponds to the first CC.

[0092] In some aspects, where the UE determines that the PDCCH monitoring behavior handover condition is met by determining that the active downlink BWP (associated with the second CC) meets the BWP handover condition, the UE can use the second PDCCH monitoring behavior for the second DCI format to monitor the second PDCCH for the second format, wherein the second PDCCH corresponds to the first CC or the third CC (e.g., another secondary cell).

[0093] As pointed out above, Figure 7 This is provided as an example. Other examples may differ from the one provided. Figure 7 The example described.

[0094] Figure 8 This is a diagram illustrating an example 800 of managing the deactivation or dormancy of CCs in cross-CC or multi-CC scheduling according to this disclosure. As shown, the UE can be configured to monitor the first DCI format of the PDSCH on more than one CC (shown as "CC1" and "CC2"). The UE can identify the content and fields of the first or second DCI format based on whether the CC scheduled via the DCI format is active or deactivated, or based on whether the BWP of the CC scheduled via the DCI format is a non-dormant BWP or a dormant BWP.

[0095] As shown in the figure, for example, a base station can provide a first CC, where the first CC is a scheduling CC. The base station can send a first DCI communication (shown as "first DCI"), which may include a set of resources associated with multi-CC scheduling. The resource set may include, for example, multiple PDSCH resources associated with a second CC. The first DCI format may include a set of dedicated data fields associated with the second CC, and in the first DCI format, the set of dedicated data fields associated with the second CC includes PDSCH scheduling information. In the second DCI format, the dedicated fields associated with the second CC may not be used for data scheduling.

[0096] As pointed out above, Figure 8 This is provided as an example. Other examples may differ from the one provided. Figure 8 The example described.

[0097] Figure 9 This is a diagram illustrating example 900 of managing the deactivation or dormancy of CCs in cross-CC or multi-CC scheduling according to this disclosure. As shown, the UE can identify the content and / or fields of the DCI format and the size of the DCI format based on whether the CC scheduled via the DCI format is active or deactivated, or based on whether the BWP of the CC scheduled via the DCI format is a non-dormant BWP or a dormant BWP.

[0098] The first DCI format may include a set of dedicated data fields associated with the second CC, and in the first DCI format, the set of dedicated data fields associated with the second CC may include PDSCH scheduling information corresponding to the second CC. As shown in the figure, the second DCI format may not include the set of dedicated data fields associated with the second CC. In some aspects, the first DCI format may have a first payload size, and the second DCI format may have a second payload size smaller than the first payload size.

[0099] As pointed out above, Figure 9 This is provided as an example. Other examples may differ from the one provided. Figure 9The example described.

[0100] Figure 10 This is a diagram illustrating example 1000 of managing the deactivation or dormancy of CCs in cross-CC or multi-CC scheduling according to this disclosure. As shown, the UE can identify the DCI format type that the UE needs to monitor based on whether a CC scheduled via the DCI format is active or deactivated, or whether the BWP of a CC scheduled via the DCI format is a non-dormant BWP or a dormant BWP. In some aspects, a first DCI format may have a first format type, and a second DCI format may have a second format type. The first format type may correspond to multi-CC scheduling, and the second format type may correspond to single-CC scheduling. In some aspects, the second format type may include conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0101] As pointed out above, Figure 10 This is provided as an example. Other examples may differ from the one provided. Figure 10 The example described.

[0102] Figure 11 This is a diagram illustrating an example 1100 of managing the deactivation or dormancy of CCs in cross-CC or multi-CC scheduling according to this disclosure. As shown, the UE can identify the CC to be monitored by the UE at least in part based on whether the scheduled CC is active or deactivated, or whether the BWP of the scheduled CC is a non-dormant BWP or a dormant BWP. A first DCI format may have a first format type, and a second DCI format may have a second format type different from the first format type. In some aspects, as shown, the first format type may correspond to multi-CC scheduling or cross-CC scheduling, and the second format type may correspond to single-CC scheduling.

[0103] As pointed out above, Figure 11 This is provided as an example. Other examples may differ from the one provided. Figure 11 The example described.

[0104] Figure 12 This is a diagram illustrating example 1200 of managing the deactivation or hibernation of CCs in a cross-CC or multi-CC scheduling according to this disclosure. Figure 12 As shown, in Figure 11The concepts illustrated can also be applied in the context of a first DCI format that facilitates cross-CC scheduling from secondary to primary cells. As shown, the UE can identify the CC it will monitor, at least in part, based on whether the scheduled CC is active or deactivated, or whether the scheduled CC's BWP is a non-dormant or dormant BWP. The first DCI format can have a first format type, and the second DCI format can have a second format type different from the first format type. In some aspects, as shown, the first format type can correspond to cross-CC scheduling, and the second format type can correspond to single-CC scheduling.

[0105] As pointed out above, Figure 12 This is provided as an example. Other examples may differ from the one provided. Figure 12 The example described.

[0106] Figure 13 This is a diagram illustrating example 1300 of managing the deactivation or hibernation of CCs in a cross-CC or multi-CC scheduling according to this disclosure. Figure 13 As shown, the various aspects of the techniques described above for managing the deactivation or dormancy of CCs can be applied in scenarios where the PDCCH monitoring behavior is altered based on whether the scheduled CC and / or the scheduled CC is active or whether the activity DL BWP of the scheduled CC and / or the scheduled CC meets one or more conditions.

[0107] For example, in some aspects, the UE can determine whether the PDCCH monitoring behavior handover conditions are met, at least in part, based on the determination that the active downlink BWP meets the BWP handover conditions. As shown in the figure, the UE can determine whether the active downlink BWP meets the BWP handover conditions by determining that the bandwidth of the active downlink BWP meets a bandwidth threshold. In some aspects, the UE can determine whether the active downlink BWP meets the BWP handover conditions by determining that the achievable downlink data rate associated with the active downlink BWP meets a threshold, determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP, etc.

[0108] In some aspects, such as Figure 13 As shown, the UE can use a second PDCCH monitoring behavior to monitor a second DCI format. In some aspects, the UE can monitor a second PDCCH for the second format, where the second PDCCH corresponds to a first CC or a third CC. In some aspects, the first DCI format may include a first format type, and the second DCI format may include a second format type different from the first format type. The first format type may correspond to multi-CC scheduling or cross-CC scheduling, and the second format type may correspond to single-CC scheduling.

[0109] As pointed out above, Figure 13 This is provided as an example. Other examples may differ from the one provided. Figure 13 The example described.

[0110] Figure 14 This is a diagram illustrating, for example, an example process 1400 performed by a UE according to this disclosure. Example process 1400 is an example in which a UE (e.g., UE 120) performs operations associated with managing the deactivation or hibernation of a CC in a cross-CC or multi-CC scheduling.

[0111] like Figure 14 As shown, in some aspects, process 1400 may include: using a first PDCCH monitoring behavior to monitor a first DCI format, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC (box 1410). For example, the UE (e.g., using...) Figure 16 The receiving component 1602) may use a first PDCCH monitoring behavior to monitor a first DCI format, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with the first CC and the second CC, as described above.

[0112] like Figure 14 Further shown, in some aspects, process 1400 may include: monitoring a second DCI format using a second PDCCH monitoring behavior based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior switching conditions (box 1420). For example, the UE (e.g., using...) Figure 16 The receiving component 1602 may use a second PDCCH monitoring behavior to monitor the second DCI format, at least in part, based on the determination of the conditions for satisfying the PDCCH monitoring behavior switching, as described above.

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

[0114] In the first aspect, process 1400 includes: determining (e.g., using...) Figure 16 The determination component 1608) satisfies the PDCCH monitoring behavior switching conditions, wherein determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, or determining that the active downlink BWP satisfies the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0115] In the second aspect, either alone or in combination with the first aspect, the first CC is associated with the primary cell, and the second CC is associated with the secondary cell.

[0116] In the third aspect, either alone or in combination with one or more of the first and second aspects, the second DCI format differs from the first DCI format, and at least one characteristic of the second DCI format is based at least in part on determining that the switching conditions for PDCCH monitoring behavior are met.

[0117] In the fourth aspect, either alone or in combination with one or more aspects from the first to the third aspect, at least one characteristic of the second DCI format includes at least one of the following: the content set of the second DCI format, the size of the second DCI format, or the format type corresponding to the second DCI format.

[0118] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the format type corresponding to the second DCI format is matched with the format type corresponding to the first DCI format, and at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format.

[0119] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, at least one feature of the second DCI format includes a content set of the second DCI format, and the resource set is associated with multi-CC scheduling.

[0120] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, at least one characteristic of the second DCI format includes the content set of the second DCI format and the size of the second DCI format, wherein the resource set is associated with multi-CC scheduling.

[0121] In the eighth aspect, monitoring using the first PDCCH monitoring behavior, either alone or in combination with one or more aspects from the first to the seventh aspect, includes monitoring the first PDCCH associated with the first CC, and monitoring using the second PDCCH monitoring behavior includes monitoring the second PDCCH associated with the second CC.

[0122] In the ninth aspect, either alone or in combination with one or more aspects from the first to the eighth aspects, process 1400 includes: receiving a configuration indicating a first DCI format and a second DCI format.

[0123] In the tenth aspect, either alone or in combination with one or more aspects from the first to the ninth aspects, process 1400 includes: determining that a PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP, wherein the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein in the first DCI format, the set of dedicated data fields associated with the second CC includes PDSCH scheduling information corresponding to the second CC, and wherein the second DCI format includes a set of dedicated data fields associated with the second CC, and wherein in the second DCI format, the set of dedicated data fields associated with the second CC does not include PDSCH scheduling information.

[0124] In the eleventh aspect, either alone or in combination with one or more aspects from the first to the tenth aspects, in the second DCI format, the set of dedicated data fields associated with the second CC is fixed to specific values.

[0125] In the twelfth aspect, either alone or in combination with one or more aspects from the first to the eleventh aspects, the payload size of the first DCI format is equal to the payload size of the second DCI format.

[0126] In the thirteenth aspect, alone or in combination with one or more aspects from the first to the twelfth aspects, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, modulation and coding scheme, hybrid automatic repeat request process identifier, redundancy version, transmit precoding matrix indicator, or antenna port.

[0127] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 1400 includes: determining that a PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP, wherein the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes PDSCH scheduling information corresponding to the second CC, and wherein the second DCI format does not include the set of dedicated data fields associated with the second CC.

[0128] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the first DCI format has a first payload size, and the second DCI format has a second payload size smaller than the first payload size.

[0129] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, MCS, HARQ process ID, RV, TPMI, or antenna port.

[0130] In the seventeenth aspect, either alone or in combination with one or more aspects from the first to the sixteenth aspects, process 1400 includes: determining that the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP, wherein the first DCI format has a first format type and the second DCI format has a second format type.

[0131] In the eighteenth aspect, either alone or in combination with one or more aspects from the first to the seventeenth aspects, the first format type corresponds to a multi-CC schedule, and the second format type corresponds to a single-CC schedule.

[0132] In the nineteenth aspect, either alone or in combination with one or more aspects from the first to the eighteenth aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0133] In the twentieth aspect, monitoring a first PDCCH for a first DCI format, either alone or in combination with one or more of the first to nineteenth aspects, includes: monitoring a first PDCCH for the first DCI format, wherein the first PDCCH corresponds to a second CC, and wherein monitoring a second PDCCH for a second DCI format includes: monitoring a second PDCCH for the second DCI format, wherein the second PDCCH corresponds to the first CC.

[0134] In the twenty-first aspect, either alone or in combination with one or more aspects from the first to the twentieth aspects, process 1400 includes: determining whether the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP.

[0135] In the twenty-second aspect, either alone or in combination with one or more aspects from the first to the twenty-first aspects, the first DCI format has a first format type, and the second DCI format has a second format type different from the first format type.

[0136] In aspect 23, either alone or in combination with one or more aspects from aspects 1 to 22, the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and wherein the second format type corresponds to single-CC scheduling.

[0137] In the twenty-fourth aspect, either alone or in combination with one or more aspects from the first to the twenty-third aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0138] In the 25th aspect, either alone or in combination with one or more of the first to 24th aspects, process 1400 includes: determining that the PDCCH monitoring behavior switching conditions are met, wherein determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0139] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, the active downlink BWP is associated with the second CC, wherein the first DCI format is associated with cross-carrier scheduling, wherein monitoring the first DCI format using the first PDCCH monitoring behavior includes: monitoring the first PDCCH for the first DCI format, wherein the first PDCCH corresponds to the second CC, and wherein monitoring the second DCI format using the second PDCCH monitoring behavior includes: monitoring the second PDCCH for the second format, wherein the second PDCCH corresponds to the first CC or the third CC.

[0140] In the twenty-seventh aspect, either alone or in combination with one or more aspects from the first to the twenty-sixth aspects, the first DCI format has a first format type, and the second DCI format has a second format type different from the first format type.

[0141] In the twenty-eighth aspect, either alone or in combination with one or more aspects from the first to the twenty-seventh aspects, the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and the second format type corresponds to single-CC scheduling.

[0142] In the twenty-ninth aspect, either alone or in combination with one or more aspects from the first to the twenty-eighth aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0143] In the thirtieth aspect, either alone or in combination with one or more aspects from the first to the twenty-ninth aspects, the second PDCCH corresponds to the third CC, and the second DCI format corresponds to cross-CC scheduling.

[0144] In the thirty-first aspect, determining, either alone or in combination with one or more of the first to thirtieth aspects, that the active downlink BWP meets the BWP handover conditions includes at least one of the following: determining that the bandwidth of the active downlink BWP meets a bandwidth threshold, determining that the achievable downlink data rate associated with the active downlink BWP meets a threshold, or determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP.

[0145] In aspect thirty-two, either alone or in combination with one or more aspects from aspect one to aspect thirty-one, the downlink data rate can be made to be based at least in part on at least one of the following: the subcarrier spacing associated with the active downlink BWP, the number of resource blocks associated with the active downlink BWP, the number of layers associated with the active downlink BWP, the maximum MCS value associated with the active downlink BWP, or the overhead factor associated with the active downlink BWP.

[0146] In the thirty-third aspect, either alone or in combination with one or more of the first to thirty-second aspects, process 1400 includes: receiving a list of unscheduled BWPs, wherein determining that a BWP identifier associated with an active downlink BWP is identified as an unscheduled BWP includes: determining that the BWP identifier is included in the list.

[0147] In aspect thirty-four, either alone or in combination with one or more aspects from aspects one through thirty-three, the active downlink BWP is associated with a scheduling CC, wherein the scheduling CC includes secondary cells, and wherein determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP includes: determining that the active downlink BWP is a dormant BWP.

[0148] Although Figure 14 An example box of process 1400 is shown, but in some aspects, process 1400 may include... Figure 14 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1400 may be executed in parallel.

[0149] Figure 15This is a diagram illustrating an example process 1500 performed by a base station, for example, according to this disclosure. Example process 1500 is an example in which a base station (e.g., base station 110) performs operations associated with managing the deactivation or hibernation of CCs in a cross-CC or multi-CC scheduling.

[0150] like Figure 15 As shown, in some aspects, process 1500 may include: sending a first PDSCH communication to the UE using a first plurality of PDSCH resources, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources (block 1510). For example, a base station (e.g., using...) Figure 17 The transmitting component 1704 may use a first plurality of PDSCH resources to transmit a first PDSCH communication to the UE, wherein the first plurality of resources are indicated by a first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of a cross-CC schedule or a multi-CC schedule associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources, as described above.

[0151] like Figure 15 Further shown, in some aspects, process 1500 may include: transmitting second DCI communication with a second DCI format (box 1520) based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions. For example, a base station (e.g., using...) Figure 14 The transmitting component 1704 can transmit second DCI communication with a second DCI format, as described above, based at least in part on the determination of whether the PDCCH monitoring behavior switching conditions are met.

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

[0153] In the first aspect, process 1500 includes: sending a configuration indicating a first DCI format and a second DCI format to the UE.

[0154] In the second aspect, either alone or in combination with the first aspect, process 1500 includes: determining that PDCCH monitoring behavior switching conditions are met, wherein determining that PDCCH monitoring behavior switching conditions are met includes: determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, or determining that the active downlink BWP meets BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0155] In the third aspect, either alone or in combination with one or more of the first and second aspects, the first CC is associated with the primary cell, and the second CC is associated with the secondary cell.

[0156] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the second DCI format differs from the first DCI format, and at least one characteristic of the second DCI format is based at least in part on the determination of the switching conditions for satisfying PDCCH monitoring behavior.

[0157] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, at least one characteristic of the second DCI format includes at least one of the following: the content set of the second DCI format, the size of the second DCI format, or the format type corresponding to the second DCI format.

[0158] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the format type corresponding to the second DCI format is matched with the format type corresponding to the first DCI format, and at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format.

[0159] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, at least one feature of the second DCI format includes a content set of the second DCI format, and the resource set is associated with multi-CC scheduling.

[0160] In the eighth aspect, either alone or in combination with one or more aspects from the first to the seventh aspect, at least one characteristic of the second DCI format includes the content set of the second DCI format and the size of the second DCI format, and the resource set is associated with multi-CC scheduling.

[0161] In the ninth aspect, either alone or in combination with one or more aspects from the first to the eighth aspects, the base station provides a first CC, wherein the first CC includes a scheduled CC, and wherein the method further includes: transmitting a first DCI communication, wherein a resource set is associated with a multi-CC scheduling, and wherein the resource set includes a second plurality of PDSCH resources associated with a second CC, and the determination of whether the PDCCH monitoring behavior handover conditions are met is based at least in part on the determination that the second CC is deactivated or on the determination that the active BWP of the second CC is a dormant BWP.

[0162] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes PDSCH scheduling information, wherein the PDSCH scheduling information indicates a second plurality of PDSCH resources.

[0163] In the eleventh aspect, either alone or in combination with one or more aspects from the first to the tenth aspects, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, MCS, HARQ process ID, RV, TPMI, or antenna port.

[0164] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the second DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the second DCI format, the set of dedicated data fields associated with the second CC does not include PDSCH scheduling information.

[0165] In the thirteenth aspect, either alone or in combination with one or more aspects from the first to the twelfth aspects, in the second DCI format, the set of dedicated data fields associated with the second CC is fixed to specific values.

[0166] In the fourteenth aspect, either alone or in combination with one or more aspects from the first to the thirteenth aspects, the payload size of the first DCI format is equal to the payload size of the second DCI format.

[0167] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the second DCI format does not include a set of dedicated data fields associated with the second CC.

[0168] In the sixteenth aspect, either alone or in combination with one or more aspects from the first to the fifteenth aspects, the first DCI format has a first payload size, and the second DCI format has a second payload size smaller than the first payload size.

[0169] In the seventeenth aspect, the second DCI format has a second format type, either alone or in combination with one or more aspects from the first to the sixteenth aspects.

[0170] In the eighteenth aspect, either alone or in combination with one or more aspects from the first to the seventeenth aspects, the second format type corresponds to a single CC schedule.

[0171] In the nineteenth aspect, either alone or in combination with one or more aspects from the first to the eighteenth aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0172] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the second DCI communication indication includes an additional set of resources of a third plurality of PDSCH resources associated with the first CC.

[0173] In the twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, the base station provides a second CC, wherein the second CC includes a scheduled CC that includes a first plurality of PDSCH resources, and wherein the determination of the handover conditions for satisfying PDCCH monitoring behavior is at least in part based on the determination that the first CC is deactivated or that the active BWP of the first CC is a dormant BWP.

[0174] In the twenty-second aspect, either alone or in combination with one or more aspects from the first to the twenty-first aspects, the first DCI format has a first format type, and the second DCI format has a second format type different from the first format type.

[0175] In aspect 23, either alone or in combination with one or more aspects from aspects 1 to 22, the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and the second format type corresponds to single-CC scheduling.

[0176] In the twenty-fourth aspect, either alone or in combination with one or more aspects from the first to the twenty-third aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0177] In the twenty-fifth aspect, either alone or in combination with one or more of the first to twenty-fourth aspects, the second DCI communication indication includes an additional set of resources of a third plurality of PDSCH resources associated with the second CC.

[0178] In the twenty-sixth aspect, either alone or in combination with one or more of the first to twenty-fifth aspects, the base station provides a second CC, wherein the second CC includes a scheduled CC that includes a first plurality of PDSCH resources, and wherein the determination of the handover conditions for satisfying PDCCH monitoring behavior is based at least in part on the determination of the BWP handover conditions for satisfying the active downlink BWP, wherein the active downlink BWP is associated with the first CC.

[0179] In the twenty-seventh aspect, either alone or in combination with one or more aspects from the first to the twenty-sixth aspects, the first DCI format has a first format type, and the second DCI format has a second format type different from the first format type.

[0180] In the twenty-eighth aspect, either alone or in combination with one or more aspects from the first to the twenty-seventh aspects, the first format type corresponds to cross-CC scheduling, and the second format type corresponds to single-CC scheduling.

[0181] In the twenty-ninth aspect, either alone or in combination with one or more aspects from the first to the twenty-eighth aspects, the second format type includes conventional DCI format 1_0, conventional DCI format 1_1, or conventional DCI format 1_2.

[0182] In the thirtieth aspect, either alone or in combination with one or more of the first to twenty-ninth aspects, the determination of whether the active downlink BWP meets the BWP handover conditions is based at least in part on at least one of the following: the determination of whether the bandwidth of the active downlink BWP meets the bandwidth threshold, the determination of whether the achievable downlink data rate associated with the active downlink BWP meets the threshold, or the determination that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP.

[0183] In the thirty-first aspect, either alone or in combination with one or more of the first to thirtieth aspects, the downlink data rate may be made based at least in part on at least one of the following: the subcarrier spacing associated with the active downlink BWP, the number of resource blocks associated with the active downlink BWP, the number of layers associated with the active downlink BWP, the maximum MCS value associated with the active downlink BWP, or the overhead factor associated with the active downlink BWP.

[0184] In aspect thirty-two, either alone or in combination with one or more of aspects one through thirty-one, the determination that a BWP identifier associated with an active downlink BWP is identified as a non-scheduled BWP is based at least in part on the determination that the BWP identifier is included in the list of non-scheduled BWPs.

[0185] In aspect thirty-three, either alone or in combination with one or more aspects from aspect one to aspect thirty-two, the first CC is a scheduling CC, wherein the scheduling CC is a secondary cell, and the determination that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP is based at least in part on the determination that the active downlink BWP is a dormant BWP.

[0186] Although Figure 15 An example box of process 1500 is shown, but in some aspects, process 1500 may include... Figure 15 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1500 may be executed in parallel.

[0187] Figure 16 This is a block diagram of an example device 1600 for wireless communication. Device 1600 may be a UE, or a UE may include device 1600. In some aspects, device 1600 includes a receiving component 1602 and a transmitting component 1604, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1600 can use the receiving component 1602 and the transmitting component 1604 to communicate with another device 1606 (such as a UE, a base station, or another wireless communication device). As further shown, device 1600 may include one or more of the determining components 1608, and other examples.

[0188] In some respects, device 1600 can be configured to perform the functions described herein. Figure 7-13 One or more operations described herein. Alternatively or concurrently, the apparatus 1600 may be configured to perform one or more processes described herein, such as... Figure 14 The process 1400. In some aspects, in Figure 16 The device 1600 and / or one or more components shown may include the above-described components. Figure 2 One or more components of the UE as described. Alternatively or in addition, in Figure 16 One or more components shown can be combined with the above. Figure 2Implementation within one or more components described. Alternatively, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0189] Receiver 1602 may receive communications from device 1606, such as reference signals, control information, data communications, or combinations thereof. Receiver 1602 may provide the received communications to one or more other components of device 1600. In some aspects, receiver 1602 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1606. In some aspects, receiver 1602 may include the combinations described above. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0190] Transmitting component 1604 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1606. In some aspects, one or more other components of device 1606 can generate communications and provide the generated communications to transmitting component 1604 for transmission to device 1606. In some aspects, transmitting component 1604 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 1606. In some aspects, transmitting component 1604 can include the combinations described above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1604 may be co-located with the receive component 1602 in a transceiver.

[0191] The receiving component 1602 may use a first PDCCH monitoring behavior to monitor a first DCI format, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC. The receiving component 1602 may use a second PDCCH monitoring behavior to monitor a second DCI format based at least in part on a determination of whether the PDCCH monitoring behavior switching conditions are met.

[0192] The transmitting component 1604 may use a first plurality of PDSCH resources to transmit first PDSCH communication to the UE, wherein the first plurality of resources are indicated by first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources. The transmitting component 1604 may transmit second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions.

[0193] The determining component can determine whether the PDCCH monitoring behavior switching conditions are met. For example, in some aspects, the determining component 1608 can determine whether the PDCCH monitoring behavior switching conditions are met by determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, or determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC. The determining component 1608 may include memory. In some aspects, the determining component 1608 may include the above-described combination of... Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0194] exist Figure 16 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 16 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 16 The two or more components shown can be implemented within a single component, or in Figure 16 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 16 The set (one or more) components shown can perform actions described by [the following]: Figure 16 The other set of components shown performs one or more functions.

[0195] Figure 17This is a block diagram of an example device 1700 for wireless communication. Device 1700 may be a base station, or a base station may include device 1700. In some aspects, device 1700 includes a receiving component 1702 and a transmitting component 1704, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1700 can use the receiving component 1702 and the transmitting component 1704 to communicate with another device 1706 (such as a UE, a base station, or another wireless communication device). As further shown, device 1700 may include one or more of the determining components 1708, and other examples.

[0196] In some respects, device 1700 can be configured to perform the functions described herein. Figure 7-13 One or more operations described herein. Alternatively or concurrently, the apparatus 1700 may be configured to perform one or more processes described herein, such as... Figure 15 The process is 1500. In some aspects, in Figure 17 The device 1700 and / or one or more components shown may include the elements described above. Figure 2 One or more components of the described base station. Alternatively or in addition, in Figure 17 One or more components shown can be combined with the above. Figure 2 Implementation within one or more components described. Alternatively, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0197] Receiver 1702 may receive communications from device 1706, such as reference signals, control information, data communications, or combinations thereof. Receiver 1702 may provide the received communications to one or more other components of device 1700. In some aspects, receiver 1702 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1706. In some aspects, receiver 1702 may include the combinations described above. Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0198] Transmitting component 1704 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1706. In some aspects, one or more other components of device 1706 can generate communications and provide the generated communications to transmitting component 1704 for transmission to device 1706. In some aspects, transmitting component 1704 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and can transmit the processed signals to device 1706. In some aspects, transmitting component 1704 can include the combinations described above. Figure 2 The described base station includes one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof. In some aspects, the transmit component 1704 may be co-located with the receive component 1702 in a transceiver.

[0199] The transmitting component 1704 may use a first plurality of PDSCH resources to transmit first PDSCH communication to the UE, wherein the first plurality of resources are indicated by first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources. The transmitting component 1704 may transmit second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior handover conditions.

[0200] The determining component 1708 can determine whether the PDCCH monitoring behavior switching conditions are met. For example, in some aspects, the determining component 1708 can determine whether the PDCCH monitoring behavior switching conditions are met by determining that the second CC is deactivated, determining that the active BWP of the second CC is a dormant BWP, or determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC. The determining component 1708 may include memory. In some aspects, the determining component 1708 may include the above-described combination of... Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof.

[0201] The transmitting component 1704 may use a first plurality of PDSCH resources to transmit first PDSCH communication to a user equipment, wherein the first plurality of resources are indicated by first DCI communication having a first DCI format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first CC and a second CC, wherein the set of resources includes the first plurality of PDSCH resources. The transmitting component 1704 may transmit second DCI communication having a second DCI format based at least in part on a determination regarding the satisfaction of PDCCH monitoring behavior switching conditions.

[0202] exist Figure 17 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 17 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 17 The two or more components shown can be implemented within a single component, or in Figure 17 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 17 The set (one or more) components shown can perform actions described by [the following]: Figure 17 The other set of components shown performs one or more functions.

[0203] The following provides a summary of some aspects of this disclosure:

[0204] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: monitoring a first downlink control information (DCI) format using a first physical downlink control channel (PDCCH) monitoring behavior, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC; and monitoring a second DCI format using a second PDCCH monitoring behavior based at least in part on a determination of conditions for satisfying the PDCCH monitoring behavior switching.

[0205] Aspect 2: The method according to aspect 1 further includes: determining that the PDCCH monitoring behavior switching conditions are met, wherein determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the second CC is deactivated, determining that the active bandwidth portion (BWP) of the second CC is a dormant BWP, or determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0206] Aspect 3: According to the method of aspect 2, wherein the first CC is associated with the primary cell and the second CC is associated with the secondary cell.

[0207] Aspect 4: The method according to any one of Aspects 1-3, wherein the second DCI format is different from the first DCI format, and wherein at least one characteristic of the second DCI format is based at least in part on determining that the switching conditions of the PDCCH monitoring behavior are met.

[0208] Aspect 5: According to the method of aspect 4, wherein the at least one characteristic of the second DCI format includes at least one of the following: the content set of the second DCI format, the size of the second DCI format, or the format type corresponding to the second DCI format.

[0209] Aspect 6: According to the method of aspect 5, wherein the format type corresponding to the second DCI format and the format type corresponding to the first DCI format are matched, and wherein the at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format.

[0210] Aspect 7: The method according to aspect 5 or 6, wherein the at least one feature of the second DCI format includes the content set of the second DCI format, and wherein the resource set is associated with the multi-CC scheduling.

[0211] Aspect 8: The method according to aspect 5 or 6, wherein the at least one characteristic of the second DCI format includes the content set of the second DCI format and the size of the second DCI format, and wherein the resource set is associated with the multi-CC scheduling.

[0212] Aspect 9: The method according to any one of Aspects 1-8, wherein monitoring using the first PDCCH monitoring behavior includes: monitoring a first PDCCH associated with the first CC, and wherein monitoring using the second PDCCH monitoring behavior includes: monitoring a second PDCCH associated with the second CC.

[0213] Aspect 10: The method according to any one of aspects 1-9 further includes: receiving a configuration indicating the first DCI format and the second DCI format.

[0214] Aspect 11: The method according to any one of Aspects 1-10 further comprises: determining that the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or determining that the active bandwidth portion (BWP) of the second CC is a dormant BWP, wherein the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes physical downlink shared channel (PDSCH) scheduling information corresponding to the second CC, and wherein, in the second DCI format, the set of dedicated data fields associated with the second CC does not include the PDSCH scheduling information.

[0215] Aspect 12: According to the method of aspect 11, wherein, in the second DCI format, the set of dedicated data fields associated with the second CC is fixed to specific values.

[0216] Aspect 13: The method according to aspect 11 or 12, wherein the payload size of the first DCI format is equal to the payload size of the second DCI format.

[0217] Aspect 14: The method according to any one of Aspects 11-13, wherein, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, modulation and coding scheme, hybrid automatic repeat request process identifier, redundancy version, transmit precoding matrix indicator, or antenna port.

[0218] Aspect 15: The method according to any one of Aspects 1-14 further comprises: determining that the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or determining that the active bandwidth portion (BWP) of the second CC is a dormant BWP, wherein the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes physical downlink shared channel scheduling information corresponding to the second CC, and wherein the second DCI format does not include the set of dedicated data fields associated with the second CC.

[0219] Aspect 16: The method according to aspect 15, wherein the first DCI format has a first payload size, and wherein the second DCI format has a second payload size smaller than the first payload size.

[0220] Aspect 17: The method according to aspect 15 or 16, wherein, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, modulation and coding scheme, hybrid automatic repeat request process identifier, redundancy version, transmit precoding matrix indicator, or antenna port.

[0221] Aspect 18: The method according to any one of Aspects 1-17 further includes: determining that the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or determining that the active bandwidth portion (BWP) of the second CC is a dormant BWP, wherein the first DCI format has a first format type, and wherein the second DCI format has a second format type.

[0222] Aspect 19: According to the method of aspect 18, wherein the first format type corresponds to a multi-CC schedule, and wherein the second format type corresponds to a single-CC schedule.

[0223] Aspect 20: According to the method of aspect 19, wherein the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0224] Aspect 21: The method according to any one of Aspects 1-20, wherein monitoring the first DCI format using the first PDCCH monitoring behavior comprises: monitoring a first PDCCH for the first DCI format, wherein the first PDCCH corresponds to the second CC, and wherein monitoring the second DCI format using the second PDCCH monitoring behavior comprises: monitoring a second PDCCH for the second DCI format, wherein the second PDCCH corresponds to the first CC.

[0225] Aspect 22: The method according to aspect 21 further includes: determining whether the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active bandwidth portion (BWP) of the second CC is a dormant BWP.

[0226] Aspect 23: The method according to aspect 21 or 22, wherein the first DCI format has a first format type, and wherein the second DCI format has a second format type different from the first format type.

[0227] Aspect 24: According to the method of aspect 23, wherein the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and wherein the second format type corresponds to single-CC scheduling.

[0228] Aspect 25: According to the method of aspect 24, wherein the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0229] Aspect 26: The method according to any one of Aspects 1-25 further includes: determining that the PDCCH monitoring behavior switching conditions are met, wherein determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0230] Aspect 27: The method according to aspect 26, wherein the active downlink BWP is associated with the second CC, wherein the first DCI format is associated with cross-carrier scheduling, wherein monitoring the first DCI format using the first PDCCH monitoring behavior includes: monitoring a first PDCCH for the first DCI format, wherein the first PDCCH corresponds to the second CC, and wherein monitoring the second DCI format using the second PDCCH monitoring behavior includes: monitoring a second PDCCH for the second DCI format, wherein the second PDCCH corresponds to the first CC or a third CC.

[0231] Aspect 28: According to the method of aspect 27, wherein the first DCI format has a first format type, and wherein the second DCI format has a second format type different from the first format type.

[0232] Aspect 29: According to the method of aspect 28, wherein the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and wherein the second format type corresponds to single-CC scheduling.

[0233] Aspect 30: According to the method of aspect 29, wherein the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0234] Aspect 31: The method according to any one of Aspects 27-30, wherein the second PDCCH corresponds to the third CC, and wherein the second DCI format corresponds to cross-CC scheduling.

[0235] Aspect 32: The method according to any one of Aspects 26-31, wherein determining that the active downlink BWP satisfies the BWP switching condition includes at least one of the following: determining that the bandwidth of the active downlink BWP meets a bandwidth threshold, determining that the achievable downlink data rate associated with the active downlink BWP meets a threshold, or determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP.

[0236] Aspect 33: According to the method of aspect 32, wherein the achievable downlink data rate is based at least in part on at least one of the following: the subcarrier spacing associated with the active downlink BWP, the number of resource blocks associated with the active downlink BWP, the number of layers associated with the active downlink BWP, the maximum modulation and coding scheme value associated with the active downlink BWP, or the overhead factor associated with the active downlink BWP.

[0237] Aspect 34: The method according to aspect 32 or 33 further includes: receiving a list of unscheduled BWPs, wherein determining that the BWP identifier associated with the active downlink BWP is identified as an unscheduled BWP includes: determining that the BWP identifier is included in the list.

[0238] Aspect 35: The method according to any one of Aspects 32-34, wherein the active downlink BWP is associated with a scheduling CC, wherein the scheduling CC includes a secondary cell, and wherein determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP includes: determining that the active downlink BWP is a dormant BWP.

[0239] Aspect 36: A method of wireless communication performed by a base station, comprising: transmitting a first PDSCH communication to a user equipment (UE) using a first plurality of physical downlink shared channel (PDSCH) resources, wherein the first plurality of resources are indicated by a first DCI communication having a first downlink control information (DCI) format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; and transmitting a second DCI communication having a second DCI format based at least in part on a determination of handover conditions for satisfying physical downlink control channel (PDCCH) monitoring behavior.

[0240] Aspect 37: The method according to aspect 36 further includes: sending to the UE a configuration indicating the first DCI format and the second DCI format.

[0241] Aspect 38: The method according to any one of Aspects 36 or 37 further includes: determining that the PDCCH monitoring behavior switching conditions are met, wherein determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the second CC is deactivated, determining that the active bandwidth portion (BWP) of the second CC is a dormant BWP, or determining that the active downlink BWP meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC.

[0242] Aspect 39: The method according to any one of Aspects 36-38, wherein the first CC is associated with the primary cell and the second CC is associated with the secondary cell.

[0243] Aspect 40: The method according to any one of Aspects 36-39, wherein the second DCI format is different from the first DCI format, and wherein at least one characteristic of the second DCI format is based at least in part on the determination regarding the satisfaction of the PDCCH monitoring behavior switching conditions.

[0244] Aspect 41: According to the method of aspect 40, wherein the at least one characteristic of the second DCI format includes at least one of the following: the content set of the second DCI format, the size of the second DCI format, or the format type corresponding to the second DCI format.

[0245] Aspect 42: According to the method of aspect 41, wherein the format type corresponding to the second DCI format and the format type corresponding to the first DCI format are matched, and wherein the at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format.

[0246] Aspect 43: The method according to any one of Aspects 41 or 42, wherein the at least one feature of the second DCI format includes the content set of the second DCI format, and wherein the resource set is associated with the multi-CC scheduling.

[0247] Aspect 44: The method according to any one of aspects 41-43, wherein the at least one characteristic of the second DCI format includes the content set of the second DCI format and the size of the second DCI format, and wherein the resource set is associated with the multi-CC scheduling.

[0248] Aspect 45: The method according to any one of Aspects 36-44, wherein the base station provides the first CC, wherein the first CC includes a scheduled CC, and wherein the method further includes: transmitting the first DCI communication, wherein the resource set is associated with a multi-CC scheduling, and wherein the resource set includes a second plurality of PDSCH resources associated with the second CC, and wherein the determination regarding the satisfaction of the PDCCH monitoring behavior switching condition is at least in part based on a determination regarding the second CC being deactivated or a determination regarding the active bandwidth portion (BWP) of the second CC being a dormant BWP.

[0249] Aspect 46: According to the method of aspect 45, wherein the first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes PDSCH scheduling information, wherein the PDSCH scheduling information indicates the second plurality of PDSCH resources.

[0250] Aspect 47: According to the method of aspect 46, wherein, in the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: frequency domain resource allocation, time domain resource allocation, modulation and coding scheme, hybrid automatic repeat request process identifier, redundancy version, transmit precoding matrix indicator, or antenna port.

[0251] Aspect 48: The method according to any one of Aspects 46 or 47, wherein the second DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the second DCI format, the set of dedicated data fields associated with the second CC does not include the PDSCH scheduling information.

[0252] Aspect 49: According to the method of aspect 48, wherein, in the second DCI format, the set of dedicated data fields associated with the second CC is fixed to specific values.

[0253] Aspect 50: The method according to any one of Aspects 48 or 49, wherein the payload size of the first DCI format is equal to the payload size of the second DCI format.

[0254] Aspect 51: The method according to any one of Aspects 46-50, wherein the second DCI format does not include a set of dedicated data fields associated with the second CC.

[0255] Aspect 52: According to the method of aspect 51, wherein the first DCI format has a first payload size, and wherein the second DCI format has a second payload size smaller than the first payload size.

[0256] Aspect 53: The method according to any one of aspects 46-52, wherein the second DCI format has a second format type.

[0257] Aspect 54: According to the method of aspect 53, wherein the second format type corresponds to a single CC schedule.

[0258] Aspect 55: The method according to any one of Aspects 53 or 54, wherein the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0259] Aspect 56: The method according to any one of aspects 45-55, wherein the second DCI communication indication includes an additional set of resources of a third plurality of PDSCH resources associated with the first CC.

[0260] Aspect 57: The method according to any one of Aspects 36-56, wherein the base station provides the second CC, wherein the second CC includes a scheduled CC, the scheduled CC including the first plurality of PDSCH resources; and wherein the determination regarding the satisfaction of the switching conditions of the PDCCH monitoring behavior is at least in part based on the determination regarding the first CC being deactivated or the determination that the active bandwidth portion (BWP) of the first CC is a dormant BWP.

[0261] Aspect 58: The method according to any one of Aspects 36-57, wherein the first DCI format has a first format type, and wherein the second DCI format has a second format type different from the first format type.

[0262] Aspect 59: According to the method of aspect 58, wherein the first format type corresponds to multi-CC scheduling or cross-CC scheduling, and wherein the second format type corresponds to single-CC scheduling.

[0263] Aspect 60: The method according to any one of Aspects 58 or 59, wherein the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0264] Aspect 61: The method according to any one of aspects 58-60, wherein the second DCI communication indication includes an additional set of resources of a third plurality of PDSCH resources associated with the second CC.

[0265] Aspect 62: The method according to any one of Aspects 36-61, wherein the base station provides the second CC, wherein the second CC includes a scheduled CC, the scheduled CC including the first plurality of PDSCH resources; and wherein the determination regarding the satisfaction of the PDCCH monitoring behavior handover condition is at least partially based on the determination regarding the satisfaction of the BWP handover condition of the active downlink BWP, wherein the active downlink BWP is associated with the first CC.

[0266] Aspect 63: According to the method of aspect 62, wherein the first DCI format has a first format type, and wherein the second DCI format has a second format type different from the first format type.

[0267] Aspect 64: According to the method of aspect 63, wherein the first format type corresponds to cross-CC scheduling, and wherein the second format type corresponds to single-CC scheduling.

[0268] Aspect 65: According to the method of aspect 64, the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

[0269] Aspect 66: The method according to any one of Aspects 62-65, wherein the determination of whether the active downlink BWP satisfies the BWP switching condition is based at least in part on at least one of the following: a determination of whether the bandwidth of the active downlink BWP meets a bandwidth threshold, a determination of whether the achievable downlink data rate associated with the active downlink BWP meets a threshold, or a determination that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP.

[0270] Aspect 67: The method according to aspect 66, wherein the achievable downlink data rate is based at least in part on at least one of the following: the subcarrier spacing associated with the active downlink BWP, the number of resource blocks associated with the active downlink BWP, the number of layers associated with the active downlink BWP, the maximum modulation and coding scheme value associated with the active downlink BWP, or the overhead factor associated with the active downlink BWP.

[0271] Aspect 68: The method according to any one of Aspects 66 or 67, wherein the determination that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP is based at least in part on the determination that the BWP identifier is included in a list of non-scheduled BWPs.

[0272] Aspect 69: The method according to any one of Aspects 66-68, wherein the first CC is a scheduling CC, wherein the scheduling CC is a secondary cell, and wherein the determination that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP is at least partially based on the determination that the active downlink BWP is a dormant BWP.

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

[0274] Aspect 71: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more aspects of aspects 1-35.

[0275] Aspect 72: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 1-35.

[0276] Aspect 73: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1-35.

[0277] Aspect 74: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects of aspects 1-35.

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

[0279] Aspect 76: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more aspects of aspects 36-69.

[0280] Aspect 77: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 36-69.

[0281] Aspect 78: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 36-69.

[0282] Aspect 79: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects of aspects 36-69.

[0283] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or modifications and variations may be derived from practice in the aspects.

[0284] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, and other examples. As used herein, processors are implemented using hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented using various forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not a limitation in any respect. Therefore, while the operation and behavior of systems and / or methods are described herein without reference to specific software code, it is to be understood that software and hardware can be designed to implement systems and / or methods, at least in part, based on the descriptions herein.

[0285] As used in this article, depending on the context, satisfying the threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0286] Even if a specific combination of features is recited in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of the aspects. In fact, many of these features can be combined in ways that are not specifically recited in the claims and / or specifically disclosed in the specification. While each dependent claim listed below may depend directly on only one claim, the disclosure of the aspects includes combinations of each dependent claim with every other claim in the claim set. As used herein, the phrase “at least one of” in the list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0287] None of the elements, actions, or instructions used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced in combination with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” Where only one item is anticipated, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series, and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in conjunction with “any” or “only one of them”).

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: Receive configuration indicating the format of the first downlink control information (DCI) and the second DCI format; The first physical downlink control channel (PDCCH) monitoring behavior is used to monitor the first PDCCH for the first DCI format, the first DCI format indicating a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with the first component carrier (CC) and the second CC. Determining that the PDCCH monitoring behavior switching conditions are met includes: determining that the active downlink bandwidth portion (BWP) meets the BWP switching conditions, wherein the active downlink BWP is associated with at least one of the first CC or the second CC, and determining that the active downlink BWP meets the BWP switching conditions includes at least one of the following: Determine that the bandwidth of the active downlink BWP meets the bandwidth threshold. Determine whether the achievable downlink data rate associated with the active downlink BWP meets the threshold, or The BWP identifier associated with the active downlink BWP is determined to be a non-scheduled BWP; and The second PDCCH is monitored for the second DCI format using a second PDCCH monitoring behavior, at least in part, based on the satisfaction of the PDCCH monitoring behavior switching conditions.

2. The method according to claim 1, wherein, The first CC is associated with the primary cell, and the second CC is associated with the secondary cell.

3. The method according to claim 1, wherein, The second DCI format is different from the first DCI format. Wherein, at least one characteristic of the second DCI format is at least partially based on determining that the switching conditions for the PDCCH monitoring behavior are met, and Wherein, the at least one characteristic of the second DCI format includes at least one of the following: The second DCI format content set, The size of the second DCI format, or The format type corresponding to the second DCI format.

4. The method according to claim 3, wherein, The format type corresponding to the second DCI format matches the format type corresponding to the first DCI format, and Wherein, the at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format.

5. The method according to claim 3, wherein, The at least one characteristic of the second DCI format includes at least one of the content set of the second DCI format or the size of the second DCI format, and The resource set is associated with the multi-CC scheduling.

6. The method according to claim 1, wherein, Monitoring using the first PDCCH monitoring behavior includes: monitoring the first PDCCH associated with the first CC, and The monitoring using the second PDCCH monitoring behavior includes: monitoring the second PDCCH associated with the second CC.

7. The method according to claim 1, further comprising: The PDCCH monitoring behavior switching condition is determined by whether the second CC is deactivated or the active BWP of the second CC is a dormant BWP. The first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes physical downlink shared channel (PDSCH) scheduling information corresponding to the second CC. The second DCI format includes the set of dedicated data fields associated with the second CC, and wherein the set of dedicated data fields associated with the second CC in the second DCI format does not include the PDSCH scheduling information.

8. The method according to claim 7, wherein, In the second DCI format, the set of dedicated data fields associated with the second CC is fixed to specific values.

9. The method according to claim 7, wherein, The payload size of the first DCI format is equal to the payload size of the second DCI format.

10. The method according to claim 7, wherein, In the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: Frequency domain resource allocation, Time-domain resource allocation Modulation and coding schemes, Hybrid Automatic Repeat Request Process Identifier Redundant version Send the precoding matrix indicator, or Antenna port.

11. The method according to claim 1, further comprising: The PDCCH monitoring behavior switching condition is determined by whether the second CC is deactivated or the active BWP of the second CC is a dormant BWP. The first DCI format includes a set of dedicated data fields associated with the second CC, and wherein, in the first DCI format, the set of dedicated data fields associated with the second CC includes physical downlink shared channel scheduling information corresponding to the second CC. The second DCI format does not include the set of dedicated data fields associated with the second CC.

12. The method according to claim 11, wherein, The first DCI format has a first payload size, and The second DCI format has a second payload size that is smaller than the first payload size.

13. The method according to claim 11, wherein, In the first DCI format, the set of dedicated data fields associated with the second CC indicates at least one of the following: Frequency domain resource allocation, Time-domain resource allocation Modulation and coding schemes, Hybrid Automatic Repeat Request Process Identifier Redundant version Send the precoding matrix indicator, or Antenna port.

14. The method according to claim 1, further comprising: The PDCCH monitoring behavior switching condition is determined by whether the second CC is deactivated or the active BWP of the second CC is a dormant BWP. Wherein, the first DCI format has a first format type, and The second DCI format has a second format type.

15. The method according to claim 14, wherein, The first format type corresponds to multi-CC scheduling, and The second format type corresponds to a single CC schedule, and the second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

16. The method according to claim 1, wherein, in, The first PDCCH corresponds to the second CC, and the method further includes: determining whether the PDCCH monitoring behavior switching condition is met by determining that the second CC is deactivated or that the active BWP of the second CC is a dormant BWP. The first DCI format has a first format type, and the second DCI format has a second format type that is different from the first format type.

17. The method according to claim 16, wherein, The first format type corresponds to multi-CC scheduling or cross-CC scheduling. The second format type corresponds to a single CC schedule, and The second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

18. The method according to claim 1, wherein, The active downlink BWP is associated with the second CC, wherein the first DCI format is associated with cross-carrier scheduling. Wherein, the first PDCCH corresponds to the second CC, and Wherein, the second PDCCH corresponds to the first CC or the third CC.

19. The method according to claim 18, wherein, The first DCI format has a first format type, and the second DCI format has a second format type that is different from the first format type.

20. The method according to claim 19, wherein, The first format type corresponds to multi-CC scheduling or cross-CC scheduling, and The second format type corresponds to a single CC schedule, and The second format type includes: DCI format 1_0, DCI format 1_1, or DCI format 1_2.

21. The method according to claim 20, wherein, The second PDCCH corresponds to the third CC, and The second DCI format corresponds to cross-CC scheduling.

22. The method according to claim 1, wherein, The achievable downlink data rate is based, at least in part, on at least one of the following: The subcarrier spacing associated with the active downlink BWP, The number of resource blocks associated with the active downlink BWP. The number of layers associated with the active downlink BWP, The maximum modulation and coding scheme value associated with the active downlink BWP, or The overhead factor associated with the active downlink BWP.

23. The method according to claim 1, further comprising: Receiving a list of unscheduled BWPs, wherein determining that the BWP identifier associated with the active downlink BWP is identified as an unscheduled BWP includes: determining that the BWP identifier is included in the list.

24. The method according to claim 1, wherein, The active downlink BWP is associated with the scheduling CC. Wherein, the scheduling CC includes secondary cells, and Specifically, determining that the BWP identifier associated with the active downlink BWP is identified as a non-scheduled BWP includes: determining that the active downlink BWP is a dormant BWP.

25. A method for wireless communication performed by a network entity, comprising: The first PDSCH communication is sent to the user equipment (UE) using a first plurality of physical downlink shared channel (PDSCH) resources, wherein the first plurality of PDSCH resources are indicated by a first DCI communication having a first downlink control information (DCI) format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; Determining whether the Physical Downlink Control Channel (PDCCH) monitoring behavior switching conditions are met includes: determining whether the Active Downlink Bandwidth Port (BWP) meets the BWP switching conditions, wherein the Active Downlink BWP is associated with at least one of the first CC or the second CC, and determining whether the Active Downlink BWP meets the BWP switching conditions includes at least one of the following: Determine that the bandwidth of the active downlink BWP meets the bandwidth threshold. Determine whether the achievable downlink data rate associated with the active downlink BWP meets the threshold, or The BWP identifier associated with the active downlink BWP is determined to be a non-scheduled BWP; and The second DCI communication with the second DCI format is sent at least in part based on the satisfaction of the PDCCH monitoring behavior switching conditions.

26. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as One or more processors coupled to the memory, the one or more processors being configured to perform the method according to any one of claims 1 to 24.

27. An apparatus for wireless communication at a network entity, comprising: Memory; as well as One or more processors coupled to the memory, the one or more processors being configured to: The first PDSCH communication is sent to the user equipment (UE) using a first plurality of physical downlink shared channel (PDSCH) resources, wherein the first plurality of PDSCH resources are indicated by a first DCI communication having a first downlink control information (DCI) format, wherein the first DCI communication indicates a set of resources associated with at least one of cross-CC scheduling or multi-CC scheduling associated with a first component carrier (CC) and a second CC, wherein the set of resources includes the first plurality of PDSCH resources; Determining whether the Physical Downlink Control Channel (PDCCH) monitoring behavior switching conditions are met includes: determining whether the Active Downlink Bandwidth Port (BWP) meets the BWP switching conditions, wherein the Active Downlink BWP is associated with at least one of the first CC or the second CC, and determining whether the Active Downlink BWP meets the BWP switching conditions includes at least one of the following: Determine that the bandwidth of the active downlink BWP meets the bandwidth threshold. Determine whether the achievable downlink data rate associated with the active downlink BWP meets the threshold, or The BWP identifier associated with the active downlink BWP is determined to be a non-scheduled BWP; and The second DCI communication with the second DCI format is sent at least in part based on the satisfaction of the PDCCH monitoring behavior switching conditions.

Images