Uplink communication direction based on probe reference signal

By having the UE send an SRS set during beam scanning and receive instructions from macro network entities to select the best beam or resource, the unresolved issues of beam association and TCI status in the mTRP environment are resolved, improving uplink communication coverage and capacity.

CN123077237APending Publication Date: 2026-11-10QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090486.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-12
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In uplink-only transmit point (mTRP) environments, existing technologies have not yet resolved issues related to beam association and transmit configuration indicator (TCI) status, resulting in inefficient uplink communication.

Method used

The User Equipment (UE) transmits a Set of Sounding Reference Signals (SRS) during beam scanning and receives instructions from the macro network entity to select an optimized beam or resource for uplink communication to the mTRP. The macro network entity measures the SRS signal strength or quality, selects the best SRS, and sends the instructions to the UE.

Benefits of technology

By optimizing beam and resource selection, uplink communication coverage and capacity were improved, signaling resources were saved, and communication throughput was increased.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077237A_ABST
    Figure CN123077237A_ABST
Patent Text Reader

Abstract

Various aspects of this disclosure relate generally to wireless communication. In some aspects, a user equipment (UE) can transmit a set of sounding reference signals (SRS) in a beam scan. The UE can receive instructions for transmitting uplink communication toward a transmit-receive point (TRP). The UE can transmit uplink communication toward the TRP based at least in part on the instructions. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless communication, and more specifically to techniques, apparatuses, and methods for indicating uplink communication direction based on sounding reference signals. BACKGROUND

[0002] Wireless communications systems are widely deployed to provide various types of communication such as voice, text, messaging, video, data, and / or other services. These services can be supported by single-access and / or multi-access wireless communication systems that can employ one or more channel access techniques to enable communication with multiple users. Examples of such multiple-access wireless communication systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] The above multiple access RATs have been adopted in various telecommunication standards to provide a common protocol that enables different wireless communication devices to communicate on a municipal, national, regional, and / or global level. An example telecommunication standard is new radio (NR). NR, which can also be referred to as 5G, is a set of enhancements to the universal mobile telecommunications system (UMTS) mobile standard. It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDM modulation. NR supports a new waveform, new numerology, new coding, and new scheduling that can be more robust for deployment of mobile broadband Internet access. SUMMARY

[0004] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method can include transmitting a set of sounding reference signals (SRSs) in a beam sweep. The method can include receiving an indication to transmit an uplink communication toward a transmission reception point (TRP). The method can include transmitting the uplink communication toward the TRP based at least in part on the indication.

[0005] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method can include receiving, from a TRP, an indication of a selected SRS. The method can include transmitting, to a UE, an indication to transmit an uplink communication to a selected TRP based at least in part on the selected SRS.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method can include receiving, from a UE, one or more SRSs. The method can include transmitting an indication of a SRS selected based at least in part on a signal strength or quality.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus can include one or more memories and one or more processors coupled to the one or more memories. The one or more processors can be individually or collectively configured to transmit a set of SRSs in a beam sweep. The one or more processors can be individually or collectively configured to receive an indication to transmit an uplink communication toward a TRP. The one or more processors can be individually or collectively configured to transmit the uplink communication toward the TRP as indicated based at least in part on the indication.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus can include one or more memories and one or more processors coupled to the one or more memories. The one or more processors can be individually or collectively configured to receive, from a TRP, an indication of a selected SRS. The one or more processors can be individually or collectively configured to transmit, to a UE, an indication to transmit an uplink communication to a selected TRP based at least in part on the selected SRS.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus can include one or more memories and one or more processors coupled to the one or more memories. The one or more processors can be individually or collectively configured to receive, from a UE, one or more SRSs. The one or more processors can be individually or collectively configured to transmit an indication of a SRS selected based at least in part on a signal strength or quality.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to transmit a set of SRSs in a beam sweep. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive an indication to transmit an uplink communication toward a TRP. The set of instructions, when executed by one or more processors of the UE, can cause the UE to transmit the uplink communication toward the TRP as indicated based at least in part on the indication.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to receive, from a TRP, an indication of a selected SRS. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to transmit, to a UE, an indication to transmit an uplink communication to a selected TRP based at least in part on the selected SRS.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to receive, from a UE, one or more SRSs. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to transmit an indication of a SRS selected based at least in part on a signal strength or quality.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for transmitting a set of SRSs in a beam sweep. The apparatus can include means for receiving an indication to transmit an uplink communication toward a TRP. The apparatus can include means for transmitting the uplink communication toward the TRP based at least in part on the indication.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving, from a TRP, an indication of a selected SRS. The apparatus can include means for transmitting, to another apparatus, an indication to transmit an uplink communication to a selected TRP based at least in part on the selected SRS.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving, from a UE, one or more SRSs. The apparatus can include means for transmitting an indication of a SRS selected based at least in part on a signal strength or quality.

[0016] Aspects of the disclosure can be implemented in whole or in part by a method, an apparatus, a system, a computer program product, a non-transitory computer-readable medium, a user equipment, a base station, a network node, a network entity, a wireless communication device, and / or a processing system as substantially described in connection with the drawings, as well as a tangible machine-readable medium comprising instructions to carry out the method, and the processor-readable instructions can be stored in a tangible, non-transitory computer-readable medium such as RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD), or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible machine-readable medium which can be used to store the desired instructions. The term “non-transitory” simply means a computer-readable medium that does not include a transitory signal. The term “machine-readable medium” includes any medium that can be accessed by a machine; e.g., by a computer. The term “storage” includes one or both of memory and disk.

[0017] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages are described below. The disclosed aspects can serve as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects are not to be considered as a departure from the spirit and scope of the appended claims. The characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0018] The accompanying drawings illustrate aspects of the present disclosure, but do not limit its scope, as other aspects can be implemented. Each drawing is provided for purposes of illustration only and not as a definition of the limits of the disclosure. The same or similar reference numbers in different drawings can identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless communication network, in accordance with the present disclosure.

[0020] Figure 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0021] Figure 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of an uplink dense deployment, in accordance with the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a sounding reference signal (SRS) resource set, in accordance with the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of an SRS-based association for indicating a direction for uplink communication, in accordance with the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of an SRS indicating for uplink communication, in accordance with the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.

[0027] Figure 9 FIG. 1 is a diagram illustrating an example process performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure.

[0028] Figure 10 FIG. 1 is a diagram illustrating an example process performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure.

[0029] Figure 11 FIG. 1 is a diagram illustrating an example process performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure.

[0030] Figure 12 FIG. 1 is a diagram illustrating an example process performed, for example, at a network entity or an apparatus of a network entity, in accordance with the present disclosure. DETAILED DESCRIPTION

[0031] Various aspects of the disclosure are described with reference to the drawings. However, aspects of the disclosure can be embodied in many different forms and should not be construed as limited to the aspects set forth in the drawings or described or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover devices, or methods that are implemented using other structure(s) in addition to or other than the structure(s) set forth herein. Any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim.

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

[0033] To improve coverage and capacity of uplink (UL) transmissions, a UL dense deployment can be used. The UL dense deployment can include a macro network entity providing macro coverage and a plurality of UL reception (Rx) points, such as a plurality of transmission reception points or a plurality of transmission and reception points (mTRP), providing UL micro coverage. Although the acronym “mTRP” refers to multiple TRPs, “mTRP” can be used in the singular and, when used in the singular, can refer to a single TRP of the multiple TRPs within the context of an mTRP environment, providing micro coverage in coordination with the macro network entity. The mTRP providing micro coverage can be considered a “micro” mTRP. The mTRP can be a UL-only node in which only UL signals and channels are received for reception by a network entity. A user equipment (UE) can transmit signals or messages to the UL-only node. Downlink (DL) signals and channels are transmitted from a different node, such as a macro node, a central node or central unit (CU), a serving cell, a serving base station. The UL Rx points are connected to the network entity via a fronthaul or backhaul.

[0034] The beams can be associated with UL. For UL-only mTRPs, there is no DL reference for UL beam association, and thus beam association or transmission configuration indicator (TCI) state cannot be based on a DL reference from the UL-only mTRP. Beam association and TCI state have not been resolved for UL-only mTRPs.

[0035] Various aspects generally relate to uplink communications. Some aspects more specifically relate to a UE transmitting, e.g., in a beam sweep, a sounding reference signal (SRS) burst that is received by one or more mTRPs. The mTRPs can measure the SRS and report to a macro network entity an SRS that can have the strongest signal strength or quality of the SRSs received from the UE by the mTRPs. The macro network entity can select the SRS and determine a beam or resource (e.g., corresponding to the selected SRS) that the UE is to use for uplink communications to the mTRP. The macro network entity can transmit an indication of the SRS to the UE based at least in part on the selected SRS. The UE can determine in which direction or toward which mTRP to transmit the uplink communications based at least in part on the indication (the indicated SRS). The UE can associate the SRS with a beam and / or resource and use the beam and / or resource to transmit the uplink communications to the mTRP (e.g., UL-only mTRP).

[0036] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. By using SRS beam sweeping and an indication of SRS association, a UE can transmit uplink communications to an mTRP using a beam and / or resource that is better than other beams or resources, which improves uplink communications without receiving downlink communications from the mTRP. As a result, signaling resources are conserved and throughput is improved.

[0037] Multiple access radio access technologies (RATs) have been adopted in various telecommunications standards to provide public protocols that enable wireless communication devices to communicate on municipal, national, regional, or global levels. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new capability requirements for 5G NR in future releases. 5G NR support a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0038] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements can be employed or implemented in 5G NR or future RATs, such as 6G, to further push the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new band extensions, licensed and unlicensed spectrum access, overlapping spectrum usage, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architecture and network topology extensions, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or environmental IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multi-subscriber implementation, high-precision positioning, radio frequency (RF) sensing, and / or artificial intelligence or machine learning (AI / ML), among others. Such technological improvements can support use cases such as wireless backhaul, wireless data center, extended reality (XR) and metaverse applications, meta-services to support vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, posture monitoring, human brain interface, digital twin applications, asset management, and general coverage applications using non-terrestrial and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0039] Figure 1is a diagram illustrating an example of a wireless communication network 100, in accordance with the present disclosure. The wireless communication network 100 can be a 5G (or NR) network or a 6G network, or include elements of both a 5G (or NR) network or a 6G network, among others. The wireless communication network 100 can include a number of network nodes 110, illustrated as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. The network nodes 110 can support communication with a number of UEs 120, illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e.

[0040] The network nodes 110 and UEs 120 of the wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, the devices of the wireless communication network 100 can communicate using one or more operating bands. In some aspects, multiple wireless networks 100 can be deployed within a given geographic area. Each wireless communication network 100 can support a particular RAT (which can also be referred to as an air interface) and can operate on one or more carrier frequencies within one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G / NR RAT, and / or a 6G RAT, among others. In some examples, when multiple RATs are deployed in a given geographic area, each RAT can operate on different carrier frequencies and / or frequencies ranges in order to avoid interference between the RATs.

[0041] Various operating bands have been defined as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles FR1 is commonly (and interchangeably) referred to as a “Sub-6 GHz” band. Similarly, FR2 is commonly (and interchangeably) referred to as a “millimeter wave” band in some documents and articles, but it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which can include frequencies in FR3. The bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and as such, features of FR1 or FR2 can be effectively extended into the mid-band frequencies. Thus, “Sub-6 GHz” (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in the mid-band frequencies. Similarly, the term “millimeter wave” (if used herein) can broadly refer to frequencies included in the mid-band frequencies, within FR2, FR4, FR4-a, or FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operations, 6G operations, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 fall within the EHF band. In some examples, wireless communications network 100 can implement dynamic spectrum sharing (DSS) where multiple RATs (e.g., 4G / LTE and 5G / NR) are utilized with dynamic allocation of the bandwidth (e.g., based on user demand). It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein can be applicable to those modified frequency ranges.

[0042] Network node 110 can include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communications network 100. Network node 110 can be, can include, or can also be referred to as a NR network node, a 5G network node, a 6G network node, a NodeB, an eNB, a gNB, an access point (AP), a TRP, a mobility element, a core, a network entity, a network element, network equipment, and / or another type of device, component, or system included in a Radio Access Network (RAN).

[0043] The network nodes 110 can be implemented as a single physical node (e.g., a single physical structure) or can be implemented as two or more physical nodes (e.g., two or more different physical structures). For example, the network nodes 110 can be a device or system that implements part of a radio protocol stack, a device or system that implements a complete radio protocol stack such as a complete gNB protocol stack, or a collection of devices or systems that collectively implement a complete radio protocol stack. For example, and as illustrated, the network nodes 110 can be disaggregated network nodes (sometimes referred to as disaggregated base stations), meaning that the network nodes 110 can implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or different geographic locations. For example, the disaggregated network nodes can have a disaggregated architecture. In some deployments, the disaggregated network nodes 110 can be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) such as a network configuration compliant with the O-RAN Alliance, or in a virtualized radio access network (vRAN) also known as a cloud radio access network (C-RAN) to facilitate scaling by separating base station functionality into multiple units that can be deployed separately.

[0044] Alternatively, and also as illustrated, the network nodes 110 can be disaggregated network nodes (sometimes referred to as disaggregated base stations), meaning that the network nodes 110 can implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or different geographic locations. For example, the disaggregated network nodes can have a disaggregated architecture. In some deployments, the disaggregated network nodes 110 can be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) such as a network configuration compliant with the O-RAN Alliance, or in a virtualized radio access network (vRAN) also known as a cloud radio access network (C-RAN) to facilitate scaling by separating base station functionality into multiple units that can be deployed separately.

[0045] The network node 110 of the wireless communication network 100 can include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). The CU can host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and / or service data adaptation protocol (SDAP) functions, among other examples. The DU can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part according to a function split, such as one defined by 3GPP. In some examples, the DU can also host one or more lower PHY layer functions, such as fast Fourier transform (FFT), inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, among other examples. The RU can host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a function split, such as a lower layer function split. In such an architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UEs 120.

[0046] In some aspects, the network node 110 can include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally, or alternatively, the network node 110 can include one or more near-real-time (near-RT) RAN intelligent controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, the CUs, DUs, and / or RUs can be implemented as virtual units, such as a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU), among other examples. The virtual units can be implemented as virtual network functions, such as in association with a cloud deployment.

[0047] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 may support one or more (e.g., three) cells. In some examples, network node 110 may provide communication coverage for macro cells, micro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., with a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A micro cell or pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0048] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0049] In some examples, the network node 110 can be, can include, or can operate as a RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which can be referred to as a “Uu” link). The radio access link can include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from the network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to the network node 110. The downlink channel can include one or more control channels and one or more data channels. The downlink control channel can be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from the network node 110 to the UE 120. The downlink data channel can be used to transmit downlink data (e.g., user data associated with the UE 120) from the network node 110 to the UE 120. The downlink control channel can include one or more physical downlink control channels (PDCCHs), and the downlink data channel can include one or more physical downlink shared channels (PDSCHs). The uplink channel can similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) (e.g., reference signals and / or feedback corresponding to one or more downlink transmissions) from the UE 120 to the network node 110. The uplink data channel can be used to transmit uplink data (e.g., user data associated with the UE 120) from the UE 120 to the network node 110. The uplink control channel can include one or more physical uplink control channels (PUCCHs), and the uplink data channel can include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink can each include a set of resources on which the network node 110 and the UE 120 can communicate.

[0050] Downlink resources and uplink resources can include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (particular transmission directions and / or beam parameters). The frequency-domain resources of some frequency bands can be subdivided into bandwidth parts (BWPs). A BWP can be a contiguous block of frequency-domain resources (e.g., a contiguous block of resource blocks) allocated for one or more UEs 120. A UE 120 can be configured with both uplink BWPs and downlink BWPs (where the uplink and downlink BWPs can be the same BWP or different BWPs). BWPs can be dynamically configured and / or reconfigured (e.g., by a network node 110 sending a DCI configuration to one or more UEs 120), meaning that the BWP can be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communications network 100 and / or based on the specific requirements of one or more UEs 120. This enables more efficient use of available frequency-domain resources in the wireless communications network 100, as fewer frequency-domain resources can be allocated to the BWP for a UE 120 (which can reduce the number of frequency-domain resources that the UE 120 needs to monitor), thereby allowing more frequency-domain resources to be spread across multiple UEs 120. Thus, BWPs can also aid implementation of lower-capability UEs 120 by facilitating configuration of smaller bandwidths for communications by such UEs 120.

[0051] As described above, in some aspects, the wireless communication network 100 can be, can include, or can be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. The anchor network node 110 can also be referred to as an IAB donor (or “IAB-donor”). The anchor network node 110 can be connected to the core network via a wireline backhaul link. For example, an Ng interface of the anchor network node 110 can terminate at the core network. Additionally or alternatively, the anchor network node 110 can be connected to one or more devices of the core network that provide core access and mobility management functions (AMF). An IAB network also typically includes a plurality of non-anchor network nodes 110, which can also be referred to as relay network nodes or simply IAB nodes (or “IAB-nodes”). Each non-anchor network node 110 can communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or can communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication, such as time resources, frequency resources, and / or space resources, can be shared between access links and backhaul links.

[0052] In some examples, any network node 110 that relays communications can be referred to as a relay network node, a relay station, or simply a relay. A relay can receive a transmission of a communication from an upstream station (e.g., another network node 110 or a UE 120) and transmit the communication to a downstream station (e.g., a UE 120 or another network node 110). In this case, the wireless communication network 100 can include or be referred to as a “multi-hop network.” In a multi-hop network, a network node 110 can be referred to as a “hop” between an upstream station and a downstream station. For example, a network node 110 can be a first hop from a base station to a UE, a second hop from the UE to the base station, and / or the like. Figure 1 In the illustrated example, the network node 110d (e.g., a relay network node) can communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 can be, or operate as, a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications can be referred to as a UE-relay or a relay-UE, among other examples.

[0053] The UEs 120 can be dispersed throughout the wireless communication network 100, and each UE 120 can be stationary or mobile. A UE 120 can be, can include, or can be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 can be, can include, or can be included in a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, and / or smart jewelry such as a smart ring or a smart bracelet), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a global navigation satellite system (GNSS) device (such as a GPS device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that is capable of communicating via a wireless medium, or can be coupled to them.

[0054] The UEs 120 and / or the network nodes 110 can include one or more chips, systems on chip (SoCs), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) such as field-programmable gate arrays (FPGAs), or other discrete gate or transistor logic components or circuitry (all of which are herein generically referred to as “processors,” individually or collectively). One or more of these processors can be capable of, individually or collectively, being configured to or configured as performing various functions or operations described herein. A group of processors that are collectively configurable to or configured to perform a set of functions can include a first processor that is configurable to or configured to perform a first function in the set and a second processor that is configurable to or configured to perform a second function in the set, or can include the group of processors that are all configurable to or configured to perform the set of functions.

[0055] The processing system can also include memory circuitry in the form of one or more memory devices, blocks of memory, memory elements, or other discrete gates or transistor logic or circuitry, each of which can include a tangible storage medium such as random access memory (RAM) or read-only memory (ROM) or a combination thereof (all of which are generally individually referred to herein as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories can be coupled with (e.g., operatively coupled with, communicatively coupled with, electronically coupled with, or electrically coupled with) one or more of the processors, and can store processor-executable code such as software, which alone or in combination can configure one or more of the processors to perform various functions or operations described herein when executed by one or more of the processors. Additionally or alternatively, in some examples, one or more of the processors can be pre-configured to perform various functions or operations described herein without the need for configuration by software. The processing system can also include or be coupled with one or more modems (such as a Wi-Fi (e.g., Institute of Electrical and Electronics Engineers (IEEE)-compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G-compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system can also include or be coupled with multiple radios (collectively, “radio(s)”), multiple RF chains, or multiple transceivers, each of which can in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains, or transceivers. The UE 120 can include or be included in a housing that houses components associated with the UE 120, including the processing system.

[0056] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, all of which can be referred to as “MTC UEs” for brevity. MTC UEs can be IoT UEs, which can comprise, be included in, or be coupled with, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, just to name a few. Some UEs 120 can be considered Internet-of-Things (IoT) devices and / or can be implemented as NB-IoT (narrowband IoT) devices. IoT UEs or NB-IoT devices can be industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or light fixtures, among other examples. Some UEs 120 can be considered customer premises equipment, which can include a telecommunications device attached to a customer’s premises (such as a home or office) to enable access to a service provider’s network, such as included or in communication with wireless communication network 100.

[0057] Some UEs 120 can be categorized according to different classes associated with different complexities and / or different capabilities. A first class of UEs 120 can facilitate massive IoT in wireless communication network 100 and can provide low complexity and / or cost relative to UEs 120 in a second class. UEs 120 in the second class can include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and / or premium UEs capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning, among other examples, in wireless communication network 100. A third class of UEs 120 can have intermediate tier complexity and / or capabilities (e.g., capabilities between the first class of UEs 120 and the second class of UEs 120). The third class of UEs 120 can be referred to as reduced capability UEs (“RedCap UEs”), intermediate tier UEs, NR light UEs, and / or NR slim UEs, among other examples. RedCap UEs can bridge the gap between capabilities and complexity of NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range, among other examples. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among other examples.

[0058] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using sidelink communication (e.g., without communicating through the network node 110 as an intermediary). For example, UE 120a can transmit data, control information, or other signaling directly to UE 120e as a sidelink communication. This is in contrast to, for example, UE 120a first transmitting the data to the network node 110 in a UL communication, and then the network node transmitting the data to UE 120e in a DL communication. In various examples, the UEs 120 can transmit and receive sidelink communications using a peer-to-peer (P2P) communication protocol, a device-to-device (D2D) communication protocol, a vehicle-to-everything (V2X) communication protocol (which can include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and / or a vehicle-to-pedestrian (V2P) protocol), and / or a mesh network communication protocol. In some deployments and configurations, the network node 110 can schedule and / or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, the UEs 120 (rather than the network node 110) can perform or cooperate or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communications.

[0059] In various examples, in addition to half-duplex operation, some of the network nodes 110 and UEs 120 of the wireless communication network 100 can be configured for full-duplex operation. Network nodes 110 or UEs 120 operating in half-duplex mode can perform only one of transmission or reception during a particular time resource, such as during a particular time slot, symbol, or other time period. Half-duplex operation can involve time division duplex (TDD), where DL transmissions by a network node 110 and UL transmissions by a UE 120 do not occur in the same time resource (i.e., transmissions do not overlap in time). In contrast, network nodes 110 or UEs 120 operating in full-duplex mode can concurrently (e.g., in the same time resource) transmit and receive communications. By operating in full-duplex mode, network nodes 110 and / or UEs 120 can generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation can involve frequency division duplex (FDD), in which DL transmissions by a network node 110 are performed in a first frequency band or on a first component carrier, and UL transmissions by a UE 120 are performed in a second frequency band or on a second component carrier, which is different from the first frequency band or first component carrier, respectively. In some examples, full-duplex operation can be enabled for UEs 120 but not for network nodes 110. For example, a UE 120 can simultaneously transmit UL transmissions to a first network node 110 and receive DL transmissions from a second network node 110 in the same time resource. In some other examples, full-duplex operation can be enabled for network nodes 110 but not for UEs 120. For example, a network node 110 can simultaneously transmit DL transmissions to a first UE 120 and receive UL transmissions from a second UE 120 in the same time resource. In some other examples, full-duplex operation can be enabled

[0060] In some examples, UEs 120 and network nodes 110 can perform MIMO communications. “MIMO” generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) over the same time and frequency resource. MIMO technology generally exploits multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmissions to multiple receivers, which is referred to as multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques, such as mTRP operation (including redundant transmissions or receptions over multiple TRPs), reciprocity in the time or frequency domain, single frequency network (SFN) transmissions, or non-coherent joint transmission (NCJT).

[0061] In some aspects, a UE (e.g., UE 120) can include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 can transmit a set of SRSs in a beam sweep. The communications manager 140 can receive, for example, from a network node 110a, an indication to transmit an uplink communication toward a transmission reception point (TRP) (e.g., network node 110b or 110c). The communications manager 140 can transmit the uplink communication toward the TRP based at least in part on the indication. Additionally, or alternatively, the communications manager 140 can perform one or more other operations described herein.

[0062] In some aspects, a network entity (e.g., network node 110a) can include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 can receive, from a TRP (e.g., network node 110b or 110c), an indication of a selected SRS. The communications manager 150 can transmit, to a UE, an indication to transmit an uplink communication to a selected TRP based at least in part on the selected SRS. Additionally, or alternatively, the communications manager 150 can perform one or more other operations described herein.

[0063] In some aspects, a network entity (e.g., network node 110b or 110c) can include a communications manager 160. As described in more detail elsewhere herein, the communications manager 160 can receive, from a UE, one or more SRSs. The communications manager 160 can transmit an indication of a SRS selected based at least in part on a signal strength or quality. Additionally, or alternatively, the communications manager 160 can perform one or more other operations described herein.

[0064] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to Figure 1 the examples described with respect to

[0065] Figure 2 is an example diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.

[0066] As Figure 2As shown, network node 110 can include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t > 1), a set of antennas 234 (shown as 234a through 234v, where v > 1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communications manager 150 or 160, among other examples. In some configurations, one or a combination of the antennas 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 214, and / or TX MIMO processor 216 can be included in a transceiver of the network node 110. The transceiver can be under the control of, and used by, one or more processors, such as the controller / processor 240, and in some aspects, in conjunction with processor-readable code stored in the memory 242, to implement aspects of the methods, processes and / or operations described herein. In some aspects, the network node 110 can include one or more interfaces, communication components, and / or other components that facilitate communication with UE 120 or another network node.

[0067] The term “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, a reference to “the processor,” “the controller / processor,” or the like, in singular form, can encompass one or more individual processors or controllers, and / or portions of one or more individual processors or controllers, collectively. The term “processor” can refer to integrated circuits designed for use in digital Figure 2 The term “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, a reference to “the processor,” “the controller / processor,” or the like, in singular form, can encompass one or more individual processors or controllers, and / or portions of one or more individual processors or controllers, collectively. The term “processor” can refer to integrated circuits designed for use in digital Figure 2 The term “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, a reference to “the processor,” “the controller / processor,” or the like, in singular form, can encompass one or more individual processors or controllers, and / or portions of one or more individual processors or controllers, collectively. The term “processor” can refer to integrated circuits designed for use in digital

[0068] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors of one or more processors can perform first operations described as being performed by the one or more processors, and a second set of one or more processors of the one or more processors can perform second operations described as being performed by the one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. References to “one or more memories” should be understood as references to any one or more memories of a corresponding device, such as the memory described in connection with Figure 2 For example, operations described as being performed by one or more memories can be performed by a same subset of the one or more memories or by different subsets of the one or more memories.

[0069] For downlink communication from a network node 110 to a UE 120, a transmit processor 214 can receive data (‘downlink data”) from a data source 212, such as a data pipe or a data queue, intended for the UE 120 (or a set of UEs including the UE 120). In some examples, the transmit processor 214 can select one or more MCSs for the UE 120 as a function of one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 can process data (e.g., including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCSs selected for the UE 120, generating data symbols. The transmit processor 214 can process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and / or control symbols. The transmit processor 214 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and / or synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)).

[0070] A TX MIMO processor 216 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide output symbol streams to the TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0071] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0072] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0073] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0074] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0075] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0076] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0077] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0078] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0079] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output symbol streams (e.g., U A set of output symbol streams is provided to a set of modems 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0080] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmissions made directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0081] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0082] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0083] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0084] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0085] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0086] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360) (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0087] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0088] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0089] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0090] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0091] In some respects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and may be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns of performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0092] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0093] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with SRS-based uplink communication direction indication, or perform one or more operations associated with SRS-based uplink communication direction indication, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with SRS-based uplink communication direction indication, or perform one or more operations associated with SRS-based uplink communication direction indication, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 8 The process 800 Figure 9 The process 900 Figure 10The operation of process 1000 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8 The process 800 Figure 9 The process 900 Figure 10 The process 1000 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0094] In some aspects, the UE (e.g., UE 120) includes: components for transmitting an SRS set in a beam scan (e.g., using a controller / processor 280, a transmit processor 264, a TX MIMO processor 266, a modem 254, an antenna 252, a memory 282, etc.); components for receiving an indication for transmitting uplink communication toward the TRP (e.g., using an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a controller / processor 280, a memory 282, etc.); and / or components for transmitting uplink communication toward the TRP at least in part based on the indication (e.g., using a controller / processor 280, a transmit processor 264, a TX MIMO processor 266, a modem 254, an antenna 252, a memory 282, etc.). Components that enable the UE to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0095] In some aspects, a network entity (e.g., network node 110) includes: components for (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) receiving an indication for a selected SRS from a TRP; and / or components for (e.g., using controller / processor 240, transmit processor 214, TXMIMO processor 216, modem 232, antenna 234, memory 242, etc.) transmitting to the UE an indication for sending uplink communication to a selected TRP, at least partially based on the selected SRS. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150 or 160, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0096] In some aspects, a network entity (e.g., network node 110) includes: components for (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) receiving one or more SRSs from a UE; and / or components for (e.g., using controller / processor 240, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, memory 242, etc.) transmitting an indication of an SRS selected at least in part based on signal strength or quality. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150 or 160, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0097] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0098] Figure 4 This is an illustration of Example 400 of a dense UL deployment according to this disclosure.

[0099] To improve UL transmission coverage and capacity, a dense UL deployment can be used. As shown in Example 400, a dense UL deployment may include a network entity 405 providing macro coverage and multiple UL receiver (Rx) points providing micro coverage, these UL receiver (Rx) points being provided by mTRP. k 410 and mTRPl As shown in 415, the mTRP can be a UL-only node, where only UL signals and channels are received for network entity 405 to receive. UE 420 (or UE 425) can send messages to the UL-only node. DL signals and channels are sent from different nodes such as network entity 405 (e.g., macro nodes, central nodes, serving cells, serving base stations, or CUs). The UL Rx point is connected to network entity 405 via backhaul.

[0100] Dense UL deployment reduces UL path loss, which is helpful when UL coverage is a bottleneck. Dense UL deployment also helps reduce deployment cost and complexity because UL Rx points do not send any DL signals. UL Rx points are expected to only receive UL signals or messages and, with or without some processing, send the UL signals or messages to macro nodes.

[0101] Example 400 illustrates that the beam associated with UL can be based on a DL synchronization signal block (SSB) selected by UE 420, and therefore the TCI state is rooted in the selected SSB (e.g., TCI 1). For UL-only mTRP, there is no DL reference for UL beam association (i.e., no SSB or CSI-RS / Tracking Reference Signal (TRS) is transmitted), and therefore beam association or TCI state (e.g., TCI 2) cannot be based on a DL reference, such as the selected SSB. Beam association and TCI state have not yet been addressed for UL-only mTRP.

[0102] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0103] Figure 5 This is a diagram illustrating example 500 of the SRS resource set according to this disclosure.

[0104] Dense UL deployments may include network entities receiving SRS from UEs (e.g., UE 425). UE 425 may be configured to have one or more SRS resource sets to allocate resources for SRS transmissions performed by UE 425. For example, the configuration for the SRS resource set may be indicated in a Radio Resource Control (RRC) message (e.g., an RRC configuration message or an RRC reconfiguration message). As shown by reference numeral 505, the SRS resource set may include one or more resources (e.g., shown as SRS resources), which may include time resources and / or frequency resources (e.g., time slots, symbols, resource blocks, and / or periodicity of time resources).

[0105] As shown by reference numeral 510 in the accompanying drawings, an SRS resource may include one or more antenna ports on which SRS is to be transmitted (e.g., in a time-frequency resource). Thus, the configuration for an SRS resource set may indicate one or more time-frequency resources on which SRS is to be transmitted, and may indicate one or more antenna ports on which SRS is to be transmitted in those time-frequency resources. In some aspects, the configuration for an SRS resource set may indicate the use case for the SRS resource set (e.g., in...). SRS-SetUse (In information elements). For example, an SRS resource set may have use cases for antenna switching, codebooks, non-codebooks, or beam management.

[0106] The antenna switching SRS resource set can be used to indicate the downlink CSI with reciprocity between the uplink and downlink channels. For example, when there is reciprocity between the uplink and downlink channels, network entity 405 can use the antenna switching SRS (e.g., an SRS transmitted using resources in the antenna switching SRS resource set) to obtain the downlink CSI (e.g., to determine the downlink pre-decoder to be used for communication with UE 425).

[0107] When network entity 405 indicates an uplink pre-decoder to UE 425, the codebook SRS resource set can be used to indicate the uplink CSI. For example, when network entity 405 is configured (e.g., using a pre-decoder codebook) to indicate an uplink pre-decoder to UE 425, network entity 405 can use the codebook SRS (e.g., an SRS transmitted using resources in the codebook SRS resource set) to obtain the uplink CSI (e.g., to determine the uplink pre-decoder to be indicated to UE 425 and used by UE 425 to communicate with network entity 405). In some aspects, at least with respect to the codebook SRS, virtual ports with maximum transmit power (e.g., a combination of two or more antenna ports) can be supported.

[0108] When UE 425 selects an uplink pre-decoder (e.g., instead of the uplink pre-decoder indicated by network entity 405 to be used by UE 425), a non-codebook SRS resource set can be used to indicate the uplink CSI. For example, when UE 425 is configured to select an uplink pre-decoder, network entity 405 can use non-codebook SRS (e.g., SRS transmitted using resources in the non-codebook SRS resource set) to obtain the uplink CSI. In this case, the pre-decoder selected by UE 425 (e.g., the pre-decoder can be indicated to network entity 405) can be used to pre-decode the non-codebook SRS. Beam management SRS resource sets can be used to indicate the CSI for millimeter-wave communications.

[0109] SRS resources can be configured as periodic, semi-persistent (sometimes referred to as semi-persistent scheduling (SPS)), or aperiodic. Periodic SRS resources can be configured via indicating the periodicity of the SRS resource (e.g., slot-level periodicity, where the SRS resource is periodically...). Y Configuration messages for periodic SRS resources (occurring in individual time slots) and time slot offsets are used for configuration. In some cases, periodic SRS resources may always be active and may not be dynamically activated or deactivated. Semi-persistent SRS resources may also be configured via configuration messages indicating the periodicity and time slot offset used for the semi-persistent SRS resource, and may be dynamically activated and deactivated (e.g., using DCI or MAC-CE). Non-periodic SRS resources may be dynamically triggered, such as via DCI (e.g., UE-specific DCI or group common DCI) or MAC-CE.

[0110] In some respects, UE 425 can be configured to have a mapping between SRS ports (e.g., antenna ports) and corresponding SRS resources. UE 425 can use the SRS port indicated in the configuration to transmit SRS on a specific SRS resource. In some respects, SRS resources can span across time slots. N Adjacent symbols (e.g., where) N (equal to 1, 2, or 4). UE 425 can be configured to have X SRS ports (e.g., where X ≤4). In some respects, X Each of the SRS ports can be mapped to a corresponding symbol of the SRS resource and used to send SRS in that symbol.

[0111] like Figure 5 As shown, in some aspects, different SRS resource sets (e.g., with different use cases) indicated to UE 425 may overlap (e.g., in time and / or frequency, such as in the same time slot). For example, as shown by reference numeral 515, a first SRS resource set (e.g., shown as SRS resource set 1) is shown as having an antenna switching use case. As shown, this example antenna switching SRS resource set includes a first SRS resource (shown as SRS resource A) and a second SRS resource (shown as SRS resource B). Therefore, antenna switching SRS can be transmitted in SRS resource A (e.g., a first time-frequency resource) using antenna ports 0 and 1, and antenna switching SRS can be transmitted in SRS resource B (e.g., a second time-frequency resource) using antenna ports 2 and 3.

[0112] As shown by reference numeral 520 in the attached figure, the second SRS resource set (e.g., shown as SRS resource set 2) can be a codebook use case. As illustrated, this example codebook SRS resource set only includes the first SRS resource (shown as SRS resource A). Therefore, codebook SRS can be transmitted in SRS resource A (e.g., the first time-frequency resource) using antenna ports 0 and 1. In this case, UE 120 may not use antenna ports 2 and 3 to transmit codebook SRS in SRS resource B (e.g., the second time-frequency resource).

[0113] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0114] Figure 6 This is a diagram illustrating example 600 of an SRS-based association for indicating the direction of uplink communication according to the present disclosure.

[0115] According to the various aspects described herein, the UE may (e.g., in beam scanning) transmit SRS bursts received by one or more mTRPs. Each mTRP may measure one or more SRSs. Each mTRP may report to the macro network entity the SRS with the strongest signal strength or quality among the SRS received from the UE by the mTRP. Each mTRP may report one or more SRSs with signal strength or quality above a threshold among the SRS received from the UE by the mTRP, or one or more measurements of the SRS received from the UE by the mTRP. The macro network entity may select an mTRP and the SRS associated with the selected mTRP based on the reports received from the mTRPs, and indicate the SRS associated with the beam or resources that the UE will use for uplink communication toward the mTRP (in the direction of the selected mTRP). The macro network entity may send an indication of the SRS to the UE. The UE may determine, at least in part, in which direction or to which mTRP, to transmit uplink communication based on the indicated SRS. The UE can associate the SRS with a beam and / or resources, and use that beam and / or resources to send uplink communication to the mTRP (e.g., UL-only mTRP). By using SRS beam scanning and indication of SRS association, the UE can send uplink communication to the mTRP using a beam and / or resources that are superior to others, which improves uplink communication even when downlink communication is not received from the mTRP. Therefore, signaling resources are saved and throughput is increased.

[0116] The UE may receive a configuration indicating one or more SRS sets for scanning SRS in one or more SRS bursts. For example, the configuration may include a first SRS set for scanning uplink beams from a first antenna panel and a second SRS set for scanning uplink beams from a second antenna panel, or an SRS set for scanning UL beams from both the first and second antenna panels.

[0117] Example 600 illustrates the UE transmitting as part of an SRS beam scan. N An SRS set of SRS resources (SRS burst) i mTRP k and mTRP l Both can receive one or more SRS. After measuring the SRS, mTRP k SRS can be selected k And mTRP l SRS can be selected l The selected SRS is the optimal SRS received from the UE during SRS beam scanning. k Available for mTRP k Uplink communication. The selected SRS. l Available for mTRP l Uplink communication. mTRP can report the selected SRS to macro network entities. Additionally or alternatively, mTRP can report measurements of SRS received from the UE during SRS beam scanning (e.g., RSSI, RSRP, or RSRQ).

[0118] The macro network entity may select the mTRP and the beam (direction) and / or resources associated with the selected SRS, at least in part, based on the selected SRS indicated by the mTRP, for the UE to use for uplink communication. The macro network entity may direct the mTRP... k and / or mTRP l Send an indication of the SRS associated with the selected beam and / or resource for the UE to use for uplink communication. This indication can be directed from the UE to the mTRP. k and / or mTRP l Uplink communication, the indication being at least in part based on association with the selected SRS (e.g., SRS k and / or SRS l Uplink communication can be configured semi-statically via RRC messages or dynamically indicated via DCI. Uplink communication may include PUCCH transmission, PUSCH transmission, and / or dedicated PRACH transmission.

[0119] The UE can receive this instruction, select the beam and / or resources associated with the indicated SRS, and use the selected beam and / or resources to transmit uplink communication. Since the UE knows the beam direction and / or resources used for the indicated SRS, no other signaling is required to indicate the direction in which the UE should transmit uplink communication to the mTRP.

[0120] Example 600 illustrates that uplink communication can be with an SRS indicated by a macro network entity. k Related PUCCH messages (PUCCH) k Or a scheduling request (SR) k PUSCH messages k ) or PRACH message (PRACH k ). The UE can be directed toward the mTRP. k Send PUCCH, PUSCH, or PRACH messages. Example 600 also shows that uplink communication can be with an SRS indicated by a macro network entity. l Related PUCCH messages (PUCCH) l or SR l ) or PUSCH message (PUSCH l ).

[0121] In some aspects, the indication may be directed to a PUCCH message associated with an SRS indicated in the SRS indication. The SRS-based association may be indicated via an SRS indication (e.g., the SRS ID, SRS index, SRS resource ID, or SRS resource index of one or more SRS bursts) for PUCCH transmission on one or more UL mTRP-only networks. This indication may be included in PUCCH spatial relation information (e.g., spatial relation information element (IE)). In some aspects, the indication may be included in the RRC configuration. PUCCHs (for DL ​​Hybrid Automatic Repeat Request (HARQ) feedback or SRs) may be configured with PUCCH spatial relation information (e.g., PUCCH-SpacialRelationInfo-ULmTRP The PUCCH spatial relationship information is referenced from a selected SRS used for mTRP only for UL (e.g., in referenceSignal-ULmTRP Below, among them srs_ULmTRP Set to have respectively for mTRP k or mTRP l of SRS_Burst i of ULmTRP-SRS_ID k , ULmTRP-SRS_Index l , ULmTRP-SRS_Resource_ID k or ULmTRP-SRS_Resource_Index l In some respects, this instruction can be included in the DCI. Macro network entities can include new fields in the DCI (e.g., ULmTRP Indicator). For example, for PUCCH transmission only on UL mTRP, ULmTRP In DCI format 1, the indicator can be equal to "1". In some respects, macro network entities can indicate to the UE that it wants to send uplink communication to the mTRP (e.g., ULmTRP (Indicator is "1") or to send uplink communication to the macro network entity (e.g., ULmTRP The indicator is "0".

[0122] In some respects, macro network entities may include new fields in the DCI for PUSCH transmission (e.g., ULmTRP Indicator). For example, for PUSCH transmission only on UL mTRP, ULmTRP The indicator can be equal to "1" in DCI format 0. In some respects, macro network entities can indicate to the UE that it wants to send uplink communication to the mTRP (e.g., ULmTRP (Indicator is "1") or to send uplink communication to the macro network entity (e.g., ULmTRP The indicator is "0".

[0123] In some respects, macro network entities may include new fields in the DCI for SRS transmission (e.g., ULmTRP Indicator). For example, for SRS transmissions specifically on UL mTRP only (e.g., dedicated to... mTRP k Non-sudden SRS k' send), ULmTRP The indicator can be equal to "1" in DCI format 0 or 1. In some respects, macro network entities can indicate to the UE whether to send uplink SRS to mTRP (e.g., ULmTRP (Indicator is "1") or to send uplink SRS to macro network entities (e.g., ULmTRP The indicator is "0".

[0124] In some aspects, the indication may be directed to a PUSCH message associated with an SRS indicated in the SRS indication. The SRS-based association may be indicated via an SRS indication (e.g., the SRS ID, SRS index, SRS resource ID, or SRS resource index of one or more SRS bursts) for PUSCH transmissions on one or more UL mTRP-only networks. This indication may be included in SRS resource information, such as in an SRS resource indicator for non-codebook-based or codebook-based transmissions. In some aspects, the indication may be in the RRC configuration. The RRC configuration may include configured parameters. srs- ResourceIndicator (for use based on) txConfig=nonCodebook or based on txConfig=CodebookThe PUSCH transmission), the parameters of this configuration are related to the SRS indication for the selected SRS of the SRS set or SRS burst (e.g., one or more SRS bursts (such as those for UL mTRP only)). SRS_Burst i )of ULmTRP-SRS_ID k , ULmTRP-SRS_Index l , ULmTRP- SRS_Resource_ID k , ULmTRP-SRS_Resource_Index l This is associated with [the relevant data]. In some respects, this indication can be included in the DCI. For example, the DCI may include DCI format 0 (for use based on...). txConfig=nonCodebook or based on txConfig= Codebook The field in the PUSCH transmission (e.g., SRS Resource Indicator (SRI)), which is associated with the SRS indication of a selected SRS for an SRS set or SRS burst (e.g., one or more SRS bursts (such as those used for...). ULmTRP of SRS_Burst i )of ULmTRP-SRS_ID k , ULmTRP-SRS_Index l , ULmTRP-SRS_Resource_ID k or ULmTRP-SRS_ Resource_Index l This configuration is associated with the number of SRS resources or SRS beams configured in the SRS resource set used for SRS bursts.

[0125] In some respects, for non-codebook-based PUSCH communication, this indication can be semi-statically configured via RRC or dynamically indicated via DCI. The UE can determine the pre-decoder and / or rank for uplink MIMO transmission based at least in part on adjusted measurements of the CSI-RS (e.g., measurements of the non-zero power (NZP) CSI-RS configured via RRC or indicated via DCI can be adjusted with offsets, such as those used for...). mTRPk or mTRPl of offset_mTRPk or offset_ mTRPl Additionally or alternatively, the UE may determine the pre-decoder and / or rank for uplink MIMO transmission based at least in part on adjusted path loss measurements for selected SRS (e.g., for each SRS). mTRPk or mTRPl Path loss ULmTRP_pl_SRSk , ULmTRP_pl_SRSk ).

[0126] In some respects, the UE may determine the SRS indication (e.g., PUCCH) based on downlink measurements (e.g., SSB or CSI-RS from a macro network entity) and / or corresponding offsets (e.g., offset for SSB measurement, offset for NZP CSI-RS measurement, offset for DL ​​path loss, or offset from the transmit power of SRS or PRACH transmissions on the uplink beam to the macro network entity). k PUSCH k , PRACH k or SRS k' (Non-sudden) to mTRP k Or PUCCH l PUSCH l , PRACH l or SRS l' (Non-sudden) to mTRP l The uplink transmission power on the associated UL beam.

[0127] In some aspects, the indication may be directed to a dedicated PRACH message associated with an SRS indicated in the SRS indication. The SRS-based association may be indicated via an SRS indication for an SRS set or SRS burst used for PRACH transmission on one or more UL mTRPs only. In some aspects, the indication may be included in a dedicated or contention-free PRACH configuration. In some aspects, the indication may indicate the mTRP used for PRACH.

[0128] In some aspects, PRACH configuration may include SRS resource information. SRS resource information may include one or more SRS resources or the beam direction of the PRACH associated with the SRS resource information. For example, it may include a CFRA configuration for UL mTRP only (e.g., CFRA-ULmTRP and / or CFRA-TwoStep-r16-ULmTRP ) only UL mTRP on RACH RRC configuration (e.g., RACH-ConfigDedicated-ULmTRP Indications for SRS may be included in the following fields: such as IE occasions-ULmTRP Below srs-perRACH-Occasion-ULmTRP , srs-ULmTRP (SRS associated with UL mTRP only) (e.g., srs-ResourceList-ULmTRP , ra-srs-OccasionMaskIndex-ULmTRP ) or IE resources-ULmTRP Below csirs-ULmTRP (For or reference to CSI-RS on DL for UL mTRP only) (e.g., csirs-ResourceList-ULmTRP , rsrp-ThresholdCSI-RS-ULmTRP or rsrp-ThresholdCSI-RS- UL mTRP-OffsetIn some respects, the SRS indication can be found in the RRC configuration field for resources based on CFRA SRS (e.g., with mTRP for UL-only resources). srs-ResourceList-UL mTRP (associated with one or more SRSs), such as CFRA-SRS-Resource-UL mTRP (For example, having) srs-UL mTRP (Includes SRS on mTRP for UL only) UL mTRP-SRS_ID or UL mTRP-SRS_Index ),and srs-UL mTRP Related ra-OccasionList- srsULmTRP and / or ra-PreambleIndex-srsULmTRP )or CFRA-CSIRS-Resource-UL mTRP (For example, having with) csi-RS-UL mTR (For example, for use with or reference to CI-RS on a DL for UL mTRP only) associated with csi-RS- UL mTRP , ra-OccasionList-UL mTRP and / or ra-PreambleIndex-UL mTRP ).

[0129] In some aspects, SRS-based associations can be indicated via an SRS indication of an SRS set or SRS burst for one or more PRACH transmissions on UL mTRP-only. This indication can be used for dedicated or contention-free PRACH transmissions. In some aspects, this indication can be included in fields that include new fields (e.g., UL mTRP In the PRACH message based on DCI commands (indicators), where at least in part it is based on PRACH on UL mTRP only, UL mTRP The indicator can be 1 in DCI format (e.g., DCI 1_0). In some respects, when UL mTRP When the indicator field is set to "1", the macro network entity can (e.g., in DCI 1_0) reuse the DCI field SS / PBCH index as... UL mTRP-SRS_ID , UL mTRP-SRS_Index , UL mTRP-SRS_ Resource_ID or UL mTRP-SRS_Resource_Index .

[0130] In some aspects, the indication of SRS may include SRS-based uplink TCI status. SRS-based associations may be indicated using a unified TCI framework via a new UL TCI status indication (e.g., SRS-based ULTCI status) associated with selected SRSs in an SRS set or SRS burst. TCI status indications may include those from macro-network entities (e.g., in...). FIG. 7 DL transmission (referred to as sTRP 705) and / or to UL-only mTRP (e.g., in FIG. 7A separate TCI status model for UL transmissions (referred to as mTRP 710 or mTRP715 in the text). Additionally or alternatively, the TCI status indication may include more than one UL transmission on only the UL mTRP. This indication may be included (e.g., in...) tci-StateToAddModList In a new UL TCI state (configured in the configuration or activated by MACCE), this new UL TCI state can be referenced from or associated with the SRS burst (e.g., having " referenceSignal srs: k "and" qcl-Type = TypeC "or" qcl-Type = TypeD "Based on SRS" k UL TCI status tci-StateId s3 For use in UL only mTRP k UL sent, or with " referenceSignal srs: l "and" qcl-Type = TypeC "or" qcl-Type = TypeD "Based on SRS" j UL TCI status tci-StateId s4 For use in UL only mTRP k (UL transmission). In some respects, TCI status tables (e.g., via RRC) tci-StateToAddModList Code points configured and activated via MAC-CE can be indicated using the unified TCI framework via the transmit configuration indication field in DCI (e.g., DCI 1_1, DCI 1_2, and DCI 1_3).

[0131] In some respects, an example of a unified TCI framework with a new UL TCI state may include a DCI that contains DL transmissions from sTRP. tci-StateId s1 code points (e.g., those with " referenceSignal ssb: i ") and / or used for UL transmission to sTRP tci-StateId s2 code points (e.g., those with " referenceSignal csi- rs: j Another example of a unified TCI framework could be a DCI, which contains DL transmissions for sTRP. tci- StateId s1 code points and / or used for mTRP k / mTRP l UL sent on tci-StateId s3 / tci-StateId s4 The code points. In yet another example, the unified TCI framework may include a DCI containing code points for mTRP. k UL sent on tci-StateId s3 code points and / or used for mTRP l UL sent on tci-StateId s4 The code points.

[0132] As indicated above, FIG. 6This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 6 The examples described are different.

[0133] FIG. 7 This is a diagram illustrating Example 700 of SRS used for uplink communication according to the instructions of this disclosure. Example 700 shows a macro network entity or a single TRP 705 (e.g., network node 110a) for both DL transmission and UL transmission, which can be connected via a wireless network (e.g., wireless communication network 100) to a UE 720 (e.g., UE 120) and multiple TRPs mTRPs for UL-only transmission. k 710 (e.g., network node 110b) and mTRP l 715 (e.g., network node 110c) communicates.

[0134] As shown by reference numeral 725 in the attached figure, sTRP 705 can send a UL-only mTRP (e.g., mTRP) to support uplink communication from UE 720. k mTRP l As indicated by reference numeral 730 in the accompanying drawings, UE 720 may transmit UE capability information and / or UE auxiliary information. UE capability information may include UE capability information for supporting UL-only mTRP. UE capability information or UE auxiliary information may indicate the number of panels, the number of UL beams per panel, and / or the total number of UL beams.

[0135] As indicated by reference numeral 735 in the attached figure, sTRP 705 may indicate a configuration (e.g., RRC configuration) for an SRS burst configuration. An SRS burst configuration may indicate one or more SRS set configurations, wherein each SRS set configuration contains an SRS set ID or index, the duration of the SRS burst, the SRS resources of the SRS burst (e.g., time slots and / or symbols in time, PRBs or ports in frequency), the periodicity of periodic SRS bursts, a time window or time interval between multiple SRS bursts, the number of SRS bursts within a time window or repeating SRS bursts, or conditions for triggering one or more SRS bursts. As indicated by reference numeral 740, UE 720 may transmit one or more SRS bursts as part of an SRS beam scan, based at least in part on an SRS burst configuration received from sTRP via reference numeral 735, or at least in part on an SRS burst indication from sTRP (as indicated by reference numeral 737) (such as a MAC activating one or more SRS bursts or a DCI requesting one or more SRS bursts). (e.g., a MAC-CE or DCI may indicate an SRS set index or ID for the SRS burst and a time window or interval or number of SRS bursts for the SRS burst). Beam scanning may be used for mTRP selection and / or UL beam selection. mTRP may each measure one or more SRS received from the SRS burst and report the measurements and associated SRS to sTRP 705 (e.g., RSSI, RSRP, or RSRQ measurements associated with received SRS, or with selected SRS with measurements above a threshold, or with selected SRS or maximum signal strength or quality SRS with maximum RSSI, RSRP, or RSRQ measurements). Alternatively, the mTRP may receive one or more SRSs from the SRSs and select the SRS to report to the sTRP 705 (e.g., the best SRS or the SRS with the highest signal strength or quality). As shown by reference numeral 745, the mTRP k Reportable measurements, SRS, etc. (e.g., at least measurements and / or SRS, such as SRS) k As shown by reference numeral 750 in the attached figure, mTRP l Reportable measurements, SRS, etc. (e.g., at least measurements and / or SRS, such as SRS) l ).

[0136] sTRP 705 may select one or more UL-only mTRPs based at least in part on reports received from mTRPs containing measurements and / or SRSs, and select one or more SRSs for each of the selected mTRPs. sTRP 705 may send an indication of the selected SRS or associated TCI status, such that UE 720 can determine the beam direction and / or resources for transmitting UL communications (e.g., non-burst SRS, PUCCH, PUSCH, and / or PRACH) toward the mTRP. Reference numerals 755 to 795 provide several examples of such indications. As shown in reference numeral 755, sTRP 705 may send an indication in an RRC configuration containing configurations for UL transmission based at least in part on the UL transmission associated with one or more SRSs selected from the SRS set (e.g., non-burst SRS configurations, PUCCH configurations, PUSCH configurations, and / or PRACH configurations based on one or more SRS indices, IDs, SRS resource indices, or IDs of the SRS set used for SRS bursts). As indicated by reference numeral 760 in the accompanying drawings, sTRP 705 may send an indication via MAC activation of one or more TCI states associated with one or more spatial relationships (e.g., associated with one or more SRS in a set of SRS for an SRS burst) or associated with one or more selected SRSs (e.g., associated with one or more selected SRS in a set of SRS for an SRS burst).

[0137] In some respects, sTRP 705 can send DCIs associated with the unified TCI state framework. As shown by reference numeral 765, sTRP 705 can send DCIs for use with mTRP k or mTRP l The UL's TCI status indication. For example, the DCI may include the first TCI status for DL ​​transmissions from sTRP 705 (e.g., PDSCH transmissions as shown in reference numeral 767) and / or for transmissions to mTRP. k 710 or mTRP l The second TCI state of UL 715. As shown by reference numeral 770 in the attached figure, UE 720 can send to mTRP k or mTRP l Send a non-burst SRS, PUCCH message (e.g., ACK or NACK for PDSCH as shown in reference numeral 767), PUSCH message (e.g., with or without ACK or NACK for PDSCH as shown in reference numeral 767), or PRACH message, depending on which mTRP is associated with the indicated SRS or TCI state. As shown in reference numeral 775, sTRP 705 can send a message in DCI for the mTRP. k or mTRPl The DCI indicates the UL TCI status. For example, the DCI may include the first UL TCI status for sTRP 705 and / or for mTRP. k 710 or mTRP l The second TCI state of UL 715. As shown by reference numeral 780, UE 720 can send SRS, PUCCH, PUSCH, or PRACH messages to sTRP 705. As shown by reference numeral 785, UE 720 can send to mTRP k or mTRP l Send a non-burst SRS, PUCCH, PUSCH, or PRACH message, depending on which mTRP is associated with the indicated SRS or TCI state.

[0138] As shown by reference numeral 790 in the attached figure, sTRP 705 can send in the DCI for use with mTRP k or mTRP l The UL's TCI status indication. For example, DCI may include information for mTRP. k UL's first TCI status and / or used for mTRP l The second TCI state of the UL. As shown by reference numeral 795 in the attached figure, the UE 720 can send a message to mTRP. k or mTRP l Sending an SRS, PUCCH, or PUSCH message depends on which mTRP is associated with the indicated SRS. In some respects, DCI can be associated with the Unified TCI State Framework.

[0139] As indicated above, FIG. 7 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 7 The examples described are different.

[0140] FIG. 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120, UE 720) performs operations associated with an SRS-based uplink communication direction.

[0141] like FIG. 8 As shown, in some aspects, process 800 may include transmitting an SRS set during beam scanning (box 810). For example, the UE (e.g., using...) FIG. 11 The depicted transmitting component 1104 and / or communication manager 1106 can transmit SRS sets during beam scanning, as described above.

[0142] like FIG. 8As further shown, in some aspects, process 800 may include receiving an indication for sending uplink communication toward the TRP (box 820). For example, the UE (e.g., using...) FIG. 11 The depicted receiving component 1102 and / or communication manager 1106 can receive instructions for sending uplink communication toward the TRP, as described above.

[0143] like FIG. 8 As further shown, in some aspects, process 800 may include sending uplink communication toward the TRP (block 830) at least in part based on an instruction. For example, the UE (e.g., using...) FIG. 11 The transmitting component 1104 and / or the communication manager 1106 depicted may transmit uplink communication toward the TRP, at least in part, based on instructions, as described above. The TRP may be an mTRP.

[0144] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0145] In the first respect, TRP is an uplink-only TRP.

[0146] In a second aspect, either alone or in combination with the first aspect, it indicates the spatial relation IE in the RRC configuration for the control channel, and the spatial relation IE includes the beam direction associated with the SRS.

[0147] In the third aspect, either alone or in combination with one or more of the first and second aspects, the indication includes a TRP indication in the DCI used for control channel transmission or data transmission.

[0148] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the indication includes an SRS indication in the RRC configuration for the data channel, and the SRS indication indicates the beam direction.

[0149] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, it indicates an SRS resource indicator in the DCI used for data channel transmission.

[0150] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 800 includes receiving an indication of an offset for uplink communication, wherein transmitting uplink communication includes transmitting uplink communication at least in part based on the offset.

[0151] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes receiving an instruction for path loss adjustment, wherein transmitting uplink communication includes transmitting uplink communication at least in part based on path loss adjustment.

[0152] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, it indicates that TRP information is included in the PRACH configuration and that the TRP is associated with the SRS in the SRS set in the beam scan.

[0153] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, it indicates SRS resource information including PRACH configuration, and the SRS resource information includes one or more of SRS resources or beam directions of PRACH associated with the SRS resource information.

[0154] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the indication includes an mTRP indication in the DCI for PRACH. The mTRP indication may be a micro TRP indication.

[0155] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, it is indicated that SRS information is included in the DCI for PRACH.

[0156] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, it indicates at least one TCI status information associated with at least one SRS in the SRS set in the beam scan.

[0157] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, at least one TCI status information indicates a unified TCI status for transmission to the TRP.

[0158] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 800 includes transmitting an indication of the UE's capability to support SRS beam scanning, and receiving an SRS set configuration indicating parameters for performing beam scanning.

[0159] although FIG. 8 An example box of process 800 is shown, but in some respects, process 800 may include... FIG. 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0160] FIG. 9This is a diagram illustrating an example process 900 performed, for example, at a network entity or a device of a network entity according to this disclosure. Example process 900 is an example in which a device or network entity (e.g., network node 110, sTRP 705) performs operations associated with an SRS-based uplink communication direction.

[0161] like FIG. 9 As shown, in some aspects, process 900 may include receiving an indication of a selected SRS from the TRP (box 910). For example, a network entity (e.g., using...) FIG. 12 The depicted receiving component 1202 and / or communication manager 1206 can receive instructions for selected SRS from the TRP, as described above.

[0162] like FIG. 9 As further shown, in some aspects, process 900 may include sending an indication to the UE for sending uplink communication to a selected TRP, at least in part, based on a selected SRS (box 920). For example, a network entity (e.g., using...) FIG. 12 The transmission component 1204 and / or communication manager 1206 described herein may, at least in part, transmit to the UE an instruction for sending uplink communication to a selected TRP based on a selected SRS, as described above.

[0163] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0164] In the first aspect, the indication includes the spatial relation IE in the RRC configuration for the control channel, and the spatial relation IE includes the beam direction associated with the SRS.

[0165] In the second aspect, either alone or in combination with the first aspect, the indication includes a TRP indication in the DCI used for control channel transmission or data transmission.

[0166] In the third aspect, either alone or in combination with one or more of the first and second aspects, the indication includes an SRS indication in the RRC configuration for the data channel, and the SRS indicates the beam direction.

[0167] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, an indication is provided that includes an SRS resource indicator in the DCI used for data channel transmission.

[0168] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 900 includes sending an indication of a transmit power offset for uplink communication.

[0169] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 900 includes sending an indication for path loss adjustment for uplink communication.

[0170] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, it indicates that TRP information is included in the PRACH configuration, and that the TRP is associated with the SRS indicated by the TRP information.

[0171] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, it indicates SRS resource information including PRACH configuration, wherein the SRS resource information includes at least one of resources and the beam direction of the PRACH associated with the SRS resource information.

[0172] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the indication includes the TRP indication in the DCI for PRACH.

[0173] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, it indicates that SRS information is included in the DCI for PRACH.

[0174] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, it indicates that at least one TCI status information is associated with the SRS indicated by the TRP.

[0175] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the TCI status information indicates the unified TCI status used to send to the TRP.

[0176] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 900 includes receiving an indication of the UE's capability to support SRS beam scanning, and transmitting an SRS set configuration indicating parameters for performing beam scanning using the SRS set.

[0177] although FIG. 9 An example box of process 900 is shown, but in some respects, process 900 may include... FIG. 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0178] FIG. 10This is a diagram illustrating an example process 1000 performed, for example, at a network entity or a device of a network entity, according to this disclosure. Example process 1000 is where a device or network entity (e.g., network node 110, mTRP) is located. k 710, mTRP l 715) An example of performing operations associated with an SRS-based uplink communication direction.

[0179] like FIG. 10 As shown, in some aspects, process 1000 may include receiving one or more SRSs from the UE (block 1010). For example, a network entity (e.g., using...) FIG. 12 The described receiving component 1202 and / or communication manager 1206 can receive one or more SRS from the UE, as described above.

[0180] like FIG. 10 As further shown, in some aspects, process 1000 may include sending an indication in an uplink message for an SRS selected at least in part based on signal strength or quality (box 1020). For example, a network entity (e.g., using...) FIG. 12 The transmitting component 1204 and / or the communication manager 1206 depicted may transmit an indication in an uplink message for an SRS selected at least in part based on signal strength or quality, as described above.

[0181] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0182] although FIG. 10 An example box of process 1000 is shown, but in some aspects, process 1000 may include... FIG. 10 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0183] FIG. 11 This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... FIG. 1The described communication manager 140. As shown, device 1100 can communicate with another device 1108 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1102 and transmitting component 1104.

[0184] In some respects, device 1100 can be configured to perform the functions described herein. FIG. 1 to FIG. 7 The described one or more operations. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as FIG. 8 The process is 800. In some respects, FIG. 11 The illustrated device 1100 and / or one or more components may include a combination FIG. 2 One or more components of the described UE. Additionally or alternatively, FIG. 11 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0185] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... FIG. 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0186] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... FIG. 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0187] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the reception of communications by the receiving component 1102 and / or the transmission of communications by the transmitting component 1104. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the reception and / or transmission of communications.

[0188] Transmitting component 1104 can transmit an SRS set during beam scanning. Receiving component 1102 can receive an indication for transmitting uplink communication toward the TRP. Transmitting component 1104 can transmit uplink communication toward the TRP at least in part based on the indication.

[0189] The receiving component 1102 may receive an indication of an offset for uplink communication, wherein transmitting uplink communication includes transmitting uplink communication at least in part based on the offset. The receiving component 1102 may also receive an indication of path loss adjustment, wherein transmitting uplink communication includes transmitting uplink communication at least in part based on path loss adjustment.

[0190] Transmitting component 1104 can transmit an indication of the UE's capability to support SRS beam scanning. Receiving component 1102 can receive an SRS set configuration indicating parameters for performing beam scanning.

[0191] FIG. 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore,FIG. 11 The two or more components shown can be implemented within a single component, or FIG. 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 11 The executable description of the collection of (one or more) components shown is composed of FIG. 11 Another set of components shown performs one or more functions.

[0192] FIG. 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a network entity, or a network entity may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1206 is combined with... FIG. 1 The described communication manager 150 or 160. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0193] In some respects, device 1200 can be configured to perform the functions described herein. FIG. 1 to FIG. 7 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as FIG. 9 The process 900 FIG. 10 The process 1000 or a combination thereof. In some respects, FIG. 12 The illustrated device 1200 and / or one or more components may include a combination FIG. 2 One or more components of the described network entity. Additionally or alternatively, FIG. 12 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0194] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... FIG. 2 The described network entity includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0195] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... FIG. 2 The described network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

[0196] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0197] In some respects, receiving component 1202 may receive an indication of a selected SRS from the TRP. Transmitting component 1204 may transmit to the UE an indication for sending uplink communication to the selected TRP, at least in part, based on the selected SRS.

[0198] Transmitting component 1204 can transmit an indication of transmit power offset for uplink communication. Transmitting component 1204 can also transmit an indication of path loss adjustment for uplink communication. Receiving component 1202 can receive an indication of UE capability to support SRS beam scanning.

[0199] The transmitting component 1204 can transmit an SRS set configuration indicating parameters for performing beam scanning using the SRS set.

[0200] In some respects, receiving component 1202 may receive one or more SRSs from the UE. Transmitting component 1204 may transmit an indication in an uplink message of an SRS selected at least in part based on signal strength or quality.

[0201] FIG. 12 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 12 The two or more components shown can be implemented within a single component, or FIG. 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 12 The executable description of the collection of (one or more) components shown is composed of FIG. 12 Another set of components shown performs one or more functions.

[0202] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: transmitting a set of sounding reference signals (SRS) in a beam scan; receiving an instruction for transmitting uplink communication toward a transmit-receive point (TRP); and transmitting the uplink communication toward the TRP based at least in part on the instruction.

[0203] Aspect 2: The method according to aspect 1, wherein the TRP is an uplink-only TRP.

[0204] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the indication includes a spatial relation information element (IE) in a radio resource control configuration for controlling the channel, and wherein the spatial relation IE includes a beam direction associated with the SRS.

[0205] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the indication includes a TRP indication in downlink control information for control channel transmission or data transmission.

[0206] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the indication includes an SRS indication in a radio resource control configuration for a data channel, and wherein the SRS indication indicates a beam direction.

[0207] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the indication includes an SRS resource indicator in downlink control information for data channel transmission.

[0208] Aspect 7: The method according to any one of aspects 1 to 6, the method further comprising receiving an indication of an offset for the uplink communication, wherein sending the uplink communication includes sending the uplink communication at least in part based on the offset.

[0209] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising receiving an indication for path loss adjustment, wherein sending the uplink communication includes sending the uplink communication at least in part based on the path loss adjustment.

[0210] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the indication includes TRP information in the physical random access channel configuration, and wherein the TRP is associated with an SRS in the SRS set in the beam scan.

[0211] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the indication includes SRS resource information in the Physical Random Access Channel (PRACH) configuration, and wherein the SRS resource information includes one or more of SRS resources or beam directions of the PRACH associated with the SRS resource information.

[0212] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the indication includes a multiple transmit receive point (mTRP) indication in downlink control information for a physical random access channel.

[0213] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the indication includes SRS information in the downlink control information for the physical random access channel.

[0214] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the indication includes at least one Transmit Configuration Indicator (TCI) status information associated with at least one SRS in the SRS set in the beam scan.

[0215] Aspect 14: According to the method of aspect 13, wherein the at least one TCI status information indicates a unified TCI status for sending to the TRP.

[0216] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: transmitting an indication of a UE capability for supporting SRS beam scanning; and receiving an SRS set configuration indicating parameters for performing the beam scanning.

[0217] Aspect 16: A method of wireless communication performed by a network entity, the method comprising: receiving an indication of a selected probe reference signal (SRS) from a transmit receiving point (TRP); and transmitting an indication to a user equipment (UE) for transmitting uplink communication to the selected TRP, at least in part based on the selected SRS.

[0218] Aspect 17: The method according to aspect 16, wherein the indication includes a spatial relation information element (IE) in a radio resource control configuration for controlling the channel, and wherein the spatial relation IE includes a beam direction associated with the SRS.

[0219] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the indication includes a TRP indication in downlink control information for control channel transmission or data transmission.

[0220] Aspect 19: The method according to any one of Aspects 16 to 18, wherein the indication includes an SRS indication in a radio resource control configuration for a data channel, and wherein the SRS indicates a beam direction.

[0221] Aspect 20: The method according to any one of Aspects 16 to 19, wherein the indication includes an SRS resource indicator in downlink control information for data channel transmission.

[0222] Aspect 21: The method according to any one of aspects 16 to 20, the method further comprising sending an indication of a transmit power offset for the uplink communication.

[0223] Aspect 22: The method according to any one of aspects 16 to 21, the method further comprising sending an indication for path loss adjustment for the uplink communication.

[0224] Aspect 23: The method according to any one of Aspects 16 to 22, wherein the indication includes TRP information in the physical random access channel configuration, and wherein the TRP is associated with the SRS indicated by the TRP information.

[0225] Aspect 24: The method according to any one of Aspects 16 to 23, wherein the indication includes SRS resource information in the Physical Random Access Channel (PRACH) configuration, and wherein the SRS resource information includes at least one of the resources of the PRACH and the beam direction associated with the SRS resource information.

[0226] Aspect 25: The method according to any one of Aspects 16 to 24, wherein the indication includes a TRP indication in the downlink control information for the physical random access channel.

[0227] Aspect 26: The method according to any one of Aspects 16 to 25, wherein the indication includes SRS information in the downlink control information for the physical random access channel.

[0228] Aspect 27: The method according to any one of Aspects 16 to 26, wherein the indication includes at least one Transmission Configuration Indicator (TCI) status information associated with the SRS indicated by the TRP.

[0229] Aspect 28: According to the method of aspect 27, wherein the TCI status information indicates a unified TCI status for sending to the TRP.

[0230] Aspect 29: The method according to any one of Aspects 16 to 28, the method further comprising: receiving an indication of a UE capability for supporting SRS beam scanning; and transmitting an SRS set configuration indicating parameters for performing beam scanning using an SRS set.

[0231] Aspect 30: A method of wireless communication performed by a network entity, the method comprising: receiving one or more sounding reference signals (SRS) from a user equipment (UE); and sending an indication in an uplink message of an SRS selected at least in part based on signal strength or quality.

[0232] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 30.

[0233] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0234] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0235] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 30.

[0236] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 30.

[0237] Aspect 36: A device for wireless communication, the device including a processing system comprising: one or more processors; and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0238] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0239] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0240] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0241] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0242] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0243] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0244] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to cause the UE to: Transmit a set of probe reference signals (SRS) during beam scanning; Receive an instruction for sending uplink communication toward the Transmitter-Receiver Point (TRP); and The uplink communication is sent toward the TRP based at least in part on the instruction.

2. The apparatus of claim 1, wherein the TRP is an uplink-only TRP.

3. The apparatus of claim 1, wherein the indication includes a spatial relation information element (IE) in a radio resource control configuration for controlling the channel, and wherein the spatial relation IE includes a beam direction associated with the SRS.

4. The apparatus of claim 1, wherein the indication includes a TRP indication in downlink control information for controlling channel transmission or data transmission.

5. The apparatus of claim 1, wherein the indication includes an SRS indication in a radio resource control configuration for a data channel, and wherein the SRS indication indicates a beam direction.

6. The apparatus of claim 1, wherein the indication includes an SRS resource indicator in downlink control information for data channel transmission.

7. The apparatus of claim 1, wherein the one or more processors are individually or jointly further configured to cause the UE to receive an indication of an offset for the uplink communication, and wherein, in order to transmit the uplink communication, the one or more processors are individually or jointly configured to cause the UE to transmit the uplink communication at least in part based on the offset.

8. The apparatus of claim 1, wherein the one or more processors are individually or jointly further configured to cause the UE to receive an indication of path loss adjustment, and wherein, in order to transmit the uplink communication, the one or more processors are individually or jointly configured to cause the UE to transmit the uplink communication at least in part based on the path loss adjustment.

9. The apparatus of claim 1, wherein the indication includes TRP information in the physical random access channel configuration, and wherein the TRP is associated with an SRS in the SRS set during the beam scan.

10. The apparatus of claim 1, wherein the indication includes SRS resource information in a Physical Random Access Channel (PRACH) configuration, and wherein the SRS resource information includes one or more of an SRS resource or a beam direction of the PRACH associated with the SRS resource information.

11. The apparatus of claim 1, wherein the indication includes a multiple transmit / receive point (mTRP) indication in downlink control information for a physical random access channel.

12. The apparatus of claim 1, wherein the indication includes SRS information in downlink control information for a physical random access channel.

13. The apparatus of claim 1, wherein the indication includes at least one transmit configuration indicator (TCI) status information associated with at least one SRS in the SRS set of the beam scan.

14. The apparatus of claim 13, wherein the at least one TCI status information indicates a unified TCI status for transmission to the TRP.

15. The apparatus of claim 1, wherein the one or more processors are further configured individually or collectively to cause the UE to: Send an indication of the UE's capability to support SRS beam scanning; and Receive the SRS set configuration indicating the parameters used to perform the beam scan.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network entity to: Receive indication of the selected sounding reference signal (SRS) from the transmit-receive point (TRP); and Instructions for sending uplink communication to the selected TRP are sent to the User Equipment (UE) at least in part based on the selected SRS.

17. The apparatus of claim 16, wherein the indication includes a spatial relation information element (IE) in a radio resource control configuration for a control channel or a data channel, and wherein the spatial relation IE includes a beam direction associated with the SRS.

18. The apparatus of claim 16, wherein the indication includes a TRP indication, an SRS indication, or an SRS resource indicator in downlink control information for control channel transmission or data transmission.

19. The apparatus of claim 16, wherein the indication includes an SRS indication in a radio resource control configuration for a data channel, and wherein the SRS indicates a beam direction.

20. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network entity to: Receive one or more detection reference signals (SRS) from user equipment (UE); as well as Send an instruction for an SRS selected at least in part based on signal strength or quality.