Techniques for monitoring physical downlink control channels in multi-cell scheduling scenarios

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a physical downlink control channel (PDCCH) monitoring configuration associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers, the PDCCH monitoring configuration associated with a splitting parameter for DCI monitoring or a hierarchical structure for DCI monitoring. The UE may monitor DCI having a format from the set of DCI formats on the set of component carriers, the monitoring based at least in part on the splitting parameter or the hierarchy. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 382,239, filed on November 3, 2022, entitled "TECHNIQUES FOR MONITORING A PHYSICAL DOWNLINK CONTROL CHANNEL IN A MULTI - CELL SCHEDULING SCENARIO" and U.S. Non - Provisional Patent Application No. 18 / 464,980, filed on September 11, 2023, entitled "TECHNIQUES FOR MONITORING A PHYSICAL DOWNLINK CONTROL CHANNEL IN A MULTI - CELL SCHEDULING SCENARIO", the entire disclosures of which are hereby incorporated by reference herein. Field of Technology

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatuses for monitoring a physical downlink control channel in a multi - cell scheduling scenario.

[0004] Description of Related Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, time division - synchronous code division multiple access (TD - SCDMA) systems, and long - term evolution (LTE). LTE / LTE - Advanced is an enhanced collection of the Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the Third Generation Partnership Project (3GPP).

[0006] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., sidelink (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link, etc.).

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, or global level. New Radio (NR) (which may also be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, Multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation to improve spectral efficiency, reduce costs, improve services, utilize new spectra, and better integrate with other open standards. Summary of the Invention

[0008] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: receiving a Physical Downlink Control Channel (PDCCH) monitoring configuration that is associated with a set of Downlink Control Information (DCI) formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a splitting parameter for DCI monitoring or a hierarchical structure for DCI monitoring. The method may include: monitoring DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the splitting parameter or the hierarchical structure.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a split parameter for DCI monitoring or a hierarchical structure for DCI monitoring. The one or more processors may be configured to monitor for DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the split parameter or the hierarchical structure.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a split parameter for DCI monitoring or a hierarchical structure for DCI monitoring. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor for DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the split parameter or the hierarchical structure.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a split parameter for DCI monitoring or a hierarchical structure for DCI monitoring. The apparatus may include means for monitoring for DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the split parameter or the hierarchical structure.

[0012] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: receiving a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers. The method may include: monitoring a set of DCIs on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, wherein the first payload is aligned with the second payload in association with an amount of a size in the PDCCH monitoring configuration exceeding a threshold.

[0013] Some aspects described herein relate to a UE for wireless communication. The user equipment may include one or more memories and one or more processors, the one or more processors being coupled to the one or more memories. The one or more processors may be configured to receive a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers. The one or more processors may be configured to monitor a set of DCIs on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, and wherein the first payload is aligned with the second payload in association with a size in the PDCCH monitoring configuration exceeding a threshold.

[0014] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the figures and the specification and as illustrated in the figures and the specification.

[0015] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and operation methods, as well as the associated advantages, will be better understood when considered in conjunction with the accompanying figures. Each of the figures provided in the accompanying drawings is for purposes of illustration and description and is not a definition of the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] To gain a more particular understanding of the above-described features of the present disclosure, a more specific description of the inventive concepts briefly summarized above may be obtained by reference to aspects, some of which are illustrated in the figures. It should be noted, however, that the figures merely illustrate certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the specification may admit other equally effective aspects. The same reference numerals in different figures may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network.

[0018] Figure 2 is a diagram illustrating an example of a network node communicating with a user equipment (UE) in a wireless network.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4A and Figure 4B is a diagram illustrating an example of downlink control information (DCI)-based scheduling according to the present disclosure.

[0021] Figure 5A and Figure 5B is a diagram illustrating an example of DCI size alignment according to the present disclosure.

[0022] Figure 6A and Figure 6B is a diagram illustrating an example of downlink control channel monitoring according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of downlink control channel size according to the present disclosure.

[0024] Figures 8A to 8D is a diagram illustrating an example associated with monitoring for a physical downlink control channel (PDCCH) in a multi-cell scheduling scenario according to the present disclosure.

[0025] Figures 9A to 9B is a diagram illustrating an example associated with size alignment in a multi-cell scheduling scenario according to the present disclosure.

[0026] Figure 10 is a diagram illustrating an example process, such as may be performed by a user equipment (UE), according to the present disclosure.

[0027] Figure 11 is a diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0028] A user equipment (UE) may be configured to monitor a maximum amount of downlink control information (DCI) sizes. For example, the UE may monitor three DCI sizes for a cell radio network temporary identifier (C-RNTI), a cell-specific radio network temporary identifier (CS-RNTI), and / or a modulation and coding scheme C-RNTI (MCS-C-RNTI), and one additional DCI size for other radio network temporary identifiers (RNTIs). This example configuration of the UE may be referred to as a “3 + 1” DCI size budget, as described in more detail herein.

[0029] The DCI can be associated with a Carrier Indicator Field (CIF) value, which can correspond to the carrier on which the DCI is being scheduled. The cell on which the DCI is received can be referred to as the "scheduling cell", and the cell that the DCI is scheduling can be referred to as the "scheduled cell". Each CIF value can be associated with a different cell in a one-to-one mapping manner, such as a first CIF value mapped to a first cell, a second CIF value mapped to a second cell, and a third CIF value mapped to a third cell. Each cell and each CIF value can have a separate maximum configured amount of blind decoding (BD), control channel elements (CCEs), and / or DCI size. Thus, each CIF value can be associated with a separate 3+1 DCI size budget.

[0030] However, when multiple types of DCI formats are configured in the network as described in more detail herein, a component carrier can be associated with more DCI sizes than are allowed. For example, a component carrier can be associated with 3 DCI sizes for a first type of DCI format and 2 DCI sizes for a second type of DCI format. When the component carrier is out of budget (e.g., can be associated with more DCI sizes than are allowed under the DCI size budget), the UE may not be able to successfully decode the DCI.

[0031] Some aspects described herein enable multi-cell scheduling via a single DCI without violating the DCI size budget. For example, the UE can report a split ratio parameter (or other split parameter), which can correspond to the amount of blind decoding between different formats of the DCI that the UE can support. The UE can be configured to perform blind decoding using the split ratio and can perform monitoring using the configuration for blind decoding and / or at least partially based on an indication of execution monitoring. In this way, by introducing the split ratio, the UE and the network node can avoid the component carrier out-of-budget problem, thereby ensuring successful blind decoding. Additionally or alternatively, the blind decoding can be divided into a set of hierarchical groups based on rules or configuration. In this case, the set of groups enables limiting the blind decoding, thereby avoiding the component carrier out-of-budget problem, as described in more detail herein. Additionally or alternatively, the UE can perform a size alignment procedure, as described herein, to ensure that the component carrier does not exceed the budget with respect to the amount of different DCI formats that the UE is to monitor, thereby avoiding the component carrier out-of-budget problem.

[0032] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific 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 the present disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement a device or practice a method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0033] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0034] Although terms generally associated with 5G or New Radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0035] Figure 1FIG. is a diagram illustrating an example of a wireless network 100. The wireless network 100 can be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or can include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 can include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e) or other entities. The network node 110 is an example of a network node that communicates with the UE 120. As shown, the network node 110 can include one or more network nodes. For example, the network node 110 can be an aggregated network node, which means that the aggregated network node is configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). Another example is that the network node 110 can be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0036] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 can include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 can be interconnected with each other or interconnected to one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0037] In some examples, network node 110 may provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of network node 110 or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographical area and may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographical area (e.g., a residence) and may allow restricted access by UEs 120 associated with that femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell may be referred to as a macro network node. The network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. In Figure 1 the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving network node 110 (e.g., a mobile network node).

[0038] In some aspects, the term "base station" or "network node" may refer to a centralized base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, an RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0039] Wireless network 100 may include one or more relay stations. A relay station is a network node that receives a transmission of data from an upstream node (e.g., network node 110 or UE 120) and forwards the transmission of data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In Figure 1 the example shown, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communication may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a relay, etc.

[0040] Wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watt to 2 watts).

[0041] The network controller 130 may be coupled to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a fronthaul communication link or a midhaul communication link. The network nodes 110 may communicate directly with each other or indirectly via a wireless fronthaul communication link or a wired fronthaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0042] UEs 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. The UEs 120 may include, for example, access terminals, terminals, mobile stations, or subscriber units. The UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless or wired medium.

[0043] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UE or eMTC UE may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, meters, monitors, or location markers that may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

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

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communicating with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which can include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such examples, UE 120 can perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0046] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the “sub-6 GHz” band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0047] The frequency between FR1 and FR2 is generally referred to as the mid-band frequency. Recent 5G NR research has identified the operating bands for these mid-band frequencies as the frequency range designated FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended into the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designated FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0048] Considering these examples, unless otherwise specifically stated, if the term "below 6 GHz" is used herein, it can generally represent frequencies that can be less than 6 GHz, frequencies that can be within FR1, or frequencies that can include the mid-band frequencies. Additionally, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it can broadly represent frequencies that can include the mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1, or FR5, or can be within the EHF band. It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein apply to those modified frequency ranges.

[0049] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a physical downlink control channel (PDCCH) monitoring configuration associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with split parameters for DCI monitoring or a hierarchical structure for DCI monitoring; and monitor DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the split parameters or the hierarchical structure. In some aspects, the communication manager 140 may receive a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers; and monitor a set of DCI on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, wherein the first payload is aligned with the second payload in association with an amount of a size in the PDCCH monitoring configuration exceeding a threshold. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 is provided as an example. Other examples may differ from the example described with respect to Figure 1 the example described.

[0051] Figure 2 FIG. 200 is a diagram illustrating an example 200 in which a network node 110 communicates with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0052] At network node 110, a transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may use one or more channel quality indicators (CQIs) received from UE 120 to select one or more modulation and coding schemes (MCSs) for the UE 120. The network node 110 may use the MCS selected for UE 120 to process (e.g., encode and modulate) the data for UE 120 and may provide data symbols to UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRSs) or demodulation reference signals (DMRSs)) and synchronization signals (e.g., primary synchronization signals (PSSs) or secondary synchronization signals (SSSs)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use the corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, down-convert, or digitize) the received signal using the respective demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols when applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data for the UE 120 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0055] One or more antennas (e.g., antennas 234a through 234t or antennas 252a through 252r) may include or may be included within one or more of the following: one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (within a single housing or multiple housings), a coplanar set of antenna elements, a non-coplanar set of antenna elements, or one or more antenna elements coupled to one or more transmit or receive components (such as Figure 2 one or more components) of.

[0056] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-coded by the TX MIMO processor 266 if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the processes described herein (e.g., with reference to Figures 8A to 11 ).

[0057] At the network node 110, the uplink signal from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., the demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 if applicable, and further processed by the receive processor 238 to obtain the decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna 234, the modem 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and the memory 242 to perform aspects of any of the processes described herein (e.g., with reference to Figures 8A to 11 ).

[0058] In some aspects, the controller / processor 280 can be a component of a processing system. A processing system can generally be a system or a series of machines or components that receive inputs and process the inputs to produce outputs (which can be passed to other systems or components such as the UE 120). For example, the processing system of the UE 120 can be a system that includes various other components or sub-components of the UE 120.

[0059] The processing system of the UE 120 can interface with one or more other components of the UE 120, process information (such as inputs or signals) received from one or more other components, or output information to one or more other components. For example, a chip or modem of the UE 120 can include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface can be an interface between the processing system of the chip or modem and a receiver, such that the UE 120 can receive information or signal inputs and pass the information to the processing system. In some examples, the second interface can be an interface between the processing system of the chip or modem and a transmitter, such that the UE 120 can transmit information output from the chip or modem. Those of ordinary skill in the art will readily recognize that the second interface can also obtain or receive information or signal inputs, and the first interface can also output, transmit, or provide information.

[0060] In some aspects, the controller / processor 240 can be a component of a processing system. A processing system can generally be a system or a series of machines or components that receive inputs and process the inputs to produce outputs (which can be passed to other systems or components such as the network node 110). For example, the processing system of the network node 110 can be a system that includes various other components or sub-components of the network node 110.

[0061] The processing system of network node 110 can interface with one or more other components of network node 110, process information (such as inputs or signals) received from one or more other components, or output information to one or more other components. For example, a chip or modem of network node 110 can include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface can be an interface between the processing system of the chip or modem and a receiver, such that network node 110 can receive information or signal inputs and pass the information to the processing system. In some examples, the second interface can be an interface between the processing system of the chip or modem and a transmitter, such that network node 110 can transmit information output from the chip or modem. Those of ordinary skill in the art will readily recognize that the second interface can also obtain or receive information or signal inputs, and the first interface can also output, transmit, or provide information.

[0062] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2 any other component of can perform one or more techniques associated with monitoring the PDCCH in a multi-cell scheduling scenario, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2 any other component (or combination of components) of can perform or direct the operation of, for example, Figure 10 process 1000 and / or other processes as described herein. Memories 242 and 282 can store data and program code for network node 110 and UE 120, respectively. In some examples, memories 242 and 282 can include non-transitory computer-readable media storing one or more instructions (e.g., code or program code) for wireless communication. For example, when executed (e.g., directly executed, or after compilation, conversion, or interpretation) by one or more processors of network node 110 or UE 120, the one or more instructions can cause the one or more processors, UE 120, or network node 110 to perform or direct the operation of, for example, Figure 10 process 1000 and / or other processes as described herein. In some examples, executing the instructions can include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0063] In some aspects, the UE 120 includes components for receiving a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with split parameters for DCI monitoring or a hierarchical structure for DCI monitoring; and / or components for monitoring DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the split parameters or the hierarchical structure. In some aspects, the UE 120 includes components for receiving a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers; and components for monitoring a set of DCIs on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, wherein the first payload is aligned with the second payload in association with an amount of size in the PDCCH monitoring configuration exceeding a threshold. Components for the UE 120 to perform the operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0064] Although Figure 2 the boxes in are illustrated as different components, the functions described above for these boxes may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described for transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0065] In some aspects, a single processor may execute all functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions jointly. For example, a first set of (one or more) processors among the one or more processors may execute a first function described as being performed by the one or more processors, and a second set of (one or more) processors among the one or more processors may execute a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. The reference to "one or more processors" should be understood to refer to a combination Figure 2Any one or more of the processors described. A reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as the memory described in conjunction with Figure 2 the memory described. For example, functions described as being performed by one or more memories may be performed by the same subset or different subsets of the one or more memories.

[0066] As indicated above, Figure 2 is provided as an example. Other examples may be different from the examples described with respect to Figure 2 the examples described.

[0067] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in an integrated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an integrated base station (also referred to as a stand-alone base station or monolithic base station) or a disaggregated base station. A "network entity" or "network node" can refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0068] An integrated base station (e.g., an integrated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU), etc.

[0069] Base station type operations or network design may consider the aggregation characteristics of base station functionality. For example, a split base station can be utilized in an IAB network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. The split base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can achieve flexibility in network design. Each unit of the split base station can be configured for wired or wireless communication with at least one other unit of the split base station.

[0070] Figure 3 FIG. is an illustration of an example split base station architecture 300 according to the present disclosure. The split base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as through an F1 interface). Each DU in the DUs 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU in the RUs 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some specific implementations, the UE 120 may be served simultaneously by multiple RUs 340.

[0071] Each unit (including the CU 310, DU 330, RU 340) and the near RT RIC 325, non-RT RIC 315, and SMO framework 305 may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or the associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each unit may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), the receiver, transmitter, or transceiver being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium or perform both.

[0072] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include, for example, Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, among others. Each control function may utilize an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP) functionality), control plane functionality (e.g., Central Unit - Control Plane (CU-CP) functionality), or a combination thereof. In some embodiments, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0073] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host at least a portion of the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and one or more of the higher Physical (PHY) layers, at least in part according to a functional split such as that defined by 3GPP. In some aspects, one or more of the higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other things. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other things. Each layer (which may also be referred to as a module) may utilize an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0074] Each RU 340 can implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on functional split (such as the functional split defined by 3GPP), such as lower layer functional split. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communication with one or more UEs 120. In some specific implementations, the real-time aspects and non-real-time aspects of the control plane communication and user plane communication with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0075] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspect of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can directly communicate with each RU in one or more RUs 340 via the corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0076] The non-RT RIC 315 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface), which connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

[0077] In some embodiments, to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0078] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 The examples described above are provided as examples. Other examples may be different from the examples described with respect to

[0079] Figure 4A and Figure 4B are diagrams illustrating example 400 / 400' of DCI-based scheduling according to the present disclosure. As Figure 4A and Figure 4B shown, the network node 110 and the UE 120 can communicate with each other (e.g., directly or via one or more network nodes).

[0080] As Figure 4AAs shown, as an example 400 of self-scheduling, network node 110 may send a set of DCI 405 for scheduling communications for UE 120. The communications may be scheduled on the same cell where the set of DCI 405 is conveyed. In some cases, the cell may be referred to as a component carrier (CC). For example, as shown, the first DCI 405 schedules communications for the first cell 410 (shown as CC0) carrying the first DCI 405, the second DCI 405 schedules communications for the second cell 415 (shown as CC1) carrying the second DCI 405, and the third DCI 405 schedules communications for the third cell 420 (shown as CC2) carrying the third DCI 405.

[0081] As Figure 4B shown, network node 110 may send a single DCI 405 for scheduling multiple communications for UE 120 (e.g., directly or via one or more network nodes). The multiple communications may be scheduled for at least two different cells. In some cases, the DCI for scheduling communications for the cell via which the DCI is sent may be referred to as self-carrier (or self-cell) scheduling DCI. In some cases, the DCI for scheduling communications for the cell via which the DCI is sent may be referred to as cross-carrier (or cross-cell) scheduling DCI. In some aspects, DCI 405 may be a cross-carrier scheduling DCI and may or may not be a self-carrier scheduling DCI. In some aspects, the DCI 405 carrying communications in at least two cells may be referred to as a combined DCI.

[0082] In example 400', the single DCI 405 schedules communications for the first cell 410 (shown as CC0) carrying DCI 405, schedules communications for the second cell 415 (shown as CC1) not carrying DCI 405, and schedules communications for the third cell 420 (shown as CC2) not carrying DCI 405. In some aspects, DCI 405 may schedule communications on Figure 4B shown different numbers of cells (e.g., two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0083] Communications scheduled by DCI 405 may include data communications such as physical downlink shared channel (PDSCH) communications, physical uplink shared channel (PUSCH) communications. For data communications, DCI 405 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs separately in multiple cells. Additionally or alternatively, communications scheduled by DCI 405 may include reference signals such as channel state information (CSI) reference signal (RS) (CSI-RS) or sounding reference signal (SRS). For reference signals, DCI 405 may trigger a single resource for reference signal transmission across multiple cells, or may schedule multiple resources separately for reference signal transmission in multiple cells. In some cases, the scheduling information in DCI 405 may be indicated once and reused for multiple communications (e.g., on different cells), such as modulation and coding scheme (MCS), resources for acknowledgement (ACK) or negative acknowledgement (NACK) to be used for the communications scheduled by DCI 405, and / or resource allocation for the scheduled communications, to save signaling overhead.

[0084] In the self-scheduling use case, as Figure 4A shown, each DCI may have a configured maximum amount M of blind decoding (BD) and a configured maximum amount C of CCEs. In some cases, M and C may be fixed values and / or the same values. In other cases, M and C may have varying values and / or may be different values. For example, the values of M and C may be at least partially based on the amount of carriers in the carrier aggregation configuration, the amount of subcarrier spacing of the carriers in the carrier aggregation configuration, or UE capabilities for PDCCH processing, etc. Thus, when the value of one or more of the foregoing factors changes, the value of M and / or C may change.

[0085] Each DCI may be configured with at most a maximum amount N of DCI formats. For example, the first DCI 405 may have at most 4 DCI formats (e.g., selected from DCI format 0_0, 1_0, 0_1, 1_1 or 0_2, 1_2) and at most 3 + 1 DCI sizes, as regarding Figure 5A and Figure 5Bis described in more detail. In contrast, the third DCI 405 can enable PDCCH overbooking (OB) and can have up to 6 DCI formats (e.g., selected from the aforementioned DCI formats) and up to 3 + 1 DCI sizes. Different types of DCI formats can be possible, such as the first type of DCI formats specified in 3GPP Release 16 (Rel.16), such as DCI format 0_0, 1_0, 0_1, 1_1 or 0_2, 1_2, etc. The second type of DCI formats has been proposed for 3GPP Release 18 (Rel.18), such as, DCI format 0_X or 1_X, etc. In some cases, the first type of DCI formats can be referred to as "legacy DCI formats", and the second type of DCI formats can be referred to as "non-legacy DCI formats" or "Rel-18 DCI formats". In the case of cross-carrier scheduling, DCI 405 can be associated with a carrier indicator field (CIF) value n CI associated. Each CIF value can correspond to the cell being scheduled by DCI 405. For example, regarding Figure 4A , each DCI in each component carrier can be associated with a CIF value associated with up to M BDs and up to C CCEs. Similarly, regarding Figure 4B , CC0 can convey one or more DCIs with one or more CIF values. For example, CC0 can convey 3 DCI messages with 3 CIF values corresponding to 3 component carriers being scheduled. In this case, each CIF value and the corresponding DCI can be associated with up to M BDs and up to C CCEs. In addition, each CIF value and the corresponding DCI can be associated with a maximum number of DCI formats, such as up to 4 DCI formats for the first CIF value and the first corresponding DCI and up to 6 DCI formats for the second CIF value and the second corresponding DCI. The UE (such as UE 120) can determine the amount of PDCCH candidates to monitor in a search space with a specific identifier for each aggregation level at least partially based on the search space set configuration for the bandwidth part. The search space set configuration can indicate BD or CCE limitations on a per-scheduled cell basis. Additional details regarding the search space set and the associated CCEs are provided in 3GPP Technical Specification (TS) 38.213 Rel.16, version 16.11.0, section 10.1.

[0086] As indicated above, Figure 4A and Figure 4B are provided as examples. Other examples can be different from the examples described regarding Figure 4A and Figure 4B .

[0087] Figure 5A and Figure 5BFIG. is an illustration of example 500 of DCI size alignment according to the present disclosure.

[0088] As Figure 5A And as shown by step 505, a UE such as UE 120 may determine a first size (size A) of common search space (CSS) DCI 0_0 and CSS DCI 1_0 (if CSS DCI 0_0 or CSS DCI 1_0 is configured respectively). In some cases, the UE may align the sizes of CSS DCI 0_0 and CSS DCI 1_0. For example, when CSS DCI 0_0 has a larger size compared to CSS DCI 1_0, the UE may add a set of zero-padding bits to CSS DCI 0_0 until the payload size is equal to the payload size of DCI 1_0. Conversely, if CSS DCI 0_0 has a smaller size compared to CSS DCI 1_0 before truncation, the UE may reduce the bit width of the frequency domain resource assignment (FDRA) field in DCI 0_0 by truncating the first few most significant bits, such that the size of DCI 0_0 is equal to the size of DCI 1_0.

[0089] As Figure 5A And as further shown by step 510, the UE may determine a second size (size B) of UE-specific search space (USS) DCI 0_0 and USS DCI 1_0 (if USS DCI 0_0 or USS DCI 1_0 is configured respectively). In some cases, the UE may align USS DCI 0_0 and USS DCI 1_0 to a common size by adding padding bits to the smaller of USS DCI 0_0 and USS DCI 1_0.

[0090] As Figure 5A And as further shown by step 515, the UE may determine a third size (size C) of USS DCI 0_1 and a fourth size (size D) of USS DCI 1_1 (if USS DCI 0_1 or USS DCI 1_1 is configured respectively). In some cases, the UE may determine size C and / or size D at least in part based on size B. For example, the UE may set size C and / or size D to be one bit larger than size B.

[0091] As Figure 5A And as further shown by step 520, the UE may determine a fifth size (size E) of USS DCI 0_2 and a sixth size (size F) of USS DCI 1_2 (if USS DCI 0_2 or USS DCI 1_2 is configured respectively).

[0092] As Figure 5BAnd as shown by step 525, the UE can determine whether a size threshold is met. For example, at least in part based on which DCIs are configured for the UE, the UE can determine the amount of DCI size. In other words, if CSS DCI 0_0 (size A), CSS DCI 1_0 (size A), USS DCI 0_1 (size C), and USS DCI 0_2 (size E) are configured, then there are three DCI sizes. Conversely, if CSS DCI 0_0 (size A), USS DCI 0_0 (size B), USS DCI 0_1 (size C), and USS DCI 0_2 (size E) are configured, then there are four DCI sizes. At least in part based on determining the amount of DCI size, the UE can determine whether there are more than 4 DCI sizes or more than 3 DCI sizes configured with C-RNTI. If neither DCI size threshold is met, the UE can continue without performing additional steps for DCI size alignment. However, if either DCI size threshold is met, the UE can perform additional steps for DCI size alignment, as described herein with respect to Figure 5B and steps 530 - 540.

[0093] As Figure 5B And as further shown by step 530, the UE can perform a first set of size alignment actions. For example, the UE can keep CSS DCI 0_0 and CSS DCI 1_0 (if configured) at size A; the UE can align USS DCI 0_0 and / or USS DCI 1_0 (if configured) to size A (e.g., using padding bits or truncating existing bits); the UE can remove the added bits added in step 515 in USS DCI 0_1 and USS DCI 1_1 (if configured), and the UE can keep the sizes of USS DCI 0_2 and USS DCI 1_2 (if configured).

[0094] As Figure 5B And as further shown by step 535, the UE can perform a second set of alignment actions. For example, the UE can keep CSS DCI 0_0, CSS DCI 1_0, USS DCI 0_0, USS DCI 1_0, USS DCI 0_1, and USS DCI 1_1 (if configured); and can align USS DCI 0_2 with USS DCI 1_2 (if configured) by adding padding bits to one or the other to give USS DCI 0_2 and USS DCI 1_2 a common size (e.g., size E or size F).

[0095] As Figure 5BAnd as further shown by step 540, the UE may perform a third set of alignment actions. For example, the UE may maintain CSSDCI 0_0, CSSDCI 1_0, USSDCI 0_0, USSDCI 1_0, USSDCI 0_2, and USSDCI 1_2 (if configured); and may align USSDCI 0_1 and USSDCI 1_1 (if configured) by adding padding bits to one or the other to make USSDCI 0_1 and USSDCI 1_1 have a common size (e.g., size C or size D). In some cases, the UE may repeat the check of step 525 after each of steps 530, 535, and 540. In other cases, the UE may perform multiple steps 530, 535, and / or 540 before repeating the check of step 525. After performing the size alignment procedure, the UE ensures that the DCI size threshold is met, which enables the UE to successfully monitor the configured DCI.

[0096] As indicated above, Figure 5A and Figure 5B are provided as examples. Other examples may be different from the examples described with respect to Figure 5A and Figure 5B which are different.

[0097] Figures 6A to 6B is a diagram illustrating example 600 of downlink control channel monitoring according to the present disclosure.

[0098] For non-carrier aggregation (non-CA) scenarios, the UE may be configured with a maximum number of BDs or non-overlapping CCEs, which may be referred to as the BD budget or CCE budget, respectively. For example, 3GPP TS 38.213, Tables 10.1-2 and 10.1-3 indicate the maximum number of monitored PDCCH candidates and non-overlapping CCEs per time slot and per serving cell, respectively. The maximum number of BDs and non-overlapping CCEs may be at least partially based on the subcarrier spacing (SCS) configuration of the serving cell. For example, for an SCS configuration of μ = 1, the UE (e.g., UE 120) may be configured with a BD budget of 36 BDs per served cell and a CCE budget of 56 CCEs per served cell. For CA scenarios, the BD budget per SCS the CCE budget per SCS is configured as described in TS 38.213, section 10.1. Similarly, the BD budget and CCE budget per cell or component carrier may be and

[0099] The foregoing BD and CCE budgets are configured assuming a single type of DCI format, such as a legacy DCI format. However, with the introduction of non-legacy DCI formats, in some cases, the foregoing BD and CCE budgets may be exceeded. For example, for monitoring, a UE may have a legacy DCI format for each CC and a non-legacy DCI format for one or more CCs. As an example, as Figure 6A shown, the PDCCH in CC1 schedules data on one or more CCs in a CC set (CC1, CC2, CC3, and CC4). The UE may monitor the legacy DCI format for each CC, resulting in 30 BDs on CC1, 18 BDs on CC2, 10 BDs on CC3, and 32 BDs on CC4. Additionally, the UE may utilize the BD budget counted on CC3 to monitor the non-legacy DCI format, resulting in an additional 26 BDs. Thus, depending on a particular SCS configuration, each CC is associated with fewer than up to 36 BDs, as Figure 6A shown. However, it is possible that the UE will assume that the network node may schedule 26 BDs associated with the non-legacy DCI format on each CC, and the UE may need to monitor these 26 BDs, which may result in each CC other than CC3 having more than up to 36 BDs. Similarly, in Figure 6B , 36 BDs may be used for the legacy DCI format on CC1, CC2, and CC4, and 36 BDs may be used for the non-legacy DCI format on CC3. In such an example, in addition to monitoring the 36 BDs associated with the legacy DCI format, the UE may also need to monitor 36 BDs associated with the non-legacy DCI format on CC1, CC2, and CC4. Thus, the UE may need to monitor more BDs than the configured maximum amount. Some UEs may not have the monitoring capability for these additional BDs.

[0100] As indicated above, Figures 6A to 6B is provided as an example. Other examples may be different from the example described with respect to Figures 6A to 6B .

[0101] Figure 7 is a diagram illustrating Example 700 of the downlink control channel size according to the present disclosure.

[0102] As described above, the UE may be configured to monitor a maximum number of DCI sizes. For example, the UE may monitor 3 DCI sizes for Cell Radio Network Temporary Identifier (C-RNTI), Cell-Specific Radio Network Temporary Identifier (CS-RNTI), and / or MCS-C-RNTI, and 1 additional DCI size for other Radio Network Temporary Identifiers (RNTIs). Additional details of this "3 + 1" DCI size budget and DCI size alignment are described in 3GPP Technical Specification (TS) 38.212, section 7.3.1.0.

[0103] The DCI may be associated with a CIF value, which may correspond to the carrier on which the DCI is being scheduled. The cell on which the DCI is received may be referred to as the "scheduling cell", and the cell being scheduled by the DCI may be referred to as the "scheduled cell". Each CIF value may be associated with a different cell in a one-to-one mapping manner, such as the first CIF value mapped to the first cell, the second CIF value mapped to the second cell, and the third CIF value mapped to the third cell. Each cell and each CIF value may have a separate maximum configured amount of BD, CCE, and / or DCI size. Therefore, each CIF value may be associated with a separate 3 + 1 DCI size budget.

[0104] Other DCI size budgets may be used. For example, as Figure 7 shown, the maximum number of DCI sizes associated with C-RNTI may be 3 DCI sizes. However, when the second type of DCI format as described above is configured in the network, a component carrier may be associated with more DCI sizes than allowed. For example, as Figure 7 shown, component carrier 3 may be associated with 3 DCI sizes for the first type of DCI format and 2 DCI sizes for the second type of DCI format. In another example, each component carrier may be configured to use the second type of DCI format. In this example, the first, third, and fourth component carriers may have 5 DCI sizes, and the second component carrier may have 4 DCI sizes. Therefore, each component carrier may be over budget.

[0105] As indicated above, Figure 7 is provided as an example. Other examples may be different from the examples described with respect to Figure 7 .

[0106] Figures 8A to 8D is a diagram illustrating Example 800 associated with monitoring for PDCCH in a multi-cell scheduling scenario according to the present disclosure. As Figure 8A shown, Example 800 includes communication between network node 110 and UE 120.

[0107] As Figure 8AAs further indicated by reference numeral 810, the UE 120 may receive PDCCH communications from the network entity 110. For example, the UE 120 may receive PDCCH monitoring configurations. In some aspects, the monitoring configuration may be associated with a set of DCI formats for monitoring on a set of component carriers. For example, the UE 120 may receive information in the PDCCH monitoring configuration, such as one or more parameters, based on which the UE 120 may determine the set of component carriers to be monitored, the set of formats to be monitored, or the set of BDs to be performed in combination with monitoring. Additionally or alternatively, the UE 120 may receive information in the PDCCH monitoring configuration associated with identifying split parameters or a hierarchical structure for DCI monitoring.

[0108] In some aspects, the split parameter may include a split ratio α, which is associated with the amount of BDs or (overlapping) CCEs counted on the same cell for which the UE 120 is to monitor DCI with a legacy format or a non-legacy format. For example, on a cell (such as Figure 8B CC3 in

[0109]

[0110] where q 18 is the maximum amount of BDs for non-legacy DCI formats (e.g., DCI formats 0_X and 1_X), α is the split ratio, is the maximum number of monitored PDCCH candidates per time slot for a downlink bandwidth part with an SCS configuration μ, is the total number of monitored PDCCH candidates per time slot for a downlink bandwidth part with an SCS configuration μ, and M BD is another way of representing q 18 In some aspects, the UE 120 may be configured with an absolute value (e.g., the amount of BDs as the value of M BD ), rather than the ratio value α. Similarly, in this case, the maximum amount of BDs for legacy DCI formats is determined at least in part based on a formula of the following form:

[0111]

[0112] where q 16This is the maximum quantity of BDs for legacy DCI formats. In some aspects, for non-legacy DCI formats, PDCCH overbooking may not be configured for UE 120. For example, network node 110 may configure PDCCH monitoring for non-legacy DCI formats such that the quantity of BDs does not exceed the previously configured value. In some aspects, for legacy DCI formats, PDCCH overbooking is configured for UE 120. For example, if the quantity of BDs for the legacy DCI format on a cell will exceed q 16 , then network node 110 may configure UE 120 to forgo monitoring one or more PDCCH candidates or SS sets. In some aspects, UE 120 may determine the maximum quantity of BDs on one or more other cells (e.g., for which non-legacy DCI formats are not monitored) as Therefore, as Figure 8B shown, UE 120 may be configured for 36 BDs on CC1, 36 BDs on CC2, M BD BDs for the non-legacy DCI format on CC3, and (36 - M BD ) BDs for the legacy DCI format, and 36 BDs on CC4.

[0113] In some aspects, UE 120 may send capability signaling. For example, UE 120 may send information indicating the value of the supported splitting ratio and may receive PDCCH monitoring configuration at least partially based on the value indicating the supported splitting ratio. In such a case, network node 110 may provide confirmation of the value of the splitting ratio in the PDCCH monitoring configuration or may indicate the value of the splitting ratio to achieve a decoding complexity lower than that indicated by the UE capability. In other words, in some cases, network node 110 may reduce the decoding complexity to less than the UE capability, such as at least partially based on network conditions or the presence of other UEs on the network.

[0114] In some aspects, UE 120 may determine the splitting ratio of non-overlapping CCEs. For example, for a cell on which BDs and non-overlapping CCEs for non-legacy DCI formats are configured (e.g., Figure 8B CC3 in ), the maximum quantity of BDs for the non-legacy DCI format is 18 and the maximum quantity of non-overlapping CCEs (r ) for the non-legacy DCI format is Similarly, the maximum quantity of BDs for the legacy DCI format is

[0115] In this case, for other cells in the same set (e.g., cells other than the component carriers on which non-legacy DCI formats are configured), the maximum amount of BD is and the maximum amount of non-overlapping CCEs is In some aspects, UE 120 may apply the splitting ratio α to other CCs. For example, for other cells in the same set and for overlapping CCEs, the maximum amount of BD is Similarly, for non-overlapping CCEs, the maximum amount of BD on other cells in the set is and the maximum amount of non-overlapping CCEs is Regarding the example of overlapping CCEs, and as Figure 8C shown, where M BD represents the item the amount of BD on CC1, CC2, and CC4 is 36 – M BD BDs. Thus, if UE 120 reports M B = 10 as its capability, UE 120 will have 26 + 10 = 36 BDs as the maximum on each CC. Similarly, if UE 120 reports M B- = 24 as its capability, UE 120 will have 12 + 24 = 36 BDs as the maximum on each CC. By changing the value of M B signaled to network node 110 in UE capability signaling, UE 120 can control the decoding complexity.

[0116] In some aspects, UE 120 may be configured with a hierarchical structure for BDs. For example, the set of BDs for non-legacy DCI formats may be partitioned into a hierarchical structure of subgroups. In some aspects, the hierarchical structure may be at least partially rule-based. For example, UE 120 may be configured with rules for arranging the subgroups into a hierarchical structure (e.g., arranging the hierarchical structure in the order of the index values of the cells). Additionally or alternatively, the hierarchical structure may be at least partially based on semi-static configuration. For example, UE 120 may receive semi-static signaling from network node 110 with an indicator of the hierarchical structure (or an indicator of the rules according to which it constructs the hierarchical structure).

[0117] Each subgroup of BDs in the hierarchical structure may be used for non-legacy DCI formats for scheduling data on a specific set of CCs, as Figure 8D shown. As Figure 8D shown, at the PDCCH monitoring occasion, there are respectively m BBDs and {m 1 , m 2 , m - 3 , m 4} BDs for legacy DCI formats for component carriers {CC1, CC2, CC3, CC4}. In this case, for non - legacy DCI formats on CC3, m B + m 3 ≤ 36 (e.g., the maximum number of BDs per component carrier configured) and m B BDs are counted. In this case, there is a set of subsets of BDs {m B23 , m B123 , m B1234}, and UE 120 can identify this set of subsets of BDs at least partially based on, for example, rules (such as at least partially based on search space set index, blind decoding index, or CC index, etc., or at least partially based on higher - layer configuration). According to the hierarchical structure of the subsets, a non - legacy DCI format for scheduling data on CC3 can be sent on any one of the m B BDs (subject to the condition m B + m 3 ≤ 36). Additionally, a non - legacy DCI format for scheduling data on CC2 or CC3 can be sent on any one of the m B BDs out of m B23 BDs (subject to the condition m B23 + m 2 ≤ 36). Additionally, a non - legacy DCI format for scheduling data on CC1, CC2, or CC3 can be sent on any one of the m B23 BDs out of m B123 BDs (subject to the condition m B123 + m 1 ≤ 36). Additionally, a non - legacy DCI format for scheduling data on CC1, CC2, CC3, or CC4 can be sent on any one of the m B123 BDs out of m B1234 BDs (subject to the condition m B1234 + m 4 ≤ 36). The foregoing hierarchical structure is an example, and other arrangements of hierarchical structures for arranging BDs for different types of DCI formats are expected.

[0118] As Figure 8AAs further indicated by reference numeral 820, the UE 120 may monitor DCI with a DCI format on a set of component carriers. For example, the UE 120 may monitor DCI with one or more configured DCI formats and may perform one or more BDs according to a split parameter for DCI monitoring or a hierarchical structure for DCI monitoring. In this case, the UE 120 may perform one or more BDs on one or more CCs to receive legacy DCI formats and / or non-legacy DCI formats on one or more CCs.

[0119] As indicated above, Figures 8A to 8D is provided as an example. Other examples may be different from the example Figures 8A to 8D described.

[0120] Figures 9A to 9B is a diagram illustrating Example 900 associated with size alignment in a multi-cell scheduling scenario according to the present disclosure.

[0121] As in Figure 9A and further indicated by reference numeral 910, the UE (e.g., UE 120) may perform legacy DCI size alignment. For example, the UE may perform size alignment on a set of legacy DCI formats, as described in more detail in 3GPP TS 38.212, Rel. 16, version 16.10.0, section 7.3.1.0. In this case, the UE may perform size alignment on the set of legacy DCI formats on each cell such that for any cell, the amount of DCI size with C-RNTI is at most 3 DCI sizes.

[0122] As in Figure 9A and further indicated by reference numeral 920, the UE may perform non-legacy DCI size alignment. For example, the UE may perform size alignment on a set of non-legacy DCI formats on a cell configured to monitor non-legacy DCI formats. In this case, the UE may recalculate the size of the set of DCI formats that includes non-legacy DCI formats and legacy DCI formats. Thus, if the amount of DCI size exceeds a maximum value (e.g., a total of 5 DCI sizes or 4 DCI sizes with C-RNTI), the UE may align the non-legacy DCI format size to a single DCI size, as Figure 9AAs shown. Alternatively, the maximum value can be a total of 4 DCI sizes or 3 DCI sizes with C-RNTI. In some aspects, the UE may consider the following scenario as an error condition: where any other cell in the set is configured such that after legacy DCI size alignment, the total amount of DCI sizes, including non-legacy DCI sizes, exceeds the configured maximum value. In some aspects, the configured maximum value can be N + 1 for the total amount of DCI sizes for a cell, or N for the amount of DCI sizes with C-RNTI for a cell. The amount N can be a configured value that is at least partially based on UE capabilities (e.g., 3, 4, or 5). If such a scenario occurs, the UE may not be able to successfully decode some information due to lack of synchronization with the DCI size alignment of the network node (e.g., network node 110).

[0123] At least partially based on performing non-legacy DCI size alignment, as Figure 9A and as shown by reference numeral 920, CC3 has 4 DCI sizes (3 legacy DCI sizes and 1 non-legacy DCI size) to monitor. Alternatively, at least partially based on performing non-legacy DCI size alignment, CC3 has 3 DCI sizes (e.g., 2 legacy DCI sizes and 1 non-legacy DCI size) to monitor. In some aspects, to align the non-legacy DCI format in size, the UE may add a set of padding bits. For example, when the first payload size (e.g., the first amount of information bits) in DCI format 0_X (before padding) is less than the second payload size of DCI format 1_X for scheduling the same one or more serving cells, the UE may generate a certain amount of zero padding bits for DCI format 0_X to make the first payload size equal to the second payload size. Similarly, if the first payload size is greater than the second payload size, the UE may generate a certain amount of zero padding bits for DCI format 1_X to make the first payload size equal to the second payload size.

[0124] In another example, as Figure 9BAnd as indicated by reference numeral 930, after performing legacy DCI size alignment and non-legacy DCI size alignment, UE 120 may have 3 DCI sizes on CC1, 2 DCI sizes on CC2, 3 + 1 DCI sizes on CC3 (e.g., 3 legacy DCI format sizes and 1 non-legacy format DCI size), and 3 DCI sizes on CC4. Thus, the amount of different DCI sizes with C-RNTI is 4 for CC1, 3 for CC2, and 4 for CC4, which is valid for N = 4, as described above. However, if the UE reports N < 4 (e.g., N = 3) as UE capability, the network node is triggered to configure the DCI format for monitoring on the cell such that the amount of different DCI sizes with C-RNTI does not exceed N. Thus, the network node may reduce the amount of legacy DCI sizes on CC1, CC2, and CC4 to 2, as Figure 9B And as indicated by reference numeral 940.

[0125] As indicated above, Figures 9A to 9B is provided as an example. Other examples may be different from the examples described with respect to Figures 9A to 9B is described.

[0126] Figure 10 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with the present disclosure. Example process 1000 is an example in which a UE (e.g., UE 120) performs operations associated with techniques for monitoring PDCCH in a multi-cell scheduling scenario.

[0127] As Figure 10 shown, in some aspects, process 1000 may include receiving a PDCCH monitoring configuration that is associated with a set of DCI formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with split parameters for DCI monitoring or a hierarchical structure for DCI monitoring (block 1010). For example, a UE (e.g., using Figure 11 the communication manager 140 and / or the receiving component 1102 depicted in Figure 11 ) may receive a PDCCH monitoring configuration as described above. In some aspects, the PDCCH monitoring configuration is associated with a set of DCI formats for monitoring on a set of component carriers. In some aspects, the PDCCH monitoring configuration is associated with split parameters for DCI monitoring or a hierarchical structure for DCI monitoring. In some aspects, the operation of block 1010 may be performed by Figure 11 the receiving component 1102 in

[0128] As Figure 10Further shown, in some aspects, process 1000 may include monitoring DCI having a format from a set of DCI formats on a set of component carriers, the monitoring being at least partially based on a splitting parameter or a hierarchical structure (block 1020). For example, a UE (e.g., using Figure 11 the communication manager 140 and / or the monitoring component 1108 depicted in Figure 11 ) may monitor DCI having a format from a set of DCI formats on a set of component carriers, the monitoring being at least partially based on a splitting parameter or a hierarchical structure, as described above. In some aspects, the operation of block 1020 may be performed by

[0129] the monitoring component 1108 in

[0130] In a first aspect, the splitting parameter is associated with the amount of DCI formats in the set of DCI formats that are monitored on a common component carrier in the set of component carriers.

[0131] In a second aspect, either alone or in combination with the first aspect, process 1000 includes transmitting information indicating the ability to identify a value for the splitting parameter.

[0132] In a third aspect, either alone or in combination with one or more of the first and second aspects, the splitting parameter or the hierarchical structure corresponds to the maximum value of the amount of blind decoding.

[0133] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the splitting parameter applies to component carriers in the set of component carriers having overlapping control channel elements, or applies to component carriers in the set of component carriers having non - overlapping control channel elements.

[0134] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the splitting parameter is a splitting ratio or an absolute value.

[0135] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the hierarchical structure is at least partially based on a configured static rule or a semi - static configuration.

[0136] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the hierarchical structure includes a hierarchical structure for blind decoding that occurs on each component carrier in a set of component carriers.

[0137] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a sub-packet of blind decoding associated with the hierarchical structure is at least partially based on at least one of a search space set index, a blind decoding index, or a higher layer configuration.

[0138] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 1000 includes aligning the size of a DCI having format 0_X or 1_X with a set of other DCI formats.

[0139] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a DCI having format 0_X or 1_X is aligned with a set of padding bits to match the size of another DCI format.

[0140] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, after the DCI size alignment, the amount of the DCI size including a DCI having format 0_X or 1_X is not greater than a threshold that is at least partially based on UE capabilities.

[0141] Although Figure 10 illustrative boxes of process 1000 are shown, in some aspects, process 1000 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 10 Additionally or alternatively, two or more boxes of process 1000 may be performed in parallel.

[0142] Figure 11 is a diagram of an example apparatus 1100 for wireless communication in accordance with the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 140. Communication manager 140 may include one or more of a monitoring component 1108 or a size alignment component 1110, among others.

[0143] In some aspects, apparatus 1100 may be configured to perform herein in connection with Figures 8A to 9BOne or more of the operations described. Additionally or alternatively, apparatus 1100 may be configured to perform one or more of the processes described herein, such as Figure 10 process 1000. In some aspects, Figure 11 the apparatus 1100 and / or one or more components shown may include one or more components of the UE described in connection with Figure 2 . Additionally or alternatively, Figure 11 one or more of the components shown may be implemented within one or more of the components described in connection with Figure 2 . Additionally or alternatively, one or more of the components in a set of components may be at least partially implemented as software stored in a 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 functions or operations of the component.

[0144] The receiving component 1102 may receive a communication from the apparatus 1106, such as a reference signal, control information, data communication, or a combination thereof. The receiving component 1102 may provide the received communication to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communication and may provide the processed signal to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the UE described in connection with Figure 2 .

[0145] The transmitting component 1104 may transmit a communication to the apparatus 1106, such as a reference signal, control information, data communication, or a combination thereof. In some aspects, one or more other components of the apparatus 1100 may generate a communication and may provide the generated communication to the transmitting component 1104 for transmission to the apparatus 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding, etc.) on the generated communication and may transmit the processed signal to the apparatus 1106. In some aspects, the transmitting component 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the UE described in connection with Figure 2 . In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0146] The receiving component 1102 may receive a PDCCH monitoring configuration that is associated with a set of DCI formats for monitoring on a set of component carriers, and that is associated with splitting parameters for DCI monitoring or a hierarchical structure for DCI monitoring. The monitoring component 1108 may monitor DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the splitting parameters or the hierarchical structure. The transmitting component 1104 may transmit information identifying the ability for a value of the splitting parameters. The size alignment component 1110 may align the size of DCI having format 0_X or 1_X with other sets of DCI formats.

[0147] Figure 11 The number and arrangement of the illustrated components are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 11 those illustrated. Additionally, Figure 11 two or more of the illustrated components may be implemented within a single component, or Figure 11 a single illustrated component may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 a set of the illustrated components (one or more components) may perform one or more functions described as being performed by Figure 11 another set of illustrated components.

[0148] Some aspects of the present disclosure are outlined below:

[0149] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a physical downlink control channel (PDCCH) monitoring configuration that is associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers, and that is associated with splitting parameters for DCI monitoring or a hierarchical structure for DCI monitoring; and monitoring DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the splitting parameters or the hierarchical structure.

[0150] Aspect 2: The method according to aspect 1, wherein the splitting parameters are associated with the amount of DCI formats in the set of DCI formats for monitoring on a common component carrier in the set of component carriers.

[0151] Aspect 3: The method according to any one of aspects 1-2, the method further comprising: transmitting information identifying the ability for a value of the splitting parameters.

[0152] Aspect 4: The method according to any one of Aspects 1 - 3, wherein the splitting parameter or the hierarchical structure corresponds to the maximum value of the amount of blind decoding.

[0153] Aspect 5: The method according to any one of Aspects 1 - 4, wherein the splitting parameter is applicable to component carriers having overlapping control channel elements in the set of component carriers, or is applicable to component carriers having non - overlapping control channel elements in the set of component carriers.

[0154] Aspect 6: The method according to any one of Aspects 1 - 5, wherein the splitting parameter is a splitting ratio or an absolute value.

[0155] Aspect 7: The method according to any one of Aspects 1 - 6, wherein the hierarchical structure is at least partially based on a configured static rule or a semi - static configuration.

[0156] Aspect 8: The method according to any one of Aspects 1 - 7, wherein the hierarchical structure includes a hierarchical structure of blind decoding occurring on each component carrier in the set of component carriers.

[0157] Aspect 9: The method according to any one of Aspects 1 - 8, wherein the sub - packets of blind decoding associated with the hierarchical structure are at least partially based on at least one of a search space set index, a blind decoding index, or a higher - layer configuration.

[0158] Aspect 10: The method according to any one of Aspects 1 - 9, the method further comprising: aligning the size of DCI having format 0_X or 1_X with a set of other DCI formats.

[0159] Aspect 11: The method according to Aspect 10, wherein the DCI having the format 0_X or 1_X is aligned with a set of padding bits to match the size of another DCI format.

[0160] Aspect 12: The method according to Aspect 10, wherein after the DCI size alignment, the amount of the DCI size including the DCI having the format 0_X or 1_X is not greater than a threshold based at least in part on UE capabilities.

[0161] Aspect 13: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving a PDCCH monitoring configuration associated with a set of DCI formats for monitoring on a set of component carriers; and monitoring a set of DCIs on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, and wherein the first payload is aligned with the second payload in association with an amount of a size in the PDCCH monitoring configuration exceeding a threshold.

[0162] Aspect 14: The method according to aspect 13, wherein the first DCI format is DCI format 0_3 and the second DCI format is DCI format 1_3.

[0163] Aspect 15: The method according to any one of aspects 13 - 14, the method further comprising: aligning a size of the first DCI format with a size of the second DCI format to align the first payload with the second payload.

[0164] Aspect 16: An apparatus for wireless communication at a device, the apparatus 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 - 15.

[0165] Aspect 17: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 - 15.

[0166] Aspect 18: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 - 15.

[0167] Aspect 19: A non - transitory computer - readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 - 15.

[0168] Aspect 20: A non - transitory computer - readable medium storing an instruction set for wireless communication, the instruction set 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 of aspects 1 - 15.

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

[0170] As used herein, the term "component" is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be broadly construed as "at least partially based on". As used herein, depending on context, "meeting a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, and so forth. As used herein, the phrase referring to "at least one" of a list of items refers to any combination of those items (which includes a single member). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a + b, a + c, b + c, and a + b + c.

[0171] In addition, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more of the items mentioned in connection with the article "the" and may be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries (e.g., related entries, unrelated entries, or a combination of related and unrelated entries) and may be used interchangeably with "one or more". If one merely wishes to refer to a single item, the phrase "only one" or similar terminology will be used. In addition, as used herein, terms such as "has" and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "includes" A may also contain B). In addition, as used herein, the term "or" when used in a series is intended to be inclusive and may be used interchangeably with "and / or", unless expressly stated otherwise (e.g., when used in conjunction with "any one of" or "only one of").

[0172] The various illustrative logical, logical block, modules, circuits, and algorithmic processes described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. The interchangeability of hardware and software has been described generally in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0173] The hardware and data processing apparatus for implementing or performing the various illustrative logics, logic blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed using a general single-chip or multi-chip processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, particular processes and methods may be performed by circuitry dedicated to a given function.

[0174] In one or more aspects, the described functions may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and structural equivalents thereof, or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (e.g., one or more modules of computer program instructions) encoded on a computer storage medium for execution or to control the operation of a data processing apparatus.

[0175] If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can transfer a computer program from one place to another. The storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, any connection may be properly termed a computer-readable medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the media described herein should also be included within the scope of computer-readable media. Additionally, operations of a method or algorithm may be represented as one or any combination of a code and instruction set, residing on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0176] Various modifications to the aspects described in this disclosure may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the widest scope consistent with the disclosure, the principles disclosed herein, and the novel features.

[0177] Additionally, those of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of description of the figures and indicate relative positions corresponding to the orientation of the figures on a correctly oriented page and may not reflect the correct orientation of any device as implemented.

[0178] Certain features that are described in the context of separate aspects in this specification may also be implemented in combination in a single aspect. Conversely, various features that are described in the context of a single aspect may also be implemented separately or in any suitable sub-combination in multiple aspects. Additionally, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excluded from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination.

[0179] Similarly, although the operations are depicted in the figures in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the illustrated operations be performed to achieve the desired result. Additionally, the figures may schematically depict one or more example processes in the form of a flowchart. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, concurrently with, or between any of the illustrated operations. In certain environments, multitasking and parallel processing may be advantageous. Further, the separation of various system components in the aspects described should not be construed as requiring such separation in all aspects, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects are within the scope of the appended claims. In some cases, the acts recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprises: receiving a physical downlink control channel (PDCCH) monitoring configuration, the PDCCH monitoring configuration being associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a splitting parameter for DCI monitoring or a hierarchical structure for DCI monitoring; and monitoring DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the splitting parameter or the hierarchical structure.

2. The method according to claim 1, wherein the splitting parameter is associated with the amount of DCI formats in the set of DCI formats for monitoring on a common component carrier in the set of component carriers.

3. The method according to claim 1, the method further comprises: transmitting information indicating the ability for a value of the splitting parameter.

4. The method according to claim 1, wherein the splitting parameter or the hierarchical structure corresponds to a maximum value of the amount of blind decoding.

5. The method according to claim 1, wherein the splitting parameter applies to component carriers in the set of component carriers having overlapping control channel elements, or applies to component carriers in the set of component carriers having non-overlapping control channel elements.

6. The method according to claim 1, wherein the splitting parameter is a splitting ratio or an absolute value.

7. The method according to claim 1, wherein the hierarchical structure is at least partially based on a configured static rule or a semi-static configuration.

8. The method according to claim 1, wherein the hierarchical structure comprises a hierarchical structure of blind decoding occurring on each component carrier in the set of component carriers.

9. The method according to claim 1, wherein a sub-packet of blind decoding associated with the hierarchical structure is at least partially based on at least one of a search space set index, a blind decoding index, or a higher layer configuration.

10. The method according to claim 1, the method further comprises: aligning the size of DCI having format 0_X or 1_X with other sets of DCI formats.

11. The method according to claim 10, wherein the DCI having the format 0_X or 1_X is aligned with a set of padding bits to match the size of another DCI format.

12. The method according to claim 10, wherein after the DCI size alignment, the amount of the DCI size including the DCI having the format 0_X or 1_X is not greater than a threshold.

13. A user equipment (UE) for wireless communication, the user equipment (UE) comprises: one or more memories; and one or more processors, the one or more processors being coupled to the memory, the one or more processors being configured to: Receive a physical downlink control channel (PDCCH) monitoring configuration, the PDCCH monitoring configuration being associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers, the PDCCH monitoring configuration being associated with a splitting parameter for DCI monitoring or a hierarchical structure for DCI monitoring; and monitor DCI having a format from the set of DCI formats on the set of component carriers, the monitoring being at least partially based on the splitting parameter or the hierarchical structure.

14. The UE according to claim 13, wherein the splitting parameter is associated with the amount of DCI formats for monitoring on a common component carrier in the set of component carriers from the set of DCI formats.

15. The UE according to claim 13, wherein the one or more processors are further configured to: transmit information identifying the ability for a value of the splitting parameter.

16. The UE according to claim 13, wherein the splitting parameter or the hierarchical structure corresponds to a maximum value of the amount of blind decoding.

17. The UE according to claim 13, wherein the splitting parameter applies to component carriers in the set of component carriers having overlapping control channel elements, or applies to component carriers in the set of component carriers having non-overlapping control channel elements.

18. The UE according to claim 13, wherein the splitting parameter is a splitting ratio or an absolute value.

19. The UE according to claim 13, wherein the hierarchical structure is at least partially based on a configured static rule or a semi-static configuration.

20. The UE according to claim 13, wherein the hierarchical structure includes a hierarchical structure of blind decoding that occurs on each component carrier in the set of component carriers.

21. The UE according to claim 13, wherein a sub-packet of blind decoding associated with the hierarchical structure is at least partially based on at least one of a search space set index, a blind decoding index, or a higher layer configuration.

22. The UE according to claim 13, wherein the one or more processors are further configured to: align the size of DCI having format 0_X or 1_X with other sets of DCI formats.

23. The UE according to claim 22, wherein the DCI having the format 0_X or 1_X is aligned with a set of padding bits to match the size of another DCI format.

24. The UE according to claim 22, wherein after the DCI size alignment, the amount of DCI size including the DCI having the format 0_X or 1_X is not greater than a threshold.

25. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a physical downlink control channel (PDCCH) monitoring configuration, the PDCCH monitoring configuration being associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers; and Monitoring a set of downlink control information (DCI) on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, and wherein the first payload is aligned with the second payload in association with an amount of size in the PDCCH monitoring configuration exceeding a threshold.

26. The method according to claim 25, wherein the first DCI format is DCI format 1_3, and the second DCI format is DCI format 0_3.

27. The method according to claim 25, the method further comprises: Aligning a size of the first DCI format with a size of the second DCI format to align the first payload with the second payload.

28. A user equipment (UE) for wireless communication, the user equipment (UE) comprises: One or more memories; and One or more processors coupled to the memory, the one or more processors being configured to: Receive a physical downlink control channel (PDCCH) monitoring configuration associated with a set of downlink control information (DCI) formats for monitoring on a set of component carriers; and Monitoring a set of DCI on the set of component carriers, wherein a first payload of a first DCI format in the set of DCI formats for a set of cells for multi-cell downlink scheduling is aligned with a second payload of a second DCI format in the set of DCI formats for the set of cells, and wherein the first payload is aligned with the second payload in association with an amount of size in the PDCCH monitoring configuration exceeding a threshold.

29. The UE according to claim 28, wherein the first DCI format is DCI format 1_3, and the second DCI format is DCI format 0_3.

30. The UE according to claim 28, wherein the one or more processors are further configured to: Align a size of the first DCI format with a size of the second DCI format to align the first payload with the second payload.

Images