CN117397195A

CN117397195A - Search space sharing for cross-carrier scheduling

Info

Publication number: CN117397195A
Application number: CN202280037219.1A
Authority: CN
Inventors: K·竹田; P·加尔; 徐慧琳; M·霍什内维桑
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-06-04
Filing date: 2022-06-02
Publication date: 2024-01-12

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a mobile station may transmit a capability indication identifying search space sharing capability of the mobile station on a scheduling cell. The mobile station may monitor a first set of Physical Downlink Control Channel (PDCCH) monitoring occasions on the scheduling cell that schedule the scheduled cell and a second set of PDCCH monitoring occasions on the scheduling cell. Several other aspects are described.

Description

Search space sharing for cross-carrier scheduling

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application Ser. No.63/202,297, entitled "SEARCH SPACE SHARING FOR CROSS-CARRIER SCHEDULING", filed on 4 th month 2021, and U.S. non-provisional patent application Ser. No.17/804,969, entitled "SEARCH SPACE SHARING FOR CROSS-CARRIER SCHEDULING", filed on 1 th month 2022, which are assigned to the assignee of the present application. The disclosures of these prior applications are considered to be part of the present patent application and are incorporated by reference into the present patent application.

Technical Field

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatuses for search space sharing across carrier scheduling.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-advanced is an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP).

A wireless network may include one or more base stations that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink and uplink communications. "downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

The above multiple access techniques have been employed in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and/or global level. The New Radio (NR), which may be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better integrate with other open standards by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), to better support mobile broadband internet access, as well as support beamforming, multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR and other radio access technologies remain useful.

Disclosure of Invention

In some aspects, a method of wireless communication performed by a mobile station includes: transmitting, by the mobile station, a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and monitoring, by the mobile station, a first set of Physical Downlink Control Channel (PDCCH) monitoring occasions of scheduling a scheduled cell and a second set of PDCCH monitoring occasions of scheduling the scheduling cell on the scheduling cell.

In some aspects, a method of wireless communication performed by a network entity comprises: receiving, by the network entity, a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and transmitting, by the network entity, a first set of PDCCH communications scheduling the scheduled cell and a second set of PDCCH communications scheduling the scheduling cell on the scheduling cell.

In some aspects, a mobile station for wireless communication includes: a memory and one or more processors coupled to the memory, the one or more processors configured to: transmitting a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and monitoring a first set of PDCCH monitoring occasions of a scheduled cell and a second set of PDCCH monitoring occasions of the scheduled cell on the scheduling cell.

In some aspects, a network entity for wireless communication comprises: a memory and one or more processors coupled to the memory, the one or more processors configured to: receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and transmitting a first PDCCH communication set of a scheduled cell and a second PDCCH communication set of the scheduled cell on the scheduling cell.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a mobile station, cause the mobile station to: transmitting a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and monitoring a first set of PDCCH monitoring occasions of a scheduled cell and a second set of PDCCH monitoring occasions of the scheduled cell on the scheduling cell.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network entity, cause the network entity to: receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and transmitting a first PDCCH communication set of a scheduled cell and a second PDCCH communication set of the scheduled cell on the scheduling cell.

In some aspects, an apparatus for wireless communication comprises: means for sending a capability indication identifying search space sharing capability of the apparatus on a scheduling cell; and means for monitoring, on the scheduling cell, a first set of PDCCH monitoring occasions that schedule the scheduled cell and a second set of PDCCH monitoring occasions that schedule the scheduling cell.

In some aspects, an apparatus for wireless communication comprises: means for receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and means for transmitting, on the scheduling cell, a first PDCCH communication set scheduling the scheduled cell and a second PDCCH communication set scheduling the scheduling cell.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user device, base station, network node, network entity, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with the associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for purposes of illustration and description and is not intended as a definition of the limits of the claims.

While aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that such aspects may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, aspects may be implemented via integrated chip embodiments or other non-module component based devices (e.g., end user devices, vehicles, communications devices, computing devices, industrial devices, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. 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). Aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements, and/or end user devices of different sizes, shapes, and configurations.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a schematic diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a schematic diagram illustrating an example of a base station in a wireless network in communication with a User Equipment (UE) in accordance with the present disclosure.

Fig. 3 is a schematic diagram illustrating an example of a resource structure for wireless communication according to the present disclosure.

Fig. 4 is a schematic diagram illustrating an example of cross-carrier scheduling according to the present disclosure.

Fig. 5A-5B are diagrams illustrating examples associated with search space sharing for cross-carrier scheduling in accordance with the present disclosure.

Fig. 6-7 are diagrams illustrating example processes associated with search space sharing for cross-carrier scheduling in accordance with the present disclosure.

Fig. 8-9 are block diagrams of example apparatuses for wireless communication according to the present disclosure.

Fig. 10 is a schematic diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.

Detailed Description

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It will be apparent to those skilled in the art that the scope of the present disclosure is intended to encompass any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is implemented with other structures, functions, or structures and functions that are alternatives to or complements of 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.

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

Although aspects may be described herein using terms commonly associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a schematic diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, among other examples. Wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Base station 110 is the entity in communication with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or transmit-receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can 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.

The base station 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 having an association with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, BS110a may be a macro base station for macro cell 102a, BS110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells.

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 moving base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected with each other and/or with one or more other base stations 110 or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that receives a transmission of data from an upstream station (e.g., base station 110 or UE 120) and sends a transmission of data to a downstream station (e.g., UE 120 or base station 110). The relay station may be a UE 120 that may relay transmissions for other UEs 120. In the example shown in fig. 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE 120d in order to facilitate communications between BS110a and UE 120 d. The base station 110 relaying communications may also be referred to as a relay station, a relay base station, a relay, etc.

The wireless network 100 may be a heterogeneous network including 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 impact on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).

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 these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. Base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.

UEs 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 mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, a super-book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or 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 device, a global positioning system device, and/or any other suitable device configured to communicate via a wireless medium.

Some UEs 120 may be considered 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, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. 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., memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, etc. Frequencies may also be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographical area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120 e) may communicate directly using one or more side-uplink channels (e.g., without using base station 110 as an intermediary in communicating with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. 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.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is commonly (interchangeably) referred to as the "Sub-6 GHz" band in various documents and articles. Similar naming problems sometimes occur for FR2, which is commonly referred to (interchangeably) in various documents and articles as the "millimeter wave" band, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) defined by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequencies between FR1 and FR2 are commonly referred to as mid-band frequencies. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above examples, unless explicitly stated otherwise, it should be understood that the term "sub-6GHz" and the like (if used herein) may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly mean frequencies that may include mid-band frequencies, may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band. It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4-a, FR4-1, and/or FR 5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

In some aspects, a mobile station, which may correspond to UE 120 described herein, may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: transmitting a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and monitoring, on a scheduling cell, a first set of Physical Downlink Control Channel (PDCCH) monitoring occasions that schedule the scheduled cell and a second set of PDCCH monitoring occasions that schedule the scheduling cell. In some aspects, UE 120 may receive Downlink Control Information (DCI) in a PDCCH monitoring occasion. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, the base station 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and transmitting a first PDCCH communication set of a scheduled cell and a second PDCCH communication set of the scheduled cell on a scheduling cell. In some aspects, the base station 110 may transmit DCI in a PDCCH communication. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

Fig. 2 is a schematic diagram illustrating an example 200 of a base station 110 in a wireless network 100 in communication with a UE 120 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234T, such as T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, such as R antennas (r≡1).

At base station 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning 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)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and/or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232T). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232T may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234T).

At UE 120, a set of antennas 252 (shown as antennas 252a through 252R) may receive downlink signals from base station 110 and/or other base stations 110 and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254R). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator assembly to condition (e.g., filter, amplify, downconvert, and/or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to a 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 others. In some examples, one or more components of UE 120 may be included in housing 284.

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

The one or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in 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. The antenna panel, antenna group, set of antenna elements, and/or antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmit and/or receive components (such as one or more components in fig. 2).

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

At base station 110, uplink signals from UE 120 and/or other UEs may be received by antennas 234, processed by modems 232 (e.g., the demodulator components of modems 232, shown as DEMODs), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a 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. Base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 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., with reference to fig. 5A-9).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other components in fig. 2 may perform one or more techniques associated with search space sharing for cross-carrier scheduling, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations of process 600 of fig. 6, process 700 of fig. 7, and/or 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 by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compilation, conversion, and/or interpretation), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, and/or other processes as described herein. In some examples, the execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions, among others.

In some aspects, a mobile station includes: means for transmitting a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and/or means for monitoring, on the scheduling cell, a first set of PDCCH monitoring occasions of the scheduling cell and a second set of PDCCH monitoring occasions of the scheduling cell. In some aspects, means for a mobile station to perform the operations described herein may comprise, for example, one or more of the communication manager 140, the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller/processor 280, or the memory 282.

In some aspects, a base station includes: means for receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and/or means for transmitting, on the scheduling cell, a first PDCCH communication set scheduling the scheduled cell and a second PDCCH communication set scheduling the scheduling cell. The means for a base station to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Although the blocks in fig. 2 are shown as distinct components, the functionality described above for the blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by controller/processor 280 or under the control of controller/processor 280.

As indicated above, fig. 2 is provided as an example. Other examples may differ from the example described with respect to fig. 2.

Fig. 3 is a schematic diagram illustrating an example resource structure 300 for wireless communication in accordance with the present disclosure. Resource structure 300 illustrates an example of various resource groups described herein. As shown, the resource structure 300 may include a subframe 305. The subframe 305 may include a plurality of slots 310. Although resource structure 300 is shown as including 2 slots per subframe, a different number of slots (e.g., 4 slots, 8 slots, 16 slots, or 32 slots, or another number of slots) may be included in a subframe. In some aspects, different types of Transmission Time Intervals (TTIs) other than subframes and/or slots may be used. The slot 310 may include a plurality of symbols 315, such as 14 symbols per slot.

The potential control region of the slot 310 may be referred to as a control resource set (CORESET) 320 and may be structured to support efficient use of resources, such as by flexibly configuring or reconfiguring the CORESET 320 for one or more PDCCHs, and/or the resources of one or more Physical Downlink Shared Channels (PDSCH). In some aspects, CORESET 320 may occupy a first symbol 315 of slot 310, the first two symbols 315 of slot 310, or the first three symbols 315 of slot 310. Accordingly, CORESET 320 may include a plurality of Resource Blocks (RBs) in the frequency domain, as well as one, two, or three symbols 315 in the time domain. In 5G, the number of resources included in CORESET 320 may be flexibly configured, for example, by using Radio Resource Control (RRC) signaling to indicate a frequency domain region (e.g., the number of resource blocks) and/or a time domain region (e.g., the number of symbols) for CORESET 320.

As shown, symbols 315 comprising CORESET 320 may include one or more Control Channel Elements (CCEs) 325 (shown as two CCEs 325, as an example) that span a portion of the system bandwidth. CCE 325 may include DCI for providing control information for wireless communication. The network entity may transmit DCI (as shown) during a plurality of CCEs 325, where the number of CCEs 325 used to transmit the DCI represents an Aggregation Level (AL) used by the BS to transmit the DCI. In fig. 3, an aggregation level of two is shown as an example, corresponding to two CCEs 325 in a slot 310. In some aspects, a different aggregation level may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

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 bundling size. REG 330 may include one resource block, which may include 12 Resource Elements (REs) 335 within symbol 315. The resource element 335 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

The search space may include all possible locations (e.g., in time and/or frequency) where the PDCCH may be located. CORESET 320 may include one or more search spaces, such as a UE-specific search space, a group public search space, and/or a public search space. The search space may indicate a set of CCE locations in which the UE may find a PDCCH that can potentially be used to send control information to the UE. The possible locations of the 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 used. The possible locations (e.g., in time and/or frequency) of the PDCCH 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 across 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 Set of Search Spaces (SSs).

CORESET 320 may be interleaved or non-interleaved. The interleaved CORESET 320 may have CCE-to-REG mappings such that adjacent CCEs are mapped to dispersed REG bundles in the frequency domain (e.g., adjacent CCEs are not mapped to consecutive REG bundles of CORESET 320). The non-interleaved CORESET 320 may have CCE-to-REG mappings such that all CCEs are mapped to consecutive REG bundles (e.g., in the frequency domain) of CORESET 320.

As indicated above, fig. 3 is provided as an example. Other examples may differ from that described with respect to fig. 3.

Fig. 4 is a schematic diagram illustrating an example 400 of cross-carrier scheduling in accordance with the present disclosure.

As shown in fig. 4, in a cross-carrier scheduling scenario, a first carrier may have resources for scheduling communications on a second carrier. For example, the scheduling cell may include: a first resource for cross-carrier scheduling on a scheduled cell (e.g., on a secondary cell (SCell)) and a second resource for self-scheduling on a scheduling cell (e.g., on a primary cell (PCell)). In cross-carrier scheduling, a first search space is configured on a scheduling cell (e.g., PCell) having a specific identifier, and a second search space is configured on a scheduled cell (e.g., SCell) having the same specific identifier. The UE may monitor the scheduling cell search space for PDCCH candidates based at least in part on the configuration of the scheduling cell search space.

The UE may identify a number of candidates (nrofCandidates) for each aggregation level in the configuration of the scheduled cell search space, which may enable the UE to identify PDCCH candidates corresponding to the scheduled cell when monitoring on the scheduling cell. In other words, when the scheduling cell search space configuration identifies the number of candidates as 4 and the scheduled cell identifies the number of candidates as 2, the UE may associate a candidate with a Carrier Indicator Field (CIF) of 0 as being related to the scheduling cell and a candidate with a CIF of 1 as being related to the scheduled cell.

Similarly, in Dynamic Spectrum Sharing (DSS) with cross-carrier scheduling, there may be two scheduling cells for data scheduling on the PCell or primary secondary cell (PSCell). In this case, the PCell (or PSCell) may have a common search space for scheduling data on the PCell (or PSCell), and the SCell may have a UE-specific search space (USS) for scheduling data on the PCell (or PSCell). In DSS cross-carrier scheduling, a PCell or PSCell USS and a SCell USS (e.g., with a CIF of 1) may schedule communications on the PCell or PSCell, and a SCell USS (e.g., with a CIF of 0) may schedule communications on the SCell.

The UE may enable search space sharing by sending a UE capability message with parameters identifying UE capabilities for search space sharing. In this case, the network entity may determine that the UE is able to receive DCI scheduling data on a cell having the first CIF value at a PDCCH candidate corresponding to the second CIF value. However, search space configurations with common parameters between the scheduling cell and the scheduled cell may limit flexibility with respect to the use of search space sharing. In some scenarios, the first carrier may have a different digital scheme than the second carrier. For example, as shown, the scheduling cell may have a subcarrier spacing (SCS) of 15 kilohertz (kHz), and the scheduled cell may have an SCS of 30 kHz.

In order to enable a UE to monitor PDCCH candidates on a first carrier (scheduling cell with 15kHz SCS) for scheduling on a second carrier (scheduled cell with 30kHz SCS), the network entity configures two PDCCH monitoring occasions in each slot of the first carrier for both cross-carrier scheduling and self-scheduling. However, self-scheduling may be achieved with only one PDCCH monitoring occasion in each slot of the first carrier. As a result, the UE monitors an excessive number of resources, which results in more utilization of network resources, over-utilization of UE power resources or over-utilization of UE processing resources, and so on.

As indicated above, fig. 4 is provided as an example. Other examples may differ from that described with respect to fig. 4.

Some aspects described herein enable different configurations for different search spaces when enabling search space sharing. For example, the UE may receive search space configurations for the scheduling cell and the scheduled cell with different (e.g., independent) parameter configurations (such as different numbers of PDCCH monitoring occasions in each slot). In another example, the UE may receive a separate search space configuration, such as a search space configuration in a scheduling cell, that indicates a scheduled cell to which the search space configuration applies, or a search space configuration in a scheduled cell that indicates a scheduling cell to which the search space configuration applies. In these examples, the UE may enable search space sharing in some PDCCH monitoring occasions and not in other PDCCH monitoring occasions, allowing the UE to efficiently receive DCI according to parameters of the cell to which the DCI is applied (e.g., according to different digital schemes for different cells).

Fig. 5A-5B are diagrams illustrating an example 500 associated with search space sharing for cross-carrier scheduling in accordance with this disclosure. As shown in fig. 5A, example 500 includes communication between a network entity 502 and a UE 120 (e.g., a mobile station). In some aspects, network entity 502 and UE 120 may be included in a wireless network (such as wireless network 100). Network entity 502 and UE 120 may communicate via a radio access link, which may include an uplink and a downlink.

As shown in fig. 5A and further illustrated by reference numeral 505, UE 120 may provide a capability indication. For example, UE 120 may send a capability indication to network entity 502 identifying the search space sharing capability of UE 120. In this case, the network entity 502 may receive the capability indication and configure DCI transmission in the configured PDCCH monitoring occasions. In some aspects, the capability indication may relate to a particular carrier or set of cells. For example, UE 120 may provide a capability indication to identify search space sharing capabilities for the scheduling cell and the scheduled cell. In this case, the scheduling cell and the scheduled cell may have different configurations, such as different digital schemes (e.g., different SCS), and so on.

As shown in fig. 5A and further by reference numerals 510 and 515, UE 120 may receive a search space configuration and may receive DCI. For example, UE 120 may receive information identifying a search space configuration for monitoring DCI on a scheduling cell. In this case, network entity 502 may transmit DCI in one or more PDCCH monitoring occasions, and UE 120 may receive the DCI (which may schedule another communication such as PDSCH communication or physical uplink shared channel communication (PUSCH), or the like).

In some aspects, the search space configuration may have: a first parameter for monitoring a first set of PDCCH monitoring occasions (e.g., scheduling a scheduled cell) and a second parameter for monitoring a second set of PDCCH monitoring occasions (e.g., scheduling the scheduling cell). In some aspects, PDCCH monitoring occasions may have different periods. For example, UE 120 may monitor a first set of PDCCH monitoring occasions having a first period corresponding to a first SCS of a scheduled cell and a second set of PDCCH monitoring occasions having a second period corresponding to a second SCS of the scheduled cell.

In some aspects, network entity 502 and UE 120 may enable search space sharing in some PDCCH monitoring occasions. For example, as shown in diagram 520-1, search space sharing is enabled in a first PDCCH monitoring occasion in a slot and not enabled in a second PDCCH monitoring occasion in the slot. In this way, the network entity 502 may transmit DCI in a scheduling cell with a first SCS (e.g., PCell with 15kHz SCS) to schedule in a scheduled cell with a second SCS (e.g., SCell with 30kHz SCS) without the UE 120 monitoring for excessive PDCCH occasions. In other words, UE 120 monitors two PDCCH occasions for cross-carrier scheduling resources in each slot and monitors only one PDCCH occasion for self-scheduling resources in each slot, thereby reducing utilization of network resources, UE power resources, or UE processing resources relative to other techniques (as shown in fig. 4).

In another example, as shown in diagram 520-2, search space sharing is enabled in a first time slot and not enabled in a second time slot. In this way, the network entity 502 may transmit DCI in a scheduling cell with a second SCS (e.g., SCell with 30kHz SCS) to schedule in a scheduled cell with a first SCS (e.g., PCell with 15kHz SCS) without the UE 120 monitoring for excessive PDCCH occasions. In other words, UE 120 monitors the cross-carrier scheduling resources and the self-scheduling resources in the first time slot on the SCell and monitors only the self-scheduling resources in the second time slot on the SCell. In this manner, network entity 502 and UE 120 reduce utilization of network resources, UE power resources, or UE processing resources relative to other technologies (as shown in fig. 4).

In another example, search space sharing may be enabled for a first set of search space set configurations and not enabled for a second set of search space set configurations. For example, UE 120 may be configured with a first set of search spaces x for which cross-carrier scheduling is configured and a second set of search spaces y (which is configured only for scheduling cells). In this case, search space set sharing is enabled only for search space set x, and UE 120 monitors PDCCH candidates for the scheduling cell and for the scheduled cell based at least in part on the configuration of search space set x. UE 120 may detect DCI for scheduling data on the scheduled cell at a PDCCH candidate for the scheduling cell and/or may detect DCI for scheduling data on the scheduling cell at a PDCCH candidate for the scheduled cell.

In some aspects, UE 120 may monitor multiple sets of search spaces associated with multiple search space configurations (e.g., a set of search spaces for DCI scheduling PDSCH and a set of search spaces for DCI scheduling PUSCH). For example, UE 120 may monitor a first set of search spaces (e.g., with a first search space identifier) with resources for both self-scheduling and cross-carrier scheduling and a second set of search spaces (e.g., with a second search space identifier) with resources for self-scheduling only. In this case, the first set of search spaces and the second set of search spaces may have different monitoring opportunities.

As an example of multiple sets of search spaces, as shown in fig. 5B and diagram 520-3, a first set of search spaces on a PCell may have a periodicity corresponding to the SCS of the SCell, and a second set of search spaces on the PCell (or, in some cases, PSCell) may have a periodicity corresponding to the SCS of the PCell. In this way, network entity 502 and UE 120 may configure different sets of search spaces to enable UE 120 to receive DCI without using excessive resources (e.g., the second search space does not occur twice in each slot). Similarly, as shown in diagram 520-4, a first set of search spaces on an SCell may have a periodicity corresponding to the SCS of the PCell, and a second set of search spaces on the SCell may have a periodicity corresponding to the SCell. In this way, network entity 502 and UE 120 may configure different sets of search spaces to enable UE 120 to receive DCI without using excessive resources (e.g., the first search space is not present in each slot).

As noted above, fig. 5A-5B are provided as examples. Other examples may differ from the examples described with respect to fig. 5A-5B.

Fig. 6 is a schematic diagram illustrating an example process 600 performed, for example, by a mobile station, in accordance with the present disclosure. Example process 600 is an example of a mobile station (e.g., UE 120) performing operations associated with search space sharing for cross-carrier scheduling.

As shown in fig. 6, in some aspects, process 600 may include: a capability indication is sent that identifies search space sharing capabilities of the mobile station on the scheduling cell (block 610). For example, a mobile station (e.g., using the communication manager 140 and/or the transmitting component 804 depicted in fig. 8) can transmit a capability indication that identifies search space sharing capabilities of the mobile station on a scheduling cell, as described above.

As further shown in fig. 6, in some aspects, process 600 may include: a first set of PDCCH monitoring occasions to schedule a scheduled cell and a second set of PDCCH monitoring occasions to schedule the scheduling cell are monitored on a scheduling cell (block 620). For example, a mobile station (e.g., using the communication manager 140 and/or monitoring component 808 depicted in fig. 8) can monitor a first set of PDCCH monitoring occasions on a scheduling cell that schedule a scheduled cell and a second set of PDCCH monitoring occasions that schedule the scheduling cell, as described above.

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

In a first aspect, a scheduled cell has a first subcarrier spacing and a scheduling cell has a second subcarrier spacing.

In a second aspect, alone or in combination with the first aspect, the first set of PDCCH monitoring occasions has a first period corresponding to a first subcarrier spacing and the second set of PDCCH monitoring occasions has a second period corresponding to a second subcarrier spacing.

In a third aspect, alone or in combination with one or more of the first and second aspects, search space sharing associated with search space sharing capabilities is enabled on a second set of PDCCH monitoring occasions, wherein the second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, downlink control information for a scheduled cell on a first set of PDCCH monitoring occasions is receivable and downlink control information for a scheduling cell on a second set of PDCCH monitoring occasions is receivable.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, search space sharing is enabled on a first set of PDCCH monitoring occasions, wherein a second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

In a sixth aspect, downlink control information for a scheduled cell on a first set of PDCCH monitoring occasions is receivable and downlink control information for a scheduling cell on the first set of PDCCH monitoring occasions is receivable, alone or in combination with one or more of the first to fifth aspects.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the scheduling cell is a primary cell and the scheduled cell is a secondary cell.

In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the scheduling cell is a secondary cell and the scheduled cell is a primary cell.

While fig. 6 shows example blocks of process 600, in some aspects process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in fig. 6. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

Fig. 7 is a schematic diagram illustrating an example process 700 performed, for example, by a network entity, in accordance with the present disclosure. Example process 700 is an example in which a network entity (e.g., base station 110 or one or more of the components described herein with respect to fig. 10, etc.) performs operations associated with search space sharing for cross-carrier scheduling.

As shown in fig. 7, in some aspects, process 700 may include: a capability indication is received that identifies search space sharing capabilities of the mobile station on the scheduling cell (block 710). For example, a network entity (e.g., using the communication manager 150 and/or the receiving component 902 depicted in fig. 9) can receive a capability indication identifying search space sharing capabilities of a mobile station on a scheduling cell, as described above.

As further shown in fig. 7, in some aspects, process 700 may include: a first set of PDCCH communications scheduling a scheduled cell and a second set of PDCCH communications scheduling the scheduled cell are transmitted on a scheduling cell (block 720). For example, a network entity (e.g., using communication manager 150 and/or transmission component 904 depicted in fig. 9) can transmit a first set of PDCCH communications on a scheduling cell that schedules a scheduled cell and a second set of PDCCH communications that schedules the scheduling cell, as described above.

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

In a second aspect, alone or in combination with the first aspect, the first PDCCH communication set has a first period corresponding to a first subcarrier spacing and the second PDCCH communication set has a second period corresponding to a second subcarrier spacing.

In a third aspect, alone or in combination with one or more of the first and second aspects, search space sharing associated with a search space sharing capability is enabled on monitoring occasions corresponding to a second PDCCH communication set, wherein the monitoring occasions corresponding to the second PDCCH communication set are a subset of the monitoring occasions corresponding to the first PDCCH communication set.

In a fourth aspect, downlink control information is sent for a scheduled cell on a first PDCCH communication set and downlink control information is sent for a scheduling cell on a second PDCCH communication set, alone or in combination with one or more of the first to third aspects.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, search space sharing is enabled on monitoring occasions corresponding to the first PDCCH communication set, wherein the monitoring occasions corresponding to the second PDCCH communication set are a subset of the monitoring occasions corresponding to the first PDCCH communication set.

In a sixth aspect, downlink control information is sent for a scheduled cell on a first PDCCH communication set and downlink control information is sent for a scheduling cell on the first PDCCH communication set, alone or in combination with one or more of the first to fifth aspects.

While fig. 7 shows example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in fig. 7. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

Fig. 8 is a block diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a mobile station or the mobile station may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802 and a transmitting component 804, which can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 800 can communicate with another apparatus 806 (such as a UE or another wireless communication device) using a receiving component 802 and a transmitting component 804. As further shown, the apparatus 800 may include a communication manager 140. The communications manager 140 can include a monitoring component 808 or the like.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with fig. 5A-5B. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of fig. 6. In some aspects, the apparatus 800 and/or one or more components illustrated in fig. 8 may comprise one or more components of a mobile station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 8 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 802 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 806. The receiving component 802 can provide the received communication to one or more other components of the apparatus 800. In some aspects, the receiving component 802 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 806. In some aspects, the receive component 802 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for a mobile station as described in connection with fig. 2.

The transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 806. In some aspects, one or more other components of the apparatus 806 may generate a communication and may provide the generated communication to the sending component 804 for transmission to the apparatus 806. In some aspects, the transmitting component 804 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 806. In some aspects, the transmit component 804 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the mobile station described in connection with fig. 2. In some aspects, the transmitting component 804 may be co-located with the receiving component 802 in a transceiver.

The transmitting component 804 can transmit a capability indication that identifies search space sharing capability of the mobile station on the scheduling cell. The monitoring component 808 can monitor a first set of PDCCH monitoring occasions on a scheduling cell that schedules a scheduled cell and a second set of PDCCH monitoring occasions that schedules the scheduling cell.

The number and arrangement of components shown in fig. 8 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in fig. 8. Further, two or more components shown in fig. 8 may be implemented within a single component, or a single component shown in fig. 8 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (e.g., one or more components) shown in fig. 8 may perform one or more functions described as being performed by another set of components shown in fig. 8.

Fig. 9 is a block diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a network entity or the network entity may comprise the apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904, the receiving component 902 and the transmitting component 904 can be in communication 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, a network entity, or another wireless communication device) using a receiving component 902 and a transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. The communication manager 150 can include a scheduling component 908 and the like.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in connection with fig. 5A-5B. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of fig. 7. In some aspects, the apparatus 900 and/or one or more components illustrated in fig. 9 may include one or more components of a base station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 9 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 902 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the apparatus 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 906. In some aspects, the receiving component 902 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for a base station described in connection with fig. 2.

The transmitting component 904 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 906. In some aspects, one or more other components of the apparatus 906 may generate a communication and may provide the generated communication to the sending component 904 for transmission to the apparatus 906. In some aspects, the transmitting component 904 can perform signal processing (e.g., filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and can transmit the processed signal to the device 906. In some aspects, the transmit component 904 can include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the base station described in connection with fig. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

The receiving component 902 can receive a capability indication that identifies search space sharing capabilities of a mobile station on a scheduling cell. The transmitting component 904 can transmit a first set of PDCCH communications on a scheduling cell that schedules a scheduled cell and a second set of PDCCH communications that schedules the scheduling cell. The scheduling component 908 can schedule communications on a scheduling cell or a scheduled cell.

The number and arrangement of components shown in fig. 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in fig. 9. Further, two or more components shown in fig. 9 may be implemented within a single component, or a single component shown in fig. 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (e.g., one or more components) shown in fig. 9 may perform one or more functions described as being performed by another set of components shown in fig. 9.

Fig. 10 is a schematic diagram illustrating an example 1000 of an open radio access network (O-RAN) architecture according to the present disclosure. As shown in fig. 10, the O-RAN architecture may include a Control Unit (CU) 1010 that communicates with a core network 1020 via a backhaul link. Further, CU 1010 may communicate with one or more Distributed Units (DUs) 1030 via respective mid-range links. DU 1030 may each communicate with one or more Radio Units (RUs) 1040 via respective forward links, and RU 1040 may each communicate with a respective UE 120 via a Radio Frequency (RF) access link. DU 1030 and RU 1040 may also be referred to as O-RAN DU (O-DU) 1030 and O-RAN RU (O-RU) 1040, respectively.

The DUs 1030 and RUs 1040 may be implemented according to a functional split architecture, wherein the functionality of the base station 110 (e.g., eNB or gNB) is provided by the DUs 1030 and one or more RUs 1040 communicating over a forward link. Thus, as described herein, base station 110 may include a DU 1030 and one or more RUs 1040, which may be co-located or geographically distributed. In some aspects, the DUs 1030 and associated RUs 1040 may communicate via a forward link to exchange real-time control plane information via a Lower Layer Split (LLS) control plane (LLS-C) interface, non-real-time management information via a LLS management plane (LLS-M) interface, and/or user plane information via a LLS user plane (LLS-U) interface.

Thus, DU 1030 may correspond to a logic unit that includes one or more base station functions to control the operation of one or more RUs 1040. For example, in some aspects, DU 1030 may host a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (e.g., forward Error Correction (FEC) encoding and decoding, scrambling, and/or modulation and demodulation) based at least in part on lower layer functional partitions. Higher layer control functions, such as Packet Data Convergence Protocol (PDCP), RRC, and/or Service Data Adaptation Protocol (SDAP), may be hosted by CU 1010. RU 1040, controlled by DU 1030, may correspond to a logical node hosting RF processing functions and low PHY layer functions (e.g., fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, and/or Physical Random Access Channel (PRACH) extraction and filtering) based at least in part on lower layer functional splitting. Thus, in the O-RAN architecture, RU 1040 handles all over-the-air (OTA) communications with UE 120, and the real-time and non-real-time aspects of control and user plane communications with RU 1040 are controlled by corresponding DU 1030, which enables DU 1030 and CU 1010 to be implemented in the cloud-based RAN architecture.

As indicated above, fig. 10 is provided as an example. Other examples may differ from the example described with respect to fig. 10.

The following provides an overview of some aspects of the disclosure.

Aspect 1: a method of wireless communication performed by a mobile station comprising: transmitting, by the mobile station, a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and monitoring, by the mobile station, a first set of Physical Downlink Control Channel (PDCCH) monitoring occasions of scheduling a scheduled cell and a second set of PDCCH monitoring occasions of scheduling the scheduling cell on the scheduling cell.

Aspect 2: the method of aspect 1, wherein the scheduled cell has a first subcarrier spacing and the scheduling cell has a second subcarrier spacing.

Aspect 3: the method of aspect 2, wherein the first set of PDCCH monitoring occasions has a first period corresponding to the first subcarrier spacing and the second set of PDCCH monitoring occasions has a second period corresponding to the second subcarrier spacing.

Aspect 4: the method of any of aspects 1-3, wherein search space sharing associated with the search space sharing capability is enabled on the second set of PDCCH monitoring occasions, wherein the second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

Aspect 5: the method of aspect 4, wherein downlink control information for the scheduled cell on the first set of PDCCH monitoring occasions is receivable and downlink control information for the scheduling cell on the second set of PDCCH monitoring occasions is receivable.

Aspect 6: the method of any of claims 1-5, wherein search space sharing is enabled on the first set of PDCCH monitoring occasions, wherein the second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

Aspect 7: the method of aspect 6, wherein downlink control information for the scheduled cell on the first set of PDCCH monitoring occasions is receivable and downlink control information for the scheduling cell on the first set of PDCCH monitoring occasions is receivable.

Aspect 8: the method of any one of aspects 1 to 7, wherein the monitoring comprises: a plurality of PDCCH monitoring occasions are monitored, the plurality of PDCCH monitoring occasions comprising the first set of PDCCH monitoring occasions and the second set of PDCCH monitoring occasions, and wherein the plurality of PDCCH monitoring occasions comprise at least one subset of PDCCH monitoring occasions associated with a first set of search spaces and a first search space identifier for self-scheduling and at least one subset of PDCCH monitoring occasions associated with a second set of search spaces and a second search space identifier for cross-carrier scheduling.

Aspect 9: the method of aspect 8, wherein the second search space identifier is used for cross-carrier scheduling and self-scheduling, and wherein the second set of search spaces includes the first set of PDCCH monitoring occasions and the second set of PDCCH monitoring occasions.

Aspect 10: the method of any one of claims 1 to 9, wherein the scheduling cell is a primary cell and the scheduled cell is a secondary cell.

Aspect 11: the method of any of claims 1-10, wherein the scheduling cell is a secondary cell and the scheduled cell is a primary cell.

Aspect 12: the method of any one of aspects 1-11, wherein search space sharing is enabled only on the first set of PDCCH monitoring occasions.

Aspect 13: the method of any one of aspects 1-12, wherein search space sharing is enabled on the first set of PDCCH monitoring occasions and the second set of PDCCH monitoring occasions.

Aspect 14: a method of wireless communication performed by a network entity, comprising: receiving, by the network entity, a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and transmitting, by the network entity, a first Physical Downlink Control Channel (PDCCH) communication set scheduling the scheduled cell and a second PDCCH communication set scheduling the scheduling cell on the scheduling cell.

Aspect 15: the method of aspect 12, wherein the scheduled cell has a first subcarrier spacing and the scheduling cell has a second subcarrier spacing.

Aspect 16: the method of claim 13, wherein the first PDCCH communication set has a first period corresponding to the first subcarrier spacing and the second PDCCH communication set has a second period corresponding to the second subcarrier spacing.

Aspect 17: the method of any of aspects 12-14, wherein search space sharing associated with the search space sharing capability is enabled on a monitoring occasion corresponding to the second PDCCH communication set, wherein the monitoring occasion corresponding to the second PDCCH communication set is a subset of a monitoring occasion corresponding to the first PDCCH communication set.

Aspect 18: the method of aspect 15, wherein downlink control information is transmitted for the scheduled cell on the first set of PDCCH communications and downlink control information is transmitted for the scheduling cell on the second set of PDCCH communications.

Aspect 19: the method of any of claims 12-16, wherein search space sharing is enabled on monitoring occasions corresponding to the first PDCCH communication set, wherein monitoring occasions corresponding to the second PDCCH communication set are a subset of the monitoring occasions corresponding to the first PDCCH communication set.

Aspect 20: the method of aspect 17, wherein downlink control information is transmitted for the scheduled cell on the first PDCCH communication set and downlink control information is transmitted for the scheduling cell on the first PDCCH communication set.

Aspect 21: the method of any of aspects 12-18, wherein the transmitting comprises: a plurality of PDCCH communications are transmitted, the plurality of PDCCH communications including the first set of PDCCH communications and the second set of PDCCH communications, and wherein the plurality of PDCCH communications include at least a subset of PDCCH communications associated with a first set of search spaces and a first search space identifier for self-scheduling and at least a subset of PDCCH communications associated with a second set of search spaces and a second search space identifier for cross-carrier scheduling.

Aspect 22: the method of claim 19, wherein the second search space identifier is used for cross-carrier scheduling and self-scheduling, and wherein the second set of search spaces includes the first set of PDCCH communications and the second set of PDCCH communications.

Aspect 23: the method of any of claims 12 to 20, wherein the scheduling cell is a primary cell and the scheduled cell is a secondary cell.

Aspect 24: the method of any of claims 12 to 20, wherein the scheduling cell is a secondary cell and the scheduled cell is a primary cell.

Aspect 25: the method of any one of aspects 12-21, wherein search space sharing is enabled only on the first set of PDCCH monitoring occasions.

Aspect 26: the method of any of aspects 12-22, wherein search space sharing is enabled on the first set of PDCCH monitoring occasions and the second set of PDCCH monitoring occasions.

Aspect 27: an apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1-13.

Aspect 28: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-13.

Aspect 29: an apparatus for wireless communication, comprising at least one unit for performing the method of one or more of aspects 1-13.

Aspect 30: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-13.

Aspect 31: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-13.

Aspect 32: an apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 14-26.

Aspect 33: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 14-26.

Aspect 34: an apparatus for wireless communication, comprising at least one unit to perform the method of one or more of aspects 14-26.

Aspect 35: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 14-26.

Aspect 36: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 14-26.

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

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. "software" should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures and/or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It will be apparent that the systems and/or methods described herein may be implemented in various forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of these aspects. Thus, the operation and behavior of the systems and/or methods were described without reference to the specific software code-as one of ordinary skill in the art would understand that software and hardware could be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, a "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, and so forth, depending on the context.

Although specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim in the set of claims. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items, including individual members. For example, "at least one of a, b, or c" is intended to encompass a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (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, or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items recited in conjunction with the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items, and may be used interchangeably with "one or more". Where it is intended that only one item is used, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "having," having, "and the like are intended to be open-ended terms that do not limit the element they modify (e.g., an element having" a may also have B). Furthermore, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and may be used interchangeably with "and/or" unless otherwise specifically indicated (e.g., if used in combination with "either" or "only one of").

Claims

1. A mobile station for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory, the one or more processors configured to:

transmitting a capability indication identifying search space sharing capability of the mobile station on a scheduling cell; and

a first set of Physical Downlink Control Channel (PDCCH) monitoring occasions of a scheduling scheduled cell and a second set of PDCCH monitoring occasions of the scheduling cell are monitored on the scheduling cell.

2. The mobile station of claim 1, wherein search space sharing is enabled only on the first set of PDCCH monitoring occasions.

3. The mobile station of claim 1, wherein search space sharing is enabled on the first and second sets of PDCCH monitoring occasions.

4. The mobile station of claim 1, wherein the scheduled cell has a first subcarrier spacing and the scheduling cell has a second subcarrier spacing.

5. The mobile station of claim 4, wherein the first set of PDCCH monitoring occasions has a first period corresponding to the first subcarrier spacing and the second set of PDCCH monitoring occasions has a second period corresponding to the second subcarrier spacing.

6. The mobile station of claim 1, wherein search space sharing associated with the search space sharing capability is enabled on the second set of PDCCH monitoring occasions, wherein the second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

7. The mobile station of claim 6, wherein downlink control information for the scheduled cell on the first set of PDCCH monitoring occasions is receivable and downlink control information for the scheduling cell on the second set of PDCCH monitoring occasions is receivable.

8. The mobile station of claim 1, wherein search space sharing is enabled on the first set of PDCCH monitoring occasions, wherein the second set of PDCCH monitoring occasions is a subset of the first set of PDCCH monitoring occasions.

9. The mobile station of claim 8, wherein downlink control information for the scheduled cell on the first set of PDCCH monitoring occasions is receivable and downlink control information for the scheduling cell on the first set of PDCCH monitoring occasions is receivable.

10. The mobile station of claim 1, wherein the one or more processors configured to monitor the first set of PDCCH monitoring occasions are further configured to:

monitoring a plurality of PDCCH monitoring occasions, the plurality of PDCCH monitoring occasions comprising the first PDCCH monitoring occasion set and the second PDCCH monitoring occasion set,

wherein the plurality of PDCCH monitoring occasions includes at least a subset of PDCCH monitoring occasions associated with a first set of search spaces and a first search space identifier for self-scheduling and at least a subset of PDCCH monitoring occasions associated with a second set of search spaces and a second search space identifier for cross-carrier scheduling.

11. The mobile station of claim 10, wherein the second search space identifier is used for cross-carrier scheduling and self-scheduling, and wherein the second set of search spaces comprises the first set of PDCCH monitoring occasions and the second set of PDCCH monitoring occasions.

12. The mobile station of claim 1, wherein the scheduling cell is a primary cell and the scheduled cell is a secondary cell.

13. The mobile station of claim 1, wherein the scheduling cell is a secondary cell and the scheduled cell is a primary cell.

14. A network entity for wireless communication, comprising:

a memory; and

receiving a capability indication identifying search space sharing capability of a mobile station on a scheduling cell; and

a first Physical Downlink Control Channel (PDCCH) communication set scheduling a scheduled cell and a second PDCCH communication set scheduling the scheduled cell are transmitted on the scheduling cell.

15. The network entity of claim 14, wherein search space sharing is enabled only on the first set of PDCCH monitoring occasions.

16. The network entity of claim 14, wherein search space sharing is enabled on the first and second sets of PDCCH monitoring occasions.

17. The network entity of claim 14, wherein the scheduled cell has a first subcarrier spacing and the scheduling cell has a second subcarrier spacing.

18. The network entity of claim 17, wherein the first PDCCH communication set has a first period corresponding to the first subcarrier spacing and the second PDCCH communication set has a second period corresponding to the second subcarrier spacing.

19. The network entity of claim 14, wherein search space sharing associated with the search space sharing capability is enabled on monitoring occasions corresponding to the second PDCCH communication set, wherein the monitoring occasions corresponding to the second PDCCH communication set are a subset of monitoring occasions corresponding to the first PDCCH communication set.

20. The network entity of claim 19, wherein downlink control information is sent for the scheduled cell on the first set of PDCCH communications and downlink control information is sent for the scheduling cell on the second set of PDCCH communications.

21. The network entity of claim 14, wherein search space sharing is enabled on monitoring occasions corresponding to the first PDCCH communication set, wherein monitoring occasions corresponding to the second PDCCH communication set are a subset of the monitoring occasions corresponding to the first PDCCH communication set.

22. The network entity of claim 21, wherein downlink control information is sent for the scheduled cell on the first set of PDCCH communications and downlink control information is sent for the scheduling cell on the first set of PDCCH communications.

23. The network entity of claim 14, wherein the one or more processors configured to transmit the first set of PDCCH monitoring occasions are further configured to:

transmitting a plurality of PDCCH communications, the plurality of PDCCH communications including the first set of PDCCH communications and the second set of PDCCH communications,

wherein the plurality of PDCCH communications includes at least a subset of PDCCH communications associated with a first set of search spaces and a first search space identifier for self-scheduling and at least a subset of PDCCH communications associated with a second set of search spaces and a second search space identifier for cross-carrier scheduling.

24. The network entity of claim 23, wherein the second search space identifier is used for cross-carrier scheduling and self-scheduling, and wherein the second set of search spaces comprises the first set of PDCCH communications and the second set of PDCCH communications.

25. The network entity of claim 14, wherein the scheduling cell is a primary cell and the scheduled cell is a secondary cell.

26. The network entity of claim 14, wherein the scheduling cell is a secondary cell and the scheduled cell is a primary cell.

27. A method of wireless communication performed by a mobile station, comprising:

28. The method of claim 27, wherein search space sharing is enabled only on the first set of PDCCH monitoring occasions.

29. The method of claim 27, wherein search space sharing is enabled on the first and second sets of PDCCH monitoring occasions.

30. A method of wireless communication performed by a network entity, comprising: