CN117121390A

CN117121390A - Indicating capability for codebook-based and non-codebook-based Physical Uplink Shared Channel (PUSCH) transmissions

Info

Publication number: CN117121390A
Application number: CN202280024140.5A
Authority: CN
Inventors: M·霍什内维桑; 陈一滔; 张晓霞
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-04-01
Filing date: 2022-04-01
Publication date: 2023-11-24

Abstract

Certain aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for transmitting repetitions of uplink data, e.g., physical Uplink Shared Channel (PUSCH), in particular for transmitting PUSCH repetitions in multiple transmission and reception points (multi-TRP) and/or multi-panel configurations. In a general aspect, the present disclosure provides techniques for signaling User Equipment (UE) capabilities for codebook-based and non-codebook-based uplink transmissions in multiple TRPs to improve reliability and robustness. For example, the UE may signal to the network entity an indication of the ability to support PUSCH transmissions with at least two repeated sets. Each repetition set is associated with at least one set of Sounding Reference Signal (SRS) resources.

Description

Indicating capability for codebook-based and non-codebook-based Physical Uplink Shared Channel (PUSCH) transmissions

Cross Reference to Related Applications

The present application claims the benefit and priority of U.S. application Ser. No.17/657,512, filed on 3 months at 2022, and U.S. provisional application Ser. No.63/169,664, filed on 1 months at 2021, which have been assigned to the assignee of the present application, the entire contents of which are expressly incorporated herein by reference as if fully set forth below for all applicable purposes.

Technical Field

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for indicating capabilities of User Equipment (UE).

Background

These wireless communication systems may use multiple-access techniques that are capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). These wireless communication systems may use multiple-access techniques that are capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include third generation partnership project (3 GPP) Long Term Evolution (LTE) systems, LTE-A advanced systems, 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 so forth.

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. New Radios (NRs) (e.g., 5G NRs) are examples of emerging telecommunication standards. NR is a set of enhancements to the LTE mobile standard published by 3 GPP. NR is designed as: better support of mobile broadband internet access by improving spectral efficiency, reduced cost, improved service, use of new spectrum, and better integration with other open standards using OFDMA with Cyclic Prefix (CP) on Downlink (DL) and Uplink (UL). To this end, NR supports beamforming, multiple Input Multiple Output (MIMO) antenna techniques, and carrier aggregation.

However, as the demand for mobile broadband access continues to increase, further improvements in NR and LTE technology are needed. Preferably, these improvements should be applicable to other multiple access techniques and telecommunication standards that use these techniques.

Disclosure of Invention

The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the application, which is expressed by the claims that follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "detailed description" one will understand how the features of this disclosure provide advantages that include improved techniques for capability indication.

Certain aspects of the subject matter described in this disclosure can be implemented by a User Equipment (UE) in a method for wireless communication. The method generally comprises: an indication of the UE's ability to support Physical Uplink Shared Channel (PUSCH) transmissions with at least two duplicate sets is signaled to a network entity. Each repetition set is associated with at least one set of Sounding Reference Signal (SRS) resources. The method further comprises the steps of: a configuration of at least two SRS resource sets based on the indicated capabilities is received from the network entity. The method comprises the following steps: the SRS is transmitted on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets. The method comprises the following steps: downlink Control Information (DCI) is received from the network entity scheduling PUSCH repetition, the DCI indicating one or more SRS resources within the at least two SRS resource sets. The method further comprises the steps of: the PUSCH repetition in the two repetition sets is transmitted based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

Certain aspects of the subject matter described in this disclosure may be implemented in a method for wireless communication by a network entity. The method generally comprises: an indication of a capability of a User Equipment (UE) to support a Physical Uplink Shared Channel (PUSCH) transmission with at least two duplicate sets is received from the UE. Each repetition set is associated with at least one set of Sounding Reference Signal (SRS) resources. The method further comprises the steps of: based on the indicated capabilities, a configuration of at least two SRS resource sets is sent to the UE. The method comprises the following steps: the SRS is received on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets. The method comprises the following steps: downlink Control Information (DCI) is transmitted to the UE scheduling PUSCH repetition, the DCI indicating one or more SRS resources within the at least two SRS resource sets. The method further comprises the steps of: the PUSCH repetition in the two repetition sets is received from the UE based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

Aspects of the present disclosure provide units, devices, processors, and computer-readable media for performing the methods described herein.

Aspects of the present disclosure provide means, processors, and computer-readable media for performing techniques and methods that may be complementary to the operation of the UE (e.g., BS) described herein.

To the accomplishment of the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

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 invention, briefly summarized above, may be had by reference to some aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description herein may admit to other equally effective aspects.

Fig. 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

Fig. 2 is a block diagram conceptually illustrating a design of an example Base Station (BS) and User Equipment (UE) in accordance with certain aspects of the present disclosure.

Fig. 3 is an example of an example frame format for a New Radio (NR) in accordance with certain aspects of the present disclosure.

Fig. 4 illustrates an example non-codebook based uplink transmission in accordance with certain aspects of the present disclosure.

Fig. 5 illustrates example multiple transmit and receive point (multi-TRP) Physical Uplink Shared Channel (PUSCH) repetition in accordance with certain aspects of the disclosure.

Fig. 6 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

Fig. 7 is a flow diagram illustrating example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure.

Fig. 8 illustrates an example non-codebook based multi-TRP PUSCH transmission in accordance with certain aspects of the present disclosure.

Fig. 9 and 10 illustrate example communication devices that may include various components configured to perform operations for the techniques disclosed herein, in accordance with aspects of the present disclosure.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.

Detailed Description

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for transmitting repetitions of uplink data (e.g., physical Uplink Shared Channel (PUSCH)), e.g., for transmitting PUSCH repetitions in multiple transmission and reception points (multi-TRP) and/or multi-panel configurations. In a general aspect, the present disclosure provides techniques for signaling User Equipment (UE) capabilities for codebook-based and non-codebook-based uplink transmissions in multiple TRPs to improve reliability and robustness.

For example, the UE may signal to the network entity an indication of the ability to support PUSCH transmissions with at least two repeated sets. Each repetition set is associated with at least one set of Sounding Reference Signal (SRS) resources. The UE may receive a configuration of at least two sets of SRS resources from the network entity based on the indicated capability and transmit SRS on SRS resources within each of the at least two sets of SRS resources associated with the at least two duplicate sets. The UE may receive Downlink Control Information (DCI) from a network entity that schedules PUSCH repetition. The DCI indicates one or more SRS resources within at least two SRS resource sets. The UE may transmit PUSCH repetitions in the two repetition sets based on SRS resources within at least two SRS resource sets indicated in the DCI.

In the case of multiple TRP, different beam or power control parameters are needed when different TRP/panel/antenna on the network side wants to receive different PUSCH repetition. In some cases, PUSCH repetition may belong to two SRS resource sets, each with its own beam or power control parameters. For example, downlink Control Information (DCI) of the scheduled PUSCH may indicate two beams or two sets of power control parameters by indicating one or more SRS resources within each of the two sets of SRS resources. The present disclosure provides techniques for extending such features in the case of multiple TRP to codebook-based and non-codebook-based uplink transmissions.

For example, in codebook-based or non-codebook-based uplink transmissions, capability signaling may be extended for the number of supported SRS resources (e.g., the maximum number) across two or more SRS resource sets and the number of supported SRS resources for each of the two or more SRS resource sets. In non-codebook based uplink transmission, capability signaling may be extended to support two or more associated CSI-RS resources of two or more SRS resource sets. The indication may include a number of SRS resources associated with one CSI-RS resource or a number of SRS resources associated with one of two or more CSI-RS resources. The indication may also include a number of ports per associated CSI-RS resource, a number of ports across two CSI-RS resources (e.g., per bandwidth part (BWP) or per Component Carrier (CC)).

The following description provides examples of capability indications in a communication system and does not limit the scope, applicability, or examples recited in the claims. The function and arrangement of elements discussed may be varied without departing from the scope of the application. Various examples may omit, replace, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into certain other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Furthermore, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to or other than the aspects of the disclosure presented herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. Frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, subbands, and so forth. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs.

The techniques described herein may be used for various wireless networks and radio technologies. Although various aspects may be described herein using terms commonly associated with 3G, 4G, and/or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure may be applied to other generation-based communication systems.

NR access may support various wireless communication services, such as task-critical for enhanced mobile broadband (emmbb) for wide bandwidths (e.g., 80MHz or more), millimeter wave (mmW) for high carrier frequencies (e.g., 25GHz or more), large-scale machine type communication MTC (emtc) for non-backward compatible MTC technologies, and/or for ultra-reliable low-latency communication (URLLC). These services may include delay and reliability requirements. These services can also have different Transmission Time Intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Furthermore, these services may coexist in the same subframe. NR supports beamforming and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configuration in DL may support up to 8 transmit antennas, with multi-layer DL transmission of up to 8 streams and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells up to 8 serving cells may be supported.

Fig. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be implemented. For example, according to certain aspects, BS110 and UE120 may be configured to support PUSCH repetition. As shown in fig. 1, BS110a includes a repetition component 112.UE120a includes a repetition component 122. The repetition component 112 and the repetition component 122 may be configured to indicate or receive an indication of codebook-based and non-codebook-based multi-TRP PUSCH capabilities (e.g., in accordance with operations 600 and 700 described below with reference to fig. 6 and 7).

The wireless communication network 100 may be an NR system (e.g., a 5G NR network). As shown in fig. 1, the wireless communication network 100 may communicate with a core network 132. The core network 132 may communicate with one or more Base Stations (BSs) 110 and/or User Equipment (UEs) 120 in the wireless communication network 100 via one or more interfaces.

As shown in fig. 1, wireless communication network 100 may include a plurality of BSs 110a-z (each also referred to herein individually or collectively as BSs 110) and other network entities. BS110 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 mobile BS 110. In some examples, BS110 may be interconnected to each other and/or one or more other BSs or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. In the example shown in fig. 1, BSs 110a, 110b, and 110c may be macro BSs of macro cells 102a, 102b, and 102c, respectively. BS110x may be a pico BS of pico cell 102 x. BSs 110y and 110z may be femto BSs of femto cells 102y and 102z, respectively. The BS may support one or more cells. Network controller 130 may be coupled to a set of BSs 110 and provide coordination and control (e.g., via backhaul) for these BSs 110.

BS110 communicates with UEs 120a-y (each also referred to herein individually or collectively as UEs 120) in wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE 120 may be stationary or mobile. The wireless communication network 100 may also include relay stations (e.g., relay station 110 r), also referred to as relay stations, etc., that receive transmissions of data and/or other information from upstream stations (e.g., BS110a or UE 120 r) and send transmissions of data and/or other information to downstream stations (e.g., UE 120 or BS 110), or relay transmissions between UEs 120 to facilitate communications between devices.

According to certain aspects, BS110 and UE 120 may be configured for capability indication as shown in fig. 1, BS110a includes repetition component 112. The repetition component 112 may be configured to receive an indication of a capability of PUSCH transmission with at least two repetition sets from the UE (e.g., when each repetition set is associated with a set of SRS resources in a multi-TRP scenario). As shown in fig. 1, UE 120a includes a repetition component 122. In accordance with aspects of the present disclosure, the repetition component 122 may be configured to implement one or more techniques described herein for indicating the ability to support PUSCH transmissions with at least two repetition sets.

Although BS102 is depicted in various aspects as a single communication device, BS102 may be implemented in a variety of configurations. For example, one or more components of a base station may be broken down, including a Central Unit (CU), one or more Distributed Units (DUs), one or more Radio Units (RUs), a Near real-time (Near-RT) RAN Intelligent Controller (RIC), or a Non-real-time (Non-RT) RIC, to name a few. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components located in a single physical location or components located in various physical locations. In examples where the base station includes components located at various physical locations, the various components may each perform a function such that the various components collectively perform a function similar to a base station located at a single physical location. In some aspects, a base station comprising components located at various physical locations may be referred to as a split radio access network architecture, such as an open RAN (O-RAN) or a Virtualized RAN (VRAN) architecture.

Fig. 2 illustrates example components of BS110a and UE 120a (e.g., in wireless communication network 100 of fig. 1), which may be used to implement aspects of the present disclosure.

At BS110a, transmit processor 220 may receive data from data source 212 and control information from controller/processor 240. The control information may be used for a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), group common PDCCH (GC PDCCH), and the like. The data may be for a Physical Downlink Shared Channel (PDSCH) or the like. 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 side link shared channel (PSSCH).

Processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, e.g., for a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a channel state information reference signal (CSI-RS). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 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 a Modulator (MOD) in the transceivers 232a-232 t. Each modulator in transceivers 232a-232t may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals received from modulators in transceivers 232a-232t may be transmitted through antennas 234a-234t, respectively.

At UE 120a, antennas 252a-252r may receive the downlink signals from BS110a and may provide the received signals to a demodulator (DEMOD) in transceivers 254a-254r, respectively. Each demodulator 354 in a transceiver 254a-254r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain the received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 260, and provide decoded control information to a controller/processor 280.

On the uplink, at UE 120a, transmit processor 264 may receive and process data from data source 262 (e.g., for a Physical Uplink Shared Channel (PUSCH)) and control information from controller/processor 280 (e.g., for a Physical Uplink Control Channel (PUCCH)). The transmit processor 264 may also generate reference symbols for a reference signal (e.g., for a Sounding Reference Signal (SRS)). The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by a Modulator (MOD) in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to BS110a. At BS110a, uplink signals from UE 120a may be received by antennas 234, processed by modulators 232a-232t in the transceiver, if applicable by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120 a. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240.

Memories 242 and 282 may store data and program codes for BS110a and UE 120a, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and/or uplink.

Antenna 252, processors 266, 258, 264, and/or controller/processor 280 of UE 120a, and/or antenna 234, processors 220, 230, 238, and/or controller/processor 240 of BS110a may be used to perform the various techniques and methods described herein. For example, as shown in fig. 2, controller/processor 240 of BS110a has (may be used to implement) a repetition component 112, which repetition component 112 may be configured to perform one or more of the techniques described herein. As shown in fig. 2, controller/processor 280 of UE 120a has (may be used to implement) a repetition component 122, which repetition component 122 may be configured to perform one or more of the techniques described herein. Although shown at a controller/processor, other components of UE 120a and BS110a may be used to perform the operations described herein.

NR may use Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on uplink and downlink. NR may support half-duplex operation using Time Division Duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into a plurality of orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. The modulation symbols may be transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers may depend on the system bandwidth. The minimum resource allocation called Resource Block (RB) may be 12 consecutive subcarriers. The system bandwidth may also be divided into sub-bands. For example, one subband may cover multiple RBs. The NR may support a basic subcarrier spacing of 15kHz and may define other SCSs (e.g., 30kHz, 60kHz, 120kHz, 240kHz, etc.) relative to the basic SCS.

Fig. 3 is a diagram showing an example of a frame format 300 for NR. The transmission timeline for each of the downlink and uplink may be partitioned into radio frame units. Each radio frame can have a predetermined duration (e.g., 10 ms) and can be divided into 10 subframes with indices 0 through 9. Each subframe is 1ms. Each subframe may include a variable number of slots (e.g., 1, 2, 4, 8, 16,... Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the SCS. An index may be assigned for the symbol period in each slot. Minislots (which may be referred to as subslot structures) refer to transmission time intervals having a duration less than a slot (e.g., 2, 3, or 4 symbols). Each symbol in a slot may indicate a link direction (e.g., DL, UL, inactive, or flexible) for data transmission and may dynamically switch the link direction for each subframe. The link direction may be based on slot format. Each slot may include DL/UL data and DL/UL control information.

Example PUSCH transmission with repetition

In order to improve the reliability of data transmission, it may be necessary to repeat data transmission between a transmitting device and a receiving device. Such repeated data transmissions may increase the likelihood that the receiver receives at least one correct version of the data (and may allow soft combining of information from different repetitions). This may be particularly useful in noisy radio environments or where the channel conditions are poor.

In some cases, repeated transmission of PUSCH may be supported. For example, in release 16, two types of PUSCH repetition are defined: PUSCH repetition type a and PUSCH repetition type B (discussed below). Both types of PUSCH repetition may be applicable for uplink Configuration Grant (CG) transmission and/or uplink Dynamic Grant (DG) transmission. For PUSCH repetition type a, each repetition of PUSCH typically occurs on one or more symbols within a given slot. However, for PUSCH repetition type B, a given repetition of PUSCH may occur on one or more symbols across slot boundaries.

Furthermore, release 15 or release 16 supports two types of PUSCH transmissions, namely codebook-based and non-codebook-based PUSCH transmissions. In codebook-based transmission, the UE may be configured with one set of SRS resources, with "use" set to "codebook". The UE may be configured with a maximum number of four SRS resources within the SRS resource set. Each SRS resource is configured with multiple Ports (nrofSRS-Ports) through RRC. An SRS Resource Indicator (SRI) field in Uplink (UL) DCI (scheduled PUSCH) indicates 1 SRS resource. The number of ports configured for the indicated SRS resource determines the number of antenna ports of the PUSCH. PUSCH is transmitted using the same spatial domain filter (i.e., UL beam) as the indicated SRS resource. The number of layers (rank) and TPMI (precoder) for the scheduled PUSCH may be determined from separate DCI fields (e.g., "precoding information and number of layers").

In non-codebook based transmission, the UE may be configured with one SRS resource set, with "use" set to "non-codebook". Similar to the codebook-based case, the UE may be configured with a maximum number of four SRS resources within the SRS resource set. The UE may be configured with a maximum number of four SRS resources within the SRS resource set. Each SRS resource has one port. The SRI field in UL DCI (scheduled PUSCH) indicates one or more SRS resources. The number of SRS resources indicated determines the rank (i.e. the number of layers) of the scheduled PUSCH. PUSCH is transmitted using the same precoder and spatial domain filters (i.e., beams) as the indicated SRS resources (indicated by the SRI). The SRS resource set may optionally be configured with one associated NZP CSI-RS resource (via RRC parameters associated with CSI-RS). The UE may calculate a precoder for the transmission of SRS resources within the set based on the measurements of the associated NZP CSI-RS resources.

PUSCH repetition type a can have a similar design as PUSCH defined in release 15. For example, one PUSCH transmission instance is not allowed to span the slot boundaries of DG and CG PUSCHs. To avoid transmitting long PUSCH across slot boundaries, the UE may transmit small PUSCH in several repetitions of UL grant or RRC scheduling in consecutive available slots. If the number of repetitions K >1, the same Start and Length Indicator (SLIV) is applied across K consecutive slots (where SLIV indicates the start symbol and length of PUSCH).

Fig. 4 shows an exemplary non-codebook based uplink transmission, e.g., in release 15. As shown, the UE may measure non-zero power (NZP) CSI-RS resources based on which the UE computes a precoder to use transmissions of each SRS resource within the set. The UE transmits SRS resources (e.g., four SRS resources shown in the SRS resource set). The network or base station (e.g., gNB) receives the precoded SRS resources from the UE and selects one or more SRS resources to indicate in the UL DCI for PUSCH scheduling (e.g., based on some metric). The base station transmits UL DCI to the UE. UL DCI in slot n schedules PUSCH transmission in later slot n+x and indicates SRI. The indicated SRI is associated with a most recent transmission of SRS resources identified by the SRI. The SRS transmission precedes the PDCCH carrying the SCI.

After receiving the UL DCI from the base station, the UE transmits PUSCH based on the indicated SRS resource indicated by the UL DCI. For example, assuming that the SRI indicates SRS resources 0 and 2 (and assuming that the PUSCH has two layers), each layer is transmitted with the same precoding and beam as used for transmitting SRS resources 0 and 2.

According to certain aspects of the disclosure, the UE may indicate the following capabilities. First, the UE may indicate codebook-based and non-codebook-based capabilities (in some cases, separately). For example, in maxNumberSRS-resource set, the UE may define a maximum number of SRS resources for each SRS resource set configured for codebook-based or non-codebook-based transmission to the UE. The indication is for each CC of each frequency band of the supported combination of frequency bands.

Second, the UE may indicate SRS-AssocCSI-RS, which defines parameters for calculating a precoder for SRS transmission based on channel measurements using associated NZP CSI-RS resources. The indication is limited to parameters of non-codebook based uplink transmissions and associated CSI-RS resources. The capability signaling includes the following list of parameters: (1) maxnumbertxportsresource, which indicates the maximum number of Tx ports in the resource; (2) maxnumberResourcesPerband, the maximum number of resources that all CCs in its band possess at the same time; (3) total number txport per band, which indicates the total number of Tx ports within the band across all CCs simultaneously.

Third, the UE may indicate CSI-RS-procaramework for SRS, which indicates support for CSI-RS processing framework for SRS. This may only apply to non-codebook based uplink transmissions. The capability signaling includes the following parameters: (1) maxnumberperiodic SRS-associcsi-RS-PerBWP indicating a maximum number of periodic SRS resources associated with CSI-RS of each BWP; (2) maxnumberAperiodicSRS-associCSI-RS-PerBWP indicating a maximum number of aperiodic SRS resources associated with the CSI-RS of each BWP; (3) maxnumbersps-SRS-AssocCSI-RS-PerBWP indicating a maximum number of semi-persistent SRS resources associated with CSI-RS of each BWP; (4) The simultaneousSRS-AssocCSI-RS-PerCC, which indicates the number of SRS resources that a UE can process simultaneously in one CC, including periodic, aperiodic, and semi-persistent SRS.

Finally, the UE may indicate a simultaneousSRS-AssocCSI-RS-all CC indicating support for a CSI-RS processing framework for SRS and the number of SRS resources that the UE may process simultaneously on all CCs, and in the case of NR-DC, the number of SRS resources that the UE may process simultaneously across MCG and SCG, including periodic, aperiodic, and semi-persistent SRS. The parameter may also limit the simultaneousSRS-AssocCSI-RS-PerCC in MIMO-ParametersPerBand and Phy-ParametersFRX-Diff for each band in a given band combination. This may only apply to non-codebook based uplink transmissions.

Fig. 5 illustrates example multiple transmit and receive point (multi-TRP) Physical Uplink Shared Channel (PUSCH) repetition in accordance with certain aspects of the disclosure. Since a multi-TRP or multi-panel is intended to improve the reliability and robustness of PUSCH transmissions, when one link (e.g., to one TRP) is blocked, another repetition may be decoded by another TRP (or panel).

In an aspect, PUSCH repetition includes type a and type B. Different PUSCH transmission opportunities (i.e., repetitions) corresponding to the same TB are transmitted in different slots or minislots. The number of repetitions may be RRC configured (e.g., in rel.15) or may be indicated dynamically (e.g., rel.16) by a Time Domain Resource Allocation (TDRA) field of the DCI. In some cases, all repetitions may be transmitted using the same beam (the SRI field of DCI applies to all repetitions).

When different TRPs (or panels/antennas) on the network side want to receive different PUSCH repetitions, different beam or power control parameters are needed. For example, as shown in fig. 5, PUSCH repetition may belong to two sets, each set having its own beam, power control, and other parameters or settings. The UP DCI schedules four PUSCH repetitions and includes two SRI fields to indicate SRS resources of each of two SRS resource sets. Each PUSCH repetition set uses a respective beam and/or power control parameter of a respective TRP. That is, the two repeated sets correspond to two SRS resource sets (DCI indicates two beams/two power control parameter sets by indicating one or more SRS resources within each of the two SRS resource sets).

Capability for multi-TRP PUSCH based on codebook and non-codebook

To fully exploit the above-described features that increase signal diversity and thus reliability and robustness in multi-TRP PUSCH repetition, aspects of the present disclosure extend multi-TRP capability signaling for codebook-based and non-codebook-based uplink transmissions. For example, the UE may signal to the network entity an indication of the ability to support PUSCH transmissions with at least two duplicate sets associated with different SRS resource sets.

Fig. 6 is a flow chart illustrating example operations 600 for wireless communication in accordance with certain aspects of the present disclosure. The operations 600 may be performed, for example, by a UE (e.g., the UE 120a in the wireless communication network 100).

The operations 600 may be implemented as software components executing and running on one or more processors (e.g., the controller/processor 260 of fig. 2). Further, the transmission and reception of signals by the UE in operation 600 may be implemented, for example, by one or more antennas (e.g., antenna 252 of fig. 2). 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 260) that obtain and/or output the signals.

Operation 600 begins at 610, where an indication of a UE's ability to support PUSCH transmissions with at least two repeated sets is signaled to a network entity. Each of the at least two repeated sets is associated with at least one set of Sounding Reference Signal (SRS) resources.

At 620, the UE receives from the network entity a configuration of at least two SRS resource sets based on the indicated capabilities. At 630, the UE transmits SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets.

At 640, the UE receives Downlink Control Information (DCI) from the network entity that schedules PUSCH repetition. The DCI indicates one or more SRS resources within at least two SRS resource sets.

At 650, the UE transmits PUSCH repetitions in two repetition sets based on SRS resources within at least two SRS resource sets indicated in the DCI.

Fig. 7 is a flow chart illustrating example operations 700 for wireless communication in accordance with certain aspects of the present disclosure. The operations 700 may be performed, for example, by a network entity (e.g., BS110a or a CU, DU, or RU of an exploded base station in the wireless communication network 100). Operation 700 may be a supplemental operation to operation 600 performed by the network entity on the UE.

The operations 700 may be implemented as software components executing and running on one or more processors (e.g., the controller/processor 240 of fig. 2). Further, the transmission and reception of signals by the network entity in operation 700 may be implemented, for example, by one or more antennas (e.g., antenna 234 of fig. 2). 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 240) that obtain and/or output the signals.

The operations 700 begin at 710, where an indication of a UE's ability to support PUSCH transmissions with at least two repeated sets is received. Each repetition set is associated with at least one SRS resource set. At 720, the network entity transmits a configuration of at least two SRS resource sets based on the indicated capabilities.

At 730, the network entity receives the SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets. At 740, the network entity transmits DCI scheduling PUSCH repetition, the DCI indicating one or more SRS resources within the at least two SRS resource sets.

At 750, the network entity receives PUSCH repetitions in two repetition sets based on SRS resources within at least two SRS resource sets indicated in the DCI.

Fig. 8 illustrates an example of non-codebook based multi-TRP PUSCH transmission in accordance with operations 600 and 700. As shown in the timeline 800 of fig. 8, the UE first indicates to the network entity the described capabilities including, for example, a non-codebook based mTRP PUSCH (two SRS resource sets), e.g., 4 SRS resources within each SRS resource set, 6 SRS resources across the two SRS resource sets, two associated CSI-RS resources per BWP, two SRS resources associated with CSI-RS resources per BWP, 4 SRS resources associated with either CSI-RS resource per BWP.

The network entity then configures two SRS resource sets, the purpose of which is set to "non-codebook", each SRS resource set being configured with 2 SRS resources and associated CSI-RS resources. In some cases, the SRS resource set may be configured with only one SRS resource.

The UE may then measure CSI-RS resources according to the first TRP and precode SRS resources within the corresponding SRS resource set. This is shown as the UE measuring the first NZP CSI-RS resource on the left side of fig. 8. The UE may then calculate a precoder for the transmission of each SRS resource within the set. The UE may also measure CSI-RS resources according to the second TRP and precode SRS resources within the corresponding SRS resource set. This is shown as the UE measuring the second NZP CSI-RS resource in the middle of fig. 8.

When the network entity receives the precoded SRS resources, the network entity selects one or more SRS resources within the first or second set of SRS resources to indicate in the UL DCI for PUSCH scheduling. That is, the network entity schedules PUSCH using two duplicate sets and indicates one or more SRS resources within the first SRS resource set and one or more SRS resources within the second SRS resource set (based on received SRS resources).

The UE receives UL DCI from the network. The UE transmits PUSCH (two repetition sets) based on SRS resources indicated within the two SRS resource sets.

In some aspects, the UE indicates that the UE supports the individual capabilities of: codebook-based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets; and a non-codebook based PUSCH transmission with at least two repeated sets associated with the at least two SRS resource sets.

In some aspects, a UE indicates that the UE supports the individual capabilities of: PUSCH transmissions having at least two repeated sets of a first type associated with at least two SRS resource sets; and PUSCH transmissions with at least two repeated sets of a second type associated with the at least two SRS resource sets.

In some aspects, the UE indicates: the number of supported SRS resources across at least two SRS resource sets. In some cases, the UE further indicates: for a bandwidth part (BWP) and Component Carrier (CC) combination configured with at least two SRS resource sets, the number of SRS resources supported by each SRS resource set.

For example, in the first option, in addition to "maxNumberSRS-resourceuserset" specified in release 15, new capabilities may be added to indicate the number of SRS resources supported across the two SRS resource sets (i.e., associated with different TRPs). For example, the UE may indicate four SRS resources per SRS resource set and six SRS resources across two SRS resource sets. Different numbers of SRS resources of the two or more SRS resource sets may be indicated in different scenarios. In some cases, the UE may indicate the number of SRS resources supported per SRS resource set. In some cases, the UE may indicate different numbers of SRS resources supported by different sets of SRS resources. In some cases, the UE may indicate a different number of SRS resources for each SRS set or for different scenarios.

In a second option, in addition to interpreting version 15 "maxnumbersts-resource set" as the number of SRS resources supported across the two SRS resource sets, new capabilities may be added to indicate the number of SRS resource sets supported per SRS resource set specific to the BWP and/or CC (which is configured with the two SRS resource sets).

In a third option, two new capabilities are added to indicate the number of SRS resources supported per SRS resource set and the number of SRS resources supported across the two SRS resource sets. These functions are specific to a BWP/CC configured with two SRS resource sets.

In some cases, the UE also indicates the number of supported SRS resources per BWP associated with any CSI-RS resource. For example, new capabilities specific to a BWP and/or CC configured with two SRS resource sets may be added to indicate the number of SRS resources supported by each SRS resource set and the number of SRS resources supported across the two SRS resource sets.

For example, "CSI-RS-procaramework for SRS" is used to indicate the maximum number of SRS resources per BWP associated with one of the CSI-RS resources. When the UE indicates that each CC supports 2 associated CSI-RS resources per BWP, the UE may also indicate a maximum number of SRS resources supported by each BWP associated with either of the two CSI-RS resources (i.e., the number of SRS resources across the two SRS resource sets when each of the two SRS resource sets is configured with associated CSI-RS resources). This capability may be separate for the number of periodic, aperiodic, or semi-persistent SRS resources per BWP and the number of SRS resources that the UE may process simultaneously in the CC (including periodic, aperiodic, and semi-persistent SRS).

The number of SRS resources associated with the CSI-RS may also be indicated according to three options. In a first option, in addition to indicating the maximum number of SRS resources per BWP associated with one of the CSI-RS resources, when the UE indicates that 2 associated CSI-RS resources are supported per BWP per CC, new capabilities may be added to indicate the maximum number of SRS resources supported per BWP associated with either of the two CSI-RS resources (i.e., the number of SRS resources across the two sets of SRS resources when each of the two sets of SRS resources is configured with associated CSI-RS resources). In a second option, in addition to indicating the maximum number of SRS resources across associated CSI-RS resources, a new capability may be added to indicate the maximum number of SRS resources per associated CSI-RS resource. In a third option, two new capabilities may be added, including one capability for the number of SRS resources supported by each associated CSI-RS resource and another capability for the number of SRS resources supported across associated CSI-RS resources.

In some aspects, when the UE indicates that the UE supports a capability of non-codebook based PUSCH transmission with at least two sets of repetition associated with at least two sets of SRS resources, the UE may also indicate support for one or more associated CSI-RS resources for calculating a precoder for SRS transmission using CSI-RS measurements. In some cases, the UE indicates the number of associated CSI-RS resources for each BWP and CC combination. In some cases, the UE also indicates a number of supported CSI-RS ports across associated CSI-RS resources.

In the first option, in addition to the capability of 15 for the maximum number of ports per associated CSI-RS resource (interchangeable with the number of ports supported) of the version indicated by "maxnumbertxportsresource", a new capability is added to indicate the number of CSI-RS ports supported across associated CSI-RS resources. In a second option, in addition to the capability indicated by "maxnumbertxportsresource" for the maximum number of ports on the cross-associated CSI-RS resource, a new capability is added to indicate the maximum number of ports for each associated CSI-RS resource. In a third option, two new capabilities are added, including one capability for the number of CSI-RS ports supported by each associated CSI-RS resource and another capability for the number of CSI-RS ports supported across associated CSI-RS resources.

For example, when the UE indicates support for a non-codebook based mTRP PUSCH (two SRS resource sets with use set to "non-codebook"), the UE may also indicate support for associated CSI-RS resources that use CSI-RS measurements for computing a precoder for SRS transmission. The UE may indicate the number of associated CSI-RS resources (e.g., 1 or 2 CSI-RS resources) per BWP per CC. For example, if the UE indicates support of 1 CSI-RS resource per BWP per CC, only one of the two SRS resource sets may be configured with associated CSI-RS resources.

In some cases, for example, in non-codebook based uplink transmissions, the configuration of the at least two SRS resource sets received from the network entity indicates SRS resources within each of the at least two SRS resource sets and associated CSI-RS resources configured for each of the at least two SRS resource sets. In some cases, the UE also measures CSI-RS on CSI-RS resources configured for each of the at least two SRS resource sets. The UE calculates a precoder based on CSI-RS measurements; and applying the precoder when transmitting SRS on SRS resources within each of at least two SRS resource sets associated with the at least two repetition sets.

In some aspects, the UE further indicates at least one of: the number of different spatial relationship information that different SRS resources can have across at least two SRS resource sets; or the number of different spatial relationship information that different SRS resources can have for each SRS resource set. For example, the UE may also indicate the number of different spatial relationship information (UL beams) that different SRS resources may have across the or each SRS resource set. For example, the UE may support 4 SRS resources per set and 8 SRS resources across two sets, but only one spatial relationship information for all SRS resources within one set and two spatial relationship information for all SRS resources across two sets, i.e. all SRS resources in one set should be configured with the same spatial relationship information.

In some aspects, when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repetition sets associated with at least two SRS resource sets, the UE further indicates at least one of: whether different SRS resources can have different numbers of SRS ports in the SRS resource set; or whether different SRS resources can have different numbers of SRS ports across at least two SRS resource sets. In some cases, the UE also indicates a number of SRS ports that each SRS resource may be configured for a first set of SRS resources of the at least two sets of SRS resources and a second set of SRS resources of the at least two sets of SRS resources. For example, the UE may also indicate whether different SRS resources may be within an SRS resource set and have different numbers of ports across two SRS resource sets. In addition, the UE may indicate a number of SRS ports that each SRS resource may configure for the first SRS resource set and the second SRS resource set. For example, the UE may support 1, 2, 4 ports when configured with 1 SRS resource set (not configured with mTRP PUSCH), but only 1 and 2 ports for each SRS resource when configured with 2 SRS resource sets (mTRP PUSCH).

Fig. 9 illustrates a communication device 900 that may include various components (e.g., corresponding to the unit plus function components) configured to perform the operations of the techniques disclosed herein (e.g., the operations shown in fig. 6). The communication device 900 includes a processing system 902 coupled to a transceiver 908 (e.g., a transmitter and/or receiver). The transceiver 908 is configured to transmit and receive signals of the communication device 900, such as the various signals described herein, via the antenna 910. The processing system 902 may be configured to perform the processing functions of the communication device 900, including processing signals received and/or to be transmitted by the communication device 900.

The processing system 918 includes a processor 904 coupled to a computer-readable medium/memory 912 via a bus 906. In certain aspects, the computer-readable medium/memory 912 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 904, cause the processor 904 to perform the operations shown in fig. 6 and/or other operations for performing the various techniques discussed herein. In certain aspects, the computer-readable medium/memory 912 stores: code 922 for signaling to a network entity an indication of a capability of the UE to support Physical Uplink Shared Channel (PUSCH) transmission with at least two repeated sets, wherein each repeated set is associated with at least one set of Sounding Reference Signal (SRS) resources; code 924 for receiving a configuration of at least two SRS resource sets based on the indicated capabilities from a network entity; code 926 for transmitting SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets; code 928 for receiving Downlink Control Information (DCI) from a network entity, the DCI indicating one or more SRS resources within at least two SRS resource sets, scheduling PUSCH repetition; and code 930 for transmitting PUSCH repetitions in the two repetition sets based on SRS resources within the at least two SRS resource sets indicated in the DCI.

In certain aspects, the processor 904 has circuitry configured to implement code stored in the computer-readable medium/memory 912. The processor 904 includes: circuitry 932 for signaling to a network entity an indication of a capability of a UE to support PUSCH transmission with at least two repetition sets, wherein each repetition set is associated with at least one SRS resource set; circuitry 934 for receiving, from a network entity, a configuration of at least two SRS resource sets based on the indicated capabilities; circuitry 936 to transmit SRS on SRS resources within each of at least two SRS resource sets associated with the at least two repetition sets; circuitry 938 for receiving Downlink Control Information (DCI) from a network entity, the DCI indicating one or more SRS resources within at least two SRS resource sets, scheduling PUSCH repetition; and circuitry 940 to transmit PUSCH repetitions in the two repetition sets based on SRS resources within the at least two SRS resource sets indicated in the DCI.

Fig. 10 illustrates a communication device 1000 that may include various components (e.g., corresponding to the unit plus function components) configured to perform the operations of the techniques disclosed herein (e.g., the operations shown in fig. 7). The communication device 1000 includes a processing system 1002 coupled to a transceiver 1008 (e.g., a transmitter and/or a receiver). The transceiver 1008 is configured to transmit and receive signals of the communication device 1000, such as the various signals described herein, via the antenna 1010. The processing system 1002 may be configured to perform processing functions of the communication device 1000, including processing signals received and/or to be transmitted by the communication device 1000.

The processing system 1018 includes a processor 1004 coupled to a computer-readable medium/memory 1012 via a bus 1006. In certain aspects, the computer-readable medium/memory 1012 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1004, cause the processor 1004 to perform the operations shown in fig. 7 and/or other operations for performing the various techniques discussed herein. In certain aspects, the computer-readable medium/memory 1012 stores: code 1022 for receiving an indication of a capability of a UE to support PUSCH transmission with at least two repeated sets, wherein each repeated set is associated with at least one SRS resource set; code 1024 for transmitting a configuration of at least two SRS resource sets based on the indicated capabilities; code 1026 for receiving SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets; code 1028 for transmitting Downlink Control Information (DCI) scheduling PUSCH repetition, the DCI indicating one or more SRS resources within at least two SRS resource sets; and code 1030 for receiving PUSCH repetitions in the two repetition sets based on SRS resources within the at least two SRS resource sets indicated in the DCI.

In certain aspects, the processor 1004 has circuitry configured to implement code stored in the computer-readable medium/memory 1012. The processor 1004 includes: circuitry 1032 to receive an indication of a capability of a UE to support PUSCH transmission with at least two repetition sets, wherein each repetition set is associated with at least one SRS resource set; circuitry 1034 for transmitting a configuration of at least two SRS resource sets based on the indicated capabilities; circuitry 1036 for receiving SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets; circuitry 1038 to transmit Downlink Control Information (DCI) scheduling PUSCH repetition, the DCI indicating one or more SRS resources within the at least two SRS resource sets; and circuitry 1040 to receive PUSCH repetitions in the two repetition sets based on SRS resources within the at least two SRS resource sets indicated in the DCI.

Example clauses

An example of an embodiment is described in the following numbered clauses:

clause 1: a method for wireless communication by a User Equipment (UE), comprising: signaling to a network entity an indication of the UE's ability to support Physical Uplink Shared Channel (PUSCH) transmissions with at least two repeated sets, wherein each repeated set is associated with at least one set of Sounding Reference Signal (SRS) resources; receiving, from the network entity, a configuration of at least two SRS resource sets based on the indicated capabilities; transmitting SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets; receiving Downlink Control Information (DCI) from the network entity, the DCI indicating one or more SRS resources within the at least two SRS resource sets, the PUSCH repetition being scheduled; and transmitting the PUSCH repetition in the two repetition sets based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

Clause 2: the method of clause 1, wherein the UE indicates that the UE supports the individual capability of: codebook-based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets; and a non-codebook based PUSCH transmission with at least two repeated sets associated with the at least two SRS resource sets.

Clause 3: the method of any of clauses 1-2, wherein the UE indicates that the UE supports individual capabilities of: PUSCH transmissions having at least two repeated sets of a first type associated with at least two SRS resource sets; and PUSCH transmissions with at least two repeated sets of a second type associated with the at least two SRS resource sets.

Clause 4: the method of any of clauses 1-3, wherein the UE indicates: the number of supported SRS resources across the at least two SRS resource sets.

Clause 5: the method of clause 4, wherein the UE further indicates: for a bandwidth part (BWP) and Component Carrier (CC) combination configured with at least two SRS resource sets, the number of SRS resources supported by each SRS resource set.

Clause 6: the apparatus of clause 4, wherein the UE indicates a number of the supported SRS resources across at least two SRS resource sets for a bandwidth portion (BWP) and Component Carrier (CC) combination configured with the at least two SRS resource sets.

Clause 7: the method of any of clauses 1-6, wherein when the UE indicates that the UE supports a capability of non-codebook based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates support for computing one or more associated CSI-RS resources for a precoder for SRS transmission using channel state information reference signal (CSI-RS) measurements.

Clause 8: the method of clause 7, wherein the UE indicates a number of associated CSI-RS resources per bandwidth part (BWP) and Component Carrier (CC) combination.

Clause 9: the method of clause 8, wherein the UE further indicates: the number of supported CSI-RS ports across the associated CSI-RS resource.

Clause 10: the method of clause 8, wherein the UE further indicates: the number of supported SRS resources per BWP associated with any one of the CSI-RS resources.

Clause 11: the method of clause 7, wherein the configuration of at least two SRS resource sets received from the network entity indicates SRS resources within each of the at least two SRS resource sets and associated CSI-RS resources configured for each of the at least two SRS resource sets.

Clause 12: the method of clause 11, further comprising: measuring CSI-RS on the CSI-RS resources configured for each of the at least two SRS resource sets; calculating a precoder based on the CSI-RS measurements; and applying the precoder when the SRS is transmitted on SRS resources within each of at least two SRS resource sets associated with the at least two repetition sets.

Clause 13: the method of any of clauses 1-12, wherein the UE further indicates at least one of: the number of different spatial relationship information that different SRS resources can have across the at least two SRS resource sets; or the number of different spatial relationship information that different SRS resources can have for each SRS resource set.

Clause 14: the method of any of clauses 1-13, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates at least one of: whether different SRS resources can have different numbers of SRS ports in the SRS resource set; or whether different SRS resources can have different numbers of SRS ports across the at least two SRS resource sets.

Clause 15: the method of any of clauses 1-14, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two sets of SRS resources, the UE further indicates a number of SRS ports each SRS resource may be configured with for a first set of SRS resources of the at least two sets of SRS resources and a second set of SRS resources of the at least two sets of SRS resources.

Clause 16: a method for wireless communication by a network entity, comprising: receiving, from a User Equipment (UE), an indication of a capability of the UE to support a Physical Uplink Shared Channel (PUSCH) transmission having at least two repeated sets, wherein each repeated set is associated with at least one set of Sounding Reference Signal (SRS) resources; transmitting a configuration of at least two SRS resource sets to the UE based on the indicated capabilities; receiving SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets; transmitting Downlink Control Information (DCI) to the UE that schedules PUSCH repetition, the DCI indicating one or more SRS resources within the at least two SRS resource sets; and receiving the PUSCH repetition in the two repetition sets from the UE based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

Clause 17: the method of clause 16, wherein the UE indicates that the UE supports the individual capability of: codebook-based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets; and a non-codebook based PUSCH transmission with at least two repeated sets associated with the at least two SRS resource sets.

Clause 18: the method of any of clauses 16-17, wherein the UE indicates that the UE supports individual capabilities of: PUSCH transmissions having at least two repeated sets of a first type associated with at least two SRS resource sets; and PUSCH transmissions with at least two repeated sets of a second type associated with the at least two SRS resource sets.

Clause 19: the method of any of clauses 16-18, wherein the UE indicates: the number of supported SRS resources across the at least two SRS resource sets.

Clause 20: the method of clause 19, wherein the UE further indicates: for a bandwidth part (BWP) and Component Carrier (CC) combination configured with at least two SRS resource sets, the number of SRS resources supported by each SRS resource set.

Clause 21: the apparatus of clause 19, wherein the UE indicates a number of the supported SRS resources across at least two SRS resource sets for a bandwidth portion (BWP) and Component Carrier (CC) combination configured with the at least two SRS resource sets.

Clause 22: the method of any of clauses 16-21, wherein when the UE indicates that the UE supports a capability of non-codebook based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates support for computing one or more associated CSI-RS resources for a precoder for SRS transmission using channel state information reference signal (CSI-RS) measurements.

Clause 23: the method of clause 22, wherein the UE indicates a number of associated CSI-RS resources per bandwidth part (BWP) and Component Carrier (CC) combination.

Clause 24: the method of clause 23, wherein the UE further indicates: the number of supported CSI-RS ports across the associated CSI-RS resource.

Clause 25: the method of clause 23, wherein the UE further indicates: the number of supported SRS resources for each BWP associated with any one of the CSI-RS resources.

Clause 26: the method of clause 22, wherein the configuration of at least two SRS resource sets received from the network entity indicates SRS resources within each of the at least two SRS resource sets and associated CSI-RS resources configured for each of the at least two SRS resource sets.

Clause 27: the method of any of clauses 16-26, wherein the UE further indicates at least one of: the number of different spatial relationship information that different SRS resources can have across the at least two SRS resource sets; or the number of different spatial relationship information that different SRS resources can have for each SRS resource set.

Clause 28: the method of any of clauses 16-27, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates at least one of: whether different SRS resources can have different numbers of SRS ports in the SRS resource set; or whether different SRS resources can have different numbers of SRS ports across the at least two SRS resource sets.

Clause 29: the method of any of clauses 16-28, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two sets of SRS resources, the UE further indicates a number of SRS ports each SRS resource may be configured with for a first set of SRS resources of the at least two sets of SRS resources and a second set of SRS resources of the at least two sets of SRS resources.

Clause 30: an apparatus, comprising: a memory comprising executable instructions; one or more processors configured to execute the executable instructions and cause the apparatus to perform a method according to any of clauses 1-29.

Clause 31: an apparatus comprising means for performing a method according to any of clauses 1-29.

Clause 32: a non-transitory computer-readable medium comprising executable instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform a method according to any of clauses 1-29.

Clause 33: a computer program product embodied on a computer-readable storage medium comprising code for performing a method according to any of clauses 1-29.

Additional considerations

The techniques described herein may be used for various wireless communication techniques such as NR (e.g., 5G NR), 3GPP Long Term Evolution (LTE), LTE-advanced (LTE-A), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal Frequency Division Multiple Access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), and other networks. The terms "network" and "system" are generally used interchangeably. A CDMA network may implement wireless technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks may implement wireless technologies such as global system for mobile communications (GSM). OFDMA networks may implement wireless technologies such as NR (e.g., 5G RA), evolved UTRA (E-UTRA), ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, flash OFDM, etc. UTRA and E-UTRA are components of Universal Mobile Telecommunications System (UMTS). LTE and LTE-a are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a and GSM are described in documents provided by an organization named "third generation partnership project" (3 GPP). Cdma2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3 GPP 2). NR is an emerging wireless communication technology being developed.

In 3GPP, the term "cell" can refer to a coverage area of a Node B (NB) and/or an NB subsystem serving the coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and BS, next generation NodeB (gNB or gnob) Access Point (AP), distributed Unit (DU), carrier, or transmission-reception point (TRP) may be used interchangeably. The BS may provide communication coverage for macro cells, pico cells, femto cells, and/or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a few kilometers in radius) and allow unrestricted access by UEs with service subscription. The pico cell may cover a relatively small geographic area and allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., home) and allow limited access for UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users at home, etc.). The BS of a macro cell may be referred to as a macro BS. The BS of the pico cell may be referred to as a pico BS. The BS of the femto cell may be referred to as a femto BS or a home BS.

The UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer Premises Equipment (CPE), cellular telephone, smart phone, personal Digital Assistant (PDA), wireless modem, wireless communication device, handheld device, laptop, cordless telephone, wireless Local Loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, superbook, appliance, medical device or equipment, biometric sensor/device, wearable device (e.g., smart watch, smart garment, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter/sensor, industrial manufacturing device, global positioning system device, or any other suitable device configured to communicate via a wireless medium or wired medium. Some UEs may be considered Machine Type Communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that may communicate with a BS, another device (e.g., a remote device), or some other entity. The wireless node may provide, for example, a connection to a network or to a network (e.g., a wide area network such as the internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered internet of things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communications between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources of one or more subordinate entities. That is, for scheduled communications, the subordinate entity uses the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may serve as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may communicate wirelessly using the resources scheduled by the UE. In some examples, the UE may be used as a scheduling entity in a peer-to-peer (P2P) network and/or a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

The methods disclosed herein comprise one or more steps or actions for achieving these methods. These method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with a plurality of the same elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-c, c-c, and c-c, or any other ordering of a, b, and c).

As used herein, the term "determining" includes various actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Further, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so forth. Further, "determining" may include resolving, picking, selecting, establishing, and the like.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects shown herein, but are to be accorded the full scope of the claim language, wherein, unless specifically stated otherwise, singular elements do not mean "one and only one" but rather "one or more". The term "some" refers to one or more unless specifically stated otherwise. All structures and functions known or to be known to those of ordinary skill in the art as equivalent to elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. Unless the phrase "unit for … …" is used to explicitly recite a claim element, or in the case of a method claim, the phrase "step for … …" is used to recite a claim element, such claim element must not be interpreted in accordance with the specification of 35u.s.c. ≡112 (f).

The various operations of the above-described methods may be performed by any suitable unit capable of performing the corresponding functions. These units may include various hardware and/or software components and/or modules including, but not limited to, circuits, application Specific Integrated Circuits (ASICs), or processors. Generally, where operations shown in the figures are present, those operations can have corresponding functional module assemblies with like reference numerals.

The various illustrative logical blocks, modules, and circuits described in connection with the present application may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

If implemented in hardware, an exemplary hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including processors, machine-readable media, and bus interfaces. The bus interface may be used to connect network adapters and others to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal (see fig. 1), a user interface (e.g., a key, a display, a mouse, a joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented using one or more general-purpose processors and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how to best implement the described functionality for the processing system depending on the particular application and overall design constraints imposed on the overall system.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should be construed broadly as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on a machine-readable storage medium. A computer readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. For example, a machine-readable medium may include a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium separate from the wireless node having instructions stored thereon, all of which may be accessed by a processor through a bus interface. Alternatively, or in addition, the machine-readable medium, or any portion thereof, may be an integral part of the processor, such as may be the case with cache and/or general purpose register files. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, a magnetic disk, an optical disk, a hard disk drive, or any other storage medium, or any combination thereof. The machine-readable medium may be embodied by a computer program product.

A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across several storage media. The computer readable medium may include a plurality of software modules. The software modules include instructions that, when executed by a device, such as a processor, cause the processing system to perform various functions. The software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. For example, when a trigger event occurs, a software module may be loaded from a hard disk drive into RAM. During execution of the software module, the processor may load some instructions into the cache to increase access speed. One or more cache lines may then be loaded into a general purpose register file for execution by a processor. When referring to the functionality of the following software modules, it should be understood that: such functions are implemented by the processor when executing instructions from the software module.

Further, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, and microwave, then the definition of medium includes the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and optical disc Optical discs, in which a magnetic disc usually magnetically replicates data, and optical discs use laser light to optically replicate data. Thus, inIn certain aspects, the computer-readable medium may comprise a non-transitory computer-readable medium (e.g., a tangible medium). In addition, for other aspects, the computer-readable medium may include a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

Accordingly, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and/or encoded) thereon that are executable by one or more processors to perform the operations described herein, e.g., instructions for performing the operations described herein and shown in fig. 6 and 7.

Furthermore, it should be understood that: the user terminal and/or base station can download and/or otherwise obtain modules and/or other suitable elements for performing the methods and techniques described herein, as appropriate. For example, such a device may be coupled to a server to facilitate transmission of elements for performing the methods described herein. Alternatively, the various methods described herein may be provided via a storage module (e.g., RAM, ROM, a physical storage medium such as a Compact Disc (CD) or floppy disk, etc.) so that the various methods are available to a user terminal and/or base station when coupled to or provided with the device. Further, any other suitable technique for providing the methods and techniques described herein to a device may be used.

It should be understood that: the claims are not limited to the precise configurations and components described above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. An apparatus for wireless communication at a User Equipment (UE), comprising:

a processor;

a memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the device to:

signaling to a network entity an indication of the UE's ability to support Physical Uplink Shared Channel (PUSCH) transmissions with at least two repeated sets, wherein each repeated set is associated with at least one set of Sounding Reference Signal (SRS) resources;

receiving, from the network entity, a configuration of at least two SRS resource sets based on the indicated capabilities;

transmitting SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets;

receiving Downlink Control Information (DCI) from the network entity, the DCI indicating one or more SRS resources within the at least two SRS resource sets, the PUSCH repetition being scheduled; and

The PUSCH repetition in the two repetition sets is transmitted based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

2. The apparatus of claim 1, wherein the UE indicates that the UE supports individual capabilities of:

codebook-based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets; and

non-codebook based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets.

3. The apparatus of claim 1, wherein the UE indicates that the UE supports individual capabilities of:

PUSCH transmissions having at least two repeated sets of a first type associated with at least two SRS resource sets; and

PUSCH transmissions having at least two duplicate sets of a second type associated with the at least two SRS resource sets.

4. The apparatus of claim 1, wherein the UE indicates:

the number of supported SRS resources across the at least two SRS resource sets.

5. The apparatus of claim 4, wherein the UE further indicates:

for a bandwidth part (BWP) and Component Carrier (CC) combination configured with at least two SRS resource sets, the number of supported SRS resources for each SRS resource set.

6. The apparatus of claim 4, wherein the UE indicates a number of the supported SRS resources across at least two SRS resource sets for a bandwidth portion (BWP) and Component Carrier (CC) combination configured with the at least two SRS resource sets.

7. The apparatus of claim 1, wherein:

when the UE indicates that the UE supports a capability of non-codebook based PUSCH transmission with at least two sets of repetition associated with at least two sets of SRS resources, the UE also indicates support for one or more associated CSI-RS resources for calculating a precoder for SRS transmissions using channel state information reference signal (CSI-RS) measurements.

8. The apparatus of claim 7, wherein the UE indicates a number of associated CSI-RS resources per bandwidth part (BWP) and Component Carrier (CC) combination.

9. The apparatus of claim 8, wherein the UE further indicates:

the number of supported CSI-RS ports across the associated CSI-RS resource.

10. The apparatus of claim 8, wherein the UE further indicates:

the number of supported SRS resources per BWP associated with any one of the CSI-RS resources.

11. The apparatus of claim 7, wherein the configuration of at least two SRS resource sets received from the network entity indicates: and associated CSI-RS resources configured for each of the at least two SRS resource sets.

12. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to:

measuring CSI-RS on the CSI-RS resources configured for each of the at least two SRS resource sets;

calculating a precoder based on the CSI-RS measurements; and

the precoder is applied when the SRS is transmitted on SRS resources within each of at least two SRS resource sets associated with the at least two repetition sets.

13. The apparatus of claim 1, wherein the UE further indicates at least one of:

the number of different spatial relationship information that different SRS resources can have across the at least two SRS resource sets; or alternatively

Different SRS resources can have different amounts of spatial relationship information for each SRS resource set.

14. The apparatus of claim 1, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates at least one of:

whether different SRS resources can have different numbers of SRS ports in the SRS resource set; or alternatively

Whether different SRS resources can have different numbers of SRS ports across the at least two SRS resource sets.

15. The apparatus of claim 1, wherein when the UE indicates that the UE supports a capability of codebook-based PUSCH transmission with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates: for a first set of SRS resources of the at least two sets of SRS resources and for a second set of SRS resources of the at least two sets of SRS resources, each SRS resource is configurable a number of SRS ports.

16. An apparatus for wireless communication at a network entity, comprising:

a processor;

a memory coupled with the processor; and

receiving an indication of a capability of a User Equipment (UE) to support a Physical Uplink Shared Channel (PUSCH) transmission having at least two repeated sets, wherein each repeated set is associated with at least one set of Sounding Reference Signal (SRS) resources;

based on the indicated capabilities, transmitting a configuration of at least two SRS resource sets;

Receiving SRS on SRS resources within each of at least two SRS resource sets associated with the at least two duplicate sets;

transmitting Downlink Control Information (DCI) scheduling PUSCH repetition from the UE, the DCI indicating one or more SRS resources within the at least two SRS resource sets; and

the PUSCH repetition in the two repetition sets is received based on the SRS resources within the at least two SRS resource sets indicated in the DCI.

17. The apparatus of claim 16, wherein the network entity receives an indication of individual capabilities of the UE to support:

18. The apparatus of claim 16, wherein a network entity receives an indication of individual capabilities of the UE to support:

19. The apparatus of claim 16, wherein the network entity receives the following indication:

20. The apparatus of claim 19, the network entity further receives an indication of:

21. The apparatus of claim 19, wherein the network entity receives the following indication: for a bandwidth part (BWP) and Component Carrier (CC) combination configured with at least two SRS resource sets, a number of the supported SRS resources across the at least two SRS resource sets.

22. The apparatus of claim 16, wherein:

when the network entity receives an indication of whether the UE supports a capability of non-codebook based PUSCH transmission with at least two repetition sets associated with at least two SRS resource sets, the network entity also receives an indication of supporting one or more associated CSI-RS resources for calculating a precoder for SRS transmission using channel state information reference signal (CSI-RS) measurements.

23. The apparatus of claim 22, wherein the network entity receives an indication of a number of associated CSI-RS resources for each bandwidth part (BWP) and Component Carrier (CC) combination.

24. The apparatus of claim 23, wherein the network entity further receives an indication of:

the number of supported CSI-RS ports across the associated CSI-RS resource.

25. The apparatus of claim 23, wherein the network entity further receives an indication of:

26. The apparatus of claim 22, wherein the configuration of at least two SRS resource sets received from the network entity indicates: an SRS resource within each of the at least two SRS resource sets and an associated CSI-RS resource configured for each of the at least two SRS resource sets.

27. The apparatus of claim 16, wherein the network entity further receives an indication of at least one of:

28. The apparatus of claim 16, wherein, when the network entity receives an indication of the UE's ability to support codebook-based PUSCH transmissions with at least two repeated sets associated with at least two SRS resource sets, the UE further indicates at least one of:

29. A method for wireless communication by a User Equipment (UE), comprising:

based on the indicated capabilities, receiving a configuration of at least two SRS resource sets from the network entity;

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