Downlink control channel monitoring capability indication

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit information identifying monitoring capabilities. The UE may monitor, according to the monitoring capability, a set of configured control channel elements (CCEs) for physical downlink control channel (PDCCH) decoding for a scheduled cell of the set of scheduled cells, the scheduled cell of the set of scheduled cells being associated with a set of configured carrier indicator field values, the monitoring is based, at least in part, on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on a per subcarrier spacing (SCS) configuration. The UE may decode the DCI in one or more of the set of CCEs of the monitored configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 63 / 377,644, filed on September 29, 2022, entitled "DOWNLINK CONTROL CHANNEL MONITORING CAPABILITY INDICATION" and U.S. Patent Application No. 18 / 463,987, filed on September 8, 2023, entitled "DOWNLINK CONTROL CHANNEL MONITORING CAPABILITY INDICATION" and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for downlink control channel monitoring. Background Art

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

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

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a user equipment (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 send information identifying monitoring capabilities. The one or more processors may be configured to monitor a set of control channel elements (CCEs) configured for physical downlink control channel (PDCCH) decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on per-carrier indicator field values, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on per-subcarrier spacing (SCS) configuration. The one or more processors may be configured to decode the DCI in one or more CCEs in the set of monitored configured CCEs.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending information identifying a monitoring capability. The method may include monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration. The method may include decoding a DCI in one or more CCEs in the set of monitored configured CCEs.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send information identifying a monitoring capability. The instruction set, when executed by one or more processors of the UE, may cause the UE to monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, wherein the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, wherein the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration. The instruction set, when executed by one or more processors of the UE, may cause the UE to: decode DCI in one or more CCEs in the set of monitored configured CCEs.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending information identifying a monitoring capability. The apparatus may include a component for monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration. The apparatus may include a component for decoding DCI in one or more CCEs in the set of monitored configured CCEs.

[0011] 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, which are coupled to the one or more memories. The one or more processors may be configured to receive an indication of monitoring a PDCCH candidate for a DCI format. The one or more processors may be configured to monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, wherein the scheduled cell in the set of scheduled cells is associated with a set of configured carrier indicator field values, and the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, and the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration. The one or more processors may be configured to decode the DCI in one or more CCEs in the set of monitored configured CCEs.

[0012] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication to monitor a PDCCH candidate for a DCI format. The method may include monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration. The method may include: decoding the DCI in one or more CCEs in the set of monitored configured CCEs.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication of monitoring a PDCCH candidate for a DCI format. The instruction set, when executed by one or more processors of the UE, may cause the UE to monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, wherein the scheduled cell in the set of scheduled cells is associated with a set of configured carrier indicator field values, the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, wherein the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration. The instruction set, when executed by one or more processors of the UE, may cause the UE to: decode the DCI in one or more CCEs in the set of monitored configured CCEs.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving an indication of monitoring a PDCCH candidate for a DCI format. The apparatus may include a component for monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration. The apparatus may include a component for decoding DCI in one or more CCEs in the set of monitored configured CCEs.

[0015] Aspects collectively include methods, apparatus, 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 drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose 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 in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

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

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

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

[0024] FIG. 6A to FIG. 6C is a diagram illustrating an example associated with downlink control channel monitoring according to the present disclosure.

[0025] 7A to 7E is a diagram illustrating an example associated with downlink control channel monitoring according to the present disclosure.

[0026] FIG. 8A to FIG. 8E is a diagram illustrating an example associated with downlink control channel monitoring according to the present disclosure.

[0027] FIG. 9A to FIG. 9B is a diagram illustrating an example associated with downlink control channel monitoring according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example associated with downlink control channel monitoring according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] A user equipment (UE) may be configured to monitor a maximum number of downlink control information (DCI) sizes. For example, the UE may monitor 3 DCI sizes for a cell radio network temporary identifier (C-RNTI), a cell-specific radio network temporary identifier (CS-RNTI), and / or an MCS-C-RNTI, and 1 additional DCI size for other radio network temporary identifiers (RNTIs). This configuration may be referred to as a "3+1" DCI size budget.

[0032] The DCI may be associated with a carrier indicator field (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 a "scheduling cell", and the cell on which the DCI is being scheduled may be referred to as a "scheduled cell". Each CIF value may 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 may have a separate maximum configuration amount BD, CCE and / or DCI size. Therefore, each CIF value may be associated with a separate 3+1 DCI size budget. However, limiting the CIF value to a one-to-one mapping may limit signaling flexibility. It has been proposed to allow CIF values ​​to be mapped to other bases. For example, a CIF value may be mapped to multiple carriers, or multiple CIF values ​​may be mapped to the same carrier. In such a scenario, each CIF value may not be configured with a separate 3+1 DCI size budget.

[0033] Some aspects described herein implement downlink control channel monitoring. For example, some aspects described herein provide configuration of DCI size budgets in cross-carrier scheduling scenarios with non-one-to-one CIF mapping. As an example, the UE may be configured with a BD or CCE (monitoring) budget based on each scheduled cell and a 3+1 DCI size budget, may receive an indication to monitor, and may monitor the scheduled cell, as described in more detail herein. As another example, the UE may be configured with a BD or CCE monitoring budget based on each CIF value. In some aspects, a 3+1 DCI size budget (or another DCI size budget) may be configured on a per-scheduled cell basis or on a per-CIF value basis. In some aspects, the UE may send information identifying the UE capability associated with the BD or CCE monitoring budget. For example, the UE may report a value for a pdcch-BlindDetectionCA parameter that identifies the number of blind decodings per time slot for all scheduled cells (e.g., with all CIF values) configured for a shared common SCS. In this way, improved network flexibility is achieved by enabling the UE to monitor the scheduled cell in the aforementioned scenario.

[0034] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the 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 present invention.

[0035] Several aspects of telecommunication systems 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 blocks, 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0037] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between 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)).

[0038] 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 the 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 decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, 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, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0039] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A 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. Figure 1 In the example shown in , 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 geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0040] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed 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, a 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 device configured to perform one or more functions (such as those described herein in conjunction 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 a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform 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 of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

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

[0042] The 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, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

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

[0044] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

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

[0046] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (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).

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may send information identifying a monitoring capability; monitor a set of configured control channel elements (CCEs) for physical downlink control channel (PDCCH) decoding for a scheduled cell in a set of scheduled cells in accordance with the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-subcarrier spacing (SCS) configuration; and decode the DCI in one or more CCEs in the monitored set of configured CCEs. The communication manager 140 may receive an indication to monitor PDCCH candidates for a DCI format; monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration; and decode the DCI in one or more CCEs in the set of monitored configured CCEs. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0053] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 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 a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0054] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / 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 (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where 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 to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / 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 to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide 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 a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0056] 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 a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0058] 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, and / 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-decoded by the TX MIMO processor 266, where 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 an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIG. 6A to FIG. 12 ).

[0059] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by 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 communication and / 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 antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). FIG. 6A to FIG. 12 ).

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion and / or interpretation), may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0061] In some aspects, UE 120 includes a component for sending information identifying a monitoring capability; a component for monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells based on the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration; and / or a component for decoding DCI in one or more CCEs in the monitored set of configured CCEs. UE 120 may include means for receiving an indication to monitor PDCCH candidates for a DCI format; means for monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration; and means for decoding DCI in one or more CCEs in the set of monitored configured CCEs. Means for UE 120 to perform 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.

[0062] In some aspects, a single processor may perform all of the 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 together. For example, a first set of (one or more) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) of the one or more processors may perform 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. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

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

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0066] An aggregated base station (e.g., an aggregated network node) may 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 decomposed base station (e.g., a decomposed network node) may 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 may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0067] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may 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. A decomposed 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 may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0068] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 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 respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0069] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an 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 a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0070] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is 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 specific implementations, 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0071] 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 one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an 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 an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a 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.

[0074] The non-RT RIC 315 may be configured to include logic functions that implement 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 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and O-eNBs with the near-RT RIC 325.

[0075] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function 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 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4A and Figure 4B 4 is a diagram illustrating an example 400 / 400' of DCI-based scheduling according to the present disclosure. Figure 4A and Figure 4B As shown, network node 110 and UE 120 may communicate with each other (eg, directly or via one or more network nodes).

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

[0079] like Figure 4B As shown, the network node 110 may send a single DCI 405 for scheduling multiple communications for the UE 120 to the 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, the DCI 405 may be cross-carrier scheduling DCI, and may or may not be self-carrier scheduling DCI. In some aspects, the DCI 405 carrying communications in at least two cells may be referred to as combined DCI.

[0080] In example 400', a single DCI 405 schedules communications for a first cell 410 (shown as CC0) that carries the DCI 405, schedules communications for a second cell 415 (shown as CC1) that does not carry the DCI 405, and schedules communications for a third cell 420 (shown as CC2) that does not carry the DCI 405. In some aspects, the DCI 405 may schedule communications with Figure 4B Communications over different numbers of cells are shown (eg, two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0081] The communication scheduled by DCI 405 may include data communication, such as physical downlink shared channel (PDSCH) communication, physical uplink shared channel (PUSCH) communication. For data communication, DCI 405 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs separately in multiple cells. Additionally or alternatively, the communication scheduled by DCI 405 may include a reference signal, such as a channel state information reference signal (CSI-RS) or a 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 MCS, resources for confirmation (ACK) or negative confirmation (NACK) of communications scheduled by DCI 405, and / or resource allocation for scheduled communications to save signaling overhead.

[0082] In the self-scheduling use case, such as Figure 4A As shown, each DCI may have a configured maximum number M of blind decodes (BD) and a configured maximum number C of CCEs. In some cases, M and C may be fixed values ​​and / or the same value. 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 based at least in part on the number of carriers in a carrier aggregation configuration, the number of subcarrier spacings of carriers in a carrier aggregation configuration, or UE capabilities for PDCCH processing, etc. Therefore, when the values ​​of one or more of the aforementioned factors change, the values ​​of M and / or C may change.

[0083] Each DCI may be configured with up to a maximum number N of DCI formats. For example, the first DCI 405 may have up to 4 DCI formats (e.g., selected from DCI formats 0_0, 1_0, 0_1, 1_1 or 0_2, 1_2, 0_3, 1_3 or other DCI formats) and up to 3+1 DCI sizes, as described with respect to Figure 5A and Figure 5B In contrast, the third DCI 405 may enable PDCCH oversubscription (OB) and may have up to 6 DCI formats (e.g., selected from the aforementioned DCI formats) and up to 3+1 DCI sizes. In the case of cross-carrier scheduling, the DCI 405 may be associated with a carrier indicator field (CIF) value n. CI Each CIF value may correspond to a cell that DCI 405 is scheduling. For example, DCI 405 may have n corresponding to CC0. CI - = 0, corresponding to CC1 n CI =1 and n corresponding to CC2CI = 2. In this case, each CIF value may be associated with M BDs and C CCEs.

[0084] As indicated above, Figure 4A and Figure 4B are provided as examples. Other examples can be found in relation to Figure 4A and Figure 4B Different from what is described.

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

[0086] like Figure 5A And as shown in step 505, the UE may determine a first size (size A) of common search space (CSS) DCI 0_0 and CSSDCI 1_0 (if CSSDCI 0_0 or CSSDCI 1_0 is configured, respectively). In some cases, the UE may align the size of CSSDCI 0_0 with that of CSSDCI 1_0. For example, when CSSDCI 0_0 has a larger size than CSSDCI 1_0, the UE may add a set of zero padding bits to CSSDCI 0_0 until the payload size is equal to the payload size of DCI 1_0. On the contrary, if CSSDCI 0_0 has a smaller size than CSSDCI 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, so that the size of DCI 0_0 is equal to the size of DCI 1_0.

[0087] like Figure 5A 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 with a common size by adding padding bits to the smaller of USS DCI 0_0 and USS DCI 1_0.

[0088] like Figure 5AAs 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 based at least in part on size B. For example, the UE may set size C and / or size D to be one bit larger than size B.

[0089] like 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).

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

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

[0092] like Figure 5B And as further shown by step 535, the UE may perform a second set of alignment actions. For example, the UE may maintain CSS DCI 0_0, CSSDCI 1_0, USSDCI 0_0, USSDCI 1_0, USSDCI 0_1, and USSDCI 1_1 (if configured); and may align USSDCI 0_2 with USSDCI 1_2 (if configured) by adding padding bits to one or the other so that USSDCI 0_2 and USSDCI 1_2 have a common size (e.g., size E or size F).

[0093] like Figure 5B And as further shown by step 540, the UE may perform a third set of alignment actions. For example, the UE may maintain CSS DCI 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 with USSDCI 1_1 (if configured) by adding padding bits to one or the other so that 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.

[0094] As indicated above, Figure 5A and Figure 5B are provided as examples. Other examples can be found in relation to Figure 5A and Figure 5B Different from what is described.

[0095] 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 a cell radio network temporary identifier (C-RNTI), a cell-specific radio network temporary identifier (CS-RNTI), and / or an 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 with respect to 3GPP Technical Specification (TS) 38.212, Section 7.3.1.0.

[0096] 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 a "scheduling cell", and the cell on which the DCI is being scheduled may be referred to as a "scheduled cell". Each CIF value may 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 may have a separate maximum configuration amount BD, CCE and / or DCI size. Therefore, each CIF value may be associated with a separate 3+1 DCI size budget. However, limiting the CIF value to a one-to-one mapping may limit signaling flexibility. It has been proposed to allow CIF values ​​to be mapped to other bases. For example, a CIF value may be mapped to multiple carriers, or multiple CIF values ​​may be mapped to the same carrier. In such a scenario, each CIF value may not be configured with a separate 3+1 DCI size budget.

[0097] Some aspects described herein implement downlink control channel monitoring. For example, some aspects described herein provide configuration of DCI size budgets in cross-carrier scheduling scenarios with non-one-to-one CIF mapping. As an example, the UE may be configured with a BD or CCE (monitoring) budget based on each scheduled cell, and a 3+1 DCI size budget, and may monitor the scheduled cells, as described in more detail herein. As another example, the UE may be configured with a BD or CCE monitoring budget based on each CIF value. In some aspects, a 3+1 DCI size budget (or another DCI size budget) may be configured on a per-scheduled cell basis or on a per-CIF value basis. In some aspects, the UE may send information identifying the UE capabilities associated with the BD or CCE monitoring budget. For example, the UE may report a value for a pdcch-BlindDetectionCA parameter that identifies the number of blind decodings per time slot for all scheduled cells (e.g., with all CIF values) configured for a shared common SCS. In this way, improved network flexibility is achieved by enabling the UE to monitor the scheduled cells in the aforementioned scenario.

[0098] In some aspects, for a search space set in which multi-cell (MC) DCI (MC-DCI) is monitored, the UE is configured with an nCI value (e.g., a CIF value). This can be used to identify a set of CCEs for blind decoding of PDCCH. If the UE monitors PDCCH candidates for MC-DCI for scheduling on a serving cell from a set of serving cells, the serving cell used to count the size of the MC-DCI, the PDCCH candidates, and the corresponding number of non-overlapping CCEs may include: a scheduling cell (if the scheduling cell is included in the set of cells and a search space set for PDCCH candidates is provided to the UE only on the scheduling cell); or a serving cell from a set of cells (if a search space set with the same searchSpaceId for MC-DCI is provided on the serving cell and on the scheduling cell). In other words, in some aspects, the value of nCI and the cell in which the DCI size, PDCCH candidates, and CCEs are counted may not need to be the same.

[0099] FIG. 6A to FIG. 6C are diagrams illustrating examples 600, 610, and 620 associated with downlink control channel monitoring according to the present disclosure.

[0100] In some aspects, a UE (e.g., UE 120) may be configured with a BD or CCE budget and / or a DCI size budget. For example, the UE may be statically configured with a BD or CCE budget on a per-scheduled cell basis (e.g., a BD or CCE budget for each scheduled cell) and a 3+1 DCI size budget on a per-scheduled cell basis. Additionally or alternatively, the UE may receive configuration information from a network node (e.g., network node 110) that configures the UE with a BD or CCE budget and / or a DCI size budget.

[0101] like Fig. 6A And as shown in example 600, each scheduled cell is associated with a single CIF value. CI =0 is mapped to the first scheduled cell, the second scheduled cell, and the third scheduled cell. The CIF value may have at most M BDs, at most C CCEs, and may be configured for a PDCCH OB. Additionally or alternatively, the CIF value may be associated with at most 8 DCI formats (e.g., DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X, where X is a format value to be specified, such as 3 or 4) and 3+1 DCI sizes. In this case, the UE may monitor the CIF value n as part of one or more search space (SS) sets or PDCCH candidates. CI=0 associated multi-carrier (MC) DCI (MC-DCI). In some aspects, the UE receives from the network node an RRC information element (IE) identifying a search space (SearchSpace) including a parameter (dci-FormatExt-r16), which is configured on the downlink bandwidth portion of the scheduling cell for one or more USS sets that the UE is to monitor for MC-DCI. Additionally or alternatively, the UE may receive from the network node a cross-carrier scheduling configuration IE (crossCarrierSchedulingConfig) identifying one or more search space sets to be used for cross-carrier scheduling for a specific CIF value.

[0102] like Figure 6B As shown in example 610, each scheduled cell is associated with a single CIF value, and multiple CIF values ​​are provided to be associated with multiple scheduled cells. CI = 0 is mapped to the first scheduled cell, and n CI = 1 is mapped to the second scheduled cell and the third scheduled cell. In this case, the CIF value n CI = 0 is associated with at most M BDs and at most C CCEs and is configured for PDCCH OB, while n CI = 1 is associated with at most M BDs and at most C CCEs and is not configured for a PDCCH OB. Although M and C are described in terms of being a single static value, M and C may have different values, such as different CIF values ​​(e.g., based at least in part on the amount of carrier or subcarrier spacing, PDCCH processing capabilities, etc.). In general, a CIF value may be associated with up to 8 DCI formats, where n CI = 0 is associated with the first set of DCI formats (eg, up to 6 DCI formats, such as 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2), and n CI = 1 is associated with a second set of DCI formats (e.g., at most 2 DCI formats, such as 0_X / 1_X, where X is a format value to be specified, such as 3 or 4). Therefore, the UE may monitor the first one or more search space sets or PDCCH candidates (e.g., with n CI =1) MC-DCI, and may monitor the second one or more search space sets or PDCCH candidates (eg, associated with n CI =0 associated) single carrier (SC) DCI (SC-DCI).

[0103] like Figure 6C And as shown by example 620, in some examples, the set of DCI formats associated with each CIF value may be an overlapping set of DCI formats. CI=0 (which maps to the first scheduled cell CC0) may be associated with a first set of DCI formats (eg, up to 6 DCI formats, such as 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2), and n CI =1 (which is mapped only to the second scheduled cell (CC1) or to the second scheduled cell and the third scheduled cell (CC0)) may be associated with a second set of DCI formats (e.g., up to 6 DCI formats, such as 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X), where at least one DCI format is in both the first set of DCI formats and the second set of DCI formats, as shown in diagram 630. In this case, the UE may monitor a portion of the search space set or a PDCCH candidate for a CIF value corresponding to the SC-DCI (e.g., n CI = 1) associated MC-DCI (e.g., for CIF value n CI =0).

[0104] In some aspects, the UE may perform DCI size alignment to ensure that the 3+1 DCI size budget is not exceeded. For example, the UE may perform as in Figure 5A and Figure 5B 0_2 and 1_2. However, in this case, with the additional DCI formats 0_X / 1_X, the UE may be configured such that DCI 0_X and DCI 0_2 are not configured to be monitored together, and DCI 1_X and DCI 1_2 are not configured to be monitored together. In this case, Size E may be either USSDCI 0_2 or USSDCI 0_X (instead of just DCI 0_2), and Size F may be either USSDCI 1_2 or USSDCI 1_X (instead of just DCI 1_2), as described with respect to Figure 5A and Figure 5B Thus, the UE may reuse the aforementioned DCI size alignment procedure with additional DCI formats by, for example, including restrictions that exclude some DCI formats from being monitored simultaneously with other DCI formats.

[0105] As indicated above, FIG. 6A to FIG. 6C are provided as examples. Other examples can be found in relation to FIG. 6A to FIG. 6C The examples described are different.

[0106] 7A to 7E are diagrams illustrating examples 700, 710, 720, 730, and 740 associated with downlink control channel monitoring according to the present disclosure.

[0107] In some aspects, a UE (e.g., UE 120) may be configured with a BD or CCE budget and / or a DCI size budget. For example, the UE may be statically configured with a BD or CCE budget on a per-scheduled cell basis (e.g., a BD or CCE budget for each scheduled cell) and a 3+1 DCI size budget on a per-scheduled cell basis. Additionally or alternatively, the UE may receive configuration information from a network node (e.g., network node 110) that configures the UE with a BD or CCE budget and / or a DCI size budget.

[0108] like Fig. 7A And as shown in example 700, each scheduled cell may be associated with one or more CIF values. CI = 0 is mapped to the first scheduled cell, and n CI =1 is mapped to the first scheduled cell, the second scheduled cell and the third scheduled cell. The first CIF value n CI = 0 may be associated with up to 6 DCI formats (eg, DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2), and the second CIF value n CI = 1 may be associated with up to 2 DCI formats (e.g., DCI formats 0_X / 1_X, where X is a format value to be specified, such as 3 or 4) and 3+1 DCI sizes, as shown in diagram 705. In this case, the UE may monitor MC-DCI in one or more first search space sets or PDCCH candidates, and may monitor SC-DCI in one or more second search space sets or PDCCH candidates.

[0109] like Figure 7B And as shown in example 710 and diagram 715, the first CIF value and the second CIF value may be mapped to an overlapping set of monitored DCI formats and scheduled cells. CI = 0 may be associated with up to 6 DCI formats (eg, DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2) and may be mapped to the first scheduled cell, and the second CIF value n CI =1 may be associated with up to 6 DCI formats (eg, DCI formats 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X) and may be mapped to the second scheduled cell, or the first scheduled cell, the second scheduled cell, and the third scheduled cell.

[0110] like Figure 7C And as shown in example 720 and diagram 725, the first CIF value and the second CIF value may be mapped to the first scheduled cell and the second scheduled cell, respectively, and the third CIF value (n CI=2) may be mapped to the first scheduled cell, the second scheduled cell, and the third scheduled cell. In this case, the UE may monitor the first one or more search spaces or PDCCH candidates (eg, for n CI = 0 is the first search space and for n CI =1 for the second search space), and the second one or more search spaces or PDCCH candidates (for example, for n CI =2 is the MC-DCI in the third search space). In some aspects, the UE may monitor different amounts of DCI formats for different CIF values. For example, the UE may monitor n CI = 0 Monitor up to 6 DCI formats for n CI = 1 monitors up to 4 DCI formats, and for n CI =2 monitors up to 2 DCI formats. Therefore, and based at least in part on the amount of BD, CCE and DCI size being on a per-scheduled cell basis, as described above, for example, for CC0, the UE may monitor up to M BDs, C CCEs and 3+1 DCI sizes, where for n CI = 0 monitors DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, and for n CI =2 monitor DCI format 0_X / 1_X. Similarly, for CC1, the UE can monitor M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =1 monitors DCI format 0_1 / 1_1 / 0_2 / 1_2, and for n CI =2 monitor DCI format 0_X / 1_X. Similarly, for CC2, the UE can monitor M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =2 monitors DCI format 0_X / 1_X.

[0111] like Fig.7D And as shown in example 730 and diagram 735, the first CIF value may be mapped to the first scheduled cell, the second scheduled cell, and the third scheduled cell, and the third CIF value may be mapped to the second scheduled cell and the third scheduled cell. In this case, the UE may monitor the first one or more search spaces or PDCCH candidates (e.g., for n CI = 0 for the first search space) and the second one or more search spaces or PDCCH candidates (eg, for n CI = 1 is the second search space, and for n CI =2 is the MC-DCI in the third search space). In some aspects, the UE may monitor different amounts of DCI formats for different CIF values. For example, the UE may monitor nCI = 0 Monitor up to 6 DCI formats for n CI = 1 monitors up to 2 DCI formats, and for n CI =2 monitors up to 2 DCI formats. Therefore, and based at least in part on the amount of BD, CCE and DCI size being on a per-scheduled cell basis, as described above, for example, for CC0, the UE may monitor up to M BDs, C CCEs and 3+1 DCI sizes, where for n CI = 0 monitors DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, and for n CI =1 monitors DCI format 0_X / 1_X. Similarly, for CC1 and CC2, the UE may monitor M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =1 monitors DCI format 0_X / 1_X, and for n CI =2 The monitoring DCI format is 0_X / 1_X.

[0112] like Fig. 7E And as shown by example 740 and diagrams 745 and 750, the UE may monitor DCI associated with other CIF value mappings and scheduled cells. For example, with respect to diagram 745, for CC0, for example, for CC0, the UE may monitor up to M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =0 monitors DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X. Similarly, for CC1, the UE may monitor M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =1 monitors DCI format 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X, and for n CI =0 monitors DCI format 0_X / 1_X. Similarly, for CC2, the UE may monitor M BDs, C CCEs, and 3+1 DCI sizes, where for n CI =1 monitors DCI format 0_X / 1_X, and for n CI =2 monitors DCI format 0_1 / 1_1 / 0_2 / 1_2.

[0113] In contrast, regarding the inclusion of additional CIF value n CI =3 and n CI =4, the UE can be in n CI = 0, monitor DCI format 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2, at n CI =3 when monitoring DCI format 0_X / 1_X, and at n CI=4. Similarly, the UE can monitor DCI format 0_X / 1_X at n CI =1 to monitor DCI format 0_0 / 1_1 / 0_2 / 1_2, at n CI =3 when monitoring DCI format 0_X / 1_X, and at n CI =4. Similarly, the UE can monitor DCI format 0_X / 1_X at n CI =2, monitor DCI format 0_0 / 1_1 / 0_2 / 1_2, at n CI =3 when monitoring DCI format 0_X / 1_X, and at n CI =4. In these cases, the UE may monitor multiple MC-DCI search space sets or PDCCH candidates, and / or multiple SC-DCI search space sets or PDCCH candidates. In some aspects, the UE may perform DCI size alignment by evaluating the DCI size across all CIF values ​​that can schedule the same cell. In some aspects, the UE may receive RRC configuration information from a network node and for each scheduled cell, the RRC configuration information identifying the CIF value associated with the scheduled cell and / or one or more DCI formats or search space sets that the UE is to monitor for the CIF value. In this way, the UE is enabled to monitor DCI across multiple CIF values ​​for a specific scheduled cell.

[0114] As indicated above, 7A to 7E are provided as examples. Other examples can be found in relation to 7A to 7E The examples described are different.

[0115] FIG. 8A to FIG. 8E are diagrams illustrating examples 800, 810, 820, 830, and 840 associated with downlink control channel monitoring according to the present disclosure.

[0116] In some aspects, a UE (e.g., UE 120) may be configured with a BD or CCE budget and / or a DCI size budget. For example, the UE may be statically configured with a BD or CCE budget on a per-CIF value basis (e.g., as described above, the BD or CCE budget is for each CIF value, not for each scheduled cell) and a 3+1 DCI size budget on a per-CIF value basis. In other words, for a CIF value n CI = 0, the UE can monitor up to 3+1 DCI sizes, for CIF value n CI=1, the UE may monitor up to 3+1 DCI sizes, etc. Therefore, when performing DCI size alignment, as described above, the UE may align the DCI size to satisfy the maximum DCI size for each CIF value, rather than for each scheduled cell, as described above. In some aspects, each scheduled cell is associated with a single CIF value. In this case, DCI size alignment may occur using the same or similar procedures as when the DCI size budget (or BD or CCE budget) is on a per-scheduled cell basis (because there is one CIF value for each scheduled cell), as described above. Additionally or alternatively, a scheduled cell may be associated with multiple CIF values. In this case, DCI size alignment may occur as described herein. In some aspects, the UE may receive configuration information from a network node (e.g., network node 110) that configures the UE with a BD or CCE budget and / or a DCI size budget.

[0117] like Fig. 8A And as shown in example 800, the scheduled cell may be associated with multiple CIF values. CI = 0 is mapped to the first scheduled cell, and n CI =1 is mapped to the first scheduled cell, the second scheduled cell and the third scheduled cell. In other words, the first scheduled cell is mapped to n CI = 0 and n CI =1 The two are associated. The first CIF value n CI = 0 may be associated with up to 6 DCI formats (eg, DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2), and the second CIF value n CI = 1 may be associated with up to 2 DCI formats (e.g., DCI formats 0_X / 1_X, where X is a format value to be specified, such as 3 or 4) and 3+1 DCI sizes, as shown in diagram 805. In this case, the UE may monitor MC-DCI in one or more first search space sets or PDCCH candidates, and may monitor SC-DCI in one or more second search space sets or PDCCH candidates.

[0118] like Figure 8B And as shown in example 810 and diagram 815, the CIF value may have multiple scheduled cell mappings. For example, the second CIF value may be mapped to the second scheduled cell, or to the first scheduled cell, the second scheduled cell, and the third scheduled cell. The first CIF value n CI = 0 may be associated with up to 6 DCI formats (eg, DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2), and the second CIF value n CI=1 may be associated with up to 6 DCI formats (eg, DCI formats 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X).

[0119] like Figure 8C And as shown in example 820 and diagram 825, the first CIF value may be mapped to the first scheduled cell, the second CIF value may be mapped to the second scheduled cell, and the third CIF value (n CI =2) may be mapped to the first scheduled cell, the second scheduled cell, and the third scheduled cell. In this case, the UE may monitor the SC-DCI in the first one or more search spaces or PDCCH candidates and the MC-DCI in the second one or more search spaces or PDCCH candidates. In some aspects, the UE may monitor different amounts of DCI formats for different CIF values. For example, the UE may monitor n CI = 0 Monitor up to 6 DCI formats for n CI = 1 monitors up to 4 DCI formats, and for n CI = 2 monitors up to 2 DCI formats. Therefore, and based at least in part on the BD, CCE and DCI size, the amount is based on a per CIF value, as described above, for example for n CI = 0, the UE can monitor up to M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 are monitored for CC0. Similarly, for n CI =1, the UE can monitor M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_1 / 1_1 / 0_2 / 1_2 are monitored for CC1. Similarly, for n CI =2, the UE can monitor M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_X / 1_X are monitored for CC0, CC1 and CC2.

[0120] like Fig.8D And as shown in example 830 and diagram 835, the first CIF value may be mapped to the first scheduled cell, the second scheduled cell, and the third scheduled cell, and the third CIF value may be mapped to the second scheduled cell and the third scheduled cell. In this case, the UE may monitor the first one or more search spaces or PDCCH candidates (e.g., for n CI = 0 for the first search space) and the second one or more search spaces or PDCCH candidates (eg, for n CI = 1 is the second search space, and for n CI=2 is the MC-DCI in the third search space). In some aspects, the UE may monitor different amounts of DCI formats for different CIF values. For example, the UE may monitor n CI = 0 Monitor up to 6 DCI formats for n CI = 1 monitors up to 2 DCI formats, and for n CI =2 monitors up to 2 DCI formats. Therefore, and based at least in part on the amount of BD, CCE and DCI size on a per-scheduled cell basis, as described above, for example, for n CI = 0, the UE can monitor up to M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 are monitored for CC0. Similarly, for n CI =1 and n CI =2, the UE may monitor M BDs, C CCEs, and 3+1 DCI sizes, wherein DCI formats 0_X / 1_X are monitored for CC0, CC1, and CC2, and for CC1 and CC2, respectively.

[0121] like Fig. 8E And as shown by example 840 and diagrams 845 and 850, the UE may monitor DCI associated with other CIF value mappings and scheduled cells. For example, with respect to diagram 845, for n CI = 0, the UE can monitor up to M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X are monitored for CC0 or CC0, CC1 and CC2. Similarly, for n CI =1, the UE can monitor M BDs, C CCEs and 3+1 DCI sizes, where DCI formats 0_1 / 1_1 / 0_2 / 1_2 / 0_X / 1_X are monitored for CC1 or CC1 and CC2. Similarly, for n CI =2, the UE can monitor M BDs, C CCEs and 3+1 DCI sizes, among which DCI formats 0_X / 1_X are monitored for CC2.

[0122] In contrast, regarding the inclusion of additional CIF value n CI =3 and n CI =4, the UE may monitor DCI formats 0_0 / 1_0 / 0_1 / 1_1 / 0_2 / 1_2 for CC0 (where n CI =0). Similarly, the UE may monitor DCI formats 0_0 / 1_1 / 0_2 / 1_2 for CC1 (where n CI =1). Similarly, the UE may monitor DCI formats 0_0 / 1_1 / 0_2 / 1_2 for CC2 (where nCI =2). Similarly, the UE may monitor DCI formats 0_X / 1_X (where n CI =3) or monitor DCI format 0_X / 1_X for CC1 and CC2 (where n CI =4). In these cases, the UE may monitor multiple MC-DCI search space sets or PDCCH candidates, and / or multiple SC-DCI search space sets or PDCCH candidates.

[0123] In some aspects, PDCCH OB may be supported for some CIF values. CI =0 for USS. In this case, if the amount of BDs or the amount of non-overlapping CCEs per span or time slot exceeds the capacity of the UE, the UE may determine not to monitor some of the search space sets configured to be monitored in the span or time slot. In other words, the network node may configure the UE to monitor more BDs than the UE is capable of monitoring, and the UE may down-select a lower amount of BDs for monitoring. In some aspects, the UE may send capability signaling indicating the amount of BDs, CCEs, and / or DCI sizes that the UE can monitor for each configured CIF value.

[0124] As indicated above, FIG. 8A to FIG. 8E are provided as examples. Other examples can be found in relation to FIG. 8A to FIG. 8E The examples described are different.

[0125] FIG. 9A to FIG. 9B are diagrams illustrating examples 900 and 910 associated with downlink control channel monitoring according to the present disclosure.

[0126] like Fig.9A And as shown in example 900 and diagram 905, the UE may be configured with four CIF values ​​(n CI =0 to 3). The first CIF value n CI =0 is mapped to the first scheduled cell; the second CIF value n CI =1 is mapped to the first scheduled cell and the second scheduled cell; the third CIF value n CI =2 is mapped to the first scheduled cell, the second scheduled cell and the third scheduled cell; and the fourth CIF value n CI =3 is mapped to the second scheduled cell and the third scheduled cell.

[0127] As shown, when the amount of BD, CCE, and DCI sizes to be monitored by the UE is on a per CIF value basis and the amount of CIF values ​​increases, the amount of BD, CCE, and DCI sizes to be monitored increases accordingly. The UE may send a capability indicator (numMaxCCsPDCCH-monitoring) to the network node to indicate the maximum amount of CIF values ​​that the UE may be configured to monitor for a set of scheduled cells. The maximum amount of scheduled cells may be indicated on a per carrier aggregation (CA) band combination basis (e.g., a maximum amount for each set of CA bands), per band per CA band combination (e.g., a maximum amount for each band within a set of CA bands), or per component carrier per CA band combination (e.g., a maximum amount for each component carrier within a band in a set of CA bands).

[0128] In some aspects, the UE may send a capability indicator for the maximum number of CIF values ​​that the UE may be configured with for the scheduled cells (e.g., the maximum number of CIF values ​​per component carrier) (numMaxNCIPerCCs). In this case, the capability indicator may indicate the maximum number of CIF values ​​on a per CA band combination basis, on a per band per CA band combination basis, or on a per component carrier per CA combination basis. When the UE indicates a value of 3 or higher, the network node may Fig.9A For example, in Fig.9A In the example, CC1 is associated with three CIF values ​​(n CI = 1, 2 and 3). In this case, the network node may configure an association or mapping between CIF values ​​and a set of scheduled cells based at least in part on the maximum amount of CIF values ​​per CC that the UE has indicated.

[0129] In some aspects, the UE may use a capability indicator to indicate the CIF or n with which the UE may be configured. CI For example, when the UE indicates a maximum of 4 CIF values, the network node may Fig.9A Alternatively, the network node may configure the UE with fewer CIF values, such as Fig. 9BAnd as shown by example 910 and diagram 915. In this case, the UE may support MC-DCI with reduced processing complexity relative to example 900. In some aspects, the maximum amount of CIF values ​​may be greater than or equal to the amount of component carriers configured for CA. For example, the network node may configure monitoring of SC-DCI and / or MC-DCI so that the amount of monitored SC-DCI and / or MC-DCI does not exceed the indicated UE capabilities. In some aspects, the configured SC-DCI is configured for different scheduled cells when configured with different CIF values. Similarly, the configured MC-DCI may be configured for different sets of scheduled cells when configured with different CIF values.

[0130] As indicated above, FIG. 9A to FIG. 9B are provided as examples. Other examples can be found in relation to FIG. 9A to FIG. 9B The examples described are different.

[0131] Fig.10 is a diagram illustrating an example 1000 associated with downlink control channel monitoring according to the present disclosure.

[0132] A UE (such as UE 120) may report UE capabilities associated with identifying a BD or CCE monitoring budget on a per SCS basis. For example, the UE may send a report identifying the value of a pdcch-BlindDetectionCA parameter. The value may indicate the number of BDs per time slot for all scheduled cells with a common SCS (and with all CIF values) that the UE is able to monitor and / or decode for all scheduled cells. In this case, the number of BDs may be determined according to the following equation:

[0133]

[0134] where μ represents a single SCS configuration (i.e., the number of BDs is on a per SCS configuration basis), is the number of monitored PDCCH candidates per slot for the downlink bandwidth portion with SCS configuration μ (e.g., as described in more detail with respect to Table 10.1-2 of 3GPP TS 38.213), is the value of the pdcch-BlindDetectionCA parameter, and is the sum of the CIF values ​​of all scheduled cells with SCS configuration μ (e.g., serving cells where no CIF value is configured are tabulated with a value of 1). In some aspects, the per-SCS BD limit is based at least in part on the equation Where N cells Indicates the number of configured cells (e.g. is the number of configured downlink cells for scheduling cells with SCS configuration μ but no CIF configuration and the number of CIF values ​​for scheduling cells with SCS configuration μ and with CIF configuration).

[0135] The network node and the UE may determine the number of BDs and select a BD budget that is less than or equal to the number of BDs to ensure that the UE capability is not exceeded. In other words, the UE and the network node may determine the maximum number of BDs per time slot with the SCS configuration μ as Similarly, using an equation similar to the above equation (e.g., where CCE parameters are indicated instead of BD parameters), the UE may indicate and the UE and the network node may determine the CCE budget on a per SCS configuration basis. For example, instead of the parameter for BD budget The CCE budget may be based at least in part on the parameter (For example, as described in more detail in Table 10.1-3 of 3GPP TS 38.213). Fig.10 As shown in, in one example (eg, where pdcch-BlindDetectionCA=4), for The value of may be for a scheduling CC (eg, a scheduling cell), a CIF value, a scheduled CC (eg, a scheduled cell), and for In some aspects, when multiple cells are derived to CIF values, a per-SCS BD limit based on the pdcch-BlindDetectCA parameter reported by the UE may be applied.

[0136] As indicated above, Fig.10 are provided as examples. Other examples can be found in relation to Fig.10 The examples described are different.

[0137] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a UE, according to the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with downlink control channel monitoring.

[0138] like Fig.11 As shown, in some aspects, process 1100 may include sending information identifying monitoring capabilities (block 1110). For example, a UE (e.g., using Fig.12 The depicted communications manager 140 and / or transmitting component 1204) may transmit information identifying monitoring capabilities, as described above. In some aspects, a UE may receive an indication to monitor a PDCCH candidate for a DCI format.

[0139] like Fig.11As further shown in FIG. 1 , in some aspects, process 1100 may include monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to a monitoring capability (block 1120). For example, a UE (e.g., using Fig.12 The depicted communication manager 140 and / or monitoring component 1208) may monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells based on the monitoring capability, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, wherein the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is at least partially based on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, wherein the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration, as described above. In some aspects, the UE may monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells based on the indication, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, wherein the set of configured CCEs is based on a per-carrier indicator field value, and the monitoring is at least partially based on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, wherein the CCE budget or the PDCCH blind decoding budget is based on a per-SCS configuration.

[0140] like Fig.11 As further shown, in some aspects, process 1100 may include decoding DCI in one or more CCEs in the set of monitored configured CCEs (block 1130). For example, a UE (e.g., using Fig.12 The communications manager 140 and / or receiving component 1210 depicted in FIG. 1 may decode the DCI in one or more CCEs of the monitored set of configured CCEs, as described above.

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

[0142] In a first aspect, the monitoring capability is a PDCCH monitoring capability, which indicates the PDCCH blind decoding budget or the CCE budget based on the per SCS configuration for the scheduled cell.

[0143] In a second aspect, either alone or in combination with the first aspect, the maximum number of PDCCH candidates monitored for PDCCH decoding is based at least in part on at least one of: the PDCCH blind decoding budget for each time slot of the downlink bandwidth portion, the CCE budget for each time slot of the downlink bandwidth portion, or the SCS configuration for the scheduling cell.

[0144] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes sending information identifying a value for a blind detection parameter, wherein at least in part based on the sending of the information identifying the value for the blind detection parameter, the CCE budget or the PDCCH blind decoding budget is based on the per SCS configuration.

[0145] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PDCCH blind decoding budget per time slot is based at least in part on the number of carrier indicator field values ​​for a set of scheduled cells having a common subcarrier spacing configuration.

[0146] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the CCE budget per time slot is based at least in part on a carrier indicator field value of a set of scheduled cells having a common subcarrier spacing.

[0147] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on the per-carrier indicator field value.

[0148] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the scheduled cell is associated with a single carrier indicator field value.

[0149] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the scheduled cell is associated with a plurality of carrier indicator field values.

[0150] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, at least one search space set associated with the DCI is based at least in part on a value of a carrier indicator field.

[0151] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1100 includes receiving signaling conveying an information element, wherein the information element includes information associated with a format of the DCI.

[0152] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1100 includes receiving signaling conveying an information element, wherein the information element includes information associated with a cross-carrier scheduling configuration.

[0153] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 1100 includes abandoning monitoring one or more search space sets based at least in part on a configuration of the UE.

[0154] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 1100 includes sending a capability indication identifying a set of component carriers for monitoring, and wherein monitoring the configured set of CCEs includes monitoring the DCI based at least in part on a communication configuration according to the capability indication.

[0155] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0156] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include one or more of a monitoring component 1208 or a decoding component 1210, etc.

[0157] In some aspects, the apparatus 1200 may be configured to perform FIG. 6A to FIG. 10 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part 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 can be executed by a controller or processor to perform the function or operation of the component.

[0158] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to the one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0159] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0160] The monitoring component 1208 may monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells, wherein the set of configured CCEs is based on a per-scheduled cell basis. The decoding component 1210 may decode the DCI in one or more CCEs in the set of monitored configured CCEs. The receiving component 1202 may receive signaling conveying an information element, wherein the information element includes information associated with a search space set and a format of the DCI. The receiving component 1202 may receive signaling conveying an information element, wherein the information element includes information associated with a format of the DCI or a list of search space set IDs, and wherein the UE monitors the DCI using a cross-carrier scheduling configuration.

[0161] The monitoring component 1208 may monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells, wherein the set of configured CCEs is based on a per-carrier indicator field value. The decoding component 1210 may decode the DCI in one or more CCEs in the set of monitored configured CCEs. The receiving component 1202 may receive signaling of an information element, wherein the information element includes information associated with a format of the DCI. The receiving component 1202 may receive signaling of an information element, wherein the information element includes information associated with a cross-carrier scheduling configuration. The sending component 1204 may send a capability indication identifying a set of component carriers for monitoring.

[0162] The sending component 1204 may send information identifying the monitoring capability. The monitoring component 1208 may monitor a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, the scheduled cells in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration. The decoding component 1210 may decode the DCI in one or more CCEs in the set of monitored configured CCEs.

[0163] The transmitting component 1204 may transmit information identifying a value for a blind detection parameter, wherein based at least in part on the transmitting of the information identifying a value for the blind detection parameter, a CCE budget or a PDCCH blind decoding budget is configured on a per SCS basis. The receiving component 1202 may receive signaling conveying an information element, wherein the information element includes information associated with a format of the DCI. The receiving component 1202 may receive signaling conveying an information element, wherein the information element includes information associated with a cross-carrier scheduling configuration. The transmitting component 1204 may transmit a capability indication identifying a set of component carriers for monitoring.

[0164] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly of (one or more) components shown may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

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

[0166] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: monitoring a set of configured control channel elements (CCEs) for physical downlink control channel (PDCCH) decoding for a scheduled cell in a set of scheduled cells, wherein the set of configured CCEs is based on each scheduled cell, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values ​​for a carrier indicator field, wherein the monitoring is at least partially based on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget; and decoding DCI in one or more CCEs in the monitored set of configured CCEs.

[0167] Aspect 2: The method according to aspect 1, wherein the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on each scheduled cell.

[0168] Aspect 3: The method according to any one of aspects 1 to 2, wherein the scheduled cell is associated with a single carrier indicator field value.

[0169] Aspect 4: The method according to any one of aspects 1 to 3, wherein the scheduled cell is associated with multiple carrier indicator field values.

[0170] Aspect 5: The method according to any one of aspects 1 to 4, wherein at least one search space set associated with the DCI is based at least in part on the value of the carrier indicator field.

[0171] Aspect 6: The method according to any one of aspects 1 to 5 further comprises: receiving signaling conveying an information element, wherein the information element comprises information associated with a set of search spaces and a format of the DCI.

[0172] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: receiving signaling for conveying an information element, wherein the information element includes information associated with the format of the DCI or a list of search space set IDs, and wherein the UE monitors the DCI using a cross-carrier scheduling configuration.

[0173] Aspect 8: The method according to any one of aspects 1 to 7, wherein the UE is configured to give up monitoring one or more search space sets based at least in part on the configuration of the UE.

[0174] Aspect 9: A method of wireless communication performed by a user equipment (UE), comprising: monitoring a set of configured control channel elements (CCEs) for physical downlink control channel (PDCCH) decoding for a scheduled cell in a set of scheduled cells, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, wherein the set of configured CCEs is based on a per-carrier indicator field value, wherein the monitoring is at least partially based on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget; and decoding DCI in one or more CCEs in the monitored set of configured CCEs.

[0175] Aspect 10: The method according to aspect 9, wherein the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on each carrier indicator field value.

[0176] Aspect 11: The method according to any one of aspects 9 to 10, wherein the scheduled cell is associated with a single carrier indicator field value.

[0177] Aspect 12: The method according to any one of aspects 9 to 11, wherein the scheduled cell is associated with multiple carrier indicator field values.

[0178] Aspect 13: The method of any one of Aspects 9 to 12, wherein at least one search space set associated with the DCI is based at least in part on a value of the carrier indicator field.

[0179] Aspect 14: The method according to any one of aspects 9 to 13, further comprising: receiving signaling conveying an information element, wherein the information element includes information associated with a format of the DCI.

[0180] Aspect 15: The method according to any one of aspects 9 to 14, further comprising: receiving signaling conveying an information element, wherein the information element comprises information associated with a cross-carrier scheduling configuration.

[0181] Aspect 16: The method according to any one of aspects 9 to 15, wherein the UE is configured to give up monitoring one or more search space sets based at least in part on the configuration of the UE.

[0182] Aspect 17: The method according to any one of Aspects 9 to 16 further includes: sending a capability indication identifying a set of component carriers for monitoring; and wherein monitoring the set of configured CCEs includes: monitoring the DCI based at least in part on a communication configuration according to the capability indication.

[0183] Aspect 18: A method for wireless communication performed by a user equipment (UE), the method comprising: sending information identifying monitoring capability; monitoring a set of configured control channel elements (CCEs) for physical downlink control channel (PDCCH) decoding for a scheduled cell in a set of scheduled cells according to the monitoring capability, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, the set of configured CCEs being based on per-carrier indicator field values, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on per-subcarrier spacing (SCS) configuration; and decoding the DCI in one or more CCEs in the monitored set of configured CCEs.

[0184] Aspect 19: The method according to Aspect 18, wherein the monitoring capability is a PDCCH monitoring capability, and the PDCCH monitoring capability indicates the PDCCH blind decoding budget or the CCE budget based on the per SCS configuration for the scheduling cell.

[0185] Aspect 20: A method according to any one of Aspects 18 to 19, wherein the maximum number of PDCCH candidates monitored for PDCCH decoding is based at least in part on at least one of: the PDCCH blind decoding budget for each time slot of the downlink bandwidth portion, the CCE budget for each time slot of the downlink bandwidth portion, or the SCS configuration for the scheduling cell.

[0186] Aspect 21: According to a method described in any one of Aspects 18 to 20, the method includes: sending information identifying a value for a blind detection parameter, wherein at least partially based on the sending of the information identifying the value for the blind detection parameter, the CCE budget or the PDCCH blind decoding budget is based on the per SCS configuration.

[0187] Aspect 22: A method according to any one of aspects 18 to 21, wherein the PDCCH blind decoding budget per time slot is based at least in part on the number of carrier indicator field values ​​of a set of scheduled cells with a common subcarrier spacing configuration.

[0188] Aspect 23: The method according to any one of aspects 18 to 22, wherein the CCE budget per time slot is based at least in part on a carrier indicator field value of a set of scheduled cells with a common subcarrier spacing.

[0189] Aspect 24: The method according to any one of aspects 18 to 23, wherein the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on each carrier indicator field value.

[0190] Aspect 25: The method according to any one of aspects 18 to 24, wherein the scheduled cell is associated with a single carrier indicator field value.

[0191] Aspect 26: The method according to any one of aspects 18 to 25, wherein the scheduled cell is associated with multiple carrier indicator field values.

[0192] Aspect 27: The method according to any one of aspects 18 to 26, wherein at least one search space set associated with the DCI is based at least in part on a value of a carrier indicator field.

[0193] Aspect 28: The method according to any one of aspects 18 to 27, the method further comprising: receiving signaling conveying an information element, wherein the information element comprises information associated with a format of the DCI.

[0194] Aspect 29: The method according to any one of aspects 18 to 28, the method further comprising: receiving signaling conveying an information element, wherein the information element comprises information associated with a cross-carrier scheduling configuration.

[0195] Aspect 30: The method according to any one of aspects 18 to 29, comprising abandoning monitoring one or more search space sets based at least in part on the configuration of the UE.

[0196] Aspect 31: According to any one of Aspects 18 to 30, the method further includes: sending a capability indication identifying a set of component carriers for monitoring; and wherein monitoring the set of configured CCEs includes: monitoring the DCI based at least in part on a communication configuration according to the capability indication.

[0197] Aspect 32: A method of wireless communication performed by a UE, the method comprising: receiving an indication to monitor a PDCCH candidate for a DCI format; monitoring a set of configured CCEs for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, wherein the scheduled cells in the set of scheduled cells are associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per-carrier indicator field value, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a DCI size budget, the CCE budget or the PDCCH blind decoding budget being based on a per-SCS configuration; and decoding the DCI in one or more CCEs in the monitored set of configured CCEs.

[0198] Aspect 33: An apparatus for performing wireless communications 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 one or more of the methods described in Aspects 1 to 32.

[0199] Aspect 34: 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 execute the method according to one or more of aspects 1 to 32.

[0200] Aspect 35: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 32.

[0201] Aspect 36: 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 to 32.

[0202] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 32.

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

[0204] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0206] As used herein, "satisfying 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, etc., depending on the context.

[0207] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it 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, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0208] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to: receiving an indication to monitor for a physical downlink control channel (PDCCH) candidate in a downlink control information (DCI) format; monitoring a set of configured control channel elements (CCEs) for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per carrier indicator field value basis, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on a per subcarrier spacing (SCS) configuration basis; and The DCI is decoded in one or more CCEs in the monitored set of configured CCEs.

2. The UE according to claim 1, wherein the monitoring is associated with a PDCCH monitoring capability, and the PDCCH monitoring capability indicates the PDCCH blind decoding budget or the CCE budget based on the per SCS configuration for a scheduled cell.

3. The UE of claim 1 , wherein the maximum number of PDCCH candidates monitored for PDCCH decoding is based at least in part on at least one of: the PDCCH blind decoding budget for each time slot of the downlink bandwidth part, the CCE budget per timeslot for the downlink bandwidth portion, or SCS configuration for scheduling cells.

4. The UE of claim 1 , wherein the one or more processors are configured to: Sending information identifying a value for a blind detection parameter, wherein the CCE budget or the PDCCH blind decoding budget is based on the per-SCS configuration, at least in part based on the sending of the information identifying the value for the blind detection parameter.

5. The UE of claim 1, wherein the PDCCH blind decoding budget per time slot is based at least in part on a number of carrier indicator field values ​​for a set of scheduled cells having a common subcarrier spacing configuration.

6. The UE of claim 1, wherein the CCE budget per time slot is based at least in part on a carrier indicator field value of a set of scheduled cells having a common subcarrier spacing.

7. The UE of claim 1, wherein the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on the per-carrier indicator field value.

8. The UE of claim 1, wherein the scheduled cell is associated with a single carrier indicator field value.

9. The UE of claim 1, wherein the scheduled cell is associated with a plurality of carrier indicator field values.

10. The UE of claim 1, wherein at least one search space set associated with the DCI is based at least in part on a value of a carrier indicator field.

11. The UE of claim 1 , wherein the one or more processors are further configured to: Signaling conveying an information element is received, wherein the information element includes information associated with a format of the DCI.

12. The UE of claim 1, wherein the one or more processors are further configured to: Signaling conveying an information element is received, wherein the information element includes information associated with a cross-carrier scheduling configuration.

13. The UE of claim 1, wherein the UE is configured to abandon monitoring one or more search space sets based at least in part on a configuration of the UE.

14. The UE of claim 1, wherein the one or more processors are further configured to: sending a capability indication identifying a set of component carriers for monitoring; and Wherein, in order to monitor the configured set of CCEs, the one or more processors are configured to: The DCI is monitored based at least in part on a communications configuration in accordance with the capability indication.

15. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication to monitor for a physical downlink control channel (PDCCH) candidate in a downlink control information (DCI) format; monitoring a set of configured control channel elements (CCEs) for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per carrier indicator field value basis, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on a per subcarrier spacing (SCS) configuration basis; and The DCI is decoded in one or more CCEs in the monitored set of configured CCEs.

16. The method of claim 15, wherein the monitoring is associated with a PDCCH monitoring capability, and the PDCCH monitoring capability indicates the PDCCH blind decoding budget or the CCE budget based on the per SCS configuration for a scheduled cell.

17. The method of claim 15, wherein the maximum number of PDCCH candidates monitored for PDCCH decoding is based at least in part on at least one of: the PDCCH blind decoding budget for each time slot of the downlink bandwidth part, the CCE budget per timeslot for the downlink bandwidth portion, or SCS configuration for scheduling cells.

18. The method according to claim 15, comprising: Sending information identifying a value for a blind detection parameter, wherein the CCE budget or the PDCCH blind decoding budget is based on the per-SCS configuration, at least in part based on the sending of the information identifying the value for the blind detection parameter.

19. The method of claim 15, wherein the PDCCH blind decoding budget per time slot is based at least in part on a number of carrier indicator field values ​​for a set of scheduled cells having a common subcarrier spacing configuration.

20. The method of claim 15, wherein the CCE budget per time slot is based at least in part on a carrier indicator field value for a set of scheduled cells having a common subcarrier spacing.

21. The method of claim 15, wherein the DCI is associated with a configured DCI size budget, wherein the configured DCI size budget is based on the per-carrier indicator field value.

22. The method of claim 15, wherein the scheduled cell is associated with a single carrier indicator field value.

23. The method of claim 15, wherein the scheduled cell is associated with a plurality of carrier indicator field values.

24. The method of claim 15, wherein at least one search space set associated with the DCI is based at least in part on a value of a carrier indicator field.

25. The method according to claim 15, further comprising: Signaling conveying an information element is received, wherein the information element includes information associated with a format of the DCI.

26. The method according to claim 15, further comprising: Signaling conveying an information element is received, wherein the information element includes information associated with a cross-carrier scheduling configuration.

27. The method of claim 15, comprising abstaining from monitoring one or more search space sets based at least in part on a configuration of the UE.

28. The method of claim 15, further comprising: sending a capability indication identifying a set of component carriers for monitoring; and The set of CCEs for monitoring the configuration includes: The DCI is monitored based at least in part on a communications configuration in accordance with the capability indication.

29. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receiving an indication to monitor for a physical downlink control channel (PDCCH) candidate in a downlink control information (DCI) format; monitoring a set of configured control channel elements (CCEs) for PDCCH decoding for a scheduled cell in a set of scheduled cells according to the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being based on a per carrier indicator field value basis, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being based on a per subcarrier spacing (SCS) configuration basis; and The DCI is decoded in one or more CCEs in the monitored set of configured CCEs.

30. An apparatus for wireless communication, comprising: means for receiving an indication to monitor for a physical downlink control channel (PDCCH) candidate in a downlink control information (DCI) format; means for monitoring a set of configured control channel elements (CCEs) for PDCCH decoding for a scheduled cell in a set of scheduled cells in accordance with the indication, the scheduled cell in the set of scheduled cells being associated with a set of configured carrier indicator field values, the set of configured CCEs being on a per carrier indicator field value basis, the monitoring being based at least in part on at least one of a CCE budget, a PDCCH blind decoding budget, or a downlink control information (DCI) size budget, the CCE budget or the PDCCH blind decoding budget being on a per subcarrier spacing (SCS) configuration basis; and Means for decoding DCI in one or more CCEs of the monitored set of configured CCEs.

Images