CN117242734A - SRS resource set and beam order association for multi-beam PUSCH - Google Patents

Abstract

Methods, apparatuses, and computer-readable storage media for PUSCH repetition and SRS resource aggregation are provided. An example method includes receiving a configuration of a first set of SRS resources and a second set of SRS resources. The exemplary method further comprises: a DCI for UL transmission is received from a network entity, the DCI indicating a first set of SRS resources and a second set of SRS resources. The first/second SRS resource sets are associated with the first/second beams, respectively. The example method further includes: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are transmitted to the network entity 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 of the scheduled UL transmission.

Description

SRS resource set and beam order association for multi-beam PUSCH

Cross Reference to Related Applications

The present application claims the benefits and priorities of U.S. provisional application Ser. No. 63/185,919 entitled "SRS REOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH" filed 5/7/2021 and U.S. non-provisional patent application Ser. No. 17/662,222 entitled "SRS REOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH", filed 5/2022, which are expressly incorporated herein by reference in their entirety.

Technical Field

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems having Sounding Reference Signals (SRS), downlink Control Information (DCI), and physical Uplink (UL) shared channels (PUSCH).

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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.

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunications standard is 5G New Radio (NR). The 5G NR is part of the continuous mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)) and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine type communication (emtc), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements may also be applicable to other multiple access techniques and telecommunication standards employing these techniques.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor 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 that is presented later. In some wireless communication systems, different Physical Uplink Shared Channel (PUSCH) repetitions are intended to be received at different Transmit Receive Points (TRPs), panels, or antennas at the base station, and the repetitions may use the same beam or different beams. For example, two sets of repetitions may be provided, each set of repetitions including its own beam associated with its own power control parameters. Each repetition set may include one or more repetitions. Such two repeated sets may correspond to two SRS resource sets, which may include DCI that may indicate two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets. Aspects herein enable association between two SRS resource sets and two PUSCH repetition sets, facilitating more efficient PUSCH transmissions.

In one aspect of the disclosure, a method, computer-readable medium, and apparatus at a User Equipment (UE) are provided. An apparatus may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to receive a configuration of the first set of SRS resources and the second set of SRS resources. 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), DCI for UL transmission, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. The memory and the at least one processor coupled to the memory may be further configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are transmitted to the network entity 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 of the scheduled UL transmission.

In another aspect of the disclosure, a method, computer-readable medium, and apparatus at a network entity (e.g., a base station or a component of a base station) are provided. An 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 the first set of SRS resources and the second set of SRS resources. The memory and the at least one processor coupled to the memory may be further configured to: a DCI for UL transmission is transmitted for a UE, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. The memory and the at least one processor coupled to the memory may be further configured to receive a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information transmitted in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling UL transmissions.

To the accomplishment of the foregoing and related ends, 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 various aspects may be employed and the description is intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is a diagram showing an example of a wireless communication system and an access network.

Fig. 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

Fig. 2B is a diagram illustrating an example of DL channels within a subframe according to aspects of the present disclosure.

Fig. 2C is a diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.

Fig. 2D is a diagram illustrating an example of UL channels within a subframe according to aspects of the present disclosure.

Fig. 3 is a diagram showing an example of a base station and a User Equipment (UE) in an access network.

Fig. 4 is a diagram illustrating a base station in communication with a UE.

Fig. 5 is a diagram illustrating communication between a UE and a network entity.

Fig. 6 is a diagram illustrating an example mapping pattern for Physical Uplink Shared Channel (PUSCH) repetition.

Fig. 7 is a diagram illustrating an example mapping pattern for PUSCH repetition.

Fig. 8 is a flow chart of a method of wireless communication.

Fig. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.

Fig. 10 is a flow chart of a method of wireless communication.

Fig. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus.

Fig. 12 shows a diagram illustrating an example deaggregated base station architecture.

Fig. 13 is a diagram illustrating an example of a hardware implementation for an example network entity.

Fig. 14 is a diagram illustrating an example of a hardware implementation for an example network entity.

Detailed description of the preferred embodiments

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts.

Several aspects of the telecommunications system will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and are 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 upon the particular application and design constraints imposed on the overall system.

As an example, an element, any portion of an element, or any combination of elements may be implemented as a "processing system" that includes 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, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can 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 types 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.

While aspects and implementations are described in the present disclosure by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may be made via integrated chip implementations and other non-module component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial devices, retail/purchasing devices, medical devices, artificial Intelligence (AI) -enabled devices, etc.). While some examples may or may not be specific to use cases or applications, a broad class 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 further to aggregate, distributed, or Original Equipment Manufacturer (OEM) devices or systems that incorporate one or more aspects of the innovations. In some practical arrangements, a device incorporating the described aspects and features may also include additional components and features to implement and practice the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders/summers, etc.). It is contemplated that the innovations described herein may be practiced in devices, chip-scale components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

Deployment of a communication system, such as a 5G NR system, may be arranged in a variety of ways with various components or parts. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, radio Access Network (RAN) nodes, core network nodes, network elements, or network devices, 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 architecture or a disaggregated architecture. For example, BSs, such as Node BS (NB), evolved NB (eNB), NR BS, 5G NB, access Points (APs), transmission and Reception Points (TRP), cells, etc., may be implemented as an aggregated base station (also referred to as a standalone BS or monolithic BS) or a disaggregated base station.

The aggregation base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The deaggregation base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (e.g., one or more central or Centralized Units (CUs), one or more Distributed Units (DUs), 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, may be geographically or virtually distributed throughout one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as virtual units, i.e., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs).

The base station operation or network design may take into account the aggregate nature of the base station functions. For example, the deaggregated 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 virtual radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually at least one unit, which may enable flexibility in network design. The various elements of the disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other element.

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. A 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., a 5G core (5 GC)). Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). The macrocell includes a base station. Small cells include femto cells, pico cells, and micro cells.

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 over a first backhaul link 132 (e.g., S1 interface). A base station 102 configured for 5G NR (collectively referred to as a next generation RAN (NG-RAN)) may interface with a core network 190 over a second backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, positioning, and delivery of warning 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 a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the 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 comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include home evolved node B (eNB) (HeNB), which may provide services to a restricted 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) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use multiple-input and multiple-output (MIMO) antenna techniques 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 a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400MHz, etc.) bandwidth per carrier allocated in carrier aggregation up to yxmhz (x component carriers) total for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., DL may be allocated more or less carriers than 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).

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as WiMedia, bluetooth, zigBee, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communication system may also include a Wi-Fi Access Point (AP) 150 in communication with a Wi-Fi Station (STA) 152 via a communication link 154 (e.g., in a 5GHz unlicensed spectrum, etc.). When communicating in an unlicensed spectrum, STAs 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communicating in order to determine whether a channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz or the like) as Wi-Fi AP 150 may use. Small cells 102' employing NRs in the unlicensed spectrum may enhance coverage of the access network and/or increase the capacity of the access network.

Electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5GNR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. FR2 sometimes suffers from similar naming problems, and in documents and articles FR2 is often (interchangeably) referred to as the "millimeter wave" band, although it is different from the very high frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency band falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, the term "sub-6 GHz" and the like, if used herein, may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, the term "millimeter wave" and the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and/or FR5, or may be within the EHF band.

In view of the above, unless specifically stated otherwise, it should be understood that the term "sub-6 GHz" or the like, if used herein, may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that the term "millimeter wave" or the like, if used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band.

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, a gndeb (gNB), or another type of base station. Some base stations (such as the gNB 180) may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Millimeter-wave base station 180 may utilize beamforming 182 with 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 facilitate beamforming.

The base station 180 may transmit the beamformed signals to the UEs 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals in one or more transmit directions to the base station 180. The base station 180 may receive the beamformed signals from the UEs 104 in one or more directions. The base stations 180/UEs 104 may perform beam training to determine the best reception and transmission direction for each of the base stations 180/UEs 104. The transmit direction and the receive direction for the base station 180 may be the same or different. The transmit direction and the receive direction of the UE 104 may be the same or different.

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.MME 162 may communicate with 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, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are communicated through the serving gateway 166, which serving gateway 166 itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, 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 be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting charging information related to eMBMS.

The core network 190 may include access and mobility management functions (AMFs) 192, other AMFs 193, session Management Functions (SMFs) 194, and User Plane Functions (UPFs) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197.IP services 197 may include internet, intranet, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.

A base station may include and/or be referred to as a gNB, a node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a Transmit Receive Point (TRP), or some other suitable terminology. The base station 102 provides an access point for the UE 104 to the EPC 160 or the core network 190. Examples of UEs 104 include a cellular telephone, a smart phone, 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 electricity meter, an air pump, a large or small kitchen device, a medical device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, 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 arrangement. One or more of these devices may access the network in common and/or individually.

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 a configuration of the first set of SRS resources and the second set of SRS resources (e.g., from a network entity such as the base station 102/180). In some aspects, SRS component 198 may also be configured to: a DCI for UL transmission is received from a network entity (e.g., base station 102/180) indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, SRS component 198 may also be configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are transmitted to the network entity 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 of the scheduled UL transmission. The UL transmission may include a PUSCH including a first repeated set of PUSCHs and a second repeated set of PUSCHs. For example, a first repeated set of PUSCHs may be transmitted on a first beam associated with a first SRS resource set, and power control for PUSCHs may be based on SRS Resource Indicators (SRIs) associated with the first SRS resource set, and a second repeated set of PUSCHs may be transmitted on a second beam associated with a second SRS resource set, and power control for PUSCHs may be based on SRIs associated with the second SRS resource set. The network entity may be a network node. The network nodes may be implemented as aggregated base stations, disaggregated base stations, integrated Access and Backhaul (IAB) nodes, relay nodes, sidelink nodes, and the like. The network entity 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.

In certain aspects, base station 180 can include SRS component 199. In some aspects, SRS component 199 can be configured to transmit a configuration of the first set of SRS resources and the second set of SRS resources. In some aspects, SRS component 199 may also be configured to: a DCI for UL transmission is transmitted for a UE, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, SRS component 199 may also be configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are received in an order based on information transmitted in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission. The UL transmission may include a PUSCH including a first repeated set of PUSCHs and a second repeated set of PUSCHs. For example, a first repeated set of PUSCHs may be received on a first beam associated with a first SRS resource set, and power control for the PUSCHs may be based on SRIs associated with the first SRS resource set, and a second repeated set of PUSCHs may be received on a second beam associated with a second SRS resource set, and power control for the PUSCHs may be based on SRIs associated with the second SRS resource set.

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

Fig. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Fig. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Fig. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Fig. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be Frequency Division Duplex (FDD) in which subframes within a subcarrier set are dedicated to DL or UL for a particular subcarrier set (carrier system bandwidth), or Time Division Duplex (TDD) in which subframes within a subcarrier set are dedicated to both DL and UL for a particular subcarrier set (carrier system bandwidth). In the example provided in fig. 2A, 2C, it is assumed that the 5GNR frame structure is TDD, where subframe 4 is configured with slot format 28 (mainly DL), where D is DL, U is UL, and F is flexibly used between DL/UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3, 4 are shown as having slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. The slot formats 0, 1 are full DL, full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically configured by Radio Resource Control (RRC) signaling) by receiving a Slot Format Indicator (SFI). Note that the following description also applies to a 5G NR frame structure as TDD.

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that 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 slots. The 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 conventional or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (limited to single stream transmission for power limited scenarios). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines a subcarrier spacing (SCS) and effectively defines a symbol length/duration equal to 1/SCS.

For a normal CP (14 symbols/slot), different parameter sets μ0 to μ4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for the normal CP and parameter set μ, there are 14 symbols/slot and 2 ^μ Time slots/subframes. The subcarrier spacing may be equal to 2 ^μ *15kHz, where μ is the parameter set 0 to 4. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely proportional to the subcarrier spacing. Fig. 2A to 2D provide examples of a normal CP having 14 symbols per slot, and a parameter set μ=2 having 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67 mus. Within a group of frames there may be one or more frequency division multiplexed different bandwidth portions (BWP) (see fig. 2B). Each BWP may have a specific set of parameters and CPs (regular or extended).

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As shown in fig. 2A, some REs carry a reference (pilot) signal (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRs), and phase tracking RSs (PT-RSs).

Fig. 2B shows an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within 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 CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWP may be located at higher and/or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be within symbol 2 of a particular subframe of a frame. The UE 104 uses PSS to determine subframe/symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The UE uses SSS to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides a plurality of RBs and System Frame Numbers (SFNs) in a system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as System Information Blocks (SIBs) and paging messages.

As shown in fig. 2C, some REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS may be transmitted in the previous or two symbols of PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency dependent scheduling on the UL.

Fig. 2D shows examples of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), 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)). PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In DL, internet Protocol (IP) packets may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. Controller/processor 375 provides RRC layer functionality associated with broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection setup, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) and handover support functions; RLC layer functions associated with upper layer Packet Data Unit (PDU) delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto Transport Blocks (TBs), de-multiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.

The Transmit (TX) processor 316 and the Receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, which includes a Physical (PHY) layer, may include error detection on a transport channel, forward Error Correction (FEC) encoding/decoding of a transport channel, interleaving, rate matching, mapping onto a physical channel, modulation/demodulation of a physical channel, and MIMO antenna processing. TX processor 316 processes the 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 decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying the time domain OFDM symbol stream. The OFDM streams are spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimate may be derived from reference signals 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 318 Tx. Each transmitter 318Tx may modulate a Radio Frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (Rx) processor 356.TX processor 368 and RX processor 356 implement layer 1 functions associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for the UE 350, then the RX processor 356 may combine them into a single OFDM symbol stream. 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 and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by base station 310. These soft decisions may be based on channel estimates computed by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller/processor 359 for implementing layer 3 and layer 2 functions.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. 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, deciphering, 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.

Similar to the functionality described in connection with DL transmission by the base station 310, the controller/processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression/decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functions associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs on TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling and logical channel prioritization.

TX base station 368 can select an appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by channel estimator 358 from reference signals or feedback transmitted by processor 310. The spatial streams generated by TX processor 368 may be provided to different antennas 352 via separate transmitters 354 TX. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform aspects related to SRS component 198 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform aspects related to SRS component 199 of fig. 1.

Fig. 4 is a diagram 400 illustrating a base station 402 in communication with a UE 404. Referring to fig. 4, a base station 402 may transmit beamforming signals to a UE 404 in one or more of directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402 h. The UE 404 may receive the beamformed signals from the base station 402 in one or more receive directions 404a, 404b, 404c, 404 d. The UE 404 may also transmit a beamformed signal to the base station 402 in one or more of the directions 404a-404 d. The base station 402 may receive the beamformed signals from the UE 404 in one or more of the receive directions 402a-402 h. The base station 402/UE 404 may perform beam training to determine the best receive direction and transmit direction for each of the base stations 402/UE 404. The transmit direction and the receive direction of the base station 402 may be the same or different. The transmit direction and the receive direction of the UE 404 may be the same or different.

In response to different conditions, the UE 404 may determine to switch beams, for example, between beams 404a-404 h. The beam at the UE 404 may be used for reception of downlink communications and/or transmission of uplink communications. In some examples, the base station 402 may transmit a transmission that triggers a beam switch by the UE 404. For example, the base station 402 may indicate a Transmit 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 examples, a UE may receive a signal from a base station configured to trigger a Transmit Configuration Indication (TCI) state change via, for example, a MAC Control Element (CE) command. The TCI state change may cause the UE to find the best UE receive beam from the base station that corresponds to the TCI state and switch to such beam. Switching beams may allow for enhanced or improved connection between a UE and a receiver by ensuring that the base station and the transmitter communicate using the same configured set of beams.

The base station 402 and the UE 404 may each include a plurality of Transmission and Reception Points (TRPs). Each TRP may include a different RF module with shared hardware and/or software controllers. Each TRP may perform separate baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements.

The set of time and frequency resources that may be used for one or more transmissions of SRS may be referred to as a "SRS resource set. In some communication systems, SRS resource set suitability (i.e., what SRS resource set is used for) of an SRS resource set may be configured by a higher layer parameter (such as "use") associated with the SRS resource set, such as in an SRS-reuureset 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, and so forth. Each SRS resource set may be configured with one or more (e.g., up to 16) SRS resources. Each SRS resource set may be aperiodic, semi-persistent, or periodic.

In some wireless communication systems, two types of PUSCH transmissions 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, a maximum of 4 SRS resources within a set may be configured for a UE. Each SRS resource may be a Radio Resource Control (RRC) configured with a plurality of ports (e.g., one or more ports). An SRS Resource Indicator (SRI) field in UL DCI of the scheduled PUSCH may indicate one SRS resource. The number of ports configured for the indicated SRS resource may determine the number of antenna ports for PUSCH. PUSCH may be transmitted using the same spatial domain filter (which may otherwise be referred to as a "beam") as the indicated SRS resources. The number of layers (i.e., rank) for scheduled PUSCH or a Transmitted Precoding Matrix Indicator (TPMI) (e.g., for a precoder) may be determined according to the separate DCI field "precoding information and number of layers".

For non-codebook based transmissions, the UE may be configured with one set of SRS resources, with "use" set to "non-codebook". For example, a maximum of 4 SRS resources within a set may be configured for a UE. Each SRS resource may be an RRC configured with one port. The SRI field in the UL DCI of the scheduled PUSCH may indicate one or more SRS resources. The indicated number of SRS resources may determine a rank (i.e., number of layers) of the PUSCH for scheduling. PUSCH may be transmitted with the same precoder and the same spatial domain filter (i.e., beam) as the indicated SRS resources.

In some aspects, a multi-TRP or multi-panel may be used to enhance the reliability and robustness of PUSCH. For example, if one link using a first TRP is blocked and one repetition of PUSCH cannot be received, another repetition may be received and decoded by another TRP. Thus, with multi-TRP, the diversity of transmission is increased and PUSCH transmission can be more reliable. The repetition may be otherwise referred to as a transmission occasion.

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 repetition is sent in different time slots in a type a repetition and the repetition is sent in different minislots in a type B repetition. The number of repetitions may be RRC configured or may be dynamically indicated, for example, by utilizing a Time Domain Resource Allocation (TDRA) field of the DCI. In some wireless communication systems, all repetitions may be transmitted with the same beam. For example, the SRI field of DCI may be applied to all repetitions. The SRI may be a field in the UL DCI that determines a beam or power control parameter for PUSCH by pointing to one or more SRS resources within a set of SRS resources.

In some other wireless communication systems, different PUSCH repetitions are intended to 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 repeated sets, where each repeated set has its own beam associated with its own power control parameters. Each repetition set may include one or more repetitions. Such two repeated sets may correspond to two SRS resource sets associated with DCI indicating two beams and two sets of power control parameters by indicating one or more SRS resources within each of the two SRS resource sets. Aspects herein enable association between two SRS resource sets and two PUSCH repetition sets.

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 at least two SRS resource sets 506 for the UE 502. In some aspects, the network entity 504 may or may not support dynamic sequential switching. In some aspects, SRS resource sets 506 may each have an SRS resource set Identifier (ID), which may be represented by a SRS-reourceseet ID field in an SRS-REourceSet parameter. In some aspects, SRS resource set 506 may include parameters representing an order, such as SRS-reourcesettorder parameters. The network entity 504 may be a network node. The network nodes may be implemented as aggregated base stations, disaggregated base stations, integrated Access and Backhaul (IAB) nodes, relay nodes, sidelink nodes, and the like. The network entity 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.

In some aspects, the network entity 504 may send DCI 508 to the UE 502. In some aspects, the network entity 504 may support dynamic sequential switching. In some aspects, DCI 508 may include one or more bits (such as two bits) to indicate an order of SRS resource sets in SRS resource sets 506.

The UE 502 may send one or more repetitions of 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 PUSCH may include repetitions of the same data or TB. In some aspects, the SRS resource set with the lowest ID may correspond to a first repetition set (the first may be the repetition set that occurs first in time) and the SRS resource set with the second lower ID corresponds to a second repetition set, among the two SRS resource sets in SRS resource set 506. For example, the first set of PUSCH repetitions may include a first PUSCH repetition 510 and a second PUSCH repetition 512, while the second set of PUSCH repetitions may include a third PUSCH repetition 514 and a fourth PUSCH repetition 516. The first PUSCH repetition set may correspond to the SRS resource set with the lowest ID. In some aspects, a first set of repetitions in time of PUSCH may be transmitted on a first beam associated with a first set of SRS resources, and power control for PUSCH may be based on SRIs associated with the first set of SRS resources, and a second set of repetitions in time of PUSCH may be transmitted on a second beam associated with a second set of SRS resources, and power control for PUSCH may be based on SRIs associated with the second set of SRS resources. In some aspects, the first set of PUSCH repetitions may be transmitted using the same beam (first beam) as the first set of SRS resources (which may otherwise 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 set of SRS resources (which may otherwise be referred to as a "spatial domain filter").

In some aspects, the first and second sets of repetitions may be transmitted on beams respectively selected for transmission to the first and second TRPs, panels or antennas of the network entity 504. If the link to the first TRP is blocked, the network entity 504 may not be able to receive the first duplicate set. However, since the data is also sent to the second TRP in the second repetition set, the network entity 504 may still receive the data. Thus, diversity of transmission is increased, and PUSCH transmission can be more reliable.

In some aspects, among the two SRS resource sets in SRS resource set 506, the SRS resource set with the highest ID may correspond to the first repetition set and the SRS resource set with the second highest ID corresponds to the second repetition set. For example, the first set of PUSCH repetitions may include a first PUSCH repetition 510 and a second PUSCH repetition 512, while the second set of PUSCH repetitions may include a third PUSCH repetition 514 and a fourth PUSCH repetition 516. The first PUSCH repetition set may correspond to the SRS resource set with the highest ID. In some aspects, the SRS resource set 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 the parameters representing the order. By using such an order, the SRS resource set and the SRI associated with the SRS resource set (which may be used for power control of PUSCH repetition) or TRP may be indicated to the UE 502 so that the UE may know which TRP and power control is to be used for PUSCH repetition.

In some aspects, if network entity 504 supports dynamic order switching and 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, DCI code points may be 0, 1, 2, or 3 and may be associated with sequences 1, 2, 12, and 21. Sequence 1 may correspond to a first TRP based on the SRS resource set with the lowest ID (e.g., it may be in single TRP mode, and a second SRS resource set may be unused). Sequence 2 may be based on the SRS resource set with the second low ID may correspond to the second TRP (e.g., it may be in single TRP mode, and the first SRS resource set may be unused). The sequence 12 may correspond to a first TRP based on the SRS resource set with the lowest ID and the SRS resource set with the second lowest ID may correspond to a second TRP. The sequence 21 may correspond to the second TRP based on the SRS resource set with the lowest ID and the SRS resource set with the second lowest ID may correspond to the first TRP. Each SRS resource set may be associated with a beam and SRI that may be used for power control in PUSCH repetition. The DCI may include an order to associate SRS resource sets with PUSCH repetitions, which in turn may associate PUSCH repetitions with beams or SRS associated with SRS resource sets. Table 1 shows example correspondence between DCI code point sets and correspondence sets indicating the order of SRS resource sets.

TABLE 1

Fig. 6 is a diagram 600 illustrating an example cyclic mapping pattern for PUSCH repetition. As shown in fig. 6, DCI 602 may schedule four PUSCH repetitions: PUSCH repetition 604, PUSCH repetition 606, PUSCH repetition 608, and PUSCH repetition 610. For cyclic 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 cyclic mapping pattern may be applicable to both type a and type B repetitions.

Fig. 7 is a diagram 700 illustrating an example sequential mapping pattern for PUSCH repetition. As shown in fig. 7, 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, a first PUSCH repetition 704 and a second PUSCH repetition 706 may be associated with the first beam and the 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 to both type a and type B repetitions.

Fig. 8 is a flow chart 800 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 404, UE 502; apparatus 902).

At 802, the UE may receive a configuration of a first set of SRS resources associated with a first beam and a second set of SRS resources associated with a second beam. For example, the UE 502 may receive, from the network entity 504, a configuration of a first set of SRS resources associated with a first beam and a second set of SRS resources associated with a second beam of SRS resources 506. In some aspects, 802 may be performed by SRS configuration component 940 or SRS component 198 in fig. 9. In some aspects, the configuration includes an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

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

At 806, the UE may send a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources to a network entity (e.g., a base station or component of the base station) in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI of the scheduled UL transmission. For example, the UE 502 may send a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set to the network entity 504 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 of the scheduled 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 performed by PUSCH component 944 or SRS component 198 in fig. 9. 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 smaller 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 order rule indicates that the SRS resource set with the lower SRS resource set ID is later in time. In some aspects, the order rule indicates that the SRS resource set with the 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 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.

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 transceiver 924 (also referred to as a modem) coupled to one or more transceivers 922 (e.g., cellular RF processors). The cellular baseband processor 924 may include on-chip memory 924'. In some aspects, the apparatus 902 may also include one or more Subscriber Identity Module (SIM) cards 920 and an application processor 906 coupled to the Secure Digital (SD) card 908 and the screen 910. The application processor 906 may include on-chip memory 906'. In some aspects, the apparatus 902 may also 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., barometric pressure sensor/altimeter, motion sensors such as an Inertial Management Unit (IMU), gyroscope, and/or accelerometer(s), light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), acoustic navigation and ranging (sonor), magnetometers, audio, and/or other techniques for positioning), additional memory modules 926, a power source 930, and/or a camera 932. Bluetooth module 912, WLAN module 914, and SPS module 916 may include an on-chip Transceiver (TRX) (or, in some cases, only a Receiver (RX)). Bluetooth module 912, WLAN module 914, and SPS module 916 may include their own dedicated antennas and/or communicate using antenna 980. The cellular baseband processor 924 communicates with the UE 104 and/or RU associated with the network entity 904 through the transceiver(s) 922 via the antenna(s) 980. The cellular baseband processor 924 and the application processor 906 may each include a computer readable medium/memory 924', 906', respectively. Additional memory modules 926 may also be considered as computer-readable media/memory. Each of the computer-readable media/memories 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 on a 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 can also be used for storing data that is manipulated by the cellular baseband processor 924/applications processor 906 when executing software. The cellular baseband processor 924/applications 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 apparatus 902 may be a processor chip (modem and/or application) and include only the cellular baseband processor 924 and/or application processor 906, and in another configuration, the apparatus 902 may be an entire UE (see, e.g., 350 of fig. 3) and include additional modules of the apparatus 902. In some aspects, the SRS component 198 may be configured to receive a configuration of the first set of SRS resources and the second set of SRS resources. In some aspects, SRS component 198 may also be configured to: a DCI for UL transmission is received from a network entity, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, SRS component 198 may also be configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are transmitted to the network entity 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 of the scheduled UL transmission. SRS component 198 can include SRS configuration component 940 that can be configured to receive a configuration of the first set of SRS resources and the second set of SRS resources, e.g., as described in connection with 802 in fig. 8. SRS component 198 may also include a DCI component 942, which DCI component 942 may be configured to receive DCI for a UL transmission from a network entity (e.g., a base station or a component of a base station) indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam, e.g., as described in connection with 804 in fig. 8. The SRS component 198 may also include a PUSCH component 944, which may be configured to transmit a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources to a network entity (e.g., a base station or component of a base station) in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in DCI of a scheduled UL transmission, e.g., as described in connection with 806 in fig. 8.

The apparatus may include additional components to perform each of the blocks of the algorithm in the flowchart of fig. 9. As such, each block in the flowchart of fig. 9 may be performed by components, and an apparatus may include one or more of these components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 902 may include various components configured for various functions. In one configuration, apparatus 902 (and in particular cellular baseband processor 924) may include means for receiving a configuration of a first set of SRS resources and a second set of SRS resources. The cellular baseband processor 924 may further include: means for receiving 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 set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources 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 the base station) a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of a scheduled UL transmission. The component may be one or more of the components of the apparatus 902 configured to perform the functions recited by the component. As described above, apparatus 902 may include TX processor 368, RX processor 356, and controller/processor 359. As such, in one configuration, the component may be TX processor 368, RX processor 356, and controller/processor 359 configured to perform the functions recited by the components.

Fig. 10 is a flow chart 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).

At 1002, a network entity can transmit a configuration of a first set of SRS resources and a second set of SRS resources. For example, the network entity 504 may transmit to the UE 502 a configuration of a first set of SRS resources associated with a first beam and a second set of SRS resources associated with a second beam of SRS resources 506. In some aspects, 1002 may be performed by SRS configuration component 1140 or SRS component 199 in fig. 11. In some aspects, the configuration includes an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

At 1004, the network entity may transmit, for the UE, DCI for UL transmission indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. For example, the network entity 504 may transmit DCI 508 for UL transmission for the UE 502, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, 1004 may be performed by DCI component 1142 or SRS component 199 in fig. 11. In some aspects, the DCI does not indicate support for dynamic sequential switching. In some aspects, DCI indicates support for dynamic sequential switching. In some aspects, the information in the DCI may include one or more bits indicating an order rule associated with the first set of SRS resources and the second set of SRS resources. In some aspects, the DCI indicates a first SRI for a first repetition set and a second SRI for a second repetition set.

At 1006, the network entity may receive a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI of the scheduled UL transmission. For example, the network entity 504 may receive a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set from the UE 502 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 of the scheduled 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 performed by PUSCH component 1144 or SRS component 199 in fig. 11. 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 smaller 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 order rule indicates that the SRS resource set with the lower SRS resource set ID is later in time. In some aspects, the order rule indicates that the SRS resource set with the 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 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.

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 a 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 on a computer-readable medium/memory. When executed by the baseband unit 1104, the software causes the baseband unit 1104 to perform the various functions described above. The computer readable medium/memory can also be used for storing data that is manipulated by the baseband unit 1104 when executing software. The baseband unit 1104 also includes a receiving component 1130, a communication manager 1132, and a transmitting component 1134. The communications manager 1132 includes one or more of the illustrated components. Components within the communications manager 1132 may be stored in a computer readable medium/memory and/or configured as hardware within the baseband unit 1104. The baseband unit 1104 may be a component of the base station 310 and may include a memory 376 and/or at least one of a TX processor 316, an RX processor 370, and a controller/processor 375.

The communication manager 1132 can include an SRS configuration component 1140 that can transmit a configuration of the first set of SRS resources and the second set of SRS resources, e.g., as described in connection with 1002 in fig. 10. The communication manager 1132 can further include a DCI component 1142 that can transmit DCI for UL transmission for the UE that indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam, e.g., as described in connection with 1004 in fig. 10. The communication manager 1132 may also include a PUSCH component 1144 that may receive the first repeated set of PUSCHs based on the first set of SRS resources and the second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling UL transmissions, e.g., as described in connection with 1006 in fig. 10.

The apparatus may include additional components to perform each of the blocks of the algorithm in the flowchart of fig. 10. As such, each block in the flowchart of FIG. 10 may be performed by components, and an apparatus may include one or more of these components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.

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 the first set of SRS resources and the second set of SRS resources. Baseband unit 1104 may also include means for transmitting, for the UE, DCI for UL transmission indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. The baseband unit 1104 may also include means for receiving a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs 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 DCI of the scheduled UL transmission. The component may be one or more of the components of the apparatus 1102 configured to perform the functions recited by the component. As described above, apparatus 1102 may include TX processor 316, RX processor 370, and controller/processor 375. As such, in one configuration, the components may be TX processor 316, RX processor 370, and controller/processor 375 configured to perform the functions recited by the components.

Fig. 12 shows a diagram illustrating an example deaggregated base station 1200 architecture. The disaggregated base station 1200 architecture may include one or more Central Units (CUs) 1010 that may communicate directly with the core network 1220 via a backhaul link, or indirectly with the core network 1220 through one or more disaggregated base station units (e.g., near real-time (near RT) RAN Intelligent Controllers (RIC) 1225 via E2 links, or non-real-time (non-RT) RIC 1215 associated with a Service Management and Orchestration (SMO) framework 1205, or both). CU 1210 can communicate with one or more Distributed Units (DUs) 1230 via corresponding intermediate range links (e.g., F1 interfaces). The DU 1230 may communicate with one or more Radio Units (RUs) 1240 via corresponding forward links. RU 1240 can communicate with corresponding UE 1222 via one or more Radio Frequency (RF) access links. In some implementations, the UE 1222 may be served by multiple RUs 1240 simultaneously. In some aspects, the network entity 504 or the base station 102/180 may be implemented based on a disaggregated base station 1200 architecture. In some aspects, UE 1222 may correspond to UE 104 or UE 502.

Each of the units (i.e., CU 1210, DU 1230, RU 1240 and near RT RIC 1225, non-RT RIC 1215 and SMO framework 1205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data or information (collectively referred to as signals) via wired or wireless transmission media. Units may be collectively referred to as "network entities". Each of the units or an associated processor or controller providing instructions to a communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive signals over a wired transmission medium or to transmit signals to one or more other units. 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, or both, to one or more other units over a wireless transmission medium.

In some aspects, 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), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 1210. 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, CU 1210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface (e.g., an E1 interface). CU 1210 can be implemented to communicate with DU 1230 as needed for network control and signaling.

DU 1230 may correspond to a logic unit comprising one or more base station functions for controlling the operation of one or more RUs 1240. In some aspects, DU 1230 may depend at least in part on a functional split, e.g., defined by the third generation partnership project (3 GPP), to 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 (e.g., modules for Forward Error Correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 1230 may also host one or more lower PHY layers. Each layer (or module) may be implemented with interfaces configured to communicate signals with other layers (and modules) hosted by DU 1230 or with control functions hosted by CU 1210.

Lower layer functions may be implemented by one or more RUs 1240. In some deployments, RU 1240 controlled by DU 1230 may correspond to a logical node that hosts RF processing functions or lower PHY layer functions (e.g., performs Fast Fourier Transforms (FFTs), inverse FFTs (iffts), digital beamforming, physical Random Access Channel (PRACH) extraction and filtering, etc.) or both based at least in part on the functional split (e.g., lower layer functional split). In such an architecture, RU(s) 1240 can be implemented to handle over-the-air (OTA) communications with one or more UEs 1222. In some implementations, the real-time and non-real-time aspects of control and user plane communications with RU(s) 1240 can be controlled by the respective DU 1230. In some scenarios, this configuration may enable DU(s) 1230 and CU 1210 to be implemented in a cloud-based RAN architecture (e.g., a vRAN architecture).

SMO framework 1205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 1205 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via operation and maintenance interfaces (such as O1 interfaces). For virtualized network elements, 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 instantiating virtualized network elements) via a cloud computing platform interface, such as an O2 interface. Such virtualized network elements may include, but are not limited to, CU 1210, DU 1230, RU 1240, and near RT RIC 1225. In some implementations, SMO framework 1205 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1211, via an O1 interface. Additionally, in some implementations, SMO framework 1205 may communicate directly with one or more RUs 1240 via an O1 interface. SMO framework 1205 may also include a non-RT RIC 1215 configured to support the functionality of SMO framework 1205.

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

In some implementations, to generate the AI/ML model to be deployed in the near RT RIC 1225, the non-RT RIC 1215 may receive parameters or external rich information from an external server. Such information may be used by near RT RIC 1225 and may be received at SMO framework 1205 or non-RT RIC 1215 from a non-network data source or from a network function. In some examples, the non-RT RIC 1215 or near-RT RIC 1225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 1215 may monitor long-term trends and patterns of performance and employ AI/ML models to perform corrective actions through SMO framework 1205 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

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. Network entity 1302 can include at least one of a CU 1310, a DU 1330, or a RU 1340. For example, depending on the layer functionality handled by SRS component 199, network entity 1302 may include CU 1310; both CU 1310 and DU 1330; each of CU 1310, DU 1330, and RU 1340; DU 1330; both DU 1330 and RU 1340; or RU 1340.CU 1310 may include a CU processor 1312.CU processor 1312 may include on-chip memory 1312'. In some aspects, CU 1310 may also include additional memory modules 1314 and a communication interface 1318.CU 1310 communicates with DU 1330 through a medium range link such as an F1 interface. The DU 1330 may include a DU processor 1332. The DU processor 1332 may include on-chip memory 1332'. In some aspects, DU 1330 may also include additional memory modules 1334 and communication interfaces 1338. The DU 1330 communicates with RU 1340 over a forward link. RU 1340 may include a RU processor 1342.RU processor 1342 may include on-chip memory 1342'. In some aspects, RU 1340 may also include additional memory modules 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348.RU 1340 communicates with UE 104. The on-chip memory 1312', 1332', 1342' and the additional memory modules 1314, 1334, 1344 may each be considered computer-readable media/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 on computer-readable media/memory. The software, when executed by the respective processor(s), causes the processor(s) to perform the various functions described supra. The computer readable medium/memory can also be used for storing data that is manipulated by the processor(s) when executing software.

As described above, SRS component 199 can be configured to transmit a configuration of a first set of SRS resources associated with a first beam and a second set of SRS resources associated with a second beam. In some aspects, SRS component 199 may also be configured to: a DCI for UL transmission is transmitted for a UE, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, SRS component 199 may also be configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are received in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission. SRS component 199 can be within one or more processors of one or more of CU 1310, DU 1330, and RU 1340. SRS component 199 can be one or more hardware components specifically configured to perform the process/algorithm, implemented by one or more processors configured to perform the process/algorithm, stored within 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, network entity 1302 includes means for transmitting a configuration of a first set of SRS resources and a second set of SRS resources. The network entity 1302 may further include: means for transmitting, for a UE, DCI for UL transmission, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. The network entity 1302 may further include: the apparatus includes means for receiving a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of a scheduled UL transmission. The component may be an SRS component 199 of the network entity 1302 configured to perform the functions recited by the component. As described above, network entity 1302 can include TX processor 316, RX processor 370, and controller/processor 375. As such, in one configuration, the component may be TX processor 316, RX processor 370, and/or controller/processor 375 configured to perform the functions recited by the components.

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 within the core network 120. The network entity 1460 can include a network processor 1412. The network processor 1412 may include on-chip memory 1412'. In some aspects, the network entity 1460 may also include additional memory modules 1414. Network entity 1460 communicates with CU 1402 either directly (e.g., backhaul link) or indirectly (e.g., through RIC) via network interface 1480. The on-chip memory 1412' and the additional memory module 1414 may each be considered as computer-readable media/memory. Each computer readable medium/memory may be non-transitory. The processor 1412 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the respective processor(s), causes the processor(s) to perform the various functions described supra. The computer readable medium/memory can also be used for storing data that is manipulated by the processor(s) when executing software.

As described above, SRS component 199 can be configured to transmit a configuration of the first set of SRS resources and the second set of SRS resources. In some aspects, SRS component 199 may also be configured to: a DCI for UL transmission is transmitted for a UE, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. In some aspects, SRS component 199 may also be configured to: the first repeated set of PUSCHs based on the first SRS resource set and the second repeated set of PUSCHs based on the second SRS resource set are received in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission. SRS component 199 can be within processor 1412. SRS component 199 can be one or more hardware components specifically configured to perform the process/algorithm, implemented by one or more processors configured to perform the process/algorithm, stored within 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, network entity 1460 includes means for transmitting a configuration of a first set of SRS resources and a second set of SRS resources. The network entity 1460 may also include: means for transmitting, for a UE, DCI for UL transmission, the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam. The network entity 1460 may also include: the apparatus includes means for receiving a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of a scheduled UL transmission. The component may be an SRS component 199 of a network entity 1460 configured to perform the functions recited by the component.

It is to be understood that the specific order or hierarchy of blocks in the disclosed processes/flowcharts are illustrative of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flow charts may be rearranged. Furthermore, some blocks may be combined or omitted. The claims of the appended method to present the elements of the various blocks in a sample order are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person 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 generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects shown herein, but are to be accorded the full scope consistent with the claim language, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Terms such as "if", "when … …" and "when … …" should be interpreted as "under … … conditions" and do not mean an immediate time relationship or reaction. That is, these phrases (e.g., "when … …") do not mean responsive to or immediate action during the occurrence of an action, but only mean that an action would occur if a condition is met, but do not require specific or immediate time constraints on the occurrence of an action. 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. The term "some" means one or more unless specifically stated otherwise. 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 multiples of a, multiples of B, or multiples of C. Specifically, a combination 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 alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C. All structural and functional equivalents to the elements of the various aspects described in the disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words "module," mechanism, "" element, "" device, "and the like are not to be substituted for the words" component. Therefore, any claim element should not be construed as a component plus function unless the use of the phrase "component for … …" explicitly describes the element.

The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, without being limited thereto.

Aspect 1 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to: receiving a configuration of a first SRS resource set and a second SRS resource set; receiving 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 set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam; and transmitting to a network entity (e.g., a base station or a component of the base station) a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of the scheduled UL transmission.

Aspect 2 is the apparatus of aspect 1, wherein 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 received in the configuration.

Aspect 3 is the apparatus of any one of aspects 1-2, wherein the first SRS resource set is sequentially designated earlier in time based on the first SRS resource set ID being a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

Aspect 4 is the apparatus of any one of aspects 1-2, wherein the first and second beams are selected for transmission to different transmission/reception points, antenna panels or antennas of the network entity.

Aspect 5 is the apparatus of any one of aspects 1-4, wherein the configuration includes an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

Aspect 6 is the apparatus of any one of aspects 1-5, wherein the same data or transport block is transmitted on each repetition.

Aspect 7 is the apparatus of any one of aspects 1-5, wherein the DCI indicates support for dynamic sequential switching.

Aspect 8 is the apparatus of any one of aspects 1-7, wherein the information in the DCI includes one or more bits indicating an order rule associated with the first set of SRS resources and the second set of SRS resources.

Aspect 9 is the apparatus of any one of aspects 1-8, wherein the order rule indicates that the SRS resource set with the lower SRS resource set ID is later in time.

Aspect 10 is the apparatus of any one of aspects 1-8, wherein the order rule indicates that the SRS resource set with the higher SRS resource set ID is later in time.

Aspect 11 is the apparatus of any one of aspects 1-10, wherein the UE transmits a first repetition set with a first set of power control parameters and a second repetition set with a second set of power control parameters.

Aspect 12 is the apparatus of any one of aspects 1-11, wherein the DCI indicates a first SRI for the first repetition set and a second SRI for the second repetition set.

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

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

Aspect 15 is a base station for wireless communication at a network entity (e.g., a component of a device or base station), comprising: a memory; and 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 is configured to cause the apparatus to: transmitting configurations of a first SRS resource set and a second SRS resource set; transmitting, for a UE, DCI for UL transmission, the DCI indicating the first and second SRS resource sets, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receiving a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission.

Aspect 16 is the apparatus of aspect 15, wherein 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.

Aspect 17 is the apparatus of any one of aspects 15-16, wherein the first SRS resource set is sequentially designated earlier in time based on the first SRS resource set ID being a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

Aspect 18 is the apparatus of any one of aspects 15-16, wherein the first and second beams correspond to different transmission/reception points, antenna panels or antennas of the network entity.

Aspect 19 is the apparatus of any one of aspects 15-18, wherein the configuration includes an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

Aspect 20 is the apparatus of any one of aspects 15-19, wherein the same data or transport block is transmitted on each repetition.

Aspect 21 is the apparatus of any one of aspects 15-19, wherein the DCI indicates support for dynamic sequential switching.

Aspect 22 is the apparatus of any one of aspects 15-21, wherein the information in the DCI includes one or more bits indicating an order rule associated with the first set of SRS resources and the second set of SRS resources.

Aspect 23 is the apparatus of any one of aspects 15-22, wherein the order rule indicates that the SRS resource set with the lower SRS resource set ID is later in time.

Aspect 24 is the apparatus of any one of aspects 15-22, wherein the order rule indicates that the SRS resource set with the higher SRS resource set ID is later in time.

Aspect 25 is the apparatus of any of aspects 15-24, wherein a network entity (e.g., a base station or a component of a base station) receives a first set of repetitions using a first set of power control parameters and a second set of repetitions using a second set of power control parameters.

Aspect 26 is the apparatus of any one of aspects 15-25, wherein the DCI indicates a first SRI for a first repetition set and a second SRI for a second repetition set.

Aspect 27 is the apparatus of any one of aspects 15-26, wherein the first set of repetitions is associated with a first antenna at a network entity (e.g., a base station or 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 component of a base station).

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

Aspect 29 is a method of wireless communication at a UE, comprising: receiving a configuration of a first SRS resource set and a second SRS resource set; receiving 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 set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam; and transmitting to a network entity (e.g., a base station or a component of the base station) a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of the scheduled UL transmission.

Aspect 30 is the method of aspect 29, further comprising a method for implementing any of aspects 1-14.

Aspect 31 is an apparatus for wireless communication at a UE, comprising: means for receiving a configuration of a first set of SRS resources and a second set of SRS resources; means for receiving 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 set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam; and means for transmitting to a network entity (e.g., a base station or a component of the base station) a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of the scheduled UL transmission.

Aspect 32 is the apparatus for wireless communication of aspect 31, further comprising: means for implementing any one of aspects 1-14.

Aspect 33 is a computer-readable medium storing computer-executable code at a UE that, when executed by a processor, causes the processor to: receiving a configuration of a first SRS resource set and a second SRS resource set; receiving 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 set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with a first beam and the second set of SRS resources is associated with a second beam; and transmitting to a network entity (e.g., a base station or a component of the base station) a first repeated set of PUSCHs based on the first set of SRS resources and a second repeated set of PUSCHs based on the second set of SRS resources in an order based on information received in a configuration of the first set of SRS resources and the second set of SRS resources or in DCI of the scheduled UL transmission.

Aspect 34 is the computer-readable medium of aspect 33, wherein the code, when executed by the processor, causes the processor to implement any one of aspects 1-14.

Aspect 35 is a method of wireless communication at a network entity (e.g., a base station or a component of a base station), comprising: transmitting configurations of a first SRS resource set and a second SRS resource set; transmitting, for a UE, DCI for UL transmission, the DCI indicating the first and second SRS resource sets, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receiving a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission.

Aspect 36 is the method of aspect 35, further comprising a method for implementing any of aspects 15-28.

Aspect 37 is a base station for wireless communication at a network entity (e.g., a component of a device or base station), comprising: means for transmitting a configuration of the first SRS resource set and the second SRS resource set; means for transmitting, for a UE, DCI for UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and means for receiving a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission.

Aspect 38 is the apparatus for wireless communication of aspect 37, further comprising: means for implementing any of aspects 15-28.

Aspect 39 is a computer-readable medium storing computer-executable code at 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: transmitting configurations of a first SRS resource set and a second SRS resource set; transmitting, for a UE, DCI for UL transmission, the DCI indicating the first and second SRS resource sets, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and receiving a first repeated set of PUSCHs based on the first SRS resource set and a second repeated set of PUSCHs based on the second SRS resource set in an order based on information received in a configuration of the first SRS resource set and the second SRS resource set or in DCI of the scheduled UL transmission.

Aspect 40 is the computer-readable medium of aspect 39, wherein the code, when executed by the processor, causes the processor to implement any one of aspects 15-28.

Claims (30)

1. An apparatus for wireless communication at a user equipment, UE, comprising:

a memory; and

at least one processor coupled to the memory and configured to cause the apparatus to:

receiving 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 and second SRS resource sets, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and

a first repeated set of physical uplink shared channels, PUSCHs, based on the first set of SRS resources and a second repeated set of PUSCHs, based on the second set of SRS resources are transmitted to the network entity in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling the UL transmission.

2. The apparatus of claim 1, wherein 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, and received in the configuration.

3. 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 a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

4. The apparatus of claim 1, wherein the first beam and the second beam are selected to be transmitted to different transmission/reception points, antenna panels, or antennas of the network entity.

5. The apparatus of claim 1, wherein the configuration comprises an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

6. The apparatus of claim 1, wherein the same data or transport block is transmitted on each repetition.

7. The apparatus of claim 1, wherein the DCI indicates support for dynamic sequential switching.

8. The apparatus of claim 1, wherein the information in the DCI comprises one or more bits indicating a sequence rule associated with the first set of SRS resources and the second set of SRS resources.

9. The apparatus of claim 8, wherein the order rule indicates that SRS resource sets with lower SRS resource set identifiers IDs are later in time.

10. The apparatus of claim 8, wherein the order rule indicates that SRS resource sets with higher SRS resource set identifiers IDs are later in time.

11. 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.

12. The apparatus of claim 1, wherein the DCI indicates a first SRS resource indicator, SRI, for the first repetition set and a second SRI for the second repetition set.

13. 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.

14. The apparatus of claim 1, further comprising a transceiver or antenna coupled to the at least one processor.

15. An apparatus for wireless communication at a network entity, comprising:

a memory; and

at least one processor coupled to the memory and configured to cause 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 uplink, UL, transmission for a user equipment, UE, the DCI indicating the first SRS resource set and the second SRS resource set, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and

a first repeated set of physical uplink shared channels, PUSCHs, based on the first set of SRS resources and a second repeated set of PUSCHs, based on the second set of SRS resources are received in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling the UL transmission.

16. The apparatus of claim 15, wherein 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, and received in the configuration.

17. 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 a lower number or a higher number between the first SRS resource set ID and the second SRS resource set ID.

18. The apparatus of claim 16, wherein the first beam and the second beam correspond to different transmission/reception points, antenna panels, or antennas of the network entity.

19. The apparatus of claim 15, wherein the configuration comprises an SRS resource set order that represents an order between the first SRS resource set and the second SRS resource set.

20. The apparatus of claim 15, wherein the same data or transport block is transmitted on each repetition.

21. The apparatus of claim 15, wherein the DCI indicates support for dynamic sequential switching.

22. The apparatus of claim 15, wherein the information in the DCI comprises one or more bits indicating a sequence rule associated with the first set of SRS resources and the second set of SRS resources.

23. The apparatus of claim 22, wherein the order rule indicates that SRS resource sets with lower SRS resource set identifiers IDs are later in time.

24. The apparatus of claim 22, wherein the order rule indicates that SRS resource sets with higher SRS resource set identifiers IDs are later in time.

25. The apparatus of claim 15, wherein the network entity receives the first set of repetitions with a first set of power control parameters and receives the second set of repetitions with a second set of power control parameters.

26. The apparatus of claim 15, wherein the DCI indicates a first SRS resource indicator, SRI, for the first repetition set and a second SRI for the second repetition set.

27. 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.

28. The apparatus of claim 15, further comprising a transceiver coupled to the at least one processor.

29. A method of wireless communication at a user equipment, UE, comprising:

receiving 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 and second SRS resource sets, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and

a first repeated set of physical uplink shared channels, PUSCHs, based on the first set of SRS resources and a second repeated set of PUSCHs, based on the second set of SRS resources are transmitted to the network entity in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling the UL transmission.

30. A method for wireless communication at 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 uplink, UL, transmission for a user equipment, UE, the DCI indicating the first SRS resource set and the second SRS resource set, wherein the first SRS resource set is associated with a first beam and the second SRS resource set is associated with a second beam; and

a first repeated set of physical uplink shared channels, PUSCHs, based on the first set of SRS resources and a second repeated set of PUSCHs, based on the second set of SRS resources are received in an order based on information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI scheduling the UL transmission.