User equipment specific search space and common search space assignment for control channel monitoring based on multiple slots

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive, from a network entity, a search space configuration indicating a first configuration for a UE-specific search space (USS) associated with a first slot group size, and a second configuration for a common search space (CSS) associated with a second slot group size. The UE may receive communications from the network entity via a downlink control channel based at least in part on monitoring the downlink control channel according to the search space configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 662,051, filed on May 4, 2022, entitled "USER EQUIPMENT SPECIFIC SEARCHSPACE AND COMMON SEARCH SPACE ASSIGNMENT FOR MULTIPLE SLOT BASED CONTROLCHANNEL MONITORING," which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for user equipment (UE) specific search space (USS) and common search space (CSS) assignments for multiple time slot (multi-slot) based 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 base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[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 integrate with other open standards 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, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. 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 UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive a search space configuration from a network entity, the search space configuration indicating a first configuration for a UE-specific search space (USS) associated with a first time slot group size, and a second configuration for a common search space (CSS) associated with a second time slot group size. The one or more processors may be configured to: receive a communication from the network entity via the downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS. The one or more processors may be configured to send a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with a first slot group size, and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for a USS associated with a first slot group size and a second configuration for a CSS associated with a second slot group size. The method may include receiving a communication from the network entity via a downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS. The method may include sending a search space configuration for the UE, the search space configuration indicating a first configuration for the USS associated with the first slot group size and a second configuration for the CSS associated with the second slot group size, wherein the search space configuration is based at least in part on the capability report.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. When executed by one or more processors of the UE, the instruction set may cause the UE to receive a search space configuration from a network entity, the search space configuration indicating a first configuration for a USS associated with a first time slot group size and a second configuration for a CSS associated with a second time slot group size. When executed by one or more processors of the UE, the instruction set may cause the UE to receive communications from the network entity via a downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. When executed by one or more processors of the network entity, the instruction set may cause the network entity to receive a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS. When executed by one or more processors of the network entity, the instruction set may cause the network entity to send a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with a first slot group size and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for USSs associated with a first slot group size and a second configuration for CSSs associated with a second slot group size. The apparatus may include: means for receiving a communication from the network entity via a downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS. The apparatus may include: means for sending a search space configuration for the UE, the search space configuration indicating a first configuration for the USS associated with the first slot group size and a second configuration for the CSS associated with the second slot group size, wherein the search space configuration is based at least in part on the capability report.

[0015] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively 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 the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection 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 accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the 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 fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate 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 base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example resource structure for wireless communication according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of multi-slot monitoring according to the present disclosure.

[0023] FIG. 5A to FIG. 5G is a diagram of an example associated with UE-specific search space (USS) and common search space (CSS) assignments for multi-slot based control channel monitoring according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0026] Figure 8 is an illustration of an example apparatus for wireless communications.

[0027] Fig. 9 is an illustration of an example apparatus for wireless communications. DETAILED DESCRIPTION

[0028] 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 protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present 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 implemented using other structures, functions, or structures and functions 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 claims.

[0029] 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 can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] 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 post-5G RATs (e.g., 6G).

[0031] 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, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) 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, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0032] The base station 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 base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0033] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a clustered 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 entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (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 entity" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some aspects, the term "base station" or "network entity" may refer to a plurality of 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 repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" 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 entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0034] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0035] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 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 FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0036] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 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 base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0038] UE 120 may be distributed throughout 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, and / or any other suitable device configured to communicate via a wireless medium.

[0039] 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, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, 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.

[0040] 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.

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. 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 base station 110.

[0042] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which 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 portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] 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, and therefore 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.

[0044] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave" or the like, if used herein, can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a search space configuration from a network entity indicating a first configuration for a UE-specific search space (USS) associated with a first slot group size and a second configuration for a common search space (CSS) associated with a second slot group size; and receive communications from the network entity via the downlink control channel based at least in part on monitoring a downlink control channel in accordance with the search space configuration. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0046] In some aspects, a network entity (e.g., Figure 1 and Figure 2 As shown, the base station 110 as an example) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS; and send a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with a first slot group size, and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0048] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0049] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the 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 (CQI) received from the UE 120. The base station 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 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., pre-coding) 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 further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 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.

[0051] 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 base station 110 via the communication unit 294.

[0052] 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.

[0053] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a 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 transmitted to the base station 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, reference FIG. 5A to FIG. 5G and Figures 6 to 9 ).

[0054] At the base station 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 of the modem 232 shown as DEMOD), 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 base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 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 200 to FIG. 1 ). FIG. 5A to FIG. 5G and Figures 6 to 9 ).

[0055] As described in more detail elsewhere herein, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with USS and CSS assignment for control channel monitoring based on multiple time slots. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 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, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Figure 6 The process of 600 Figure 7 The process 700 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.

[0056] In some aspects, the UE 120 includes: a means for receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for a USS associated with a first slot group size and a second configuration for a CSS associated with a second slot group size; and / or a means for receiving a communication from the network entity via a downlink control channel based at least in part on monitoring the downlink control channel according to the search space configuration. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0057] In some aspects, a network entity (e.g., Figure 1 and Figure 2As shown, the base station 110 as an example includes: a component for receiving a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS; and / or a component for sending a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with a first slot group size and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report. In some aspects, the component for a network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0058] 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.

[0059] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0060] 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 BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station.

[0061] A clustered base station 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 may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as a CU, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or more other RAN 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.

[0062] 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. Various 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.

[0063] For example, a decomposed base station architecture may include a CU that may communicate directly with a core network via a backhaul link, or indirectly with a core network through one or more decomposed control units (such as a near-RT RIC via an E2 link, or a non-RT RIC associated with a service management and orchestration (SMO) framework, or both). The CU may communicate with one or more DUs via corresponding midhaul links, such as through an F1 interface. Each of the DUs may communicate with one or more RUs via corresponding fronthaul links. Each of the RUs may communicate with one or more UEs 120 via corresponding radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs simultaneously.

[0064] Each unit in the unit (including CU, DU, RU, and near-RT RIC, non-RT RIC, and SMO framework) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit 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 unit in the unit 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, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0065] In some aspects, the CU may be in charge of one or more higher-layer control functions. Such control functions may include RRC functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each DU may correspond to a logical unit, which includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, the DU may host one or more of the radio link control (RLC) layer, the MAC layer, and one or more high physical (PHY) layers at least in part according to functional divisions such as those defined by 3GPP. Each RU may implement lower-layer functionality. In some deployments, the RU controlled by the DU may correspond to a logical node, which hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based at least in part on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower-layer functional splitting). In such an architecture, each RU may be operated to handle air (OTA) communications with one or more UEs 120.

[0066] Figure 3 300 is a diagram illustrating an example resource structure 300 for wireless communication according to the present disclosure. Resource structure 300 shows examples of various resource groups described herein. As shown, resource structure 300 may include subframe 305. Subframe 305 may include multiple time slots 310. Although resource structure 300 is shown as including 2 time slots per subframe, a different number of time slots (e.g., 4 time slots, 8 time slots, 16 time slots, 32 time slots, or another number of time slots) may be included in a subframe. In some aspects, in addition to subframes and / or time slots, different types of transmit time intervals (TTIs) may be used. Time slots 310 may include multiple symbols 315, such as 14 symbols per time slot.

[0067] The potential control region of the time slot 310 may be referred to as a control resource set (CORESET) 320, and may be configured to support efficient use of resources, such as by flexibly configuring or reconfiguring the resources of the CORESET 320 for one or more physical downlink control channels (PDCCHs) and / or one or more physical downlink shared channels (PDSCHs). In some aspects, the CORESET 320 may occupy the first symbol 315 of the time slot 310, the first two symbols 315 of the time slot 310, or the first three symbols 315 of the time slot 310. Thus, the CORESET 320 may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols 315 in the time domain. In 5G, the number of resources included in the CORESET 320 may be flexibly configured (such as by using radio resource control (RRC) signaling to indicate the frequency domain region (e.g., the number of resource blocks) and / or the time domain region (e.g., the number of symbols) of the CORESET 320).

[0068] As shown, a symbol 315 including a CORESET 320 may include one or more control channel elements (CCEs) 325 (shown as two CCEs 325 as an example) across a portion of the system bandwidth. The CCEs 325 may include downlink control information (DCI) for providing control information for wireless communications. The base station may transmit the DCI during a plurality of CCEs 325 (as shown), wherein the number of CCEs 325 used for transmission of the DCI represents an aggregation level (AL) used by the BS for transmission of the DCI. Figure 3 , an aggregation level of two is shown as an example, which corresponds to two CCEs 325 in time slot 310. In some aspects, a different aggregation level may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

[0069] Each CCE 325 may include a fixed number of resource element groups (REGs) 330 (shown as 6 REGs 330), or may include a variable number of REGs 330. In some aspects, the number of REGs 330 included in a CCE 325 may be specified by a REG cluster size. A REG 330 may include one resource block, which may include 12 resource elements (REs) 335 within a symbol 315. A resource element 335 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0070] The search space may include all possible locations where a PDCCH may be located (e.g., in time and / or frequency). CORESET 320 may include one or more search spaces, such as a UE-specific search space (USS), a group common search space, and / or a common search space (CSS). The search space may indicate a set of CCE positions in which a UE may find a PDCCH that may potentially be used to send control information to the UE. The possible locations of a PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group common PDCCH (e.g., for multiple UEs), and / or the aggregation level being used. The possible locations of a PDCCH (e.g., in time and / or frequency) may be referred to as PDCCH candidates, and the set of all possible PDCCH locations at an aggregation level may be referred to as a search space. For example, the set of all possible PDCCH locations for a particular UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH locations for all UEs may be referred to as a common search space. The set of all possible PDCCH locations for a particular UE group may be referred to as a group common search space. One or more search spaces across aggregation levels may be referred to as a search space (SS) set.

[0071] The CORESET 320 may be interleaved or non-interleaved. An interleaved CORESET 320 may have a CCE to REG mapping such that adjacent CCEs are mapped to scattered REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to continuous REG bundles of the CORESET 320). A non-interleaved CORESET 320 may have a CCE to REG mapping such that all CCEs are mapped to continuous REG bundles of the CORESET 320 (e.g., in the frequency domain).

[0072] In some RATs (such as 3GPP Release 15 for 5G / NR), different PDCCH monitoring capabilities are defined. As an example, a first feature group may be mandatory for Release 15 UEs, which may indicate that the UE is able to monitor all PDCCH candidates for data within the first few symbols of a scheduling time slot. As another example, a second feature group may be optionally supported for Release 15 UEs, which may be defined at least in part based on the concept of span. The span is the number of consecutive symbols in a time slot in which the UE is configured to monitor the PDCCH. Each PDCCH monitoring opportunity is within a span. A time slot may include multiple spans, and a span may include one or more PDCCH candidates. Different span configurations may be supported.

[0073] In a 5G / NR network, a network entity may send PDCCH communications (e.g., including control information (such as DCI)) based at least in part on a search space set. A given search space set defines candidates that can carry PDCCH communications within the search space set, where each candidate is associated with one or more CCEs. "Candidates" are used interchangeably with "PDCCH candidates" herein. A CCE may consist of multiple REGs. A REG may include a resource block and an OFDM symbol. One or more search space sets may be associated with a CORESET. In a 5G / NR network, a network entity may flexibly schedule and send PDCCH communications. In other words, the transmission of PDCCH communications in a 5G / NR network is not limited to a specific set of frequency resources and / or time resources in a given radio frame, such as in the case of an LTE network. PDCCH frequency domain and time domain resources are configured on a per-CORESET basis. Therefore, once a UE is configured with a CORESET, the UE has information identifying which resource blocks in the frequency domain are assigned to the search space set associated with the CORESET and information identifying the number of consecutive symbols occupied by the search space set.

[0074] In order to receive PDCCH communications associated with one or more candidates of a given UE-specific search space set (i.e., a search space set that may carry control information that varies for one or more specific UEs), the UE may attempt to decode the PDCCH communications in the candidates of the search space set. For example, the UE may determine one or more CCE indices associated with the candidate and may attempt to decode the PDCCH communication (e.g., using a blind decoding procedure). The UE may signal to the base station a capability indicating how many non-overlapping CCEs and blind decoding (BD) the UE can handle. In some cases (e.g., 3GPP Release 15 for 5G / NR), a limit on the number of non-overlapping CCEs and BDs is defined on a per-slot basis (e.g., a per-slot CCE / BD limit (also referred to as a per-slot capability). In some cases (e.g., 3GPP Release 16 for 5G / NR), a limit on the number of non-overlapping CCEs and BDs is defined on a per-span basis (e.g., a per-span CCE / BD limit (also referred to as a per-span capability).

[0075] The PDCCH monitoring capability defined on a per-span basis may be referred to herein as a span-based monitoring capability or a Release 16 monitoring capability, while the PDCCH monitoring capability defined on a per-slot basis may be referred to as a slot-based monitoring capability or a Release 15 monitoring capability. In other words, slot-based monitoring is to monitor which CCE / BD restrictions are defined per slot, while span-based monitoring is to monitor which CCE / BD restrictions are defined per span.

[0076] The span configuration may be associated with a per-span capability for the number of BDs and / or the number of non-overlapping CCEs in the span. The per-span capability for the number of BDs may identify the maximum number of BDs that may be configured in the span, and the per-span capability for the number of non-overlapping CCEs may identify the maximum number of non-overlapping CCEs that may be configured in the span. These per-span capabilities may also be referred to as BD limits and CCE limits, respectively.

[0077] In some cases, a network entity may send an indication of a PDCCH configuration, and the UE may receive the indication. The PDCCH configuration may be associated with, or may be based at least in part on, a PDCCH BD restriction or a PDCCH CCE restriction. In some cases, the PDCCH configuration may configure the number of PDCCH candidates associated with the UE, which results in the number of blind decodings or the number of CCEs exceeding the PDCCH blind decoding limit and the PDCCH CCE limit. This may be referred to as "oversubscription" in this document. The UE may apply one or more oversubscription rules or drop rules in an oversubscription scenario so that the number of blind decodings does not exceed the PDCCH blind decoding limit or the number of CCEs does not exceed the PDCCH CCE limit.

[0078] For example, the UE may determine to monitor a PDCCH candidate associated with a CSS set (e.g., a search space set associated with a group of UEs). The UE may determine the number of blind decodings and / or CCEs corresponding to the PDCCH candidates associated with the CSS set. The UE may subtract the number of blind decodings and / or CCEs from the PDCCH blind decoding limit and / or the PDCCH CCE limit, respectively, to determine the remaining number of blind decodings and / or CCEs.

[0079] The UE may identify the USS set with the lowest index relative to other USS sets (e.g., a search set associated only with the UE), and may determine the number of blind decodings and / or CCEs corresponding to the PDCCH candidates associated with the identified USS set. The UE may determine whether the number of blind decodings and / or CCEs corresponding to the PDCCH candidates associated with the identified USS set is greater than or equal to the remaining number of blind decodings and / or CCEs. When the number of blind decodings and / or CCEs corresponding to the PDCCH candidates associated with the identified USS set is greater than or equal to the remaining number of blind decodings and / or CCEs, the UE may determine to monitor the PDCCH candidates associated with the identified USS set. When the number of blind decodings and / or CCEs corresponding to the PDCCH candidates associated with the identified USS set is less than the remaining number of blind decodings and / or CCEs, the UE may determine not to monitor the PDCCH candidates associated with the identified USS set or the PDCCH candidates associated with any remaining USS sets. The UE may continue in a similar manner for each USS set.

[0080] In some aspects, a network entity may broadcast a synchronization signal block (SSB), which may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) centralized within a physical broadcast channel (PBCH). Accordingly, an SSB may also be referred to as an SS / PBCH block.

[0081] Accordingly, a UE (e.g., UE 120) may detect the PSS and / or SSS to determine a physical cell identifier (PCID) associated with a network entity and timing associated with the PBCH. Accordingly, the UE 120 may decode the PBCH to obtain a master information block (MIB) message. The MIB message may include frequency and timing information to allow the UE 120 to establish a radio resource control (RRC) connection with a cell including the network entity, and information for scheduling the reception of remaining minimum system information (RMSI) by the UE 120. For example, the MIB message may include a pdcch-ConfigSIB1 data structure (e.g., as defined in a 3GPP specification and / or another standard) or another similar data structure defining a search space (e.g., in a physical downlink control channel (PDCCH), etc.), where the UE 120 may receive scheduling information for the RMSI. Such a search space may be referred to as a type 0-PDCCH common search space (CSS).

[0082] In some cases, the MIB message may include information associated with a control resource set (CORESET) configuration that defines physical resources (e.g., one or more frequency resources, one or more time resources, and / or other resources) for monitoring a Type 0-PDCCH CSS. Accordingly, the CORESET may be referred to as a Type 0-PDCCH CORESET.

[0083] For other CSSs (e.g., a type 0A-PDCCH CSS associated with an additional SIB message, a type 1-PDCCH CSS associated with a random access response (RAR), and / or a type 2-PDCCH CSS associated with a paging occasion (PO)), the network entity may instruct UE 120 to monitor a similar set of monitoring opportunities including monitoring opportunities in consecutive time slots (e.g., by setting SearchSpaceOtherSystemInformation, ra-SearchSpace, and / or pagingSearchSpace in PDCCH-ConfigCommon as defined in a 3GPP specification and / or another standard to zero). These other CSSs may be similarly associated with corresponding CORESET configurations (e.g., a type 0A-PDCCH CSS, a type 1-PDCCH CSS, and / or a type 2-PDCCH CSS as described above) that define physical resources for monitoring the CSS. Accordingly, these corresponding CORESETs may be referred to as a type 0A-PDCCH CORESET, a type 1-PDCCH CORESET, or a type 2-PDCCH CORESET, respectively.

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

[0085] Figure 4 4 is a diagram illustrating an example 400 of multi-slot monitoring according to the present disclosure. Figure 4 As shown, a UE (e.g., UE120) may monitor a set 405 of monitoring opportunities (MOs) that are continuous across time slots (e.g., PDCCH monitoring per time slot). As used herein, a "time slot" may refer to a portion of a subframe, which in turn may be a portion of a radio frame within an LTE, 5G, or other wireless communication structure. In some aspects, a time slot may include one or more symbols. In addition, a "symbol" may refer to an OFDM symbol or another similar symbol within a time slot. A set 405 of MOs may be associated with a search space set.

[0086] In example 400, set 405 includes MO 410a in time slot n, where n represents an integer. Although shown at the beginning of time slot n, MO 410a can be configured to include one or more symbols anywhere in time slot n. Set 405 includes MOs that are continuous across time slots. Accordingly, in set 405, MO 410b is in time slot n+1. These continuous MOs can be repeated in time. In example 400, this repetition is in each time slot, so that MO 410c is in time slot n+2, MO 410d is in time slot n+4, MO 410e is in time slot n+4, MO 410f is in time slot n+5, MO 410g is in time slot n+6, MO 410h is in time slot n+7, MO 410i is in time slot n+8, and so on. Although the continuous MO is repeated in each time slot in Example 400, the continuous MO may be repeated every other time slot (e.g., MO 410c in time slot n+3, and MO 410d in time slot n+4, etc.), every three time slots (e.g., MO 410c in time slot n+4, and MO 410d in time slot n+5, etc.), or according to a larger period.

[0087] In higher frequencies (e.g., between 52.6 GHz and 114.25 GHz), phase noise may increase. Accordingly, in order to reduce the effects of phase noise, wireless networks may adopt larger subcarrier spacing (SCS). As used herein, "subcarrier spacing" or "SCS" may refer to the frequency range (or amount of bandwidth) between subcarriers used in a cell of a wireless network. For example, a cell configured for FR2 may use an SCS between 60 kHz and 120 kHz, while a cell configured for a higher frequency may use an SCS between 240 kHz and 1.92 MHz. A larger SCS results in a time slot with a shorter duration. For example, a time slot in FR2 with a 120 kHz SCS may be approximately 125 μs in length, while a time slot in a higher frequency with a 960 kHz SCS may be approximately 15.6 μs in length.

[0088] In some cases, the processing timeline of UE 120 (e.g., for control and data processing) may not scale proportionally with the length of the time slot. For example, a UE 120 using a lower frequency range (e.g., FR1 / FR2) can enjoy the energy-saving advantages of micro-sleep. However, for a UE 120 using a higher frequency range (e.g., FR4), control channel processing may be comparable to the time slot length, or may even exceed the time slot length. Therefore, micro-sleep may not be possible. As another example, a UE 120 using FR1 / FR2 may be configured to monitor PDCCH in each time slot. However, in FR4 (e.g., due to limited processing power), the minimum PDCCH monitoring period may be greater than a single time slot. Therefore, it may not be possible to perform PDCCH monitoring in each time slot.

[0089] In some cases, UE 120 may be configured to perform micro-sleep with or without cross-slot scheduling. In a first example, UE 120 may perform PDCCH monitoring in the first three symbols of a slot, and UE 120 may perform micro-sleep with cross-slot scheduling in the remaining 11 symbols. In a second example, PDCCH monitoring and processing time may require half (or more) of the slot time. Therefore, micro-sleep without cross-slot scheduling may be less than half of the slot length.

[0090] In some cases, UE 120 may be configured to perform multi-slot PDCCH monitoring. For example, UE 120 may be configured to monitor PDCCH every other slot or every few slots instead of every single slot. Figure 4 As further shown, due to the short duration of the time slot, UE 120 can monitor a set 415 of MOs that are non-continuous across time slots (e.g., multi-slot PDCCH monitoring). The set 415 of MOs can be associated with a CSS. In example 400, the set 415 includes MOs 420a in time slot n, where n represents an integer. Although shown at the beginning of time slot n, MO 420a can be configured to include one or more symbols anywhere within time slot n. The set 415 includes MOs that are non-continuous across time slots. Accordingly, in the set 415, MO 420b is in time slot n4, MO 420c is in time slot n+8, and so on. Although the non-continuous MO is repeated every three time slots in example 400, the continuous MO may be repeated every other time slot (e.g., MO 420b in time slot n+2, MO 420c in time slot n+4, etc.), every eight time slots (e.g., MO 420b in time slot n+8, MO 420c in time slot n+16, etc.), or according to a larger period.

[0091] For some SCS, such as, for SCS of 480kHz or 960kHz, etc., multi-slot PDCCH monitoring can be supported by UE. In some cases, UE can be associated with the capability for multi-slot PDCCH monitoring. Capability can be represented by two values ​​(X, Y), where X is the number of slots included in the slot group for multi-slot PDCCH monitoring, and Y is the number of continuous slots within a given slot group, where PDCCH can be monitored by UE. As used herein, "slot group" can refer to two or more slots (e.g., set 415 can be associated with slot group size 4 (e.g., the value of X is 4)). The supported value of X can be based at least in part on one or more capabilities of UE 120, and the network entity can configure one or more PDCCH search spaces for UE 120 based at least in part on UE 120 capability reports. In some cases, variable Y can be used to represent the monitoring span. The monitoring span can correspond to the number of continuous slots in which the monitoring opportunity resides within the slot group. The monitoring occasions may be defined within a monitoring span of a group of time slots. For example, a monitoring span with one time slot may have a value of Y=1, and a monitoring span with three consecutive time slots may have a value of Y=3.

[0092] In some cases, for a group (1) search space (SS) (e.g., a type 1 common search space (CSS) and a type 3 CSS, a UE-specific SS with a dedicated RRC configuration), one or more of the following may be supported: the SS may monitor within Y consecutive time slots within a time slot group of X time slots; the Y consecutive time slots may be located anywhere within the time slot group of X time slots; the positions of the Y consecutive time slots within the time slot group of X time slots may be maintained across different time slot groups; and blind decoding (BD) attempts for all group (1) SSs may be restricted to falling within the same Y consecutive time slots.

[0093] In some cases, for group (2) SSs (eg, type 1 CSS and types 0, 0A, and 2 CSS without dedicated RRC configuration), the SS monitoring position may be anywhere within the slot group of X slots (exceptions may exist).

[0094] In some cases, the supported combinations of (X,Y) may be as follows. A UE 120 capable of multi-slot monitoring may (e.g., mandatorily) support: for SCS 480kHz: (X,Y)=(4,1); and for SCS 960kHz: (X,Y)=(8,1). A UE 120 capable of multi-slot monitoring may (e.g., optionally) support: for SCS 480kHz: (X,Y)=(4,2); and for SCS 960kHz: (X,Y)=(8,4), (4,2), (4,1).

[0095] PDCCH candidate restrictions, BD restrictions and / or CCE restrictions may be defined (e.g., by wireless communication standards, such as 3GPP) for different supported multi-slot PDCCH monitoring capabilities. For example, for SCS 480kHz and (X,Y)=(4,1), the maximum number of PDCCH candidates monitored in a slot group may be 20, and the maximum number of non-overlapping CCEs in a slot group may be 32. For another example, for SCS 960kHz and (X,Y)=(4,2), the maximum number of PDCCH candidates monitored in a slot group may be 10, and the maximum number of non-overlapping CCEs in a slot group may be 16. For another example, for SCS 960kHz and (X,Y)=(8,1), the maximum number of PDCCH candidates monitored in a slot group may be 20, and the maximum number of non-overlapping CCEs in a slot group may be 32.

[0096] For smaller slot group sizes (e.g., X=4), the UE may have a strict or small BD restriction and / or CC restriction. For example, for SCS 960kHz and (X,Y)=(4,1) and (4,2), the maximum number of PDCCH candidates monitored in a slot group may be 10, and the maximum number of non-overlapping CCEs in a slot group may be 16. In some cases, up to 7 PDCCH candidates and 28 CCEs may be configured for a CSS set (e.g., as defined by a wireless communication standard (e.g., by 3GPP Technical Specification 38.213 Version 17.0.0), or otherwise fixed). Therefore, for smaller slot group sizes (e.g., X=4), the maximum aggregation level for the CSS may be limited to less than or equal to 16 due to limited BD / CCE budget. As a result, broadcast or common PDCCH performance may be degraded. Additionally, after assigning PDCCH candidates, BDs, or CCEs for the CSS set, there may be few PDCCH candidates, BDs, or CCEs that can be assigned to the USS set (e.g., due to limited BD / CCE budget associated with a smaller slot group size). Therefore, unicast PDCCH performance and flexibility may be degraded.

[0097] Some techniques and apparatus described herein enable USS and CSS assignments for multi-slot based control channel (e.g., PDCCH) monitoring. For example, multi-slot based PDCCH monitoring may be associated with different slot group sizes for CSS sets and USS sets. For example, a UE may receive a search space configuration indicating a first configuration for USS associated with a first slot group size (e.g., X1) and a second configuration for CSS associated with a second slot group size (e.g., X2). The UE may receive communications via a downlink control channel (e.g., PDCCH) based at least in part on monitoring a downlink control channel according to the search space configuration. In some aspects, PDCCH candidates and / or CCE assignments and overbooking rules may be defined for scenarios in which the UE is configured with a CSS set and a USS set with different slot group sizes.

[0098] Therefore, downlink control channel monitoring and / or communication can be improved. For example, using different slot group sizes for CSS sets and USS sets can improve the flexibility of PDCCH candidate and / or CCE assignment. For example, CSS can be associated with a first slot group size (for example, the first slot group size is associated with a first PDCCH restriction, a first BD restriction and / or a first CCE restriction). USS can be associated with a second slot group size (for example, the second slot group size is associated with a second PDCCH restriction, a second BD restriction and / or a second CCE restriction). In some aspects, the first slot group size can be larger than the second slot group time slot. Therefore, UE can implement assignment of more PDCCH candidates and / or CCE for CSS (for example, within a larger slot group size associated with a larger PDCCH restriction, a BD restriction and / or a CCE restriction) (for example, because CSS can be associated with more PDCCH candidates and / or CCE than USS). The UE may implement assignment of PDCCH candidates and / or CCEs for the USS within a smaller time slot group size (e.g., after allocating resources for the CSS set, based at least in part on the remaining PDCCH candidates or CCE budget) to save resources and / or ensure that the UE can implement entry into a sleep state or a micro-sleep state. Therefore, the search space configuration associated with different time slot group sizes for the CSS set and the USS set may increase the flexibility of PDCCH candidate and / or CCE assignment.

[0099] FIG. 5A to FIG. 5G is a diagram of an example 500 associated with USS and CSS assignment for multi-slot based control channel monitoring according to the present disclosure. Figure 5AAs shown, a network entity 505 (e.g., base station 110, CU, DU, and / or RU) may communicate with a UE (e.g., UE 120). In some aspects, the network entity 505 and the UE 120 may be part of a wireless network (e.g., wireless network 100). In some aspects, the UE 120 and the network entity 505 may be part of a wireless network (e.g., wireless network 100). FIG. 5A to FIG. 5G The operations shown are performed after a wireless connection has been established.

[0100] In some aspects, the network entity 505 may send the configuration information, and the UE 120 may receive the configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of radio resource control (RRC) signaling, one or more medium access control (MAC) control elements (MAC-CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., stored by the UE 120 and / or previously indicated by the network entity 505 or another network device), and / or explicit configuration information for the UE 120 to configure itself, etc.

[0101] In some aspects, the configuration information may instruct the UE 120 to monitor a downlink control channel (e.g., a PDCCH) using multi-slot PDCCH monitoring. In some aspects, the configuration information may instruct the UE 120 to monitor a downlink control channel using one or more CSS sets and one or more USS sets, wherein the CSS set is associated with a first slot group size and the USS set is associated with a second slot group size. In some aspects, the configuration information may instruct the UE 120 to report capabilities associated with multi-slot PDCCH monitoring. In some aspects, the configuration information may instruct the UE 120 to report capabilities associated with PDCCH monitoring using different slot group sizes for the CSS set and the USS set.

[0102] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0103] As shown by reference numeral 510, UE 120 may send a capability report (e.g., to network entity 505 or to another network entity). Network entity 505 may receive the capability report (e.g., from UE 120 or from another network entity). In some aspects, the capability report may indicate that the UE supports multi-slot downlink control channel monitoring. In some aspects, the capability report may indicate that UE 120 supports CSS sets and USS sets configured with different slot group sizes.

[0104] For example, UE 120 may send a capability report indicating at least one of a first supported first slot group size for USS and / or a second supported slot group size for CSS. In some aspects, UE 120 may report different capabilities for CSS and USS. For example, UE 120 may send an indication of a first PDCCH monitoring capability of (X, Y) associated with multi-slot PDCCH monitoring of USS. UE 120 may send an indication of a second PDCCH monitoring capability of (X, Y) associated with multi-slot PDCCH monitoring of CSS. In some other aspects, UE 120 may send an indication of a single capability (e.g., (X, Y)), where UE 120 may be expected to support any configuration of (X3, Y3) for CSS and / or USS as long as X3≥X and Y3≤Y. For example, for the capabilities of (X, Y) and (X3, Y3), when X3≥X, the PDCCH candidate restriction, BD restriction and / or CCE restriction associated with (X3, Y3) may be greater than or equal to the restriction associated with (X, Y).

[0105] The UE 120 may send the capability report via uplink control channel communication (e.g., physical uplink control channel (PUCCH) communication), uplink data channel or shared channel communication (e.g., physical uplink shared channel (PUSCH) communication), UE capability signaling, UE assistance information (UAI) communication, or another type of communication or signaling. The network entity 505 may receive the capability report and may determine a downlink control channel monitoring configuration for the UE 120 based at least in part on the capability report (e.g., as described in more detail elsewhere herein).

[0106] As indicated by reference numeral 515, the UE 120 may receive a search space configuration (e.g., from the network entity 505 or from another network entity) indicating a first configuration for a USS associated with a first slot group size (e.g., X1) and a second configuration for a CSS associated with a second slot group size (e.g., X2). The network entity 505 may send the search space configuration (e.g., to the UE 120 or to another network entity). The search space configuration may be included in a PDCCH configuration or associated with it (e.g., pdcch-Config). In some aspects, the UE 120 may receive the search space configuration via one or more of RRC signaling, one or more MAC-CEs, and / or DCI, etc. In some aspects, the search space configuration may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., stored by the UE 120 and / or previously indicated by the network entity 505 or another network device), and / or explicit configuration information for the UE 120 to configure itself, etc.

[0107] The first configuration for USS may use a slot group size X1 to indicate one or more USS sets associated with multi-slot PDCCH monitoring. A USS set may indicate a set of frequency domain resources and / or time domain resources (e.g., one or more PDCCH candidates, one or more BDs, and / or one or more CCEs) to be monitored by UE 120 for receiving PDCCH communications (e.g., unicast PDCCH communications). For example, a USS set may be associated with one or more monitoring opportunities (MOs) within the number of X1 slots. A second configuration for CSS may use a slot group size X2 to indicate one or more CSS sets associated with multi-slot PDCCH monitoring. A CSS set may indicate a set of frequency domain resources and / or time domain resources (e.g., one or more PDCCH candidates, one or more BDs, and / or one or more CCEs) to be monitored by UE 120 for receiving PDCCH communications (e.g., public or broadcast PDCCH communications). For example, a CSS set may be associated with one or more MOs within the number of X2 slots.

[0108] The network entity 505 may determine the search space configuration. In some aspects, the network entity 505 may determine the search space configuration based at least in part on a capability (e.g., (X, Y) capability and / or another capability) of the UE 120, such as one or more capabilities indicated via a capability report. In some aspects, the network entity 505 may configure the CSS set and the USS set with different slot group sizes for the UE 120 based at least in part on the UE 120 indicating that the UE 120 supports configuring the CSS set and the USS set with different slot group sizes (e.g., in a capability report).

[0109] In some aspects, the network entity 505 may determine the values ​​of X1 and / or X2 based at least in part on the capabilities of the UE 120 (e.g., the (X, Y) capabilities and / or another capability). In some aspects, the network entity 505 may determine the value of X1 (e.g., for the USS) based at least in part on the capabilities of the UE 120, and may determine the value of X2 (e.g., for the CSS) based at least in part on a threshold value common to multiple (e.g., all) UEs communicating with the network entity 505. For example, in some cases, the threshold value (e.g., a limit on the size of the CSS time slot group) may be defined by a wireless communication standard (such as 3GPP), or otherwise fixed (e.g., and may be stored in a memory of the network entity 505 and / or the UE 120, such as part of an original equipment manufacturer (OEM) configuration). For another example, the network entity 505 may determine the threshold value and may send an indication of the threshold value. For example, the network entity 505 may send an indication of the limitation on the CSS slot group size in a broadcast communication, a system information communication (eg, in a system information block (SIB) or a master information block (MIB)), and / or an RRC communication, among others.

[0110] In some aspects, the UE 120 may receive an indication of the first time slot group size X1 and / or the second time slot group size X2. In some aspects, the indication of the first time slot group size X1 and / or the second time slot group size X2 may be included in a search space configuration (e.g., in an RRC communication). As another example, the indication of the first time slot group size X1 and / or the second time slot group size X2 may be included in a system information communication (e.g., in a SIB or MIB). For example, the search space configuration may indicate a value of X1, and the system information communication or another RRC communication may indicate a value of X2. As another example, the search space configuration may indicate a value of X1, and the value of X2 may be stored by the UE 120, such as in an OEM configuration (e.g., when the value of X2 is defined by a wireless communication standard (such as 3GPP), or otherwise fixed). In other words, the value of X1 (e.g., for USS) may be specific to UE 120 and selected by the network entity based at least in part on the capabilities (e.g., (X, Y) capabilities and / or another capability) of UE 120. The value of X2 may be common to multiple UEs, may be a predetermined value hard-coded in a memory of UE 120 or network entity 505, and / or may be indicated by network entity 505 via system information or RRC signaling, etc.

[0111] In some aspects, a first blind decoding restriction (e.g., a first PDCCH candidate restriction) and / or a first CCE restriction associated with monitoring a downlink control channel via a USS may be based at least in part on a first slot group size X1. A second blind decoding restriction (e.g., a second PDCCH candidate restriction) and / or a second CCE restriction associated with monitoring a downlink control channel via a CSS may be based at least in part on a second slot group size X2. In other words, the time units for applying PDCCH oversubscription and / or drop rules may be different for USS and CSS.

[0112] In some aspects, the first time slot group size may be less than or equal to the second time slot group size (e.g., X1≤X2). By making the configuration value of X2 greater than the configuration value of X1, the flexibility of assigning PDCCH candidates and / or CCEs for CSS monitoring may be increased. For example, previously, if UE 120 only supported a small time slot group size (e.g., such as X=4), CSS monitoring and / or communication performance may be degraded due to strict PDCCH candidate restrictions and / or CCE restrictions associated with the small time slot group size. By making the configuration value of X2 greater than the configuration value of X1, the PDCCH candidate restrictions and / or CCE restrictions associated with the CSS may be relaxed, while the USS may also be configured to a smaller time slot group size.

[0113] In some aspects, the second time slot group size may be an integer multiple of the first time slot group size. For example, X2 may be K·X1, where K is an integer greater than or equal to one (1). As explained in more detail elsewhere herein, this may reduce the complexity associated with applying PDCCH monitoring oversubscription and / or drop rules between USS sets and CSS sets having different time slot group sizes.

[0114] UE 120 may configure itself based at least in part on the search space configuration.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the search space configuration.

[0115] like Figure 5B , an example of a configured CSS (e.g., CSS 540 and USS 545) is depicted (e.g., as configured by a search space configuration). As shown, CSS 540 can be associated with a slot group size of X2, and USS 545 can be associated with a slot group size of X1. For example, X2 can be eight, and X1 can be four. As an example, Figure 5BAs shown, CSS540 can be associated with a single CSS set. The CSS set can be associated with a MO in an X2 slot with seven BDs (e.g., seven PDCCH candidates) and sixteen CCEs. USS 545 can be associated with a first USS set (USS1) and a second USS set (USS2). For example, in the first X1 slot, UE 120 can be configured to monitor the first USS set and the second USS set. In the second X1 slot, UE 120 can be configured to monitor the first USS set and the second USS set. The first USS set can be associated with four BDs (e.g., four PDCCH candidates) and eight CCEs. The second USS set can be associated with four BDs (e.g., four PDCCH candidates) and eight CCEs. As described above, the value X2 (e.g., eight) can be associated with a first BD restriction (e.g., a first PDCCH candidate restriction) and a first CCE restriction. For example, for a value of eight, UE 120 may be limited to configuring twenty PDCCH candidates (e.g., twenty BDs) and thirty-two CCEs within a given eight consecutive time slots. A value of X1 (e.g., four) may be associated with a second BD restriction (e.g., a second PDCCH candidate restriction) and a second CCE restriction. For example, for a value of four, UE 120 may be limited to configuring ten PDCCH candidates (e.g., ten BDs) and sixteen CCEs within a given eight consecutive time slots.

[0116] Back to Figure 5A As shown by reference numeral 520, the UE 120 and / or the network entity 505 may assign or allocate PDCCH candidates and / or CCEs to the CSS and the USS (e.g., the CSS 540 and the USS 545). In some aspects, the UE 120 may allocate PDCCH candidates (e.g., blind decodings) and / or CCEs to the CSS first and to the USS second. For example, the UE 120 may allocate blind decodings (e.g., PDCCH candidates) and / or CCEs to the CSS within a first number of slots indicated by the second slot group size (e.g., within an X2 slot) to obtain a remaining blind decoding or CCE budget, wherein the first blind decoding restriction or the first CCE restriction is based at least in part on the second slot group size. The UE 120 may allocate blind decodings (e.g., PDCCH candidates) and / or CCEs to the USS within a first number of slots indicated by the second slot group size, based at least in part on the remaining blind decoding or CCE budget.

[0117] For example, using Figure 5B, UE 120 may be associated with a twenty PDCCH candidate restriction (e.g., a BD restriction) and a thirty-two CCE restriction within an X2 slot. UE 120 may be configured with a CSS having seven BDs (e.g., seven PDCCH candidates) and sixteen CCEs. Therefore, after allocating seven PDCCH candidates for the CSS, the remaining blind decoding budget (e.g., remaining PDCCH budget) within the X2 slot may be thirteen (e.g., 20-7=13). Similarly, after allocating sixteen CCEs for the CSS, the remaining CCE budget within the X2 slot may be sixteen (e.g., 32-16=16). Therefore, UE 120 may have thirteen PDCCH candidates (e.g., thirteen BDs) and sixteen CCEs, which may be allocated to a USS set within an X2 slot.

[0118] In some aspects, as shown by reference numeral 525, the UE 120 may apply oversubscription and / or drop rules for the USS (e.g., if the number of PDCCH candidates and / or CCEs configured in the X2 slot for the USS is greater than the remaining blind decoding or CCE budget after allocating resources to the CSS). In some aspects, the network entity 505 may identify the set of USSs or MOs that are dropped (e.g., not monitored) by the UE 120 in a similar manner as described in more detail elsewhere herein. Figure 5B As shown, UE 120 may be configured with a first USS set having four BDs (e.g., four PDCCH candidates) and eight CCEs and a second USS set having four BDs (e.g., four PDCCH candidates) and eight CCEs. This results in UE 120 being configured with sixteen PDCCH candidates (e.g., eight in the first X1 slot and eight in the second X1 slot) and thirty-two CCEs (e.g., sixteen in the first X1 slot and sixteen in the second X1 slot) in the X2 slot. Since the sixteen PDCCH candidates are larger than the remaining PDCCH candidate budget (e.g., the thirteen remaining PDCCH candidate budgets as described above) and / or since the thirty-two CCEs are larger than the remaining CCE budget (e.g., the sixteen remaining CCE budgets as described above), UE 120 may apply one or more oversubscription and / or drop rules. In some aspects, one or more oversubscription and / or drop rules may be defined by a wireless communication standard (such as 3GPP) or otherwise fixed. In some aspects, one or more oversubscription and / or dropping rules may be indicated to the UE 120 (eg, by the network entity 505, in a search space configuration, in a system information communication, and / or in another communication).

[0119] In some aspects, one or more overbooking rules and / or one or more drop rules may assume X2 slots as time units. For example, for a slot group of X1 slots that overlaps with a slot group of X2 slots for a CSS, the overbooking and drop rules may assume X2 slots as time units (e.g., for each slot group of X1 slots). In other words, assuming that X2 is greater than or equal to X1, the UE 120 may allocate blind decodes or CCEs for the USS within a second number of slots indicated by the first slot group size (e.g., within X1 slots) based at least in part on a blind decode limit or a CCE limit, wherein the blind decode limit or the CCE limit is based at least in part on the first slot group size (e.g., X2).

[0120] like Figure 5CAs shown, the oversubscription and / or discarding rules may instruct the UE 120 to discard (e.g., prohibit monitoring) one or more USS sets until the number of PDCCH candidates and / or CCEs allocated for the USS 545 in the X2 time slot is less than or equal to the remaining PDCCH candidate budget and / or the remaining CCE budget in the X2 time slot. One or more USS sets may be identified based at least in part on an index value or identifier associated with one or more USS sets. For example, each USS set may be associated with an index value (e.g., searchSpaceID). The UE 120 may discard (e.g., prohibit monitoring) USS sets one by one in the order indicated by the index value. In some aspects, the order may be from the highest index value to the lowest index value. In some other aspects, the order may be from the lowest index value to the highest index value. For example, the UE 120 may first discard the first USS set (e.g., the USS set associated with the highest index value). UE 120 may determine whether the number of PDCCH candidates and / or CCEs allocated for USS 545 in the X2 slot is less than or equal to the remaining PDCCH candidate budget and / or the remaining CCE budget in the X2 slot. If the number of PDCCH candidates and / or CCEs allocated for USS 545 in the X2 slot is greater than the remaining PDCCH candidate budget and / or the remaining CCE budget in the X2 slot, UE 120 may discard a second USS set (e.g., a USS set associated with a second high index value after the first USS set). After discarding the second USS set, UE 120 may determine whether the number of PDCCH candidates and / or CCEs allocated for USS 545 in the X2 slot is less than or equal to the remaining PDCCH candidate budget and / or the remaining CCE budget in the X2 slot. UE 120 may continue to discard USS sets in this one-by-one manner until the number of PDCCH candidates and / or CCEs allocated for USS 545 in the X2 slot is less than or equal to the remaining PDCCH candidate budget and / or remaining CCE budget in the X2 slot, or until no USS sets remain.

[0121] For example, Figure 5CAs shown, UE 120 may discard the second USS set (e.g., USS2). After discarding the second USS set, UE 120 may be configured with only USS1, resulting in eight BD / PDCCH candidates and sixteen CCEs configured for USS 545 in the X2 slot (e.g., four BD / PDCCH candidates and eight CCEs in the first X1 slot and four BD / PDCCH candidates and eight CCEs in the second X1 slot). Since eight PDCCH candidates are less than the remaining thirteen PDCCH candidate budgets and since sixteen CCEs are equal to the remaining CCE budget, UE 120 may implement monitoring USS1 as configured. For example, UE 120 may allocate blind decoding / PDCCH candidates and / or CCEs for the first USS set associated with the first configuration.

[0122] For example, back to Figure 5A , as shown by reference numeral 530, UE 120 may monitor the downlink control channel via the first USS set and / or CSS. As described in more detail elsewhere herein, UE 120 may refrain from monitoring one or more USS sets associated with the first configuration (e.g., USS2) based at least in part on the number of blind decodes or CCEs associated with the first configuration exceeding a remaining blind decode or CCE budget within the first number of time slots.

[0123] Figure 5DAnother example of overbooking and / or discarding rules is depicted. For example, UE 120 may allocate blind decoding / PDCCH candidates and / or CCEs for one or more USS sets associated with a first configuration until the remaining blind decoding / PDCCH or CCE budget within the first number of slots (e.g., within an X2 slot) is met. For example, UE 120 may allocate PDCCH candidates and / or CCEs to USS MO in a one-by-one manner over time until the remaining PDCCH candidate budget and / or remaining CCE budget are met. For example, (e.g., after allocating PDCCH candidates and / or CCEs to CSS 540) the remaining PDCCH candidate budget may be thirteen and the remaining CCE budget may be sixteen. UE 120 may allocate PDCCH candidates (e.g., four PDCCH candidates) and CCEs (e.g., eight CCEs) to the first monitoring opportunity of USS1. This may result in nine new remaining PDCCH candidate budgets and eight new remaining CCE budgets. UE 120 may allocate PDCCH candidates (e.g., four PDCCH candidates) and CCEs (e.g., eight CCEs) to the first monitoring opportunity of USS2. This may result in five new remaining PDCCH candidate budgets and zero new remaining CCE budgets. Since there are no remaining CCEs available for allocation in the X2 time slot, UE 120 may discard (e.g., prohibit monitoring) the remaining configured monitoring opportunities for USS 545 (e.g., in the second X1 time slot). For example, UE 120 may monitor the downlink control channel via one or more USS sets (e.g., MO in the first X1 time slot). UE 120 may prohibit monitoring USS in any remaining USS MO associated with the first configuration (e.g., the USS may be discarded) based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decodings or CCE budgets in the first time slot number (e.g., in the X2 time slot).

[0124] Figure 5E Another example of an oversubscription and / or drop rule is depicted. Figures 5B to 5GAs shown, the number of slot groups associated with the USS 545 (e.g., two in the example shown) may overlap with a single slot group associated with the CSS 540. In some aspects, when allocating PDCCH candidates and / or CCEs for the USS 545, the UE 120 may allocate a first portion of blind decodings or CCEs for a first set of slots (e.g., for a first one or more sets of slots) for a first one or more sets of USSs associated with a first configuration within a first number of slots indicated by the second slot group size (e.g., within X2 slots). The UE 120 may allocate a second portion of blind decodings or CCEs for a second set of slots (e.g., for a second one or more sets of slots) for a first one or more sets of USSs associated with a first configuration within a first number of slots indicated by the second slot group size (e.g., within X2 slots). In other words, the UE 120 may allocate a first portion of blind decodings or CCEs for a first X1 slot and a second portion of blind decodings or CCEs for a second X1 slot. In some aspects, the first part and the second part may be the same. In other words, the UE 120 may evenly distribute the remaining blind decoding / PDCCH budget and / or the remaining CCE budget within the group of time slots associated with the USS 545 that overlap with the X2 time slot. In some other aspects, the first part and the second part may be different.

[0125] For example, the remaining PDCCH candidate budget may be thirteen, as described in the above example. UE 120 may allocate the remaining PDCCH candidate budget divided by K to each slot group associated with the USS that overlaps a single slot group of the CSS (e.g., where X2=K·X1). In this example, K is equal to two. Therefore, UE 120 may allocate six PDCCH candidates to the first X1 slot and seven PDCCH candidates to the second X1 slot. Additionally, UE 120 may allocate seven PDCCH candidates to the first X1 slot and six PDCCH candidates to the second X1 slot. For example, when the remaining PDCCH candidate budget divided by K is not an integer (e.g., 6.5 in this example), UE 120 may round the value up to the nearest integer (e.g., 7) for the first slot group, and round the number down to the nearest integer (e.g., 6) for the second slot group. As another example, UE 120 may allocate the remaining CCE budget divided by K to each time slot group associated with the USS that overlaps with a single time slot group of the CSS. For example, the remaining CCE budget may be sixteen and K may be two. Therefore, UE 120 may allocate eight CCEs for the first X1 time slot and eight CCEs for the second X1 time slot. UE 120 may also consider the PDCCH candidate restriction and / or CCE restriction for a given X1 time slot set when allocating PDCCH candidates and / or CCEs. For example, UE 120 may allocate a minimum value between the PDCCH candidate restriction for the X1 time slot and the remaining PDCCH candidate budget divided by K. Similarly, UE 120 may allocate a minimum value between the CCE restriction for the X1 time slot and the remaining CCE budget divided by K.

[0126] As an example, Figure 5E As shown, UE 120 may allocate six PDCCH candidates and eight CCEs for the first X1 time slot. UE 120 may allocate seven PDCCH candidates and eight CCEs for the second X1 time slot. Figure 5EAs shown, eight BDs (e.g., eight PDCCH candidates) and sixteen CCEs may be configured for each X1 time slot. Therefore, UE 120 may apply one or more overbooking and / or discarding rules. UE 120 may apply overbooking and / or discarding rules for each time slot group of the X1 time slot, respectively. For example, UE 120 may discard (e.g., prohibit monitoring) one or more USS sets until the number of PDCCH candidates and / or CCEs to be monitored by UE 120 is less than or equal to the number of PDCCH candidates and / or CCEs allocated for each time slot group of the X1 time slot. For example, UE 120 may discard USS2 in the first time slot group of the X1 time slot, resulting in four PDCCH candidates and eight CCEs (e.g., which are less than or equal to the allocated (six) PDCCH candidates and (eight) CCE budgets) being allocated for each time slot group. Therefore, UE 120 may monitor the downlink control channel via the first one or more USS sets (e.g., USS1) in the first X1 time slot set and the second X1 time slot set. Similarly, UE 120 may discard USS2 in a second slot group of X1 slots, resulting in four PDCCH candidates and eight CCEs being allocated for each slot group (e.g., which is less than or equal to the allocated (seven) PDCCH candidates and (eight) CCE budget). For example, in some aspects, UE 120 may refrain from monitoring USSs for a second one or more USS sets in a first X1 slot set (e.g., may discard USSs) based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the first portion of the blind decodings or CCEs. Similarly, UE 120 may refrain from monitoring USSs for a third one or more USS sets in a second slot set based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the second portion of the blind decodings or CCEs.

[0127] Fig. 5F Another example of an oversubscription and / or drop rule is depicted. Fig. 5F As shown, in some aspects, the UE 120 may monitor the USSs in one or more time slot groups overlapping with a single CSS time slot group, and may discard the set of USSs in one or more time slot groups (e.g., the remaining time slot groups) overlapping with the single CSS time slot group. For example, the remaining PDCCH candidate budget and / or the remaining CCE budget may be applied only to one or more (but not all) of the USS time slot groups that overlap with the CSS time slot group in time. For example, Fig. 5FAs shown, the remaining PDCCH candidate budget (e.g., thirteen) and / or the remaining CCE budget (e.g., sixteen) may be applied to the first time slot group of the X1 time slot. The second time slot group of the X1 time slot may be discarded (e.g., may not be monitored by the UE 120). Since the MO configured in the first time slot group of the X1 time slot is combined into eight PDCCH candidates (e.g., which is less than the thirteen remaining PDCCH candidate budget) and sixteen CCEs (e.g., which is equal to the sixteen remaining CCE budget), the UE 120 may monitor both USS1 and USS2 in the first time slot group of the X1 time slot. If the PDCCH candidates and / or CCEs configured in the first time slot group of the X1 time slot are greater than the remaining PDCCH candidate budget and / or the remaining CCE budget, the UE 120 may (e.g., in a similar manner as described in more detail elsewhere herein) discard one or more USS sets configured within the first time slot group of the X1 time slot.

[0128] For example, UE 120 may allocate blind decoding or CCE for a first set of time slots within a first number of time slots (e.g., X2) indicated by a second time slot group size, wherein the first set of time slots includes a second number of time slots (e.g., X1) indicated by the first time slot group size. UE 120 may monitor a downlink control channel via a USS in the first set of time slots. UE 120 may prohibit monitoring of the USS in a second set of time slots, wherein the second set of time slots includes a second number of time slots, based at least in part on the number of blind decoding or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots. In some aspects, the UE identifies the second set of time slots based at least in part on the time domain location of the CSS measurement opportunity indicated by the second configuration. For example, UE 120 may discard the first one or more time slot groups associated with the USS in time. Additionally, UE 120 may discard the last one or more time slot groups associated with the USS in time.

[0129] Figure 5G Another example of an oversubscription and / or drop rule is depicted. Figure 5G As shown, in some aspects, the oversubscription and / or drop rules may instruct the UE 120 to drop (e.g., not monitor) any USS MO configured in a timeslot group that at least partially overlaps with a CSS timeslot group that includes a configured CSS MO. Figure 5GAs shown, the first time slot group of X1 time slots and the second time slot group of X1 time slots may overlap in time with the CSS time slot group of X2 time slots (e.g., including the configured CSSMO). UE 120 may monitor the downlink control channel via the CSS according to the search space configuration. UE 120 may be configured in one or more time slot groups based at least in part on USSs, prohibiting monitoring of the downlink control channel via the USSs (e.g., may be discarded), wherein the one or more time slot groups overlap in the time domain with the time slot group associated with the CSS. In other words, regardless of the remaining PDCCH candidate budget or the remaining CCE budget, UE 120 may discard all USSs in the time slot group of X1 time slots, wherein the time slot group overlaps in the time domain with the CSS time slot group of X2 time slots.

[0130] In some aspects, if the CSS is not configured, the UE 120 may apply legacy oversubscription and / or drop rules (e.g., as defined by a wireless communication standard (such as Release 17 or Release 16 of a 3GPP technical specification), or otherwise fixed). In some aspects, the UE 120 may monitor a downlink control channel according to a search space configuration via the USS based at least in part on not configuring a CSS measurement opportunity in a first group of time slots, wherein the first group of time slots at least partially overlaps in the time domain with a second group of time slots associated with the USS.

[0131] Back to Figure 5A As shown by reference numeral 535, the UE 120 may receive PDCCH communications (e.g., via the CSS and / or USS) based at least in part on monitoring the PDCCH according to the search space configuration. For example, the PDCCH communication may be sent in the CSS or USS (e.g., by the network entity 505 or by another network entity). In some aspects, the network entity 505 may send one or more signals using a downlink control channel according to the search space configuration via the USS based at least in part on not configuring any CSS measurement opportunities in the first time slot group, wherein the first time slot group at least partially overlaps with a second time slot group associated with the USS in the time domain. In some aspects, the network entity 505 may prohibit sending downlink signals via the USS and / or MO that have been discarded by the UE 120. Based at least in part on the search space configuration, wherein the CSS and USS are associated with different time slot group sizes, the performance of the PDCCH communication may be improved.

[0132] For example, using different slot group sizes for the CSS set and the USS set can increase the flexibility of PDCCH candidate and / or CCE assignment. For example, the CSS can be associated with a first slot group size (e.g., the first slot group size is associated with a first PDCCH restriction, a first BD restriction, and / or a first CCE restriction). The USS can be associated with a second slot group size (e.g., the second slot group size is associated with a second PDCCH restriction, a second BD restriction, and / or a second CCE restriction). Therefore, the UE 120 can achieve assignment of more PDCCH candidates and / or CCEs for the CSS (e.g., within a larger slot group size associated with a larger PDCCH restriction, a BD restriction, and / or a CCE restriction) (e.g., because the CSS can be associated with more PDCCH candidates and / or CCEs than the USS). UE 120 may implement assigning PDCCH candidates and / or CCEs for USS within a smaller slot group size (e.g., based at least in part on the remaining PDCCH candidates or CCE budget after allocating resources for the CSS set) to save resources and / or ensure that the UE can implement entering a sleep state or a micro-sleep state. Therefore, the search space configuration associated with different slot group sizes for the CSS set and the USS set may increase the flexibility of PDCCH candidate and / or CCE assignment.

[0133] As indicated above, provided as an example FIG. 5A to FIG. 5G Other examples can be compared with FIG. 5A to FIG. 5G The examples described are different.

[0134] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE in accordance with the present disclosure. Example process 600 is an example of a UE (eg, UE 120) performing operations associated with USS and CSS assignment for control channel monitoring based on multiple time slots.

[0135] like Figure 6 As shown, in some aspects, process 600 may include: receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for USSs associated with a first time slot group size and a second configuration for CSSs associated with a second time slot group size (block 610). For example, (e.g., using Figure 8 The UE (including the described communication manager 140 and / or receiving component 802) may receive a search space configuration from a network entity indicating a first configuration for a USS associated with a first time slot group size and a second configuration for a CSS associated with a second time slot group size, as described above.

[0136] like Figure 6As will be further shown, in some aspects, process 600 may include receiving a communication from a network entity via a downlink control channel based at least in part on monitoring the downlink control channel according to the search space configuration (block 620). Figure 8 The UE (including the communication manager 140 and / or receiving component 802 described in the foregoing) can monitor a downlink control channel via which communications are received from a network entity based at least in part on the search space configuration, as described above.

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

[0138] In a first aspect, process 600 includes monitoring a downlink control channel according to a search space configuration via at least one of a USS or a CSS.

[0139] In a second aspect, alone or in combination with the first aspect, process 600 includes: sending a capability report to a network entity, the capability report indicating at least one of a first supported first time slot group size for the USS or a second supported time slot group size for the CSS, wherein the search space configuration is at least partially based on the capability report.

[0140] In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes receiving an indication of at least one of the first slot group size or the second slot group size from a network entity.

[0141] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication is included in at least one of an RRC communication or a system information communication.

[0142] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, a first blind decoding limit or a first CCE limit associated with monitoring a downlink control channel via a USS is based at least in part on a first time slot group size, and a second blind decoding limit or a second CCE limit associated with monitoring a downlink control channel via a CSS is based at least in part on a second time slot group size.

[0143] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first time slot group size is less than or equal to the second time slot group size.

[0144] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the second time slot group size is an integer multiple of the first time slot group size.

[0145] In an eighth aspect, alone or in combination with one or more of aspects 1 to 7, process 600 includes: allocating blind decoding or CCE for the CSS within a first number of time slots indicated by a second time slot group size to obtain a remaining blind decoding or CCE budget based at least in part on a first blind decoding limit or a first CCE limit, wherein the first blind decoding limit or the first CCE limit is based at least in part on the second time slot group size; and allocating blind decoding or CCE for the USS within the first number of time slots indicated by the second time slot group size based at least in part on the remaining blind decoding or CCE budget.

[0146] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, allocating blind decoding or CCE for USS comprises: allocating blind decoding or CCE for USS within a second number of time slots indicated by a first time slot group size, based at least in part on a blind decoding restriction or a CCE restriction, wherein the blind decoding restriction or the CCE restriction is based at least in part on the first time slot group size.

[0147] In a tenth aspect, alone or in combination with one or more of aspects 1 to 9, allocating blind decoding or CCE to USS includes: allocating blind decoding or CCE to a first USS set associated with a first configuration, and process 600 includes: monitoring a downlink control channel via the first USS set; and prohibiting monitoring of one or more USS sets associated with the first configuration based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding a remaining blind decoding or CCE budget within a first number of time slots.

[0148] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, one or more USS sets are identified based at least in part on index values ​​or identifiers associated with the one or more USS sets.

[0149] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, allocating blind decoding or CCE to USS includes: allocating blind decoding or CCE to one or more USS sets associated with the first configuration until the remaining blind decoding or CCE budget within the first number of time slots is met, and process 600 includes: monitoring the downlink control channel via one or more USS sets; and prohibiting monitoring of USS in any remaining USS sets associated with the first configuration based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0150] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, allocating blind decoding or CCE for USS includes: allocating a first part of blind decoding or CCE for the first set of time slots indicated by the first time slot group size for a first one or more USS sets associated with the first configuration within a first number of time slots indicated by the second time slot group size; and allocating a second part of blind decoding or CCE for the second set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size.

[0151] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the process 600 includes monitoring a downlink control channel via a first set of one or more USSs in a first set of time slots and a second set of time slots.

[0152] In a fifteenth aspect, alone or in combination with one or more of aspects one to fourteen, process 600 includes: prohibiting monitoring of a first one or more USS sets in a first set of time slots based at least in part on an index value or identifier associated with the first one or more USS sets and a number of blind decodings or CCEs associated with a first configuration exceeding a first portion of the blind decodings or CCEs; or prohibiting monitoring of a second one or more USS sets in a second set of time slots based at least in part on an index value or identifier associated with a second one or more USS sets and a number of blind decodings or CCEs associated with the first configuration exceeding a second portion of the blind decodings or CCEs.

[0153] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, allocating blind decoding or CCE for the USS includes: allocating blind decoding or CCE for a first set of time slots within a first number of time slots indicated by a second time slot group size, wherein the first set of time slots includes a second number of time slots indicated by the first time slot group size, and process 600 includes: monitoring a downlink control channel via the USS in the first set of time slots; and prohibiting monitoring of the USS in a second set of time slots based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding a remaining blind decoding or CCE budget within the first number of time slots, wherein the second set of time slots includes a second number of time slots.

[0154] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the UE identifies a second set of time slots based at least in part on a time domain location of a CSS measurement opportunity indicated by a second configuration.

[0155] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 600 includes: monitoring a downlink control channel via the CSS according to a search space configuration, and prohibiting monitoring of the downlink control channel via the USS based at least in part on the USS being configured in one or more time slot groups, wherein the one or more time slot groups overlap in the time domain with a time slot group associated with the CSS.

[0156] In a nineteenth aspect, alone or in combination with one or more of aspects one to eighteen, process 600 comprises: monitoring a downlink control channel via a USS according to a search space configuration, based at least in part on the fact that a CSS measurement opportunity is not configured in a first time slot group, wherein the first time slot group at least partially overlaps in time domain with a second time slot group associated with the USS.

[0157] although Figure 6 Example blocks of process 600 are shown, but in some aspects, process 600 may include Figure 6 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 600 may be performed in parallel.

[0158] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a network entity according to the present disclosure. Example process 700 is an example of a network entity (e.g., network entity 505, base station 110, CU, DU, and / or RU) performing operations associated with USS and CSS assignment for control channel monitoring based on multiple time slots.

[0159] like Figure 7 As shown, in some aspects, process 700 may include receiving a capability report associated with a UE, the capability report indicating at least one of a first supported first time slot group size for a USS or a second supported time slot group size for a CSS (block 710). For example, (e.g., using Fig. 9 The depicted communication manager 150 and / or receiving component 902) network entity may receive a capability report associated with the UE indicating at least one of a first supported first time slot group size for the USS or a second supported time slot group size for the CSS, as described above.

[0160] like Figure 7As further shown, in some aspects, process 700 may include sending a search space configuration for the UE, the search space configuration indicating a first configuration for USSs associated with a first slot group size and a second configuration for CSSs associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report (block 720). For example, (e.g., using Fig. 9 The depicted communication manager 150 and / or sending component 904) network entity may send a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with a first time slot group size and a second configuration for a CSS associated with a second time slot group size, wherein the search space configuration is based at least in part on the capability report, as described above.

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

[0162] In a first aspect, process 700 includes sending communications via a downlink control channel according to a search space configuration.

[0163] In a second aspect, either alone or in combination with the first aspect, process 700 includes sending an indication of at least one of the first time slot group size or the second time slot group size.

[0164] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication is included in at least one of an RRC communication or a system information communication.

[0165] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, a first blind decoding limit or a first CCE limit associated with monitoring a downlink control channel via a USS is based at least in part on a first time slot group size, and a second blind decoding limit or a second CCE limit associated with monitoring a downlink control channel via a CSS is based at least in part on a second time slot group size.

[0166] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first time slot group size is less than or equal to the second time slot group size.

[0167] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the second time slot group size is an integer multiple of the first time slot group size.

[0168] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 700 includes: allocating blind decoding or CCE for the CSS within a first number of time slots indicated by a second time slot group size to obtain a remaining blind decoding or CCE budget based at least in part on a first blind decoding limit or a first CCE limit, wherein the first blind decoding limit or the first CCE limit is based at least in part on the second time slot group size; and allocating blind decoding or CCE for the USS within the first number of time slots indicated by the second time slot group size based at least in part on the remaining blind decoding or CCE budget.

[0169] In an eighth aspect, alone or in combination with one or more of aspects 1 to 7, allocating blind decoding or CCE for USS includes: allocating blind decoding or CCE for USS within a second number of time slots indicated by a first time slot group size based at least in part on a blind decoding restriction or a CCE restriction, wherein the blind decoding restriction or the CCE restriction is based at least in part on the first time slot group size.

[0170] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, allocating blind decoding or CCE for USS includes: allocating blind decoding or CCE for a first USS set associated with a first configuration, and prohibiting transmission via one or more USS sets associated with the first configuration based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding a remaining blind decoding or CCE budget within a first number of time slots.

[0171] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more USS sets are identified based at least in part on index values ​​or identifiers associated with the one or more USS sets.

[0172] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, allocating blind decoding or CCE to USS includes: allocating blind decoding or CCE to one or more USS sets associated with a first configuration until a remaining blind decoding or CCE budget within a first number of time slots is met; and prohibiting transmission via USS in any remaining USS sets associated with the first configuration based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0173] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, allocating blind decoding or CCE for USS includes: allocating a first part of blind decoding or CCE for the first set of time slots indicated by the first time slot group size for a first one or more USS sets associated with the first configuration within a first number of time slots indicated by the second time slot group size; and allocating a second part of blind decoding or CCE for the second set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size.

[0174] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 700 includes: prohibiting transmission via the first one or more USS sets in the first time slot set based at least in part on an index value or identifier associated with the first one or more USS sets and the number of blind decodings or CCEs associated with the first configuration exceeds a first portion of the blind decodings or CCEs; or prohibiting transmission via the second one or more USS sets in the second time slot set based at least in part on an index value or identifier associated with the second one or more USS sets and the number of blind decodings or CCEs associated with the first configuration exceeds a second portion of the blind decodings or CCEs.

[0175] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, allocating blind decoding or CCE for the USS includes: allocating blind decoding or CCE for a first set of time slots within a first number of time slots indicated by a second time slot group size, wherein the first set of time slots includes a second number of time slots indicated by the first time slot group size; and prohibiting transmission via the USS in a second set of time slots based at least in part on the number of blind decoding or CCE associated with the first configuration exceeding a remaining blind decoding or CCE budget within the first number of time slots, wherein the second set of time slots includes a second number of time slots.

[0176] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, a second set of time slots is identified based at least in part on time domain locations of CSS measurement opportunities indicated by a second configuration.

[0177] In a sixteenth aspect, either alone or in combination with one or more of aspects one to fifteen, process 700 comprises: prohibiting transmission using a downlink control channel via the USS based at least in part on the USS being configured in one or more time slot groups, wherein the one or more time slot groups overlap in the time domain with a time slot group associated with the CSS.

[0178] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 700 includes: at least in part based on the fact that no CSS measurement opportunity is configured in a first time slot group, sending one or more signals using a downlink control channel via the USS according to the search space configuration, wherein the first time slot group at least partially overlaps in the time domain with a second time slot group associated with the USS.

[0179] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 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 700 may be performed in parallel.

[0180] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include one or more of a monitoring component 808, an allocation component 810, or a search space discarding component 812, etc.

[0181] In some aspects, the apparatus 800 may be configured to perform FIG. 5A to FIG. 5G Additionally or alternatively, the apparatus 800 may be configured to perform one or more of the processes described herein (such as Figure 6 In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally 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.

[0182] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 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.

[0183] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 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 806. In some aspects, the transmitting component 804 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 804 can be co-located with the receive component 802 in a transceiver.

[0184] Receiving component 802 can receive a search space configuration from a network entity, the search space configuration indicating a first configuration for USSs associated with a first slot group size and a second configuration for CSSs associated with a second slot group size. Receiving component 802 can receive communications from the network entity via the downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0185] Monitoring component 808 can monitor the downlink control channel according to the search space configuration via at least one of the USS or the CSS.

[0186] Transmitting component 804 can transmit a capability report to a network entity indicating at least one of a first supported first slot group size for the USS or a second supported slot group size for the CSS, wherein the search space configuration is based at least in part on the capability report.

[0187] Receiving component 802 can receive an indication of at least one of the first time slot group size or the second time slot group size from a network entity.

[0188] The allocation component 810 can allocate blind decoding or CCE for the CCS within a first number of time slots indicated by a second time slot group size to obtain a remaining blind decoding or CCE budget, at least in part based on a first blind decoding limit or a first CCE limit, wherein the first blind decoding limit or the first CCE limit is at least in part based on the second time slot group size.

[0189] Allocating component 810 can allocate blind decoding or CCEs for the USS within a first number of slots indicated by a second slot group size based at least in part on a remaining blind decoding or CCE budget.

[0190] Monitoring component 808 can monitor a downlink control channel via first one or more sets of USSs in the first set of time slots and the second set of time slots.

[0191] Search space discarding component 812 can refrain from monitoring USSs for a second set of one or more USSs in the first set of time slots based at least in part on a number of blind decodes or CCEs associated with the first configuration exceeding a first portion of the blind decodes or CCEs.

[0192] Search space discarding component 812 can refrain from monitoring USSs for a third set of one or more USSs in the second set of time slots based at least in part on a number of blind decodes or CCEs associated with the first configuration exceeding a second portion of the blind decodes or CCEs.

[0193] Monitoring component 808 can monitor the downlink control channel via the CSS according to the search space configuration.

[0194] Search space discarding component 812 can refrain from monitoring a downlink control channel via the USS based at least in part on the USS being configured in one or more time slot groups that overlap in the time domain with a time slot group associated with the CSS.

[0195] Monitoring component 808 can monitor a downlink control channel according to a search space configuration via the USS based at least in part on not configuring a CSS measurement opportunity in a first group of time slots that at least partially overlaps in time domain with a second group of time slots associated with the USS.

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

[0197] Fig. 9 900 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a network entity, or a network entity may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include one or more of an allocating component 908 and / or a disabling component 910, among others.

[0198] In some aspects, the apparatus 900 may be configured to perform FIG. 5A to FIG. 5G Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein (such as Figure 7 In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally 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.

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

[0200] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 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 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entity. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0201] Receiving component 902 can receive a capability report associated with a UE, the capability report indicating at least one of a first supported first slot group size for a USS or a second supported slot group size for a CSS. Sending component 904 can send a search space configuration for the UE, the search space configuration indicating a first configuration for a USS associated with the first slot group size and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report.

[0202] Transmitting component 904 can transmit communications via a downlink control channel in accordance with the search space configuration.

[0203] Transmitting component 904 can transmit an indication of at least one of the first slot group size or the second slot group size.

[0204] The allocating component 908 can allocate blind decoding or CCE for the CCS within a first number of time slots indicated by the second time slot group size to obtain a remaining blind decoding or CCE budget based at least in part on a first blind decoding limit or a first CCE limit, wherein the first blind decoding limit or the first CCE limit is based at least in part on the second time slot group size.

[0205] Allocating component 908 can allocate blind decoding or CCEs for the USS within a first number of slots indicated by a second slot group size based at least in part on a remaining blind decoding or CCE budget.

[0206] The disabling component 910 can disabling transmission via USSs for a second set of one or more USSs in the first set of time slots based at least in part on a number of blind decodes or CCEs associated with the first configuration exceeding a first portion of the blind decodes or CCEs.

[0207] The disabling component 910 can disabling transmission via the USS for a third set of one or more USSs in the second set of time slots based at least in part on a number of blind decodes or CCEs associated with the first configuration exceeding a second portion of the blind decodes or CCEs.

[0208] The prohibiting component 910 can prohibit transmission using the downlink control channel via the USS based at least in part on the USS being configured in one or more time slot groups that overlap in the time domain with a time slot group associated with the CSS.

[0209] The sending component 904 can send one or more signals using a downlink control channel according to the search space configuration via the USS based at least in part on the fact that no CSS measurement opportunity is configured in the first time slot group, wherein the first time slot group at least partially overlaps with a second time slot group associated with the USS in the time domain.

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

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

[0212] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for a UE-specific search space (USS) associated with a first slot group size, and a second configuration for a common search space (CSS) associated with a second slot group size, and receiving a communication from the network entity via a downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

[0213] Aspect 2: According to the method of aspect 1, the method further includes: monitoring the downlink control channel according to the search space configuration via at least one of the USS or the CSS.

[0214] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: sending a capability report to the network entity, the capability report indicating at least one of a first supported time slot group size for USS or a second supported time slot group size for CSS, wherein the search space configuration is at least partially based on the capability report.

[0215] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: receiving an indication of at least one of the first time slot group size or the second time slot group size from the network entity.

[0216] Aspect 5: The method according to aspect 4, wherein the indication is included in at least one of a radio resource control (RRC) communication or a system information communication.

[0217] Aspect 6: A method according to any one of Aspects 1 to 5, wherein a first blind decoding limit or a first control channel element (CCE) limit associated with monitoring the downlink control channel via the USS is at least partially based on the first time slot group size, and wherein a second blind decoding limit or a second CCE limit associated with monitoring the downlink control channel via the CSS is at least partially based on the second time slot group size.

[0218] Aspect 7: The method according to any one of aspects 1 to 6, wherein the first time slot group size is less than or equal to the second time slot group size.

[0219] Aspect 8: The method according to any one of aspects 1 to 7, wherein the second time slot group size is an integer multiple of the first time slot group size.

[0220] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: allocating blind decoding or CCE for the CCS within a first number of time slots indicated by the second time slot group size to obtain a remaining blind decoding or CCE budget, at least in part based on a first blind decoding restriction or a first control channel element (CCE) restriction, wherein the first blind decoding restriction or the first CCE restriction is at least in part based on the second time slot group size; and allocating blind decoding or CCE for the USS within the first number of time slots indicated by the second time slot group size based at least in part on the remaining blind decoding or CCE budget.

[0221] Aspect 10: A method according to Aspect 9, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to the USS within a second number of time slots indicated by the first time slot group size, at least in part based on a blind decoding restriction or a CCE restriction, wherein the blind decoding restriction or the CCE restriction is at least in part based on the first time slot group size.

[0222] Aspect 11: A method according to any one of Aspects 9 to 10, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to a first USS set associated with the first configuration; and wherein the method also includes: monitoring the downlink control channel via the first USS set; and prohibiting monitoring of one or more USS sets associated with the first configuration based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0223] Aspect 12: The method according to aspect 11, wherein the one or more USS sets are identified based at least in part on an index value or identifier associated with the one or more USS sets.

[0224] Aspect 13: A method according to any one of Aspects 9 to 12, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to one or more USS sets associated with the first configuration until the remaining blind decoding or CCE budget within the first number of time slots is met; and wherein the method also includes: monitoring the downlink control channel via the one or more USS sets; and prohibiting monitoring of the USS in any remaining USS sets associated with the first configuration based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0225] Aspect 14: A method according to any one of Aspects 9 to 13, wherein allocating the blind decoding or the CCE for the USS includes: allocating a first part of the blind decoding or the CCE for the first set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size; and allocating a second part of the blind decoding or the CCE for the second set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size.

[0226] Aspect 15: The method according to aspect 14, the method further comprising: monitoring the downlink control channel via the first one or more USS sets in the first time slot set and the second time slot set.

[0227] Aspect 16: According to the method described in any one of Aspects 14 to 15, the method further includes: prohibiting monitoring of the first one or more USS sets in the first time slot set at least in part based on the index value or identifier associated with the first one or more USS sets and the number of blind decodings or CCEs associated with the first configuration exceeding the first part of the blind decodings or CCEs; or prohibiting monitoring of the second one or more USS sets in the second time slot set at least in part based on the index value or identifier associated with the second one or more USS sets and the number of blind decodings or CCEs associated with the first configuration exceeding the second part of the blind decodings or CCEs.

[0228] Aspect 17: A method according to any one of Aspects 9 to 16, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to a first time slot set within the first number of time slots indicated by the second time slot group size, wherein the first time slot set includes a second number of time slots indicated by the first time slot group size; and wherein the method also includes: monitoring the downlink control channel via the USS in the first time slot set; and prohibiting monitoring the USS in a second time slot set based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots, wherein the second time slot set includes the second number of time slots.

[0229] Aspect 18: The method according to aspect 17, wherein the UE identifies the second set of time slots based at least in part on the time domain location of the CSS measurement occasion indicated by the second configuration.

[0230] Aspect 19: According to the method described in any one of Aspects 1 to 18, the method further includes: monitoring the downlink control channel via the CSS according to the search space configuration; and prohibiting monitoring the downlink control channel via the USS at least in part based on the USS being configured in one or more time slot groups, wherein the one or more time slot groups overlap with the time slot group associated with the CSS in the time domain.

[0231] Aspect 20: According to the method described in any one of Aspects 1 to 19, the method further includes: monitoring the downlink control channel according to the search space configuration via the USS, at least in part based on the fact that a CSS measurement opportunity is not configured in a first time slot group, wherein the first time slot group at least partially overlaps with a second time slot group associated with the USS in the time domain.

[0232] Aspect 21: A method of wireless communication performed by a network entity, the method comprising: receiving a capability report associated with a user equipment (UE), the capability report indicating at least one of a first supported time slot group size for a UE-specific search space (USS) or a second supported time slot group size for a common search space (CSS); and sending a search space configuration for the UE, the search space configuration indicating a first configuration for the USS associated with the first time slot group size, and a second configuration for the CSS associated with a second time slot group size, wherein the search space configuration is at least partially based on the capability report.

[0233] Aspect 22: The method according to aspect 21, the method further comprising: sending communication via a downlink control channel according to the search space configuration.

[0234] Aspect 23: The method according to any one of aspects 21 to 22, further comprising: sending an indication of at least one of the first time slot group size or the second time slot group size.

[0235] Aspect 24: The method according to aspect 23, wherein the indication is included in at least one of a radio resource control (RRC) communication or a system information communication.

[0236] Aspect 25: A method according to any one of Aspects 21 to 24, wherein a first blind decoding limit or a first control channel element (CCE) limit associated with monitoring a downlink control channel via the USS is at least partially based on the first time slot group size, and wherein a second blind decoding limit or a second CCE limit associated with monitoring a downlink control channel via the CSS is at least partially based on the second time slot group size.

[0237] Aspect 26: The method according to any one of Aspects 21 to 25, wherein the first time slot group size is less than or equal to the second time slot group size.

[0238] Aspect 27: The method according to any one of Aspects 21 to 26, wherein the second time slot group size is an integer multiple of the first time slot group size.

[0239] Aspect 28: According to the method described in any one of Aspects 21 to 27, the method further includes: allocating blind decoding or CCE for the CCS within a first number of time slots indicated by the second time slot group size to obtain a remaining blind decoding or CCE budget, at least in part based on a first blind decoding restriction or a first control channel element (CCE) restriction, wherein the first blind decoding restriction or the first CCE restriction is at least in part based on the second time slot group size; and allocating blind decoding or CCE for the USS within the first number of time slots indicated by the second time slot group size based at least in part on the remaining blind decoding or CCE budget.

[0240] Aspect 29: A method according to Aspect 28, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to the USS within a second number of time slots indicated by the first time slot group size based at least in part on a blind decoding restriction or a CCE restriction, wherein the blind decoding restriction or the CCE restriction is based at least in part on the first time slot group size.

[0241] Aspect 30: A method according to any one of Aspects 28 to 29, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to a first USS set associated with the first configuration; and prohibiting transmission via one or more USS sets associated with the first configuration based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0242] Aspect 31: The method according to aspect 30, wherein the one or more USS sets are identified based at least in part on an index value or identifier associated with the one or more USS sets.

[0243] Aspect 32: A method according to any one of Aspects 28 to 31, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to one or more USS sets associated with the first configuration until the remaining blind decoding or CCE budget within the first number of time slots is met; and prohibiting transmission via the USS in any remaining USS set associated with the first configuration based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots.

[0244] Aspect 33: A method according to any one of Aspects 28 to 32, wherein allocating the blind decoding or the CCE for the USS includes: allocating a first part of the blind decoding or the CCE for the first set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size; and allocating a second part of the blind decoding or the CCE for the second set of time slots indicated by the first time slot group size for the first one or more USS sets associated with the first configuration within the first number of time slots indicated by the second time slot group size.

[0245] Aspect 34: According to the method of Aspect 33, the method also includes: prohibiting transmission via the USS for a second one or more USS sets in the first time slot set at least in part based on the number of blind decodings or CCEs associated with the first configuration exceeding the first part of the blind decodings or CCEs; or prohibiting transmission via the USS for a third one or more USS sets in the second time slot set at least in part based on the number of blind decodings or CCEs associated with the first configuration exceeding the second part of the blind decodings or CCEs.

[0246] Aspect 35: A method according to any one of Aspects 28 to 34, wherein allocating the blind decoding or the CCE to the USS includes: allocating the blind decoding or the CCE to a first time slot set within the first number of time slots indicated by the second time slot group size, wherein the first time slot set includes a second number of time slots indicated by the first time slot group size; and prohibiting transmission via the USS in a second time slot set based at least in part on the number of blind decodings or CCEs associated with the first configuration exceeding the remaining blind decoding or CCE budget within the first number of time slots, wherein the second time slot set includes the second number of time slots.

[0247] Aspect 36: The method according to aspect 35, wherein the second set of time slots is identified based at least in part on the time domain location of the CSS measurement occasion indicated by the second configuration.

[0248] Aspect 37: According to any one of Aspects 21 to 36, the method further includes: prohibiting the use of a downlink control channel for transmission via the USS, at least in part based on the USS being configured in one or more time slot groups, wherein the one or more time slot groups overlap in the time domain with a time slot group associated with the CSS.

[0249] Aspect 38: According to the method described in any one of Aspects 21 to 37, the method further includes: at least in part based on the fact that no CSS measurement opportunity is configured in the first time slot group, sending one or more signals using a downlink control channel via the USS according to the search space configuration, wherein the first time slot group at least partially overlaps with a second time slot group associated with the USS in the time domain.

[0250] Aspect 39: 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 20.

[0251] Aspect 40: A device for wireless communication, the device comprising: a memory; and one or more processors, the 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 20.

[0252] Aspect 41: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 20.

[0253] Aspect 42: 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 20.

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

[0255] Aspect 44: 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 21 to 38.

[0256] Aspect 45: A device for wireless communication, the device comprising: a memory; and one or more processors, the 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 21 to 38.

[0257] Aspect 46: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 21 to 38.

[0258] Aspect 47: 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 21 to 38.

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

[0260] 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 these aspects.

[0261] 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, processes 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, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, 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.

[0262] 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.

[0263] Although specific combinations of features are 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 (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, 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).

[0264] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. 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 you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for a UE-specific search space (USS) associated with a first slot group size and a second configuration for a common search space (CSS) associated with a second slot group size; and Communications are received from the network entity via the downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

2. The UE of claim 1, wherein the one or more processors are further configured to: The downlink control channel is monitored according to the search space configuration via at least one of the USS or the CSS.

3. The UE of claim 1 , wherein the one or more processors are further configured to: sending a capability report to the network entity, the capability report indicating at least one of a first supported first time slot group size for a USS or a second supported time slot group size for a CSS, Wherein the search space configuration is based at least in part on the capability report.

4. A UE according to claim 1, wherein a first blind decoding limit or a first control channel element (CCE) limit associated with monitoring the downlink control channel via the USS is at least partially based on the first time slot group size, and wherein a second blind decoding limit or a second CCE limit associated with monitoring the downlink control channel via the CSS is at least partially based on the second time slot group size.

5. The UE of claim 1, wherein the first time slot group size is less than or equal to the second time slot group size.

6. The UE of claim 1, wherein the one or more processors are further configured to: allocating blind decodes or CCEs for the CCS within a first number of slots indicated by the second slot group size to obtain a remaining blind decode or CCE budget based at least in part on a first blind decode limit or a first control channel element (CCE) limit, wherein the first blind decode limit or the first CCE limit is based at least in part on the second slot group size; and Based at least in part on the remaining blind decoding or CCE budget, blind decoding or CCEs are allocated for the USS within the first number of time slots indicated by the second time slot group size.

7. The UE of claim 6, wherein in order to allocate the blind decoding or the CCE for the USS, the one or more processors are configured to: The blind decoding or CCEs are allocated for the USS within a second number of time slots indicated by the first time slot group size based at least in part on a blind decoding limit or a CCE limit based at least in part on the first time slot group size.

8. The UE of claim 6, wherein in order to allocate the blind decoding or the CCE for the USS, the one or more processors are configured to: allocating the blind decoding or the CCE for one or more USS sets associated with the first configuration until the remaining blind decoding or CCE budget within the first number of time slots is met; and wherein the one or more processors are further configured to: monitoring the downlink control channel via the one or more sets of USSs; and Based at least in part on the number of blind decodes or CCEs associated with the first configuration exceeding the remaining blind decode or CCE budget within the first number of time slots, refraining from monitoring the USS in any remaining set of USSs associated with the first configuration.

9. The UE of claim 6, wherein in order to allocate the blind decoding or the CCE for the USS, the one or more processors are configured to: allocating, for a first one or more sets of USSs associated with the first configuration, a first portion of the blind decodings or the CCEs for a first set of slots indicated by the first set of slots indicated by the second set of slots size within the first number of slots indicated by the second set of slots group size; and A second portion of the blind decodings or the CCEs for a second set of slots indicated by the first slot group size are allocated for the first one or more sets of USSs associated with the first configuration within the first number of slots indicated by the second slot group size.

10. The UE of claim 6, wherein in order to allocate the blind decoding or the CCE for the USS, the one or more processors are configured to: allocating the blind decoding or the CCE for a first set of time slots within the first number of time slots indicated by the second time slot group size, wherein the first set of time slots includes the second number of time slots indicated by the first time slot group size; and wherein the one or more processors are further configured to: monitoring the downlink control channel via the USS in the first set of time slots; and Based at least in part on the number of blind decodes or CCEs associated with the first configuration exceeding the remaining blind decode or CCE budget within the first number of time slots, refraining from monitoring the USS in a second set of time slots, wherein the second set of time slots includes the second number of time slots.

11. The UE of claim 10, wherein the UE identifies the second set of time slots based at least in part on a time domain location of a CSS measurement opportunity indicated by the second configuration.

12. The UE of claim 1, wherein the one or more processors are further configured to: monitoring the downlink control channel according to the search space configuration via the CSS; and Monitoring of the downlink control channel via the USS is prohibited based at least in part on the USS being configured in one or more time slot groups that overlap in time domain with a time slot group associated with the CSS.

13. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a capability report associated with a user equipment (UE), the capability report indicating at least one of a first supported first slot group size for a UE-specific search space (USS) or a second supported slot group size for a common search space (CSS); and A search space configuration is transmitted for the UE, the search space configuration indicating a first configuration for USSs associated with a first slot group size and a second configuration for CSSs associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report.

14. The network entity of claim 13, wherein the one or more processors are further configured to: Communications are sent via a downlink control channel according to the search space configuration.

15. The network entity of claim 13, wherein the one or more processors are further configured to: An indication of at least one of the first time slot group size or the second time slot group size is sent.

16. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a search space configuration from a network entity, the search space configuration indicating a first configuration for a UE-specific search space (USS) associated with a first slot group size and a second configuration for a common search space (CSS) associated with a second slot group size; and Communications are received from the network entity via the downlink control channel based at least in part on monitoring a downlink control channel according to the search space configuration.

17. The method according to claim 16, further comprising: The downlink control channel is monitored according to the search space configuration via at least one of the USS or the CSS.

18. The method according to claim 16, further comprising: sending a capability report to the network entity, the capability report indicating at least one of a first supported first time slot group size for a USS or a second supported time slot group size for a CSS, Wherein the search space configuration is based at least in part on the capability report.

19. The method according to claim 16, further comprising: An indication of at least one of the first time slot group size or the second time slot group size is received from the network entity.

20. The method of claim 16, wherein a first blind decoding limit or a first control channel element (CCE) limit associated with monitoring the downlink control channel via the USS is based at least in part on the first time slot group size, and Wherein a second blind decoding limit or a second CCE limit associated with monitoring the downlink control channel via the CSS is based at least in part on the second time slot group size.

21. The method according to claim 16, further comprising: allocating blind decodes or CCEs for the CCS within a first number of slots indicated by the second slot group size to obtain a remaining blind decode or CCE budget based at least in part on a first blind decode limit or a first control channel element (CCE) limit, wherein the first blind decode limit or the first CCE limit is based at least in part on the second slot group size; and Based at least in part on the remaining blind decoding or CCE budget, blind decoding or CCEs are allocated for the USS within the first number of time slots indicated by the second time slot group size.

22. The method according to claim 21, wherein allocating the blind decoding or the CCE for the USS comprises: allocating the blind decoding or the CCE for a first USS set associated with the first configuration; and The method further comprises: monitoring the downlink control channel via the first set of USSs; as well as Based at least in part on the number of blind decodes or CCEs associated with the first configuration exceeding the remaining blind decode or CCE budget within the first number of time slots, one or more sets of USSs associated with the first configuration are prohibited from monitoring.

23. The method of claim 22, wherein the one or more USS sets are identified based at least in part on an index value or identifier associated with the one or more USS sets.

24. The method according to claim 21, wherein allocating the blind decoding or the CCE for the USS comprises: allocating the blind decoding or the CCE for one or more USS sets associated with the first configuration until the remaining blind decoding or CCE budget within the first number of time slots is satisfied; and The method further comprises: monitoring the downlink control channel via the one or more sets of USSs; as well as Based at least in part on the number of blind decodes or CCEs associated with the first configuration exceeding the remaining blind decode or CCE budget within the first number of time slots, refraining from monitoring the USS in any remaining set of USSs associated with the first configuration.

25. The method according to claim 21, wherein allocating the blind decoding or the CCE for the USS comprises: allocating, for a first set of one or more USSs associated with the first configuration, a first portion of the blind decodings or the CCEs for a first set of slots indicated by the first slot group size, within the first number of slots indicated by the second slot group size; as well as A second portion of the blind decodings or the CCEs for a second set of slots indicated by the first slot group size are allocated for the first one or more sets of USSs associated with the first configuration within the first number of slots indicated by the second slot group size.

26. The method according to claim 25, further comprising: The downlink control channel is monitored via the first one or more sets of USSs in the first set of time slots and the second set of time slots.

27. The method according to claim 25, further comprising: refraining from monitoring the first one or more sets of USSs in the first set of time slots based at least in part on the index value or identifier associated with the first one or more sets of USSs and the number of the blind decodes or CCEs associated with the first configuration exceeds the first portion of the blind decodes or CCEs; or Based at least in part on the index value or identifier associated with the second one or more sets of USSs and the number of the blind decodings or CCEs associated with the first configuration exceeding the second portion of the blind decodings or CCEs, monitoring of the second one or more sets of USSs in the second set of time slots is prohibited.

28. The method of claim 16, further comprising: monitoring, via the CSS, the downlink control channel according to the search space configuration; as well as Monitoring of the downlink control channel via the USS is prohibited based at least in part on the USS being configured in one or more time slot groups that overlap in time domain with a time slot group associated with the CSS.

29. A method of wireless communication performed by a network entity, the method comprising: receiving a capability report associated with a user equipment (UE), the capability report indicating at least one of a first supported first slot group size for a UE-specific search space (USS) or a second supported slot group size for a common search space (CSS); and A search space configuration is sent for the UE, the search space configuration indicating a first configuration for a USS associated with a first slot group size and a second configuration for a CSS associated with a second slot group size, wherein the search space configuration is based at least in part on the capability report.

30. The method according to claim 29, further comprising: Communications are sent via a downlink control channel according to the search space configuration.

Images