JP2024517192A - Association of SRS resource sets and beam orders for multi-beam PUSCH - Google Patents

Abstract

A method, apparatus, and computer-readable storage medium for PUSCH repetition and SRS resource sets are provided. An exemplary method includes receiving a configuration of a first SRS resource set and a second SRS resource set. The exemplary method further includes receiving a DCI for UL transmission from a network entity, the DCI indicating the first SRS resource set and the second SRS resource set. The first SRS resource set/second SRS resource set are associated with a first beam/second beam, respectively. The exemplary method further includes having the network entity transmit a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.

Description

Claiming priority

CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of and priority to U.S. Provisional Application No. 63/185,919, entitled "SRS RESOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH," filed May 7, 2021, and U.S. Nonprovisional Application No. 17/662,222, entitled "SRS RESOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH," filed May 5, 2022, which are expressly incorporated by reference in their entireties.

[0002] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems having a sounding reference signal (SRS), downlink control information (DCI), and a physical uplink (UL) shared channel (PUSCH).

Introduction
[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP®) to meet new requirements related to latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE®) standard. Further improvements in 5G NR technology are necessary. These improvements may also be applicable to other multiple access technologies and telecommunications standards that employ these technologies.

[0005] The following presents a simplified summary of one or more aspects to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description presented later. In some wireless communication systems, different physical uplink shared channel (PUSCH) repetitions shall be received at different transmit reception points (TRPs), panels, or antennas at a base station, and the repetitions may use the same beam or different beams. For example, two sets of repetitions may be provided, each including its own beam associated with its own power control parameters. Each set of repetitions may include one or more repetitions. Such two sets of repetitions may correspond to two SRS resource sets, which may include a DCI that may indicate one or more SRS resources in each of the two SRS resource sets, thereby indicating two beams and two sets of power control parameters. Aspects herein enable an association between the two SRS resource sets and the two sets of PUSCH repetitions, which facilitates more efficient PUSCH transmissions.

[0006] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus in a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive a configuration of a first SRS resource set and a second SRS resource set. The memory and the at least one processor coupled to the memory may be further configured to receive, from a network entity (e.g., a base station or a component of a base station), a DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The memory and at least one processor coupled to the memory may be further configured to transmit, to the network entity, a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.

[0007] In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus in a network entity (e.g., a base station or a component of a base station) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set. The memory and the at least one processor coupled to the memory may be further configured to transmit, for the UE, a DCI for an UL transmission, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The memory and at least one processor coupled to the memory may be further configured to receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information transmitted in a configuration of the first SRS resource set and the second SRS resource set or in a DCI that schedules the UL transmission.

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

[0009] FIG. 1 illustrates an example of a wireless communication system and access network. [0010] FIG. 2 illustrates an example of a first frame, in accordance with various aspects of the present disclosure. [0011] FIG. 2 illustrates an example of a DL channel in a subframe, in accordance with various aspects of the present disclosure. [0012] FIG. 4 illustrates an example of a second frame, in accordance with various aspects of the present disclosure. [0013] FIG. 2 illustrates an example of a UL channel in a subframe, in accordance with various aspects of the present disclosure. [0014] FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. [0015] FIG. 2 illustrates a base station in communication with a UE. [0016] FIG. 2 illustrates communication between a UE and a network entity. [0017] FIG. 2 illustrates an example mapping pattern for physical uplink shared channel (PUSCH) repetition. [0018] FIG. 1 illustrates an example mapping pattern for PUSCH repetition. [0019] FIG. 1 is a flow chart of a method of wireless communication. [0020] FIG. 1 illustrates an example of a hardware implementation for an exemplary apparatus. [0021] FIG. 1 is a flow chart of a method of wireless communication. [0022] FIG. 1 illustrates an example of a hardware implementation for an exemplary apparatus. [0023] FIG. 1 illustrates an example disaggregated base station architecture. [0024] FIG. 1 illustrates an example of a hardware implementation for an exemplary network entity. [0025] FIG. 1 illustrates an example of a hardware implementation for an exemplary network entity.

[0026] The detailed description of the invention described below with reference to the accompanying drawings illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] Next, several aspects of a telecommunications system are presented with respect to various apparatus and methods. These apparatus and methods are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0028] As an example, the elements, or any portion of the elements, or any combination of the elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0029] Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of that type of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Although aspects and implementations are described in this application by way of illustration for several examples, those skilled in the art will appreciate that additional implementations and use cases may occur in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and/or uses may occur via integrated chip implementations and other non-modular component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically targeted to a use case or application, a wide combination of applicability of the described innovations may occur. Implementations may range from chip-level or modular components to non-modular non-chip-level implementations, and even aggregated, distributed, or original equipment manufacture (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders/adders, etc.). It is intended that the innovations described herein may be practiced in a wide variety of devices of different sizes, shapes and configurations, chip-level components, systems, distributed configurations, aggregated or disaggregated components, end-user devices, etc.

[0031] A deployment of a communication system, such as a 5G NR system, may be configured in multiple ways with various components or components. In a 5G NR system, or network, a network node, network entity, mobility element of a network, radio access network (RAN) node, core network node, network element, or network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functions, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit reception point (TRP), or cell) may be implemented as an aggregated or disaggregated base station (also known as a standalone BS or monolithic BS).

[0032] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may take into account the aggregation characteristics of base station functions. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration sponsored by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in various physical locations, as well as virtually distributing functions for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0034] FIG. 1 illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., 5G core (5GC)). The base station 102 may include macro cells (high power cellular base stations) and/or small cells (low power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0035] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 through a second backhaul link 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: forwarding of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and distribution of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) over the third backhaul link 134 (e.g., the X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0036] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may serve a closed group known as a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) transmissions (also referred to as a reverse link) from the UE 104 to the base station 102, and/or downlink (DL) transmissions (also referred to as a forward link) from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may be through one or more carriers. The base station 102/UE 104 may use spectrum with up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth per carrier allocated in a carrier aggregation with up to Yx MHz total (x component carriers) used for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0037] Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL/UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0038] The wireless communication system may further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STA 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating to determine if a channel is available.

[0039] The small cell 102' may operate in licensed and/or unlicensed frequency spectrums. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. A small cell 102' employing NR in an unlicensed frequency spectrum may boost coverage to and/or increase capacity of the access network.

[0040] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar naming issue sometimes occurs with FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0041] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified these mid-band frequency bands of operation as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and/or FR2 characteristics, thus effectively extending FR1 and/or FR2 features to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042] With the above aspects in mind, unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, terms such as "millimeter wave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

[0043] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "millimeter wave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.

[0044] The base station 102, whether a small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and/or at near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates at millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and/or antenna arrays, to enable beamforming.

[0045] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive a beamformed signal from the base station 180 in one or more receive directions 182''. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive a beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180/UE 104. The transmit direction and receive direction for the base station 180 may be the same or different. The transmit direction and receive direction for the UE 104 may be the same or different.

[0046] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to a PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for the UE as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to an IP Services 176. The IP services 176 may include Internet, Intranet, IP Multimedia Subsystem (IMS), PS Streaming Services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and start MBMS bearer services in the Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to base stations 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start/stop) and collecting eMBMS-related charging information.

[0047] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with an integrated data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, intranets, IP multimedia subsystems (IMS), packet switched (PS) streaming (PSS) services, and/or other IP services.

[0048] A base station may include and/or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UEs 104. Examples of UEs 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communications devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration. One or more of these devices may collectively access the network and/or individually access the network.

[0049] Referring again to FIG. 1, in some aspects the UE 104 may include an SRS component 198. In some aspects the SRS component 198 may be configured to receive (e.g., from a network entity such as the base station 102/180) a configuration of a first SRS resource set and a second SRS resource set. In some aspects the SRS component 198 may be further configured to receive from the network entity (e.g., the base station 102/180) a DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. In some aspects, the SRS component 198 may be further configured to transmit to the network entity a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The UL transmission may include a PUSCH, including the first set of PUSCH repetitions and the second set of PUSCH repetitions. For example, a first set of repetitions of the PUSCH may be transmitted on a first beam associated with a first SRS resource set, and power control for the PUSCH may be based on an SRS resource indicator (SRI) associated with the first SRS resource set, and a second set of repetitions of the PUSCH may be transmitted on a second beam associated with a second SRS resource set, and power control for the PUSCH may be based on an SRI associated with the second SRS resource set. The network entity may be a network node. The network node may be implemented as an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. The network entities may be implemented in an aggregated or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, DU, RU, Near-Real-Time (Near-RT) RAN Intelligent Controller (RIC), or Non-Real-Time (Non-RT) RIC.

[0050] In some aspects, the base station 180 may include an SRS component 199. In some aspects, the SRS component 199 may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set. In some aspects, the SRS component 199 may be further configured to transmit, for the UE, a DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. In some aspects, the SRS component 199 may be further configured to receive a first set of repetitions of the PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information transmitted in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The UL transmission may include a PUSCH including a first set of PUSCH repetitions and a second set of PUSCH repetitions. For example, the first set of PUSCH repetitions may be received on a first beam associated with a first SRS resource set, and power control for the PUSCH may be based on an SRI associated with the first SRS resource set, and the second set of PUSCH repetitions may be received on a second beam associated with a second SRS resource set, and power control for the PUSCH may be based on an SRI associated with the second SRS resource set.

[0051] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0052] FIG. 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) where subframes within the set of subcarriers for a particular set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL, or may be time division duplex (TDD) where subframes within the set of subcarriers for a particular set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. In the example provided by Figures 2A and 2C, the 5G NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically/statically through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure, which is TDD.

2A-2D show a frame structure, aspects of the disclosure may be applicable to other wireless communication technologies, which may have different frame structures and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (also called Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-limited scenarios limited to single stream transmission). The number of slots in a subframe is based on the CP and numerology. The numerology defines the subcarrier spacing (SCS) and the symbol length/duration, which is effectively equal to 1/SCS.

[0054] For normal CP (14 symbols/slot), different numerologies μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, numerology 2 allows 4 slots per subframe. Thus, for normal CP and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. Subcarrier spacing may be equal to 2 ^μ * 15 kHz, where μ is numerology 0-4. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz, and numerology μ=4 has a subcarrier spacing of 240 kHz. Symbol length/duration is inversely related to subcarrier spacing. Figures 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0055] A resource grid may be used to represent the frame structure. Each time slot contains a physical resource block (RB), also called PRB, that spans 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0056] As shown in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (shown as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0057] Figure 2B shows an example of various DL channels in a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE containing 6 RE groups (REGs), each REG containing 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and/or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe/symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data and broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0058] As shown in FIG. 2C, some of the REs carry DM-RS (denoted as R for one particular configuration, although other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0059] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as shown in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and/or negative ACKs (NACKs)). The PUSCH carries data and may be further used to carry buffer status reports (BSRs), power headroom reports (PHRs), and/or UCI.

3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller/processor 375. The controller/processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller/processor 375 controls RRC layer functions related to broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions related to header compression/decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), and MAC SDUs from TBs. Provides MAC layer functions related to SDU demultiplexing, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0061] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions related to various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined with each other using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

[0062] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers the information modulated onto an RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover the spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the spatial streams may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functions.

[0063] The controller/processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0064] Similar to the functionality described with respect to DL transmissions by base station 310, controller/processor 359 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting, as well as PDCP layer functions related to header compression/decompression, security (encryption, decryption, integrity protection, integrity verification), as well as RLC layer functions related to forwarding of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs, as well as MAC layer functions related to mapping between logical channels and transport channels, multiplexing and demultiplexing of MAC SDUs onto and from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0065] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to enable spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0066] UL transmissions are processed at the base station 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0067] The controller/processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0068] At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to implement aspects related to the SRS component 198 of FIG. 1.

[0069] At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to implement aspects related to the SRS component 199 of FIG. 1.

[0070] FIG. 4 is a diagram 400 illustrating a base station 402 in communication with a UE 404. With reference to FIG. 4, the base station 402 may transmit beamformed signals to the UE 404 in one or more of the directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h. The UE 404 may receive beamformed signals from the base station 402 in one or more receive directions 404a, 404b, 404c, 404d. The UE 404 may also transmit beamformed signals to the base station 402 in one or more of the directions 404a-404d. The base station 402 may receive beamformed signals from the UE 404 in one or more of the receive directions 402a-402h. The base station 402/UE 404 may perform beam training to determine the best receive and transmit directions for each of the base stations 402/UE 404. The transmit and receive directions for the base station 402 may or may not be the same. The transmit and receive directions for the UE 404 may or may not be the same.

[0071] In response to different conditions, the UE 404 may decide to switch beams, for example, between beams 404a-404h. The beams at the UE 404 may be used for receiving downlink communications and/or transmitting uplink communications. In some examples, the base station 402 may send a transmission that triggers a beam switch by the UE 404. For example, the base station 402 may indicate a transmission configuration indication (TCI) state change, and in response, the UE 404 may switch to a new beam for the new TCI state of the base station 402. In some cases, the UE may receive a signal from the base station, for example, via a MAC control element (CE) command, configured to trigger a transmission configuration indication (TCI) state change. The TCI state change may cause the UE to find the best UE reception beam corresponding to the TCI state from the base station and switch to such beam. Switching beams may allow for enhanced or improved connectivity between the UE and the base station by ensuring that the transmitter and receiver use the same configured set of beams for communication.

[0072] The base station 402 and the UE 404 may each include multiple transmit receive points (TRPs). Each TRP may include a different RF module with a shared hardware and/or software controller. Each TRP may perform separate baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements.

[0073] A set of time and frequency resources that may be used for one or more transmissions of an SRS may be referred to as an "SRS resource set." In some communication systems, the SRS resource set applicability (i.e., what the SRS resource set is used for) for an SRS resource set may be configured by a higher layer parameter, such as a "use" associated with the SRS resource set, such as in an SRS-ResourceSet parameter. For example, the use may be configured as one of beam management, codebook (e.g., for codebook-based transmission), non-codebook (e.g., for non-codebook-based transmission), antenna switching, etc. Each SRS resource set may be composed of one or more SRS resources (e.g., up to 16). Each SRS resource set may be aperiodic, semi-persistent, or periodic.

[0074] In some wireless communication systems, two types of PUSCH transmission may be supported. The first type may be referred to as codebook-based transmission. For codebook-based transmission, the UE may be configured with one SRS resource set with "use" set to "codebook". For example, up to four SRS resources in the set may be configured for the UE. Each SRS resource may be radio resource control (RRC) configured with some number of ports, such as one or multiple ports. The SRS resource indicator (SRI) field in the UL DCI that schedules the PUSCH may indicate one SRS resource. The number of ports configured for the indicated SRS resource may determine the number of antenna ports for the PUSCH. The PUSCH may be transmitted with the same spatial domain filter (sometimes also referred to as "beam") as the indicated SRS resource. The number of layers (i.e., rank) for the scheduled PUSCH or the transmitted precoding matrix indicator (TPMI) (e.g., for the precoder) may be determined from a separate DCI field "precoding information and number of layers."

[0075] For non-codebook based transmission, the UE may be configured with one SRS resource set with "use" set to "non-codebook". For example, up to four SRS resources in the set may be configured for the UE. Each SRS resource may be RRC configured on one port. The SRI field in the UL DCI that schedules the PUSCH may indicate one or multiple SRS resources. The number of indicated SRS resources may determine the rank (i.e., number of layers) for the scheduled PUSCH. The PUSCH may be transmitted with the same precoder as the indicated SRS resource as well as the same spatial domain filter (i.e., beam).

[0076] In some aspects, multiple TRPs or panels may be used to improve reliability and robustness for the PUSCH. For example, if one link using a first TRP is blocked and one repetition of the PUSCH fails to be received, another repetition may be received and decoded by another TRP. Thus, with multiple TRPs, the diversity of transmission is increased and the PUSCH transmission may be more reliable. Repetitions may also be referred to as transmission occasions.

[0077] The PUSCH may be transmitted in one or more repetitions using different types of repetitions. For different PUSCH repetitions corresponding to the same TB (e.g., which may carry the same data), the repetitions are transmitted in different slots in type A repetitions, while the repetitions are transmitted in different minislots in type B repetitions. The number of repetitions may be RRC configured or may be indicated dynamically, such as by utilizing a time domain resource allocation (TDRA) field of the DCI. In some wireless communication systems, all repetitions may be transmitted on the same beam. For example, the SRI field of the DCI may apply to all repetitions. The SRI may be a field in the UL DCI that determines the power control parameters or beam for the PUSCH by pointing to one or more SRS resources in the SRS resource set.

[0078] In some other wireless communication systems, different PUSCH repetitions may be received at different TRPs, panels, or antennas at a network entity (e.g., a base station), and the repetitions may use the same beam or different beams. For example, there may be two sets of repetitions, each set having its own beam associated with its own power control parameters. Each set of repetitions may include one or more repetitions. Such two sets of repetitions may correspond to two SRS resource sets, which are associated with a DCI indicating the two sets of power control parameters and the two beams by indicating one or more SRS resources in each of the two SRS resource sets. Aspects herein enable an association between the two SRS resource sets and the two sets of PUSCH repetitions.

[0079] FIG. 5 is a diagram 500 illustrating communication between a UE 502 and a network entity 504 (e.g., a base station). As shown in FIG. 5, the network entity 504 may configure the UE 502 with at least two SRS resource sets 506. In some aspects, the network entity 504 may or may not support dynamic order switching. In some aspects, the SRS resource sets 506 may each have an SRS resource set identifier (ID), which may be represented by an srs-ResourceSetID field in the SRS-ResourceSet parameter. In some aspects, the SRS resource sets 506 may include a parameter representing an order, such as an SRS-ResourceSetOrder parameter. The network entity 504 may be a network node. The network node may be implemented as an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or the like. The network entities may be implemented in an aggregated or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, DU, RU, Near-Real-Time (Near-RT) RAN Intelligent Controller (RIC), or Non-Real-Time (Non-RT) RIC.

[0080] In some aspects, the network entity 504 may transmit a DCI 508 to the UE 502. In some aspects, dynamic order switching may be supported by the network entity 504. In some aspects, the DCI 508 may include one or more bits, such as two bits, to indicate an order for the SRS resource sets in the SRS resource set 506.

[0081] The UE 502 may transmit one or more repetitions of a PUSCH, such as a first PUSCH repetition 510, a second PUSCH repetition 512, a third PUSCH repetition 514, and a fourth PUSCH repetition 516, to the network entity 504. The one or more repetitions of the PUSCH may include repetitions of the same data or TB. In some aspects, within two SRS resource sets in the SRS resource set 506, the SRS resource set with the lowest ID may correspond to the first set of repetitions (the first one may be the one that appears first in time), and the SRS resource set with the second lowest ID corresponds to the second set of repetitions. For example, the first set of PUSCH repetitions may include a first PUSCH repetition 510 and a second PUSCH repetition 512, and the second set of PUSCH repetitions may include a third PUSCH repetition 514 and a fourth PUSCH repetition 516. The first set of PUSCH repetitions may correspond to the SRS resource set with the lowest ID. In some aspects, the first set of time repetitions of the PUSCH may be transmitted on a first beam associated with the first SRS resource set, and power control for the PUSCH may be based on an SRI associated with the first SRS resource set, and the second set of time repetitions of the PUSCH may be transmitted on a second beam associated with the second SRS resource set, and power control for the PUSCH may be based on an SRI associated with the second SRS resource set. In some aspects, the first set of PUSCH repetitions may be transmitted using the same beam (first beam) as the first SRS resource set (which may also be referred to as a "spatial domain filter"). In some aspects, the second set of PUSCH repetitions may be transmitted using the same beam (second beam) as the second SRS resource set (which may also be referred to as a "spatial domain filter").

[0082] In some aspects, the first and second sets of repetitions may be transmitted on beams selected for transmission to the first and second TRPs, panels, or antennas of the network entity 504, respectively. If the link to the first TRP is blocked, the first set of repetitions may fail to be received by the network entity 504. However, the network entity 504 may still receive the data because the data is also sent to the second TRP in the second set of repetitions. Thus, the diversity of the transmission is increased and the PUSCH transmission may be more reliable.

[0083] In some aspects, among the two SRS resource sets in the SRS resource set 506, the SRS resource set with the highest ID may correspond to the first set of repetitions, and the SRS resource set with the second highest ID may correspond to the second set of repetitions. For example, the first set of PUSCH repetitions may include the first PUSCH repetition 510 and the second PUSCH repetition 512, and the second set of PUSCH repetitions may include the third PUSCH repetition 514 and the fourth PUSCH repetition 516. The first set of PUSCH repetitions may correspond to the SRS resource set with the highest ID. In some aspects, the SRS resource sets associated with the first PUSCH repetition 510, the second PUSCH repetition 512, the third PUSCH repetition 514, and the fourth PUSCH repetition 516 may be determined based on a parameter representing an order. By using such an order, the SRS resource set and the SRI or TRP associated with the SRS resource set (which may be used for power control of PUSCH repetition) may be indicated to the UE 502, so that the UE may be aware of which TRP and power control to use for PUSCH repetition.

[0084] In some aspects, if dynamic order switching is supported by the network entity 504 and the DCI 508 includes one or more bits representing an order, the one or more bits may represent a DCI code point that may correspond to the order. For example, the DCI code point may be 0, 1, 2, or 3 and may be associated with orders 1, 2, 12, and 21. Order 1 may be based on the SRS resource set with the lowest ID being compatible with the first TRP (e.g., this may be in a single TRP mode and the second SRS resource set may be unused). Order 2 may be based on the SRS resource set with the second lowest ID being compatible with the second TRP (e.g., this may be in a single TRP mode and the first SRS resource set may be unused). Order 12 may be based on the SRS resource set with the lowest ID being compatible with the first TRP and the SRS resource set with the second lowest ID being compatible with the second TRP. The order 21 may be based on the SRS resource set with the lowest ID corresponding to the second TRP and the SRS resource set with the second lowest ID corresponding to the first TRP. Each SRS resource set may be associated with a beam and an SRI that may be used for power control in the PUSCH repetition. The DCI may include an order associating the SRS resource set with the PUSCH repetition, which may associate the PUSCH repetition with the beam or SRS associated with the SRS resource set. Table 1 shows an example correspondence between a set of DCI code points and a corresponding set of relationships indicating an order for the SRS resource sets.

[0085] FIG. 6 is a diagram 600 illustrating an example cyclical mapping pattern for PUSCH repetitions. As shown in FIG. 6, a DCI 602 may schedule four PUSCH repetitions, PUSCH repetition 604, PUSCH repetition 606, PUSCH repetition 608, and PUSCH repetition 610. For cyclical beam mapping, the first PUSCH repetition 604 and the third PUSCH repetition 608 may be associated with a first beam and a first set of power control parameters. The second PUSCH repetition 606 and the fourth PUSCH repetition 610 may be associated with a second beam and a second set of power control parameters. The cyclical mapping pattern may be applicable for both Type A and Type B repetitions.

[0086] FIG. 7 is a diagram 700 illustrating an example sequential mapping pattern for PUSCH repetitions. As shown in FIG. 7, a DCI 702 may schedule four PUSCH repetitions, a first PUSCH repetition 704, a second PUSCH repetition 706, a third PUSCH repetition 708, and a fourth PUSCH repetition 710. For sequential beam mapping, the first PUSCH repetition 704 and the second PUSCH repetition 706 may be associated with a first beam and a first set of power control parameters. The third PUSCH repetition 708 and the fourth PUSCH repetition 710 may be associated with a second beam and a second set of power control parameters. The sequential mapping pattern may be applicable for both Type A and Type B repetitions.

[0087] FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 404, UE 502, device 902).

[0088] At 802, the UE may receive a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam. For example, the UE 502 may receive a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam in the SRS resource set 506 from the network entity 504. In some aspects, 802 may be implemented by the SRS configuration component 940 in FIG. 9, or the SRS component 198. In some aspects, the configuration includes an SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.

[0089] At 804, the UE may receive a DCI for UL transmission from a network entity (e.g., a base station or a component of a base station), the DCI indicating a first SRS resource set and a second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. For example, the UE 502 may receive a DCI 508 for UL transmission from the network entity 504, the DCI 508 indicating a first SRS resource set and a second SRS resource set. In some aspects, 804 may be implemented by the DCI component 942 in FIG. 9, or the SRS component 198. In some aspects, the DCI does not indicate support for dynamic order switching. In some aspects, the DCI indicates support for dynamic order switching. In some aspects, the information in the DCI may include one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set. In some aspects, the DCI indicates a first SRI for the first set of repetitions and a second SRI for the second set of repetitions.

At 806, the UE may transmit to a network entity (e.g., a base station or a component of a base station) a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. For example, the UE 502 may transmit to the network entity 504 a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. For example, the first set of repetitions may include one or more of PUSCH repetitions 510, 512, 514, and 516, and the second set of repetitions may include one or more of PUSCH repetitions 510, 512, 514, and 516. In some aspects, 806 may be implemented by the PUSCH component 944 in FIG. 9, or the SRS component 198. In some aspects, the order is based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set and is received in the configuration. In some aspects, the first SRS resource set ID is a lower number between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the first SRS resource set ID is a higher number between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the ordering rule indicates that an SRS resource set with a lower SRS resource set ID is later in time. In some aspects, the ordering rule indicates that an SRS resource set with a higher SRS resource set ID is later in time. In some aspects, the UE transmits a first set of repetitions with a first set of power control parameters and transmits a second set of repetitions with a second set of power control parameters. In some aspects, the first set of repetitions is associated with a first antenna at the network entity and the second set of repetitions is associated with a second antenna at the network entity.

[0091] FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902. The apparatus 902 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2304 may include a cellular baseband processor 924 (also referred to as a modem) coupled to one or more transceivers 922 (e.g., cellular RF transceivers). The cellular baseband processor 924 may include on-chip memory 924'. In some aspects, the apparatus 902 may further include one or more subscriber identity module (SIM) cards 920 and an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910. The application processor 906 may include on-chip memory 906'. In some aspects, the device 902 may further include a Bluetooth module 912, a WLAN module 914, an SPS module 916 (e.g., a GNSS module), one or more sensor modules 918 (e.g., motion sensors such as a barometric sensor/altimeter, an inertial management unit (IMU), a gyroscope, and/or an accelerometer(s), light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), acoustic navigation and ranging (SONAR), magnetometer, audio, and/or other technologies used for positioning), additional memory module 926, a power source 930, and/or a camera 932. The Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include their own dedicated antennas and/or utilize antennas 980 for communication. The cellular baseband processor 924 communicates with the UE 104 and/or with RUs associated with the network entity 904 through the transceiver(s) 922 via one or more antennas 980. The cellular baseband processor 924 and the application processor 906 may each include a computer-readable medium/memory 924', 906', respectively. The additional memory module 926 may also be considered a computer-readable medium/memory. Each computer-readable medium/memory 924', 906', 926 may be non-transitory. The cellular baseband processor 924 and the application processor 906 are each responsible for general processing, including the execution of software stored in the computer-readable medium/memory. The software, when executed by the cellular baseband processor 924/application processor 906, causes the cellular baseband processor 924/application processor 906 to perform the various functions described above. The computer-readable medium/memory may also be used to store data that is manipulated by the cellular baseband processor 924/application processor 906 when executing the software. The cellular baseband processor 924/application processor 906 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the device 902 is a processor chip (modem and/or application) and may include just the cellular baseband processor 924 and/or the application processor 906, and in another configuration, the device 902 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the device 902. In some aspects, the SRS component 198 may be configured to receive a configuration of a first SRS resource set and a second SRS resource set. In some aspects, the SRS component 198 may be further configured to receive a DCI for an UL transmission from a network entity, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. In some aspects, the SRS component 198 may be further configured to transmit to the network entity a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The SRS component 198 may include an SRS configuration component 940 that may be configured to receive a configuration of a first SRS resource set and a second SRS resource set, e.g., as described with respect to 802 in FIG. 8. The SRS component 198 may further include a DCI component 942 that may be configured to receive a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station), e.g., as described with respect to 804 in FIG. 8, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The SRS component 198 may further include a PUSCH component 944 that may be configured to transmit a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI that schedules the UL transmission, for example, as described with respect to 806 in FIG. 8 to a network entity (e.g., a base station or a component of a base station).

[0092] The apparatus may include additional components that implement each of the blocks of the algorithm in the flowchart of FIG. 9. Thus, each block in the flowchart of FIG. 9 may be implemented by one component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process/algorithm, implemented by a processor configured to perform the described process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0093] As shown, the apparatus 902 may include various components configured for various functions. In one configuration, the apparatus 902, and in particular the cellular baseband processor 924, may include means for receiving a configuration of a first SRS resource set and a second SRS resource set. The cellular baseband processor 924 may further include means for receiving a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The cellular baseband processor 924 may further include means for transmitting, to a network entity (e.g., a base station or a component of a base station), a first set of repetitions of the PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The means may be one or more of the components of the device 902 configured to perform the functions recited by the means. As described above, the device 902 may include the TX processor 368, the RX processor 356, and the controller/processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the means.

[0094] FIG. 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a network entity, such as a base station (e.g., base station 102/180, base station 402, network entity 504, network entity 1302, or network entity 1460, device 1102).

[0095] At 1002, a network entity may transmit a configuration of a first SRS resource set and a second SRS resource set. For example, the network entity 504 may transmit to the UE 502 a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam in the SRS resource set 506. In some aspects, 1002 may be implemented by the SRS configuration component 1140 in FIG. 11, or the SRS component 199. In some aspects, the configuration includes an SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.

[0096] At 1004, the network entity may transmit, for the UE, a DCI for UL transmission, where the DCI indicates a first SRS resource set and a second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. For example, the network entity 504 may transmit, for the UE 502, a DCI for UL transmission, where the DCI indicates a first SRS resource set and a second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. In some aspects, 1004 may be implemented by the DCI component 1142 in FIG. 11, or the SRS component 199. In some aspects, the DCI does not indicate support for dynamic order switching. In some aspects, the DCI indicates support for dynamic order switching. In some aspects, the information in the DCI may include one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set. In some aspects, the DCI indicates a first SRI for the first set of repetitions and a second SRI for the second set of repetitions.

[0097] At 1006, the network entity may receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. For example, the network entity 504 may receive from the UE 502 a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. For example, the first set of repetitions may include one or more of PUSCH repetitions 510, 512, 514, and 516, and the second set of repetitions may include one or more of PUSCH repetitions 510, 512, 514, and 516. In some aspects, 1006 may be implemented by the PUSCH component 1144 in FIG. 11, or the SRS component 199. In some aspects, the order is received in the configuration based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set. In some aspects, the first SRS resource set ID is a lower number between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the first SRS resource set ID is a higher number between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the ordering rule indicates that an SRS resource set with a lower SRS resource set ID is later in time. In some aspects, the ordering rule indicates that an SRS resource set with a higher SRS resource set ID is later in time. In some aspects, the UE transmits a first set of repetitions with a first set of power control parameters and transmits a second set of repetitions with a second set of power control parameters. In some aspects, the first set of repetitions is associated with a first antenna at the base station and the second set of repetitions is associated with a second antenna at the base station.

[0098] FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1102. The apparatus 1102 may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the apparatus 1102 may include a baseband unit 1104. The baseband unit 1104 may communicate with the UE 104 through a cellular RF transceiver 1122. The baseband unit 1104 may include a computer-readable medium/memory. The baseband unit 1104 is responsible for general processing, including the execution of software stored in the computer-readable medium/memory. The software, when executed by the baseband unit 1104, causes the baseband unit 1104 to perform the various functions described above. The computer-readable medium/memory may also be used to store data that is manipulated by the baseband unit 1104 when executing the software. The baseband unit 1104 further includes a receiving component 1130, a communications manager 1132, and a transmitting component 1134. The communications manager 1132 includes one or more of the illustrated components. The components in the communications manager 1132 may be stored in a computer-readable medium/memory and/or configured as hardware in the baseband unit 1104. The baseband unit 1104 may be a component of the base station 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

[0099] The communications manager 1132 may include an SRS configuration component 1140 that may transmit a configuration of the first SRS resource set and the second SRS resource set, e.g., as described with respect to 1002 in FIG. 10. The communications manager 1132 may further include a DCI component 1142 that may transmit a DCI for an UL transmission, e.g., as described with respect to 1004 in FIG. 10, for the UE, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The communications manager 1132 may further include a PUSCH component 1144 that may receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, for example, as described with respect to 1006 in FIG. 10.

[0100] The apparatus may include additional components that implement each of the blocks of the algorithm in the flowchart of FIG. 10. Thus, each block in the flowchart of FIG. 10 may be implemented by one component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process/algorithm, implemented by a processor configured to perform the described process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0101] As shown, the apparatus 1102 may include various components configured for various functions. In one configuration, the apparatus 1102, and in particular the baseband unit 1104, may include means for transmitting a configuration of a first SRS resource set and a second SRS resource set. The baseband unit 1104 may further include means for transmitting, for a UE, a DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The baseband unit 1104 may further include means for receiving a first set of repetitions of the PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The means may be one or more of the components of the device 1102 configured to perform the functions recited by the means. As described above, the device 1102 may include the TX processor 316, the RX processor 370, and the controller/processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller/processor 375 configured to perform the functions recited by the means.

[0102] Figure 12 shows a diagram illustrating an example disaggregated base station 1200 architecture. The disaggregated base station 1200 architecture may include one or more central units (CUs) 1210 that may communicate directly with the core network 1220 over a backhaul link or indirectly with the core network 1220 through one or more disaggregated base station units (such as a Near-RT RAN Intelligent Controller (RIC) 1225 over an E2 link, or a Non-RT RIC 1215 associated with a Service Management and Orchestration (SMO) framework 1205, or both). The CUs 1210 may communicate with one or more distributed units (DUs) 1230 over respective midhaul links, such as an F1 interface. The DU 1230 may communicate with one or more radio units (RUs) 1240 via respective fronthaul links. The RUs 1240 may communicate with respective UEs 1222 via one or more radio frequency (RF) access links. In some implementations, a UE 1222 may be served by multiple RUs 1240 simultaneously. In some aspects, the network entity 504 or base station 102/180 may be implemented based on the disaggregated base station 1200 architecture. In some aspects, the UE 1222 may correspond to a UE 104 or a UE 502.

[0103] Each of the units, i.e., CU1210, DU1230, RU1240, and Near-RT RIC1225, Non-RT RIC1215, and SMO Framework1205, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. The units may be collectively referred to as "network entities." Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals to one or more of the other units, or both, over a wireless transmission medium.

[0104] In some aspects, the CU 1210 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1210. The CU 1210 may be configured to handle user plane functions (i.e., Central Unit - User Plane (CU-UP)), control plane functions (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 1210 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 1210 may be implemented to communicate with the DU 1230 for network control and signaling, as necessary.

[0105] The DU 1230 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 1240. In some aspects, the DU 1230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split, such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 1230 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1230 or with control functions hosted by the CU 1210.

[0106] Lower layer functions may be implemented by one or more RUs 1240. In some deployments, the RUs 1240, controlled by the DU 1230, may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing Fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU(s) 1240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 1222. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 1240 may be controlled by the corresponding DU 1230. In some scenarios, this configuration may enable the DU(s) 1230 and CU 1210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0107] The SMO framework 1205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1205 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 1205 may be configured to interact with a cloud computing platform (such as an Open Cloud (O-Cloud) 1290) to perform network element lifecycle management (such as to instantiate a virtualized network element) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, a CU 1210, a DU 1230, an RU 1240, and a Near-RT RIC 1225. In some implementations, the SMO framework 1205 can communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1211, over an O1 interface. Additionally, in some implementations, the SMO framework 1205 can communicate directly with one or more RUs 1240 over an O1 interface. The SMO framework 1205 can also include a Non-RT RIC 1215 configured to support the functionality of the SMO framework 1205.

[0108] The Non-RT RIC 1215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 1225. The Non-RT RIC 1215 may be coupled to or in communication with the Near-RT RIC 1225 (e.g., via an A1 interface). The Near-RT RIC 1225 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and action on interfaces (e.g., via an E2 interface) that connect one or more CUs 1210, one or more DUs 1230, or both, and O-eNBs with the Near-RT RIC 1225.

[0109] In some implementations, the Non-RT RIC 1215 may receive parameters or external enrichment information from an external server to generate the AI/ML model to be deployed in the Near-RT RIC 1225. Such information may be utilized by the Near-RT RIC 1225 and may be received in the SMO framework 1205 or the Non-RT RIC 1215 from a non-network data source or from a network function. In some examples, the Non-RT RIC 1215 or the Near-RT RIC 1225 may be configured to adjust RAN behavior or performance. For example, the Non-RT RIC 1215 may monitor long-term trends and patterns in performance and employ the AI/ML model to take corrective action through the SMO framework 1205 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0110] FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for a network entity 1302. The network entity 1302 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1302 may include at least one of a CU 1310, a DU 1330, or an RU 1340. For example, depending on the layer functionality handled by the SRS component 199, the network entity 1302 may include a CU 1310, both a CU 1310 and a DU 1330, each of a CU 1310, a DU 1330, and a RU 1340, a DU 1330, both a DU 1330 and a RU 1340, or an RU 1340. The CU 1310 may include a CU processor 1312. The CU processor 1312 may include an on-chip memory 1312'. In some aspects, the CU 1310 may further include an additional memory module 1314 and a communication interface 1318. The CU 1310 communicates with the DU 1330 over a midhaul link, such as an F1 interface. The DU 1330 may include a DU processor 1332. The DU processor 1332 may include an on-chip memory 1332'. In some aspects, the DU 1330 may further include an additional memory module 1334 and a communication interface 1338. The DU 1330 communicates with the RU 1340 over a fronthaul link. The RU 1340 may include an RU processor 1342. The RU processor 1342 may include an on-chip memory 1342'. In some aspects, the RU 1340 may further include an additional memory module 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348. The RU 1340 communicates with the UE 104. The on-chip memories 1312', 1332', 1342' and the additional memory modules 1314, 1334, 1344 may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the processors 1312, 1332, 1342 is responsible for general processing, including the execution of software stored in the computer-readable medium/memory. The software, when executed by the corresponding processor(s), causes the processor(s) to perform the various functions described above. The computer-readable medium/memory may also be used to store data that is manipulated by the processor(s) when executing the software.

[0111] As described above, the SRS component 199 may be configured to transmit a configuration of a first SRS resource set associated with a first beam and a second SRS resource set associated with a second beam. In some aspects, the SRS component 199 may be further configured to transmit a DCI for an UL transmission for the UE, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with the first beam and the second SRS resource set is associated with the second beam. In some aspects, the SRS component 199 may be further configured to receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The SRS component 199 may be within one or more processors of one or more of the CU 1310, DU 1330, and RU 1340. The SRS component 199 may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by one or more processors configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1302 may include various components configured for various functions. In one configuration, the network entity 1302 includes means for transmitting a configuration of a first SRS resource set and a second SRS resource set. The network entity 1302 may further include means for transmitting a DCI for an UL transmission for the UE, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The network entity 1302 may further include means for receiving a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The means may be an SRS component 199 of the network entity 1302 configured to perform the functions recited by the means. As described above, the network entity 1302 may include a TX processor 316, an RX processor 370, and a controller/processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.

[0112] FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a network entity 1460. In one example, the network entity 1460 may be in the core network 120. The network entity 1460 may include a network processor 1412. The network processor 1412 may include an on-chip memory 1412'. In some aspects, the network entity 1460 may further include an additional memory module 1414. The network entity 1460 communicates with the CU 1402 via a network interface 1480, either directly (e.g., a backhaul link) or indirectly (e.g., through a RIC). The on-chip memory 1412' and the additional memory module 1414 may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. The processor 1412 is responsible for general processing, including the execution of software stored in the computer-readable medium/memory. The software, when executed by the corresponding processor(s), causes the processor(s) to perform the various functions described above. The computer-readable medium/memory may also be used to store data that is manipulated by the processor(s) when executing the software.

[0113] As described above, the SRS component 199 may be configured to transmit a configuration of a first SRS resource set and a second SRS resource set. In some aspects, the SRS component 199 may be further configured to transmit a DCI for an UL transmission for the UE, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. In some aspects, the SRS component 199 may be further configured to receive a first set of repetitions of the PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The SRS component 199 may be within the processor 1412. The SRS component 199 may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by one or more processors configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1460 may include various components configured for various functions. In one configuration, the network entity 1460 includes means for transmitting a configuration of a first SRS resource set and a second SRS resource set. The network entity 1460 may further include means for transmitting a DCI for an UL transmission for a UE, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam. The network entity 1460 may further include means for receiving a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission. The means may be an SRS component 199 of the network entity 1460 configured to perform the functions recited by the means.

[0114] It is understood that the particular order or hierarchy of the blocks in the disclosed processes/flowcharts is an example of an example approach. Based on design preferences, it is understood that the particular order or hierarchy of the blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in an example order and are not limited to the particular order or hierarchy presented.

[0115] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects set forth herein, but are to be accorded the full scope consistent with the claim language, in which reference to an element in the singular does not mean "one and only," unless so expressly stated, but rather means "one or more." Terms such as "if," "when," and "while" should be construed to mean "under the condition that," rather than implying an immediate time relationship or reaction. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but merely imply that if a condition is met, an action occurs, but does not require a specific or immediate time constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and/or C, and may include multiple A, multiple B, or multiple C. In particular, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or that later become known to those of skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is made public, regardless of whether such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no claim element should be construed as a means plus function unless the element is expressly recited using the phrase "means for."

[0116] The following aspects are exemplary only and may be combined with, but not limited to, other aspects or teachings described herein.

[0117] Aspect 1 is an apparatus for wireless communications in a UE, comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured to: receive a configuration of a first SRS resource set and a second SRS resource set; receive a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station); and transmit a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission to the network entity (e.g., a base station or a component of a base station), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0118] Aspect 2 is the apparatus of aspect 1, in which the order is received in a configuration based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set.

[0119] Aspect 3 is the apparatus of any of aspects 1 to 2, in which the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID being either a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

[0120] Aspect 4 is the apparatus of any of aspects 1 to 2, in which the first beam and the second beam are selected to transmit to different transmitting/receiving points, antenna panels, or antennas of the network entity.

[0121] Aspect 5 is the apparatus of any of aspects 1 to 4, wherein the configuration includes an SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.

[0122] Aspect 6 is the apparatus of any of aspects 1 to 5, wherein the same data or transport block is transmitted on each repetition.

[0123] Aspect 7 is the apparatus of any one of aspects 1 to 5, in which the DCI indicates support for dynamic order switching.

[0124] Aspect 8 is the apparatus of any of aspects 1 to 7, wherein the information in the DCI comprises one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set.

[0125] Aspect 9 is the apparatus of any of aspects 1 to 8, wherein the ordering rule indicates that an SRS resource set with a lower SRS resource set ID is later in time.

[0126] Aspect 10 is the apparatus of any of aspects 1 to 8, wherein the ordering rule indicates that an SRS resource set with a higher SRS resource set ID is later in time.

[0127] Aspect 11 is the apparatus of any of aspects 1 to 10, wherein the UE transmits a first set of repetitions with a first set of power control parameters and transmits a second set of repetitions with a second set of power control parameters.

[0128] Aspect 12 is the apparatus of any of aspects 1 to 11, in which the DCI indicates a first SRI for a first set of repetitions and a second SRI for a second set of repetitions.

[0129] Aspect 13 is the apparatus of any of aspects 1 to 12, wherein a first set of repetitions is associated with a first antenna at a network entity (e.g., a base station or a component of a base station) and a second set of repetitions is associated with a second antenna at the network entity.

[0130] Aspect 14 is the apparatus of any one of aspects 1 to 13, further comprising a transceiver or antenna coupled to the at least one processor.

[0131] Aspect 15 is an apparatus for wireless communications in a network entity (e.g., a base station or a component of a base station), comprising: a memory; and at least one processor coupled to the memory, wherein, based at least in part on information stored in the memory, the at least one processor is configured to cause the apparatus to: transmit a configuration of a first SRS resource set and a second SRS resource set; transmit a DCI for an UL transmission for the UE; and receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0132] Aspect 16 is the apparatus of aspect 15, wherein the order is received in a configuration based on a first SRS resource set ID associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set.

[0133] Aspect 17 is the apparatus of any of aspects 15 to 16, in which the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID being either a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

[0134] Aspect 18 is the apparatus of any of aspects 15 to 16, wherein the first beam and the second beam correspond to different transmitting/receiving points, antenna panels, or antennas of the network entity.

[0135] Aspect 19 is the apparatus of any of aspects 15 to 18, wherein the configuration includes an SRS resource set order representing an order between the first SRS resource set and the second SRS resource set.

[0136] Aspect 20 is the apparatus of any of aspects 15 to 19, wherein the same data or transport block is transmitted on each repetition.

[0137] Aspect 21 is the apparatus of any of aspects 15 to 19, wherein the DCI indicates support for dynamic order switching.

[0138] Aspect 22 is the apparatus of any of aspects 15 to 21, wherein the information in the DCI comprises one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set.

[0139] Aspect 23 is the apparatus of any of aspects 15 to 22, wherein the ordering rule indicates that an SRS resource set with a lower SRS resource set ID is later in time.

[0140] Aspect 24 is the apparatus of any of aspects 15 to 22, wherein the ordering rule indicates that an SRS resource set with a higher SRS resource set ID is later in time.

[0141] Aspect 25 is the apparatus of any of aspects 15 to 24, in which a network entity (e.g., a base station or a component of a base station) receives a first set of repetitions with a first set of power control parameters and receives a second set of repetitions with a second set of power control parameters.

[0142] Aspect 26 is the apparatus of any of aspects 15 to 25, wherein the DCI indicates a first SRI for a first set of repetitions and a second SRI for a second set of repetitions.

[0143] Aspect 27 is the apparatus of any of aspects 15 to 26, in which the first set of repetitions is associated with a first antenna at a network entity (e.g., a base station or a component of a base station) and the second set of repetitions is associated with a second antenna at the network entity (e.g., a base station or a component of a base station).

[0144] Aspect 28 is the apparatus of any of aspects 15 to 27, further comprising a transceiver coupled to the at least one processor.

[0145] Aspect 29 is a method of wireless communication in a UE, comprising: receiving a configuration of a first SRS resource set and a second SRS resource set; receiving a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station); and transmitting a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set to the network entity (e.g., a base station or a component of a base station), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam, in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.

[0146] Aspect 30 is the method of aspect 29, further comprising a method for implementing any of aspects 1 to 14.

[0147] Aspect 31 is an apparatus for wireless communication in a UE, comprising: means for receiving a configuration of a first SRS resource set and a second SRS resource set; means for receiving a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station); and means for transmitting a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set to a network entity (e.g., a base station or a component of a base station) in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0148] Aspect 32 is an apparatus for wireless communication as described in aspect 31, further comprising means for implementing any of aspects 1 to 14.

[0149] Aspect 33 is a computer-readable medium storing computer-executable code in a UE, which when executed by a processor causes the processor to receive a configuration of a first SRS resource set and a second SRS resource set, receive a DCI for an UL transmission from a network entity (e.g., a base station or a component of a base station), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam, and transmit a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.

[0150] Aspect 34 is a computer-readable medium according to aspect 33, the code, when executed by a processor, causing the processor to implement any of aspects 1 to 14.

[0151] Aspect 35 is a method of wireless communication in a network entity (e.g., a base station or a component of a base station), comprising: transmitting a configuration of a first SRS resource set and a second SRS resource set; transmitting, for a UE, a DCI for an UL transmission; and receiving a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0152] Aspect 36 is the method of aspect 35, further comprising a method for implementing any of aspects 15 to 28.

[0153] Aspect 37 is an apparatus for wireless communication in a network entity (e.g., a base station or a component of a base station), comprising: means for transmitting a configuration of a first SRS resource set and a second SRS resource set; means for transmitting, for a UE, a DCI for an UL transmission; and means for receiving a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0154] Aspect 38 is an apparatus for wireless communication as described in aspect 37, further comprising means for implementing any of aspects 15 to 28.

[0155] Aspect 39 is a computer-readable medium storing computer-executable code in a network entity (e.g., a base station or a component of a base station), which when executed by a processor causes the processor to: transmit a configuration of a first SRS resource set and a second SRS resource set; transmit a DCI for an UL transmission for the UE; and receive a first set of PUSCH repetitions based on the first SRS resource set and a second set of PUSCH repetitions based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission, where the DCI indicates the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam.

[0156] Aspect 40 is a computer-readable medium according to aspect 39, the code of which, when executed by a processor, causes the processor to implement any of aspects 15 to 28.

Claims (30)

An apparatus for wireless communication in a user equipment (UE), comprising:
Memory,
at least one processor coupled to the memory;
and based at least in part on the information stored in the memory, the at least one processor causes the apparatus to:
receiving a configuration of a first sounding reference signal (SRS) resource set and a second SRS resource set;
receiving downlink control information (DCI) for uplink (UL) transmission from a network entity, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam;
transmitting, to the network entity, a first set of repetitions of a physical uplink shared channel (PUSCH) based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission;
An apparatus configured to cause the order is based on a first SRS resource set identifier (ID) associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set;
The apparatus of claim 1 , wherein the order is received in the configuration. The apparatus of claim 2, wherein the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID being either a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID. The device of claim 1, wherein the first beam and the second beam are selected to transmit to different transmitting/receiving points, antenna panels, or antennas of the network entity. The apparatus of claim 1, wherein the configuration includes an SRS resource set order representing the order between the first SRS resource set and the second SRS resource set. The apparatus of claim 1, wherein the same data or transport block is transmitted on each repetition. The device of claim 1, wherein the DCI indicates support for dynamic order switching. The apparatus of claim 1, wherein the information in the DCI comprises one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set. The apparatus of claim 8, wherein the ordering rule indicates that an SRS resource set with a lower SRS resource set identifier (ID) is later in time. The apparatus of claim 8, wherein the ordering rule indicates that an SRS resource set with a higher SRS resource set identifier (ID) is later in time. The apparatus of claim 1, wherein the UE transmits the first set of repetitions with a first set of power control parameters and transmits the second set of repetitions with a second set of power control parameters. The apparatus of claim 1, wherein the DCI indicates a first SRS resource indicator (SRI) for the first set of repetitions and a second SRI for the second set of repetitions. The apparatus of claim 1, wherein the first set of repetitions is associated with a first antenna at the network entity, and the second set of repetitions is associated with a second antenna at the network entity. The device of claim 1, further comprising a transceiver or antenna coupled to the at least one processor. An apparatus for wireless communication in a network entity, comprising:
Memory,
at least one processor coupled to the memory;
and based at least in part on the information stored in the memory, the at least one processor causes the apparatus to:
transmitting a configuration of a first sounding reference signal (SRS) resource set and a second SRS resource set;
transmitting downlink control information (DCI) for an uplink (UL) transmission to a user equipment (UE), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam;
receiving a first set of repetitions of a physical uplink shared channel (PUSCH) based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission;
An apparatus configured to cause the order is based on a first SRS resource set identifier (ID) associated with the first SRS resource set and a second SRS resource set ID associated with the second SRS resource set;
The apparatus of claim 15 , wherein the order is received in the configuration. The apparatus of claim 16, wherein the order specifies that the first SRS resource set is earlier in time based on the first SRS resource set ID being either a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID. The apparatus of claim 16, wherein the first beam and the second beam correspond to different transmitting/receiving points, antenna panels, or antennas of the network entity. The apparatus of claim 15, wherein the configuration includes an SRS resource set order representing the order between the first SRS resource set and the second SRS resource set. The apparatus of claim 15, wherein the same data or transport block is transmitted on each repetition. The device of claim 15, wherein the DCI indicates support for dynamic order switching. The apparatus of claim 15, wherein the information in the DCI comprises one or more bits indicating an ordering rule associated with the first SRS resource set and the second SRS resource set. 23. The apparatus of claim 22, wherein the ordering rule indicates that an SRS resource set with a lower SRS resource set identifier (ID) is later in time. 23. The apparatus of claim 22, wherein the ordering rule indicates that an SRS resource set with a higher SRS resource set identifier (ID) is later in time. 16. The apparatus of claim 15, wherein the network entity receives the first set of repetitions in a first set of power control parameters and receives the second set of repetitions in a second set of power control parameters. The apparatus of claim 15, wherein the DCI indicates a first SRS resource indicator (SRI) for the first set of repetitions and a second SRI for the second set of repetitions. The apparatus of claim 15, wherein the first set of repetitions is associated with a first antenna at the network entity, and the second set of repetitions is associated with a second antenna at the network entity. The apparatus of claim 15, further comprising a transceiver coupled to the at least one processor. 1. A method of wireless communication in a user equipment (UE), comprising:
receiving a configuration of a first sounding reference signal (SRS) resource set and a second SRS resource set;
receiving downlink control information (DCI) for uplink (UL) transmission from a network entity, the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam;
transmitting, to the network entity, a first set of repetitions of a physical uplink shared channel (PUSCH) based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission;
A method comprising: 1. A method for wireless communication in a network entity, comprising:
transmitting a configuration of a first sounding reference signal (SRS) resource set and a second SRS resource set;
transmitting downlink control information (DCI) for an uplink (UL) transmission to a user equipment (UE), the DCI indicating the first SRS resource set and the second SRS resource set, where the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam;
receiving a first set of repetitions of a physical uplink shared channel (PUSCH) based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission;
A method comprising:

Images