TW202249522A - Srs resource set and beam order association for multi-beam pusch - Google Patents

Abstract

Methods, apparatuses, and computer readable storage medium for PUSCH repetitions and SRS resource sets are provided. An example method includes receiving a configuration of a first SRS resource set and a second SRS resource set. The example method further includes receiving, from a network entity, DCI for an UL transmission, the DCI indicating the first SRS resource set and the second SRS resource set. The first/second SRS resource set is respectively associated with a first/second beam. The example method further includes transmitting, to the network entity, a first set of repetitions of a PUSCH based on the first SRS resource set and a second set of repetitions of the PUSCH based on the second SRS resource set in an order based on information received in the configuration of the first SRS resource set and the second SRS resource set or in the DCI scheduling the UL transmission.

Description

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

This patent application claims the benefit and priority of U.S. Provisional Application No. 63/2021, filed May 7, 2021, and entitled "SRS RESOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH" 185,919; and U.S. Nonprovisional Patent Application No. 17/662,222, filed May 5, 2022, and entitled "SRS RESOURCE SET AND BEAM ORDER ASSOCIATION FOR MULTI-BEAM PUSCH," the entirety of which is expressly incorporated herein by reference.

In general, this case relates to communication systems, and more specifically, this case relates to communications systems with Sounding Reference Signal (SRS), Downlink Control Information (DCI) and Physical Uplink (UL) Shared Channel (PUSCH) wireless communication system.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging and broadcasting. A typical wireless communication system may employ a multiple access technology capable of supporting communication with multiple users by sharing 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 Access (OFDMA) system, single carrier frequency division multiple access (SC-FDMA) system and time division synchronous code division multiple access (TD-SCDMA) system.

These multiplexing access techniques have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, national, regional and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the evolution of continuous mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet requirements associated with latency, reliability, security, scalability (e.g., together with Internet of Things (IoT)) New requirements and others. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC) and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements are also applicable to other multiplex access technologies and the telecommunication standards using these technologies.

A brief overview of one or more aspects is provided below 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 illustrate 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 Transceiver Points (TRPs), panels or antennas at the base station, and the repetitions may use the same beam or different beam. For example, two repetition sets may be provided, each repetition set comprising its own beams associated with its own power control parameters. Each set of repetitions may contain one or more repetitions. Such two repeating sets may correspond to two sets of SRS resources that may include DCIs that may indicate two beams by indicating one or more SRS resources within each of the two sets of SRS resources and two sets of power control parameters. Aspects herein implement the association between two sets of SRS resources and two sets of PUSCH repetitions, thereby facilitating more efficient PUSCH transmission.

In one aspect of the subject matter, a method, computer readable medium and apparatus at a user equipment (UE) are provided. The apparatus can include 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 configurations 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 also be configured to: receive DCI for UL transmission from a network entity (eg, a base station or a component of a base station), the DCI indicating the first set of SRS resources and the second set of SRS resources Two sets of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the second beam. The memory and the at least one processor coupled to the memory may also be configured to: 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 scheduling UL transmissions, 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 are sent to the network entity.

In another aspect of the subject matter, a method, computer-readable medium, and apparatus at a network entity (eg, a base station or a component of a base station) are provided. The apparatus can include 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: transmit configurations 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 also be configured to: send DCI for UL transmission to the 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 the same as the second set of SRS resources. One beam is associated, and a second set of SRS resources is associated with the second beam. The memory and the at least one processor coupled to the memory may also be configured to: in an order based on information sent in the configuration of the first set of SRS resources and the second set of SRS resources or in DCI scheduling UL transmissions, A first repeated set of PUSCH is received based on the first set of SRS resources and a second repeated set of PUSCH is received based on the second set of SRS resources.

To the accomplishment of the foregoing and related ends, one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The description below and the annexed drawings set forth certain illustrative features of one or more aspects in detail. These characterizations indicate, however, but some of the various ways in which principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

The embodiments set forth below in conjunction with the figures are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. The embodiments include specific details for the purpose of providing a thorough understanding of various concepts. It will be apparent, however, to one having ordinary skill in the art to which the present invention pertains, that these 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 such concepts.

Several aspects of telecommunications systems will now be provided with reference to various devices and methods. These apparatuses and methods will be described in the detailed description below, and shown in the drawings through various blocks, components, circuits, programs, 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.

For example, an element, or any portion of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, on-chip System (SoC), baseband processor, field programmable gate array (FPGA), programmable logic device (PLD), state machine, gating logic, individual hardware circuits, and Other suitable hardware for various functions. One or more processors in the processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be construed broadly to mean instructions, sets of instructions, code, code fragments, code, programs, Subroutine, software component, application, software application, package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored 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 may include random access memory (RAM), read only memory (ROM), electronically erasable programmable ROM (EEPROM), optical disk memory, Disk memory, other magnetic storage devices, combinations of the above 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.

Although aspects and implementations are described in this case by way of illustration of a few examples, those of ordinary skill in the art to which this invention pertains will understand that additional implementations and use cases are possible in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, implementation and/or use may be implemented via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communications equipment, computing equipment, industrial equipment, retail/purchasing equipment, medical equipment, artificial intelligence-enabled Intelligent (AI) devices, etc.) are generated. There can be a wide variety of scopes of applicability for the innovations described, although certain examples may or may not be specific to use cases or applications. Implementations can range from wafer-level or modular components to non-modular, non-wafer-level implementations, and further to aggregated, decentralized, or OEMs incorporating one or more aspects of the described innovations (OEM) equipment or systems. In some practical arrangements, devices incorporating the described aspects and features may also include additional components and features for the implementation and implementation of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for both analog and digital purposes (including, for example, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/addition hardware components such as controllers). The innovations described herein are intended to be implemented in a variety of devices, wafer-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., having different sizes, shapes and configurations.

Deployment of communication systems (eg, 5G NR systems) can be arranged in a variety of ways with various components or components. In a 5G NR system or network, a network node, network entity, mobile element of the network, radio access network (RAN) node, core network node, network element or network device (such as a base station ( BS) or one or more units (or one or more components) performing base station functions) can be implemented in a converged or disaggregated architecture. For example, a BS such as Node B (NB), Evolved NB (eNB), NR BS, 5G NB, Access Point (AP), Transceiver Point (TRP) or cell, etc.) can be implemented as an aggregated base station ( Also known as independent BS or single-chip BS) or decomposed base station.

Converged base stations can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node. Disaggregated base stations may be configured to utilize physical or logical distribution over two or more units such as one or more central or centralized units (CUs), one or more distributed units (DUs) or a or multiple radio units (RUs)) stacking agreement. 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 among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

Base station operations or network design may take into account the aggregation nature of base station functions. For example, it can be implemented in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations sponsored by the O-RAN Alliance)) or Virtual Radio Access Networks (vRAN, also Known as Cloud Radio Access Network (C-RAN)) utilizes disaggregated base stations. Decomposition may include allocating functionality across two or more elements at various physical locations, as well as virtually allocating functionality for at least one element, which may enable flexibility in network design. Each element of the disaggregated base station or the 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 access network 100 . A wireless communication system (also known 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 (eg, 5G core (5GC)). The base stations 102 may include macrocells (high power cellular base stations) and/or small cells (low power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and minicells.

The base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may communicate via a first backhaul link 132 (eg, S1 interface) Come to dock with EPC 160. Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with a core network 190 via a second backhaul link 184 . Base station 102 may also perform, among other functions, one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover , dual connectivity), intercellular 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 multi broadcast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, location and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190 ) over the third backhaul link 134 (eg, the X2 interface). The first backload link 132, the second backload link 184, and the third backload link 134 may be wired or wireless.

Base station 102 can communicate with UE 104 wirelessly. Each of the base stations 102 can provide communication coverage for a corresponding geographic coverage area 110 . Overlapping geographic coverage areas 110 may exist. For example, the minicell 102 ′ may have a coverage area 110 ′ that overlaps the coverage area 110 of one or more macro base stations 102 . Networks that include both small cells and macrocytes can be referred to as heterogeneous networks. Heterogeneous networks may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide services to restricted groups known as Closed Subscriber Groups (CSGs). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also known as reverse link) transmissions from the UE 104 to the base station 102 and/or transmissions from the base station 102 to the UE. 104 for downlink (DL) (also known as forward link) transmissions. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. Communication links may be via one or more carriers. The base station 102/UE 104 can use up to Y MHz per carrier (e.g., 5, 10, 15 , 20, 100, 400, etc. MHz) bandwidth spectrum. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (eg, more or fewer carriers may be allocated for DL than for UL). 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).

Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158 . The D2D communication link 158 may use DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH) and a physical sidelink control channel (PSCCH). D2D communication can be via various wireless D2D communication systems such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on 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 communicating with a Wi-Fi station (STA) 152 via a communication link 154 in eg 5 GHz unlicensed spectrum. When communicating in unlicensed spectrum, the STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communicating to determine whether a channel is available.

The small cell 102' may operate in licensed and/or license-exempt spectrum. When operating in the unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum as used by the Wi-Fi AP 150 (eg, 5 GHz, etc.). Employing NR small cells 102' in unlicensed spectrum can improve the coverage and/or increase the capacity of the access network.

The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency/wavelength. In 5G NR, two initial operating frequency bands have been identified as the frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz. Although part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band. Similar nomenclature issues sometimes arise with regard to FR2, although it is distinct from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz), but in Commonly (interchangeably) referred to in documents and articles as the "mmWave" band, the EHF band is identified as the "mmWave" band by the International Telecommunication Union (ITU).

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified the operating band for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 can inherit FR1 characteristics and/or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as frequency range designations 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.

With the above in mind, unless specifically stated otherwise, if the term "below 6 GHz", etc. is used herein, it can broadly mean frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. frequency. In addition, unless specifically stated otherwise, if the term "millimeter wave" and the like are used herein, it may broadly mean that it may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may Frequencies within the EHF band.

In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" etc. is used herein, it can broadly mean that it can be less than 6 GHz, can be within FR1, or can include The frequency of the band frequency. In addition, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" etc. is used herein, it can broadly mean that it can include mid-band frequencies, can be in FR2, FR4, FR4-a or FR4-1 and and/or frequencies within FR5, or possibly within the EHF band.

A base station 102 (whether a small cell 102' or a macrocell (eg, a macro base station)) may include and/or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 , may operate in the conventional sub-6 GHz spectrum, at millimeter wave frequencies and/or near millimeter wave frequencies, to communicate with 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. The mmWave base station 180 can utilize beamforming 182 with the UE 104 to compensate for extremely high path loss and short distance. Base station 180 and UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays, to facilitate beamforming.

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

EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174 . MME 162 is a control node that handles signaling between UE 104 and EPC 160 . In general, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted via the service gateway 166 , which itself is connected to the PDN gateway 172 . The PDN Gateway 172 provides IP address allocation and other functions to UEs. PDN gateway 172 and BM-SC 170 are connected to IP service 176 . IP services 176 may include Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 can provide functions for MBMS user service setup and delivery. The BM-SC 170 can be used as an entry point for MBMS transmissions for content providers, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start/stop) and for collecting and Billing information related to eMBMS.

The core network 190 may include an access and mobility management function (AMF) 192 , other AMFs 193 , a session management function (SMF) 194 and a user plane function (UPF) 195 . The AMF 192 can communicate with a Unified Data Management (UDM) 196 . AMF 192 is a control node that handles signaling between UE 104 and core network 190 . In general, AMF 192 provides QoS flow and traffic session management. All User Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation as well as other functions. UPF 195 connects to IP service 197 . IP services 197 may include Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and/or other IP services.

A base station may include and/or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set ( ESS), Transmit Receive Point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104 . Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video equipment, digital audio players printers (e.g., MP3 players), video cameras, game consoles, tablets, smart devices, wearables, vehicles, electric meters, air pumps, large or small kitchen appliances, healthcare equipment, implants, sensors/ actuators, displays, or any other similarly functional device. Some of UEs 104 may be referred to as IoT devices (eg, parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be called a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile service client, client, or some other appropriate term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device cluster arrangement. One or more of these devices may access the network jointly and/or individually.

Referring again to FIG. 1 , in some aspects, UE 104 may include an SRS component 198 . In some aspects, SRS component 198 can be configured to receive (eg, from a network entity such as base station 102/180) 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 receive DCI for UL transmission from a network entity (eg, base station 102/180), the DCI indicating a first set of SRS resources and a second set of SRS resources, wherein A first set of SRS resources is associated with a first beam, and a second set of SRS resources is associated with a second beam. In some aspects, the SRS component 198 can also be configured to provide the network entity with 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 for scheduling UL transmissions. A first repeated set of PUSCH is sent based on the first set of SRS resources and a second repeated set of PUSCH is sent based on the second set of SRS resources. The UL transmission may include PUSCH including a first repeated set of PUSCHs and a second repeated set of PUSCHs. For example, a first repeated set 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 an SRS resource indicator (SRI ), and a second repeated set 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 the SRI associated with the second set of SRS resources. A network entity may be a network node. 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. Network entities may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include CUs, DUs, RUs, near real-time (near-RT) RAN intelligent controllers (RICs) ) or one or more of non-instant (non-RT) RIC.

In some aspects, base station 180 may include an SRS component 199 . In some aspects, SRS component 199 may be configured to transmit configurations of the first set of SRS resources and the second set of SRS resources. In some aspects, the SRS component 199 may also be configured to send DCI for UL transmission to the UE, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam , and the second set of SRS resources is associated with the second beam. In some aspects, the SRS component 199 can also be configured to, based on the order of the information sent in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI of scheduling UL transmission, based on the first SRS The set of resources receives a first repeated set of PUSCH and receives a second repeated set of PUSCH based on a second set of SRS resources. The UL transmission may include PUSCH including a first repeated set of PUSCHs and a second repeated set of PUSCHs. For example, a first repeated set of PUSCH may be received on a first beam associated with a first set of SRS resources, and power control for PUSCH may be based on the SRI associated with the first set of SRS resources, and may be performed at A second repeated set of PUSCH is received on a second beam associated with the second set of SRS resources, and power control for PUSCH may be based on the SRI associated with the second set of SRS resources.

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

FIG. 2A is a schematic diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a schematic diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a schematic diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. 2D is a schematic diagram 280 showing an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be Frequency Division Duplex (FDD) (wherein for a specific set of subcarriers (carrier system bandwidth), The subframes in the subcarrier set are dedicated to DL or UL), or can be time division duplex (TDD) (where for a specific subcarrier set (carrier system bandwidth), the subframes in the subcarrier set dedicated to both DL and UL). In the example provided via Figures 2A, 2C, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL and U is UL , and F is flexible between DL/UL, and subframe 3 is configured with slot format 1 (all of which are 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. Timeslot formats 0 and 1 are full DL and 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 via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically/statically via Radio Resource Control (RRC) signaling ). It should be noted that the following description is also applicable to the frame structure of 5G NR as TDD.

SCS

循環字首 0 15 普通 1 30 普通 2 60 普通 擴展 3 120 普通 4 240 普通 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and/or different channels. A frame (10 ms) can be divided into 10 sub-frames (1 ms) of equal size. Each subframe can include one or more time slots. A subframe can also include mini-slots, which can include 7, 4 or 2 symbols. Each slot can consist of 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. Each slot may include 14 symbols for a normal CP and 12 symbols for an extended CP. The symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread spectrum OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiplexing access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single stream transmission). The number of slots in a subframe can be based on CP and numerology. The digital scheme defines the sub-carrier spacing (SCS) and indeed the symbol length/duration (which may be equal to 1/SCS).

SCS

cyclic prefix 0 15 ordinary 1 30 ordinary 2 60 common extension 3 120 ordinary 4 240 ordinary

kHz，其中

是數字方案0至4。因此，數字方案µ=0具有15 kHz的次載波間隔，並且數字方案µ=4具有240 kHz的次載波間隔。符號長度/持續時間是與次載波間隔逆相關的。圖2A-2D提供普通CP（具有每時槽14個符號）以及數字方案µ=2（具有每子訊框4個時槽）的實例。時槽持續時間是0.25 ms，次載波間隔是60 kHz，並且符號持續時間近似為16.67 µs。在訊框集合內，可以存在分頻多工的一或多個不同的頻寬部分（BWP）（參見圖2B）。每個BWP可以具有特定的數字方案和CP（普通或擴展）。 For a normal CP (14 symbols/slot), the different number schemes µ 0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For extended CPs, Number Plan 2 allows 4 time slots per subframe. Correspondingly, for common CP and digital scheme µ, there are 14 symbols/slot and 2 ^µ slots/subframe. The subcarrier spacing can be equal to

kHz, where

is the number scheme 0 to 4. Thus, the digital scheme µ=0 has a subcarrier spacing of 15 kHz, and the digital scheme µ=4 has a subcarrier spacing of 240 kHz. Symbol length/duration is inversely related to subcarrier spacing. Figures 2A-2D provide examples of a normal CP (with 14 symbols per slot) and a digital scheme µ=2 (with 4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 µs. Within a frame set, there may be one or more different bandwidth parts (BWPs) of frequency division multiplexing (see FIG. 2B ). Each BWP can have a specific digital scheme and CP (normal or extended).

A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)), and a PRB includes 12 consecutive subcarriers. A resource grid is divided into resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As shown in FIG. 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as _Rx for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI- RS). RS may also include beam-squaring RS (BRS), beam-refining RS (BRRS), and phase-tracking RS (PT-RS).

FIG. 2B shows examples of various DL channels within subframes of a frame. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (for example, 1, 2, 4, 8 or 16 CCEs), each CCE comprising six RE groups (REGs) , each REG includes four consecutive REs in one OFDM symbol. A PDCCH within one BWP may be called a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (eg, common search space, UE-specific search space) during PDCCH monitoring occasions on CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and/or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by the UE 104 to determine subframe/symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE 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 can determine the physical cell identifier (PCI). Based on PCI, UE can determine the location of DM-RS. A physical broadcast channel (PBCH) carrying a master block (MIB) can be logically packed together with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also known as SS Block (SSB)). The MIB provides the number of RBs and the system frame number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) and paging messages not sent via PBCH.

As shown in Figure 2C, some of the REs carry DM-RSs (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). PUSCH DM-RS may be sent in the first one 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 depending on the specific PUCCH format used. The UE may send a sounding reference signal (SRS). SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. SRS can be used by the base station for channel quality estimation for 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. PUCCH carries uplink control information (UCI), such as scheduling request, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and hybrid automatic repeat request (HARQ) acknowledgment ( ACK) (HARQ-ACK) feedback (ie, one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)). The PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSRs), Power Headroom Reports (PHRs) and/or UCIs.

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

Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 including the physical (PHY) layer may include error detection for the transport channel, forward error correction (FEC) encoding/decoding for the transport channel, interleaving, rate matching, mapping onto the physical channel, Modulation/demodulation, and MIMO antenna processing. The TX processor 316 is based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-phase-shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)), to handle the mapping to signal clusters. The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed in time and/or frequency domain with a reference signal (e.g. pilot tone), and then combined using an inverse fast Fourier transform (IFFT), To generate a physical channel carrying a stream of time-domain OFDM symbols. OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to decide coding and modulation schemes and for spatial processing. Channel estimation can be derived based on reference signals sent by UE 350 and/or channel condition feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 Tx. Each transmitter 318 Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

At UE 350 , each receiver 354 Rx receives signals via its corresponding antenna 352 . Each receiver 354 Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356 . TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for UE 350 . If multiple spatial streams are destined for UE 350, they may be combined by RX processor 356 into a single stream of OFDM symbols. The RX processor 356 then uses Fast Fourier Transform (FFT) to convert the stream of OFDM symbols from the time domain to the frequency domain. The frequency domain signal includes a separate stream of OFDM symbols for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal cluster point transmitted by the 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 originally sent by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functions.

Controller/processor 359 can be associated with 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, packet reassembly, deciphering, header decompression, and control signal processing between transport lanes and logical lanes to recover IP packets. Controller/processor 359 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

Similar to the functionality described in connection with DL transmissions by the base station 310, the controller/processor 359 provides: RRC layer functionality associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and traffic test report; PDCP layer functions associated with: header compression/decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: upper layer PDU transmission, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: Mapping to and from transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, prioritization and logical channel prioritization.

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

UL transmissions are handled at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350 . Each receiver 318Rx receives signals via its corresponding antenna 320 . Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370 .

Controller/processor 375 can be associated with memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, control signal processing between transport lanes and logical lanes 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 communicating with a UE 404 . Referring to FIG. 4 , the base station 402 may transmit beamforming signals to the UE 404 in one or more of directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h. The UE 404 may receive beamformed signals from the base station 402 in one or more receive directions 404a, 404b, 404c, 404d. UE 404 may also send beamformed signals to base station 402 in one or more of directions 404a-404d. The base station 402 may receive beamformed signals from the UE 404 in one or more of the receive directions 402a-402h. The base station 402/UE 404 can perform beam training to decide the best receive and transmit directions for each of the base station 402/UE 404 . The transmit and receive directions for base station 402 may be the same or may be different. The transmit and receive directions for UE 404 may be the same or may be different.

In response to different conditions, UE 404 may decide to switch beams, eg, switch beams between beams 404a-404h. The beam at UE 404 can be used to receive downlink communications and/or send uplink communications. In some examples, base station 402 can send a transmission that triggers beam switching by UE 404 . For example, the base station 402 may indicate a transmission configuration indication (TCI) state change, and in response, the UE 404 may switch to a new beam for the new TCI state of the base station 402 . In some examples, a UE may receive a signal from a base station configured to trigger a Transmission Configuration Indication (TCI) state change via, for example, a MAC Control Element (CE) command. The change of the TCI state can make the UE find the best UE receiving beam corresponding to the TCI state from the base station, and switch to this beam. Switching beams may allow for an enhanced or improved connection between a UE and a base station by ensuring that the transmitter and receiver communicate using the same configured set of beams.

Base station 402 and UE 404 may each include multiple transmit-receive points (TRPs). Each TRP may include different RF modules with shared hardware and/or software controllers. Each TRP can perform individual baseband processing. Each TRP may include a different antenna panel or a different set of antenna elements.

A set of time and frequency resources that may be used for one or more transmissions of SRS may be referred to as an "SRS resource set." In some communication systems, the SRS resource set applicability (i.e., the usage of the SRS resource set) for the SRS resource set can be determined via higher layer parameters (such as the "usage" associated with the SRS resource set, such as in the SRS -ResourceSet parameter) to configure. For example, usage may be configured as one of beam management, codebook (eg, for codebook-based transmission), non-codebook (eg, for non-codebook-based transmission), antenna switching, and the like. Each SRS resource set may be configured with one or more (such as a maximum of 16) SRS resources. Each set of SRS resources can be aperiodic, semi-persistent or periodic.

In some wireless communication systems, two types of PUSCH transmissions can be supported. The first type may be referred to as codebook-based transmission. For codebook based transmission, the UE may be configured with a set of SRS resources with "use" set to "codebook". For example, up to 4 SRS resources in the set can be configured for the UE. Each SRS resource can be configured with a number of ports (such as one or more ports) by Radio Resource Control (RRC). An SRS resource indicator (SRI) field in the UL DCI of the scheduled PUSCH may indicate an SRS resource. The number of ports configured for the indicated SRS resource may determine the number of antenna ports used for PUSCH. The PUSCH may be transmitted using the same spatial filters (which may otherwise be referred to as "beams") as the indicated SRS resources. The number of layers (i.e., rank) used for the scheduled PUSCH or the transmitted precoding matrix indicator (TPMI) (e.g., for precoding coding).

For non-codebook based transmission, the UE may be configured with a set of SRS resources with "use" set to "non-codebook". For example, up to 4 SRS resources in the set can be configured for the UE. Each SRS resource can be configured with a port by RRC. 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 the rank (ie, number of layers) used for the scheduled PUSCH. The PUSCH may be transmitted with the same precoder and the same spatial filter (ie, beam) as the indicated SRS resource.

In some aspects, multiple TRPs or multiple panels can be used to enhance reliability and robustness for PUSCH. For example, if a link using the first TRP is blocked, and one repetition of PUSCH fails to be received, another repetition can be received and decoded by another TRP. Therefore, with multiple TRPs, the diversity of transmission increases and PUSCH transmission can be more reliable. Repetition may otherwise be referred to as a transmission opportunity.

The PUSCH may be sent 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), in type A repetitions, repetitions are sent in different time slots, and in type B repetitions, repetitions are sent in different micro-slots sent in. The number of repetitions may be RRC configured, or may be indicated dynamically, such as via a Time Domain Resource Assignment (TDRA) field using DCI. In some wireless communication systems, all repetitions may be sent using the same beam. For example, the SRI field of DCI can be applied to all repetitions. The SRI may be a field in the UL DCI, and the SRI determines the beam or power control parameters for the PUSCH by pointing to one or more SRS resources in the SRS resource set.

In some other wireless communication systems, different PUSCH repetitions are intended to be received at different TRPs, panels or antennas at network entities (eg, base stations), and the repetitions may use the same beam or different beams. For example, there may be two repeating sets, where each set has its own beam associated with its own power control parameters. Each set of repetitions may contain one or more repetitions. Such two repeating sets may correspond to two sets of SRS resources associated with a DCI indicating two beams by indicating one or more SRS resources within each of the two sets of SRS resources and two sets of power control parameters. Aspects herein implement the association between two sets of SRS resources and two sets of PUSCH repetitions.

5 is a diagram 500 illustrating communications between a UE 502 and a network entity 504 (eg, a base station). As shown in FIG. 5 , the network entity 504 may configure the UE 502 with at least two SRS resource sets 506 . In some aspects, network entity 504 may or may not support dynamic order switching. In some aspects, SRS resource sets 506 can each have an SRS resource set identifier (ID), which can be represented by the srs-ResourceSetID field in the SRS-ResourceSet parameter. In some aspects, the set of SRS resources 506 may include a parameter indicating an order, such as a SRS-ResourceSetOrder parameter. Network entity 504 may be a network node. 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. Network entities can be implemented in aggregated or monolithic base station architectures, or alternatively, can be implemented in disaggregated base station architectures, and can include CUs, DUs, RUs, near real-time (near-RT) RAN smart controllers ( RIC) or non-real-time (non-RT) RIC.

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

UE 502 may send one or more repetitions of PUSCH to network entity 504 , such as first PUSCH repetition 510 , second PUSCH repetition 512 , third PUSCH repetition 514 , and fourth PUSCH repetition 516 . One or more repetitions of PUSCH may include repetitions of the same data or TB. In some aspects, among the two SRS resource sets in SRS resource sets 506, the SRS resource set with the lowest ID may correspond to the first repeated set (the first repeated set may be the first repeated set in time set), and the SRS resource set with the second lowest ID corresponds to the second repeated set. For example, a first set of PUSCH repetitions may include a first PUSCH repetition 510 and a second PUSCH repetition 512 , while a second set of PUSCH repetitions may include a third 514 and fourth 516 PUSCH repetitions. The first PUSCH repetition set may correspond to the SRS resource set with the lowest ID. In some aspects, a first repeated set of PUSCHs in time may be transmitted on a first beam associated with a first set of SRS resources, and power control for PUSCH may be based on associated SRI, and a second repeated set of PUSCH in time may be transmitted on a second beam associated with a second set of SRS resources, and power control for PUSCH may be based on Linked to SRI's. In some aspects, the first PUSCH repetition set may be transmitted using the same beam as the first set of SRS resources (the first beam) (which may otherwise be referred to as a "spatial filter"). In some aspects, the second set of PUSCH repetitions may be transmitted using the same beam as the second set of SRS resources (the second beam) (which may otherwise be referred to as a "spatial filter").

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

In some aspects, within the two sets of SRS resources in SRS resource sets 506, the set of SRS resources with the highest ID may correspond to the first repeated set, and the set of SRS resources with the second highest ID to the second repeated set. corresponding to the set. For example, a first set of PUSCH repetitions may include a first PUSCH repetition 510 and a second PUSCH repetition 512 , while a second set of PUSCH repetitions may include a third 514 and fourth 516 PUSCH repetitions. The first PUSCH repetition set may correspond to the SRS resource set with the highest ID. In some aspects, the set of SRS resources associated with the first PUSCH repetition 510, the second PUSCH repetition 512, the third PUSCH repetition 514, and the fourth PUSCH repetition 516 may be determined based on a parameter indicative of an order. Via using such an order, the set of SRS resources and the SRI (which can be used for power control of PUSCH repetition) or TRP associated with the set of SRS resources can be indicated to the UE 502 so that the UE can know which TRP and power control to use for Push repeats.

In some aspects, if the network entity 504 supports dynamic order switching, and the DCI 508 includes one or more bits representing the order, the one or more bits may represent DCI codepoints that may correspond to the order. For example, DCI codepoints can be 0, 1, 2, or 3, and can be associated with orders 1, 2, 12, and 21. Order 1 may be based on the fact that the set of SRS resources with the lowest ID may correspond to the first TRP (eg, it may be in single TRP mode, and the second set of SRS resources may not be used). Order 2 may be based on the fact that the set of SRS resources with the second lowest ID may correspond to the second TRP (eg, it may be in single TRP mode and the first set of SRS resources may not be used). The order 12 may be based on that the set of SRS resources with the lowest ID may correspond to the first TRP and the set of SRS resources with the second lowest ID may correspond to the second TRP. The order 21 may be based on the fact that the set of SRS resources with the lowest ID may correspond to the second TRP and the set of SRS resources with the second lowest ID may correspond to the first TRP. Each set of SRS resources may be associated with a beam and an SRI, which may be used for power control in PUSCH repetition. The DCI may include an order in which sets of SRS resources are associated with PUSCH repetitions, which in turn associates PUSCH repetitions with beams or SRSs associated with the sets of SRS resources. Table 1 illustrates an example correspondence between a set of DCI code points and a set of correspondences indicating an order for a set of SRS resources. DCI code point order SRS resource collection order 0 1 The set of SRS resources with the lowest ID corresponds to the first repeated set 1 2 The set of SRS resources with the lowest ID corresponds to the second repeated set 2 1,2 The set of SRS resources with the lowest ID corresponds to the first repeated set The set of SRS resources with the next lowest ID corresponds to the second repeated set 3 2,1 The set of SRS resources with the second lowest ID corresponds to the first repeated set The set of SRS resources with the lowest ID corresponds to the second repeated set Table 1

6 is a diagram 600 illustrating an example cyclic mapping pattern for PUSCH repetition. As shown in FIG. 6 , DCI 602 can schedule four PUSCH repetitions, PUSCH repetition 604 , PUSCH repetition 606 , PUSCH repetition 608 and PUSCH repetition 610 . For cyclic beammapping, a first PUSCH repetition 604 and a 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. Cyclic mapping patterns can be applied to both Type A repetitions and Type B repetitions.

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 a first beam and a first set of power control parameters. A third PUSCH repetition 708 and a fourth PUSCH repetition 710 may be associated with a second beam and a second set of power control parameters. Sequential mapping schemas can be applied to both Type A repeats and Type B repeats.

FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a UE (eg, 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, UE 502 may receive from 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 in set of SRS resources 506 . In some aspects, 802 may be performed by SRS configuring component 940 or SRS component 198 in FIG. 9 . In some aspects, the configuration includes an SRS resource set order representing an order between the first set of SRS resources and the second set of SRS resources.

At 804, the UE may receive DCI for UL transmission from a network entity (eg, 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 the same as The first beam is associated and the second set of SRS resources is associated with the second beam. For example, UE 502 may receive DCI 508 for UL transmission from network entity 504, DCI 508 indicating a first set of SRS resources and a 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, DCI does not indicate support for dynamic order switching. In some aspects, DCI indicates support for dynamic order switching. In some aspects, the information in the DCI may include one or more bits indicating order rules 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 repeated set and a second SRI for a second repeated set.

At 806, the UE may notify a network entity (e.g., base station or The component) transmits a first repetition set of PUSCH based on the first set of SRS resources and transmits a second repetition set of PUSCH based on the second set of SRS resources. For example, the UE 502 may send PUSCH to the network entity 504 based on the first 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 for scheduling UL transmissions The first repetition set of and the second repetition set of sending PUSCH based on the second SRS resource set. For example, a first set of repetitions may include one or more of PUSCH repetitions 510 , 512 , 514 and 516 and a 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 the PUSCH component 944 or the SRS component 198 in FIG. 9 . In some aspects, the order is based on a first SRS resource set ID associated with the first set of SRS resources and a second SRS resource set ID associated with the second set of SRS resources and is received in the configuration. In some aspects, the first SRS resource set ID is the lower digit between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the first SRS resource set ID is the higher digit between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the order rule indicates that SRS resource sets with lower SRS resource set IDs are later in time. In some aspects, the ordering rule indicates that SRS resource sets with higher SRS resource set IDs are later in time. In some aspects, the UE transmits a first set of repetitions using a first set of power control parameters and transmits a second set of repetitions using a second set of power control parameters. In some aspects, the first repeating set is associated with a first antenna at the network entity and the second repeating set 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 . Apparatus 902 may be a UE, a component of a UE, or may implement a UE function. In some aspects, apparatus 2304 may include a cellular baseband processor 924 (also referred to as a modem) coupled to one or more transceivers 922 (eg, cellular RF transceivers). The cellular baseband processor 924 may include on-chip memory 924'. In some aspects, device 902 may also include one or more subscriber identity module (SIM) cards 920 and application processor 906 coupled to secure digital (SD) card 908 and screen 910 . The application processor 906 may include on-chip memory 906'. In some aspects, device 902 may also include Bluetooth module 912, WLAN module 914, SPS module 916 (eg, GNSS module), one or more sensor modules 918 (eg, barometric pressure sensing sensor/altimeter; motion sensors such as inertial management unit (IMU), gyroscope and/or accelerometer); light detection and ranging (LIDAR), radio-aided detection and ranging (radar), voice navigation and ranging (SONAR), magnetometer, audio and/or other technologies for positioning), additional memory module 926, power supply 930 and/or camera 932. The Bluetooth module 912, the WLAN module 914, and the SPS module 916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). Bluetooth module 912, WLAN module 914, and SPS module 916 may include their own dedicated antennas and/or utilize antenna 980 for communication. The cellular baseband processor 924 communicates with the UE 104 and/or RUs associated with the network entity 904 via the transceiver 922 via one or more antennas 980 . The cellular baseband processor 924 and the application processor 906 may each include computer readable media/memory 924', 906', respectively. The additional memory module 926 can also be regarded as a computer-readable medium/memory. Each computer readable medium/memory 924', 906', 926 may be non-transitory. The cellular baseband processor 924 and application processor 906 are each responsible for general processing, including executing software stored on a computer-readable medium/memory. The software, when executed by the cellular baseband processor 924/application processor 906, enables the cellular baseband processor 924/application processor 906 to perform the aforementioned various functions. The computer readable medium/memory can also be used to store data that is manipulated by the cellular baseband processor 924/application processor 906 when executing software. Cellular baseband processor 924 /application processor 906 may be part of UE 350 and may include memory 360 and/or at least one of TX processor 368 , RX processor 356 and controller/processor 359 . In one configuration, device 902 may be a processor die (modem and/or application) and include only cellular baseband processor 924 and/or application processor 906, and in another configuration device 902 may be an entire UE (eg, see 350 of FIG. 3 ), and includes additional modules of apparatus 902 . In some aspects, SRS component 198 can be configured to receive configurations of the first set of SRS resources and the second set of SRS resources. In some aspects, the SRS component 198 may also be configured to receive DCI for UL transmission from the network entity, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is connected to the first beam are associated, and a second set of SRS resources is associated with a second beam. In some aspects, the SRS component 198 can also be configured to provide the network entity with 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 for scheduling UL transmissions. A first repeated set of PUSCH is sent based on the first set of SRS resources and a second repeated set of PUSCH is sent based on the second set of SRS resources. SRS component 198 may include SRS configuring component 940, which may be configured to receive configurations of the first set of SRS resources and the second set of SRS resources, eg, as described in connection with 802 in FIG. 8 . The SRS component 198 may also include a DCI component 942, which may be configured to receive DCI for UL transmission from a network entity (e.g., a base station or a component of a base station), the DCI indicating the first set of SRS resources and the second set of SRS resources A set, wherein a first set of SRS resources is associated with a first beam and a second set of SRS resources is associated with a second beam, eg, 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 send information to the network 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 for scheduling UL transmissions. An entity (eg, a base station or a component of a base station) transmits a first repeated set of PUSCH based on a first set of SRS resources and transmits a second repeated set of PUSCH based on a second set of SRS resources, for example, as described in connection with 806 in FIG. 8 of.

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 9 . Accordingly, each block of the flowchart of FIG. 9 may be performed by components, and the apparatus may include one or more of those components. The components may be one or more hardware components specially configured to execute the program/algorithm, implemented by a processor configured to execute the program/algorithm, stored in a computer-readable medium for implemented by the processor, or some combination thereof.

As shown, apparatus 902 may include various components configured for various functions. In one configuration, the apparatus 902 (specifically, the cellular baseband processor 924) may include means for receiving configurations of the first set of SRS resources and the second set of SRS resources. The cellular baseband processor 924 may also include means for receiving DCI for UL transmissions from a network entity (e.g., a base station or a component of a base station), the DCI indicating the first set of SRS resources and the second set of SRS resources, Wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the second beam. The cellular baseband processor 924 may also include a function to provide information to network entities (e.g., The base station or a component of the base station) is a unit for sending a first repeated set of PUSCH based on a first set of SRS resources and sending a second repeated set of PUSCH based on a second set of SRS resources. The unit may be one or more of the components of the apparatus 902 configured to perform the function recited by the unit. As before, apparatus 902 may include TX processor 368 , RX processor 356 and controller/processor 359 . Thus, in one configuration, the unit may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the unit.

FIG. 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a network entity, such as a base station (eg, base station 102/180, base station 402, network entity 504, network entity 1302, or network entity 1460; apparatus 1102).

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

At 1004, the network entity may send DCI for UL transmission to the UE, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources A set is associated with a second beam. For example, the network entity 504 may send DCI 508 for UL transmission to the UE 502, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam and the second set of SRS resources A set of resources is associated with the second beam. In some aspects, 1004 may be performed by DCI component 1142 or SRS component 199 in FIG. 11 . In some aspects, DCI does not indicate support for dynamic order switching. In some aspects, DCI indicates support for dynamic order switching. In some aspects, the information in the DCI may include one or more bits indicating order rules 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 the first set of repetitions and a second SRI for the second set of repetitions.

At 1006, the network entity may receive the first set of SRS resources based on the first 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 for scheduling UL transmissions. A repetition set and a second repetition set of receiving PUSCH based on a second set of SRS resources. For example, the network entity 504 may receive the PUSCH from the UE 502 based on the first 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 for scheduling UL transmissions The first repetition set of and the second repetition set of receiving PUSCH based on the second set of SRS resources. For example, a first set of repetitions may include one or more of PUSCH repetitions 510 , 512 , 514 and 516 and a 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 the PUSCH component 1144 or the SRS component 199 in FIG. 11 . In some aspects, the order is based on a first SRS resource set ID associated with the first set of SRS resources and a second SRS resource set ID associated with the second set of SRS resources and is received in the configuration. In some aspects, the first SRS resource set ID is the lower digit 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 digit between the first SRS resource set ID and the second SRS resource set ID. In some aspects, the order rule indicates that SRS resource sets with lower SRS resource set IDs are later in time. In some aspects, the ordering rule indicates that SRS resource sets with higher SRS resource set IDs are later in time. In some aspects, the UE transmits a first set of repetitions using a first set of power control parameters and transmits a second set of repetitions using a second set of power control parameters. In some aspects, the first repeating set is associated with a first antenna at the base station and the second repeating set 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 . Apparatus 1102 may be a base station, a component of a base station, or may implement the function of a base station. In some aspects, apparatus 1102 may include baseband unit 1104 . The baseband unit 1104 may communicate with the UE 104 via a cellular RF transceiver 1122 . The baseband unit 1104 may include computer readable media/memory. The baseband unit 1104 is responsible for general processing, including executing software stored on computer-readable media/memory. When the software is executed by the baseband unit 1104, the baseband unit 1104 can perform the aforementioned various functions. The computer readable medium/memory can also be used to store data manipulated by the baseband unit 1104 when executing software. The baseband unit 1104 also includes a receiving unit 1130 , a communication manager 1132 and a sending unit 1134 . Communications manager 1132 includes one or more components as shown. Components within the communication manager 1132 may be stored on a computer readable medium/memory and/or configured as hardware within the baseband unit 1104 . Baseband unit 1104 may be a component of base station 310 and may include memory 376 and/or at least one of TX processor 316 , RX processor 370 and controller/processor 375 .

The communications manager 1132 can include an SRS configuration component 1140 that can transmit configurations of the first set of SRS resources and the second set of SRS resources, eg, as described in connection with 1002 in FIG. 10 . The communication manager 1132 may also include a DCI component 1142, which may send DCI for UL transmission to the 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 the first beam, And the second set of SRS resources is associated with the second beam, eg, as described at 1004 in FIG. 10 . The communication manager 1132 may also include a PUSCH component 1144, which may be based on the order of information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI for scheduling UL transmissions, based on the first SRS resource A first repeated set of PUSCHs is received in aggregate and a second repeated set of PUSCHs is received based on a second set of SRS resources, eg, as described in connection with 1006 in FIG. 10 .

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 10 . Accordingly, each block of the flowchart of FIG. 10 may be performed by components, and the apparatus may include one or more of those components. The components may be one or more hardware components specially configured to execute the program/algorithm, implemented by a processor configured to execute the program/algorithm, stored in a computer-readable medium for implemented by the processor, or some combination thereof.

As shown, apparatus 1002 may include various components configured for various functions. In one configuration, the apparatus 1002 (specifically, the base frequency unit 1104 ) may include a unit for transmitting configurations of the first set of SRS resources and the second set of SRS resources. The base frequency unit 1104 may also include a unit for sending DCI for UL transmission to the UE, and the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the first beam. Two sets of SRS resources are associated with the second beam. The baseband unit 1104 may also include a device for receiving the PUSCH based on the first 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 for scheduling UL transmissions. The units of the first repetition set and the second repetition set of receiving PUSCH based on the second set of SRS resources. The unit may be one or more components among the components of the apparatus 1102 configured to perform the function recited by the unit. As before, apparatus 1102 may include TX processor 316 , RX processor 370 and controller/processor 375 . Thus, in one configuration, the unit may be the TX processor 316, the RX processor 370, and the controller/processor 375 configured to perform the functions recited by the unit.

FIG. 12 illustrates a diagram illustrating an example disaggregated base station 1200 architecture. The disaggregated base station 1200 architecture may include one or more central units (CUs) 1210, which may communicate directly with the core network 1220 via a backhaul link, or via one or more disaggregated base station units (such as via E2 Link's near real-time (near-RT) RAN intelligent controller (RIC) 1225, or non-real-time (non-RT) RIC 1215 associated with service management and orchestration (SMO) framework 1205, or both) indirectly to the core network 1220 for communication. CU 1210 may communicate with one or more distributed units (DU) 1230 via corresponding medium-range links (such as the F1 interface). DU 1230 may communicate with one or more radio units (RU) 1240 via respective fronthaul links. RUs 1240 may communicate with corresponding UEs 1222 via one or more radio frequency (RF) access links. In some implementations, a UE 1222 can 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 the disaggregated base station 1200 architecture. UE 1222 may correspond to UE 104 or UE 502 in some aspects.

Each of the units (i.e., CU 1210, DU 1230, RU 1240, and near-RT RIC 1225, non-RT RIC 1215, and SMO frame 1205) may include or be coupled to one or more interfaces that Receive is 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 the unit's communication interface, 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 or send signals to one or more other units in the other units over a wired transmission medium. Additionally, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver, such as a radio frequency (RF) transceiver, configured to receive signals over a wireless transmission medium Or send a signal to one or more other units in other units, or both.

In some aspects, CU 1210 may host one or more higher-level 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 using an interface configured to communicate signals with other control functions hosted by CU 1210 . The CU 1210 may be configured to handle user plane functions (ie, central unit-user-plane (CU-UP)), control plane functions (ie, central unit-control plane (CU-CP)), or a combination thereof. In some implementations, a CU 1210 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface (eg, via an E1 interface when implemented in an O-RAN configuration). When necessary, CU 1210 may be implemented to communicate with DU 1230 for network control and signaling.

DU 1230 may correspond to a logic unit that includes one or more base station functions to control the operation of one or more RUs 1240 . In some aspects, DU 1230 may host a radio link control (RLC) layer, media access control ( MAC) layer and one or more higher physical (PHY) layers (such as 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 an interface configured to communicate with other layers (and modules) hosted by DU 1230 or control functions hosted by CU 1210 .

Lower layer functions may be implemented by one or more RUs 1240 . In some deployments, based at least in part on a functional split (such as a lower layer functional split), the RU 1240 controlled by the DU 1230 may correspond to hosting RF processing functions or low PHY layer functions (e.g., performing Fast Fourier Transform (FFT) , inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both. In such architectures, RU 1240 may 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 the control and user plane communications with the RU 1240 can be controlled by the corresponding DU 1230 . In some scenarios, this configuration may enable DU 1230 and CU 1210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO framework 1205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface, such as the O1 interface. For virtualized network elements, the SMO framework 1205 may be configured to interact with a cloud computing platform, such as an open cloud (O-cloud) 1290, to perform network element lifecycle management via a cloud computing platform interface, such as an O2 interface ( For example, to generate physical virtualization network elements). 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, the SMO framework 1205 can communicate with a hardware aspect of the 4G RAN, such as an open eNB (O-eNB) 1211 , via the O1 interface. Additionally, in some implementations, the SMO framework 1205 can communicate directly with one or more RUs 1240 via the O1 interface. The SMO framework 1205 may also include a non-RT RIC 1215 configured to support the functionality of the SMO framework 1205 .

The non-RT RIC 1215 can be configured to include logic functions that enable non-instantaneous control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows (including model training and updates), Policy-based guidance on application/features in or near RT RIC 1225. The non-RT RIC 1215 can couple to or communicate with the near-RT RIC 1225 (eg, via the Al interface). The near RT RIC 1225 may be configured to include logical functionality via an interface connecting one or more CUs 1210, one or more DUs 1230, or both, and an O-eNB with the near RT RIC 1225 (e.g., via the E2 interface) to enable near real-time control and optimization of RAN elements and resources.

In some implementations, the non-RT RIC 1215 may receive parameters or external enrichment information from an external server in order to generate an AI/ML model to be deployed in the near-RT RIC 1225 . Such information may be utilized by the near RT RIC 1225 and may be received at the SMO framework 1205 or non-RT RIC 1215 from non-network sources or network functions. In some examples, 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 can monitor long-term trends and patterns in performance and implement corrective actions using AI/ML models via the SMO framework 1205 (e.g., via reconfiguration of O1) or via establishment 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 a BS function. Network entity 1302 may include at least one of CU 1310 , DU 1330 or RU 1340 . For example, depending on the layer function 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; DU 1330 and RU 1340 Both; or RU 1340. The CU 1310 may include a CU processor 1312 . The CU processor 1312 may include on-chip memory 1312'. In some aspects, CU 1310 may also include additional memory module 1314 and communication interface 1318 . CU 1310 communicates with DU 1330 via a medium-range link, such as the F1 interface. DU 1330 may include a DU processor 1332 . The DU processor 1332 may include on-chip memory 1332'. In some aspects, the DU 1330 may also include an additional memory module 1334 and a communication interface 1338 . DU 1330 communicates with RU 1340 via a fronthaul link. RU 1340 may include RU processor 1342 . The RU processor 1342 may include on-chip memory 1342'. In some aspects, RU 1340 may also include additional memory module 1344 , one or more transceivers 1346 , antenna 1380 and communication interface 1348 . RU 1340 communicates with UE 104 . The on-chip memories 1312', 1332', 1342' and the additional memory modules 1314, 1334, 1344 can each be considered a computer readable medium/memory. Each computer-readable medium/memory can be non-transitory. Each of the processors 1312, 1332, 1342 is responsible for general processing, including executing software stored on computer-readable media/memory. The software, when executed by the corresponding processors, causes the processors to perform the various functions described above. Computer readable media/memory can also be used to store data that is manipulated by the processor when the software is executed.

As before, the SRS component 199 may be configured to transmit configurations 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, the SRS component 199 may also be configured to send DCI for UL transmission to the UE, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam , and the second set of SRS resources is associated with the second beam. In some aspects, the SRS component 199 can also be configured to, based on the order of information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI for scheduling UL transmissions, based on the first SRS The set of resources receives a first repeated set of PUSCH and receives a second repeated set of PUSCH based on a second set of SRS resources. SRS component 199 may reside within one or more processors of one or more of CU 1310 , DU 1330 , and RU 1340 . The SRS component 199 may be one or more hardware components specially configured to execute the program/algorithm, realized by one or more processors configured to execute the program/algorithm, stored in a computer Reading within the medium is intended to be implemented by one or more processors, or some combination thereof. The network entity 1302 may include various components configured for various functions. In one configuration, the network entity 1302 includes means for sending configurations of the first set of SRS resources and the second set of SRS resources. The network entity 1302 may also include a unit for sending DCI for UL transmission to the UE, the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the first beam. Two sets of SRS resources are associated with the second beam. The network entity 1302 may also include means for receiving the PUSCH based on the first 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 for scheduling UL transmissions. The units of the first repetition set and the second repetition set of PUSCH are received based on the second set of SRS resources. The element may be the SRS component 199 of the network entity 1302 configured to perform the function recited by the element. As before, network entity 1302 may include TX processor 316 , RX processor 370 and controller/processor 375 . Thus, in one configuration, the unit may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the unit.

FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a network entity 1460 . In one example, network entity 1460 may be located within core network 120 . Network entity 1460 may include network processor 1412 . The network processor 1412 may include on-chip memory 1412'. In some aspects, the network entity 1460 may also include an additional memory module 1414 . Network entity 1460 communicates with CU 1402 via network interface 1480 directly (eg, a loopback link) or indirectly (eg, via a RIC). Each of the on-chip memory 1412' and the additional memory module 1414 can be considered a computer-readable medium/memory. Each computer-readable medium/memory can be non-transitory. Processor 1412 is responsible for general processing, including executing software stored on computer-readable media/memory. The software, when executed by the corresponding processors, causes the processors to perform the various functions described above. Computer-readable media/memory can also be used to store data that is manipulated by the processor when the software is executed.

As mentioned above, the SRS component 199 may be configured to transmit configurations of the first set of SRS resources and the second set of SRS resources. In some aspects, the SRS component 199 may also be configured to send a DC for UL transmission to the UE, and the DCI indicates a first set of SRS resources and a second set of SRS resources, wherein the first set of SRS resources is associated with the first beam , and the second set of SRS resources is associated with the second beam. In some aspects, the SRS component 199 can also be configured to, based on the order of information received in the configuration of the first set of SRS resources and the second set of SRS resources or in the DCI for scheduling UL transmissions, based on the first SRS The set of resources receives a first repeated set of PUSCH and receives a second repeated set of PUSCH based on a second set of SRS resources. SRS component 199 may reside within processor 1412 . The SRS component 199 may be one or more hardware components specially configured to execute the program/algorithm, implemented by one or more processors configured to execute the program/algorithm, stored in the computer Reading within the medium is intended to be implemented by one or more processors, or some combination thereof. The network entity 1460 may include various components configured for various functions. In one configuration, the network entity 1460 includes means for sending configurations of the first set of SRS resources and the second set of SRS resources. The network entity 1460 may also include a unit for sending DCI for UL transmission to the 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 the first beam, and the second set of SRS resources is associated with the first beam. Two sets of SRS resources are associated with the second beam. The network entity 1460 may also include means for receiving the PUSCH based on the first 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 for scheduling UL transmissions. The units of the first repetition set and the second repetition set of receiving PUSCH based on the second set of SRS resources. The element may be an SRS component 199 of the network entity 146 configured to perform the function recited by the element.

It is understood that the specific order or hierarchy of blocks in the disclosed procedures/flow diagrams is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the procedures/flow diagrams may be rearranged. Also, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not meant to be limited to the specific order or hierarchy presented.

The preceding description is provided to enable any person having ordinary knowledge in the art to which the invention pertains to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art to which this invention pertains, and the generic principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the literal claims, wherein reference to an element in the singular is not intended to mean "One and only one" instead of "one or more". Terms such as "if", "when" and "while" should be interpreted as "under the conditions of" rather than implying a direct temporal relationship or response. That is, these phrases (e.g., "when") do not imply immediate action in response to or during the occurrence of the action, but only that the action will occur if the conditions are met, but No specific or immediate time constraint is required for this action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" means one or more. 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, 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", "among A, B, and C Combinations such as "one or more of", and "A, B, C or any combination thereof" may be only A, only B, only 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 or several members of A, B or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference, and are intended to be encompassed by the claims, which are commonly known in the art to which this invention pertains is known or will be known later. Furthermore, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The words "module", "mechanism", "element", "device", etc. may not be substituted for the word "unit". Thus, no claim element is to be construed as means-plus-function unless the element is explicitly recited using the phrase "means for".

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, but are not limited thereto.

Aspect 1 is an apparatus for wireless communication at a UE, including: a memory; and at least one processor coupled to the memory and configured to: receive a first SRS resource set and a second SRS resource set configuration; receiving DCI for UL transmission from a network entity (eg, a base station or a component of a base station), the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is the same as The first beam is associated and the second set of SRS resources is associated with the second beam; and based on the configuration of the first set of SRS resources and the second set of SRS resources or scheduling the UL transmission The order of information received in the DCI, sending to the network entity (e.g., a base station or a component of a base station) a first repeated set of PUSCHs based on the first set of SRS resources and sending the PUSCHs based on the second set of SRS resources Second repeating set.

Aspect 2 is the apparatus according to 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 is received in that configuration.

Aspect 3 is the apparatus according to any one of aspects 1-2, wherein the order is based on the first SRS resource set ID being between the first SRS resource set ID and the second SRS resource set ID A lower or higher number designates that the first set of SRS resources is earlier in time.

Aspect 4 is the apparatus of any of aspects 1-2, wherein the first beam and the second beam are selected to transmit to different transmit/receive points, antenna panels or antennas of the network entity .

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

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

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

Aspect 8 is the apparatus of any one of aspects 1-7, wherein the information in the DCI includes one or multiple bits.

Aspect 9 is the apparatus of any one of aspects 1-8, wherein the sequence 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 sequence rule indicates that SRS resource sets with higher SRS resource set IDs are later in time.

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

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

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

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

Aspect 15 is an apparatus for wireless communication at a network entity (eg, a base station or a component of a base station), comprising: a memory; and at least one processor coupled to the memory, and at least partially based on The information stored in the memory, the at least one processor is configured to cause the device to perform the following operations: sending configurations of the first SRS resource set and the second SRS resource set; sending DCI for UL transmission for the UE, the The DCI indicates the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the second beam; and based on the first set of SRS resources an order of information received in the configuration of a set of SRS resources and the second set of SRS resources or in the DCI scheduling the UL transmission, based on the first set of SRS resources for receiving a first repeated set of PUSCHs and based on the first set of SRS resources Two sets of SRS resources receive the second repeated set of the PUSCH.

Aspect 16 is the apparatus according to 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 that configuration.

Aspect 17 is the apparatus of any of aspects 15-16, wherein the order is based on the first SRS resource set ID being between the first SRS resource set ID and the second SRS resource set ID A lower or higher number designates that the first set of SRS resources is earlier in time.

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

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

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

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

Aspect 22 is the apparatus of any of aspects 15-21, wherein the information in the DCI includes one or multiple bits.

Aspect 23 is the apparatus of any one of aspects 15-22, wherein the sequence 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 sequence rule indicates that SRS resource sets with higher SRS resource set IDs are later in time.

Aspect 25 is the apparatus of any of aspects 15-24, wherein the network entity (e.g., a base station or a component of a base station) utilizes a first set of power control parameters to receive the first repeated set and The second repeated set is received with a second set of power control parameters.

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

Aspect 27 is the apparatus of any of aspects 15-26, wherein the first repeating set is associated with a first antenna at the network entity (e.g., a base station or a component of a base station), And the second repeating set is associated with a second antenna at the network entity (eg, a base station or a component of a base station).

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

Aspect 29 is a wireless communication method at a UE, including: receiving configurations of a first set of SRS resources and a second set of SRS resources; a transmitted DCI indicating the first set of SRS resources and the second set of SRS resources, where 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 to the network entity (e.g., base station or The component) transmits a first repetition set of PUSCH based on the first set of SRS resources and transmits a second repetition set of PUSCH based on the second set of SRS resources.

Aspect 30 is the method according to aspect 29, which also includes the method for implementing any one of aspects 1-14.

Aspect 31 is an apparatus for wireless communication at a UE, including: a unit for receiving configurations of a first set of SRS resources and a second set of SRS resources; A unit of a station) receiving DCI for UL transmission, the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second SRS a set of resources associated with a second beam; and for, 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, to A unit for the network entity (eg, a base station or a component of a base station) to transmit a first repeated set of PUSCH based on the first set of SRS resources and to transmit a second repeated set of PUSCH based on the second set of SRS resources.

Aspect 32 is the device for wireless communication according to Aspect 31, and also includes a unit for realizing any one of Aspects 1-14.

Aspect 33 is a computer-readable medium stored at a UE with computer-executable code that, when executed by a processor, causes the processor to: receive a first set of SRS resources and a second set of SRS resources configuration; receiving DCI for UL transmission from a network entity (for example, a base station or a component of a base station), the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second set of SRS resources is associated with the second beam; and based on the configuration of the first set of SRS resources and the second set of SRS resources or scheduling the UL transmission The sequence of information received in the DCI, sending to the network entity (e.g., a base station or a component of a base station) a first repeated set of PUSCH based on the first set of SRS resources and sending the PUSCH based on the second set of SRS resources The second repeated set of .

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

Aspect 35 is a wireless communication method at a network entity (for example, a base station or a base station component), including: sending configurations of the first SRS resource set and the second SRS resource set; a transmitted DCI indicating the first set of SRS resources and the second set of SRS resources, where 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 receiving a first repetition of PUSCH based on the first 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 the UL transmission and receiving a second repeated set of the PUSCH based on the second set of SRS resources.

Aspect 36 is the method according to Aspect 35, and also includes the method for realizing any one of Aspects 15-28.

Aspect 37 is an apparatus for wireless communication at a network entity (for example, a base station or a component of a base station), including: a unit for sending configurations of a first SRS resource set and a second SRS resource set; A unit for sending DCI for UL transmission to the UE, the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is associated with the first beam, and the second SRS resource a set is associated with a second beam; and for, 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, based on the The first set of SRS resources receives the first repeated set of PUSCH and the second set of SRS resources receives the unit of the second repeated set of PUSCH.

Aspect 38 is the device for wireless communication according to Aspect 37, and also includes a unit for realizing any one of Aspects 15-28.

Aspect 39 is a computer-readable medium of computer-executable code stored at a network entity (e.g., a base station or a component of a base station) that, when executed by a processor, causes the processor to: : sending the configuration of the first SRS resource set and the second SRS resource set; sending DCI for UL transmission to the UE, the DCI indicating the first SRS resource set and the second SRS resource set, wherein the first SRS resource set is associated with the first beam, and the second set of SRS resources is associated with the second beam; and based on the configuration of the first set of SRS resources and the second set of SRS resources or scheduling the UL transmission The order of information received in the DCI is to receive a first repeated set of PUSCH based on the first set of SRS resources and to receive a second repeated set of PUSCH based on the second set of SRS resources.

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

100: Wireless communication system and access network 102: base station 102': small cell 104:UE 110:Geographic coverage area 110': Geographic coverage area 120: Communication link 132: The first backload link 134: The third return link 150: Wi-Fi access point (AP) 152: Wi-Fi station (STA) 154: Communication link 158: D2D communication link 160: Evolved Packet Core (EPC) 162: Mobility Management Entity (MME) 164: Other MME 166: service gateway 168: Multimedia Broadcast Multicast Service (MBMS) Gateway 170:Broadcast Multicast Service Center (BM-SC) 172:Packet data network (PDN) gateway 174: Home Subscriber Server (HSS) 176: IP service 180: base station 182: Beamforming 182': sending direction 182'': receiving direction 184: The second backload link 190: Core network 192: Access and Mobility Management Function (AMF) 193:Other AMFs 194:Communication period management function (SMF) 195: User Plane Function (UPF) 196: Unified Data Management Unit (UDM) 197: IP service 198: SRS components 199: SRS components 200: Schematic diagram 230: schematic diagram 250: Schematic diagram 280: Schematic diagram 310: base station 316: Transmit (TX) processor 318Rx: Receiver 318Tx: Transmitter 320: Antenna 350:UE 352: Antenna 354Rx: Receiver 354Tx: Transmitter 356: RX processor 358: Channel Estimator 359: Controller/Processor 360: Memory 368:TX processor 370: Receive (RX) processor 374: Channel Estimator 375: Controller/Processor 376: memory 400: Figure 402: base station 402a: direction 402b: direction 402c: direction 402d: direction 402e: direction 402f: direction 402g: direction 402h: direction 404:UE 404a: Receive direction 404b: Receiving direction 404c: Receiving direction 404d: Receive direction 500: figure 502:UE 504: Network Entity 506: SRS resource collection 508:DCI 510: First PUSCH repeat 512: Second PUSCH repetition 514: The third PUSCH repeats 516: The fourth PUSCH repeats 600: figure 602:DCI 604:PUSCH repeat 606:PUSCH repeat 608:PUSCH repeat 610:PUSCH repeat 700: figure 702:DCI 704: The first PUSCH is repeated 706: The second PUSCH is repeated 708: The third PUSCH is repeated 710: The fourth PUSCH repeats 800: flow chart 802: block 804: block 806: cube 900: figure 902: device 904:Network entity 906: application processor 906': Computer readable media/memory 908:Secure Digital (SD) Card 910: screen 912:Bluetooth module 914: WLAN module 916:SPS module 918:Sensor module 922: Transceiver 924: Honeycomb baseband processor 924':Computer-readable media/memory 926:Extra Memory Module 930: power supply 932:Camera 940: SRS Configuration Parts 942: DCI components 944:PUSCH parts 980:antenna 1000: flow chart 1002: block 1004: block 1006: block 1100: Figure 1102: device 1104: base frequency unit 1122: Cellular RF Transceiver 1130: Receive component 1132: Communication Manager 1134:Send parts 1140: SRS configuration components 1142: DCI component 1144:PUSCH parts 1200: Decomposed base station 1205:Service Management and Orchestration (SMO) Framework 1210: Central Unit (CU) 1211: Open eNB (O-eNB) 1215: Non-instant (non-RT) RIC 1220: core network 1222:UE 1225:near RT RIC 1230:DU 1240:RU 1290: Open cloud (O-cloud) 1300: Figure 1302: Network entity 1312: CU processor 1312': On-chip memory 1314:Memory module 1318: communication interface 1330:DU 1332:DU processor 1332': On-chip memory 1334:Memory module 1338: communication interface 1340:RU 1342: RU processor 1342': On-chip memory 1344:Memory module 1346: Transceiver 1348: communication interface 1380: Antenna 1400: Figure 1402:CU 1412: network processor 1412': On-chip memory 1414:Memory module 1460: Network entity 1480: Network interface A1: Interface BWP: bandwidth part CSI-RS: Channel Status Information Reference Signal DCI: DL Control Information E2: link O1: interface O2:O2 PBCH: Physical broadcast channel PDCCH: Physical Downlink Control Channel PDSCH: Physical Downlink Shared Channel PSS: Primary Synchronization Signal PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel RB: resource block SSS: Secondary Synchronization Signal

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 according to various aspects of the present disclosure.

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

FIG. 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

FIG. 2D is a diagram illustrating examples of UL lanes within a subframe according to various aspects of the present disclosure.

FIG. 3 is a diagram showing examples of base stations and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating communication between a base station and a UE.

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

6 is a diagram illustrating an example mapping pattern for physical uplink shared channel (PUSCH) repetition.

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

FIG. 8 is a flowchart of a method of wireless communication.

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

FIG. 10 is a flowchart of a method of wireless communication.

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

12 illustrates a diagram of an example disaggregated base station architecture.

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

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

Domestic deposit information (please note in order of depositor, date, and number) none Overseas storage information (please note in order of storage country, institution, date, and number) none

500: figure

502:UE

504: Network Entity

506: SRS resource collection

508:DCI

510: First PUSCH repeat

512: Second PUSCH repetition

514: The third PUSCH repeats

516: The fourth PUSCH repeats

Claims (30)

An apparatus for wireless communication at a user equipment (UE), comprising: a memory; and At least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor configured to cause the apparatus to: receiving a configuration of a first set of sounding reference signal (SRS) resources and a second set of SRS resources; receiving downlink control information (DCI) for an uplink (UL) transmission from a network entity, the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is is associated with a first beam, and the second set of SRS resources is associated with a second beam; and sending to the network entity based on the first 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 the UL transmission A first repeated set of a physical uplink shared channel (PUSCH) is sent and a second repeated set of the PUSCH is sent based on the second set of SRS resources. The apparatus according to 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 associated with the second SRS resource set ID and is received in this configuration. The apparatus according to claim 2, wherein the order specifies the first SRS resource set ID based on the first SRS resource set ID being a lower or higher number between the first SRS resource set ID and the second SRS resource set ID An SRS resource set is earlier in time. The apparatus according to claim 1, wherein the first beam and the second beam are selected to transmit to different transmission/reception points, antenna panels or antennas of the network entity. The apparatus according to claim 1, wherein the configuration comprises an SRS resource set order representing the order between the first set of SRS resources and the second set of SRS resources. The apparatus according to claim 1, wherein an identical data or transport block is sent on each repetition. The device according to claim 1, wherein the DCI indicates support for dynamic order switching. The device according to claim 1, wherein the information in the DCI includes one or more bits indicating an ordering rule associated with the first set of SRS resources and the second set of SRS resources. The device according to claim 8, wherein the sequence rule indicates that an SRS resource set with a lower SRS resource set identifier (ID) is later in time. The device according to claim 8, wherein the sequence rule indicates that an SRS resource set with a higher SRS resource set identifier (ID) is later in time. The apparatus according to claim 1, wherein the UE transmits the first repeated set with a first set of power control parameters and transmits the second repeated set with a second set of power control parameters. The device according to 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. The apparatus according to claim 1, wherein the first repeated set is associated with a first antenna at the network entity, and the second repeated set is associated with a second antenna at the network entity. The device according to claim 1, further comprising: a transceiver or an antenna coupled to the at least one processor. An apparatus for wireless communication at a network entity, comprising: a memory; and At least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor configured to cause the apparatus to: sending configurations of a first sounding reference signal (SRS) resource set and a second SRS resource set; sending downlink control information (DCI) for an uplink (UL) transmission to a user equipment (UE), the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first the set of SRS resources is associated with a first beam, and the second set of SRS resources is associated with a second beam; and receiving a physical uplink based on the first 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 the UL transmission A first repeated set of road shared channel (PUSCH) and a second repeated set of the PUSCH are received based on the second set of SRS resources. The apparatus according to 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 associated with the second SRS resource set ID and is received in this configuration. The apparatus according to claim 16, wherein the order specifies the first SRS resource set ID based on the first SRS resource set ID being a lower or higher number between the first SRS resource set ID and the second SRS resource set ID An SRS resource set is earlier in time. The apparatus according to claim 16, wherein the first beam and the second beam correspond to different transmission/reception points, antenna panels or antennas of the network entity. The apparatus according to claim 15, wherein the configuration comprises an SRS resource set order representing the order between the first set of SRS resources and the second set of SRS resources. The apparatus according to claim 15, wherein a same data or transport block is sent on each repetition. The device according to claim 15, wherein the DCI indicates support for dynamic order switching. The device according to claim 15, wherein the information in the DCI includes one or more bits indicating an ordering rule associated with the first set of SRS resources and the second set of SRS resources. The device according to claim 22, wherein the sequence rule indicates that an SRS resource set with a lower SRS resource set identifier (ID) is later in time. The device according to claim 22, wherein the sequence rule indicates that an SRS resource set with a higher SRS resource set identifier (ID) is later in time. The apparatus according to claim 15, wherein the network entity receives the first repeated set using a first set of power control parameters and receives the second repeated set using a second set of power control parameters. The device according to 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. The apparatus according to claim 15, wherein the first repeated set is associated with a first antenna at the network entity, and the second repeated set is associated with a second antenna at the network entity. The apparatus according to claim 15, further comprising: a transceiver coupled to the at least one processor. A method of wireless communication at a user equipment (UE), comprising the steps of: receiving configurations of a first sounding reference signal (SRS) resource set and a second SRS resource set; receiving downlink control information (DCI) for an uplink (UL) transmission from a network entity, the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first set of SRS resources is is associated with a first beam, and the second set of SRS resources is associated with a second beam; and sending to the network entity based on the first 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 the UL transmission A first repeated set of a physical uplink shared channel (PUSCH) is sent and a second repeated set of the PUSCH is sent based on the second set of SRS resources. A method for wireless communication at a network entity, comprising the steps of: sending configurations of a first sounding reference signal (SRS) resource set and a second SRS resource set; sending downlink control information (DCI) for an uplink (UL) transmission to a user equipment (UE), the DCI indicating the first set of SRS resources and the second set of SRS resources, wherein the first the set of SRS resources is associated with a first beam, and the second set of SRS resources is associated with a second beam; and receiving a physical uplink based on the first 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 the UL transmission A first repeated set of road shared channel (PUSCH) and a second repeated set of the PUSCH are received based on the second set of SRS resources.

Images