Techniques for dynamic switching between asymmetric antenna panels for uplink

Abstract

Methods, systems, and devices for wireless communication are described. Techniques described herein relate to dynamic transmission of sounding reference signals (SRS) by a user equipment (UE) to support dynamic switching between asymmetric antenna panels at the UE. The UE may transmit, to a network entity, a beam report indicating a maximum number of SRS resources of a Physical Uplink Shared Channel (PUSCH) supported by the UE for a given beam. The UE may transmit a number of SRSs equal to the maximum number to the network entity. The network entity may indicate a subset of SRS resources for the UE to use the PUSCH, and the UE may transmit the PUSCH using a number of ports equal to the indicated number of SRS resources. The UE may indicate a plurality of maximum numbers of SRS resources supported by the UE for a plurality of overlapping PUSCHs.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 18 / 505,842, filed by Chen et al. on November 9, 2023, entitled “TECHNIQUES FOR DYNAMIC SWITCHING BETWEEN ASYMMETRIC ANTENNA PANELS FOR UPLINK,” which claims the benefit of U.S. provisional patent application No. 63 / 481,785, filed by Chen et al. on January 26, 2023, entitled “TECHNIQUES FOR DYNAMIC SWITCHING BETWEEN ASYMMETRIC ANTENNA PANELS FOR UPLINK,” each of which is assigned to the assignee of this application, and each of which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including techniques for dynamically switching between asymmetric antenna panels for uplink. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems (such as long-term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting techniques for dynamically switching between asymmetric antenna panels for uplink communications. For example, the described techniques provide for dynamic transmission of sounding reference signals (SRSs) by a user equipment (UE) to support dynamic switching between asymmetric antenna panels at the UE. A network entity may send a downlink reference signal associated with a transmit configuration indicator (TCI) state of a channel state information (CSI) reference signal to the UE. The UE may send a beam report to the network entity, the beam report indicating a maximum number of SRS resources (e.g., associated with downlink reference signals) supported by the UE for physical uplink shared channel (PUSCH) transmission. The UE may send a number of SRSs to the network entity equal to the maximum number indicated in the beam report. For example, the UE may send SRSs autonomously or in response to signaling from the network entity (e.g., an acknowledgment of a beam report or request), thereby supporting dynamic switching between asymmetric antenna panels at the UE. The network entity may indicate a subset of SRS resources for the UE to use for PUSCH in scheduling information for the PUSCH. The UE may send the PUSCH via a subset of the SRS resources.

[0006] In some examples, the UE may indicate in a beam report multiple maximum numbers of SRS resources supported by the UE for multiple overlapping PUSCH transmissions. In such examples, the network entity may indicate multiple subsets of SRS resources for the UE to use when sending overlapping PUSCH transmissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An example of a wireless communication system supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0008] Figure 2 An example of a wireless communication system supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0009] Figure 3 Illustrated are examples of resource maps supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure.

[0010] Figure 4 Illustrated are examples of resource maps supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure.

[0011] Figure 5An example of a wireless communication system supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0012] Figure 6 Illustrated are examples of resource maps supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure.

[0013] Figure 7 An example of a process flow supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0014] Figure 8 and Figure 9 A block diagram illustrating a device supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0015] Figure 10 A block diagram illustrating a communications manager supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0016] Figure 11 A diagram illustrating a system including devices supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0017] Figure 12 and Figure 13 A block diagram illustrating a device supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0018] Figure 14 A block diagram illustrating a communications manager supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0019] Figure 15 A diagram illustrating a system including devices supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated.

[0020] Figures 16 to 19 A flow chart illustrating a method of supporting techniques for dynamically switching between asymmetric antenna panels for uplink in accordance with one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0021] In non-codebook based communications, a user equipment (UE) may measure downlink reference signals (e.g., channel state information reference signals (CSI-RS)) sent by a network entity. The UE may calculate precoding candidates based on the measured downlink reference signals. In contrast, in codebook based transmissions, the UE may be provided with a precoding matrix indicator (PMI) that is mapped to a codebook or precoding parameters. In non-codebook based communications, the UE may use the determined precoding candidates to send one or more sounding reference signal (SRS) resources to the network entity, and the network entity may measure the SRS to determine the quality of the precoding candidates (e.g., received signal strength, spectral efficiency, etc.). The network entity may use an SRS resource indicator (SRI) in scheduling information for a physical uplink shared channel (PUSCH) (e.g., in downlink control information (DCI) that schedules the PUSCH) to indicate a subset of SRS resources for the PUSCH. In non-codebook based PUSCH transmission, one SRS port may be used per SRS resource, and accordingly, the number of indicated SRS resources used for PUSCH may determine the rank (i.e., number of layers) of the uplink transmission. The UE may report the maximum number of SRS ports supported for a given beam in a beam report. However, currently, the UE may perform SRS sounding when scheduled by a network entity via radio resource control (RRC) signaling. Therefore, if the active antenna panel changes (e.g., based on the new strongest beam), the UE may not dynamically transmit SRS, and therefore the number of supported SRS ports may increase or decrease.

[0022] The technology described herein supports a method for dynamically sending SRS in non-codebook based uplink communications to switch between asymmetric antenna panels (e.g., with different numbers of supported ports) at a UE. For example, in response to sending a beam report indicating the strongest beam (e.g., based on a downlink reference signal), the UE may send an SRS set using a subset of SRS resources configured for the downlink reference signal. For example, the UE may receive RRC signaling that configures a set of SRS resources associated with the downlink reference signal. The number of SRSs sent by the UE may be equal to the maximum number of SRS resources supported by the UE indicated in the beam report. The beam report may be sent in uplink control information (UCI). In one example, the UE may autonomously send the SRS after sending the beam report. In another example, the UE may send the SRS in response to an acknowledgment of receipt of the beam report from a network entity. In another example, the network entity may send a request to the UE to send the SRS. The maximum number of SRS resources indicated in the beam report may be equal to the maximum number of uplink ports (e.g., SRS / PUSCH ports) of the UE's antenna panel used to receive downlink reference signals (e.g., CSI-RS or synchronization signal blocks (SSBs)). The network entity may receive and measure SRS. Based on SRS, the network entity may schedule PUSCH and indicate to the UE in the SRI which SRS resources are used for PUSCH. The UE may accordingly use a number of PUSCH ports equal to the number of indicated SRS resources to transmit PUSCH.

[0023] In some examples, the UE may transmit SRS for the second beam for overlapping PUSCH transmissions (e.g., in multiple-DCI multiple transmit reception points (TRPs) or single-DCI multiple TRPs scenarios). In such scenarios, the UE may indicate the maximum number of SRS resources supported by the UE for each beam for overlapping PUSCH transmissions, and the number of SRSs transmitted by the UE for each beam may be equal to the maximum number of SRS resources supported by the UE for each beam.

[0024] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described by and with reference to resource diagrams, process flows, apparatus diagrams, system diagrams, and flow charts related to techniques for dynamically switching between asymmetric antenna panels for uplink.

[0025] Figure 1An example of a wireless communication system 100 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0026] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support communication of signals according to one or more radio access technologies (RATs).

[0027] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105 or other UEs 115 or network entities 105 as shown.

[0028] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0029] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0030] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).

[0031] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or TRP. One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0032] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165 such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.

[0033] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0034] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between the IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., the F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0035] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0036] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal the transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. That is, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0037] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the techniques described herein for dynamically switching between asymmetric antenna panels for uplink. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0038] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0039] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0040] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0041] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster used for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection by UE 115 may occur via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0042] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0043] A carrier may be associated with a particular bandwidth of RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth, or may be capable of being configured to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0044] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0045] One or more parameter sets for a carrier may be supported, and the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications by the UE 115 may be constrained to one or more active BWPs.

[0046] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0047] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0048] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0049] Physical channels may be multiplexed according to various techniques for communication using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0050] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish between adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), such cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, etc.

[0051] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Small cells may be associated with lower-power network entities 105 (e.g., lower-power base stations 140) than macro cells, and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as the macro cells. Small cells may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communication via one or more cells using one or more component carriers.

[0052] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0053] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0054] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication can include private communication or group communication and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.

[0055] In some examples, a UE 115 can be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group can be outside of the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0056] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0057] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macro cell to provide service to a UE 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) than communication using the smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0058] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using the unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0059] A network entity 105 (e.g., a base station 140, a RU 170) or a UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0060] The network entity 105 or the UE 115 may use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technique may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0061] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0062] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different sets of beamforming weights associated with different transmit directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as the network entity 105, or by a receiving device, such as the UE 115) the beam direction for later transmission or reception by the network entity 105.

[0063] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (e.g., receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0064] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across the system bandwidth or one or more subbands. Network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), CSI-RS), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0065] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving data signals). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0066] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmissions, thereby improving link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.

[0067] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0068] The techniques described herein support methods for dynamically transmitting SRS in non-codebook-based uplink communications to switch between asymmetric antenna panels (e.g., having different numbers of supported ports) at UE 115. For example, in response to sending a beam report indicating the strongest beam (e.g., based on a downlink reference signal), UE 115 may transmit a set of SRS using a subset of SRS resources configured for the downlink reference signal. For example, UE 115 may receive RRC signaling configuring a set of SRS resources associated with the downlink reference signal. The number of SRSs transmitted by UE 115 may be equal to the maximum number of SRS resources supported by UE 115 as indicated in the beam report. The beam report may be transmitted in UCI. In one example, UE 115 may autonomously transmit SRS after transmitting the beam report. In another example, UE 115 may transmit SRS in response to an acknowledgment of receipt of the beam report from network entity 105. In another example, network entity 105 may transmit a request to UE 115 to transmit SRS. The maximum number of SRS resources indicated in the beam report may be equal to the maximum number of uplink ports (e.g., SRS / PUSCH ports) of the antenna panel of the UE 115 used to receive downlink reference signals (e.g., CSI-RS or SSB). The network entity 105 may receive and measure the SRS. Based on the SRS, the network entity 105 may schedule the PUSCH and indicate to the UE 115 in the SRI which SRS resources are used for the PUSCH. The UE 115 may accordingly transmit the PUSCH using a number of PUSCH ports equal to the number of indicated SRS resources.

[0069] UE 115 may transmit SRS for the second beam for overlapping PUSCH transmissions (e.g., in multi-DCI multi-TRP or single-DCI multi-TRP scenarios). In such scenarios, UE 115 may indicate the maximum number of SRS resources supported by UE 115 for each beam for overlapping PUSCH transmissions, and the number of SRSs transmitted by UE 115 for each beam may be equal to the maximum number of SRS resources supported by UE 115 for each beam.

[0070] Figure 2 An example of a wireless communication system 200 that supports dynamic panel switching for non-codebook based uplink communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 can implement aspects of the wireless communication system 100 or can be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115 (e.g., UE 115-a) and a network entity 105 (e.g., network entity 105-a), which may be as described in reference to FIG. Figure 1Examples of corresponding devices described.

[0071] UE 115-a may communicate with network entity 105-a using communication link 125-a. Communication link 125-a may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a may include a bidirectional link that enables both uplink and downlink communication. For example, UE 115-a may use communication link 125-a to send uplink signals 205 (e.g., uplink transmissions), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a may use communication link 125-a to send downlink signals 210 (e.g., downlink transmissions), such as downlink control signals or downlink data signals, to UE 115-a.

[0072] In some examples of the wireless communication system 200, the UE 115-a may communicate with the network entity 105-a via codebook-based uplink transmission. In such examples, the UE 115-a may be configured with an SRS resource set, for example, via RRC signaling, where the parameter "usage" is set to "codebook". In some examples, up to four SRS resources within the SRS resource set may be configured for the UE 115-a. In the codebook-based transmission, each SRS resource may use the number of SRS ports given by the RRC parameter "nofSRS-Ports". The network entity 105-a may send an SRI in an uplink DCI (e.g., a DCI scheduling a PUSCH). The SRI may indicate one SRS resource for the UE 115-a to use for the PUSCH, and the number of ports configured for the SRS resource may determine the number of antenna ports used for the PUSCH. The PUSCH may be transmitted using the same spatial domain filter (e.g., beam) as the indicated SRS resource. The network entity 105 - a may indicate the number of layers (eg, rank) and transmit precoding matrix index (TPMI) used for PUSCH transmission in a separate DCI field (eg, DCI field “Precoding information and number of layers”).

[0073] In some other examples of the wireless communication system 200, the UE 115-a may communicate with the network entity 105-a via non-codebook based uplink transmission. In non-codebook based PUSCH, the UE 115-a may be configured with an SRS resource set, for example, via RRC signaling, where the parameter "usage" is set to "non-codebook". In non-codebook based PUSCH, each SRS resource may use one SRS port, and accordingly, the number of indicated SRS resources used for the PUSCH may determine the rank of the PUSCH (e.g., the number of layers). In some examples, up to four SRS resources within the SRS resource set may be configured for the UE 115-a. The UE 115-a may report to the network entity 105-a in a beam report 220 the number of SRS resources (e.g., the maximum number) that can be supported for a given beam. The SRI field in the scheduling DCI may indicate one or more SRS resources for the scheduled PUSCH, and the PUSCH may be transmitted using the same precoder and spatial domain filter (e.g., beam) as the indicated SRS resources. The size of the SRI field may vary with the number of SRS resources in the SRS resource set configured for the UE.

[0074] For non-codebook-based PUSCH, UE 115-a may measure the downlink CSI-RS transmitted by network entity 105-a and calculate precoding candidates. UE 115-a may use the determined precoding candidates to transmit one or more SRSs 225 to network entity 105-a, and network entity 105-a may measure the SRSs 225 to determine the quality of the precoding candidates (e.g., signal strength, spectral efficiency, etc.). Network entity 105-a may indicate a subset of SRS resources for UE 115-a to use for PUSCH 235 via an SRI in scheduling DCI 230.

[0075] The techniques described herein may support methods for dynamically transmitting SRS 225 in non-codebook based uplink communications to switch between asymmetric panels (e.g., having different numbers of ports). In some examples, a UE 115-a may receive a control message 215 from a network entity 105-a indicating a set of SRS resources associated with a CSI-RS 240. The UE 115-a may send a beam report 220 to the network entity 105-a (e.g., in a UCI) indicating the number (e.g., maximum number) of SRS resources supported by the UE 115-a for downlink reference signals (e.g., CSI-RS 240 or synchronization signal blocks (SSBs)) transmitted by the network entity 105-a. The downlink reference signal may be associated with a transmit configuration indicator (TCI) state of the CSI-RS. For example, the TCI state may be configured with a downlink reference signal or quasi-co-located (QCL) with a downlink reference signal (e.g., directly or indirectly).

[0076] UE 115-a may (e.g., in response to sending beam report 220) send a set of SRS 225 using a subset of SRS resources configured for downlink reference signals. The number of SRS 225 may be equal to the number (e.g., maximum number) of SRS resources supported by UE 115-a (e.g., as indicated in beam report 220). In one example, UE 115-a may autonomously send SRS 225 after sending beam report 220. In another example, UE 115-a may send SRS 225 in response to receiving an acknowledgment of beam report 220 from network entity 105-a. In another alternative, network entity 105-a may send a request to UE 115-a to send SRS 225. The number of SRS resources may be equal to the number of uplink ports (e.g., SRS / PUSCH ports) of an antenna panel (e.g., an antenna panel for receiving downlink reference signals) of UE 115-a.

[0077] The network entity 105-a may receive the SRS 225 and schedule a PUSCH 235 via a scheduling DCI 230. The network entity 105-a may indicate in the scheduling DCI 230 that the PUSCH 235 is to be transmitted using a subset of the SRS resources. The UE 115-a may accordingly transmit the PUSCH 235 using a number of PUSCH ports equal to the number of SRS resources in the subset of SRS resources.

[0078] In some examples, UE 115-a may transmit additional SRS 225 for the second beam for overlapping PUSCH 235 (e.g., a multi-DCI multi-TRP or a single-DCI multi-TRP scenario). In such examples, UE 115-a may indicate the number (e.g., a maximum number) of SRS resources supported by UE 115-a for each beam in overlapping PUSCH 235. For example, UE 115-a may transmit a number of SRS 225 equal to the maximum number of SRS resources supported by UE 115-a for each beam.

[0079] Figure 3 An example of a resource map 300 supporting dynamic panel switching for non-codebook based uplink communications according to one or more aspects of the present disclosure is illustrated. The resource map 300 may implement aspects of the wireless communication system 100 or the wireless communication system 200, or may be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the resource map 300 may include the UE 115 and the network entity 105, which may be as described in reference to FIG. Figure 1 Examples of corresponding devices described.

[0080] As described herein, a UE 115 may communicate with a network entity 105 via non-codebook-based uplink transmission. The UE 115 may measure non-zero power (NZP) CSI-RS from the network entity 105 via CSI-RS resources 305 associated with an SRS resource set. For example, RRC signaling may indicate the association of the SRS resource set with the CSI-RS resources 305. In a non-codebook-based uplink, the UE 115 may not desire to be configured with both the parameter SpatialRelationInfo for SRS and the associatedCSI-RS in the field SRS-ResourceSet for the SRS resource set. At 310, the UE 115 may calculate precoding candidates to be used when transmitting SRS via SRS resources 315-a, 315-b, 315-c, and 315-d in the SRS resource set. UE 115 may use the calculated precoding candidates to transmit an SRS to network entity 105 via SRS resources 315 (e.g., up to four SRS resources). Network entity 105 may measure the SRS to determine the quality of the precoding candidates (e.g., signal strength, spectral efficiency, etc.). At 320, network entity 105 may determine one or more SRS resources in SRS resources 315 for UE 115 to use for PUSCH 335 based on the SRS. Network entity 105 may indicate one or more SRS resources in SRS resources 315 for UE 115 to use for PUSCH 335 via an SRI in a scheduling DCI 325. The SRI may be associated with a most recent SRS transmission by UE 115 before the scheduling DCI 325 carries the SRI. At 330, UE 115 may transmit PUSCH 335 via the indicated SRS resources.

[0081] For example, the network entity 105 may indicate SRS resource 315-a and SRS resource 315-b via an SRI. Because the network entity 105 indicates two SRS resources, the PUSCH 335 may have two layers. Therefore, at 330, the UE 115 may transmit the PUSCH 335 using the same precoding and beam as used for the SRS transmitted via SRS resource 315-a and SRS resource 315-b.

[0082] Figure 4 An example of a resource map 400 supporting dynamic panel switching for non-codebook based uplink communications according to one or more aspects of the present disclosure is illustrated. The resource map 400 may implement aspects of the wireless communication system 100 or the wireless communication system 200, or may be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the resource map 400 may be provided by the UE 115 and / or the network entity 105 (which may be as described in reference to FIG. Figure 1 Examples of corresponding devices described above) are implemented.

[0083] In some examples (e.g., if the UE 115 is configured with the parameter associatedCSI-RS in the RRC field SRS-ResourceSet), for single TRP (sTRP) transmission, the UE 115 can be configured to report a capability index (e.g., a maximum number of SRS resources 410 in the SRS resource set 405) associated with the downlink reference signal 415 (e.g., an SSB index or a CSI-RS resource) to the network entity 105. For non-codebook-based uplink communication, the reported capability index can indicate the maximum number of SRS resources 410 per SRS resource set (e.g., rather than the maximum number of SRS ports per SRS resource as in codebook-based PUSCH). Thus, the capability index can indicate the maximum number of uplink (e.g., PUSCH) ports of the antenna panel at the UE 115 for receiving the downlink reference signal 415. The UE 115 may send the report as part of a layer 1 (L1) beam report (e.g., on a physical uplink control channel (PUCCH) or PUSCH) via the UCI 420. For codebook-based PUSCH, if uplink sounding is required, the network entity 105 may schedule SRS with a corresponding number of ports, and the network entity 105 may schedule PUSCH with a maximum number of layers limited to the number of supported ports.

[0084] In some examples, as described herein, the number of ports of an SRS resource may be changed solely via RRC signaling. For example, in some examples, a UE 115 may not be able to dynamically transmit SRS from a panel with a larger or smaller capability index (e.g., a panel capable of transmitting more or less SRS). Thus, in such examples, the network entity 105 may not be able to dynamically indicate an increase or decrease in the number of SRS ports used for PUSCH scheduling. In some aspects, unless full power mode 2 is configured for the UE 115, all SRS resources may have the same number of ports. However, even in such a full power mode 2 configuration, it may be necessary to dynamically change the number of SRS ports of an SRS resource having a TCI state equal to the reported L1 beam.

[0085] As described herein, for non-codebook-based PUSCH, the UE 115 is not expected to be configured with both the parameter SpatialRelationInfo for SRS and the associatedCSI-RS in the field SRS-ResourceSet for the SRS resource set. Therefore, in the first case, the UE 115 may be configured with the associatedCSI-RS in the field SRS-ResourceSet for the SRS resource set. And in the second case, the UE 115 may be configured with spatialRelationInfo for the SRS resource.

[0086] When UE 115 is configured with an associated CSI-RS in an SRS-ResourceSet for an SRS resource set including one or more SRS resources for non-codebook based PUSCH, UE 115 may report a capability index (maximum number or SRS resources) associated with downlink reference signal 415 (e.g., SSB index or CSI-RS resource) in UCI 420 (e.g., in a beam report for downlink reference signal 415). The capability index may indicate the maximum number of uplink (e.g., PUSCH) ports of a panel for receiving downlink reference signal 415. In some cases, the beam report included in UCI 420 may include capability indexes for multiple downlink reference signals.

[0087] UE 115 may determine whether a TCI state of a CSI-RS (e.g., a CSI-RS associated with SRS resource set 405) is associated with downlink reference signal 415. For example, network entity 105 may indicate to UE 115 that the TCI state is associated with downlink reference signal 415. In some examples, UE 115 may determine that the TCI state is associated with downlink reference signal 415 if the TCI state is configured with downlink reference signal 415, if the TCI state is quasi-co-located with downlink reference signal 415, or both.

[0088] If the TCI state is associated with downlink reference signal 415, UE 115 may determine a subset 425 of SRS resource set 405. For example, UE 115 may determine that the number of SRS resources 410 is equal to the number of SRS resources 410 indicated by the capability index in UCI 420. That is, for example, if UE 115 indicates a maximum of two SRS resources 410 in a beam report sent via UCI 420, UE 115 may determine a subset 425 that includes two SRS resources (e.g., SRS resource 410-a and SRS resource 410-b). In some examples, if the number of SRS resources 410 indicated in UCI 420 is less than the number of SRS resources 410 in SRS resource set 405, UE 115 may select the first SRS resource 410 according to the number indicated in UCI 420. In some other examples, UE 115 may select SRS resources 410 for subset 425 according to rules in the UE specification.

[0089] In some examples, UE 115 can autonomously update the maximum number of SRS resources 410 (e.g., the number of SRS resources 410 in subset 425). That is, UE 115 can update the number of SRS resources 410 after a duration (e.g., a fixed number of symbols or time slots) after transmitting UCI 420. In some examples (e.g., to avoid collisions if network entity 105 does not decode UCI 420), UE 115 can update the maximum number of SRS resources 410 after receiving an acknowledgment message corresponding to UCI 420 from network entity 105 (e.g., a fixed number of symbols or time slots after receiving an acknowledgment message corresponding to UCI 420 from network entity 105). Network entity 105 can send the acknowledgment message using DCI or a MAC control element (MAC-CE). In some other examples, UE 115 can update the maximum number of SRS resources 410 when explicitly instructed by network entity 105. In such examples, the network entity 105 may decide whether and when to update the maximum number of SRS resources 410 after receiving the UCI 420 .

[0090] The UE 115 may transmit one or more SRSs to the network entity 105 via the subset 425 of the SRS resources 410. The network entity 105 may transmit scheduling information for PUSCH transmission to the UE 115, wherein the scheduling information includes an SRI based on the determined subset 425 of the SRS resources 410. For example, the network entity 105 may transmit an uplink grant indicating one or more SRS resources in the SRS resources 410 in the subset 425 for the UE 115 to use in the PUSCH. The UE 115 may transmit the PUSCH using a number of PUSCH ports equal to the indicated number of SRS resources 410 (e.g., the indicated one or more SRS resources in the SRS resources 410 in the subset 425), as described with reference to FIG. Figure 3 described.

[0091] Figure 5 An example of a wireless communication system 500 that supports dynamic panel switching for non-codebook based uplink communication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 500 can implement aspects of the wireless communication system 100 or the wireless communication system 200, or can be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the wireless communication system 500 may include a UE 115 and a network entity 105 (e.g., a network entity 105-b), which may be as described in reference Figure 1 Examples of corresponding devices described.

[0092] In an example of a wireless communication system 500, a UE 115 can communicate with a network entity 105-b using simultaneous transmission of a PUSCH across multiple panels (STxMP). In one example, the UE 115 can communicate via spatial division multiplexing (SDM) based on a single DCI. That is, the network entity 105-a can transmit a single DCI that schedules a PUSCH with multiple port sets 515 (e.g., multiple layer sets 505 transmitted from multiple panels 520 using different transmit beams 525, precoders, power control parameters, etc.). Each of the multiple layer sets can be associated with an SRS resource set.

[0093] For example, network entity 105-a may schedule PUSCH transmissions with two layer sets (e.g., layer set 505-a and layer set 505-b). Each of layer set 505-a and layer set 505-b may be associated with a TPMI or SRI (e.g., SRI 510-a and SRI 510-b, respectively). Each of SRI 510-a and SRI 510-b may indicate two SRS resources associated with two PUSCH ports (e.g., PUSCH ports 515-a and 515-b and PUSCH ports 515-c and 515-d, respectively). Thus, UE 115 may transmit PUSCH from two panels (e.g., panel 520-a associated with PUSCH ports 515-a and 515-b and panel 520-b associated with PUSCH ports 515-c and 515-d). That is, UE 115 may transmit a PUSCH from panel 520-a to TRP 535-a at network entity 105-b via beam 525-a, and may transmit a PUSCH from panel 520-b to TRP 535-b at network entity 105-b via beam 525-b. Although this example is described with reference to two layers associated with each transmission of a PUSCH (e.g., 2+2 layers), network entity 105-b may instruct UE 115 to transmit a PUSCH using a different layer combination (e.g., 1+1, 2+1, 1+2, etc.).

[0094] In another example, the UE 115 may communicate with the network entity 105-b using overlapping PUSCH transmissions (e.g., multi-DCI based communication with multiple TRPs (mTRPs)). That is, the network entity 105-b may send multiple DCIs that instruct the UE 115 to send at least two different PUSCH transmissions (e.g., a first PUSCH transmission and a second PUSCH transmission) in the same serving cell. The PUSCH transmissions may overlap (e.g., partially or completely) in the time domain (e.g., and in the frequency domain). The PUSCH transmissions may be associated with different coresetPoolIndex values ​​(e.g., coresetPoolIndex value 0 and coresetPoolIndex value 1) rather than being associated with the same coresetPoolIndex value (e.g., as in a single DCI based SDM). The two PUSCH transmissions may additionally be associated with a first set of layers 505-a and a second set of layers 505-b, respectively (e.g., and with different TCI states, power control parameters, precoders, etc.).

[0095] For example, network entity 105-a may schedule two PUSCH transmissions with two layer sets (e.g., a first PUSCH transmission associated with layer set 505-a and a second PUSCH transmission associated with layer set 505-b). Each of layer set 505-a and layer set 505-b may be associated with a TPMI or SRI (e.g., SRI 510-a and SRI 510-b, respectively). Each of SRI 510-a and SRI 510-b may indicate two SRS resources associated with two PUSCH ports (e.g., PUSCH ports 515-a and 515-b and PUSCH ports 515-c and 515-d, respectively). Thus, UE 115 may transmit a first PUSCH from panel 520-a associated with PUSCH ports 515-a and 515-b, and a second PUSCH from panel 520-b associated with PUSCH ports 515-c and 515-d. That is, UE 115 may transmit a first PUSCH from panel 520-a to TRP 535-a at network entity 105-b via beam 525-a, and may transmit a second PUSCH from panel 520-b to TRP 535-b at network entity 105-b via beam 525-b. Although this example is described with reference to two layers associated with each PUSCH (e.g., 2+2 layers), network entity 105-b may instruct UE 115 to transmit each PUSCH using a different layer combination (e.g., 1+1, 2+1, 1+2, etc.).

[0096] However, in the case of sTRP communication, the network entity 105-b may instruct the UE 115 to use a greater number of SRS resources (e.g., from a resource set) than the number of resources that may be indicated by the network entity 105-b in the case of mTRP (e.g., for SDM, FDM, or single frequency network schemes). For example, the maximum number of layers associated with an SRS resource set in an sTRP communication may be greater than the maximum number of layers associated with the same SRS resource set in a simultaneous transmission. For example, the layers in the resource set associated with the simultaneous transmission may be a subset of the layers in the resource set associated with the sTRP communication. This subset relationship may be consistent with the reference Figure 4 The described subsets 425 conflict.

[0097] Figure 6An example of a resource map 600 supporting dynamic panel switching for simultaneous transmission in non-codebook based uplink communications according to one or more aspects of the present disclosure is illustrated. The resource map 600 may implement aspects of the wireless communication system 100, the wireless communication system 200, or the wireless communication system 500, or may be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or the wireless communication system 500. For example, the resource map 600 may be provided by the UE 115 and / or the network entity 105 (which may be as described in reference to FIG. Figure 1 Examples of corresponding devices described above) are implemented.

[0098] In some examples (e.g., if UE 115 is configured with two SRS resource sets 605-a and 605-b and is configured with the parameter associatedCSI-RS in the RRC field SRS-ResourceSet), UE 115 can report to network entity 105 a pair of capability indices (e.g., a maximum number of SRS resources 610 in SRS resource set 605-a and SRS resource set 605-b) associated with downlink reference signal 615-a and downlink reference signal 615-b, respectively (e.g., they can each correspond to an SSB index or CSI-RS resource). For non-codebook based uplink communication, each maximum number of SRS resources 610 can indicate a maximum number of uplink (e.g., PUSCH) ports of the panel for receiving downlink reference signal 615-a and downlink reference signal 615-b, respectively. UE 115 can send the report via UCI 620 as part of an L1 beam report (e.g., on PUCCH or PUSCH).

[0099] In some examples, in addition to reference Figure 4 In addition to the described sending of separate capability index reports for each downlink reference signal, UE 115 may also send capability index pairs. For example, if beams corresponding to downlink reference signal 615-a and downlink reference signal 615-b are to be sent simultaneously (e.g., for mTRP), UE 115 may report capability indexes for the downlink reference signal pair (615-a, 615-b). Additionally, UE 115 may separately report capability indexes for downlink reference signal 615-a and capability indexes for downlink reference signal 615-b (e.g., for sTRP). Although the example is described with reference to two layers associated with downlink reference signal 615-a and one layer associated with downlink reference signal 615-b (e.g., 2+1 layers), downlink reference signal 615-a and downlink reference signal 615-b may be associated with different layer combinations (e.g., 1+1, 1+2, etc.).

[0100] UE 115 may determine whether the TCI state of a CSI-RS (e.g., a CSI-RS associated with SRS resource set 605-a and a CSI-RS associated with SRS resource set 605-b) is associated with downlink reference signal 615-a and downlink reference signal 615-b, respectively. For example, network entity 105 may indicate to UE 115 that a first TCI state is associated with downlink reference signal 615-a and a second TCI state is associated with downlink reference signal 615-b. Network entity 105 may determine that the TCI state is associated with downlink reference signal 615 if the TCI state is configured with downlink reference signal 615, if the TCI state is QCL with downlink reference signal 615, or both.

[0101] In the example of simultaneous transmission, if one or both of the first TCI state and the second TCI state are associated with downlink reference signal 615-a and downlink reference signal 615-b, respectively, UE 115 may determine a subset 625-a of SRS resource set 605-a and a subset 625-c of SRS resource set 605-b. For example, UE 115 may determine that the number of SRS resources 610 is equal to the number of SRS resources 610 indicated in UCI 620. If downlink reference signal 615-a and downlink reference signal 615-b are associated with simultaneous transmission, the number of SRS resources in subset 625-a and subset 625-c may not exceed the number of SRS resources 610 in SRS resource set 605-a and SRS resource set 605-b, respectively. For example, if UE 115 indicates a capability index (1+2) in a beam report sent via UCI 620, UE 115 may determine a subset 625-a including two SRS resources (e.g., SRS resource 610-a and SRS resource 610-b) and a subset 625-c including one SRS resource (e.g., SRS resource 610-e). In some examples, if the number of SRS resources 610 indicated in UCI 620 is less than the number of SRS resources 610 in SRS resource set 605-a and SRS resource set 605-b, UE 115 may select the first SRS resource 610, or UE 115 may select SRS resources 610 for subset 625-a and subset 625-c according to rules in the UE specification, as described with reference to FIG. Figure 4 described.

[0102] The UE 115 may send one or more SRSs to the network entity 105 via a subset 625-a of the SRS resource set 605-a and a subset 625-c of the SRS resource set 605-b. The network entity 105 may send an SRI to schedule a PUSCH transmission to the UE 115 based on the determined subset 625. That is, the network entity 105 may send an uplink grant indicating one or more SRS resources in the SRS resources 610 in each of the subset 625-a and the subset 625-c for the UE 115 to use in the PUSCH transmission. The PUSCH transmission may be multiple transmission opportunities for one PUSCH with two TCI states, or two overlapping PUSCH transmissions associated with different TCI states. If the SRI bit width varies with the update of the maximum number of SRS resources, the network entity 105 may send an SRI field or two SRI fields with different bit widths. Otherwise, the SRI field may be as described in reference Figure 4 UE 115 may transmit PUSCH transmissions utilizing a number of PUSCH ports equal to the indicated number of SRS resources 610 (e.g., the indicated one or more SRS resources in each of subsets 625-a and 625-c) as described with reference to Figure 3 described.

[0103] In the example of sTRP communication, if one of the first TCI state or the second TCI state is associated with downlink reference signal 615-a or downlink reference signal 615-b, respectively, UE 115 may determine subset 625-b of SRS resource set 605-a and subset 625-d of SRS resource set 605-b. For example, UE 115 may determine that the number of SRS resources 610 is equal to the number of SRS resources 610 indicated in UCI 620. If downlink reference signal 615-a or downlink reference signal 615-b is associated with sTRP transmission, the number of SRS resources in subset 625-b and subset 625-d may be equal to the number of SRS resources 610 in SRS resource set 605-a and SRS resource set 605-b, respectively. For example, if UE 115 indicates a capability index of 2 for each of downlink reference signal 615-a and downlink reference signal 615-b in a beam report sent via UCI 620, UE 115 may determine a subset 625-b including two SRS resources (e.g., SRS resource 610-a and SRS resource 610-b) and a subset 625-d including two SRS resources (e.g., SRS resource 610-e and SRS resource 610-f). In some examples, if the number of SRS resources 610 indicated in UCI 620 is less than the number of SRS resources 610 in SRS resource set 605-a and SRS resource set 605-b, UE 115 may select the first SRS resource 610, or UE 115 may select SRS resources 610 for subset 625-b and subset 625-d according to rules in the UE specification, as described in reference to FIG. Figure 4 described.

[0104] The UE 115 may transmit one or more SRSs via a subset 625-b or a subset 625-d of the SRS resource set 605-a and the SRS resource set 605-b, respectively. The network entity 105 may transmit an SRI to the UE 115 that schedules a PUSCH transmission based on one of the subsets 625-b or the subsets 625-d. That is, the network entity 105 may transmit an uplink grant that indicates one or more SRS resources from the SRS resources 610 from one of the subsets 625-b or the subsets 625-d for use by the UE 115 in the PUSCH transmission. The UE 115 may transmit the PUSCH transmission using a number of PUSCH ports equal to the indicated number of SRS resources 610 (e.g., the indicated one or more SRS resources from the SRS resources 610 in the indicated subset 625), as described with reference to FIG. Figure 3 described.

[0105] In some examples, UE 115 can autonomously update the maximum number of SRS resources 610 (e.g., the number of SRS resources 610 in subsets 625-a, 625-b, 625-c, and / or 625-d). That is, UE 115 can update the number of SRS resources 610 a duration (e.g., a fixed number of symbols or time slots) after transmitting UCI 620. In some examples (e.g., to avoid collisions when network entity 105 does not decode UCI 620), UE 115 can update the maximum number of SRS resources 610 after receiving an acknowledgment message corresponding to UCI 620 from network entity 105 (e.g., a fixed number of symbols or time slots after receiving an acknowledgment message corresponding to UCI 620 from network entity 105). Network entity 105 can send the acknowledgment message using DCI or MAC-CE. In some examples, UE 115 can update the maximum number of SRS resources 610 when explicitly instructed by network entity 105. In such examples, the network entity 105 may decide whether and when to update the maximum number of SRS resources 610 after receiving the UCI 620 .

[0106] Figure 7 An example of a process flow 700 for supporting dynamic panel switching for non-codebook based uplink communications according to one or more aspects of the present disclosure is illustrated. The process flow 700 may implement aspects of the wireless communication system 100, the wireless communication system 200, or the wireless communication system 500, or may be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or the wireless communication system 500. For example, the process flow 700 may include a UE 115 (e.g., UE 115-b) and a network entity 105 (e.g., network entity 105-c), which may be as described in reference to FIG. Figure 1 Examples of corresponding devices are described. In the following description of process flow 700, operations between network entity 105-c and UE 115-b may be presented in an order different from the example order shown. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0107] At 705, network entity 105-c may send a first control message to UE 115-b indicating a first set of SRS resources associated with a first CSI-RS. In some examples, the control message may further indicate a second set of SRS resources associated with a second CSI-RS.

[0108] In some examples, at 710, network entity 105-c may send an indication to UE 115-b that a first TCI state for a first CSI-RS is associated with a first downlink reference signal. Additionally, network entity 105-c may send an indication to UE 115-b that a second TCI state for a second CSI-RS is associated with a second downlink reference signal. For example, network entity 105-c may send the indication if the TCI state is configured with a downlink reference signal or if the TCI state is QCL with a downlink reference signal.

[0109] At 715, UE 115-b may send a second control message to network entity 105-c, the second control message indicating a first maximum number of SRS resources associated with the first downlink reference signal. UE 115-b may send the second control message via a UCI including a beam report indicating a beam associated with the first downlink reference signal. In some examples, the second control message may also include an indication of a second maximum number of SRS resources associated with the second downlink reference signal. In some examples, the second control message may also include an indication of a third maximum number and a fourth maximum number of SRS resources for separate uplink transmissions associated with the first downlink reference signal and the second downlink reference signal, respectively. In some examples, the third maximum number of SRS resources may be greater than the first maximum number of SRS resources. In some examples, the fourth maximum number of SRS resources may be greater than the second maximum number of SRS resources.

[0110] In some examples, network entity 105-c may send an acknowledgment message to UE 115-b in response to receiving the UCI at 720. UE 115-b may send an SRS set in response to receiving the acknowledgment message, as described with reference to 735.

[0111] In some examples, at 725 , the network entity 105 - c may send a third control message to the UE 115 - b that includes a request to update the maximum number of SRS resources. The UE 115 - b may send the SRS set in response to receiving the third control message, as described with reference to 735 .

[0112] In some examples, at 730, UE 115-b may select a first subset of SRS resources based on corresponding index values ​​of SRS resources in the first set of SRS resources. The number of SRS resources in the first subset of SRS resources may be equal to the first maximum number. UE 115-b may further select a second subset of SRS resources based on corresponding index values ​​of SRS resources in the second set of SRS resources. Additionally or alternatively, UE 115-b may select a third subset and a fourth subset of SRS resources based on corresponding index values ​​of SRS resources in the first set and the second set of SRS resources. The number of SRS resources in the second subset, the third subset, and the fourth subset of SRS resources may be equal to the second maximum number, the third maximum number, and the fourth maximum number, respectively.

[0113] At 735, UE 115-b may transmit a first set of SRS to network entity 105-c via the first subset of SRS resources. As described with reference to 730, the number of SRS resources in the first subset of SRS resources may be equal to the first maximum number. In some examples, UE 115-b may autonomously transmit the first set of SRS for a duration (e.g., a certain number of symbols or time slots) after transmitting UCI, as described with reference to 715. In some other examples, UE 115-b may transmit the first set of SRS in response to receiving an acknowledgment or a third control message, as described with reference to 720 and 725, respectively.

[0114] In some examples, at 740, UE 115-b may transmit a second set of SRS to network entity 105-c via the second subset of SRS resources. As described with reference to 730, the number of SRS resources in the second subset of SRS resources may be equal to the second maximum number. In some examples, UE 115-b may autonomously transmit the second set of SRS for a duration (e.g., a certain number of symbols or time slots) after transmitting the UCI, as described with reference to 715. In some examples, UE 115-b may transmit the second set of SRS in response to receiving an acknowledgment or a third control message, as described with reference to 720 and 725, respectively.

[0115] At 745, the network entity 105-c may send first scheduling information to the UE 115-b for sending the first PUSCH. The first scheduling information may indicate one or more SRS resources from the first subset of SRS resources, one or more SRS resources from the second subset of SRS resources, or one or more SRS resources from the third subset of SRS resources. The network entity 105-c may send the first scheduling information via a first DCI. Additionally, the first DCI may include second scheduling information for a second PUSCH, the second scheduling information indicating one or more SRS resources from the fourth subset of SRS resources. The second PUSCH may at least partially overlap with the first PUSCH in time (e.g., and frequency).

[0116] In some examples, at 750, network entity 105-c may send second scheduling information for a second PUSCH to UE 115-b, the second scheduling information indicating one or more SRS resources in a fourth subset of SRS resources. Network entity 105-c may send the second scheduling information via a second DCI. The second PUSCH may at least partially overlap with the first PUSCH in time (e.g., and frequency).

[0117] At 755, UE 115-b may send a first PUSCH transmission to network entity 105-c using the SRS resources indicated by the first scheduling information. That is, UE 115-b may send the first PUSCH using a number of PUSCH ports equal to the number of SRS resources indicated by the first scheduling information.

[0118] In some examples, UE 115-b may send a second PUSCH transmission to network entity 105-c using the SRS resources indicated by the second scheduling information at 760. That is, UE 115-b may send the second PUSCH using a number of PUSCH ports equal to the number of SRS resources indicated by the second scheduling information.

[0119] Figure 8 A block diagram 800 illustrates a device 805 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. The device 805 can be an example of aspects of the UE 115 as described herein. The device 805 can include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0120] Receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for dynamically switching between asymmetric antenna panels for uplink). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a set of multiple antennas.

[0121] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for dynamically switching between asymmetric antenna panels for uplink). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0122] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0123] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0124] Additionally or alternatively, in some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0125] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0126] According to the examples disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured as or otherwise support a component for receiving a first control message from a network entity, the first control message indicating an SRS resource set associated with a CSI-RS. The communication manager 820 may be configured as or otherwise support a component for sending a second control message to the network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The communication manager 820 may be configured as or otherwise support a component for sending an SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The communication manager 820 may be configured as or otherwise support a component for receiving scheduling information for sending an uplink shared channel from the network entity. The communication manager 820 may be configured as or otherwise support means for transmitting an uplink shared channel to a network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information.

[0127] By including or configuring a communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support techniques for more efficiently utilizing communication resources.

[0128] Figure 9 A block diagram 900 illustrates a device 905 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. The device 905 can be an example of aspects of the device 805 or UE 115 as described herein. The device 905 can include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0129] Receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for dynamically switching between asymmetric antenna panels for uplink). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a set of multiple antennas.

[0130] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for dynamically switching between asymmetric antenna panels for uplink). In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0131] Device 905 or its various components may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein. For example, communication manager 920 may include an SRS resource configuration manager 925, an SRS capability manager 930, an SRS transmission manager 935, a scheduling information manager 940, an uplink transmission manager 945, or any combination thereof. Communication manager 920 may be an example of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 910, transmitter 915, or both. For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0132] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a UE. The SRS resource configuration manager 925 may be configured as or otherwise support a component for receiving a first control message from a network entity, the first control message indicating a set of SRS resources associated with a CSI-RS. The SRS capability manager 930 may be configured as or otherwise support a component for sending a second control message to the network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The SRS transmission manager 935 may be configured as or otherwise support a component for transmitting an SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The scheduling information manager 940 may be configured as or otherwise support a component for receiving scheduling information for transmitting an uplink shared channel from the network entity. The uplink transmission manager 945 may be configured as or otherwise support means for transmitting an uplink shared channel to a network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information.

[0133] Figure 10 Block diagram 1000 illustrates a communication manager 1020 that supports techniques for dynamically switching between asymmetric antenna panels for uplink, in accordance with one or more aspects of the present disclosure. Communication manager 1020 may be an example of communication manager 820, communication manager 920, or aspects of both, as described herein. Communication manager 1020 or its various components may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink, as described herein. For example, communication manager 1020 may include an SRS resource configuration manager 1025, an SRS capability manager 1030, an SRS transmission manager 1035, a scheduling information manager 1040, an uplink transmission manager 1045, a UCI manager 1050, a downlink reference signal (TCI) state manager 1055, a UCI acknowledgment manager 1060, or any combination thereof. Each of these components may communicate with each other, directly or indirectly (e.g., via one or more buses).

[0134] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. The SRS resource configuration manager 1025 may be configured as or otherwise support means for receiving a first control message from a network entity, the first control message indicating a set of SRS resources associated with a CSI-RS. The SRS capability manager 1030 may be configured as or otherwise support means for sending a second control message to the network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The SRS transmission manager 1035 may be configured as or otherwise support means for transmitting an SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The scheduling information manager 1040 may be configured as or otherwise support means for receiving scheduling information for transmitting an uplink shared channel from the network entity. The uplink transmission manager 1045 may be configured as or otherwise support means for transmitting an uplink shared channel to a network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information.

[0135] In some examples, to support sending the second control message, the UCI manager 1050 may be configured as or otherwise support means for sending UCI including a beam report indicating a beam associated with a downlink reference signal.

[0136] In some examples, to support sending the SRS set, the SRS transmission manager 1035 may be configured as or otherwise support means for sending the SRS set after a duration after sending the UCI.

[0137] In some examples, UCI acknowledgement manager 1060 may be configured as or otherwise support means for receiving an acknowledgement in response to the UCI from a network entity, wherein sending the SRS set is based on receiving the acknowledgement.

[0138] In some examples, the SRS transmission manager 1035 may be configured as or otherwise support means for receiving a third control message from a network entity indicating that SRS resources in the SRS resource set are to be updated, wherein transmitting the SRS set is based on the third control message.

[0139] In some examples, to support receiving scheduling information, the SRS resource configuration manager 1025 may be configured as or otherwise support means for receiving an indication of one or more SRS resources in a subset of a set of SRS resources.

[0140] In some examples, the downlink reference signal TCI state manager 1055 may be configured as or otherwise support means for receiving an indication of a TCI state with a downlink reference signal QCL.

[0141] In some examples, the downlink reference signal TCI state manager 1055 may be configured as or otherwise support means for receiving an indication that the TCI state is configured with a downlink reference signal.

[0142] In some examples, the SRS resource configuration manager 1025 may be configured as or otherwise support means for selecting a subset of the SRS resource set from the SRS resource set based on corresponding index values ​​of the SRS resources in the SRS resource set.

[0143] In some examples, the SRS resource configuration manager 1025 may be configured as or otherwise support means for receiving, via a first control message, an indication of a second set of SRS resources associated with a second CSI-RS. In some examples, the SRS capability manager 1030 may be configured as or otherwise support means for sending, via a second control message, an indication of a second maximum number of SRS resources associated with a second downlink reference signal received by the UE, wherein the second downlink reference signal is associated with a second TCI state of the second CSI-RS. In some examples, the SRS transmission manager 1035 may be configured as or otherwise support means for transmitting, to a network entity, a second set of SRS resources via a second subset of the second set of SRS resources, wherein the number of SRS resources in the second subset of the second set of SRS resources is equal to the second maximum number. In some examples, the scheduling information manager 1040 may be configured as or otherwise support means for receiving, from the network entity, second scheduling information for transmitting a second uplink shared channel, wherein the second uplink shared channel at least partially overlaps in time with the uplink shared channel. In some examples, the uplink transmission manager 1045 may be configured as or otherwise support means for transmitting a second uplink shared channel to the network entity using a second number of uplink shared channel ports equal to a second number of SRS resources indicated by the second scheduling information.

[0144] In some examples, the SRS capability manager 1030 may be configured as or otherwise support means for sending, via a second control message, an indication of a third maximum number of SRS resources for a separate uplink transmission associated with a downlink reference signal, and an indication of a fourth maximum number of SRS resources for a separate uplink transmission associated with a second downlink reference signal, wherein the maximum number of SRS resources and the second maximum number of SRS resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

[0145] In some examples, to support receiving the scheduling information and the second scheduling information, the scheduling information manager 1040 may be configured as or otherwise support means for receiving the scheduling information and the second scheduling information via the same DCI.

[0146] In some examples, to support receiving the scheduling information and the second scheduling information, the scheduling information manager 1040 can be configured as or otherwise support means for receiving the scheduling information via the first DCI. In some examples, to support receiving the scheduling information and the second scheduling information, the scheduling information manager 1040 can be configured as or otherwise support means for receiving the second scheduling information via the second DCI.

[0147] Figure 11 A diagram illustrating a system 1100 including a device 1105 supporting techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of, or include components of, a device 805, a device 905, or a UE 115 as described herein. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1145).

[0148] I / O controller 1110 can manage input and output signals for device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor, such as processor 1140. In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0149] In some cases, device 1105 may include a single antenna 1125. However, in some other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired, or wireless links, as described herein. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be examples of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof, or components thereof, as described herein.

[0150] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform the various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium (such as system memory) or another type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1130 may contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0151] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting techniques for dynamically switching between asymmetric antenna panels for uplink). For example, the device 1105 or a component of the device 1105 may include the processor 1140 and the memory 1130 coupled to or coupled to the processor 1140, the processor 1140 and the memory 1130 being configured to perform the various functions described herein.

[0152] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a UE. For example, the communication manager 1120 may be configured as or otherwise support a component for receiving a first control message from a network entity, the first control message indicating an SRS resource set associated with a CSI-RS. The communication manager 1120 may be configured as or otherwise support a component for sending a second control message to the network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The communication manager 1120 may be configured as or otherwise support a component for sending an SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The communication manager 1120 may be configured as or otherwise support a component for receiving scheduling information for sending an uplink shared channel from the network entity. The communication manager 1120 may be configured as or otherwise support means for transmitting an uplink shared channel to a network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information.

[0153] By including or configuring a communication manager 1120 according to examples as described herein, the device 1105 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

[0154] In some examples, the communication manager 1120 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 can be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 can include instructions that can be executed by the processor 1140 to cause the device 1105 to perform various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein, or the processor 1140 and the memory 1130 can be otherwise configured to perform or support such operations.

[0155] Figure 12 A block diagram 1200 illustrates a device 1205 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. The device 1205 can be an example of aspects of the network entity 105 as described herein. The device 1205 can include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0156] Receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0157] Transmitter 1215 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0158] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0159] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0160] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in this disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0161] In some examples, communication manager 1220 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 can receive information from receiver 1210, transmit information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0162] According to the examples disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured as or otherwise support a component for sending a first control message to a UE, the first control message indicating a set of SRS resources associated with a CSI-RS. The communication manager 1220 may be configured as or otherwise support a component for receiving a second control message from the UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The communication manager 1220 may be configured as or otherwise support a component for receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The communication manager 1220 may be configured as or otherwise support a component for sending scheduling information for sending an uplink shared channel to the UE. The communication manager 1220 may be configured as or otherwise support means for receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information.

[0163] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 (e.g., a processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof) can support techniques for more efficiently utilizing communication resources.

[0164] Figure 13 A block diagram 1300 illustrates a device 1305 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. The device 1305 can be an example of aspects of the device 1205 or the network entity 105 as described herein. The device 1305 can include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0165] Receiver 1310 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0166] Transmitter 1315 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0167] Device 1305 or its various components may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein. For example, communications manager 1320 may include SRS resource configuration manager 1325, UE SRS capability manager 1330, SRS reception manager 1335, scheduling information manager 1340, uplink reception manager 1345, or any combination thereof. Communications manager 1320 may be examples of aspects of communications manager 1220 as described herein. In some examples, communications manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1310, transmitter 1315, or both. For example, communications manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0168] According to examples as disclosed herein, a communication manager 1320 may support wireless communications at a network entity. An SRS resource configuration manager 1325 may be configured as or otherwise support means for sending a first control message to a UE, the first control message indicating a set of SRS resources associated with a CSI-RS. A UE SRS capability manager 1330 may be configured as or otherwise support means for receiving a second control message from a UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. An SRS reception manager 1335 may be configured as or otherwise support means for receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. A scheduling information manager 1340 may be configured as or otherwise support means for sending scheduling information for transmitting an uplink shared channel to the UE. The uplink reception manager 1345 may be configured as or otherwise support means for receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information.

[0169] Figure 14A block diagram 1400 illustrates a communication manager 1420 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both, as described herein. The communication manager 1420 or its various components may be examples of means for performing various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein. For example, the communication manager 1420 may include an SRS resource configuration manager 1425, a UE SRS capability manager 1430, an SRS reception manager 1435, a scheduling information manager 1440, an uplink reception manager 1445, a UCI manager 1450, a UCI acknowledgment manager 1455, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0170] According to examples as disclosed herein, a communication manager 1420 may support wireless communications at a network entity. An SRS resource configuration manager 1425 may be configured as or otherwise support means for sending a first control message to a UE, the first control message indicating a set of SRS resources associated with a CSI-RS. A UE SRS capability manager 1430 may be configured as or otherwise support means for receiving a second control message from a UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. An SRS reception manager 1435 may be configured as or otherwise support means for receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. A scheduling information manager 1440 may be configured as or otherwise support means for sending scheduling information for transmitting an uplink shared channel to the UE. The uplink reception manager 1445 may be configured as or otherwise support means for receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information.

[0171] In some examples, to support receiving the second control message, the UCI manager 1450 may be configured as or otherwise support means for receiving UCI including a beam report indicating a beam associated with a downlink reference signal.

[0172] In some examples, to support receiving the SRS set, the SRS reception manager 1435 may be configured as or otherwise support means for receiving the SRS set after a duration after receiving the UCI.

[0173] In some examples, the UCI acknowledgement manager 1455 may be configured as or otherwise support means for sending an acknowledgement in response to the UCI to the UE, wherein receiving the SRS set is based on sending the acknowledgement.

[0174] In some examples, the SRS reception manager 1435 may be configured as or otherwise support means for sending a third control message to the UE indicating that SRS resources in the SRS resource set are to be updated, wherein receiving the SRS set is based on the third control message.

[0175] In some examples, to support sending scheduling information, the scheduling information manager 1440 may be configured as or otherwise support means for sending an indication of one or more SRS resources in a subset of a set of SRS resources.

[0176] In some examples, the SRS resource configuration manager 1425 may be configured as or otherwise support means for sending, via a first control message, an indication of a second set of SRS resources associated with a second CSI-RS. In some examples, the UE SRS capability manager 1430 may be configured as or otherwise support means for receiving, via a second control message, an indication of a second maximum number of SRS resources associated with a second downlink reference signal received by the UE, wherein the second downlink reference signal is associated with a second TCI state of the second CSI-RS. In some examples, the SRS reception manager 1435 may be configured as or otherwise support means for receiving, from the UE, a second set of SRS resources via a second subset of the second set of SRS resources, wherein the number of SRS resources in the second subset of the second set of SRS resources is equal to the second maximum number. In some examples, the scheduling information manager 1440 may be configured as or otherwise support means for sending, to the UE, second scheduling information for transmitting a second uplink shared channel, wherein the second uplink shared channel at least partially overlaps in time with the uplink shared channel. In some examples, the uplink reception manager 1445 may be configured as or otherwise support means for receiving a second uplink shared channel from the UE, where the second number of layers of the second uplink shared channel is equal to the second number of SRS resources indicated by the scheduling information.

[0177] In some examples, the UE SRS capability manager 1430 may be configured as or otherwise support a component for receiving, via a second control message, an indication of a third maximum number of SRS resources for a separate uplink transmission associated with a downlink reference signal, and an indication of a fourth maximum number of SRS resources for a separate uplink transmission associated with a second downlink reference signal, wherein the maximum number of SRS resources and the second maximum number of SRS resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

[0178] In some examples, to support sending the scheduling information and the second scheduling information, the scheduling information manager 1440 may be configured as or otherwise support means for sending the scheduling information and the second scheduling information via the same DCI.

[0179] In some examples, to support sending the scheduling information and the second scheduling information, the scheduling information manager 1440 can be configured as or otherwise support means for sending the scheduling information via the first DCI. In some examples, to support sending the scheduling information and the second scheduling information, the scheduling information manager 1440 can be configured as or otherwise support means for sending the second scheduling information via the second DCI.

[0180] Figure 15 A diagram illustrates a system 1500 including a device 1505 that supports techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure. Device 1505 can be an example of device 1205, device 1305, or network entity 105 as described herein, or include components thereof. Device 1505 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1505 may include components that support outgoing and incoming communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0181] As described herein, the transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535 or memory 1525 or both) may be included in a chip or chip assembly installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0182] Memory 1525 may include RAM and ROM. Memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium (such as system memory) or another type of memory. In some cases, code 1530 may not be directly executable by processor 1535, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1525 may include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0183] The processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1535. The processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting techniques for dynamically switching between asymmetric antenna panels for uplink). For example, the device 1505 or a component of the device 1505 may include a processor 1535 and a memory 1525 coupled to the processor 1535, the processor 1535 and the memory 1525 being configured to perform the various functions described herein. Processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that can host functionality for performing the functions of device 1505 (e.g., by executing code 1530). Processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within memory 1525). In some implementations, processor 1535 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs that can be delivered to other systems or components (e.g., of device 1505). For example, a processing system of device 1505 may refer to a system that includes various other components or subcomponents of device 1505 (such as processor 1535, or transceiver 1510, or communications manager 1520, or other components or combinations of components of device 1505). The processing system of device 1505 can be interfaced with other components of device 1505 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1505 may include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that the device 1505 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1505 can obtain information or signal input and pass the information to the processing system. A person skilled in the art will readily recognize that a first interface can also obtain information or signal input, and a second interface can also output information or signal output.

[0184] In some examples, bus 1540 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1505, or communications performed between different components of device 1505 that may be co-located or located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of the different components or divided between the different components).

[0185] In some examples, communication manager 1520 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1520 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1520 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UEs 115 in coordination with other network entities 105. In some examples, communication manager 1520 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0186] According to the examples disclosed herein, the communication manager 1520 may support wireless communications at a network entity. For example, the communication manager 1520 may be configured as or otherwise support a component for sending a first control message to a UE, the first control message indicating an SRS resource set associated with a CSI-RS. The communication manager 1520 may be configured as or otherwise support a component for receiving a second control message from the UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The communication manager 1520 may be configured as or otherwise support a component for receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The communication manager 1520 may be configured as or otherwise support a component for sending scheduling information for sending an uplink shared channel to the UE. The communication manager 1520 may be configured as or otherwise support means for receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information.

[0187] By including or configuring a communication manager 1520 according to examples as described herein, the device 1505 can support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

[0188] In some examples, the communication manager 1520 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise coordinating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 can be supported or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 can include instructions that can be executed by the processor 1535 to cause the device 1505 to perform various aspects of the techniques for dynamically switching between asymmetric antenna panels for uplink as described herein, or the processor 1535 and the memory 1525 can be otherwise configured to perform or support such operations.

[0189] Figure 16A flow chart illustrating a method 1600 for supporting techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 11 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0190] At 1605, the method may include receiving a first control message from a network entity, the first control message indicating a set of SRS resources associated with a CSI-RS. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 10 The described SRS resource configuration manager 1025 is executed.

[0191] At 1610, the method may include sending a second control message to a network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by reference to Figure 10 The described SRS capability manager 1030 is executed.

[0192] At 1615, the method may include sending the SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 10 The described SRS transmission manager 1035 is executed.

[0193] At 1620, the method may include receiving scheduling information for transmitting an uplink shared channel from a network entity. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 10 The described scheduling information manager 1040 is executed.

[0194] At 1625, the method may include transmitting an uplink shared channel to the network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Figure 10 The described uplink transmission manager 1045 is performed.

[0195] Figure 17 A flow chart illustrating a method 1700 for supporting techniques for dynamic switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE as described in reference to Figures 1 to 11 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0196] At 1705, the method may include receiving a first control message from a network entity, the first control message indicating a set of SRS resources associated with a CSI-RS. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 10 The described SRS resource configuration manager 1025 is executed.

[0197] At 1710, the method may include sending a second control message to a network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a method as described in reference to Figure 10 The described SRS capability manager 1030 is executed.

[0198] At 1715, the method may include sending UCI including a beam report indicating a beam associated with a downlink reference signal. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by reference to Figure 10 The described UCI manager 1050 is executed.

[0199] At 1720, the method may include sending the SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figure 10 The described SRS transmission manager 1035 is executed.

[0200] At 1725, the method may include receiving scheduling information for transmitting an uplink shared channel from a network entity. The operations of 1725 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figure 10 The described scheduling information manager 1040 is executed.

[0201] At 1730, the method may include transmitting an uplink shared channel to the network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information. The operations of 1730 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1730 may be performed as described in reference to Figure 10 The described uplink transmission manager 1045 is performed.

[0202] Figure 18 A flow chart illustrating a method 1800 for supporting techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or component thereof as described herein. Figures 1 to 7 and Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0203] At 1805, the method may include sending a first control message to the UE, the first control message indicating a set of SRS resources associated with the CSI-RS. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 14 The described SRS resource configuration manager 1425 is executed.

[0204] At 1810, the method may include receiving a second control message from the UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of a CSI-RS. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by Figure 14 The UE SRS capability manager 1430 described above is used to perform the above operations.

[0205] At 1815, the method may include receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figure 14 The described SRS reception manager 1435 is executed.

[0206] At 1820, the method may include sending scheduling information for sending an uplink shared channel to the UE. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Figure 14 The described scheduling information manager 1440 is executed.

[0207] At 1825, the method may include receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information. The operations of 1825 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed as described in reference to Figure 14 The described uplink reception manager 1445 is executed.

[0208] Figure 19 A flow chart illustrating a method 1900 for supporting techniques for dynamically switching between asymmetric antenna panels for uplink according to one or more aspects of the present disclosure is illustrated. The operations of the method 1900 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or component thereof as described herein. Figures 1 to 7 and Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0209] At 1905, the method may include sending a first control message to the UE, the first control message indicating a set of SRS resources associated with the CSI-RS. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Figure 14 The described SRS resource configuration manager 1425 is executed.

[0210] At 1910, the method may include receiving a second control message from the UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of a CSI-RS. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by reference to Figure 14 The UE SRS capability manager 1430 described above is used to perform the above operations.

[0211] At 1915, the method may include receiving UCI including a beam report indicating a beam associated with a downlink reference signal. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by Figure 14 The described UCI manager 1450 is executed.

[0212] At 1920, the method may include receiving an SRS set from a UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Figure 14 The described SRS reception manager 1435 is executed.

[0213] At 1925, the method may include sending scheduling information for sending an uplink shared channel to the UE. The operations of 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed as described in reference to Figure 14 The described scheduling information manager 1440 is executed.

[0214] At 1930, the method may include receiving an uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information. The operations of 1930 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1930 may be performed as described in reference to Figure 14 The described uplink reception manager 1445 is executed.

[0215] The following provides an overview of various aspects of the disclosure:

[0216] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first control message from a network entity, the first control message indicating an SRS resource set associated with a CSI-RS; sending a second control message to the network entity, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS; sending an SRS set to the network entity via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number; receiving scheduling information for sending an uplink shared channel from the network entity; and sending the uplink shared channel to the network entity using a number of uplink shared channel ports equal to the number of SRS resources indicated by the scheduling information.

[0217] Aspect 2: The method according to aspect 1, wherein sending the second control message includes: sending UCI including a beam report, the beam report indicating the beam associated with the downlink reference signal.

[0218] Aspect 3: The method according to aspect 2, wherein sending the SRS set comprises sending the SRS set after a duration after sending the UCI.

[0219] Aspect 4: The method of aspect 2, further comprising: receiving an acknowledgment in response to the UCI from the network entity, wherein sending the SRS set is based at least in part on receiving the acknowledgment.

[0220] Aspect 5: According to the method of Aspect 2, the method also includes: receiving a third control message from the network entity, the third control message indicating that the SRS resources in the SRS resource set are to be updated, wherein sending the SRS set is at least partially based on the third control message.

[0221] Aspect 6: The method according to any one of aspects 1 to 5, wherein receiving the scheduling information includes receiving an indication of one or more SRS resources in the subset of the set of SRS resources.

[0222] Aspect 7: According to the method according to any one of Aspects 1 to 6, the method further includes: receiving an indication of the TCI state and the downlink reference signal QCL.

[0223] Aspect 8: According to the method according to any one of aspects 1 to 7, the method further includes: receiving an indication that the TCI state is configured with the downlink reference signal.

[0224] Aspect 9: According to the method of any one of aspects 1 to 8, the method further includes: selecting the subset of the SRS resource set from the SRS resource set based at least in part on the corresponding index values ​​of the SRS resources in the SRS resource set.

[0225] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: receiving an indication of a second set of SRS resources associated with a second CSI-RS via the first control message; sending an indication of a second maximum number of SRS resources associated with a second downlink reference signal received by the UE via the second control message, wherein the second downlink reference signal is associated with a second TCI state of the second CSI-RS; sending a second set of SRS to the network entity via a second subset of the second set of SRS resources, wherein the number of SRS resources in the second subset of the second set of SRS resources is equal to the second maximum number; receiving second scheduling information for sending a second uplink shared channel from the network entity, wherein the second uplink shared channel at least partially overlaps with the uplink shared channel in time; and sending the second uplink shared channel to the network entity using a second number of uplink shared channel ports equal to the second number of SRS resources indicated by the second scheduling information.

[0226] Aspect 11: The method according to Aspect 10 further includes: sending, via the second control message, an indication of a third maximum number of SRS resources for separate uplink transmissions associated with the downlink reference signal, and an indication of a fourth maximum number of SRS resources for separate uplink transmissions associated with the second downlink reference signal, wherein the maximum number of SRS resources and the second maximum number of SRS resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

[0227] Aspect 12: The method according to any one of aspects 10 to 11, wherein receiving the scheduling information and the second scheduling information comprises: receiving the scheduling information and the second scheduling information via the same DCI.

[0228] Aspect 13: The method according to any one of aspects 10 to 12, wherein receiving the scheduling information and the second scheduling information comprises: receiving the scheduling information via a first DCI; and receiving the second scheduling information via a second DCI.

[0229] Aspect 14: A method for wireless communication at a network entity, the method comprising: sending a first control message to a UE, the first control message indicating an SRS resource set associated with a CSI-RS; receiving a second control message from the UE, the second control message indicating a maximum number of SRS resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a TCI state of the CSI-RS; receiving an SRS set from the UE via a subset of the SRS resource set, wherein the number of SRS resources in the subset of the SRS resource set is equal to the maximum number; sending scheduling information for sending an uplink shared channel to the UE; and receiving the uplink shared channel from the UE, wherein the number of layers of the uplink shared channel is equal to the number of SRS resources indicated by the scheduling information.

[0230] Aspect 15: The method according to aspect 14, wherein receiving the second control message includes: receiving UCI including a beam report, the beam report indicating the beam associated with the downlink reference signal.

[0231] Aspect 16: The method of aspect 15, wherein receiving the SRS set comprises receiving the SRS set after a duration after receiving the UCI.

[0232] Aspect 17: The method according to aspect 15, further comprising: sending an acknowledgement in response to the UCI to the UE, wherein receiving the SRS set is based at least in part on sending the acknowledgement.

[0233] Aspect 18: The method according to aspect 15 further includes: sending a third control message to the UE, the third control message indicating that the SRS resources in the SRS resource set are to be updated, wherein receiving the SRS set is at least partially based on the third control message.

[0234] Aspect 19: The method according to any one of aspects 14 to 18, wherein sending the scheduling information comprises sending an indication of one or more SRS resources in the subset of the set of SRS resources.

[0235] Aspect 20: According to the method described in any one of Aspects 14 to 19, the method further includes: sending an indication of a second set of SRS resources associated with a second CSI-RS via the first control message; receiving an indication of a second maximum number of SRS resources associated with a second downlink reference signal received by the UE via the second control message, wherein the second downlink reference signal is associated with a second TCI state of the second CSI-RS; receiving a second set of SRS from the UE via a second subset of the second set of SRS resources, wherein the number of SRS resources in the second subset of the set of SRS resources is equal to the second maximum number; sending second scheduling information for sending a second uplink shared channel to the UE, wherein the second uplink shared channel at least partially overlaps with the uplink shared channel in time; and receiving the second uplink shared channel from the UE, wherein the second number of layers of the second uplink shared channel is equal to the second number of SRS resources indicated by the scheduling information.

[0236] Aspect 21: The method according to Aspect 20 further includes: receiving, via the second control message, an indication of a third maximum number of SRS resources for separate uplink transmissions associated with the downlink reference signal, and an indication of a fourth maximum number of SRS resources for separate uplink transmissions associated with the second downlink reference signal, wherein the maximum number of SRS resources and the second maximum number of SRS resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

[0237] Aspect 22: The method according to any one of aspects 20 to 21, wherein sending the scheduling information and the second scheduling information comprises: sending the scheduling information and the second scheduling information via the same DCI.

[0238] Aspect 23: The method according to any one of aspects 20 to 22, wherein sending the scheduling information and the second scheduling information comprises: sending the scheduling information via a first DCI; and sending the second scheduling information via a second DCI.

[0239] Aspect 24: An apparatus for wireless communication at a UE, the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 13.

[0240] Aspect 25: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0241] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0242] Aspect 27: An apparatus for wireless communication at a network entity, the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method according to any one of Aspects 14 to 23.

[0243] Aspect 28: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 14 to 23.

[0244] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 14 to 23.

[0245] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0246] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0247] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0248] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, 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 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 combination with a DSP core, or any other such configuration).

[0249] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or transmitted using one or more instructions or codes of a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0250] Computer readable medium includes both non-transient computer storage medium and communication medium, and this communication medium includes any medium that promotes computer program to be transferred from one location to another location.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, magnetic disk storage device or other magnetic storage device or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer readable medium.For example, if software is to be sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Magnetic disks can reproduce data magnetically, and optical discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0251] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0252] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0253] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description can apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0254] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0255] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the UE to: receiving a first control message from a network entity, the first control message indicating a set of sounding reference signal resources associated with a channel state information reference signal; sending a second control message to the network entity, the second control message indicating a maximum number of sounding reference signal resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a transmission configuration indicator state of the channel state information reference signal; sending a sounding reference signal set to the network entity via a subset of the sounding reference signal resource set, wherein a number of sounding reference signal resources in the subset of the sounding reference signal resource set is equal to the maximum number; receiving scheduling information for sending an uplink shared channel from the network entity; as well as The uplink shared channel is transmitted to the network entity using a number of uplink shared channel ports equal to the number of sounding reference signal resources indicated by the scheduling information.

2. The apparatus of claim 1 , wherein to send the second control message, the one or more processors, individually or collectively, are further operable to execute the code to cause the UE to: Uplink control information including a beam report is transmitted, the beam report indicating a beam associated with the downlink reference signal.

3. The apparatus of claim 2 , wherein, to transmit the sounding reference signal set, the one or more processors, individually or collectively, are further operable to execute the code to cause the UE to: The sounding reference signal set is sent after a duration after sending the uplink control information.

4. The apparatus of claim 2 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: An acknowledgement is received from the network entity in response to the uplink control information, wherein sending the set of sounding reference signals is based at least in part on receiving the acknowledgement.

5. The apparatus of claim 2, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: A third control message is received from the network entity, the third control message indicating that sounding reference signal resources in the set of sounding reference signal resources are to be updated, wherein sending the set of sounding reference signal resources is based at least in part on the third control message.

6. The apparatus of claim 1 , wherein to receive the scheduling information, the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: An indication of one or more sounding reference signal resources in the subset of the set of sounding reference signal resources is received.

7. The apparatus of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: An indication of quasi-co-location of the transmit configuration indicator state with the downlink reference signal is received.

8. The apparatus of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: An indication that the transmit configuration indicator state is configured with the downlink reference signal is received.

9. The apparatus of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: The subset of the set of sounding reference signal resources is selected from the set of sounding reference signal resources based at least in part on respective index values ​​of sounding reference signal resources in the set of sounding reference signal resources.

10. The apparatus of claim 1 , wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: receiving, via the first control message, an indication of a second set of sounding reference signal resources associated with a second channel state information reference signal; transmitting, via the second control message, an indication of a second maximum number of sounding reference signal resources associated with a second downlink reference signal received by the UE, wherein the second downlink reference signal is associated with a second transmit configuration indicator state of the second channel state information reference signal; sending a second set of sounding reference signal resources to the network entity via a second subset of the second set of sounding reference signal resources, wherein a number of sounding reference signal resources in the second subset of the second set of sounding reference signal resources is equal to the second maximum number; receiving, from the network entity, second scheduling information for transmitting a second uplink shared channel, wherein the second uplink shared channel at least partially overlaps in time with the uplink shared channel; as well as The second uplink shared channel is transmitted to the network entity using a second number of uplink shared channel ports equal to a second number of sounding reference signal resources indicated by the second scheduling information.

11. The apparatus of claim 10, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the UE to: An indication of a third maximum number of sounding reference signal resources for separate uplink transmissions associated with the downlink reference signal and an indication of a fourth maximum number of sounding reference signal resources for separate uplink transmissions associated with the second downlink reference signal are sent via the second control message, wherein the maximum number of sounding reference signal resources and the second maximum number of sounding reference signal resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

12. The apparatus of claim 10, wherein to receive the scheduling information and the second scheduling information, the one or more processors, individually or collectively, are further operable to execute the code to cause the UE to: The scheduling information and the second scheduling information are received via the same downlink control information.

13. The apparatus of claim 10, wherein to receive the scheduling information and the second scheduling information, the one or more processors, individually or collectively, are further operable to execute the code to cause the UE to: receiving the scheduling information via first downlink control information; and The second scheduling information is received via second downlink control information.

14. An apparatus for wireless communication at a network entity, the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and individually or collectively operable to execute the code to cause the network entity to: sending a first control message to a user equipment (UE), the first control message indicating a sounding reference signal resource set associated with a channel state information reference signal; receiving a second control message from the UE, the second control message indicating a maximum number of sounding reference signal resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a transmit configuration indicator state of the channel state information reference signal; receiving a sounding reference signal set from the UE via a subset of the sounding reference signal resource set, wherein a number of sounding reference signal resources in the subset of the sounding reference signal resource set is equal to the maximum number; Sending scheduling information for sending an uplink shared channel to the UE; as well as The uplink shared channel is received from the UE, wherein the number of layers of the uplink shared channel is equal to the number of sounding reference signal resources indicated by the scheduling information.

15. The apparatus of claim 14, wherein to receive the second control message, the one or more processors, individually or collectively, are further operable to execute the code to cause the network entity to: Uplink control information including a beam report is received, the beam report indicating a beam associated with the downlink reference signal.

16. The apparatus of claim 15, wherein to receive the sounding reference signal set, the one or more processors, individually or collectively, are further operable to execute the code to cause the network entity to: The set of sounding reference signals is received after a duration after receiving the uplink control information.

17. The apparatus of claim 15, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: An acknowledgement is sent to the UE in response to the uplink control information, wherein receiving the set of sounding reference signals is based at least in part on sending the acknowledgement.

18. The apparatus of claim 15, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: A third control message is sent to the UE, the third control message indicating that a sounding reference signal resource in the set of sounding reference signal resources is to be updated, wherein receiving the set of sounding reference signal resources is based at least in part on the third control message.

19. The apparatus of claim 14, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: An indication of one or more sounding reference signal resources in the subset of the set of sounding reference signal resources is sent.

20. The apparatus of claim 14, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: sending, via the first control message, an indication of a second set of sounding reference signal resources associated with a second channel state information reference signal; receiving, via the second control message, an indication of a second maximum number of sounding reference signal resources associated with a second downlink reference signal received by the UE, wherein the second downlink reference signal is associated with a second transmit configuration indicator state of the second channel state information reference signal; receiving a second set of sounding reference signal resources from the UE via a second subset of the second set of sounding reference signal resources, wherein a number of sounding reference signal resources in the second subset of the second set of sounding reference signal resources is equal to the second maximum number; sending, to the UE, second scheduling information for sending a second uplink shared channel, wherein the second uplink shared channel at least partially overlaps with the uplink shared channel in time; as well as The second uplink shared channel is received from the UE, wherein a second number of layers of the second uplink shared channel is equal to a second number of sounding reference signal resources indicated by the scheduling information.

21. The apparatus of claim 20, wherein the one or more processors are further operable, individually or collectively, to execute the code to cause the network entity to: and receiving, via the second control message, an indication of a third maximum number of sounding reference signal resources for separate uplink transmissions associated with the downlink reference signal and an indication of a fourth maximum number of sounding reference signal resources for separate uplink transmissions associated with the second downlink reference signal, wherein the maximum number of sounding reference signal resources and the second maximum number of sounding reference signal resources are associated with overlapping uplink transmissions associated with the downlink reference signal and the second downlink reference signal.

22. The apparatus of claim 20, wherein to transmit the scheduling information and the second scheduling information, the one or more processors, individually or collectively, are further operable to execute the code to cause the network entity to: The scheduling information and the second scheduling information are transmitted via the same downlink control information.

23. The apparatus of claim 20, wherein to transmit the scheduling information and the second scheduling information, the one or more processors, individually or collectively, are further operable to execute the code to cause the network entity to: transmitting the scheduling information via first downlink control information; and The second scheduling information is transmitted via second downlink control information.

24. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first control message from a network entity, the first control message indicating a set of sounding reference signal resources associated with a channel state information reference signal; sending a second control message to the network entity, the second control message indicating a maximum number of sounding reference signal resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a transmission configuration indicator state of the channel state information reference signal; sending a sounding reference signal set to the network entity via a subset of the sounding reference signal resource set, wherein a number of sounding reference signal resources in the subset of the sounding reference signal resource set is equal to the maximum number; receiving scheduling information for sending an uplink shared channel from the network entity; as well as The uplink shared channel is transmitted to the network entity using a number of uplink shared channel ports equal to the number of sounding reference signal resources indicated by the scheduling information.

25. The method of claim 24, wherein sending the second control message comprises: Uplink control information including a beam report is transmitted, the beam report indicating a beam associated with the downlink reference signal.

26. The method of claim 25, wherein sending the sounding reference signal set comprises: The sounding reference signal set is sent after a duration after sending the uplink control information.

27. The method according to claim 25, further comprising: An acknowledgement is received from the network entity in response to the uplink control information, wherein sending the set of sounding reference signals is based at least in part on receiving the acknowledgement.

28. The method according to claim 25, further comprising: A third control message is received from the network entity, the third control message indicating that sounding reference signal resources in the set of sounding reference signal resources are to be updated, wherein sending the set of sounding reference signal resources is based at least in part on the third control message.

29. The method of claim 24, wherein receiving the scheduling information comprises: An indication of one or more sounding reference signal resources in the subset of the set of sounding reference signal resources is received.

30. A method for wireless communication at a network entity, the method comprising: sending a first control message to a user equipment (UE), the first control message indicating a sounding reference signal resource set associated with a channel state information reference signal; receiving a second control message from the UE, the second control message indicating a maximum number of sounding reference signal resources associated with a downlink reference signal received by the UE, wherein the downlink reference signal is associated with a transmit configuration indicator state of the channel state information reference signal; receiving a sounding reference signal set from the UE via a subset of the sounding reference signal resource set, wherein a number of sounding reference signal resources in the subset of the sounding reference signal resource set is equal to the maximum number; Sending scheduling information for sending an uplink shared channel to the UE; as well as The uplink shared channel is received from the UE, wherein the number of layers of the uplink shared channel is equal to the number of sounding reference signal resources indicated by the scheduling information.

Images