Patent Description:
US patent application <CIT> discloses a method of default Quasi-Co-Location (QCL) assumption for Physical Downlink Shared Channel (PDSCH) reception in NR networks. When PDSCH is scheduled by a DCI over PDCCH after a Scheduling Offset, the spatial RX filter for the PDSCH reception can be determined according to a QCL indication conveyed by the DCI. When the Scheduling Offset for PDSCH reception scheduled by DCI is less than a time duration, then a default QCL assumption is applied. UE assumes that the DMRS ports of PDSCH of a serving cell are QCL'ed with the RS( s) with respect to QCL parameter(s) used for PDCCH QCL indication of a CORESET. The CORESET is associated with a UE-monitored search space in the latest slot with the lowest CORESET-ID on an active BWP on the serving cell.

The present disclosure provides a method for wireless communications by a user equipment according to claim <NUM>, a method for wireless communications by a network entity according to claim <NUM>, an apparatus for wireless communication by a user equipment according to claim <NUM>, and an apparatus for wireless communication by a network entity according to claim <NUM>. Specific embodiments are subject of the dependent claims.

The following description and the appended drawings set forth in detail certain illustrative features of one or more aspects.

Aspects of the present disclosure provide apparatus, devices, methods, processing systems, and computer readable mediums for determining quasi-co-located (QCL) assumptions for control resource sets (CORESETs).

For example, a UE may be configured with transmission configuration indicator (TCI) states may be configured for a dynamic CORESET. In some cases, a downlink control information (DCI) scheduling the dynamic CORESET may (dynamically) indicate one of the TCI states. The UE may then monitor the dynamic CORESET for a physical downlink control channel (PDCCH) in accordance with the indicated TCI state.

<FIG> illustrates an example wireless communication network <NUM> (e.g., an NR/<NUM> network), in which aspects of the present disclosure may be performed. For example, the wireless network <NUM> may include a UE <NUM> configured with a dynamic CORESET manager <NUM> to perform operations <NUM> of <FIG> to determine quasi-co-location (QCL) assumptions for dynamic control resource sets (CORESETs). Similarly, the wireless network <NUM> may include a base station <NUM> configured with a dynamic CORESET manager <NUM> to perform operations <NUM> of <FIG> to determine QCL assumptions for dynamic CORESETS.

As illustrated in <FIG>, the wireless network <NUM> may include a number of base stations (BSs) <NUM> and other network entities. A BS may be a station that communicates with user equipments (UEs). Each BS <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a NodeB (NB) and/or a NodeB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and next generation NodeB (gNB), new radio base station (NR BS), <NUM> NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

In the example shown in <FIG>, a relay station 110r may communicate with the BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r.

The BSs <NUM> communicate with UEs 120a-y (each also individually referred to herein as UE <NUM> or collectively as UEs <NUM>) in the wireless communication network <NUM>. In one example, a quadcopter, drone, or any other unmanned aerial vehicle (UAV) or remotely piloted aerial system (RPAS) 120d may be configured to function as a UE.

A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, gaming device, reality augmentation device (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device that is configured to communicate via a wireless or wired medium.

In some scenarios, air interface access may be scheduled. For example, a scheduling entity (e.g., a base station (BS), Node B, eNB, gNB, or the like) can allocate resources for communication among some or all devices and equipment within its service area or cell. That is, for scheduled communication, subordinate entities can utilize resources allocated by one or more scheduling entities.

Turning back to <FIG>, this figure illustrates a variety of potential deployments for various deployment scenarios. For example, in <FIG>, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. Other lines show component to component (e.g., UE to UE) communication options.

<FIG> illustrates example components of BS <NUM> and UE <NUM> (as depicted in <FIG>), which may be used to implement aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> may be used to perform operations <NUM> of <FIG> (e.g., to implement a dynamic CORESET module <NUM>), while antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform operations <NUM> of <FIG>.

A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a through 232t. Downlink signals from modulators 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.

At the UE <NUM>, antennas 252a through 252r may receive downlink signals from the base station <NUM> and may provide received signals to demodulators (DEMODs) in transceivers 254a through 254r, respectively. Each demodulator <NUM> may condition (e.g., filter, amplify, down convert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from all demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.

The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station <NUM>. At the BS <NUM>, uplink signals from the UE <NUM> may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE <NUM>.

The controllers/processors <NUM> and <NUM> may direct operations at the base station <NUM> and the UE <NUM>, respectively. The processor <NUM> and/or other processors and modules at the BS <NUM> may perform or direct execution of processes for techniques described herein.

Embodiments discussed herein may include a variety of spacing and timing deployments. For example, in LTE, the basic transmission time interval (TTI) or packet duration is the <NUM> subframe. A subframe contains a variable number of slots (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, slots) depending on the subcarrier spacing.

A mini-slot is a subslot structure (e.g., <NUM>, <NUM>, or <NUM> symbols).

In NR, a synchronization signal (SS) block (SSB) is transmitted. The PSS may provide half-frame timing, and the SS may provide the CP length and frame timing. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc..

As shown in <FIG>, the SS blocks (SSBs) <NUM> may be organized into SS burst sets <NUM> to support beam sweeping. As shown, each SSB <NUM> within a burst set <NUM> of L SSBs may be transmitted using a different beam <NUM> (e.g., beams B0-BL), which may help a UE quickly acquire both transmit (Tx) and receive (Rx) beams (particular for mmW applications). A physical cell identity (PCI) may still decoded from the PSS and SSS of the SSB <NUM>.

Certain deployment scenarios may include one or both NR deployment options. Some may be configured for non-standalone (NSA) and/or standalone (SA) option. A standalone cell may need to broadcast both SSB and remaining minimum system information (RMSI), for example, with SIB1 and SIB2. A non-standalone cell may only need to broadcast SSB, without broadcasting RMSI. In a single carrier in NR, multiple SSBs may be sent in different frequencies, and may include the different types of SSB.

A control resource set (CORESET) for an orthogonal frequency division multiple access (OFDMA) system (e.g., a communications system transmitting physical downlink control channel (PDCCH) using OFDMA waveforms) may comprise one or more control resource (e.g., time and frequency resources) sets, configured for conveying PDCCH, within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. Search spaces are generally areas or portions of the CORESET where a communication device (e.g., a UE) may look for control information.

According to aspects of the present disclosure, a CORESET is a set of time and frequency domain resources, defined in units of resource element (RE) groups (REGs). Each REG may comprise a fixed number (e.g., twelve) tones in one symbol period (e.g., a symbol period of a slot), where one tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). Sets of CCEs may be used to transmit PDCCHs (e.g., new radio (NR) PDCCHs), with different numbers of CCEs in the sets used to transmit NR-PDCCHs using differing aggregation levels. Multiple sets of CCEs may be defined as search spaces for UEs, and thus a NodeB or other base station may transmit an NR-PDCCH to a UE by transmitting the NR-PDCCH in a set of CCEs that is defined as a decoding candidate within a search space for the UE, and the UE may receive the NR-PDCCH by searching in search spaces for the UE and decoding the NR-PDCCH transmitted by the NodeB.

Operating characteristics of a NodeB or other base station in a communications system (e.g., a NR communications system) may be dependent on a frequency range (FR) in which the system operates. A frequency range may comprise one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band), and a communications system (e.g., one or more NodeBs and UEs) may operate in one or more operating bands. Frequency ranges and operating bands are described in more detail in "Base Station (BS) radio transmission and reception" TS38. <NUM> (Release <NUM>), which is available from the 3GPP website.

As described above, a CORESET is a set of time and frequency domain resources. The CORESET can be configured for conveying PDCCH within system bandwidth. A UE may determine a CORESET and monitors the CORESET for control channels. During initial access, a UE may identify an initial CORESET (CORESET #<NUM>) configuration from a field (e.g., pdcchConfigSIB1) in a maser information block (MIB). This initial CORESET may then be used to configure the UE (e.g., with other CORESETs and/or bandwidth parts via dedicated (UE-specific) signaling. When the UE detects a control channel in the CORESET, the UE attempts to decode the control channel and communicates with the transmitting BS (e.g., the transmitting cell) according to the control data provided in the control channel (e.g., transmitted via the CORESET).

According to aspects of the present disclosure, when a UE is connected to a cell (or BS), the UE may receive a master information block (MIB). The MIB can be in a synchronization signal and physical broadcast channel (SS/PBCH) block (e.g., in the PBCH of the SS/PBCH block) on a synchronization raster (sync raster). In some scenarios, the sync raster may correspond to an SSB. From the frequency of the sync raster, the UE may determine an operating band of the cell. Based on a cell's operation band, the UE may determine a minimum channel bandwidth and a subcarrier spacing (SCS) of the channel. The UE may then determine an index from the MIB (e.g., four bits in the MIB, conveying an index in a range <NUM>-<NUM>).

Given this index, the UE may look up or locate a CORESET configuration (this initial CORESET configured via the MIB is generally referred to as CORESET #<NUM>). This may be accomplished from one or more tables of CORESET configurations. These configurations (including single table scenarios) may include various subsets of indices indicating valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of indices in the table.

Alternatively or additionally, the UE may select a search space CORESET configuration table from several tables of CORESET configurations. These configurations can be based on a minimum channel bandwidth and SCS. The UE may then look up a CORESET configuration (e.g., a Type0-PDCCH search space CORESET configuration) from the selected table, based on the index. After determining the CORESET configuration (e.g., from the single table or the selected table), the UE may then determine the CORESET to be monitored (as mentioned above) based on the location (in time and frequency) of the SS/PBCH block and the CORESET configuration.

<FIG> shows an exemplary transmission resource mapping <NUM>, according to aspects of the present disclosure. In the exemplary mapping, a BS (e.g., BS 110a, shown in <FIG>) transmits an SS/PBCH block <NUM>. The SS/PBCH block includes a MIB conveying an index to a table that relates the time and frequency resources of the CORESET <NUM> to the time and frequency resources of the SS/PBCH block.

The BS may also transmit control signaling. In some scenarios, the BS may also transmit a PDCCH to a UE (e.g., UE <NUM>, shown in <FIG>) in the (time/frequency resources of the) CORESET. The PDCCH may schedule a PDSCH <NUM>. The BS then transmits the PDSCH to the UE. The UE may receive the MIB in the SS/PBCH block, determine the index, look up a CORESET configuration based on the index, and determine the CORESET from the CORESET configuration and the SS/PBCH block. The UE may then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH that was allocated by the PDCCH.

Different CORESET configurations may have different parameters that define a corresponding CORESET. For example, each configuration may indicate a number of resource blocks (e.g., <NUM>, <NUM>, or <NUM>), a number of symbols (e.g., <NUM>-<NUM>), as well as an offset (e.g., <NUM>-<NUM> RBs) that indicates a location in frequency.

In many cases, it is important for a UE to know which assumptions it can make on a channel corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS (e.g., a gNB) for scheduling, link adaptation, and/or beam management purposes. Currently (e.g., in NR, the concept of quasi co-location (QCL) and transmission configuration indicator (TCI) states is used to convey information about these assumptions.

QCL assumptions are generally defined in terms of channel properties. Per 3GPP TS <NUM>, "two antenna ports are said to be quasi-co-located if properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. " Different reference signals may be considered quasi co-located ("QCL'ed") if a receiver (e.g., a UE) can apply channel properties determined by detecting a first reference signal to help detect a second reference signal. TCI states generally include configurations such as QCL-relationships, for example, between the downlink (DL) reference signals (RSs) in one CSI-RS set and the PDSCH demodulation reference signal (DMRS) ports.

In some cases, a UE may be configured with up to M TCI-States. Configuration of the M TCI-States can come about via higher layer signalling, while a UE may be signalled to decode PDSCH according to a detected PDCCH with DCI indicating one of the TCI states. Each configured TCI state may include one RS set TCI-RS-SetConfig that indicates different QCL assumptions between certain source and target signals.

<FIG> illustrate examples of the association of DL reference signals (<NUM>, <NUM>) with corresponding QCL types <NUM> that may be indicated by a TCI-RS-SetConfig.

In the examples of <FIG>, a source RS <NUM> is indicated in the top block and is associated with a target signal <NUM> indicated in the bottom block. In this context, a target signal generally refers to a signal for which channel properties may be inferred by measuring those channel properties for an associated source signal. As noted above, a UE may use the source RS to determine various channel parameters, depending on the associated QCL type, and use those various channel properties (determined based on the source RS) to process the target signal. A target RS does not necessarily need to be PDSCH's DMRS, rather it can be any other RS type: PUSCH DMRS, CSIRS, TRS, and SRS.

As illustrated, each TCI-RS-SetConfig contains parameters. These parameters can, for example, configure quasi co-location relationship(s) between reference signals in the RS set and the DM-RS port group of the PDSCH. The RS set contains a reference to either one or two DL RSs and an associated QCL Type for each one configured by the higher layer parameter QCL-Type.

As illustrated in <FIG>, for the case of two DL RSs, the QCL types can take on a variety of arrangements. For example, QCL types may not be the same, regardless of whether the references are to the same DL RS or different DL RSs. In the illustrated example, SSB is associated with Type C QCL for P-TRS, while CSI-RS for beam management (CSIRS-BM) is associated with Type D QCL.

QCL information and/or types may in some scenarios depend on or be a function of other information. For example, the QCL types indicated to the UE can be based on higher layer parameter QCL-Type and may take one or a combination of the following types:.

Spatial QCL assumptions (e.g., QCL-TypeD) may be used to help a UE to select an analog reception (Rx) beam (e.g., during beam management procedures). For example, an SSB resource indicator may indicate a same beam for a previous reference signal should be used for a subsequent transmission.

An initial CORESET (e.g., CORESET ID <NUM> or simply CORESET#<NUM>) in NR may be identified during initial access by a UE (e.g., via a field in the MIB). A ControlResourceSet information element (CORESET IE) sent via radio resource control (RRC) signaling may convey information regarding a CORESET configured for a UE. The CORESET IE generally includes a CORESET ID, an indication of frequency domain resources (e.g., number of RBs) assigned to the CORESET, contiguous time duration of the CORESET in a number of symbols, and Transmission Configuration Indicator (TCI) states.

As noted above, a subset of the TCI states provide quasi co-location (QCL) relationships between DL RS(s) in one RS set (e.g., TCI-Set) and PDCCH demodulation RS (DMRS) ports. A particular TCI state for a given UE (e.g., for unicast PDCCH) may be conveyed to the UE by the Medium Access Control (MAC) Control Element (MAC-CE). The particular TCI state is generally selected from the set of TCI states conveyed by the CORESET IE, with the initial CORESET (CORESET#<NUM>) generally configured via MIB.

Search space information may also be provided via RRC signaling. For example, the SearchSpace IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with one CORESET. The SearchSpace IE identifies a search space configured for a CORESET by a search space ID. In an aspect, the search space ID associated with CORESET # <NUM> is SearchSpace ID #<NUM>. The search space is generally configured via PBCH (MIB).

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for processing and signaling dynamic control channel resources. As will be described, the techniques presented herein may allow for the use of more sparse "regular" periodic control channel resources, allowing a UE to conserve power by staying in a low power state longer (e.g., unless dynamic control channel resources are indicated in the regular control channel resources).

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In <NUM> NR two initial operating bands have been identified as frequency range designations FR1 (<NUM> - <NUM>) and FR2 (<NUM> - <NUM>). It should be understood that although a portion of FR1 is greater than <NUM>, FR1 is often referred to (interchangeably) as a "Sub-<NUM>" band in various documents and articles.

Recent <NUM> NR studies have identified an operating band for these mid-band frequencies as frequency range designation <CIT> GHz - <NUM>). For example, three higher operating bands have been identified as frequency range designations- FR4a or FR4-<NUM> (<NUM> - <NUM>), FR4 (<NUM> - <NUM>), and FR5 (<NUM> - <NUM>).

In certain applications, a UE may be designed to support a limited number of NR features (also referred to as NR Light or NR Lite), for example, to keep costs low. Due to limited device capability in such applications, a UE may not be able to monitor PDCCH in every slot.

In FR4 or NR Lite applications, control channel resource can be sparsely configured (e.g., occurring with a relatively low periodicity). Sparse control channel monitoring by the UE may alleviate the issues described above and provide a power saving gain. For example, a PDCCH monitoring periodicity (e.g., by search space periodicity configuration in NR) can be very large (e.g., much greater than <NUM> slot) in FR4.

Unfortunately, sparse control channel resources may limit scheduling flexibility and increase latency. Dynamic configuration and indication of additional control channel resource proposed herein may help avoid these drawbacks of sparse control channel resources. In some cases, a network entity (e.g., a gNB) may dynamically indicate additional control channel resources in certain conditions, for example, to accommodate an increase (burst) of traffic targeting a particular UE.

As illustrated in the example diagram <NUM> <FIG>, dynamic control channel resources <NUM> may be indicated by dynamic signaling, for example, via a PDCCH in regular (sparse/periodic) control channel resource <NUM> carrying downlink control information (DCI) or layer <NUM> (L1) signaling. Unlike regular control channel resources <NUM>, the dynamic resources <NUM> are non-recurring (e.g., aperiodic) and may be for one-shot (or a limited number of) monitoring occasions.

In some cases, the network (e.g., a gNB) may configure a UE with different options for sets of dynamic control channel resources. Based on the configuration and an indication, the UE can monitor control channels (e.g., PDCCH) within the dynamic control channel resources.

As illustrated in <FIG>, dynamic control channel resources provided between sparse regular control channel monitoring occasions provide additional opportunities for control channel transmissions. As shown, the dynamic resources may be nested within resources for a PDSCH scheduled by the PDCCH. As will be described below, in some cases, the dynamic resources may be offset in frequency from the scheduled PDSCH to avoid a collision.

As illustrated, in some cases a PDCCH/DCI sent in dynamic control signal resources may indicate still additional dynamic control channel resources which creates a chain. In some cases, if such a chain expands beyond a regular control channel resource, the UE may skip monitoring the regular control channel resource.

There are various options for how dynamic control channel resources may be triggered. For example, in some cases, one or more sets of dynamic control channel resources may be indicated simultaneously. For example, PDCCH can be used for signaling the dynamic control channel resources. As illustrated, the PDCCH may be transmitted either in the regular control channel resources or in other dynamic control channel resources.

In some cases, the PDCCH may be a UE-specific PDCCH for DL/UL scheduling and/or a non-scheduling group-common PDCCH (e.g., with no grant). In some cases, a DCI carried by the PDCCH may have one or more additional fields for indicating the dynamic resources can be added in the DCI. In other cases, a single field in the DCI may trigger multiple sets of dynamic resources jointly. In other cases, multiple separate fields may be used, each triggering a different set.

In some cases, a network entity may configure a UE with a list of one or more sets of dynamic control channel resources (e.g., by RRC signaling). In such cases, a triggering field in the DCI may include an index in the list.

In such cases, the configuration may include various parameters, such as: time/frequency resources, a resource mapping type (e.g., interleaved or localized), precoding, beam (e.g., a QCL/TCI state), aggregation level, and/or a number of PDCCH candidates.

For joint triggering of multiple dynamic control channel resource sets, a combination of more than one sets of resources can be associated with a single entry in the list.

In some cases, instead of pre-configuration (some or all of the dynamic control channel resource parameters), some parameters related to the dynamic resources may be determined at the moment of triggering. For example, when the dynamic resources are triggered by a DL scheduling DCI, the TCI state for the dynamic resources may be determined by the TCI state of the scheduled PDSCH (which may be particular appropriate when there is an overlap of resources).

Alternatively, at least one of the regular control channel resources can be indicated to the UE and the UE may determine dynamic control channel resources based on this regular configuration. In such cases, the same resource configuration as the regular control channel resources may be applied to the dynamic resources with some modification. For example, the periodicity configuration of the regular control channel may be ignored and the timing may be determined by an offset relative to the triggering DCI. As noted above, in some cases, a frequency shift (e.g., relative to the co-scheduled PDSCH) may be applied to avoid resource collision. In some cases, the dynamic indication may tell the UE to skip (avoid monitoring for PDCCH in) one or more regular control channel resources.

As noted above, certain assumptions, such as quasi-co-located (QCL) assumptions, may help a user equipment (UE) process downlink transmissions. Aspects of the present disclosure provide techniques for determining QCL assumptions (relationships) for dynamic CORESETs, for example, based on QCL relationships and transmission configuration information (TCI) states. For example, the techniques may allow the UE to know which reference signals it can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH) in a dynamic CORESET. As noted above, the concept of quasi co-location (QCL) and transmission configuration indicator (TCI) states is used to convey information about these assumptions.

Further, while the techniques described herein may be applicable to new radio (NR) technologies, it should be appreciated that the techniques of the present disclosure may be implemented in any suitable technology.

A first approach to determine the QCL/TCI for the dynamic CORESETs may leverage QCL/TCI state determination mechanisms for regular CORESETs.

According to a second approach, TCI states for dynamic CORESETs may be dynamically indicated, for example, similar to how TCI states are dynamically indicated for PDSCH, but separately. This approach may improve flexibility and may allow for refined beams.

According to a third approach, if PDSCH and dynamic CORESETs are co-scheduled (e.g., by the same DCI), dynamic CORESETs may be able to reuse the same TCI state indication as used for (the co-scheduled) physical downlink shared channel (PDSCH). This approach may enable use of a refined beam for dynamic CORESETs. In some cases, some combination of two or more of these various approach may be used.

<FIG> and <FIG> illustrate example operations that may be performed by a UE and network entity, respectively, for determining QCL assumptions for dynamic CORESETs according to the first approach.

<FIG> illustrates example operations <NUM> for wireless communications by a UE, in accordance with certain aspects of the present disclosure. For example, operations <NUM> may be performed by a UE <NUM> of <FIG> to determine QCL assumptions for dynamic CORESETs.

Operations <NUM> begin, at <NUM>, by receiving (or detecting) a first PDCCH in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic CORESET. For example, referring back to <FIG>, a first PDCCH (e.g., PDCCH1) in a regular (sparse) CORESET can indicate one or more dynamic CORESETs. The dynamic CORESETs could be nested in PDSCH regions or standalone and could indicate other dynamic CORESETs.

At <NUM>, the UE receives a second PDCCH within the at least one dynamic CORESET, wherein the second PDCCH is received in accordance with at least one QCL assumption for the at least one dynamic CORESET. In certain aspects, the UE determines at least one QCL assumption for the at least one dynamic CORESET. In some cases, a TCI/QCL of the PDCCH DMRS may follow similar principals as PDCCH DMRS of the regular scheduling CORESET (e.g., in which the first PDCCH was sent). As will be described in greater detail below, in case the UE is not provided with a TCI state configuration or does not receive an activation command in sufficient time to apply to the dynamic CORESET, the UE may determine the TCI/QCL for the dynamic CORESET according to various options. In some cases, the UE monitors, in accordance with the determined QCL assumption, the at least one dynamic CORESET for at least a second PDCCH.

<FIG> illustrates example operations <NUM> for wireless communications by a network entity and may be considered complementary to operations <NUM> of <FIG> and may be considered complementary to operations <NUM> of <FIG>. For example, operations <NUM> may be performed by a gNB scheduling transmissions to a UE <NUM> performing operations <NUM> of <FIG>.

Operations <NUM> begin, at <NUM>, by sending a UE a first PDCCH in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set CORESET. In certain aspects, the network entity also determines at least one QCL assumption for the at least one set of dynamic control resources.

At <NUM>, the network entity sends the UE at least a second PDCCH on the at least one dynamic CORESET, in accordance with at least one QCL assumption determined for the at least one dynamic CORESET.

As noted above, in some cases, the TCI/QCL of the PDCCH DMRS in the dynamic CORESET may follow the same or similar principles as that of PDCCH DMRS of regular scheduling CORESETs (with some customizations). For example, for a dynamic CORESET, a list of TCI states may be optionally signaled in the dynamic CORESET RRC configuration (the RRC messaging configuring dynamic CORESETs and corresponding parameters).

A medium access control (MAC) control element (MAC-CE) may activate one of the configured TCI states and the activated TCI state may be applied after some time (e.g., to give the UE time to update beam settings in the case of QCL type D). For example, the UE may be able to apply the activation command in the first slot that is after slot <MAT>, where k is the slot where the UE transmits a PUCCH with hybrid automatic repeat request (HARQ) acknowledgement (ACK) information for the PDSCH providing the activation command and µ is the subcarrier spacing (SCS) configuration (e.g., of active BWP) for the PUCCH. The active BWP may be defined as the active BWP in the slot when the activation command is applied.

In some cases, the UE may not be provided with TCI state configuration(s) for the dynamic CORESET, may not receive a MAC-CE activation command for a TCI for the dynamic CORESET, or may not receive the MAC-CE activation command for one of the provided TCI states (e.g., in an RRC configuration) for the dynamic CORESET in sufficient time to apply it for the dynamic CORESET (e.g., if the dynamic CORESET is in a slot before <MAT>).

In such cases (e.g., before the UE is signaled TCI states, before the UE receives signaling activating a TCI state, or before the UE is signaled an active TCI state with sufficient time to apply for monitoring the dynamic CORESET for at least a second PDCCH, the QCL assumption is determined based on an assumption a demodulation reference signal (DMRS) of the second PDCCH shares a QCL relationship with at least one prior downlink transmission), the QCL assumption for the dynamic CORESET may be determined according to various options. The various options may be understood with reference to <FIG>.

For example, according to a first option, labeled QCL Option A in <FIG>, PDCCH DMRS for the dynamic CORESET <NUM> may be QCL'ed with the SSB <NUM> that the UE identified during the initial access procedure (and used to locate the regular scheduling CORESET <NUM>). For example, the UE may monitor the dynamic CORESET with a same receive beam corresponding to the SSB.

According to a second option, labeled QCL Option B in <FIG>, PDCCH DMRS for the dynamic CORESET may be QCL'ed with PDCCH DMRS for the scheduling CORESET (regardless if dynamic or regular). In other words, if the regular CORESET schedules the dynamic CORESET, the PDCCH DMRS for the dynamic CORESET is QCL'ed with the PDCCH DMRS for the regular CORESET. If another dynamic CORESET schedules the dynamic CORESET, the PDCCH DMRS for the scheduled dynamic CORESET is QCL'ed with the PDCCH DMRS for the scheduling dynamic CORESET.

According to a third option, labeled as QCL Option C in <FIG>, PDCCH DMRS for the dynamic CORESET is QCL'ed with PDCCH DMRS for the original scheduling CORESET (e.g., only if the scheduling CORESET is a regular CORESET).

According to a fourth option, labeled as QCL Option D in <FIG>, PDCCH DMRS for dynamic CORESET is QCL'ed with PDCCH DMRS for a CORESET with the lowest controlResourceSetId in a latest slot. In this case, that CORESET can be dynamic or regular. The lowest ID could be for dynamic CORESETs only, regular CORESETs only, or both.

In some cases, one of multiple options (e.g., one of the four QCL options A-D described above), may be signaled or specified.

In some cases, if the UE receives a MAC-CE activation command for one of the provided TCI states (e.g., provided in RRC configuration) for the dynamic CORESET and the dynamic CORESET is in slot on or after <MAT> (e.g. so the UE has sufficient time to apply the activated TCI state) or the UE is provided (e.g., in a RRC configuration) with only one TCI state for the dynamic CORESET then the PDCCH DMRS for the dynamic CORESET may be QCL'ed with the one or more DL RS configured by the (activated or only one) TCI state.

In some cases, the network may indicate (e.g., in a RRC configuration or at the scheduling of the dynamic CORESET) that the dynamic CORESET shares the same configured and activated TCI states with its scheduling CORESET.

As illustrated in <FIG>, in such cases, if the UE receives a MAC-CE <NUM> activation command for one of the provided TCI states (in a RRC configuration) for the scheduling CORESET <NUM> and the dynamic CORESET <NUM> is in slot on or after slot <MAT>, or if the UE is provided (e.g., in RRC config) with only one TCI state for the scheduling CORESET <NUM>, then the PDCCH DMRS for the dynamic CORESET <NUM> is QCL'ed with the one or more DL RS configured by the (activated or single) TCI state (for the scheduling CORESET <NUM>).

In some cases, the UE may not be provided with a TCI state configuration for the dynamic CORESET, the UE may not receive a MAC-CE activation command for TCI, and/or the UE may receive a MAC-CE activation command for one of the provided TCI states (in a RRC configuration) for the dynamic CORESET and the dynamic CORESET too late for it to apply (e.g., the dynamic CORESET is in a slot before slot <MAT>). In such cases (e.g., before the UE is signaled TCI states, before the UE receives signaling activating a TCI state, or before the UE is signaled an active TCI state with sufficient time to apply for monitoring the dynamic CORESET for at least a second PDCCH, the QCL assumption is determined based on an assumption a DMRS of the second PDCCH shares a QCL relationship with at least one prior downlink transmission), if the dynamic CORESET slot is at least <MAT> from the HARQ-ACK <NUM> of a MAC-CE activation for the scheduling CORESET (regardless if dynamic or regular), then the PDCCH DMRS for the dynamic CORESET may be QCL'ed with the one or more DL RS configured by a latest (activated) TCI state for the scheduling CORESET.

In some cases, a DCI (that schedules a dynamic CORESET) received on one component carrier (CC) may schedule a dynamic CORESET on another CC. For example, assuming scheduling CORESET <NUM> of <FIG> is in a first CC (CC1), a DCI received in scheduling CORESET <NUM> could schedule a dynamic CORESET <NUM> in a second CC (CC2). In such cases, the UE may obtain its QCL assumption for the dynamic PDCCH from the activated TCI state with the lowest ID applicable to PDCCH (e.g., in the active BWP of the scheduled cell).

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG>, or other operations for performing the various techniques discussed herein. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for receiving a first physical downlink control channel (PDCCH) in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set (CORESET); and code <NUM> for receiving a second PDCCH within the dynamic CORESET, wherein the second PDCCH is received in accordance with at least one quasi-co-located (QCL) assumption for the at least one dynamic CORESET. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes the circuitry <NUM> for receiving a first physical downlink control channel (PDCCH) in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set (CORESET); and circuitry <NUM> for receiving a second PDCCH within the dynamic CORESET, wherein the second PDCCH is received in accordance with at least one quasi-co-located (QCL) assumption for the at least one dynamic CORESET.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG>, or other operations for performing the various techniques discussed herein. In certain aspects, computer-readable medium/memory <NUM> stores: code <NUM> for sending a UE a first physical downlink control channel (PDCCH) in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set (CORESET); and code <NUM> for sending the UE at least a second PDCCH on the at least one dynamic CORESET, in accordance with at least one quasi-co-located (QCL) assumption determined for the at least one dynamic CORESET. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> for sending a UE a first physical downlink control channel (PDCCH) in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set (CORESET); and circuitry <NUM> for sending the UE at least a second PDCCH on the at least one dynamic CORESET, in accordance with at least one quasi-co-located (QCL) assumption determined for the at least one dynamic CORESET.

<FIG> illustrates example operations <NUM> for wireless communications by a UE, not claimed in the appended claims. For example, operations <NUM> may be performed by a UE <NUM> of <FIG> to determine QCL assumptions for dynamic CORESETs.

Operations <NUM> begin, at <NUM>, by detecting a first physical downlink control channel (PDCCH) in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic control resource set (CORESET). For example, referring back to <FIG>, a first PDCCH (PDCCH1) in a regular (sparse) CORESET can indicate one or more dynamic CORESETs. The dynamic CORESETs could be nested in PDSCH regions or standalone could indicate other dynamic CORESETs. In the case where a single PDCCH indicates the dynamic CORESET and schedules a PDSCH, the PDSCH and dynamic CORESET are referred to herein as "co-scheduled.

At <NUM>, the UE determines at least one quasi-co-located (QCL) assumption for the dynamic CORESET. For example, in case the UE is not provided with a TCI state configuration or does not receive an activation command in sufficient time to apply to the dynamic CORESET, in some cases, the UE may reuse the TCI/QCL assumptions for the PDSCH co-scheduled with the dynamic CORESET.

At <NUM>, the UE monitors in accordance with the determined QCL assumption, the at least one CORESET for at least a second PDCCH. For example, the UE may monitor the dynamic CORESET using QCL/TCI assumptions of the co-scheduled PDSCH, if applicable.

<FIG> illustrates example operations <NUM> for wireless communications by a network entity and may be considered complementary to operations <NUM> of <FIG>. For example, operations <NUM> may be performed by a gNB scheduling transmissions to a UE <NUM> performing operations <NUM> of <FIG>.

Operations <NUM> begin, at <NUM>, by sending a UE a first PDCCH in a control channel monitoring occasion, the first PDCCH indicating at least one dynamic CORESET.

At <NUM>, the network entity determines at least one QCL assumption for the at least one set of dynamic control resources. At <NUM>, the network entity sends the UE at least a second PDCCH on the at least one set of dynamic control channel resources, in accordance with the determined QCL assumption.

Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

For example, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> shown in <FIG> may be configured to perform operations <NUM> of <FIG> or operations <NUM> of <FIG>.

Means for receiving may include a receiver (such as one or more antennas or receive processors) illustrated in <FIG>. Means for transmitting may include a transmitter (such as one or more antennas or transmit processors) illustrated in <FIG>. Means for determining, means for processing, means for treating, and means for applying may include a processing system, which may include one or more processors, such as processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> shown in <FIG>.

In some cases, rather than actually transmitting a frame a device may have an interface to output a frame for transmission (a means for outputting). For example, a processor may output a frame, via a bus interface, to a radio frequency (RF) front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device (a means for obtaining). For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for reception.

Claim 1:
A method for wireless communications by a user equipment, UE (<NUM>; <NUM>), comprising:
receiving (<NUM>) a first physical downlink control channel, PDCCH, in a control channel monitoring occasion (<NUM>; <NUM>), the first PDCCH indicating at least one dynamic control resource set, CORESET (<NUM>; <NUM>); and
receiving (<NUM>) a second PDCCH within the at least one dynamic CORESET, wherein the second PDCCH is received in accordance with at least one quasi-co-located, QCL, assumption for the at least one dynamic CORESET.