WO2021232390A1

WO2021232390A1 - Group common sounding reference signal downlink control information configuration

Info

Publication number: WO2021232390A1
Application number: PCT/CN2020/091708
Authority: WO
Inventors: Alexandros MANOLAKOS; Muhammad Sayed Khairy Abdelghaffar; Seyed Ali Akbar Fakoorian; Runxin WANG; Yu Zhang; Hwan Joon Kwon; Krishna Kiran Mukkavilli
Original assignee: Qualcomm Incorporated
Priority date: 2020-05-22
Filing date: 2020-05-22
Publication date: 2021-11-25

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a base station may transmit, and a user equipment (UE) may receive, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions. The base station may transmit, and the UE may receive, a DCI message having the group common format, wherein the DCI message includes an SRS request field. The UE may transmit, and the base station may receive, one or more SRS resources or SRS resource sets triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format. Numerous other aspects are provided.

Description

GROUP COMMON SOUNDING REFERENCE SIGNAL DOWNLINK CONTROL INFORMATION CONFIGURATION

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for providing a group common sounding reference signal (SRS) downlink control information (DCI) configuration.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like) . Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) . LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .

A wireless network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs) . A user equipment (UE) may communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an access point (AP) , a radio head, a transmit receive point (TRP) , a New Radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate on a municipal, national, regional, and even global level. New Radio (NR) , which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP) . NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL) , using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink (UL) , as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

SUMMARY

In some aspects, a method of wireless communication, performed by a user equipment (UE) , may include: receiving, from a base station, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions; receiving, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, a method of wireless communication, performed by a base station, may include transmitting, to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; transmitting, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and receiving, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive, from a base station, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; receive, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and transmit one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: transmit, to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; transmit, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and receive, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: receive, from a base station, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; receive, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and transmit one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a base station, may cause the one or more processors to: transmit, to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; transmit, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and receive, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, an apparatus for wireless communication may include: means for receiving, from a base station, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; means for receiving, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and means for transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

In some aspects, an apparatus for wireless communication may include: means for transmitting, to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions; means for transmitting, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and means for receiving, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.

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

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with various aspects of the present disclosure.

Fig. 2 is a diagram illustrating an example of a base station in communication with a UE in a wireless network, in accordance with various aspects of the present disclosure.

Figs. 3A-3B are diagrams illustrating an example of a sounding reference signal (SRS) resource configuration and downlink control information (DCI) formats to trigger SRS transmissions, in accordance with various aspects of the present disclosure.

Figs. 4A-4B are diagrams illustrating one or more examples associated with a group common SRS DCI configuration, in accordance with various aspects of the present disclosure.

Figs. 5-6 are diagrams illustrating example processes associated with a group common SRS DCI configuration, in accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

It should be noted that while aspects may be described herein using terminology commonly associated with a 5G or NR radio access technologies (RAT) , aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G) .

Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with various aspects of the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network, an LTE network, and/or the like. The wireless network 100 may include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and may also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, a transmit receive point (TRP) , and/or the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG) ) . A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in Fig. 1, a BS 110a may be a macro BS for a macro cell 102a, a BS 110b may be a pico BS for a pico cell 102b, and a BS 110c may be a femto BS for a femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB” , “base station” , “NR BS” , “gNB” , “TRP” , “AP” , “node B” , “5G NB” , and “cell” may be used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.

Wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS) . A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in Fig. 1, a relay station 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts) .

A network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like. A UE may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet) ) , an entertainment device (e.g., a music or video device, or a satellite radio) , a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device) , or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE) . UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like. In some aspects, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, and/or the like.

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, and/or the like. A frequency may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like) , a mesh network, and/or the like. In this case, the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with various aspects of the present disclosure. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T ≥ 1 and R ≥ 1.

At base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , and/or the like) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS) ) . A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

At UE 120, antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. A channel processor may determine reference signal received power (RSRP) , received signal strength indicator (RSSI) , reference signal received quality (RSRQ) , channel quality indicator (CQI) , and/or the like. In some aspects, one or more components of UE 120 may be included in a housing 284.

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

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

At base station 110, the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240. Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna (s) 234, modulators and/or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein, for example, as described with reference to Figs. 3A-3B, Figs. 4A-4B, and/or Figs. 5-6.

Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with a group common sounding reference signal (SRS) downlink control information (DCI) configuration, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 500 of Fig. 5, process 600 of Fig. 6, and/or other processes as described herein.

Memories

242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, interpreting, and/or the like) by one or more processors of the base station 110 and/or the UE 120, may perform or direct operations of, for example, process 500 of Fig. 5, process 600 of Fig. 6, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, interpreting the instructions, and/or the like. A scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.

In some aspects, UE 120 may include means for receiving, from base station 110, a radio resource control (RRC) configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280, memory 282, and/or the like) , means for receiving, from base station 110, a DCI message having the group common format (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280, memory 282, and/or the like) , wherein the DCI message includes an SRS request field, means for transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format (e.g., using controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, and/or the like) , and/or the like. In some aspects, such means may include one or more components of UE 120 described in connection with Fig. 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and/or the like.

In some aspects, base station 110 may include means for transmitting, to UE 120, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions (e.g., using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, memory 242, and/or the like) , means for transmitting, to UE 120, a DCI message having the group common format, wherein the DCI message includes an SRS request field (e.g., using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, memory 242, and/or the like) , means for receiving, from UE 120, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, and/or the like) , and/or the like. In some aspects, such means may include one or more components of base station 110 described in connection with Fig. 2, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and/or the like.

As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

Figs. 3A-3B are diagrams illustrating an example 300 of an SRS resource configuration and DCI formats to trigger SRS transmissions, in accordance with various aspects of the present disclosure.

In a wireless network, such as an LTE network, an NR network, and/or the like, a UE may be configured to transmit an SRS to a base station on an uplink to enable the base station to estimate channel state information (CSI) or uplink channel quality over a wide bandwidth. For example, in some aspects, a base station may configure a UE with one or more SRS resource sets to allocate resources for SRS transmissions by the UE 120. For example, an SRS resource set configuration may be indicated in an RRC message (e.g., an RRC configuration message, an RRC reconfiguration message, and/or the like) , which may indicate one or more resources (e.g., shown in Fig. 3A as SRS resources 1-4) that are included in an SRS resource set. In general, the SRS resources may include time resources, frequency resources, spatial resources, and/or the like (e.g., a slot, a symbol, a resource block, a periodicity for the time resources, a beam, a spatial reference, a collection of consecutive symbols on specific subcarriers, and/or the like) that a UE is to use to transmit an SRS. Accordingly, an SRS resource set may generally contain a set of one or more SRS resources to be transmitted by one UE, and SRS resources may be grouped within an SRS resource set depending on a usage or use case associated with the grouped SRS resources. For example, an SRS resource and/or an SRS resource set containing one or more SRS resources may be associated with an antenna switching use case, as shown by reference number 310, a codebook-based use case, as shown by reference number 312, and/or other use cases not explicitly shown in Fig. 3A (e.g., a non-codebook use case, a beam management (sometimes referred to as uplink beam management) use case, a positioning use case, and/or the like) .

In some aspects, a UE may be configured to transmit an SRS resource or one or more SRS resources within an SRS resource set according to a semi-persistent configuration, a periodic configuration, or an aperiodic configuration. In the case of an aperiodic SRS transmission, a base station may configure the SRS resource (s) or SRS resource set (s) via RRC signaling, and a DCI message may include a two-bit SRS request field used to trigger transmission of an SRS resource or SRS resource set. For example, each aperiodic SRS resource or aperiodic SRS resource set may be associated with a parameter (e.g., an RRC-configured ‘aperiodicSRS-ResourceTrigger’ parameter) defining an index of 1, 2, or 3 for the corresponding aperiodic SRS resource or aperiodic SRS resource set, which may respectively correspond to codepoints ‘01’ , ‘10’ , or ‘11’ that may be indicated in the SRS request field of the DCI message to trigger transmission of the corresponding aperiodic SRS resource or aperiodic SRS resource set. Additionally, or alternatively, the codepoint in the two-bit SRS request field may be set to ‘00’ to indicate that no aperiodic SRS transmission is triggered.

For example, in some aspects, Fig. 3B illustrates one or more example DCI formats that can be used to trigger SRS transmissions in order to enable carrier switching for a UE. For example, in Fig. 3B, the example DCI format (s) may be DCI format 2_3, which is generally used to enable a UE to switch an uplink carrier used for uplink transmissions from one serving cell to another by transmitting an aperiodic SRS signal with an antenna switching usage or use case. For example, as described herein, DCI format 2_3 may be a group common DCI format that is used to transmit a group of transmit power control (TPC) commands for SRS transmissions by one or more UEs. As shown in Fig. 3B, DCI format 2_3 may generally include multiple blocks (e.g., block 1, block 2, …, block n) , which may be structured and/or be interpreted by a UE in different ways depending on a type of a DCI message having DCI format 2_3.

For example, as shown by reference number 320, a DCI message having the group common format 2_3 may be associated with a Type A format in which a UE is configured with one block among the multiple blocks included in the DCI message. As further shown by reference number 322, each block in the Type A format may apply to N component carrier sets (e.g., up to three component carrier sets) , each of which may include a set of serving cells that are configured by higher-layer (e.g., RRC) signaling. Accordingly, as shown by reference number 324, a block may include an SRS request field that may either be empty or absent (e.g., zero bits) or populated with a two-bit codepoint to identify a particular component carrier set for which aperiodic SRS resource transmissions are triggered. For example, as shown by reference number 326, the block may include a TPC command set with a TPC command for each serving cell index that is associated with a component carrier in the component carrier set identified by the SRS request field. Accordingly, no aperiodic SRS resource (s) or SRS resource set (s) are triggered in cases where the SRS request field is set to ‘00’ , whereas aperiodic SRS resource (s) or SRS resource set (s) that are associated with an antenna switching use case are respectively triggered for a first set, a second set, or a third set of serving cells in cases where the SRS request field is set to ‘01’ , ‘10’ , or ‘11’ . In other words, in the Type A format, the SRS request field is used to select a component carrier set that includes one or more component carriers (or serving cells) , and the UE may transmit the aperiodic SRS resource (s) or SRS resource set (s) that are associated with the antenna switching use case for the selected component carrier set.

Alternatively, as shown by reference number 330, a DCI message having the group common format 2_3 may be associated with a Type B format in which a UE is configured with one or more blocks among the multiple blocks included in the DCI message. In this case, as shown by reference number 332, each block in the Type B format may apply to one uplink component carrier, which may be associated with one or more (e.g., up to three) aperiodic SRS resources or SRS resource sets that are configured by higher-layer (e.g., RRC) signaling. Accordingly, as shown by reference number 334, a block in DCI format 2_3, Type B may include an SRS request field that may either be empty or absent (e.g., zero bits) or populated with a two-bit codepoint to identify a particular SRS resource or SRS resource set triggered by the corresponding DCI message. For example, as shown by reference number 336, the block may include a TPC command field including a TPC command for the SRS resource or SRS resource set identified by the SRS request field. Accordingly, no aperiodic SRS resource (s) or SRS resource set (s) are triggered in cases where the SRS request field is set to ‘00’ , whereas aperiodic SRS resource (s) or SRS resource set (s) that are associated with an antenna switching use case are respectively triggered for a first SRS index, a second SRS index, or a third SRS index in cases where the SRS request field is set to ‘01’ , ‘10’ , or ‘11’ . In other words, in the Type B format, the SRS request field associated with each block is used to select an SRS resource or SRS resource set associated with an uplink component carrier corresponding to the block, and the UE may transmit the selected aperiodic SRS resource (s) or SRS resource set (s) that are associated with the antenna switching use case for the corresponding uplink component carrier.

Accordingly, DCI messages associated with the group common DCI format 2_3 Type A and/or Type B as shown in Fig. 3B may be configured to trigger SRS transmissions by one or more UEs. For example, a base station may transmit a DCI message having the group common format to multiple UEs, and each UE may transmit one or more SRS resources or SRS resource sets based at least in part on one or more blocks that are applicable to the UE. For example, in the case of a DCI message having format 2_3 and Type A, a UE may identify one block that may correspond to multiple component carrier sets that are configured for the UE, and may identify a particular component carrier set for which aperiodic SRS resources or SRS resource sets are triggered according to the value of the SRS request field. Alternatively, in the case of a DCI message having format 2_3 and Type B, a UE may identify one or more blocks that respectively correspond to one component carrier configured for the UE, and may identify an aperiodic SRS resource or SRS resource set that is triggered for each respective component carrier according to the value of the SRS request field.

In this way, DCI format 2_3 may reduce signaling overhead and provide scheduling flexibility by enabling the base station to simultaneously trigger aperiodic SRS transmissions by different UEs for SRS resources or SRS resources sets associated with different component carrier sets, SRS resources or SRS resources sets associated with individual component carriers, and/or the like. However, as described above, DCI format 2_3 has limited applicability to SRS resources or SRS resource sets that are associated with an antenna switching use case. Accordingly, DCI format 2_3 does not currently support a reduction in signaling overhead or scheduling flexibility for SRS transmissions that are associated with other use cases, such as codebook-based use cases, non-codebook-based use cases, beam management use cases, positioning use cases, and/or the like. Furthermore, the SRS carrier switching mechanism provided by DCI format 2_3 is limited to component carriers that are not configured for physical uplink shared channel (PUSCH) and/or physical uplink control channel (PUCCH) transmission. In other words, DCI format 2_3 is limited to component carriers used to transmit SRS resources for antenna switching use cases so that a base station can configure a downlink precoder based at least in part on uplink channel conditions.

Some aspects described herein relate to techniques and apparatuses to enable more flexibility in triggering SRS transmissions on different component carriers and/or for different use cases using a DCI message having a group common format associated with triggering SRS transmissions. For example, in some aspects, a base station may configure a trigger state parameter (e.g., ‘srs-triggerState’ ) for one or more SRS resources and/or SRS resource sets via RRC signaling, and a DCI message having the group common format associated with triggering SRS transmissions (e.g., format 2_3) may be used to trigger transmission of the SRS resource (s) and/or SRS resource set (s) . For example, when the DCI message has a first type (e.g., Type A) , the SRS request field associated with a block may indicate a component carrier set in a similar manner as described above, and the UE may transmit each SRS resource or SRS resource set in the indicated component carrier set for which the trigger state parameter is enabled. Alternatively, when the DCI message has a second type (e.g., Type B) , the SRS request field associated with a block may indicate any SRS resource or SRS resource set in the corresponding component carrier, or the SRS request field may be absent or empty to trigger SRS resources or SRS resource sets in the corresponding component carrier set for which the RRC-configured trigger state parameter is enabled. In this way, the DCI message having the group common format can be used to trigger SRS transmissions for any suitable use case (e.g., without limitation to antenna switching use cases) and for any suitable component carrier (e.g., including component carriers associated with a PUSCH and/or PUCCH configuration) .

As indicated above, Figs. 3A-3B are provided as an example. Other examples may differ from what is described with regard to Figs. 3A-3B.

Figs. 4A-4B are diagrams illustrating one or more examples 400 associated with a group common SRS DCI configuration, in accordance with various aspects of the present disclosure. As shown in Figs. 4A-4B, example (s) 400 may include a UE (e.g., UE 120) in communication with a base station (e.g., base station 110) in a wireless network (e.g., wireless network 100) .

As shown in Fig. 4A, and by reference number 410, the base station may transmit, and the UE may receive, an RRC configuration indicating one or more component carrier sets to be configured for the UE. For example, as described above, a DCI message having the group common format (e.g., format 2_3) may include an SRS request field associated with triggering SRS transmissions. For example, the SRS request field associated with a block includes two bits to indicate a codepoint associated with a particular component carrier set in the Type A format, or the SRS request field associated with a block alternatively includes two bits to indicate a codepoint associated with a particular SRS resource or SRS resource set associated with a particular component carrier in the Type B format. Accordingly, a size (e.g., number of bits) of the SRS request field generally limits the number of component carriers that can be configured for the UE. For example, given a two-bit SRS request field to indicate a particular component carrier set, the UE can be configured with up to four (4) component carrier sets. As a result, one way to potentially increase the number of component carrier sets that can be configured for the UE is to increase the size (number of bits) in the SRS request field. However, this technique is not backward-compatible, and may result in each block of the DCI message having a larger size, which may affect a DCI detection rate and/or the like. Accordingly, in some aspects, the RRC configuration may indicate N component carrier sets that are configured for the UE, where N may have a value greater than four (e.g., sixteen (16) and/or the like) , and subsequent signaling (e.g., a medium access control (MAC) control element (MAC-CE) command) may be used to down-select the N component carrier sets to a number of component carrier sets that is based at least in part on a size of the SRS request field. For example, as described herein, the MAC-CE command may select up to four (4) component carrier sets out of the N component carrier sets that are RRC-configured such that the two-bit SRS request field in the DCI message can indicate a codepoint associated with one of the component carrier sets selected by the MAC-CE command.

As further shown by reference number 410, the base station may transmit, and the UE may receive, an RRC configuration indicating a trigger state parameter for one or more SRS resources that are configured for the UE. For example, in some aspects, an SRS resource configured for the UE may include an RRC-configured trigger state parameter (e.g., ‘srs-triggerState’ ) that indicates whether the SRS resource can be triggered by the DCI message having the group common format associated with triggering aperiodic SRS transmissions (e.g., format 2_3) . For example, the trigger state parameter may be set to ‘true’ , ‘enabled’ , ‘1’ , and/or the like to indicate that the SRS resource can be triggered by the DCI message having the group common format associated with triggering aperiodic SRS transmissions. Alternatively, the trigger state parameter may be set to ‘false, ‘disabled’ , ‘0’ , omitted from the RRC configuration, and/or the like to indicate that the SRS resource is not to be triggered by a DCI message having the group common format associated with triggering aperiodic SRS transmissions. Additionally, or alternatively, the trigger state parameter may be configured for an SRS resource set, whereby one or more SRS resources that are grouped within an SRS resource set may inherit the value of the trigger state parameter that is configured for the SRS resource set in which the SRS resources are grouped. In some aspects, the RRC-configured trigger state parameter may be indicated for any suitable SRS resource or SRS resource set, including SRS resources or SRS resource sets associated with an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, a positioning use case, and/or the like. Furthermore, the SRS resources or SRS resource sets that are associated with the RRC-configured trigger state parameter may be associated with any suitable component carrier or component carrier set, including component carriers or component carrier sets associated with a PUSCH and/or PUCCH configuration.

As further shown in Fig. 4A, and by reference number 415, the base station may transmit, and the UE may receive, a MAC-CE command down-selecting the component carrier sets configured for the UE. For example, as described above, a DCI message having the group common format and Type A may include an SRS request field to indicate a component carrier set for which SRS transmissions are triggered. Accordingly, in some aspects, the MAC-CE command may be used to down-select N component carrier sets that are configured for a UE to a number of component carrier sets that can be indicated by the SRS request field based at least in part on a size of the SRS request field. For example, the MAC-CE command may select up to four component carrier sets out of the N component carrier sets configured for the UE if the SRS request field has two bits, up to eight component carrier sets out of the N component carrier sets configured for the UE if the SRS request field has three bits, and/or the like. In this way, a larger number of component carrier sets can be configured for the UE, and the MAC-CE command can be used to down-select the component carrier sets to a number that can be indicated in the SRS request field without increasing a size of the DCI message. Alternatively, in cases where 2 ^M or fewer component carrier sets are configured for the UE, where M is a number of bits in the SRS request field, the base station may not need to transmit the MAC-CE command to down-select the component carrier sets configured for the UE.

Additionally, or alternatively, as further shown by reference number 415, the base station may transmit, and the UE may receive, a MAC-CE command to dynamically update the RRC-configured trigger state parameter for one or more SRS resources. For example, in some aspects, the MAC-CE command may dynamically change the RRC-configured trigger state parameter for one or more SRS resources from ‘enabled’ to ‘disabled’ , from ‘true’ to ‘false’ , from ‘1’ to ‘0’ , or vice versa. Additionally, or alternatively, the MAC-CE command may dynamically update the RRC-configured trigger state parameter for one or more SRS resource sets in order to simultaneously change the RRC-configured trigger state parameter for each SRS resource within the corresponding SRS resource set (s) .

As shown in Fig. 4B, and by reference number 420, the base station may transmit, and the UE may receive, a DCI message having the group common format associated with triggering SRS transmissions. For example, in some aspects, the DCI message may be associated with DCI format 2_3, and may have a first type (Type A) to trigger SRS resources or SRS resource sets associated with one or more serving cells in a component carrier set. Alternatively, in some aspects, the DCI message may have a second type (Type B) to trigger an SRS resource or SRS resource set for one or more component carriers. In some aspects, the DCI message having the group common format may be transmitted to multiple UEs, and each UE may determine the SRS resource (s) or SRS resource set (s) that are triggered by the DCI message according to one or more blocks in the DCI message that are applicable to the UE.

For example, as further shown in Fig. 4B, and by reference number 425, the UE may determine one or more SRS resources (or SRS resource sets) that are triggered by the DCI message based at least in part on a type of the DCI message, a value of the SRS request field in one or more blocks of the DCI message that are applicable to the UE, and/or the like. For example, in cases where the DCI message has a first type (e.g., Type A) , the DCI message may include multiple blocks, and one of the blocks may correspond to a group of up to 2 ^M component carrier sets configured for the UE, where M is a number of bits in the SRS request field of the DCI message. In this case, when the DCI message has the first type, the UE may identify one block in the DCI message that corresponds to the group of component carrier sets configured for the UE, and may determine the SRS resources or SRS resource sets triggered by the DCI message based at least in part on a value of the SRS field included in the block that corresponds to the group of component carrier sets configured for the UE. For example, if the value of the SRS request field is ‘00’a nd/or the like, the DCI message does not trigger any SRS transmissions. Otherwise (e.g., the value of the SRS request field is ‘01’ , ‘10’ , ‘11’ , and/or the like) , the UE may determine a component carrier set that corresponds to the codepoint indicated in the SRS request field, and each SRS resource or SRS resource set in the corresponding component carrier set for which the trigger state parameter is true or otherwise enabled may be triggered for transmission by the UE.

Alternatively, in cases where the DCI message has a second type (e.g., Type B) , the DCI message may include multiple blocks, and one or more of the blocks may correspond to one or more respective uplink component carriers configured for the UE. In this case, the UE may identify one or more blocks in the DCI message that correspond to uplink component carriers configured for the UE, and may determine the SRS resources or SRS resource sets triggered by the DCI message based at least in part on a value of the SRS field included in the one or more blocks. For example, if the value of the SRS request field is ‘00’ and/or the like, the DCI message does not trigger any SRS transmissions. Otherwise (e.g., the value of the SRS request field is ‘01’ , ‘10’ , ‘11’ , and/or the like) , the UE may determine an SRS resource or SRS resource set that corresponds to the codepoint indicated in the SRS request field, each of which may be triggered for transmission by the UE. Accordingly, in cases where the DCI message has the second type, the SRS request field in a block may trigger an SRS resource or an SRS resource set independently from the RRC-configured trigger state parameter for the SRS resource or an SRS resource set. In other words, the DCI message having the second type may trigger an SRS resource or an SRS resource set for transmission by the UE even if the RRC-configured trigger state parameter associated with the SRS resource or SRS resource set is absent, false, disabled, and/or the like. Alternatively, in cases where the SRS request field is absent within a block that corresponds to a particular uplink carrier, the UE may refer to the RRC-configured trigger state parameter for the SRS resources or SRS resource sets associated with the uplink carrier. For example, if the UE receives a group common DCI message having the second type and the SRS request field is absent in a block corresponding to a component carrier configured for the UE, the UE may determine that the group common DCI message triggers each SRS resource or SRS resource set associated with the component carrier for which the trigger state parameter is true or otherwise enabled.

As further shown in Fig. 4B, and by reference number 430, the UE may transmit, and the base station may receive, one or more SRS resources or SRS resource sets triggered by the DCI message having the group common format. For example, in some aspects, the transmitted SRS resource (s) or SRS resource set (s) may be associated with an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use, a positioning use case, and/or the like. Accordingly, the DCI message having the group common format can be used to flexibly schedule SRS transmissions for any suitable SRS use case (e.g., without limitation to antenna switching use cases) . Furthermore, in some aspects, the one or more SRS resources or SRS resource sets may be transmitted on one or more component carriers that have a PUSCH configuration, one or more component carriers that have a PUCCH configuration, one or more component carriers that are used to enable the base station to select a downlink precoder, and/or the like. In this way, the DCI message having the group common format can be used to flexibly schedule SRS transmissions for any suitable component carrier (e.g., without limitation to component carriers that are not configured for PUSCH and/or PUCCH transmissions) .

As indicated above, Figs. 4A-4B are provided as one or more examples. Other examples may differ from what is described with regard to Figs. 4A-4B.

Fig. 5 is a diagram illustrating an example process 500 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 500 is an example where the UE (e.g., UE 120 and/or the like) performs operations associated with a group common SRS DCI configuration.

As shown in Fig. 5, in some aspects, process 500 may include receiving, from a base station, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions (block 510) . For example, the UE may receive (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280, memory 282, and/or the like) , from a base station, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions, as described above, for example, with reference to Figs. 4A-4B.

As further shown in Fig. 5, in some aspects, process 500 may include receiving, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field (block 520) . For example, the UE may receive (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller/processor 280, memory 282, and/or the like) , from the base station, a DCI message having the group common format, as described above, for example, with reference to Figs. 4A-4B. In some aspects, the DCI message includes an SRS request field.

As further shown in Fig. 5, in some aspects, process 500 may include transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format (block 530) . For example, the UE may transmit (e.g., using controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, and/or the like) one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format, as described above, for example, with reference to Figs. 4A-4B.

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

In a first aspect, the one or more SRS resources or SRS resource sets that are triggered by the DCI message are associated with one or more of an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, or a positioning use case.

In a second aspect, alone or in combination with the first aspect, the one or more SRS resources or SRS resource sets are associated with one or more component carriers that have a PUSCH and/or a PUCCH configuration.

In a third aspect, alone or in combination with one or more of the first and second aspects, the value of the SRS request field indicates one or more component carriers that are associated with the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type A.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 500 includes receiving, from the base station, a MAC-CE command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type B.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted independent of the RRC configuration when the type associated with the DCI message is Type B.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more SRS resources or SRS resource sets to be transmitted are identified based at least in part on the RRC configuration when the type associated with the DCI message is Type A, or when the type associated with the DCI message is Type B and the SRS request field is absent in one or more blocks of the DCI message that are applicable to the UE.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 500 includes receiving, from the base station, a MAC-CE command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.

Although Fig. 5 shows example blocks of process 500, in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 5. Additionally, or alternatively, two or more of the blocks of process 500 may be performed in parallel.

Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process 600 is an example where the base station (e.g., base station 110 and/or the like) performs operations associated with a group common SRS DCI configuration.

As shown in Fig. 6, in some aspects, process 600 may include transmitting, to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions (block 610) . For example, the base station may transmit (e.g., using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, memory 242, and/or the like) , to a UE, an RRC configuration indicating whether one or more SRS resources or SRS resource sets can be triggered by DCI having a group common format associated with triggering SRS transmissions, as described above, for example, with reference to Figs. 4A-4B.

As further shown in Fig. 6, in some aspects, process 600 may include transmitting, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field (block 620) . For example, the base station may transmit (e.g., using controller/processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, memory 242, and/or the like) , to the UE, a DCI message having the group common format, as described above, for example, with reference to Figs. 4A-4B. In some aspects, the DCI message includes an SRS request field.

As further shown in Fig. 6, in some aspects, process 600 may include receiving, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format (block 630) . For example, the base station may receive (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, and/or the like) , from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format, as described above, for example, with reference to Figs. 4A-4B.

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

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 600 includes transmitting, to the UE, a MAC-CE command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 600 includes transmitting, to the UE, a MAC-CE command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.

Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

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

As used herein, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code-it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single 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 multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like) , and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .

Claims

A method of wireless communication performed by a user equipment (UE) , comprising:

receiving, from a base station, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

receiving, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
The method of claim 1, wherein the one or more SRS resources or SRS resource sets that are triggered by the DCI message are associated with one or more of an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, or a positioning use case.
The method of claim 1, wherein the one or more SRS resources or SRS resource sets are associated with one or more component carriers that have one or more of a physical uplink shared channel or a physical uplink control channel configuration.
The method of claim 1, wherein the value of the SRS request field indicates one or more component carriers that are associated with the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type A.
The method of claim 4, further comprising:

receiving, from the base station, a medium access control (MAC) control element (MAC-CE) command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.
The method of claim 1, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type B.
The method of claim 1, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted independent of the RRC configuration when the type associated with the DCI message is Type B.
The method of claim 1, wherein the one or more SRS resources or SRS resource sets to be transmitted are identified based at least in part on the RRC configuration when the type associated with the DCI message is Type A, or when the type associated with the DCI message is Type B and the SRS request field is absent in one or more blocks of the DCI message that are applicable to the UE.
The method of claim 1, further comprising:

receiving, from the base station, a medium access control (MAC) control element (MAC-CE) command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.
A method of wireless communication performed by a base station, comprising:

transmitting, to a user equipment (UE) , a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

transmitting, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

receiving, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
The method of claim 10, wherein the one or more SRS resources or SRS resource sets that are triggered by the DCI message are associated with one or more of an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, or a positioning use case.
The method of claim 10, wherein the one or more SRS resources or SRS resource sets are associated with one or more component carriers that have one or more of a physical uplink shared channel or a physical uplink control channel configuration.
The method of claim 10, wherein the value of the SRS request field indicates one or more component carriers that are associated with the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type A.
The method of claim 13, further comprising:

transmitting, to the UE, a medium access control (MAC) control element (MAC-CE) command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.
The method of claim 10, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type B.
The method of claim 10, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted independent of the RRC configuration when the type associated with the DCI message is Type B.
The method of claim 10, wherein the one or more SRS resources or SRS resource sets to be transmitted are identified based at least in part on the RRC configuration when the type associated with the DCI message is Type A, or when the type associated with the DCI message is Type B and the SRS request field is absent in one or more blocks of the DCI message that are applicable to the UE.
The method of claim 10, further comprising:

transmitting, to the UE, a medium access control (MAC) control element (MAC-CE) command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.
A user equipment (UE) for wireless communication, comprising:

a memory; and

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

receive, from a base station, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

receive, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

transmit one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
The UE of claim 19, wherein the one or more SRS resources or SRS resource sets that are triggered by the DCI message are associated with one or more of an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, or a positioning use case.
The UE of claim 19, wherein the one or more SRS resources or SRS resource sets are associated with one or more component carriers that have one or more of a physical uplink shared channel or a physical uplink control channel configuration.
The UE of claim 19, wherein the value of the SRS request field indicates one or more component carriers that are associated with the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type A.
The UE of claim 22, wherein the one or more processors are further configured to:

receive, from the base station, a medium access control (MAC) control element (MAC-CE) command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.
The UE of claim 19, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type B.
The UE of claim 19, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted independent of the RRC configuration when the type associated with the DCI message is Type B.
The UE of claim 19, wherein the one or more SRS resources or SRS resource sets to be transmitted are identified based at least in part on the RRC configuration when the type associated with the DCI message is Type A, or when the type associated with the DCI message is Type B and the SRS request field is absent in one or more blocks of the DCI message that are applicable to the UE.
The UE of claim 19, wherein the one or more processors are further configured to:

receive, from the base station, a medium access control (MAC) control element (MAC-CE) command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.
A base station for wireless communication, comprising:

a memory; and

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

transmit, to a user equipment (UE) , a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

transmit, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

receive, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
The base station of claim 28, wherein the one or more SRS resources or SRS resource sets that are triggered by the DCI message are associated with one or more of an antenna switching use case, a codebook-based use case, a non-codebook-based use case, a beam management use case, or a positioning use case.
The base station of claim 28, wherein the one or more SRS resources or SRS resource sets are associated with one or more component carriers that have one or more of a physical uplink shared channel or a physical uplink control channel configuration.
The base station of claim 28, wherein the value of the SRS request field indicates one or more component carriers that are associated with the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type A.
The base station of claim 31, wherein the one or more processors are further configured to:

transmit, to the UE, a medium access control (MAC) control element (MAC-CE) command selecting, among multiple component carrier sets configured for the UE, up to a maximum number of component carrier sets based at least in part on a size of the SRS request field, wherein the value of the SRS request field identifies one of the component carrier sets selected by the MAC-CE command.
The base station of claim 28, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted when the type associated with the DCI message is Type B.
The base station of claim 28, wherein the value of the SRS request field indicates the one or more SRS resources or SRS resource sets to be transmitted independent of the RRC configuration when the type associated with the DCI message is Type B.
The base station of claim 28, wherein the one or more SRS resources or SRS resource sets to be transmitted are identified based at least in part on the RRC configuration when the type associated with the DCI message is Type A, or when the type associated with the DCI message is Type B and the SRS request field is absent in one or more blocks of the DCI message that are applicable to the UE.
The base station of claim 28, wherein the one or more processors are further configured to:

transmit, to the UE, a medium access control (MAC) control element (MAC-CE) command dynamically updating whether the one or more SRS resources or SRS resource sets can be triggered by the DCI having the group common format associated with triggering SRS transmissions.
A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising:

one or more instructions that, when executed by one or more processors of a user equipment, cause the one or more processors to:

receive, from a base station, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

receive, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

transmit one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising:

one or more instructions that, when executed by one or more processors of a base station, cause the one or more processors to:

transmit, to a user equipment (UE) , a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

transmit, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

receive, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
An apparatus for wireless communication, comprising:

means for receiving, from a base station, a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

means for receiving, from the base station, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

means for transmitting one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.
An apparatus for wireless communication, comprising:

means for transmitting, to a user equipment (UE) , a radio resource control (RRC) configuration indicating whether one or more sounding reference signal (SRS) resources or SRS resource sets can be triggered by downlink control information (DCI) having a group common format associated with triggering SRS transmissions;

means for transmitting, to the UE, a DCI message having the group common format, wherein the DCI message includes an SRS request field; and

means for receiving, from the UE, one or more SRS resources or SRS resource sets that are triggered by the DCI message based at least in part on a value of the SRS request field, the RRC configuration, and a type associated with the DCI message having the group common format.