Patent Description:
In other examples (e.g., in a next generation, a new radio (NR), or a <NUM> network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more DUs, in communication with a central unit, may define an access node (e.g., which may be referred to as a BS, a <NUM> NB, a next generation NodeB (gNB or gNodeB), a transmit receive point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a BS or DU).

<CIT> relates to a method of sending TCI, a network-side device and a terminal device.

"<NPL>, relates to a number of agreements relating to beam management.

NR (e.g., <NUM> NR) is an example of an emerging telecommunication standard.

Aspects of the present disclosure provide apparatus, devices, methods, processing systems, and computer readable mediums for quasi co-location (QCL) reference signals for uplink transmission configuration indicator (TCI) states.

Aspects of the present disclosure may help provide a unified framework for uplink and downlink TCI states. In the unified framework, a base station (BS) can configure and/or indicate antenna panel-specific transmission for uplink transmission, via an uplink TCI.

The following description provides examples of QCL RS for TCI states, and is not limiting of the scope, applicability, or examples set forth in the claims.

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 some cases, new radio (NR) RAT networks may be deployed.

The techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with <NUM>, <NUM>, and/or new radio (e.g., <NUM> NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.

NR access (e.g., <NUM> technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth, millimeter wave (mmW) targeting high carrier frequency, massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC).

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>). 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.

NR supports beamforming and beam direction may be dynamically configured. MIMO configurations in the DL may support multiple (e.g., up to <NUM>) transmit antennas with multilayer DL transmissions (e.g., up to <NUM> streams) and multiple (e.g., up to <NUM>) streams per UE. Aggregation of multiple cells may be supported (e.g., up to <NUM> serving cells).

<FIG> illustrates an example wireless communication network <NUM> (e.g., an NR/<NUM> network), in which aspects of the present disclosure may be performed. As shown in <FIG>, the wireless communication network <NUM> may be in communication with a core network <NUM>. The core network <NUM> may in communication with one or more base station (BSs) 110a-z (each also individually referred to herein as BS <NUM> or collectively as BSs <NUM>) and/or user equipment (UE) 120a-y (each also individually referred to herein as UE <NUM> or collectively as UEs <NUM>) in the wireless communication network <NUM> via one or more interfaces.

According to certain aspects, the BSs <NUM> and UEs <NUM> may be configured for quasi co-location (QCL) reference signals for uplink transmission configuration indicator (TCI) states. As shown in <FIG>, the BS 110a includes a TCI state manager <NUM>. The TCI state manager <NUM> may be configured to send an uplink TCI indicating one or more uplink quasi co-location (QCL) types, from a plurality of uplink QCL types, for one or more source reference signals (RSs), in accordance with aspects of the present disclosure. The UE 120a includes a TCI state manager <NUM>. The TCI state manager <NUM> may be configured to receive an uplink TCI indicating one or more uplink QCL types, from a plurality of uplink QCL types, for one or more source RSs, in accordance with aspects of the present disclosure.

A BS 110a may provide communication coverage for a particular geographic area, sometimes referred to as a "cell" , which may be stationary, or may move according to the location of a mobile BS. In some examples, the BSs <NUM> may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network.

In aspects, the network controller <NUM> may be in communication with the core network <NUM> (e.g., a <NUM> Core Network (5GC)), which provides various network functions such as Access and Mobility Management, Session Management, User Plane Function, Policy Control Function, Authentication Server Function, Unified Data Management, Application Function, Network Exposure Function, Network Repository Function, Network Slice Selection Function, etc..

The BSs <NUM> communicate with UEs <NUM> in the wireless communication network <NUM>.

<FIG> illustrates an example logical architecture of a distributed radio access network (RAN) <NUM>, which may be implemented in the wireless communication network <NUM> illustrated in <FIG>.

For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, TRPs <NUM> may be connected to more than one ANC.

The logical architecture of distributed RAN <NUM> may support various backhauling and fronthauling solutions. This support may occur via and across different deployment types.

<FIG> illustrates example components of BS 110a and UE 120a (e.g., the wireless communication network <NUM> of <FIG>), which may be used to implement aspects of the present disclosure.

At the BS 110a, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

The processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS). 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) in transceivers 432a-432t. Each modulator in transceivers 432a-432t may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Downlink signals from the modulators in transceivers 432a-432t may be transmitted via the antennas 434a-434t, respectively.

At the UE 120a, the antennas 452a-452r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 454a-454r, respectively. Each demodulator in transceivers 454a-454r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. A MIMO detector <NUM> may obtain received symbols from all the demodulators in transceivers 454a-454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at UE 120a, a transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor <NUM>. The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the modulators in transceivers 454a-454r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signals from the UE 120a may be received by the antennas <NUM>, processed by the demodulators in transceivers 432a-432t, 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 120a.

Antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE 120a and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS 110a may be used to perform the various techniques and methods described herein. For example, as shown in <FIG>, the controller/processor <NUM> of the BS 110a has a TCI state manager <NUM> that sends an uplink TCI to a UE, the uplink TCI indicating one or more QCL types from a plurality of uplink QCL types for one or more RSs, according to aspects described herein. As shown in <FIG>, the controller/processor <NUM> of the UE 120a has a TCI state manager <NUM> that receives an uplink TCI, the uplink TCI indicating one or more QCL types from a plurality of uplink QCL types for one or more RSs, according to aspects described herein. Although shown at the controller/processor, other components of the UE 120a and BS 110a may be used to perform the operations described herein.

A first option <NUM>-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC <NUM> in <FIG>) and distributed network access device (e.g., TRP <NUM> in <FIG>).

Each subframe may include a variable number of slots (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>,. slots) depending on the SCS. Each slot may include a variable number of symbol periods (e.g., <NUM>, <NUM>, or <NUM> symbols) depending on the SCS. A sub-slot structure may refer to a transmit time interval having a duration less than a slot (e.g., <NUM>, <NUM>, or <NUM> symbols). Each symbol in a slot may be configured for a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched.

In NR, a synchronization signal block (SSB) is transmitted. In certain aspects, SSBs may be transmitted in a burst where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and/or beam refinement). The SSB includes a PSS, a SSS, and a two symbol PBCH. The SSB can be transmitted in a fixed slot location, such as the symbols <NUM>-<NUM> as shown in <FIG>. 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. The SSBs may be organized into SS bursts to support beam sweeping. The SSB can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmWave. The multiple transmissions of the SSB are referred to as a SS burst set. SSBs in an SS burst set may be transmitted in the same frequency region, while SSBs in different SS bursts sets can be transmitted at different frequency regions.

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

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.

Operating characteristics of a gNB in an NR communications system may be dependent on a frequency range (FR) in which the system operates. A frequency range may include one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band, etc.). A communications system (e.g., one or more gNBs and UEs) may operate in one or more operating bands.

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 include 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 where a communication device (e.g., a UE) may look for (e.g., monitor) control information.

A CORESET may be defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) of 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 new radio PDCCHs (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. A gNB may transmit a NR-PDCCH to a UE in a set of CCEs, called a decoding candidate, within a search space for the UE. The UE may receive the NR-PDCCH by searching (e.g., monitoring) in search spaces and decoding the NR-PDCCH.

During initial access, a UE may identify an initial CORESET (e.g., referred to as CORESET #<NUM>) configuration from an indication field (e.g., a pdcchConfigSIB1 field) in system information (e.g., in a maser information block (MIB) carried in PBCH). 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 the UE communicates with the transmitting BS (e.g., the transmitting cell) according to the control information provided in a decoded control channel.

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 the 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 example transmission resource mapping <NUM>, according to aspects of the present disclosure. In the 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 transmits the control signaling in a PDCCH to a UE (e.g., UE 120a, shown in <FIG>) in the (time/frequency resources of the) CORESET <NUM>. The PDCCH may schedule a PDSCH <NUM>. The BS then transmits the PDSCH <NUM> to the UE. The UE may receive the MIB in the SS/PBCH block <NUM>, determine the index, look up a CORESET configuration based on the index, and determine the CORESET <NUM> from the CORESET configuration and the SS/PBCH block. The UE may then monitor the CORESET <NUM>, decode the PDCCH in the CORESET <NUM>, and receive the PDSCH <NUM> 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.

As discussed above, aspects of the disclosure related to QCL reference signals for uplink TCI states.

It may be desirable for a UE to know which assumptions the UE can make on a channel for different transmissions. For example, the UE should know which reference signals the UE can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH or PDSCH). It may also be desirable for the UE to be able to report relevant channel state information (CSI) to the BS for scheduling, link adaptation, and/or beam management purposes. In NR, the concept of QCL and TCI states is used to convey information about these assumptions.

QCL assumptions are generally defined in terms of channel properties. For example, 3GPP TS <NUM> defines QCL as "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 (RSs) may be considered quasi co-located (QCL'd) if a receiver can apply channel properties determined by detecting a first reference signal to help detect a second signal. TCI states generally include configurations such as QCL-relationships, such as the relationships between the downlink (DL) source RSs in one CSI reference signal (CSI-RS) set and the target 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 may be via higher layer signalling (e.g., a higher layer parameter TCI-States). A UE may be signalled to decode PDSCH according to a detected PDCCH with downlink control information (DCI) indicating one of the TCI states. Each configured TCI state may include one RS set (e.g., by higher layer parameter TCI-RS-SetConfig) that indicates different QCL assumptions between certain source and target signals.

QCL signaling may be provided for RSs and channels across scenarios involving multiple cells, such as in coordinated multipoint (CoMP) scenarios in which multiple transmit receive points (TRPs) or integrated access and backhaul (IAB) nodes each have their own cell ID.

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

The table <NUM> shows source RSs, target RSs, and QCL type assumptions that may be configured by a valid UL- TCI state configuration. The 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. Examples of source RSs include phase tracking reference signals (PTRSs), SSBs, sounding reference signal (SRS), and/or CSI-RSs (e.g., CSI-RS for beam management). Examples of target RSs include aperiodic tracking reference signals (TRSs), periodic TRSs, PRACHs, PUCCHs, and/or PUSCHs. The QCL types include the QCL types A/B/C/D discussed below.

For the case of two source RSs, the different QCL types can be configured for the same target RS. In the illustrative example, SSB is associated with TypeC QCL for P-TRS, while CSI-RS for beam management (CSI-RS-BM) is associated with TypeD QCL.

QCL types indicated to the UE can be based on a higher layer parameter (e.g., higher layer parameter QCL-Type). QCL types and may take one or a combination of the following types:.

Spatial QCL assumptions (QCL-TypeD) may be used to help a UE to select an analog receive (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 information element (e.g., CORESET IE) sent via 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 TCI states.

As noted above, a subset of the TCI states provide QCL relationships between DL RS(s) in one RS set (e.g., a TCI set) and another signal (e.g., DMRS ports for another transmission). A particular TCI state for a given UE (e.g., for unicast PDCCH) may be conveyed to the UE by a MAC-CE. The TCI state may be 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 (e.g., carried in the MIB).

Aspects of the present disclosure relate to techniques for QCL reference signals for uplink TCI states.

According to aspects of the present disclosure, a base station (BS) and a user equipment (UE) may have a transmission configuration indicator (TCI) framework for downlink and/or uplink beam indication. The BS can configure and/or indicate panel-specific transmission for uplink transmission via an uplink TCI framework or a panel ID. If the BS uses an uplink TCI framework, in some systems, uplink TCI based signalling is supported, where a new panel identifier (ID) may or may not be introduced and a panel specific signalling is performed using uplink TCI state.

Aspects of the present disclosure involve including quasi co-located (QCL) types with an uplink TCI so that a UE may know which assumptions the UE can make on a channel for different transmissions.

If the BS uses a panel ID, the panel ID may be implicitly or explicitly applied to the transmission for a target RS resource or resource set. The target RS resource may be a physical uplink control channel (PUCCH) resource, a sounding reference signal (SRS) resource, a physical uplink shared channel (PUSCH) resource, and/or a physical random access channel (PRACH) resource.

For a TCI framework for downlink and/or uplink beam indications, the uplink TCI may indicate a source reference signal (RS) associated with the uplink transmit beam for a target uplink RS and/or a target uplink channel. In some cases, the source RS may be an SRS, a synchronization signal block (SSB), and/or a channel state information (CSI) RS (CSI-RS). The target uplink RS or channel may be a PUCCH, SRS, PRACH, and/or PUSCH.

<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>. The operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the UE in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

Operations <NUM> begin, at <NUM>, by receiving, as claimed, an uplink TCI indicating one or more quasi co-location (QCL) types, from a plurality of uplink QCL types, for one or more source RSs. The uplink TCI may indicate multiple QCL types from the plurality of uplink QCL types for multiple source RSs. One of the plurality of uplink QCL types may indicate a spatial relation between one of the source RSs and the uplink transmission, and one or more of the plurality of uplink QCL types indicates a Doppler shift, average delay, Doppler spread, delay spread, or a combination thereof, associated with the one or more source RSs and the uplink transmission.

In some aspects, at <NUM>, the UE may receive the one or more source RSs. The one or more source RS may include SRSs, SSBs, CSI-RSs, or a combination thereof.

In some aspects, at <NUM>, the UE may determine one or more parameters for the uplink transmission based on the uplink TCI and the one or more source RSs. The one or more parameters may include a beam, a time, a frequency, a transmit power, or a combination thereof for the uplink transmission.

At <NUM>, the UE sends, as claimed, an uplink transmission in accordance with the uplink TCI. In some claimed aspects, different types of uplink transmissions are associated with different sets of uplink QCL types. The one or more uplink transmissions may include a PUCCH transmission, a RACH transmission, a PUSCH transmission, or a combination thereof.

According to the claimed invention, different types of uplink transmission by the UE are associated with different sets of uplink QCL types such that a first uplink transmission is associated with a first QCL uplink type and a second uplink transmission is associated with a second uplink QCL type.

<FIG> illustrates example operations <NUM> for wireless communications, in accordance with certain aspects of the present disclosure. For example, operations <NUM> may be performed by a network entity, such as a base station (BS) (e.g., BS 110a of <FIG> which may be a gNB). The operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the BS in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

Operations <NUM> begin, at <NUM>, by sending, as claimed, an uplink TCI to a UE, the uplink TCI indicating one or more QCL types from a plurality of uplink QCL types for one or more source RS. The uplink TCI indicates, as claimed, multiple QCL types from the plurality of uplink QCL types for multiple source RSs. One of the plurality of uplink QCL types may indicate a spatial relation between one of the source RSs and the uplink transmission, and one or more of the plurality of uplink QCL types indicates a Doppler shift, average delay, Doppler spread, delay spread, or a combination thereof, associated with the one or more source RSs and the uplink transmission.

At <NUM>, the network entity sends, as claimed, at least one of the source RSs to the UE. The one or more source RS may include SRSs, SSBs, CSI-RSs, or a combination thereof.

At <NUM>, the network entity receives, as claimed, from the UE, an uplink transmission in accordance with the uplink TCI. In some claimed aspects, different types of uplink transmissions are associated with different sets of uplink QCL types. The uplink transmission may include a PUCCH transmission, a RACH transmission, a PUSCH transmission, or a combination thereof.

In some aspects, at <NUM>, the network entity estimates uplink time, frequency offsets, or both, based on the uplink TCI and the at least one source RS.

In some systems, each configured uplink TCI state only contains one source RS for uplink transmit beam indication, similar to QCL TypeD RS in downlink TCI state. Accordingly, other uplink QCL Type RSs for gNB may be used to estimate uplink time and/or frequency offset.

Besides the source RS for uplink spatial relation indication, each configured uplink TCI state can contain at least one uplink QCL Type RSs. For example, the configured uplink TCI state can be used to estimate uplink Doppler and/or delay spread statistics for uplink time/frequency offset compensation. As mentioned, the QCL may take one or a combination of the following types:.

In some aspects, the UE receives a timing reference signal (TRS) parameter per SRS resource or per SRS resource set. The corresponding SRS resources can serve as other uplink QCL Type RSs, including an uplink non-spatial relation indication.

In some aspects, the UE receives a repetition parameter per SRS resource set. Generally, a repetition factor is configured per SRS resource.

In some aspects, each target uplink RS and/or channel has its own set of combinations of different QCL Type RSs. The target uplink RS and/or channel may include SRS resources or resource sets. These SRS resources or resource sets may be configured with a TRS parameter and/or with usage as beam management (BM). The SRS resource or resource set may be classified as periodic (P), semi-persistent (SP), and/or aperiodic (AP). In some examples, the target uplink RS and/or channel may include PUCCH, PUSCH, and/or PRACH. Each combination of QCL Type RSs for the target uplink RS and/or channel may include a corresponding uplink QCL types. The corresponding uplink QCL type may be any combination of uplink QCL TypeA, QCL-TypeB, QCL-TypeC, and/or QCL-TypeD. In some cases (e.g., for Frequency Range <NUM> (FR2)), the combination may include uplink QCL TypeD. In some cases (e.g., for Frequency Range (FR1)), the combination may not include uplink QCL TypeD.

The communications device <NUM> includes a processing system <NUM> coupled to a transceiver <NUM> (e.g., a transmitter and/or a receiver).

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 for QCL reference signals for uplink TCI states. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for receiving an uplink TCI indicating one or more uplink QCL types, from a plurality of uplink QCL types, for one or more source RSs; and code <NUM> for sending an uplink transmission in accordance with the uplink TCI. In certain aspects, computer-readable medium/memory <NUM> may store code <NUM> for receiving the one or more source RSs; and/or code <NUM> for determining one or more parameters for the uplink transmission based on the uplink TCI and the one or more source RSs. 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 receiving an uplink TCI indicating one or more uplink QCL types, from a plurality of uplink QCL types, for one or more source RSs; circuitry <NUM> for sending an uplink transmission in accordance with the uplink TCI. In certain aspects, the processor <NUM> may include circuitry <NUM> for receiving the one or more source RSs; and/or circuitry <NUM> for determining one or more parameters for the uplink transmission based on the uplink TCI and the one or more source RSs.

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 for QCL reference signals for uplink TCI states. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for sending an uplink TCI to a UE, the uplink TCI indicating one or more QCL types from a plurality of uplink QCL types for one or more source RS; code <NUM> for sending at least one of the source RSs to the UE; and/or code <NUM> for receiving, from the UE, an uplink transmission in accordance with the uplink TCI. In certain aspects, computer-readable medium/memory <NUM> may store code for estimating uplink time, frequency offsets, or both, based on uplink TCI and the at least one source RS. 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 an uplink TC) to a UE, the uplink TCI indicating one or more QCL types from a plurality of uplink QCL types for one or more source RS; circuitry <NUM> for sending at least one of the source RSs to the UE; and circuitry <NUM> for receiving, from the UE, an uplink transmission in accordance with the uplink TCI. In certain aspects, the processor <NUM> may include circuitry <NUM> for estimating uplink time, frequency offsets, or both, based on uplink TCI and the at least one source RS.

Claim 1:
A method (<NUM>) of wireless communications by a user equipment, UE, the method (<NUM>) comprising:
receiving (<NUM>) an uplink transmission configuration indicator, TCI, indicating one or more uplink quasi co-location, QCL, types, from a plurality of uplink QCL types, for one or more source reference signals, RSs; and
sending (<NUM>) an uplink transmission in accordance with the uplink TCI, characterized in that different types of uplink transmission by the UE are associated with different sets of uplink QCL types such that a first uplink transmission is associated with a first QCL uplink type and a second uplink transmission is associated with a second uplink QCL type.