Stacked sounding reference signals on uplink data transmission

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may identify time and frequency resources allocated to an uplink shared channel, and may identify a threshold signal-to-noise ratio (SNR) associated with the time and frequency resources. The UE may transmit both an uplink data signal and a sounding reference signal (SRS) via at least time and frequency resources. The uplink data signal and the SRS may overlap in time and frequency within time and frequency resources. The uplink data signal may be transmitted using a first transmit power, and the SRS may be transmitted using a second transmit power. The first transmit power and the second transmit power may be based on a threshold SNR.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 332,108, filed June 9, 2023, entitled “SUPERIMPOSED SOUNDING REFERENCE SIGNALS ON UPLINK DATA TRANSMISSIONS”, which is assigned to the assignee of this application and whose entire contents are expressly incorporated herein by reference. Technical Field

[0002] The following pertains to wireless communication, including sounding reference signals (SRS) superimposed on uplink data transmission. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Some examples of such multiple access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems. Other examples of multiple access systems include fifth-generation (5G) systems and sixth-generation (6G) systems, which may be referred to as New Radio (NR) systems. These systems, and other generations of multiple access systems, can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more network entities, each supporting wireless communication for communication devices (which may be referred to as User Equipment (UE)). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting a sounding reference signal (SRS) superimposed on uplink data transmission. For example, the described technology provides a framework for transmitting both uplink data signals and SRS via the same resource allocation. In some examples, the user equipment (UE) can identify time and frequency resources allocated to the uplink shared channel. The UE can also identify a threshold signal-to-noise ratio (SNR) associated with the time and frequency resources. The UE can transmit both the uplink data signal and SRS at least via the time and frequency resources. The uplink data signal and SRS can overlap in time and frequency within the time and frequency resources. A first transmit power can be used to transmit the uplink data signal, and a second transmit power can be used to transmit the SRS. The first and second transmit powers can be based on a threshold SNR.

[0005] A method for wireless communication at a UE is described. The method may include: identifying time and frequency resources allocated to an uplink shared channel; identifying a threshold SNR associated with the time and frequency resources; and transmitting both an uplink data signal and an SRS at least via the time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power, and the SRS is transmitted using a second transmit power, the first transmit power and the second transmit power being based on the threshold SNR.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor, at least one memory coupled to the at least one processor, and instructions stored in the at least one memory. The instructions are executable by the at least one processor to cause the apparatus to: identify time and frequency resources allocated to an uplink shared channel; identify a threshold SNR associated with the time and frequency resources; and transmit both an uplink data signal and an SRS at least via the time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power, and the SRS is transmitted using a second transmit power, the first transmit power and the second transmit power being based on the threshold SNR.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: units for identifying time and frequency resources allocated to an uplink shared channel; units for identifying a threshold SNR associated with the time and frequency resources; and units for transmitting both an uplink data signal and an SRS at least via the time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power, and the SRS is transmitted using a second transmit power, the first transmit power and the second transmit power being based on the threshold SNR.

[0008] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: identify time and frequency resources allocated to an uplink shared channel; identify a threshold SNR associated with the time and frequency resources; and transmit both an uplink data signal and an SRS at least via the time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power, and the SRS is transmitted using a second transmit power, the first transmit power and the second transmit power being based on the threshold SNR.

[0009] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of both uplink data signals and SRS may include operations, features, means, or instructions for transmitting a combined signal, which includes uplink data signals and SRS, at least via time and frequency resources.

[0010] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, transmitting the combined signal may include operations, features, units or instructions for performing the following: transmitting the uplink data signal via the time and frequency resources; and transmitting the SRS via the time and frequency resources and at least a second time and frequency resource that may also be allocated to the uplink shared channel.

[0011] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, at least a portion of the SRS may be superimposed on at least a portion of the uplink data signal within the time and frequency resources, and at least a portion of the uplink data signal may be superimposed on at least a portion of the SRS within the time and frequency resources.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: transmitting an uplink message instructing the UE to transmit SRS via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the SRS in both time and frequency within the time and frequency resources may be based on the capability.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving an indication of one or more parameters for transmitting SRS via time and frequency resources allocated to an uplink shared channel, wherein the transmission of uplink data signals and SRS via time and frequency resources may be based on one or more parameters.

[0014] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the one or more parameters include a period associated with transmitting SRS via time and frequency resources allocated to the uplink shared channel, or a threshold SNR, or both.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting a second SRS via a second time and frequency resource using a third transmit power that may be higher than the second transmit power.

[0016] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, time and frequency resources may be based on a first period that can be associated with transmissions via SRS allocated time and frequency resources to the uplink shared channel, and second time and frequency resources may be based on a second period that can be associated with transmissions via SRS not allocated time and frequency resources to the uplink shared channel.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second cycle may be shorter than the first cycle.

[0018] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the second SRS can be used at the network entity to estimate the properties of the downlink channel between the UE and the network entity, and the SRS can be used at the network entity to track the properties.

[0019] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, identifying a threshold SNR may include operations, features, components or instructions for receiving control signaling that indicates the threshold SNR.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control signaling includes DCI messages, MAC-CE, or RRC messages.

[0021] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, identifying the threshold SNR may include operations, features, units or instructions for identifying the threshold SNR from a set of threshold SNRs based on the time and frequency resources.

[0022] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the threshold SNR may be based on the MCS associated with time and frequency resources, or the rank associated with time and frequency resources, or both.

[0023] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the threshold SNR may be based on the SNR associated with the decoded uplink data signal.

[0024] A method for wireless communication at a network entity is described. The method may include: acquiring both an uplink data signal and a SRS (Service-Responding Response) signal, at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signal and the SRS overlap in time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired at a first receive power, and the SRS is acquired at a second receive power less than the first receive power, the first receive power and the second receive power being based on a threshold SNR associated with the time and frequency resources; decoding the uplink data signal based on the first receive power satisfying the threshold SNR; and processing the SRS based on the decoding of the uplink data signal.

[0025] An apparatus for wireless communication at a network entity is described. The apparatus may include at least one processor, at least one memory coupled to the at least one processor, and instructions stored in the at least one memory. The instructions are executable by the at least one processor to cause the apparatus to perform the following operations: acquiring both an uplink data signal and a SRS at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired at a first receive power, and the SRS is acquired at a second receive power less than the first receive power, the first receive power and the second receive power being based on a threshold SNR associated with the time and frequency resources; decoding the uplink data signal based on the first receive power satisfying the threshold SNR; and processing the SRS based on the decoding of the uplink data signal.

[0026] Another apparatus for wireless communication at a network entity is described. The apparatus may include: unit for acquiring both an uplink data signal and a SRS at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired using a first receive power, and the SRS is acquired using a second receive power less than the first receive power, the first receive power and the second receive power being based on a threshold SNR associated with the time and frequency resources; unit for decoding the uplink data signal based on the first receive power satisfying the threshold SNR; and unit for processing the SRS based on decoding the uplink data signal.

[0027] A non-transitory computer-readable medium is described, storing code for wireless communication at a network entity. The code may include instructions executable by a processor to perform the following operations: acquiring both an uplink data signal and a signal-received restatement (SRS) at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired at a first receive power, and the SRS is acquired at a second receive power less than the first receive power, the first and second receive powers being based on a threshold signal-to-noise ratio (SNR) associated with the time and frequency resources; decoding the uplink data signal based on the first receive power satisfying the threshold SNR; and processing the SRS based on the decoding of the uplink data signal.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, obtaining both the uplink data signal and the SRS may include operations, features, means, or instructions for obtaining a combined signal, which includes the uplink data signal and the SRS, at least via time and frequency resources.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for subtracting decoded uplink data signals from combined signals, wherein processing of SRS may be based on this subtraction.

[0030] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, obtaining the combined signal may include operations, features, units or instructions for performing the following: obtaining the uplink data signal via the time and frequency resources; and obtaining the SRS via the time and frequency resources and at least a second time and frequency resource allocated to the uplink shared channel.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for processing the SRS to satisfy a threshold processing gain based on the processing gain of the SRS across time and frequency resources and a second time and frequency resource in time or frequency.

[0032] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, time and frequency resources occur during a first time slot, and second time and frequency resources occur during either the first or second time slot.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: processing the SRS may be based on the combined received power of the SRS across the said time and frequency resources and the second time and frequency resources satisfying a second threshold SNR.

[0034] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, at least a portion of the SRS may be superimposed on at least a portion of the uplink data signal within the time and frequency resources, and at least a portion of the uplink data signal may be superimposed on at least a portion of the SRS within the time and frequency resources.

[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for obtaining an uplink message instructing a UE to transmit SRS via time and frequency resources allocated to an uplink shared channel, wherein the overlap of uplink data signals and SRS in both time and frequency within the time and frequency resources may be based on that capability.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for outputting indications of one or more parameters for transmitting SRS via time and frequency resources allocated to an uplink shared channel, wherein obtaining uplink data signals and SRS via time and frequency resources may be based on one or more parameters.

[0037] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the one or more parameters include a period associated with transmitting SRS via time and frequency resources allocated to the uplink shared channel, or a threshold SNR, or both.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a second SRS having a third receive power that may be higher than the second receive power via a second time and frequency resource.

[0039] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, time and frequency resources may be based on a first period that can be associated with transmissions via SRS allocated time and frequency resources to the uplink shared channel, and second time and frequency resources may be based on a second period that can be associated with transmissions via SRS not allocated time and frequency resources to the uplink shared channel.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second cycle may be shorter than the first cycle.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing: estimating the properties of the downlink channel between the UE and a network entity based on a second SRS; and tracking the properties of the downlink channel based on the SRS.

[0042] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, control signaling indicating the threshold SNR is output.

[0043] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the threshold SNR may be based on the MCS associated with time and frequency resources, or the rank associated with time and frequency resources, or both.

[0044] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the threshold SNR may be based on the SNR associated with the decoded uplink data signal. Attached Figure Description

[0045] Figure 1 and Figure 2 An example of a wireless communication system that supports the superposition of a probe reference signal (SRS) on uplink data transmission according to one or more aspects of this disclosure is shown.

[0046] Figure 3 An example of a signal combination scheme for SRS superimposed on uplink data transmission, according to one or more aspects of this disclosure, is shown.

[0047] Figure 4 An example of a power graph of SRS superimposed on uplink data transmission supported by one or more aspects of this disclosure is shown.

[0048] Figure 5 An example of an SRS process flow overlaid on uplink data transmission is shown, supported by one or more aspects of this disclosure.

[0049] Figure 6 and Figure 7 A block diagram of an apparatus supporting SRS overlay on uplink data transmission according to one or more aspects of this disclosure is shown.

[0050] Figure 8 A block diagram of a communication manager supporting SRS overlay on uplink data transmission according to one or more aspects of this disclosure is shown.

[0051] Figure 9 A diagram of a system including an apparatus supporting SRS overlay on uplink data transmission is shown, according to one or more aspects of this disclosure.

[0052] Figure 10 and Figure 11 A block diagram of an apparatus supporting SRS overlay on uplink data transmission according to one or more aspects of this disclosure is shown.

[0053] Figure 12 A block diagram of a communication manager supporting SRS overlay on uplink data transmission according to one or more aspects of this disclosure is shown.

[0054] Figure 13 A diagram of a system including an apparatus that supports SRS overlay on uplink data transmission is shown, according to one or more aspects of this disclosure.

[0055] Figure 14 and Figure 15 A flowchart illustrating a method for supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. Detailed Implementation

[0056] Some wireless communication systems can support precoding operations for directional communication. For example, wireless communication devices operating within a wireless communication system can communicate via directional transmission, where beamforming can be applied to form a beam in one direction. In some examples of beamforming (e.g., for digital beamforming), communication devices (e.g., transmitting communication devices, receiving communication devices) can apply signal processing techniques to select, shape, or manipulate a beam (e.g., an antenna, a directional beam) along a spatial path between the communication device and one or more other communication devices. In some examples of beamforming, the spatial orientation of the formed beam can depend on a set of parameters applied at the communication device (e.g., the communication device generating the beam). This set of parameters may be referred to herein as a precoder or precoding matrix.

[0057] Wireless communication systems may support one or more technologies for selecting a precoder. For example, a wireless communication system may include a user equipment (UE) that supports technologies for selecting a precoder for uplink communication (e.g., for selecting an uplink precoder). Additionally or alternatively, the wireless communication system includes one or more network entities that can support technologies for selecting a precoder for downlink communication (e.g., for selecting a downlink precoder). In some examples, the network entity may select the downlink precoder based on channel estimation performed at the UE. For example, the network entity may transmit a number of downlink reference signals to the UE on a downlink channel. The UE may perform one or more measurements on the downlink reference signals to estimate the downlink channel and may report the estimated downlink channel to the network entity for selecting the downlink precoder. In some examples, the number of downlink reference signals transmitted from the network entity may be based on the number of antenna elements used at the network entity (e.g., for downlink communication). Additionally, in some examples, the number of antenna elements used at the network entity may be based on one or more radio frequencies used at the network entity (e.g., for downlink communication). For example, signals transmitted using relatively high radio frequencies may experience relatively high path loss, and therefore, network entities can use an increased number of antennas for downlink transmissions with relatively high radio frequencies. However, in some examples, using an increased number of antennas to transmit downlink reference signals to the UE (e.g., for channel estimation) may result in increased overhead.

[0058] In some other examples, the network entity may select a downlink precoder based on channel estimation performed at the network entity. For example, the network entity may assume that the downlink and uplink channels between the network entity and the UE are reciprocal (e.g., the uplink channel conditions are relatively similar to the downlink channel conditions). Therefore, the network entity can use uplink channel estimation to determine the downlink precoder. For example, the UE may transmit an uplink reference signal, such as a sounding reference signal (SRS), to the network entity on the uplink channel. The network entity uses the SRS to estimate the uplink channel and, under the reciprocity assumption, selects a downlink precoder based on the estimated uplink channel. However, in some examples, the UE may be configured to avoid transmitting uplink data signals during time and frequency resources configured for SRS transmission. Therefore, to maintain an appropriate throughput for data transmission between the UE and the network entity, the UE may transmit SRS relatively infrequently. However, in some examples, relatively infrequent SRS transmissions may result in relatively infrequent opportunities for channel estimation at the network entity. The relatively infrequent channel estimation at network entities can cause the downlink precoder selected at the network entity (e.g., based on channel estimation using SRS) to become obsolete. An obsolete downlink precoder can degrade the performance of downlink communication between the UE and the network entity, potentially reducing throughput.

[0059] Various aspects of this disclosure relate to techniques for superimposing SRS onto uplink data transmission or vice versa, and more specifically, to frameworks for superimposing SRS onto uplink data signals or vice versa. Examples herein can be described based on SRS superimposed on uplink data signals; however, it should be understood that the techniques described herein are agnostic regarding which signal is considered superimposed on another signal, and therefore can also be applied to superimposing uplink data signals onto SRS. In some examples, the UE can identify time and frequency resources allocated to the uplink shared channel. For example, a network entity can configure the UE (or the UE can be otherwise configured) using time and frequency resources allocated to the uplink shared channel for uplink data transmission. In some examples, the UE can identify a threshold signal-to-noise ratio (SNR) based on the identified time and frequency resources. For example, the threshold SNR may correspond to the SNR used to decode uplink data signals transmitted via the time and frequency resources. In some examples, the UE can identify the threshold SNR based on signaling from a network entity (e.g., downlink shared channel signaling, downlink control channel signaling). In some other examples, the UE can identify the threshold SNR from a set of threshold SNRs configured at the UE (e.g., autonomously).

[0060] The UE can transmit both uplink data signals and SRS via identified time and frequency resources. In this way, the uplink data signals and SRS can overlap in time and frequency within the time and frequency resources. That is, the SRS can be superimposed on the uplink data signals within the time and frequency resources (or the uplink data signals can be superimposed on the SRS). For example, the UE can add the SRS signal to the uplink data signal to obtain a combined signal, and the UE can transmit the combined signal. In some examples, the UE can use a first transmit power to transmit the uplink data signal and can use a second transmit power to transmit the SRS (e.g., the uplink data signal can be generated or otherwise processed according to the first transmit power, and the SRS can be generated or otherwise processed according to the second transmit power, such that the combined signal includes an uplink data signal component based on the first transmit power and an SRS component based on the second transmit power).

[0061] The second transmit power can be lower than the first transmit power, for example, to reduce the likelihood that SRS will degrade the performance of the uplink data signal. Additionally, in some examples, the first and second transmit powers can be based on a threshold SNR. For example, the first transmit power may meet the threshold SNR (e.g., it may be equal to or greater than the threshold SNR), and the second transmit power may not meet the threshold SNR (e.g., it may be less than the threshold SNR). Network entities can use one or more techniques to obtain both the uplink data signal and SRS. In some examples, network entities can use SRS to estimate the uplink channel, or to track the estimated uplink channel, or both.

[0062] Aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. For example, the technology employed by the described communication device can provide benefits and enhancements to the operation of the communication device, including improved precoder selection or tracking at network entities. Operations performed by the described communication device to improve precoder selection or tracking at network entities may include transmitting both SRS and uplink data signals via the same time and frequency resources. In some examples, operations performed by the described communication device may also support increased throughput and increased reliability of communications within the wireless communication system, among other benefits.

[0063] The various aspects of this disclosure are first described within the context of a wireless communication system. These aspects are also described in the context of signal combination schemes, power diagrams, and process flows. The various aspects of this disclosure are further illustrated and described through apparatus diagrams, system diagrams, and flowcharts related to SRS overlaid on uplink data transmission.

[0064] Figure 1An example of a wireless communication system 100 supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. 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 improved LTE (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 expressly mentioned herein.

[0065] Network entity 105 can be distributed throughout a geographic area to form wireless communication system 100, and can include devices of different forms or with different capabilities. In various examples, network entity 105 may be referred to by nomenclature such as network element, mobile element, radio access network (RAN) node, or network device. In some examples, network entity 105 and UE 115 can wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographic coverage area), on which UE 115 and network entity 105 can establish one or more communication links 125. Coverage area 110 may be an example of a geographic area where network entity 105 and UE 115 can support signal communication according to one or more radio access technologies (RATs).

[0066] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s or network entities 105, such as... Figure 1 As shown.

[0067] As described herein, a node in 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first, second, and third nodes may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include public UE 115, network entity 105, device, equipment, computing system, or node, etc. For example, public UE 115 is configured to receive information from network entity 105, and first node is also public, configured to receive information from second node.

[0068] In some examples, network entity 105 may communicate with core network 130, or communicate with each other, or both. For example, network entity 105 may 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 entity 105 may 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 entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may 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), other instances therebetween, or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0069] One or more of the network entities 105 described herein may include or be referred to as base station 140 (e.g., base transceiver, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), fifth-generation (5G) NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which 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 base station 140).

[0070] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed among 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, network entity 105 may include one or more central units (CU) 160, distributed units (DU) 165, radio units (RU) 170, RAN intelligent controllers (RIC) 175 (e.g., near-real-time RIC, non-real-time RIC), service management and orchestration (SMO) systems 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0071] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functions depending on the functions performed at CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptive Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU160 can connect to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layer functions, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functions and signaling, each of which can be at least partially controlled by the CU 160. Alternatively, a protocol stack functional split can be employed between the DU 165 and RU 170, allowing the DU 165 to support one or more layers of the protocol stack, and the RU 170 to support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, functional splitting between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions at the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions at the protocol layer are performed by different functions within CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165s via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170s via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by the respective network entity 105 communicating via such a communication link.

[0072] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) can partially control each other. One or more IAB nodes 104 can be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s can be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 can include IAB mobile terminals (IAB-MTs) controlled (e.g., scheduled) by DU 165 coupled to IAB donors. IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas of IAB node 104 (e.g., the same antennas of RU 170) for access via DU 165 of IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within the 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 IAB node 104) may be configured to operate according to the techniques described herein.

[0073] When the techniques described herein are applied in the context of a deconverged RAN architecture, one or more components of the deconverged RAN architecture can be configured to support SRS overlaid on uplink data transmission as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the deconverged RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0075] like Figure 1 As shown, the UE 115 described herein can communicate with various types of devices, such as other UE 115s that may sometimes act as relays, as well as network entities 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.

[0076] UE 115 and network entity 105 can 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" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating 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 coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between a device and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can mean that any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicates with another device (e.g., directly or via one or more other network entities 105).

[0077] The signal waveform transmitted via a carrier can consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can refer to the resource of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can 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., over the transmission duration) and a relatively high modulation scheme order can correspond to a relatively high communication rate. Wireless communication resources can refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0078] The time interval used for network entity 105 or UE 115 can be expressed as a multiple of the basic time unit, for example, it can refer to A sampling period of seconds, for which It can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by its System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0079] Each frame may include multiple 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 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 number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some examples of the wireless communication system 100, the time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of the symbol period is related to the sampling period. The duration of the symbol period can depend on the subcarrier spacing or the operating frequency band.

[0080] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively or additionally, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst form of a shortened TTI (sTTI)).

[0081] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM technologies can be used to multiplex physical control channels and physical data channels via downlink carriers for signaling. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a group of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner with one or more aggregation levels. The aggregation level of the control channel candidates can 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 set may include: a common search space set configured to send control information to multiple UEs 115, and a UE-specific search space set used to send control information to a specific UE 115.

[0082] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage for mobile coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0083] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication can include private 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 prioritizing 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 are used interchangeably herein.

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

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

[0086] Wireless communication system 100 can operate using one or more frequency bands, ranging from 300 MHz to 300 GHz. Typically, the region from 300 MHz to 3 GHz is referred to as the Very High Frequency (UHF) region or decimeter band, due to its wavelength range of approximately 1 decimeter to 1 meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum (HF or VHF), communication using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0087] Wireless communication system 100 may use licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band, employing Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be based on carrier aggregation configurations combined with component carriers used for operation with licensed bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0088] Network entity 105 (e.g., base station 140, RU 170) or 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) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit beamforming or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (e.g., an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include antenna arrays having a set of rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support RF beamforming for signals transmitted via antenna ports.

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

[0090] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, 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 UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals based on different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (e.g., network entity 105) or by a receiving device (e.g., UE 115)) using transmissions along different beam directions so that network entity 105 may transmit or receive later.

[0091] Some signals, such as data signals associated with a specific 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., the direction associated with the receiving device, such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0092] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., network entity 105 or UE 115), and the device can 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 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 can transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may employ similar techniques to transmit signals multiple times along different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

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

[0094] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and network entity 105 or core network 130. The PHY layer can map transport channels to physical channels.

[0095] Wireless communication system 100 can support precoding operations for directional communication. Therefore, wireless communication system 100 can also support one or more techniques for selecting a precoder. According to such techniques, network entity 105 can select a downlink precoder based on channel estimation performed at UE 115. For example, network entity 105 can transmit a certain amount of downlink reference signal to UE 115 on the downlink channel. UE 115 can perform one or more measurements on the downlink reference signal to estimate the downlink channel and can report the estimated downlink channel to network entity 105 for selection of the downlink precoder. In some examples, such as for relatively high-frequency deployments, network entity 105 can use an increased number of antennas for downlink communication. Thus, network entity 105 can transmit an increased amount of downlink reference signal to UE 115 for channel estimation, which can result in increased overhead and reduced throughput.

[0096] In some other examples, network entity 105 may select a downlink precoder based on channel estimation performed at network entity 105. For example, UE 115 may transmit an uplink reference signal (such as SRS) to network entity 105 on an uplink channel. Network entity 105 uses SRS to estimate the uplink channel and, under the reciprocity assumption, selects a downlink precoder based on the estimated uplink channel. However, in some examples, UE 115 may avoid transmitting uplink data signals during time and frequency resources configured for SRS transmission. Therefore, to maintain an appropriate throughput for data transmitted between UE 115 and network entity 105, UE 115 may transmit SRS relatively infrequently. In some examples, relatively infrequent SRS transmissions may result in relatively infrequent opportunities for channel estimation at network entity 105, which may degrade downlink precoding at network entity 105 and thus degrade the performance of downlink communication between UE 115 and network entity 105.

[0097] In some examples, UE 115 and network entity 105 may support a framework for superimposing SRS onto uplink data signals. In such examples, UE 115 may identify time and frequency resources allocated to the uplink shared channel. Additionally, UE 115 may identify a threshold SNR based on the identified time and frequency resources. In some examples, UE 115 may transmit both uplink data signals and SRS via the identified time and frequency resources. Thus, the uplink data signals and SRS can overlap in time and frequency within the time and frequency resources. In some examples, the UE may use a first transmit power to transmit uplink data signals and a second transmit power to transmit SRS. The first and second transmit powers may be based on a threshold SNR. For example, the first transmit power may meet the threshold SNR, while the second transmit power may not. Network entity 105 may use one or more techniques to obtain both uplink data signals and SRS. In some examples, network entity 105 may use SRS to estimate the uplink channel, or track the estimated uplink channel, or both. In such examples, sending both SRS and uplink data signals via the same time and frequency resources can improve downlink precoding while maintaining (or improving) throughput, among other benefits.

[0098] Figure 2 An example of a wireless communication system 200 supporting SRS superimposed on uplink data transmission according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 200 may implement or be implemented by one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 215, which may be a reference Figure 1 An example of UE 115 is described. The wireless communication system 200 may also include a network entity 205, which may be as described in reference... Figure 1 Examples of one or more of the network entities 105 described (e.g., CU, DU, RU, base station, IAB node, or one or more other network nodes). Network entity 205 and UE 215 can communicate using communication link 220, which can be as described in reference... Figure 1 An example of communication link 125 is described. For example, communication link 220 could be an example of an uplink (e.g., a Uu interface). Figure 2 In the example, UE 215 and network entity 205 can communicate within coverage area 210, which can be as shown in the reference. Figure 1 An example of coverage area 110 is described. Wireless communication system 200 may include features for improving communication between network entity 205 and UE 215, as well as other benefits.

[0099] Wireless communication system 200 may support precoding operations for directional communication (e.g., beamforming). For example, wireless communication devices (e.g., UE 215, network entity 205) operating within wireless communication system 200 may communicate via directional transmission, where beamforming may be applied to form a beam in one direction. That is, UE 215 or network entity 205, or both, may communicate via directional transmission (e.g., beamforming), where one or more antenna elements may be used to apply beamforming to form a beam in one direction. In some examples of beamforming (e.g., for digital beamforming), communication devices (e.g., transmitting communication devices, receiving communication devices) may apply signal processing techniques to select, shape, or manipulate beams (e.g., antennas, directional beams) along a spatial path between the communication device and one or more other communication devices. In other words, UE 215 or network entity 205, or both, may apply beamforming to form a beam along a spatial path between UE 215 and network entity 205 (e.g., for directional transmission or reception). In some examples of beamforming, the spatial orientation of the formed beam can depend on a set of parameters applied by a communication device (e.g., the communication device that generates the beam). This set of parameters may be referred to herein as a precoder or precoding matrix.

[0100] Wireless communication system 200 may support one or more techniques for selecting a precoder. For example, wireless communication system 200 may support one or more techniques for selecting a precoder used at UE 215 (e.g., a precoder for uplink communication, an uplink precoder) or a precoder used at network entity 205 (e.g., a precoder for downlink communication, a downlink precoder), or both. In some examples, network entity 205 may select a downlink precoder based on channel estimation performed at UE 215. That is, network entity 205 may use channel estimation at UE 215 to determine the precoder for downlink communication between UE 215 and network entity 205. In other words, the use of UE channel estimation may include gNB downlink precoding (e.g., singular value decomposition (SVD) precoding, MU-MIMO).

[0101] For example, network entity 205 may transmit CSI-RS (or another type of downlink reference signal) to UE 215 on a downlink channel. UE 215 may receive the CSI-RS and may perform one or more measurements to estimate the downlink channel on which the CSI-RS is transmitted. That is, UE 215 may estimate the downlink channel based on one or more measurements performed on the downlink reference signal (e.g., CSI-RS) transmitted via the downlink channel (e.g., Reference Signal Received Power (RSRP) measurement, Signal-to-Interference Plus Noise Ratio (SINR) measurement). In some examples, UE 215 may report the estimated downlink channel to network entity 205. For example, UE 215 may send a report (e.g., a CSI report) to network entity 205 indicating the estimated downlink channel (e.g., indicating multiple parameters that indicate the estimated downlink channel or otherwise associate with the estimated downlink channel) so that network entity 205 can select a precoder for downlink transmission to UE 215 (e.g., so that network entity 205 can select a downlink precoder).

[0102] In some examples, network entity 205 may send multiple CSI-RS (e.g., beamforming CSI-RS) to UE 215. For example, UE 215 may receive a number of CSI-RS from network entity 205. UE 215 may use this number of CSI-RS to estimate the downlink channel (e.g., one or more attributes of the downlink channel) and may report the estimated downlink channel to network entity 205 for selection of a downlink precoder. In some examples, the number of CSI-RS (or other types of downlink reference signals) sent from network entity 205 for downlink channel estimation (e.g., at UE 215) may be based on the number of antenna elements at network entity 205 (e.g., the number of antenna elements used at network entity 205, such as those used for downlink communication). Additionally, in some examples, the number of antenna elements at network entity 205 (or the number of antenna elements used at network entity 205) may be based on one or more radio frequencies used for wireless communication at network entity 205.

[0103] For example, signals transmitted using relatively high radio frequencies may experience relatively high path loss. Thus, network entity 205 can be configured to use an increased number of antennas (e.g., antenna elements, antenna arrays) to achieve adequate coverage of signals transmitted using relatively high radio frequencies. However, in some examples, using an increased number of antennas to transmit CSI-RS to UE 215 (e.g., for channel estimation) may lead to increased overhead. That is, in some examples, network entity 205 may transmit one or more CSI-RS per antenna at network entity 205. Therefore, as the number of antennas at network entity 205 increases, the number of CSI-RS transmitted to UE 215 (e.g., for channel estimation) may also increase, which may result in increased processing at UE 215 (e.g., to estimate the downlink channel) or increased signaling overhead (e.g., to report the estimated downlink channel) or both. Therefore, using CSI-RS for downlink channel estimation may be relatively inefficient for some high-frequency deployments. In other words, for higher radio frequency bands (e.g., millimeter wave (mmW) bands, sub-THz bands, or frequency range 3 (FR3) bands), network entity 205 (e.g., gNB) can use a relatively large number of transmit antennas. In some examples, a relatively large number of transmit antennas may result in CSI-RS-based channel estimation being relatively impractical (e.g., because there are more transmit antennas at network entity 205 than receive antennas at UE 215).

[0104] In some other examples, network entity 205 may select a downlink precoder based on channel estimation performed at network entity 205. That is, for some high-frequency deployments, such as for NR (e.g., sixth-generation (6G)) deployments, network entity 205 may select a downlink precoder based on uplink channel estimation. For example, network entity 205 may assume that the downlink channel and uplink channel (e.g., between network entity 205 and UE 215) are reciprocal, and therefore the uplink channel estimation can be used to determine the downlink precoder. That is, the reciprocity between the uplink channel and the downlink channel can be assumed (e.g., by UE 215, by network entity 205) such that the downlink channel (e.g., one or more properties of the downlink channel) can be inferred at network entity 205 from the uplink channel (e.g., from uplink communication sent by UE 215). In other words, network entity 205 may infer the downlink channel condition based on measurements performed on the uplink reference signal (e.g., SRS) at network entity 205. For example, UE 215 can transmit an SRS to network entity 205 over an uplink channel. Network entity 205 can receive the SRS and use it to measure the uplink channel over which the SRS was transmitted. That is, UE 215 can transmit an SRS to network entity 205 so that network entity 205 (e.g., gNB) can perform channel estimation for downlink communication (e.g., at the receiver at UE 215) under the reciprocity assumption. In other words, network entity 205 can estimate the uplink channel based on measurements performed on the transmitted uplink reference signal (e.g., RSRP measurement, SINR measurement). For example, network entity 205 can receive an SRS (or another type of uplink reference signal) from UE 215 via an uplink channel, can estimate the uplink channel based on measurements performed on the SRS, and can select a downlink precoder based on the estimated uplink channel.

[0105] In some examples, UE 215 may use antenna switching to transmit one or more SRS to network entity 205. In such examples, this SRS transmission enables network entity 205 (e.g., gNB) to perform channel estimation. That is, under the reciprocity assumption, transmitting SRS to network entity 205 enables network entity 205 to estimate the channel experienced at the UE receiver. Antenna switching can be a relatively common SRS pattern. In some examples of antenna switching, UE 215 may use multiple antennas to transmit SRS over multiple durations (e.g., symbols, time slots) (e.g., across multiple durations). That is, UE 215 may use multiple antennas to transmit repetitions of SRS via one or more time and frequency resources that may occur over multiple symbols or multiple time slots.

[0106] In some examples, UE 215 may be configured to transmit SRS via multiple time and frequency resources (e.g., via multiple SRS resources) occurring during multiple symbol periods in the same time slot. For example, UE 215 may be configured with a first SRS port (e.g., SRS port 0), which may be associated with a first SRS resource occurring during a first symbol period in the same time slot and a second SRS resource occurring during a second symbol period in the same time slot. In such an example, UE 215 may use a first antenna (e.g., UE antenna port 0) to transmit SRS during the first symbol period and a second antenna (e.g., UE antenna port 1) to transmit SRS during the second symbol period. In some other examples, UE 215 may be configured with a first SRS port (e.g., SRS port 0) and a second SRS port (e.g., SRS port 1). The first SRS port and the second SRS port may each be associated with a first SRS resource and a second SRS resource. In such an example, UE 215 may use both the first and second antennas to transmit SRS during the first symbol period. Additionally, UE 215 may use a third antenna (e.g., UE antenna port 2) and a fourth antenna (e.g., UE antenna port 3) to transmit SRS during the second symbol.

[0107] In some other examples, UE 215 may be configured to transmit SRS via SRS resources occurring over multiple symbol periods across multiple time slots. For example, UE 215 may be configured with a first SRS port (e.g., SRS port 0). The first SRS port may be associated with a first SRS resource, a second SRS resource, a third SRS resource, and a fourth SRS resource. The first SRS resource may occur during the first symbol period of a first time slot, the second SRS resource may occur during the second symbol period of a first time slot, the third SRS resource may occur during the third symbol period of a second time slot, and the fourth SRS resource may occur during the fourth symbol period of a second time slot. In such an example, UE 215 may transmit SRS using a first antenna (e.g., UE antenna port 0) during the first symbol period, a second antenna (e.g., UE antenna port 1) during the second symbol period, a third antenna (e.g., UE antenna port 2) during the third symbol period, and a fourth antenna (e.g., UE antenna port 3) during the fourth symbol period. Antennas used for SRS transmission during the duration (e.g., time slot, symbol) can be based on an association (e.g., mapping) between the SRS port and the UE antenna port associated with the antenna.

[0108] In some examples, UE 215 can be configured to perform antenna switching for aperiodic SRS resources. Additionally or alternatively, UE 215 can be configured to perform antenna switching for periodic SRS resources. For example, UE 215 can be configured with a period during which UE 215 can send SRS to network entity 205. In such examples, UE 215 can select one or more antennas for SRS transmission based on the period. In some examples, the antennas used to transmit SRS during SRS resources (e.g., periodic SRS resources, aperiodic SRS resources) can be based on an association between one or more SRS ports and one or more UE antenna ports (e.g., corresponding antennas).

[0109] In some examples, UE 215 can be configured to avoid transmitting uplink data signaling during time and frequency resources configured for SRS transmission (e.g., during SRS resource periods). For example, UE 215 can be configured to avoid transmitting signaling via PUSCH (or receiving signaling via downlink channels, such as the Physical Downlink Shared Channel (PDSCH) or Physical Downlink Control Channel (PDCCH)) during SRS resource periods. Thus, to maintain appropriate throughput of data (e.g., uplink data transmitted via PUSCH or downlink data transmitted via PDSCH), the period configured at UE 215 for SRS transmission (e.g., the SRS resource period) can be relatively low. That is, UE 215 can be configured to transmit SRS relatively infrequently. In other words, higher SRS overhead (e.g., more SRS resources) can reduce throughput. Therefore, network entity 205 can constrain (e.g., reduce, decrease, limit) the period during which UE 215 can transmit SRS (e.g., limit the SRS resource period). However, a relatively low SRS resource cycle can lead to SRS aging, which can degrade the performance of downlink communication between network entity 205 and UE 215. In other words, configuring UE 215 to send SRS at a relatively low cycle can result in relatively infrequent opportunities for channel estimation at network entity 205 (e.g., using SRS). This relatively infrequent channel estimation at network entity 205 can cause the downlink precoder (e.g., selected at network entity 205 based on channel estimation) to become obsolete. An obsolete downlink precoder can degrade the performance of downlink communication between UE 215 and network entity 205, which can also reduce throughput.

[0110] In some examples, one or more techniques, as described herein, for overlaying SRS onto uplink data transmission can enable UE 215 to increase the frequency of SRS transmissions while maintaining (or increasing) throughput. For example, such techniques can provide a framework for overlaying SRS onto uplink data transmission, which can improve SRS aging and reduce SRS overhead. In other words, as described herein, techniques for overlaying SRS onto uplink data transmission can result in improved SRS aging (which can increase throughput) and reduced SRS overhead (which can also increase throughput).

[0111] like Figure 2 As shown in the example, superimposed SRS can be used (e.g., defined for) relatively high radio frequency bands. For example, network entity 205 can configure UE 215 (or UE 215 can be otherwise configured) to transmit combined signal 230 to network entity 205 via PUSCH. That is, UE 215 can be configured to transmit SRS over uplink data signals. In such an example, UE 215 can identify resource 235-b that can be allocated to the uplink shared channel. That is, resource 235-b can be an example of time and frequency resources allocated to PUSCH. For example, network entity 205 can configure UE 215 with resources 235-a and 235-b (or UE 215 can be otherwise configured). Resource 235-a can be an example of SRS resources (e.g., dedicated resources configured for SRS transmission within a time slot), and resource 235-b can be an example of PUSCH resources (e.g., resources allocated to PUSCH). In some examples, network entity 205 may configure UE 215 with resource 235-b (or resource 235-a) via control signaling, such as via downlink control information (DCI), MAC control element (MAC-CE), or RRC messages, and other examples of control signaling. In some other examples, resource 235-b or resource 235-a, or both, may be determined at UE 215 (e.g., autonomously) (e.g., it may be pre-configured at UE 215, or it may be determined at UE 215 based on rules, mappings, or periods).

[0112] UE 215 may identify SNR threshold 240 based on resource 235-b. For example, SNR threshold 240 may correspond to the SNR used for decoding uplink data signals transmitted via PUSCH. In some examples, decoding uplink data signals may be based on the modulation and coding scheme (MCS) or rank used for transmitting uplink data signals. Thus, SNR threshold 240 may be based on (e.g., associated with) the MCS or rank used for transmitting uplink data signals via resource 235-b. For example, UE 215 may be configured to use MCS or rank, or both, to transmit one or more uplink data signals via resource 235-b (e.g., via PUSCH). In such an example, SNR threshold 240 may be based on MCS, rank, or both.

[0113] In some examples, UE 215 may transmit combined signal 230 (e.g., both uplink data signal and SRS) via resource 235-b. In such examples, the uplink data signal and SRS may overlap in both time and frequency within resource 235-b. That is, SRS may be superimposed on the uplink data signal within resource 235-b. UE 215 may use a first transmit power to transmit the uplink data signal (of combined signal 230). Alternatively, UE 215 may use a second transmit power to transmit the SRS (of combined signal 230). In some examples, the first and second transmit powers may be based on an SNR threshold 240. For example, the first transmit power may satisfy the SNR threshold 240 (e.g., may exceed the SNR threshold 240, may be equal to or greater than the SNR threshold 240), and the second transmit power may not satisfy the SNR threshold 240 (e.g., may not exceed the SNR threshold 240, may be lower than the SNR threshold 240 by some amount, such as about 10 dB). In some examples, UE 215 may transmit SRS 225 via resource 235-a. In such examples, network entity 205 may use SRS 225 for channel estimation 245 and use combined signal 230 (e.g., SRS of combined signal 230) for channel tracking 250. That is, network entity 205 may use SRS 225 to estimate the uplink channel and select a downlink precoder (e.g., under the reciprocity assumption). Additionally, network entity 205 may use SRS superimposed on the uplink data signal (e.g., SRS of combined signal 230) to track the estimated uplink channel and, in some examples, update the selected downlink precoder. In some examples, transmitting combined signal 230 to network entity 205 may result in increased throughput, reduced overhead for SRS transmission, and improved channel tracking. In other words, superimposing SRS onto the uplink data signal can result in relatively high throughput, relatively low overhead for SRS transmission, improved gNB tracking for UE channel estimation (e.g., due to the relatively high SRS period), and other benefits.

[0114] Figure 3 An example of a signal combining scheme 300 supporting SRS superimposed on uplink data transmission according to one or more aspects of this disclosure is shown. In some examples, the signal combining scheme 300 may be implemented or be implemented in one or more aspects of wireless communication system 100 and wireless communication system 200. For example, the signal combining scheme 300 may be implemented at a UE or network entity, which may be as described in reference... Figure 1 and Figure 2 Examples of corresponding devices are described. Signal combination scheme 300 may include features for improving communication between network entities and UEs, as well as other benefits.

[0115] In some examples, the UE can be configured to multiplex SRS with uplink data signals (e.g., in time or in frequency). That is, the UE can multiplex SRS with uplink data transmitted via PUSCH signaling. For example, the UE can be configured to use different time-domain resources or different frequency-domain resources, or both, to transmit SRS and uplink data signals to network entities. However, in some examples, multiplexing SRS with uplink data signals in time or frequency may result in a reduction in data rate (e.g., reduced throughput). For example, the UE can be configured to multiplex SRS with uplink data signals in time on a set of time-domain resources. In such an example, the UE can use a portion of the time-domain resources for SRS transmission, and therefore, the UE can omit that portion of the time-domain resources for uplink data transmission, which can result in reduced throughput. Alternatively, the UE can be configured to multiplex SRS with uplink data signals in frequency on a set of frequency-domain resources. In such an example, the UE can use a portion of its frequency domain resources for SRS transmission, and therefore, the UE can choose not to use a portion of its frequency domain resources for uplink data transmission, which can result in reduced throughput.

[0116] To increase throughput, the UE may determine to reduce a portion of the time-domain resources or frequency-domain resources used for SRS transmission, allowing the UE to transmit SRS relatively infrequently. However, relatively infrequent SRS transmission may result in relatively infrequent channel estimation at the network entity. Relatively infrequent channel estimation may degrade downlink communication between the network entity and the UE. For example, the downlink precoder selected at the network entity based on channel estimation may become obsolete (e.g., over time) and may degrade the performance of downlink communication between the UE and the network entity, potentially leading to reduced throughput. In some other examples, the UE may be configured to support a framework for overlaying SRS onto uplink data transmission. For example, according to this framework, the UE may overlay at least a portion of the SRS onto at least a portion of the uplink data signal (e.g., or overlay at least a portion of the uplink data signal onto at least a portion of the SRS).

[0117] like Figure 3 As shown in the example, the UE can use signal combiner 315 to superimpose SRS 310 onto uplink data signal 305. That is, the UE can use signal combiner 315 to generate (e.g., output) a combined signal 320, which may include SRS 310 superimposed on uplink data signal 305 (e.g., added to and superimposed on uplink data signal 305), or vice versa. Although Figure 3The example shows the uplink data signal 305 as having a lower frequency than SRS 310, but the uplink data signal 305 can have a higher frequency than SRS 310, or the uplink data signal 305 can have the same frequency as SRS 310. Although Figure 3 The example shows both uplink data signal 305 and SRS 310 as sinusoidal waveforms; however, it should be understood that one or both can be of a different type of waveform. The combined signal 320 can be... Figure 2 Explanation and reference Figure 2 Examples of combined signals described. For example, a UE can identify time and frequency resources allocated to an uplink shared channel (e.g., PUSCH) and can transmit combined signal 320 to a network entity at least via the identified time and frequency resources. That is, the UE can transmit both SRS 310 and uplink data signal 305 via the same time and frequency resources that can be allocated to PUSCH.

[0118] In some examples, the UE may use a first transmit power for uplink data signal 305 and a second transmit power for SRS 310. The second transmit power may be less than the first transmit power, such that SRS 310 does not affect the performance of uplink data signal 305 (e.g., it does not affect the decoding of uplink data signal 305 at the network entity). For example, the UE may identify a threshold SNR for transmitting uplink data signal 305. In some examples, the UE may identify the threshold SNR based on control signaling received from the network entity. That is, the network entity may send control signaling (e.g., DCI, MAC-CE, RRC messages) indicating the threshold SNR to the UE. In some other examples, the UE may be configured with a threshold SNR set (e.g., a threshold SNR table) and may identify the threshold SNR from the threshold SNR set. In some examples, the UE may identify the threshold SNR based on time and frequency resources. For example, the threshold SNR may correspond to the SNR used for decoding uplink data signals transmitted via time and frequency resources.

[0119] The UE can transmit uplink data signal 305 based on a first transmit power that satisfies a threshold SNR. For example, the first transmit power may be equal to or greater than the threshold SNR, allowing the network entity to decode uplink data signal 305. Alternatively, the UE can transmit SRS 310 based on a second transmit power that may not satisfy the threshold SNR. For example, the second transmit power may be less than (e.g., about 10 dB less) the threshold SNR. In such an example, the network entity can use Continuous Interference Cancellation (SIC) to receive both uplink data signal 305 and SRS 310. For example, the network entity can receive a combined signal 320 and decode uplink data signal 305 (e.g., because the first transmit power is higher than the second transmit power). The network entity can then subtract the uplink data signal 305 from the combined signal 320 to obtain SRS 310 (e.g., SRS 310 and noise associated with the combined signal 320). Then, the network entity can process SRS 310—for example, the network entity can use SRS to estimate or track the properties of the communication channels (e.g., uplink channels, downlink channels) between the UE and the network entity.

[0120] In some examples, the UE can transmit SRS across multiple time and frequency resources. For example, the UE can transmit SRS via both time and frequency resources and a second time and frequency resource. In such examples, the processing gain of SRS 310 across multiple resources (e.g., in time or frequency) can enable network entities to use SRS 310 for channel estimation, channel tracking, or both (e.g., the processing gain can be high enough that network entities can use SRS for channel estimation, channel tracking, or both). That is, the UE can transmit multiple repetitions of SRS 310 across multiple time and frequency resources occurring within one or more durations (e.g., within a time slot or across multiple time slots), and network entities can combine (e.g., process jointly) these multiple repetitions to increase the processing gain of SRS 310. In some examples, superimposing SRS 310 on uplink data signal 305 can result in increased throughput, among other benefits.

[0121] Figure 4 An example of a power map 400 supporting SRS superimposed on uplink data transmission according to one or more aspects of this disclosure is shown. In some examples, the power map 400 may be implemented or implemented at one or more aspects of wireless communication system 100, wireless communication system 200, and signal combination scheme 300. For example, the power map 400 may be implemented at a UE or network entity, which may be as described in reference... Figures 1 to 3 Examples of corresponding devices are described. Power diagram 400 may include features for improving communication between network entities and UEs, as well as other benefits.

[0122] In some examples, the UE and network entities can be configured to support a framework for overlaying SRS onto uplink data signals. For example... Figure 4 As shown in the example, the UE can transmit both uplink data signals (e.g., PUSCH data signals) and SRS to the network entity during the time and frequency resources allocated to the uplink shared channel. That is, during the time and frequency resources, the network entity can receive a combined signal including both the uplink data signal and SRS (e.g., SRS superimposed on the uplink data signal). The combined signal can be a reference signal. Figure 2 and Figure 3 Examples of combined signals are shown and described. The UE can transmit uplink data signals based on uplink data signal power 405 and SRS based on SRS power 415. Noise associated with the combined signal may be at noise level 410. That is, noise associated with the combined signal may correspond to noise level 410 (e.g., the noise level of the combined signal may be noise level 410). In some examples, the UE can select uplink data signal power 405 such that the SNR of the uplink data signal (e.g., uplink data signal SNR 420) meets a threshold SNR for decoding the uplink data signal (e.g., for decoding uplink data signals transmitted via time and frequency resources). For example, uplink data signal SNR 420 may be equal to or greater than the threshold SNR for decoding the uplink data signal. In some examples, the UE may transmit SRS below uplink data signal SNR 420. As an illustrative example, SRS power 415 may be about 10 dB lower than uplink data signal SNR 420. Therefore, the SRS power 415 can also be about 10 dB lower than the noise level 410, and the SRS SINR 425 can be about 10 dB higher than the uplink data signal SNR 420. Figure 4 In the example, the uplink data signal SNR 420 can be approximately 30 dB, and the SRS SINR 425 can be approximately -40 dB (e.g., because the SRS power 415 is approximately 10 dB lower than the uplink data signal SNR 420). That is, the SRS power 415 can be approximately 40 dB lower than the uplink data signal power 405.

[0123] In some examples, network entities can use SIC to reduce interference between the uplink data signal and SRS, thereby improving the processing of SRS (e.g., and thus improving channel estimation of SRS). For example, a network entity can decode the uplink data signal (e.g., based on the uplink data signal power 405 satisfying a threshold SNR). The network entity can then cancel the decoded uplink data signal to obtain SRS. For example, the network entity can subtract the decoded uplink data signal from the combined signal (e.g., a received signal including both the uplink data signal and SRS). In some examples, after the network entity removes the uplink data signal from the combined signal, the SNR of SRS can be SRS SNR 430. That is, SRS SNR 430 can correspond to the SNR of SRS after SIC. Figure 4 In the example, SRS SNR 430 could be approximately -10 dB (e.g., because SRS power 415 is approximately 10 dB lower than noise level 410).

[0124] In some examples, a UE can transmit SRS via time and frequency resources as well as via one or more other time and frequency resources. That is, a UE can transmit multiple repetitions (e.g., multiple instances) of SRS via multiple time and frequency resources. In such examples (e.g., since the SRS is a known sequence of network entities), network entities can combine (e.g., jointly process) multiple SRS transmissions. That is, the SRS is a known signal of the network entity, and therefore, the network entity can collect (e.g., combine) the power of SRS across multiple frequency domain resources (e.g., across the bandwidth used for SRS repetition) or across multiple time domain resources (e.g., across multiple symbols) or both. In some examples, such as those where the network entity can combine (e.g., add) the power of SRS across multiple symbols (e.g., OFDM symbols or some other suitable duration), which may occur in the same time slot or in multiple (e.g., different) time slots. As an illustrative example, a UE can transmit SRS across 10 time and frequency resources, where time and frequency resources include symbols and subcarriers. In other words, a UE can transmit SRS across 10 resource elements. In such examples, the network entity can combine (e.g., add up) the power of the SRS across 10 symbols, 10 subcarriers, or both. In some examples, by combining the SRS across 10 resource elements (e.g., 10 symbols, 10 subcarriers), the network entity can increase the processing gain of the SRS to a processing gain of 435. That is, the processing gain 435 can correspond to the processing gain of the SRS. Therefore, the network entity can increase the SNR of the SRS to a post-processed SNR of 440. In other words, the post-processed SNR obtained (e.g., implemented) for the SRS at the network entity can correspond to the post-processed SNR 440. Figure 4 In this example, the processing gain 435 can be approximately 20 dB, and therefore the post-processed SNR 440 can be approximately +10 dB. That is, the post-processed SNR 440 can be approximately 10 dB higher than the noise level 410. In some examples, the post-processed SNR 440 can be suitable for channel tracking. In other words, the post-processed SNR obtained (e.g., implemented) for SRS at the network entity can be suitable for channel tracking. Therefore, the network entity can use SRS for channel tracking, which can lead to improved downlink precoder selection at the network entity, among other benefits.

[0125] Figure 5 An example of a process flow 500 supporting SRS overlay on uplink data transmission according to one or more aspects of this disclosure is shown. Process flow 500 may be implemented or be implemented at one or more aspects of wireless communication system 100, wireless communication system 200, signal combination scheme 300, and power map 400. For example, process flow 500 may include operation at UE 515 and network entity 505, which may be referenced herein. Figures 1 to 4 Examples of corresponding devices are described. In the following description of process flow 500, the operations between UE 515 and network entity 505 may occur in a different order than the exemplary order shown. Additionally or alternatively, the operations performed by UE 515 and network entity 505 may be performed in a different order or at different times. Some operations may also be omitted or combined. The operations performed by network entity 505 and UE 515 may support improvements to communication between UE 515 and network entity 505, as well as other benefits.

[0126] UE 515 and network entity 505 can be configured to support a framework for overlaying SRS onto uplink data transmissions (e.g., PUSCH data transmissions). That is, SRS can be transmitted as an overlaid signal onto PUSCH data transmissions from UE 515. In other words, UE 515 can transmit SRS to network entity 505 with PUSCH data transmissions (e.g., with each PUSCH data transmission or with a portion of a PUSCH data transmission). Figure 5 As shown in the example, UE 515 can identify the resource allocation used to send PUSCH data to network entity 505, and can use the same resource allocation to overlay SRS on PUSCH data.

[0127] At 530, UE 515 can identify the first time and frequency resources allocated to the uplink shared channel (e.g., PUSCH). For example, UE 515 can receive control signaling (e.g., DCI, MAC-CE, RRC messages) indicating the first time and frequency resources from network entity 505, or UE 515 can otherwise configure the first time and frequency resources. The time and frequency resources can be referenced... Figure 4 Examples of time and frequency resources described. For example, time and frequency resources can be examples of resource elements.

[0128] At 535, UE 515 can identify a threshold SNR for the first time and frequency resources. The threshold SNR can be determined by... Figures 2 to 4 Explanation and reference Figures 2 to 4 Examples of threshold SNR described. For example, the threshold SNR may be based on the SNR associated with decoding PUSCH data (e.g., uplink data signals) via time and frequency resources. That is, the threshold SNR may be associated with time and frequency resources. For example, the threshold SNR may be based on the MCS associated with the first time and frequency resources, or the rank associated with the first time and frequency resources, or both. In some examples, network entity 505 (e.g., gNB) may know (e.g., determine) the MCS and rank used for transmission of one or more PUSCHs via the first time and frequency resources (or via one or more other resources allocated to PUSCHs). Additionally, network entity 505 may know (e.g., determine) the threshold SNR used for decoding PUSCH transmissions (e.g., unicast PUSCH transmissions) via the first time and frequency resources (or via one or more other resources allocated to PUSCHs). Thus, network entity 505 may send a signaling notification (e.g., indicate) to UE 515 of the threshold SNR. For example, UE 515 may receive control signaling indicating a threshold SNR (e.g., via PDSCH or PDCCH) from network entity 505. For example, the control signaling may take the form of one or more DCI messages, one or more MAC-CE messages, or one or more RRC messages indicating the threshold SNR, as well as other possible types of control signaling. In some other examples, the threshold SNR may be determined (e.g., predefined, preconfigured) at UE 515. For example, UE 515 may be configured with a table of threshold SNRs (e.g., a set of one or more SNRs), and the threshold SNRs included in the table (e.g., each threshold SNR) may correspond to a corresponding MCS, or a corresponding rank, or both. Thus, UE 515 may determine the MCS associated with time and frequency resources, or the rank associated with time and frequency resources, or both. UE 515 may identify the threshold SNR for time and frequency resources from the set of threshold SNRs (e.g., based on the determined MCS or rank).

[0129] At 545, UE 515 can transmit both uplink data signals (e.g., PUSCH data) and SRS at least via first time and frequency resources. For example, UE 515 can transmit a combined signal, comprising both uplink data signals and SRS, at least via time and frequency resources. In other words, UE 515 can transmit uplink data signals and SRS such that at least a portion of the SRS is superimposed on at least a portion of the uplink data signals within the time and frequency resources, or at least a portion of the uplink data signals is superimposed on at least a portion of the SRS within the time and frequency resources. Thus, the uplink data signals and SRS can overlap in time and frequency within the first time and frequency resources. In some examples, the overlap of uplink data signals and SRS in time and frequency within the time and frequency resources can be based on the capabilities of UE 515.

[0130] In some scenarios, such as at 520, UE 515 may send an uplink message indicating its ability to transmit SRS via time and frequency resources allocated to the uplink shared channel. In other words, UE 515 may send an uplink message indicating its ability to overlay SRS onto uplink data signals. In some examples, UE 515 may send the uplink message as part of a handshake protocol between UE 515 and network entity 505. In such examples, the uplink message may indicate UE 515's ability to overlay SRS onto uplink data signals, as well as one or more other capabilities of UE 515.

[0131] The signal strength of the SRS can be lower than (e.g., much lower) the signal strength of the uplink data signal (e.g., PUSCH data). For example, the transmit power used to transmit the SRS at UE 515 can be lower than the transmit power used to transmit the uplink data signal at UE 515. Thus, the signal strength of the SRS can be lower than the signal strength of the uplink data signal, and therefore, the receive power of the SRS at network entity 505 can be lower than the receive power of the uplink data signal at network entity 505.

[0132] In some examples, the transmit power used at UE 515 for transmitting uplink data signals and the transmit power used at UE 515 for transmitting SRS can be based on a threshold SNR. For example, the transmit power used at UE 515 for uplink data signals may meet the threshold SNR (e.g., it may be equal to or greater than the threshold SNR), and a second transmit power may not meet the threshold SNR (e.g., it may be less than the threshold SNR). That is, SRS can be transmitted with a transmit power that may be lower than (e.g., about 10 dB lower or some other suitable power amount) the threshold SNR used for decoding uplink data signals (e.g., so that SRS may not affect the performance of uplink data signals). In some examples, the SINR of SRS can be negative (e.g., about -40 dB or some other suitable power amount). In such examples, interference contributing to SINR may be due to the uplink data signal. In some examples, the transmission of uplink data signals and the probe reference signal via time and frequency resources can be based on one or more parameters.

[0133] For example, at 525, UE 515 may receive an indication of the overlaid SRS configuration, which includes parameter indication from network entity 505. That is, UE 515 may receive an indication of one or more parameters for transmission of SRS via time and frequency resources allocated to the uplink shared channel (e.g., including first time and frequency resources). These one or more parameters may include: a period, or a threshold SNR, or both, associated with SRS transmission via time and frequency resources allocated to the uplink shared channel, and other examples of parameters that may be used at UE 515 for SRS transmission via uplink shared channel resources (e.g., PUSCH resources). For example, signaling indicating one or more parameters may include control signaling (e.g., DCI, MAC-CE, RRC messages) indicating the threshold SNR. In some examples, the signaling may include PDSCH signaling or PDCCH signaling. Additionally or alternatively, signaling indicating one or more parameters may include control signaling (e.g., DCI, MAC-CE, RRC messages) that indicates the period at which UE 515 may transmit SRS to network entity 505 via time and frequency resources allocated to PUSCH (e.g., how frequently UE 515 may overlay SRS onto PUSCH data transmission). In some examples, a first period in which UE 515 may transmit SRS via time and frequency resources allocated to PUSCH may be different from (or the same as) a second period in which UE 515 may transmit SRS via time and frequency resources not allocated to the uplink shared channel (e.g., via time and frequency resources not associated with PUSCH data transmission).

[0134] For example, at 540, UE 515 can transmit a second SRS to network entity 505 via second time and frequency resources. In such an example, the time and frequency resources used to transmit the SRS superimposed on the uplink data signal can be based on a first period, and the second time and frequency resources can be based on a second period. In some examples, the second period can be lower (or higher) than the first period. For example, UE 515 can transmit the second SRS based on (e.g., using) a transmit power that can be higher than the transmit power used at UE 515 to transmit the SRS superimposed on the uplink data signal. In such an example, the second SRS can be used at network entity 505 for channel estimation, and the SRS superimposed on the uplink data signal can be used at network entity 505 to track the estimated channel. That is, a reference signal with relatively high receive power can be suitable for channel estimation (e.g., with relatively high accuracy), and a reference signal with relatively low receive power can be suitable for channel tracking. Thus, network entity 505 can use the second SRS for channel estimation and the SRS superimposed on the uplink data signal for tracking the estimated channel. In some examples, the first and second cycles can be adjusted (e.g., dynamically) based on channel conditions. For example, network entity 505 can (e.g., based on one or more observations at network entity 505, such as observed uplink signaling quality from UE 515) determine whether to estimate the channel more frequently or less frequently (e.g., estimate one or more attributes of the channel). Therefore, network entity 505 can determine to adjust (e.g., increase or decrease) the second cycle. Additionally or alternatively, network entity 505 can (e.g., based on one or more observations at network entity 505, such as observed uplink signaling quality from UE 515) determine whether to track the channel more frequently or less frequently (e.g., track one or more attributes of the channel). Therefore, network entity 505 can determine to adjust (e.g., increase or decrease) the first cycle. In some other examples, UE 515 can (e.g., autonomously) determine whether to adjust the first or second cycle (e.g., based on one or more observations at UE 515, such as observed downlink signaling quality from network entity 505).

[0135] In some examples, at 550, network entity 505 can decode the uplink data signal. For example, network entity 505 (e.g., gNB) can decode the uplink data signal (e.g., PUSCH) and subtract the decoded uplink data signal (e.g., known data) from the received signal to receive the SRS signal. That is, network entity 505 can use SIC to decode the uplink data signal and subtract the decoded uplink data signal from the received signal to obtain the SRS signal. In other words, network entity 505 can use SIC to receive both the SRS and uplink data signals. For example, network entity 505 can receive a combined signal including the uplink data signal and the SRS. Network entity 505 can decode the uplink data signal and can subtract (e.g., eliminate) the decoded uplink data signal (e.g., known data) from the received combined signal to obtain the SRS signal. In some examples, decoding the uplink data signal at 550 can satisfy a threshold SNR based on the received power (or transmitted power) of the uplink data signal.

[0136] In some examples, at 555, network entity 505 may process SRS based on decoding the uplink data signal (e.g., and subtracting the uplink data signal from the received combined signal). For example, the SNR of SRS after SIC (e.g., after subtracting the decoded uplink data signal from the received combined signal) may be less than the SINR of SRS before SIC (e.g., the SNR of SRS after SIC may be about -10 dB). In some examples, the SNR of SRS after SIC (e.g., the SNR of SRS after SIC) may be suitable (e.g., sufficiently high) for processing SRS. That is, the SNR of SRS after SIC may be suitable for channel estimation using SRS, or suitable for channel tracking using SRS, or both.

[0137] In some examples, such as those where the SNR of PDSCH signaling from network entity 505 may be relatively high (e.g., for a relatively high PDSCH SNR scenario), precoding at network entity 505 may affect downlink transmission. In such examples, it may be desirable to improve the performance of channel estimation using SRS (e.g., to improve downlink precoder selection at network entity 505). UE 515 may determine multiple repetitions (e.g., multiple instances) of SRS to be transmitted across multiple time and frequency resources. For example, UE 515 may transmit SRS across multiple resource elements (e.g., approximately 10 resource elements or some other suitable number of resource elements). In such examples, network entity 205 may obtain an SRS processing gain that can be adapted to update the precoding (e.g., it can be high enough, such as approximately 20 dB or some other suitable amount of power). In other words, UE 515 can transmit SRS in multiple resource elements (e.g., in each of 10 resource elements), allowing network entity 505 to obtain relatively large processing gains for channel estimation (e.g., for precoder selection) or for channel tracking (e.g., for updating the precoder). For example, network entity 505 can increase SRS processing gain by combining (e.g., jointly processing) SRS across multiple resource elements (e.g., across 10 OFDM symbols). In some examples, processing SRS can satisfy a threshold processing gain based on the processing gain (in time or frequency) of SRS across multiple time and frequency resources. In other words, processing SRS can satisfy a threshold SNR for processing SRS based on the combined received power of SRS (in time or frequency) across multiple time and frequency resources. These multiple time and frequency resources can occur within the same time slot or across multiple time slots (e.g., between multiple time slots). In some examples, by overlaying the SRS onto the uplink data signal, UE515 can reduce SRS aging (e.g., reduce channel estimation aging, thereby reducing the likelihood that the precoder will become obsolete), which can improve the performance of downlink communication between network entity 505 and UE 515 (e.g., by enabling network entity 505 to update the downlink precoder), among other benefits.

[0138] Figure 6A block diagram 600 of a device 605 supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0139] Receiver 610 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and SRS-related information channels superimposed on uplink data transmission), or combinations thereof. The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0140] Transmitter 615 may provide a unit for transmitting signals generated by other components of device 605. For example, transmitter 615 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, and information channels associated with SRS superimposed on uplink data transmission). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may use one antenna or a collection of antennas.

[0141] Communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of SRS superimposed on uplink data transmission as described herein. For example, communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0142] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., with communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise individually or collectively to support units for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to at least one processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in at least one memory by at least one processor).

[0143] Alternatively or concurrently, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented using code executed by at least one processor (e.g., as communication management software or firmware). If implemented using code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support units for performing the functions described in this disclosure).

[0144] In some examples, the communication manager 620 can be configured to use or otherwise cooperate with the receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 can receive information from the receiver 610, send information to the transmitter 615, or integrate with the receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0145] According to the examples disclosed herein, the communication manager 620 can support wireless communication at the UE (e.g., device 605). For example, the communication manager 620 is capable of, configured to, or operable to support elements for identifying time and frequency resources allocated to the uplink shared channel. The communication manager 620 is capable of, configured to, or operable to support elements for identifying a threshold SNR associated with the time and frequency resources. The communication manager 620 is capable of, configured to, or operable to support elements for transmitting both uplink data signals and SRS at least via the time and frequency resources, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are transmitted using a first transmit power and the SRS are transmitted using a second transmit power, the first and second transmit powers being based on a threshold SNR.

[0146] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., at least one processor that controls or is otherwise coupled to the receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for more efficient use of communication resources.

[0147] Figure 7 A block diagram 700 of a device 705 supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720) may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] Receiver 710 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and SRS-related information channels superimposed on uplink data transmission), or combinations thereof. The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0149] Transmitter 715 may provide a unit for transmitting signals generated by other components of device 705. For example, transmitter 715 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, and information channels associated with SRS superimposed on uplink data transmission). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may use one antenna or a collection of antennas.

[0150] Device 705 or its various components may be examples of units for performing various aspects of SRS superimposed on uplink data transmission as described herein. For example, communication manager 720 may include resource identification component 725, SNR threshold component 730, signal combiner component 735, or any combination thereof. Communication manager 720 may be examples of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 720 may receive information from receiver 710, send information to transmitter 715, or integrate with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0151] According to the examples disclosed herein, the communication manager 720 can support wireless communication at the UE (e.g., device 705). The resource identification component 725 is capable of, configured to, or operable to support elements for identifying time and frequency resources allocated to the uplink shared channel. The SNR threshold component 730 is capable of, configured to, or operable to support elements for identifying a threshold SNR associated with the time and frequency resources. The signal combiner component 735 is capable of, configured to, or operable to support elements for transmitting both uplink data signals and SRS at least via time and frequency resources, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are transmitted using a first transmit power and the SRS are transmitted using a second transmit power, the first and second transmit powers being based on a threshold SNR.

[0152] Figure 8A block diagram 800 of a communication manager 820 supporting SRS superimposed on uplink data transmission according to one or more aspects of this disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of units for performing the various aspects of SRS superimposed on uplink data transmission as described herein. For example, the communication manager 820 may include a resource identification component 825, an SNR threshold component 830, a signal combiner component 835, a capability indication component 840, a parameter component 845, an SRS component 850, an uplink data signaling component 855, or any combination thereof. Components of each of these components or its sub-components (e.g., one or more processors, one or more memories) may communicate directly or indirectly with each other (e.g., via one or more buses).

[0153] According to the examples disclosed herein, the communication manager 820 can support wireless communication at the UE. The resource identification component 825 is capable of, configured to, or operable to support elements for identifying time and frequency resources allocated to the uplink shared channel. The SNR threshold component 830 is capable of, configured to, or operable to support elements for identifying a threshold SNR associated with the time and frequency resources. The signal combiner component 835 is capable of, configured to, or operable to support elements for transmitting both uplink data signals and SRS at least via time and frequency resources, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are transmitted using a first transmit power and the SRS are transmitted using a second transmit power, the first and second transmit powers being based on a threshold SNR.

[0154] In some examples, in order to support the transmission of both uplink data signals and SRS, the signal combiner component 835 can be configured or operable to support units for transmitting combined signals, which include uplink data signals and SRS, at least via time and frequency resources.

[0155] In some examples, to support the transmission of combined signals, the uplink data signaling component 855 can be configured or operable to support elements for transmitting uplink data signals via time and frequency resources. In some examples, to support the transmission of combined signals, the SRS component 850 can be configured or operable to support elements for transmitting SRS via time and frequency resources and at least a second time and frequency resource also allocated to the uplink shared channel.

[0156] In some examples, at least a portion of the SRS is superimposed on at least a portion of the uplink data signal within the time and frequency resources.

[0157] In some examples, the capability indication component 840 is capable of, configured to, or operable to support a unit for transmitting an uplink message that indicates the UE's ability to transmit SRS via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the SRS in both time and frequency within the time and frequency resources is based on this capability.

[0158] In some examples, parameter component 845 is capable of, configured to, or operable to support a unit for receiving an indication of one or more parameters for transmitting SRS via time and frequency resources allocated to the uplink shared channel, wherein the transmission of uplink data signals and SRS via time and frequency resources is based on the one or more parameters.

[0159] In some examples, the one or more parameters include a period, a threshold SNR, or both, associated with SRS transmissions via time and frequency resources allocated to the uplink shared channel. In some examples, the SRS component 850 is capable of, configured to, or operable to support elements for transmitting a second SRS via a third transmit power higher than the second transmit power using second time and frequency resources.

[0160] In some examples, the time and frequency resources are based on a first period associated with SRS transmissions via time and frequency resources allocated to the uplink shared channel. In some examples, the second time and frequency resources are based on a second period associated with SRS transmissions via time and frequency resources not allocated to the uplink shared channel. In some examples, the second period is shorter than the first period.

[0161] In some examples, the second SRS can be used at the network entity to estimate the attributes of the downlink channel between the UE and the network entity. In some examples, the SRS can be used at the network entity to track attributes. In some examples, to support the identification threshold SNR, the SNR threshold component 830 can be, configured, or operable to support elements for receiving control signaling indicating the threshold SNR. In some examples, the control signaling includes DCI, MAC-CE, or RRC messages.

[0162] In some examples, to support the identification of a threshold SNR, the SNR threshold component 830 can be, configured, or operated to support units for identifying a threshold SNR from a set of threshold SNRs based on time and frequency resources. In some examples, the threshold SNR is based on the MCS associated with the time and frequency resources, or the rank associated with the time and frequency resources, or both. In some examples, the threshold SNR is based on the SNR associated with the decoded uplink data signal.

[0163] Figure 9 A diagram of a system 900 including device 905 supporting SRS overlay on uplink data transmission, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or a component including device 705, device 805, or UE 115 as described herein. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 945).

[0164] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Alternatively or concurrently, I / O controller 910 can represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 910 can be implemented as part of one or more processors (such as at least one processor 940). In some cases, a user can interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0165] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. Transceiver 915 may communicate bidirectionally via one or more antennas 925, wired or wireless links as described herein. For example, transceiver 915 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 915 may also include a modem for modulating packets to provide modulated packets to one or more antennas 925 for transmission, and for demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0166] At least one memory 930 may include random access memory (RAM) or read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions, which, when executed by at least one processor 940, causes device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 930 may include a basic I / O system (BIOS), which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting SRS overlaid on uplink data transmission). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to at least one processor 940, at least one processor 940 and at least one memory 930 configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0168] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE (e.g., device 905). For example, the communication manager 920 is capable of, configured to, or operable to support elements for identifying time and frequency resources allocated to the uplink shared channel. The communication manager 920 is capable of, configured to, or operable to support elements for identifying a threshold SNR associated with the time and frequency resources. The communication manager 920 is capable of, configured to, or operable to support elements for transmitting both uplink data signals and SRS at least via the time and frequency resources, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are transmitted using a first transmit power and the SRS are transmitted using a second transmit power, the first and second transmit powers being based on a threshold SNR.

[0169] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support technologies for improving communication reliability, reducing latency, and utilizing communication resources more efficiently.

[0170] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or executed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions executable by at least one processor 940 to cause device 905 to perform aspects of the SRS superimposed on uplink data transmission as described herein, or at least one processor 940 and at least one memory 930 may otherwise be configured individually or jointly to perform or support such operations.

[0171] Figure 10 A block diagram 1000 of a device 1005 supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. Device 1005 may be an example of an aspect of network entity 105 described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0172] Receiver 1010 may provide units for acquiring (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Alternatively or additionally, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0173] Transmitter 1015 may provide a unit for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of device 1005. For example, transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Alternatively or additionally, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0174] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of the SRS superimposed on uplink data transmission as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0175] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., with communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware component, or any combination thereof, configured to, or otherwise individually or collectively, support a unit for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to at least one processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in at least one memory by at least one processor).

[0176] Alternatively or concurrently, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented using code executed by at least one processor (e.g., as communication management software or firmware). If implemented using code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support units for performing the functions described in this disclosure).

[0177] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from receiver 1010, send information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0178] Communication manager 1020 can support wireless communication at a network entity (e.g., device 1005) according to the examples disclosed herein. For example, communication manager 1020 can be configured or operable to support units for acquiring both uplink data signals and SRS at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are acquired at a first receive power, and the SRS are acquired at a second receive power less than the first receive power, the first and second receive powers being based on a threshold SNR associated with the time and frequency resources. Communication manager 1020 can be configured or operable to support units for decoding uplink data signals based on the first receive power satisfying the threshold SNR. Communication manager 1020 can be configured or operable to support units for processing SRS based on the decoded uplink data signals.

[0179] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., at least one processor that controls or is otherwise coupled to the receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for more efficient use of communication resources.

[0180] Figure 11A block diagram 1100 of a device 1105 supporting SRS overlaid on uplink data transmission according to one or more aspects of this disclosure is shown. Device 1105 may be an example of an aspect of device 1005 or network entity 105 described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] Receiver 1110 may provide units for acquiring (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Alternatively or additionally, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0182] Transmitter 1115 may provide a unit for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of device 1105. For example, transmitter 1115 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 1115 may support outputting information by transmitting signals via one or more antennas. Alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0183] Device 1105 or its various components may be examples of units for performing various aspects of SRS superimposed on uplink data transmission as described herein. For example, communication manager 1120 may include combination signal component 1125, data signal component 1130, reference signal component 1135, or any combination thereof. Communication manager 1120 may be examples of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0184] Communication manager 1120 may support wireless communication at a network entity (device 1105) according to the examples disclosed herein. Combining signal component 1125 is capable of, configured to, or operable to support units for acquiring both uplink data signals and SRS at least via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are acquired at a first receive power, and the SRS are acquired at a second receive power less than the first receive power, the first and second receive powers being based on a threshold SNR associated with the time and frequency resources. Data signal component 1130 is capable of, configured to, or operable to support units for decoding the uplink data signals based on the first receive power satisfying the threshold SNR. Reference signal component 1135 is capable of, configured to, or operable to support units for processing SRS based on decoding the uplink data signals.

[0185] Figure 12A block diagram 1200 of a communication manager 1220 supporting SRS superimposed on uplink data transmission according to one or more aspects of this disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of units for performing the various aspects of SRS superimposed on uplink data transmission as described herein. For example, the communication manager 1220 may include a combination signal component 1225, a data signal component 1230, a reference signal component 1235, a UE capability component 1240, a parameter indication component 1245, an SNR threshold indication component 1250, a channel estimation component 1255, a channel tracking component 1260, or any combination thereof. Each of these components or components in its sub-components (e.g., one or more processors, one or more memories) may communicate directly or indirectly with each other (e.g., via one or more buses), which may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualized components associated with network entity 105, between devices, components, or virtualized components associated with network entity 105), or any combination thereof.

[0186] Communication manager 1220 can support wireless communication at network entities according to the examples disclosed herein. Combining signal component 1225 is capable of, configured to, or operable to support units for acquiring both uplink data signals and SRS at least via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are acquired at a first receive power, while the SRS are acquired at a second receive power less than the first receive power, the first and second receive powers being based on a threshold SNR associated with the time and frequency resources. Data signal component 1230 is capable of, configured to, or operable to support units for decoding uplink data signals based on the first receive power satisfying the threshold SNR. Reference signal component 1235 is capable of, configured to, or operable to support units for processing SRS based on decoding the uplink data signals.

[0187] In some examples, to support the acquisition of both uplink data signals and SRS, the combined signal component 1225 can be configured or operable to support units for acquiring a combined signal, which includes the uplink data signal and SRS, at least via time and frequency resources. In some examples, the data signal component 1230 can be configured or operable to support units for subtracting the decoded uplink data signal from the combined signal, wherein SRS processing is based on this subtraction.

[0188] In some examples, to support the acquisition of combined signals, data signal component 1230 can be configured or operable to support elements for acquiring uplink data signals via time and frequency resources. In some examples, to support the acquisition of combined signals, reference signal component 1235 can be configured or operable to support elements for acquiring SRS via time and frequency resources and at least a second time and frequency resource allocated to the uplink shared channel.

[0189] In some examples, SRS processing is based on the processing gain of SRS across time and frequency resources and the processing gain of a second time and frequency resource in time or frequency satisfying a threshold processing gain. In some examples, the time and frequency resources occur during a first time slot, and the second time and frequency resources occur during either the first or second time slot. In some examples, SRS processing is based on the combined received power of SRS across time and frequency resources and the second time and frequency resources satisfying a second threshold SNR.

[0190] In some examples, at least a portion of the SRS is superimposed on at least a portion of the uplink data signal within the time and frequency resources.

[0191] In some examples, UE capability component 1240 is capable of, configured to, or operable to support a unit for obtaining uplink messages that instruct the UE to transmit SRS via time and frequency resources allocated to the uplink shared channel, wherein the overlap of uplink data signals and SRS in both time and frequency within the time and frequency resources is based on this capability.

[0192] In some examples, parameter indication component 1245 is capable of, configured to, or operable to support a unit for outputting indications of one or more parameters for transmitting SRS via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signal and SRS are obtained via time and frequency resources based on the one or more parameters.

[0193] In some examples, the one or more parameters include the period, or threshold SNR, or both, associated with SRS transmission via time and frequency resources allocated to the uplink shared channel. In some examples, the reference signal component 1235 is capable of, configured to, or operable to support elements for obtaining a second SRS with a third receive power higher than the second receive power via the second time and frequency resources.

[0194] In some examples, the time and frequency resources are based on a first period associated with SRS transmissions via time and frequency resources allocated to the uplink shared channel. In some examples, the second time and frequency resources are based on a second period associated with SRS transmissions via time and frequency resources not allocated to the uplink shared channel. In some examples, the second period is shorter than the first period.

[0195] In some examples, the channel estimation component 1255 is capable of, configured to, or operable to support elements for estimating attributes of the downlink channel between the UE and a network entity based on a second SRS. In some examples, the channel tracking component 1260 is capable of, configured to, or operable to support elements for tracking attributes of the downlink channel based on the SRS.

[0196] In some examples, the SNR threshold indication component 1250 is capable of, configured to, or operable to support units for outputting control signaling indicating the threshold SNR. In some examples, the threshold SNR is based on the MCS associated with time and frequency resources, or the rank associated with time and frequency resources, or both. In some examples, the threshold SNR is based on the SNR associated with the decoded uplink data signal.

[0197] Figure 13 A diagram of a system 1300 including device 1305 supporting SRS overlay on uplink data transmission, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 described herein, or a component including device 1005, device 1105, or network entity 105. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and may include communication over one or more wired interfaces, communication over one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and acquisition of communication, such as a communication manager 1320, transceiver 1310, antenna 1315, memory 1325, code 1330, and processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0198] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Alternatively or additionally, in some examples, transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be able to transmit or receive wireless transmissions (e.g., simultaneously). Transceiver 1310 may also include a modem to modulate signals, provide modulated signals for transmission (e.g., by one or more antennas 1315, by a wired transmitter), receive modulated signals (e.g., from one or more antennas 1315, from a wired receiver), and demodulate signals. In some implementations, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 and configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1311 and configured to support various transmit or output operations, or combinations thereof. In some implementations, transceiver 1310 may include or be configured to couple to one or more processors or one or more memory components operatively performing or supporting operations based on received or acquired information or signals, or generating information or other signals for transmission or other output, or any combination thereof. In some implementations, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., at least one processor 1335, or at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0199] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by one or more of the at least one processor 1335, cause the device 1305 to perform the various functions described herein. The code 1330 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 1330 may not be directly executable by a processor in the at least one processor 1335, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may also include a BIOS, etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0200] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into one or more of the at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more of at least one memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting overlay SRS over uplink data transmission). For example, device 1305 or components of device 1305 may include at least one processor 1335 configured to perform the various functions described herein and at least one memory 1325 coupled to at least one processor 1335, at least one processor 1335, and one or more of at least one memory 1325. At least one processor 1335 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 delegate functions (e.g., by executing code 1330) to perform the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (e.g., within one or more of at least one memory 1325). In some implementations, at least one processor 1335 may be a component of a processing system.

[0201] A processing system can generally refer to a system or a series of machines or components that receive input and process it to produce a set of outputs (which can be passed to other systems or components, such as device 1305). For example, the processing system of device 1305 can refer to a system that includes various other components or sub-components of device 1305 (such as at least one processor 1335, or transceiver 1310, or communication manager 1320, or other components or combinations of components of device 1305). The processing system of device 1305 can interface with other components of device 1305 and can process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of device 1305 may include a processing system and an interface for outputting information, or acquiring information, or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to output and acquire information. In some implementations, one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1305 to send information output from the chip or modem. Alternatively, in some implementations, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1305 to receive information or signal input and to transmit information to the processing system. Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0202] In some examples, bus 1340 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305 or communication performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one of the different components or divided between the different components).

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

[0204] Communication manager 1320 can support wireless communication at a network entity (device 1305) according to the examples disclosed herein. For example, communication manager 1320 can be configured or operable to support units for acquiring both uplink data signals and SRS at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signals and SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signals are acquired at a first receive power, and the SRS are acquired at a second receive power less than the first receive power, the first and second receive powers being based on a threshold SNR associated with the time and frequency resources. Communication manager 1320 can be configured or operable to support units for decoding the uplink data signals based on the first receive power satisfying the threshold SNR. Communication manager 1320 can be configured or operable to support units for processing SRS based on the decoded uplink data signals.

[0205] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support techniques for improving communication reliability, reducing latency, and utilizing communication resources more efficiently.

[0206] In some examples, the communication manager 1320 may be configured to use or otherwise cooperate with the transceiver 1310, one or more antennas 1315 (e.g., if applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is described as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more of at least one processor 1335, one or more of at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors of at least one processor 1335 to cause device 1305 to perform various aspects of the superimposed SRS on uplink data transmission as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0207] Figure 14 A flowchart illustrating a method 1400 for supporting SRS overlaid on uplink data transmission according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referred to... Figures 1 to 9 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Alternatively or separately, the UE can use dedicated hardware to perform aspects of the described function.

[0208] At 1405, the method may include identifying time and frequency resources allocated to the uplink shared channel. The operation of box 1405 can be performed according to examples disclosed herein. In some examples, it can be performed by, as referenced... Figure 8 The resource identification component 825 is described to perform various aspects of the operation of 1405.

[0209] At 1410, the method may include identifying a threshold SNR associated with time and frequency resources. The operations of box 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an SNR threshold component 830 as described with reference to 8.

[0210] At 1415, the method may include: transmitting both an uplink data signal and an SRS at least via time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power, and the SRS is transmitted using a second transmit power, the first and second transmit powers being based on a threshold SNR. The operation of block 1415 can be performed according to examples as disclosed herein. In some examples, aspects of operation 1415 may be provided by reference to... Figure 8 The signal combiner component 835 is described to perform this action.

[0211] Figure 15 A flowchart illustrating a method 1500 for supporting SRS overlaid on uplink data transmission according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a network entity or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 1 to 5 and Figures 10 to 13 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional units of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0212] At 1505, the method may include: acquiring both an uplink data signal and an SRS at least via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired at a first received power, and the SRS is acquired at a second received power less than the first received power, the first and second received powers being based on a threshold SNR associated with the time and frequency resources. Operation of block 1505 can be performed according to examples as disclosed herein. In some examples, aspects of operation 1505 may be derived from references... Figure 12 The combined signal component 1225 described is used to perform this action.

[0213] At 1510, the method may include decoding an uplink data signal based on a first received power satisfying a threshold SNR. The operation of block 1510 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from, as referenced... Figure 12 The data signal component 1230 described is used to perform this action.

[0214] In 1515, the method may include processing the SRS based on decoding the uplink data signal. The operation of block 1515 can be performed according to examples disclosed herein. In some examples, aspects of the operation of 1515 may be derived from, as referenced... Figure 12 The reference signal component 1235 described is used to perform this action.

[0215] The following provides an overview of some aspects of this disclosure.

[0216] Aspect 1: A method for wireless communication at a UE, comprising: identifying time and frequency resources allocated to an uplink shared channel; identifying a threshold SNR associated with the time and frequency resources; and transmitting both an uplink data signal and an SRS at least via the time and frequency resources, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power and the SRS is transmitted using a second transmit power, the first transmit power and the second transmit power being at least partially based on the threshold SNR.

[0217] Aspect 2: According to the method of aspect 1, transmitting both the uplink data signal and the SRS includes: transmitting a combined signal at least via the time and frequency resources, wherein the combined signal includes the uplink data signal and the SRS.

[0218] Aspect 3: According to the method of aspect 2, transmitting the combined signal includes: transmitting the uplink data signal via the time and frequency resources; and transmitting the SRS via the time and frequency resources and at least a second time and frequency resource also allocated to the uplink shared channel.

[0219] Aspect 4: The method according to any one of Aspects 1 to 3, wherein at least a portion of the SRS is superimposed on at least a portion of the uplink data signal within the time and frequency resources, or at least a portion of the uplink data signal is superimposed on at least a portion of the SRS within the time and frequency resources.

[0220] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: sending an uplink message indicating the UE's ability to transmit SRS via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the SRS in the time and frequency resources is at least partially based on the capability.

[0221] Aspect 6: The method according to any one of aspects 1 to 5 further includes: receiving an indication of one or more parameters for transmitting SRS via time and frequency resources allocated to the uplink shared channel, wherein transmitting the uplink data signal and the SRS via the time and frequency resources is based on the one or more parameters.

[0222] Aspect 7: The method according to aspect 6, wherein the one or more parameters include a period associated with the transmission of the SRS via time and frequency resources allocated to the uplink shared channel, or the threshold SNR, or both.

[0223] Aspect 8: The method according to any one of aspects 1 to 7 further includes: transmitting the second SRS using a third transmit power higher than the second transmit power via a second time and frequency resource.

[0224] Aspect 9: The method according to aspect 8, wherein the time and frequency resources are at least partially based on a first period associated with transmissions via SRS allocated to the uplink shared channel time and frequency resources, and the second time and frequency resources are at least partially based on a second period associated with transmissions via SRS not allocated to the uplink shared channel time and frequency resources.

[0225] Aspect 10: According to the method of aspect 9, wherein the second period is shorter than the first period.

[0226] Aspect 11: The method according to any one of Aspects 8 to 10, wherein the second SRS can be used at the network entity to estimate the attributes of the downlink channel between the UE and the network entity, and the SRS can be used at the network entity to track the attributes.

[0227] Aspect 12: The method according to any one of aspects 1 to 11, wherein identifying the threshold SNR comprises: receiving control signaling indicating the threshold SNR.

[0228] Aspect 13: The method according to aspect 12, wherein the control signaling includes DCI, MAC-CE or RRC messages.

[0229] Aspect 14: The method according to any one of Aspects 1 to 11, wherein identifying the threshold SNR comprises: identifying the threshold SNR from a set of threshold SNRs based at least in part on the time and frequency resources.

[0230] Aspect 15: The method according to any one of Aspects 1-14, wherein the threshold SNR is at least partially based on the MCS associated with the time and frequency resources, or the rank associated with the time and frequency resources, or both.

[0231] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the threshold SNR is at least partially based on the SNR associated with decoding the uplink data signal.

[0232] Aspect 17: A method for wireless communication at a network entity, comprising: acquiring both an uplink data signal and a signal-received rest (SRS) at least via time and frequency resources allocated to an uplink shared channel, wherein the uplink data signal and the SRS overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is acquired with a first receive power and the SRS is acquired with a second receive power less than the first receive power, the first receive power and the second receive power being at least partially based on a threshold SNR associated with the time and frequency resources; decoding the uplink data signal at least partially based on the first receive power satisfying the threshold SNR; and processing the SRS at least partially based on decoding the uplink data signal.

[0233] Aspect 18: According to the method of aspect 17, obtaining both the uplink data signal and the SRS comprises: obtaining a combined signal at least via the time and frequency resources, wherein the combined signal comprises the uplink data signal and the SRS.

[0234] Aspect 19: The method according to aspect 18 further includes: subtracting the decoded uplink data signal from the combined signal, wherein processing the SRS is at least in part based on the subtraction.

[0235] Aspect 20: The method according to any one of Aspects 18 to 19, wherein obtaining the combined signal comprises: obtaining the uplink data signal via the time and frequency resources; and obtaining the SRS via the time and frequency resources and at least a second time and frequency resource allocated to the uplink shared channel.

[0236] Aspect 21: According to the method of aspect 20, the processing of the SRS is at least in part based on the processing gain of the SRS across the time and frequency resources and the second time and frequency resources in time or frequency satisfying a threshold processing gain.

[0237] Aspect 22: According to the method of aspect 21, wherein the time and frequency resources occur during the first time slot, and the second time and frequency resources occur during the first time slot or the second time slot.

[0238] Aspect 23: The method according to any one of Aspects 20 to 22, wherein processing the SRS is based at least in part on the combined received power of the SRS across the time and frequency resources and the second time and frequency resources satisfying a second threshold SNR.

[0239] Aspect 24: The method according to any one of aspects 17 to 23, wherein at least a portion of the SRS is superimposed on at least a portion of the uplink data signal within the time and frequency resources, or at least a portion of the uplink data signal is superimposed on at least a portion of the SRS within the time and frequency resources.

[0240] Aspect 25: The method according to any one of Aspects 17 to 24 further includes: obtaining an uplink message indicating the ability of a UE to transmit SRS via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the SRS in both time and frequency within the time and frequency resources is at least partially based on the capability.

[0241] Aspect 26: The method according to any one of aspects 17 to 25 further includes: outputting an indication of one or more parameters for transmitting SRS via time and frequency resources allocated to the uplink shared channel, wherein obtaining the uplink data signal and the SRS via the time and frequency resources is based on the one or more parameters.

[0242] Aspect 27: The method according to aspect 26, wherein the one or more parameters include a period associated with the transmission of the SRS via time and frequency resources allocated to the uplink shared channel, or the threshold SNR, or both.

[0243] Aspect 28: The method according to any one of aspects 17 to 27 further includes: obtaining a second SRS having a third receive power higher than the second receive power via a second time and frequency resource.

[0244] Aspect 29: The method according to aspect 28, wherein the time and frequency resources are at least partially based on a first period associated with transmissions via SRS allocated to the uplink shared channel time and frequency resources, and the second time and frequency resources are at least partially based on a second period associated with transmissions via SRS not allocated to the uplink shared channel time and frequency resources.

[0245] Aspect 30: The method according to aspect 29, wherein the second period is shorter than the first period.

[0246] Aspect 31: The method according to any one of Aspects 28 to 30 further includes: estimating the attributes of a downlink channel between the UE and the network entity based at least in part on the second SRS; and tracking the attributes of the downlink channel based at least in part on the SRS.

[0247] Aspect 32: The method according to any one of aspects 17 to 31 further includes: outputting control signaling indicating the threshold SNR.

[0248] Aspect 33: The method according to any one of Aspects 17 to 32, wherein the threshold SNR is at least partially based on the MCS associated with the time and frequency resources, or the rank associated with the time and frequency resources, or both.

[0249] Aspect 34: The method according to any one of Aspects 17 to 33, wherein the threshold SNR is at least partially based on the SNR associated with decoding the uplink data signal.

[0250] Aspect 35: An apparatus for wireless communication at a UE, comprising: at least one processor; at least one memory coupled to said at least one processor; and instructions stored in said at least one memory and executable by said at least one processor to cause the apparatus to perform the method of any of aspects 1 to 16.

[0251] Aspect 36: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 16.

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

[0253] Aspect 38: An apparatus for wireless communication at a network entity, comprising: at least one processor; and a memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of aspects 17 to 34.

[0254] Aspect 39: An apparatus for wireless communication at a network entity, comprising: at least one unit for performing the method according to any one of aspects 17 to 34.

[0255] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication at a network entity, said code comprising instructions executable by a processor to perform a method according to any one of aspects 17 to 34.

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

[0257] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0258] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0259] The various illustrative boxes and components described herein can be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor can be performed by multiple processors capable of performing the described function or operation individually or collectively.

[0260] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the function can be stored on or transmitted on a computer-readable medium using one or more instructions or code. 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 can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the function can also be physically located in different locations, including portions that are briefed to enable implementation of the function in different physical locations.

[0261] Computer-readable media include non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired units of program code in the form of instructions or data structures, and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically copy data, while optical discs can optically copy data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0262] As used herein (including in the claims), the word "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could 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 "at least partially based on".

[0263] As used herein, including in claims, the article "a" preceding a noun is open-ended and is understood to refer to "at least one" or "one or more" of those nouns. Therefore, the terms "a," "at least one," "one or more," and "at least one of one or more" can be interchangeable. For example, if a claim recites a "component" performing one or more functions, each of the various functions can be performed by a single component or by any combination of multiple components. Thus, the term "component" having a characteristic or performing a function can refer to "at least one of one or more components" having a particular characteristic or performing a particular function. Subsequent use of the terms "the" or "the" to refer to a component introduced with the article "a" can refer to any one or all of the one or more components. For example, a component introduced with the article "a" can be understood to mean "one or more components," and subsequent reference to "the component" in a claim can be understood as equivalent to referring to "at least one of one or more components." Furthermore, as used herein, the phrase "set" should be interpreted to include the possibility of a set having one member. That is, the phrase "set" should be interpreted in the same manner as "one or more."

[0264] The term "determine" or "determining" encompasses a variety of actions, and therefore, "determining" can include calculating, computation, processing, derivation, investigation, searching (e.g., via searching in a table, database, or other data structure), and confirming. Furthermore, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Additionally, "determining" can include resolving, obtaining, selecting, choosing, creating, and other similar operations.

[0265] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any one of the similar components having the same first reference numeral, without regard to the second or other subsequent reference numerals.

[0266] This specification, illustrated in conjunction with the accompanying drawings, describes exemplary configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the examples.

[0267] The descriptions provided herein are intended to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: At least one processor; as well as At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to perform the following operations: Identify the time and frequency resources allocated to the uplink shared channel; Identify the threshold signal-to-noise ratio associated with the time and frequency resources; and Both an uplink data signal and a probe reference signal are transmitted at least via the time and frequency resources, wherein the uplink data signal and the probe reference signal overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power and the probe reference signal is transmitted using a second transmit power, the first transmit power and the second transmit power being at least partially based on the threshold signal-to-noise ratio.

2. The apparatus according to claim 1, wherein, In order to transmit both the uplink data signal and the probe reference signal, the instruction can be executed by the at least one processor to cause the device to perform the following operations: The combined signal is transmitted at least via the time and frequency resources, wherein the combined signal includes the uplink data signal and the probe reference signal.

3. The apparatus according to claim 2, wherein, In order to send the combined signal, the instruction can be executed by the at least one processor to cause the device to perform the following operations: The uplink data signal is transmitted via the time and frequency resources; as well as The probe reference signal is transmitted via the time and frequency resources and at least a second time and frequency resources that are also allocated to the uplink shared channel.

4. The apparatus according to claim 1, wherein: At least a portion of the detection reference signal is superimposed on at least a portion of the uplink data signal within the time and frequency resources, or At least a portion of the uplink data signal is superimposed on at least a portion of the probe reference signal within the time and frequency resources.

5. The apparatus according to claim 1, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: Sending an uplink message indicating the UE's ability to transmit a probe reference signal via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the probe reference signal in both time and frequency within the time and frequency resources is at least partially based on the capability.

6. The apparatus according to claim 1, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: The device receives an instruction for one or more parameters for the transmission of a probe reference signal via time and frequency resources allocated to the uplink shared channel, wherein the instruction is executable by the at least one processor to cause the device to: transmit the uplink data signal and the probe reference signal via the time and frequency resources according to the one or more parameters.

7. The apparatus according to claim 6, wherein, The one or more parameters include: the period associated with the transmission via a probe reference signal allocated time and frequency resources to the uplink shared channel, or the threshold signal-to-noise ratio, or both.

8. The apparatus according to claim 1, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: The second detection reference signal is transmitted using a third transmission power higher than the second transmission power, via the second time and frequency resources.

9. The apparatus according to claim 8, wherein: The time and frequency resources are based, at least in part, on a first period associated with the transmission of a probe reference signal via time and frequency resources allocated to the uplink shared channel, and The second time and frequency resources are based, at least in part, on a second cycle associated with the transmission of a probe reference signal via time and frequency resources not allocated to the uplink shared channel.

10. The apparatus according to claim 9, wherein, The second cycle is shorter than the first cycle.

11. The apparatus according to claim 8, wherein: The second probe reference signal can be used at the network entity to estimate the properties of the downlink channel between the UE and the network entity, and The detection reference signal can be used at the network entity to track the attribute.

12. The apparatus according to claim 1, wherein, In order to identify the threshold signal-to-noise ratio, the instruction can be executed by the at least one processor to cause the device to perform the following operations: Receive control signaling indicating the threshold signal-to-noise ratio.

13. The apparatus according to claim 1, wherein, In order to identify the threshold signal-to-noise ratio, the instruction can be executed by the at least one processor to cause the device to perform the following operations: The threshold signal-to-noise ratio is identified from a set of threshold signal-to-noise ratios, based at least in part on the time and frequency resources.

14. The apparatus according to claim 1, wherein, The threshold signal-to-noise ratio is based at least in part on the modulation and coding scheme associated with the time and frequency resources, or the rank associated with the time and frequency resources, or both.

15. The apparatus according to claim 1, wherein, The threshold signal-to-noise ratio is based, at least in part, on the signal-to-noise ratio associated with decoding the uplink data signal.

16. An apparatus for wireless communication at a network entity, comprising: At least one processor; as well as At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to perform the following operations: Both an uplink data signal and a probe reference signal are obtained at least via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signal and the probe reference signal overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is obtained at a first receive power and the probe reference signal is obtained at a second receive power less than the first receive power, the first receive power and the second receive power being at least partially based on a threshold signal-to-noise ratio associated with the time and frequency resources; The uplink data signal is decoded at least in part based on the first received power satisfying the threshold signal-to-noise ratio; and The probe reference signal is processed at least in part based on decoding the uplink data signal.

17. The apparatus according to claim 16, wherein, In order to obtain both the uplink data signal and the probe reference signal, the instruction can be executed by the at least one processor to cause the device to perform the following operations: A combined signal is obtained at least via the time and frequency resources, wherein the combined signal includes the uplink data signal and the probe reference signal.

18. The apparatus according to claim 17, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: The decoded uplink data signal is subtracted from the combined signal, wherein the instruction is executable by the at least one processor to cause the device to process the probe reference signal at least in part based on the subtraction.

19. The apparatus according to claim 17, wherein, In order to obtain the combined signal, the instruction can be executed by the at least one processor to cause the device to perform the following operations: The uplink data signal is obtained via the time and frequency resources; as well as The probe reference signal is obtained via the time and frequency resources and at least a second time and frequency resource allocated to the uplink shared channel.

20. The apparatus according to claim 19, wherein, The instructions can be executed by the at least one processor to cause the device to process the probe reference signal at least in part based on the fact that the processing gain of the probe reference signal across the time and frequency resources and the second time and frequency resources in time or frequency meets a threshold processing gain.

21. The apparatus according to claim 20, wherein, The time and frequency resources occur during the first time slot, and the second time and frequency resources occur during either the first or the second time slot.

22. The apparatus according to claim 19, wherein, The instructions can be executed by the at least one processor to cause the device to process the probe reference signal at least in part based on the combined received power of the probe reference signal across the time and frequency resources and the second time and frequency resources satisfying a second threshold signal-to-noise ratio.

23. The apparatus according to claim 16, wherein: At least a portion of the detection reference signal is superimposed on at least a portion of the uplink data signal within the time and frequency resources, or At least a portion of the uplink data signal is superimposed on at least a portion of the probe reference signal within the time and frequency resources.

24. The apparatus according to claim 16, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: An uplink message is obtained, the uplink message indicating the ability of a user equipment (UE) to transmit a probe reference signal via time and frequency resources allocated to the uplink shared channel, wherein the overlap of the uplink data signal and the probe reference signal in both time and frequency within the time and frequency resources is at least in part based on the capability.

25. The apparatus according to claim 16, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: The device outputs an indication of one or more parameters for the transmission of a probe reference signal via time and frequency resources allocated to the uplink shared channel, wherein the instruction is executable by the at least one processor to cause the device to: obtain the uplink data signal and the probe reference signal via the time and frequency resources according to the one or more parameters.

26. The apparatus according to claim 16, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: A second detection reference signal with a third receiving power higher than the second receiving power is obtained through the second time and frequency resources.

27. The apparatus according to claim 26, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: The properties of the downlink channel between the user equipment (UE) and the network entity are estimated, at least in part, based on the second probe reference signal; as well as The properties of the downlink channel are tracked at least in part based on the probe reference signal.

28. The apparatus according to claim 16, wherein, The instructions can also be executed by the at least one processor to cause the device to perform the following operations: Output control signaling indicating the threshold signal-to-noise ratio.

29. A method for wireless communication at a user equipment (UE), comprising: Identify the time and frequency resources allocated to the uplink shared channel; Identify the threshold signal-to-noise ratio associated with the time and frequency resources; as well as Both an uplink data signal and a probe reference signal are transmitted at least via the time and frequency resources, wherein the uplink data signal and the probe reference signal overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is transmitted using a first transmit power and the probe reference signal is transmitted using a second transmit power, the first transmit power and the second transmit power being at least partially based on the threshold signal-to-noise ratio.

30. A method for wireless communication at a network entity, comprising: Both an uplink data signal and a probe reference signal are obtained at least via time and frequency resources allocated to the uplink shared channel, wherein the uplink data signal and the probe reference signal overlap in both time and frequency within the time and frequency resources, and wherein the uplink data signal is obtained at a first receive power and the probe reference signal is obtained at a second receive power less than the first receive power, the first receive power and the second receive power being at least partially based on a threshold signal-to-noise ratio associated with the time and frequency resources; The uplink data signal is decoded at least in part based on the first received power satisfying the threshold signal-to-noise ratio; and The probe reference signal is processed at least in part based on decoding the uplink data signal.

Images