PRS-DMRS association for sTRP / SDM PUSCH

Abstract

A plurality of configurations for an uplink phase tracking reference signal (PTRS) and downlink control information (DCI) for scheduling a PUSCH associated with a transmission parameter indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a space division multiplexed (SDM) PUSCH are received from a network entity. One or more uplink PTRS configurations are identified based on the transmission parameters. The PUSCH is then transmitted to the network entity, where the PUSCH is associated with the identified one or more uplink PTRS configurations based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

Description

[0001] Related Applications

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 18 / 364,311 filed on August 2, 2023 and U.S. Provisional Patent Application No. 63 / 397,754 filed on August 12, 2022, which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The present disclosure generally relates to communication systems, and more specifically to communications based on a single transmit receive point (sTRP) / spatial division multiplexing (SDM) physical uplink shared channel (PUSCH) and the association between a phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5GNR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] An overview of one or more aspects is presented below in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0007] In some examples, a user equipment (UE) configured for wireless communication is disclosed, the user equipment (UE) comprising: a memory; and at least one processor coupled to the memory and configured to: receive multiple configurations for an uplink phase tracking reference signal (PTRS) from a network entity; receive downlink control information (DCI) from the network entity for scheduling a PUSCH associated with a transmission parameter indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; identify one or more uplink PTRS configurations based on the transmission parameter; and send the PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

[0008] In some examples, a method for wireless communication for a user equipment (UE) is disclosed, the method comprising: receiving multiple configurations for uplink PTRS from a network entity; receiving DCI from the network entity for scheduling a PUSCH associated with a transmission parameter indicating one of sTRPPUSCH or SDM PUSCH; identifying one or more uplink PTRS configurations based on the transmission parameter; and sending the PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on an association between the identified one or more uplink PTRS configurations and a DMRS port.

[0009] In some examples, a network entity configured for wireless communication is disclosed, the network entity comprising: a memory; and at least one processor coupled to the memory and configured to: send multiple configurations for an uplink PTRS; send a DCI for scheduling a PUSCH associated with a transmission parameter indicating one of an sTRP PUSCH or an SDM PUSCH; and receive a PUSCH associated with one or more identified uplink PTRS configurations based on the transmission parameter, wherein the PUSCH is based on an association between the one or more identified uplink PTRS configurations and a DMRS port.

[0010] In some examples, a method for wireless communication for a network entity is disclosed, the method comprising: sending multiple configurations for uplink PTRS; sending DCI for scheduling a PUSCH associated with a transmission parameter indicating one of an sTRP PUSCH or an SDM PUSCH; and receiving a PUSCH associated with one or more identified uplink PTRS configurations based on the transmission parameter, wherein the PUSCH is based on an association between the one or more identified uplink PTRS configurations and a DMRS port.

[0011] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and access network according to some aspects.

[0013] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

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

[0015] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0016] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0017] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network according to some aspects.

[0018] Figure 4 A diagram illustrating an example decomposed base station architecture in accordance with some aspects is shown.

[0019] Figure 5 is a call flow diagram illustrating communications between a UE and a network entity according to some aspects.

[0020] Figure 6 is a diagram illustrating a phase tracking reference signal (PTRS)-demodulation reference signal (DMRS) allocation according to some aspects.

[0021] Figure 7

[0013] Illustrated is a PTRS-DMRS association table for an uplink PTRS port according to some aspects.

[0022] Figure 8 is a diagram illustrating a transmit precoding matrix index (TPMI) matrix indicating PTRS-DMRS associations in accordance with some aspects.

[0023] Fig. 9

[0013] Illustrated is a PTRS-DMRS association table for an uplink PTRS port according to some aspects.

[0024] Fig.10 A single DCI based PUSCH repetition configuration according to some aspects of the present disclosure is illustrated.

[0025] Fig.11 A block diagram for scheduling PUSCH for a single TRP and SDM configuration is illustrated in accordance with some aspects of the present disclosure.

[0026] Fig.12 A block diagram is illustrated for scheduling PUSCH using multiple PTRS configurations for a single TRP and SDM configuration in accordance with some aspects of the present disclosure.

[0027] Fig.13 A block diagram is illustrated for scheduling PUSCH using multiple PTRS configurations for a single TRP and SDM configuration in accordance with some aspects of the present disclosure.

[0028] Fig.14 is a flow chart of a method of wireless communication at a UE in accordance with some aspects.

[0029] Fig.15 is a flow chart of a method of wireless communication at a base station in accordance with some aspects.

[0030] Fig.16 is a diagram illustrating an example of a hardware implementation for an example apparatus according to some aspects.

[0031] Fig.17 is a diagram illustrating an example of a hardware implementation for an example apparatus according to some aspects. DETAILED DESCRIPTION

[0032] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0033] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic component, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0035] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented with software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage device, magnetic disk storage device, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store instructions or data structure forms that can be accessed by a computer.

[0036] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, specific implementations and / or uses can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. Specific implementations can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0037] Figure 11 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes network entities (e.g., base stations 102), UEs 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

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

[0039] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier 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).

[0040] Some 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 may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0041] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

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

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

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR2-2 and / or FR5, or can be within the EHF band.

[0046] The base station 102, whether a small cell 102' or a large cell (e.g., 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 gNBs, may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UEs 104. When a gNB operates at or near millimeter wave frequencies, the gNB may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0047] Base station 180 may send beamformed signals to 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 send beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different.

[0048] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0049] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming (PSS) service, and / or other IP services.

[0050] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceivers, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client or some other suitable term. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network together and / or individually.

[0051] Reference again Figure 1In certain aspects, the UE 104 may include a single transmit reception point (sTRP) / spatial division multiplexing (SDM) physical uplink shared channel (PUSCH) component 198, which is configured to receive downlink control information (DCI) for scheduling a PUSCH associated with a transmission parameter indicating one of a single transmit reception point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH from a base station; identify an uplink PTRS configuration based on the transmission parameter; and send a PUSCH associated with the identified configuration to the base station based on the transmission parameter, the transmission parameter being based on an association between the identified uplink PTRS configuration and a demodulation reference signal (DMRS) port. In certain aspects, the base station 180 may include a PTRS-DMRS association component 199 configured to send a configuration for an uplink PTRS to a UE; send a DCI to the UE to schedule a PUSCH based on one of sTRP or SDM, the PUSCH being associated with a plurality of transmission parameters; and receive a PUSCH associated with the uplink PTRS configuration from the UE based on the transmission parameters, wherein the plurality of transmission parameters are based on an association between an uplink PTRS and a DMRS port. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0052] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2CIn the example provided, 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, 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 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0053] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of the same size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For conventional CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0054]

[0055] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0056] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0057] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DMRS) (indicated as R for one particular configuration, but other DMRS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PTRS).

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

[0059] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send DM-RS for a physical uplink control channel (PUCCH) and DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0060] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0061] Figure 3 375. The UE 350 is a block diagram of a network entity (e.g., base station 310) in an access network communicating with a UE 350. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting 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 functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

[0063] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0065] Similar to the functions described in conjunction with DL transmissions performed 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 measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 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.

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

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

[0069] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 All aspects related to SDM PUSCH 198.

[0070] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The PTRS-DMRS association component 199 performs various aspects.

[0071] Wireless communication systems can be configured to share available system resources and provide various telecommunication services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA systems, TDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, and TD-SCDMA systems, etc.). In many cases, common protocols that facilitate communication with wireless devices are adopted in various telecommunication standards. For example, communication methods associated with eMBB, mMTC, and ultra-reliable low-latency communications (URLLC) may be incorporated into the 5G NR telecommunication standard, while other aspects may be incorporated into the 4G LTE standard. Since mobile broadband technology is part of the ongoing evolution, further improvements in mobile broadband remain useful for the continued development of such technology.

[0072] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB (gNB), an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0073] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0074] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0075] Figure 4 A diagram illustrating an example decomposed base station 400 architecture is shown. The decomposed base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RU 440 may communicate with respective UEs 450 via one or more radio frequency (RF) access links. In some implementations, a UE 450 may be served simultaneously by multiple RUs 440.

[0076] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0077] In some aspects, CU 410 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 410. CU 410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 410 may be implemented to communicate with DU 430 for network control and signaling.

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

[0079] The lower layer functionality may be implemented by one or more RUs 440. In some deployments, the RU 440 controlled by the DU 430 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 450. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

[0080] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 411) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

[0081] The non-RT RIC 415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 425. The non-RT RIC 415 may be coupled to or communicate with the near-RT RIC 425 (such as via an A1 interface). The near-RT RIC 425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 410, one or more DUs 430, or both, and the O-eNB with the near-RT RIC 425.

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

[0083] Figure 5 5 is a call flow diagram 500 illustrating communication between a UE 502 and a network entity 504. At 506, the network entity 504 may send an uplink PTRS configuration to the UE 502. The uplink PTRS associated with the uplink PTRS configuration may correspond to one or more PTRS ports. The uplink PTRS may be used for phase noise correction, such as phase noise associated with FR2 signaling. At 508, the network entity 504 may send a scheduling DCI to the UE 502 for transmitting the SDM PUSCH. The SDM PUSCH may be associated with different layer sets having different sets of transmission parameters. For example, the different transmission parameters may correspond to different beam parameters, different power control parameters, different transmit precoding matrix indexes (TPMIs), etc.

[0084] At 510, the UE 502 may determine whether the uplink PTRS configuration received at 506 from the network entity 504 and the scheduling DCI received at 508 are associated with 1 PTRS port or 2 PTRS ports. At 512, the UE 502 may perform PTRS-DMRS association differently based on whether 1 PTRS port or 2 PTRS ports are configured. For example, if 1 PTRS port is configured, the PTRS-DMRS association performed at 512 may associate the uplink PTRS with the DMRS port based on a single value indicated in the PTRS-DMRS association field of the scheduling DCI received at 508. However, if 2 PTRS ports are configured, the PTRS-DMRS association performed at 512 may associate the uplink PTRS with the DMRS port based on a plurality of bits included in the PTRS-DMRS association field of the scheduling DCI received at 508. A first bit / a most significant bit (MSB) among the plurality of bits may indicate a first DMRS port, and a second bit / a least significant bit (LSB) among the plurality of bits may indicate a second DMRS port.

[0085] At 514, the UE 502 may map the DMRS ports to beams based on at least one SRS resource set or code division multiplexing (CDM) group. The mapping technique at 514 may be performed by the UE 502 regardless of how the UE 502 performs PTRS-DMRS association at 512 and how the uplink PTRS configuration is identified based on the transmission parameters. At 516, the UE 502 may send an SDM PUSCH to the network entity 504 based on the PTRS-DMRS association performed at 512 and the mapping performed at 514.

[0086] Figure 6 600 is an illustration of an example PTRS-DMRS allocation. PUSCH transmissions from a UE may be codebook-based or non-codebook-based. That is, the PUSCH transmissions may or may not be based on a codebook / matrix used to transform data bits into another data set mapped to the antenna ports of the UE. For codebook-based transmissions, the UE may be configured with an SRS resource set, where the "use" of the SRS resource set may be set to "codebook". Some resource sets used for codebook-based transmissions may be limited to a maximum of 4 SRS resources within the resource set that may be configured for the UE. For example, the UE's communications may be associated with rank 4 or less.

[0087] Each SRS resource may be configured by RRC with a certain number of ports (e.g., via nrofSRS-Ports). The number of ports may correspond to the rank associated with the communication of the UE. The SRS Resource Indicator (SRI) field included in the uplink DCI associated with scheduling the PUSCH may indicate an SRS resource. The number of ports configured for the UE based on the indicated SRS resource may correspond to the number of antenna ports for the PUSCH. The PUSCH may be sent based on the same spatial domain filter (e.g., uplink beam) as the indicated SRS resource. The number of layers that may indicate the rank and the TPMI of the predecoder for the scheduled PUSCH may be determined based on separate DCI fields (e.g., precoding information and number of layers field).

[0088] For non-codebook based transmission, the UE may be configured with an SRS resource set, where the use of the SRS resource set may be set to "non-codebook". Some resource sets for non-codebook based transmission may be limited to a maximum of 4 SRS resources within the resource set that may be configured for the UE. For example, the communication of the UE may be associated with a rank of 4 or less. Unlike codebook based SRS resources, each non-codebook based SRS resource may be associated with a port. Also different from the codebook based configuration, the SRI field included in the uplink DCI associated with the scheduling of PUSCH may indicate one or more SRS resources in the non-codebook based configuration. The number of indicated SRS resources may indicate the rank (i.e., the number of layers) of the scheduled PUSCH. The PUSCH may be transmitted with the same pre-decoder and spatial domain filter (e.g., uplink beam) as the indicated SRS resource.

[0089] The uplink PTRS associated with PTRS port 0 602 may be sent within multiple RBs allocated for PUSCH and may be used for phase noise correction. For example, PTRS may be used to reduce phase noise in FR2 signaling. In diagram 600, the number of allocated RBs is 2 RBs corresponding to RB1 and RB2. PTRS may be sent in PUSCH OFDM symbols that do not include DMRS (e.g., symbols 1 to 3 of diagram 600 that include most of PUSCH data REs 608). In symbols that include DMRS (such as symbol 0), phase noise correction may not be required, and therefore PTRS may not be required to be included in such symbols. PTRS may have sparse frequency allocation. For example, PTRS may be allocated to one frequency tone per port every 2 to 4 RBs. Diagram 600 illustrates the allocation of PTRS to one frequency tone for PTRS port 0 602 on RB1 and RB2.

[0090] Although PTRS allocations may be sparse in the frequency domain, in some cases, PTRS allocations may be dense in the time domain. For example, PTRS may be allocated every other OFDM symbol, every other 2 OFDM symbols, every other 4 OFDM symbols, etc. In diagram 600, PTRS associated with PTRS port 0 602 is allocated every other OFDM symbol without gaps in the time domain. That is, PTRS is allocated to each symbol in symbols 1 to 3. Symbol 0 may not include a PTRS allocation because symbol 0 includes DMRS associated with PUSCH DMRS port 0 604 and PUSCH DMRS port 2 606.

[0091] The allocation of PTRS may be based on RRC configuration (e.g., via the RRC parameter PTRS-UplinkConfig). The maxNrofPorts parameter may be configured for 1 port or 2 ports. For example, 2 PTRS ports may be configured for CP-OFDM waveforms, while 1 PTRS port may be configured for fully coherent UEs. Full coherence may refer to a configuration in which two or more ports (e.g., DMRS ports) are shared between each layer. The actual number of PTRS ports used for non-codebook based configuration (where maxNrofPorts=2) may be based on the value indicated in the SRI field. The SRI field may indicate one or more SRS resources. Each SRS resource may be configured with a PTRS port index. If the SRS resource indicated via the SRI field corresponds to the same value for the PTRS port index, one PTRS port may be configured. Otherwise, 2 PTRS ports may be configured.

[0092] In a codebook-based example associated with a partially coherent or non-coherent UE, the actual number of PTRS ports (where maxNrofPorts=2) may be based on the TPMI indicated via the precoding information and the number of layers field. Partial coherence may refer to a configuration in which two or more ports are shared between some but not all layers of a layer. Non-coherence may refer to a configuration in which each layer is associated with one port.

[0093] Figure 7 PTRS-DMRS association tables 700 to 750 for uplink PTRS ports are illustrated. Table 700 can be used for the case where one uplink PTRS port is configured. For example, PTRS can be sent on the strongest layer (e.g., DMRS port) based on the association with the DMRS port. The determination of the strongest layer can be performed in an instance where more than one layer is scheduled (e.g., more than one DMRS port is available). In an instance where one layer is scheduled, such determination / procedure may not be performed because only one layer is to be selected as the strongest layer. Therefore, PTRS can be sent on one layer / DMRS port. The uplink DCI (e.g., DCI format 0_1, 0_2) may include a PTRS-DMRS association field. This field may include 2 bits, and if uplink PTRS is configured, a CP-OFDM waveform is used (e.g., transform pre-decoder is disabled), and MaxRank>1 is configured. In other configurations, the PTRS-DMRS association field may be excluded.

[0094] If one uplink PTRS port is configured (e.g., PTRS port 0), the value of the bit associated with the PTRS-DRMS association field may indicate the DMRS port associated with the PTRS port. For example, as illustrated in Table 700, a value of 0 may indicate the first scheduled DMRS port, a value of 1 may indicate the second scheduled DMRS port, a value of 2 may indicate the third scheduled DMRS port, and a value of 3 may indicate the fourth scheduled DMRS port. If the PTRS-DMRS association field includes 2 bits, the value of the bit used to perform PTRS-DMRS association may correspond to the second bit. Since a PTRS port is not associated with more than one DMRS port, the first of the 2 bits may be ignored.

[0095] If multiple uplink PTRSs are configured (e.g., PTRS port 0 and PTRS port 1), a first bit of the 2 bits included in the PTRS-DMRS association field may indicate a first DMRS port of the multiple DMRS ports that share PTRS port 0, and a second bit of the 2 bits included in the PTRS-DMRS association field may indicate a second DMRS port of the multiple DMRS ports that share PTRS port 1. To determine which DMRS ports share which PTRS ports, the first bit may correspond to the value of the MSB, and the second bit may correspond to the value of the LSB, as illustrated in Table 750. If the first bit / MSB has a value of 0, the first DMRS port may share PTRS port 0. If the first bit / MSB has a value of 1, the second DMRS port may share PTRS port 0. Similarly, if the second bit has a value of 0, the first DMRS port may share PTRS port 1. If the second bit has a value of 1, the second DMRS port may share PTRS port 1. Therefore, the first bit / MSB can be used to identify which DMRS ports share PTRS port 0 based on the value of the first bit / MSB (e.g., value 0 = first DMRS port; value 1 = second DMRS port), and the second bit / LSB can be used to identify which DMRS ports share PTRS port 1 based on the value of the second bit / LSB (e.g., value 0 = first DMRS port; value 1 = second DMRS port).

[0096] For non-codebook based uplink PTRS, the SRI field may indicate one or more SRS resources. A one-to-one mapping between the indicated SRS resources and the indicated DMRS ports may be performed via the antenna port field. Each SRS resource may be configured with a PTRS port index. For example, SRS resource [0,1] may be configured with PTRS port 0 by RRC, and SRS resource [2,3] may be configured with PTRS port 1 by RRC. The SRI field of the DCI may indicate 4 SRS resources. The antenna port field of the DCI may indicate which DMRS ports share which PTRS ports. For example, DMRS ports 0 to 1 may share PTRS port 0, and DMRS ports 2 to 3 may share PTRS port 1. The PTRS-DMRS association field of the DCI may indicate a PTRS-DMRS association.

[0097] For codebook-based uplink PTRS, where the configuration may be associated with partially coherent UEs or non-coherent UEs, the TPMI may indicate a PTRS-DRMS association. For example, the TPMI may indicate that PUSCH antenna ports 1000 and 1002 share PTRS port 0, and PUSCH antenna ports 1001 and 1003 share PTRS port 1. A DMRS port may correspond to a layer transmitted with a PUSCH antenna port. For example, PUSCH antenna port 1000 and PUSCH antenna port 1002 are indicated via the TPMI as sharing PTRS port 0.

[0098] Figure 8 8 is a diagram illustrating a TPMI matrix indicating PTRS-DMRS association. Diagram 700 illustrates 4 PUSCH antenna ports and 3 layers corresponding to 3 DMRS ports. Based on the non-zero values ​​included in the corresponding rows of the TPMI matrix, the first layer / first DMRS port is associated with PUSCH antenna ports 1000 and 1002. Based on the value 1 included in the second row of the TPMI matrix, the second layer / second DMRS port is associated with PUSCH antenna port 1001. Based on the value 1 included in the fourth row of the TPMI matrix, the third layer / third DMRS port is associated with PUSCH antenna port 1003.

[0099] The precoding information and layer number field included in the DCI may indicate that the number of layers is 3 and the TPMI index is 2, which may correspond to the TPMI matrix illustrated in diagram 800. The antenna port field may indicate that DMRS ports 0 to 2 (e.g., the first DMRS port to the third DMRS port) correspond to the three layers illustrated in diagram 800. Since the first layer / DMRS port 0 shares PTRS port 0, the first layer / DMRS may be transmitted using PUSCH antenna ports 1000 and 1002. Since the second layer / DMRS port 1 and the third layer / DMRS port 2 share PTRS port 1, the second layer may be transmitted using PUSCH antenna port 1001, and the third layer may be transmitted using PUSCH antenna port 1003.

[0100] If a DMRS port shares a PTRS port, the first bit of the PTRS-DMRS Association field may not be used. However, the second bit of the PTRS-DMRS Association field may indicate which DMRS port is associated with the PTRS port from among the DMRS ports that share the PTRS port. To map PTRS to RE. For DMRS configuration type 1, PTRS may be mapped to DMRS ports 0 to 3. For DMRS configuration type 2, PTRS may be mapped to ports 0 to 5. That is, DMRS configuration type 1 may be associated with rank 4 or less, and DMRS configuration type 2 may be associated with ranks 1 to 4+.

[0101] Spatial division multiplexing (SDM) for PUSCH may provide different layer sets with different transmission parameters. For example, different layer sets may be associated with different beams, different power control parameter sets, different TPMIs, etc. In addition, rank combinations such as 1+1, 1+2, 2+1, and 2+2 may be supported in association with SDM PUSCH based on the PTRS-DMRS association being explicitly indicated to the UE.

[0102] Configurations associated with different layer sets may follow different protocols than configurations associated with a single beam. If a UE is configured with uplink PTRS and the UE receives a DCI scheduling an SDM PUSCH with a different set of transmit parameters (e.g., different beams, different sets of power control parameters, different TPMIs, etc.), the UE may separately determine the PTRS-DMRS associations for different layers / DMRS port sets. If two PTRS ports are configured, the 2 bits included in the PTRS-DMRS Association field of the DCI may be used to indicate which DMRS ports are associated with which PTRS ports. For example, the 2 bits may indicate which of the DMRS ports share PTRS port 0 and which of the DMRS ports share PTRS port 1.

[0103] For a codebook-based configuration associated with 2 TPMIs, DMRS ports associated with the first TPMI / first SRS resource set may share PTRS port 0, and DMRS ports associated with the second TPMI / second SRS resource set may share PTRS port 1. Thus, the first bit may indicate a PTRS-DMRS association for a DMRS port associated with the first TPMI / SRS resource set, and the second bit may indicate a PTRS-DMRS association for a different DMRS port associated with the second TPMI / second SRS resource set. For a non-codebook-based configuration, DMRS ports associated with the first SRS resource set (e.g., SRS resources indicated via the first SRI and selected from the first SRS resource set) may share PTRS port 0. DMRS ports associated with the second SRS resource set (e.g., SRS resources indicated via the second SRI and selected from the second SRS resource set) may share PTRS port 1.

[0104] If one PTRS port is configured, then 2 bits in the PTRS-DMRS association field of the DCI may be used to indicate which DMRS ports are associated with the PTRS based on the value of a single bit (such as the second bit). For example, values ​​0 to 3 may indicate the first DMRS port to the fourth DMRS port, respectively, as shown in Tables 800 and Fig. 9 As illustrated in Tables 900 to 950 shown. The mapping from DMRS ports to beams may be based on CDM groups, SRS resource sets, etc. For example, based on CDM groups, DMRS ports associated with a first CDM group may correspond to a first beam, and DMRS ports associated with a second CDM group may correspond to a second beam.

[0105] In a first example associated with a codebook-based PUSCH, the UE may have 4 antenna ports, a rank combination of 2+2, and 2 PTRS ports. TPMI 0 may be indicated for the first two layers, and TPMI 2 may be indicated for the second two layers. Therefore, the 2 bits in the PTRS-DMRS association field of the DCI may correspond to '01'. The first DMRS port and the second DMRS port (e.g., associated with the first TPMI) may share PTRS port 0. Similarly, the third DMRS port and the fourth DMRS port (e.g., associated with the second TPMI) may share PTRS port 1. Since the MSB is 0, the first DMRS port may be associated with PTRS port 0. Since the LSB is 1, the fourth DMRS port may be associated with PTRS port 1.

[0106] In a second example associated with non-codebook based PUSCH, the UE may have 4 antenna ports, the first SRS resource set may have two SRS resources [0, 1], and the second SRS resource set may have another two SRS resources [2, 3]. The antenna port field of the DCI may indicate that SRS resources 0 to 3 correspond to the first DMRS port to the fourth DMRS port, where SRS resources [0, 1] may share PTRS port 0, and SRS resources [2, 3] may share PTRS port 1. If 2 bits in the PTRS-DMRS association field of the DCI correspond to '10', DMRS port 1 may be associated with PTRS port 0, and DMRS port 2 may be associated with PTRS port 1.

[0107] Fig. 9 PTRS-DMRS association tables 900 to 950 for uplink PTRS ports are illustrated. In some configurations, 4 layers (e.g., DMRS ports) may be utilized across two beams. However, for single TRP (e.g., sTRP) or multi-TRP transmission (e.g., SDM), other uplink configurations may include a rank greater than 4 (e.g., rank 8). For example, tables 900 to 950 may be used in association with a rank greater than 4. Thus, in addition to rank combinations 1+1, 1+2, 2+1, and 2+2, some configurations may be extended to include additional rank combinations such as rank combinations 2+3, 3+2, 3+3, 3+4, 4+3, and 4+4 (e.g., with or without restrictions on mapping PTRS to REs).

[0108] Table 900 may be used for PTRS-DMRS associations for configurations that do not include mapping restrictions from PTRS to RE. The values ​​listed in Table 900 may be indicated via the PTRS-DMRS association field and may correspond to the respective scheduled DMRS ports. The PTRS-DMRS association may also be associated with the reserved field in Table 900.

[0109] For SDM PUSCH, a PTRS port may be associated with one of the two beams. The mapping from DMRS ports to beams may be based on a CDM group, an SRS resource set, etc. If one PTRS port is configured, an enhanced PTRS-DMRS association field of the DCI (e.g., which includes 4 bits) may be used to indicate which DMRS port is associated with the PTRS port. For example, an enhanced PTRS-DMRS association may be performed based on Table 900 to associate the PTRS with one DMRS port, where the rank / number of configured DMRS ports may be greater than 4 (e.g., rank 8). That is, the PTRS-DMRS association field may indicate a DMRS port to be associated with the PTRS port (e.g., selected from 8 DMRS ports). If multiple PTRS ports are configured, a first set of 2 bits and a second set of 2 bits (e.g., a total of 4 bits) may be included in the PTRS-DMRS association field of the DCI to indicate the association, rather than including the first bit separately and the second bit separately as used in a rank 4 configuration.

[0110] For configurations associated with restrictions for mapping PTRS to REs, and in the case where one PTRS port is configured, the PTRS-DMRS association may be based on the DMRS configuration type. For DMRS configuration type 1, the 2-bit PTRS-DMRS association field of the DCI may indicate a PTRS-DMRS association table (such as DMRS_CONFIG_DCI_PT ... Figure 7 950). For DMRS configuration type 2, the enhanced 3-bit PTRS-DMRS association field of the DCI may indicate a value associated with a higher-rank PTRS-DMRS association table (e.g., table 950) used to determine which DMRS port is associated with the PTRS. Table 950 includes values ​​that may be indicated via the PTRS-DMRS association field and corresponding scheduled DMRS ports corresponding to these values. The PTRS-DMRS association may also be associated with one or more of the reserved fields of table 950.

[0111] For SDM PUSCH, a PTRS port may correspond to two beams. Similar to the mapping for one beam, the mapping of DMRS ports to two beams may be based on a CDM group, an SRS resource set, etc. If two PTRS ports are configured, then for DMRS configuration type 1, the PTRS port may be associated with the first DMRS port to the fourth DMRS port. For DMRS configuration type 2, a first set of 2 bits and a second set of 2 bits (e.g., a total of 4 bits) may be included in the PTRS-DMRS association field of the DCI to indicate the association, rather than including the first bit separately and the second bit separately as used in the rank 4 configuration. Restrictions on the PTRS-DMRS association may include that certain rank combinations may not be configured, for example, rank combinations 3+4, 4+3, 4+4. Such indications may be based on Table 950.

[0112] In some examples, a time division multiplexed (TDM) PUSCH may be scheduled in a DCI for a PTRS port to be associated with one of the two beams. The mapping from DMRS ports to beams may be based on CDM groups, SRS resource sets, etc. TDM is used to allow repeated scheduling of PUSCH in a single DCI to specify different transmission parameters. Fig.10 A single DCI based PUSCH repetition configuration according to some aspects of the present disclosure is illustrated. In this example, a UE (e.g., 502) receives a scheduling DCI 1002 from a network entity (e.g., 504), where the DCI schedules 4 PUSCH repetitions 1004, 1006, 1008, and 1010, as shown. The repetitions (1004 to 1006) may be scheduled such that a first set of repetitions 1004, 1008 may be associated with a first set of SRS resources 912 for a first beam having a first set of power control parameters targeting a first TRP. A second set of repetitions 1006, 1010 may be associated with a second set of SRS resources 914 for a second beam having a first set of power control parameters targeting a second TRP.

[0113] Thus, the DCI 1002 may configure PUSCH repetitions for multiple SRS resource sets, where each PUSCH repetition has its own corresponding parameters (e.g., beam, spatial resolution, TCI state, power control, precoding). In some examples, different repetitions may be associated with the same TB. For both codebook-based and non-codebook-based PUSCH, the DCI may use two corresponding SRI fields to indicate two beam or power control parameter sets. For codebook-based PUSCH, two TPMI fields may be included to indicate two precoders for two repetition sets.

[0114] In some examples, a UE (e.g., 502) may be configured using DCI to dynamically switch uplink PTRS between multiple transmission parameters for PUSCH. Using SRS resources, a UE may dynamically switch between single TRP (sTRP) based PUSCH and multiple TRP (e.g., SDM) based PUSCH, where PUSCH is associated with multiple transmission parameters. Fig.10 Block diagram 1000 for scheduling PUSCH for single TRP and multi-TRP configurations according to some aspects of the present disclosure is illustrated.

[0115] As discussed above, the allocation of PTRS may be based on an RRC configuration, where the maxNrofPorts parameter may be configured for 1 port or 2 ports for fully coherent, partially coherent, or non-coherent UEs. The actual number of PTRS ports for non-codebook based configuration (where maxNrofPorts = 2) may be based on the value indicated in the SRI field. The SRI field may indicate one or more SRS resources. Each SRS resource may be configured with a PTRS port index. If the SRS resources indicated via the SRI field correspond to the same value for the PTRS port index, one PTRS port may be configured. Otherwise, 2 PTRS ports may be configured.

[0116] exist Fig.11 In the example of , a UE (e.g., 502) may be configured with a first SRS resource set 1102 and a second SRS resource set 1110, wherein the first SRS resource set 1102 is configured with a PTRS port index setting 1104 ("PTRS port index 0", "PTRS port index 1") associated with two SRS resources 1106, 1108. Similarly, the second SRS resource set 1110 is configured with a PTRS port index setting 1112 ("PTRS port index 0", "PTRS port index 1") associated with two SRS resources 1114, 1116. Here, the UE is configured with multiple PTRS ports (maxNrofPorts=2) and is also configured with 2 SRS resource sets with usage for SDM set to "nonCodebook". In this case, the UE will assume that the port index for all SRS resources in the first SRS resource set 1102 is set to "zero" 1118 (PTRS port index = 0), and the SRS resources in the second SRS resource set 1110 are set to "one", where the SRS resources within the corresponding SRS resource set are configured with the same PTRS port. When the UE is scheduled with sTRP PUSCH via one of the resource sets (e.g., SRS resource set 1110), the UE operates using the resource set as if the actual number of PTRS ports is 1, because the SRS resources within a given SRS resource set are configured with the same PTRS port.

[0117] exist Fig.11 In another example illustrated, if a UE (e.g., 502) is scheduled for SDM PUSCH (as opposed to sTRPPUSCH), the UE ignores all PTRS port index settings (1104, 1112) of one of the SRS resources (1106 to 1108, 1114 to 1116) of the first SRS resource set 1102 or the second SRS resource set 1110. Using this configuration, the UE can be configured for SDM PUSCH or sTRP PUSCH (e.g., associated with only one of the SRS resource sets). Therefore, within a given SRS resource set 1102, 1110, some SRS resources can be configured with a PTRS port index of 0, while other SRS resources are configured with a PTRS port index of 1. Moreover, depending on the SRI indicated in the DCI that schedules the sTRP PUSCH, the actual number of PTRS ports can be 1 or 2. At the same time, for scheduling SDM PUSCH, the UE may assume that all SRS resources in the first SRS resource set are associated with the first PTRS port and all SRS resources in the second SRS resource set are associated with the second PTRS port, regardless of the actual configuration of the PTRS port index. In other words, when two SRS resource sets are indicated, the port index configuration of the SRS resources is ignored by the UE for SDM PUSCH, and when only one SRS resource set in the SRS resource set is indicated, the port index configuration of the SRS resources is used by the UE for sTRP PUSCH.

[0118] During operation, if one PTRS port is configured, the UE may associate the uplink PTRS with one of the DMRS ports based on the value included in the PTRS-DMRS association field of the DCI. Figure 5 and Figure 7 At 512, UE 502 may perform PTRS-DMRS association based on determining at 510 that 1 PTRS port is configured. PTRS-DMRS association table 700 may be used to associate the value included in the PTRS-DMRS association field of the DCI with the DMRS port. If 2 PTRS ports are configured, the UE may associate the uplink PTRS with the DMRS port based on a number of bits included in the PTRS-DMRS association field of the DCI. For example, referring to Figure 5 and Figure 7At 512, UE 502 may perform PTRS-DMRS association based on determining at 510 that two PTRS ports are configured. PTRS-DMRS association table 650 may be used to associate the values ​​of the two bits included in the PTRS-DMRS association field of the DCI with the DMRS ports.

[0119] In some examples, a first PTRS port may be shared by one or more first DMRS ports, and a second PTRS port may be shared by one or more second DMRS ports, where the DMRS port is included in the one or more first DMRS ports or the one or more second DMRS ports. As illustrated in the PTRS-DMRS association table 750, a first bit of the plurality of bits may indicate a first DMRS port of the one or more first DMRS ports, and a second bit of the plurality of bits may indicate a second DMRS port of the one or more second DMRS ports. As further illustrated in the PTRS-DMRS association table 750, a first bit of the plurality of bits may be an MSB, and a second bit of the plurality of bits may be an LSB. The UE may map the DMRS ports to beams based on the SRS resource set. For example, referring to Figure 5 At 514, UE 502 may map DMRS ports to beams based on the SRS resource set.

[0120] Fig.12 A block diagram 1200 is illustrated for scheduling PUSCH using multiple PTRS configurations for single TRP and multi-TRP configurations according to some aspects of the present disclosure. In this example, a UE (e.g., 502) may receive a first SRS resource set 1202 and a second SRS resource set 1204, similar to Fig.11 . The first SRS resource set 1202 includes SRS resources 1206, 1208 and two PTRS port index configurations 1204, 1210, wherein the first PTRS port index configuration 1204 is associated with sTRP PUSCH and the second PTRS port index configuration 1210 is associated with SDM PUSCH. The second SRS resource set 1212 similarly includes SRS resources 1216, 1218 and two PTRS port index configurations 1214, 1220, wherein the first PTRS port index configuration 1214 is associated with sTRP PUSCH and the second PTRS port index configuration 1220 is associated with SDM PUSCH.

[0121] Fig.12The configuration allows the UE to be configured with two PTRS configurations 1222, 1224 via RRC (PTRS-UplinkConfig). Each PTRS configuration may include a maximum number of ports (maxNrofPorts), frequency domain and / or time domain density, RE offset, PTRS power, etc. When scheduling sTRP PUSCH, sTRP PUSCH 1222 is associated with only one resource set in the resource set, while the second PTRS configuration 1224 for SMD PUSCH associates the first layer set with the first SRS resource set (1202), and the second layer set with the second SRS resource set (1212). In some examples, the corresponding PTRS configuration (1222, 1224) is used depending on whether the DCI schedules sTRP PUSCH or schedules SDM PUSCH. In addition, for non-codebook based PUSCH, each SRS resource (in the first set or in the second set) may be configured with two PTRS port index values, one of which is specific to sTRPPUSCH and the other is specific to SDM PUSCH.

[0122] The UE may therefore configure the maximum number of ports to be "one" (maxNrofPorts=1) for sTRP PUSCH scheduling and to be "two" (maxNrofPorts=2) for SDM PUSCH scheduling, or vice versa. Alternatively or in addition, the UE may assume that the SRS resources within the corresponding SRS resource set are configured with the same PTRS ports for sTRP PUSCH. In the case where SDM supports more than 2 PTRS ports, Fig.12 The configuration allows the UE to configure the maximum number of ports for sTRP PUSCH to one or two (maxNrofPorts=1 or maxNrofPorts=2), regardless of the maximum number of PTRS ports configured for SDM (e.g., maxNrofPorts=4 for SDM PUSCH).

[0123] Fig.13 A block diagram 1300 is illustrated for scheduling PUSCH using multiple PTRS configurations for single TRP and multi-TRP configurations according to some aspects of the present disclosure. In this example, a UE (e.g., 502) may receive a first SRS resource set 1302 and a second SRS resource set 1310, similar to Fig.11. The first SRS resource set 1302 includes SRS resources 1306, 1308 and a corresponding PTRS port index configuration 1304. The second SRS resource set 1310 similarly includes SRS resources 1314, 1316 and a corresponding PTRS port index configuration 1312. Here, the UE is configured (PTRS-UplinkConfig) with separate PTRS configurations 1304, 1312 specific to the first SRS resource set 1302 and the second SRS resource set 1310. Therefore, when the sTRP PUSCH is scheduled, the PUSCH is associated with only one SRS resource set, and the corresponding PTRS configuration is used depending on which SRS resource set is indicated. As an example, when only the first SRS resource set 1302 is indicated for sTRP, the maximum number of ports can be two, as shown in box 1318. In another example, when only the second SRS resource set 1304 is indicated for sTRP, the maximum number of ports can be one, as shown in box 1320.

[0124] In another example, when two SRS sets (1302, 1310) are indicated (e.g., for SDM), the maximum number of PTRS ports can be three. During SDM PUSCH, the first layer set is associated with the first SRS resource set 1302, and the second layer set is associated with the second SRS resource set 1310. When scheduling SDM PUSCH, two PTRS configurations are used. As in the examples above, each PTRS configuration (1304, 1312) may include a maximum number of ports, frequency / time domain density, RE offset, PTRS power, etc. In some examples, the frequency / time domain density and RE offset may be configured to have the same value to avoid non-uniform mapping of different PTRS ports to REs. In some examples, Fig.13 The configuration may allow up to 4 PTRS ports for SDM PUSCH and asymmetry across the two SRS resource sets (e.g., up to 2 PTRS ports associated with the first SRS resource set and up to 1 PTRS port associated with the second SRS resource set).

[0125] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 502), which may include memory 360, and the UE may be the entire UE 104 / 502 or a component of the UE 104 / 502 (such as TX processor 368, RX processor 356 and / or controller / processor 359).

[0126] At 1402, the UE may receive a plurality of configurations for uplink PTRS from a network entity. Figure 5At 506, UE 502 may receive an uplink PTRS configuration from network entity 504. The reception at 1402 may be performed by Fig.16 The receiving component 1630 of the device 1602 is executed.

[0127] At 1404, the UE may receive from a network entity downlink control information (DCI) for scheduling a PUSCH associated with transmission parameters indicating one of an sTRP physical uplink shared channel (PUSCH) or an SDM PUSCH. Figure 5 At 508, UE 502 may receive a scheduling DCI for one of sTRP or SDM PUSCH from network entity 504. sTRP / SDM PUSCH may be associated with different parameters for beams, power control, TPMI, etc. The reception at 1404 may be performed by Fig.16 The receiving component 1630 of the device 1602 is executed.

[0128] At 1406, the UE may identify the uplink PTRS configuration based on the transmitted parameters. Figure 5 At 512, UE 502 may identify one or more uplink PTRS configurations based on the transmission parameters for one of sTRP or SDM PUSCH. The identification at 1406 may be performed by Fig.16 The ID / association component 1640 of the device 1602 is executed.

[0129] At 1408, the UE may send a PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on the association between the identified one or more uplink PTRS configurations and the DMRS ports. Figure 5 At 516, UE 502 may transmit a PUSCH associated with the identified configuration to base station 504 based on the identified uplink PTRS configuration and DMRS port 512. The transmission at 1408 may be performed by Fig.16 The sending component 1634 of the device 1602 is executed.

[0130] Fig.151500 is a flow chart of a method of wireless communication. The method may be performed by a network entity (e.g., a base station 102 / 504; an apparatus 1702; etc.), which may include a memory 376, and the network entity may be the entire base station 102 / 504 or a component of the base station 102 / 504 (such as a TX processor 316, an RX processor 370, and / or a controller / processor 375). The network entity may also be implemented in a converged or monolithic base station architecture, or in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0131] In block 1502, the network entity may transmit multiple configurations for uplink PTRS. In block 1504, the network entity may transmit DCI for scheduling a PUSCH associated with a transmit parameter indicating one of a sTRP PUSCH or a SDM PUSCH. In some examples, the transmitting component 1734 of the network entity 1702 and the communication manager 1732 may act as a means for transmitting multiple configurations for uplink PTRS and for transmitting a DCI for scheduling a PUSCH associated with a transmit parameter indicating one of a sTRP PUSCH or a SDM PUSCH.

[0132] In block 1506, the network entity may receive, for example, from the UE, a PUSCH associated with the identified one or more uplink PTRS configurations based on the transmission parameters, wherein the PUSCH is based on an association between the identified one or more uplink PTRS configurations and a DMRS port. In some examples, the receiving component 1730 of the network entity 1702 and the communication manager 1732 and the PTRS-DMRS associating component 1740 may function as a means for receiving, based on the transmission parameters, a PUSCH associated with the identified one or more uplink PTRS configurations, wherein the PUSCH is based on an association between the identified one or more uplink PTRS configurations and a DMRS port.

[0133] Fig.161600 is a diagram illustrating an example of a hardware implementation for an apparatus 1602. The apparatus 1602 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1602 may include a cellular baseband processor 1604 (also referred to as a modem) coupled to a cellular RF transceiver 1622. In some aspects, the apparatus 1602 may also include one or more subscriber identity modules (SIM) cards 1620, an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610, a Bluetooth module 1612, a wireless local area network (WLAN) module 1614, a global positioning system (GPS) module 1616, or a power source 1618. The cellular baseband processor 1604 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1622. The cellular baseband processor 1604 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1604 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1604, causes the cellular baseband processor 1604 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1604 when executing the software. The cellular baseband processor 1604 also includes a receiving component 1630, a communication manager 1632, and a sending component 1634. The communication manager 1632 includes one or more illustrated components. The components within the communication manager 1632 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1604. The cellular baseband processor 1604 may be a component of the UE 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1602 may be a modem chip and include only the baseband processor 1604, and in another configuration, the apparatus 1602 may be the entire UE (e.g., see Figure 3 350) and includes additional modules of device 1602.

[0134] The receiving component 1630 is configured to (for example, in combination with Fig.14 The method further comprises: receiving a configuration for an uplink PTRS from a network entity; and receiving a DCI for scheduling a PUSCH based on one of sTRP or SDM from a base station, wherein the PUSCH is associated with a plurality of transmission parameters. The transmission component 1634 is configured to transmit a PUSCH associated with a plurality of transmission parameters to a network entity based on an association between an uplink PTRS and a DMRS port (e.g., as described in conjunction with 1408).

[0135] The communication manager 1532 includes an ID / association component 1640, which can be configured to identify the uplink PTRS configuration based on the transmission parameters (e.g., as described in conjunction with 1406), and associate the uplink PTRS with one of the DMRS ports based on a value included in a PTRS-DMRS association field of the DCI. The communication manager 1632 also includes a mapper component 1642, which is configured to map the DMRS port to a beam based on an SRS resource set.

[0136] The device may include executing Fig.14 Each box in the flowchart of the algorithm is an additional component. Therefore, Fig.14 Each block in the flowchart of can be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0137] As shown, the apparatus 1602 may include various components configured for various functions. In one configuration, the apparatus 1602, and in particular the cellular baseband processor 1604, includes a component for receiving a plurality of configurations for uplink PTRS from a network entity; a component for receiving a DCI for scheduling a PUSCH associated with a transmit parameter indicating one of an sTRP PUSCH or an SDM PUSCH from the network entity; a component for identifying one or more uplink PTRS configurations based on the transmit parameter; and a component for sending a PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on an association between the identified one or more uplink PTRS configurations and a DMRS port.

[0138] These means may be one or more of the components of the apparatus 1602 configured to perform the functions recited by these means. As described above, the apparatus 1602 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, these means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by these means.

[0139] Fig.171700 is a diagram illustrating an example of a hardware implementation for an apparatus 1702. The apparatus 1702 may be a network entity, a component of a network entity, or may implement network entity functionality. For example, the apparatus 1702 may be implemented in an aggregated or monolithic base station architecture, or in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the apparatus 1702 may include a baseband unit 1704. The baseband unit 1704 may communicate with the UE 104 via a cellular RF transceiver 1722. The baseband unit 1704 may include a computer-readable medium / memory. The baseband unit 1704 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 1704, causes the baseband unit 1704 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 1704 when executing software. The baseband unit 1704 also includes a receiving component 1730, a communication manager 1732, and a transmitting component 1734. The communication manager 1732 includes one or more illustrated components. The components within the communication manager 1732 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1704. The baseband unit 1704 may be a component of the base station 310 and may include a memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375.

[0140] The communication manager 1732 includes a PTRS-DMRS association component 1740, which is configured to (e.g., as in conjunction with Fig.15 The invention discloses a method for transmitting a PUSCH associated with one or more uplink PTRS configurations identified by the wireless communication system; and receiving a PUSCH associated with one or more uplink PTRS configurations identified based on the transmission parameters, wherein the PUSCH is based on an association between the one or more uplink PTRS configurations identified and a DMRS port.

[0141] The device may include executing Fig.15 Each box in the flowchart of the algorithm is an additional component. Therefore, Fig.15Each block in the flowchart of can be performed by a component, and the device may include one or more of these components. These components can be one or more hardware components, which are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0142] As shown, the apparatus 1702 may include various components configured for various functions. In one configuration, the apparatus 1702, and in particular the baseband unit 1704, includes means for transmitting a plurality of configurations for uplink PTRS; means for transmitting a DCI for scheduling a PUSCH associated with a transmit parameter indicating one of an sTRP PUSCH or an SDM PUSCH; and means for receiving a PUSCH associated with one or more identified uplink PTRS configurations based on the transmit parameter, wherein the PUSCH is based on an association between the one or more identified uplink PTRS configurations and a DMRS port.

[0143] These means may be one or more of the components of the apparatus 1802 configured to perform the functions recited by these means. As described above, the apparatus 1802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, these means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by these means.

[0144] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

[0145] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless specifically so stated, but "one or more". Terms such as "if", "when ......" and "while ......" should be interpreted as "under the conditions of ......", rather than meaning an immediate time relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be disclosed to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be construed as a part-plus-function unless the element is explicitly stated using the phrase "component for..."

[0146] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0147] Aspect 1 is a user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: receive multiple configurations for an uplink phase tracking reference signal (PTRS) from a network entity; receive downlink control information (DCI) for scheduling a PUSCH associated with a transmission parameter indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH from the network entity; identify one or more uplink PTRS configurations based on the transmission parameters; and send the PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

[0148] Aspect 2 may be combined with aspect 1 and includes: the multiple configurations for the PTRS include a first sounding reference signal (SRS) resource set and a second SRS resource set.

[0149] Aspect 3 may be combined with any one of Aspects 1 and / or 2, and includes: the multiple configurations for the PTRS include PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

[0150] Aspect 4 can be combined with any one of Aspects 1 to 3, and includes: the at least one processor is also configured to identify the uplink PTRS configuration as having a PTRS port in response to the DCI indicating the sTRP PUSCH.

[0151] Aspect 5 can be combined with any one of Aspects 1 to 4 and includes: the at least one processor is also configured to identify the uplink PTRS configuration as using one of the first SRS resource set or the second SRS resource set in response to the DCI indicating the sTRP PUSCH.

[0152] Aspect 6 can be combined with any one of Aspects 1 to 5 and includes: the at least one processor is also configured to identify the uplink PTRS configuration by associating one PTRS port with the first SRS resource set and associating another PTRS port with the second SRS resource set in response to the DCI indicating the SDM PUSCH.

[0153] Aspect 7 can be combined with any one of aspects 1 to 6, and includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH

[0154] Aspect 8 can be combined with any one of Aspects 1 to 7, and includes: the at least one processor is also configured to identify the uplink PTRS configuration as having the first PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to identify the uplink PTRS configuration as having the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

[0155] Aspect 9 may be combined with any one of Aspects 1 to 8, and includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

[0156] Aspect 10 can be combined with any one of Aspects 1 to 9, and includes: the at least one processor is also configured to identify the uplink PTRS configuration as having the first PTRS port index configuration or the second PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to identify the uplink PTRS configuration as having the first PTRS port index configuration and the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

[0157] Aspect 11 may be combined with any one of aspects 1 to 10, and includes: the at least one processor is further configured to map the DMRS port to a beam based on at least one of the SRS resource sets.

[0158] Aspect 12 may be combined with any one of aspects 1 to 11, and includes: the multiple configurations for PTRS include at least one of a maximum number of ports, frequency domain density, time domain density, resource element (RE) offset, and PTRS power.

[0159] Aspect 13 may be combined with any one of aspects 1 to 12, and includes: the at least one processor is further configured to associate the uplink PTRS with the DMRS port based on a plurality of bits included in a PTRS-DMRS association field of the DCI.

[0160] Aspect 14 can be combined with any one of Aspects 1 to 13, and includes: one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

[0161] Aspect 15 is a method for wireless communication of a user equipment (UE), the method comprising: receiving multiple configurations for an uplink phase tracking reference signal (PTRS) from a network entity; receiving downlink control information (DCI) for scheduling a PUSCH associated with transmission parameters indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH from the network entity; identifying one or more uplink PTRS configurations based on the transmission parameters; and sending the PUSCH associated with the identified one or more uplink PTRS configurations to the network entity based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

[0162] Aspect 16 may be combined with Aspect 15, and includes: the plurality of configurations for the PTRS includes a first sounding reference signal (SRS) resource set and a second SRS resource set.

[0163] Aspect 17 may be combined with any one of Aspects 15 and / or 16, and includes: the multiple configurations for the PTRS include PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

[0164] Aspect 18 may be combined with any one of Aspects 15 to 17, and further comprises: identifying the uplink PTRS configuration as having one PTRS port in response to the DCI indicating the sTRPPUSCH.

[0165] Aspect 19 can be combined with any one of Aspects 15 to 18, and also includes: identifying the uplink PTRS configuration as using one of the first SRS resource set or the second SRS resource set in response to the DCI indicating the sTRPPUSCH.

[0166] Aspect 20 can be combined with any one of Aspects 15 to 19, and also includes: identifying the uplink PTRS configuration by associating one PTRS port with the first SRS resource set and associating another PTRS port with the second SRS resource set in response to the DCI indicating the SDM PUSCH.

[0167] Aspect 21 can be combined with any one of Aspects 15 to 20, and also includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH.

[0168] Aspect 22 can be combined with any one of Aspects 15 to 21, and also includes: identifying the uplink PTRS configuration as having the first PTRS port index configuration in response to the DCI indicating the sTRPPUSCH, and identifying the uplink PTRS configuration as having the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

[0169] Aspect 23 may be combined with any one of Aspects 15 to 22, and further comprises: the PTRS port index configuration comprises a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

[0170] Aspect 24 can be combined with any one of Aspects 15 to 23, and also includes: identifying the uplink PTRS configuration as having the first PTRS port index configuration or the second PTRS port index configuration in response to the DCI indicating the sTRPPUSCH, and identifying the uplink PTRS configuration as having the first PTRS port index configuration and the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

[0171] Aspect 25 may be combined with any one of Aspects 15 to 24, and further comprises: mapping the DMRS ports to beams based on at least one of the SRS resource sets.

[0172] Aspect 26 may be combined with any one of aspects 15 to 25, and further include: the multiple configurations for PTRS include at least one of a maximum number of ports, frequency domain density, time domain density, resource element (RE) offset, and PTRS power.

[0173] Aspect 27 may be combined with any one of aspects 15 to 26, and further comprises associating the uplink PTRS with the DMRS port based on a plurality of bits included in a PTRS-DMRS association field of the DCI.

[0174] Aspect 28 can be combined with any one of Aspects 15 to 27, and also includes: one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

[0175] Aspect 29 is a network entity configured for wireless communication, the network entity comprising: a memory; and at least one processor, the at least one processor coupled to the memory and configured to: send multiple configurations for an uplink phase tracking reference signal (PTRS); send downlink control information (DCI) for scheduling a PUSCH associated with a transmission parameter indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; and receive a PUSCH associated with one or more identified uplink PTRS configurations based on the transmission parameters, wherein the PUSCH is based on an association between the one or more identified uplink PTRS configurations and a demodulation reference signal (DMRS) port.

[0176] Aspect 30 may be combined with Aspect 29, and includes: the plurality of configurations for the PTRS includes a first sounding reference signal (SRS) resource set and a second SRS resource set.

[0177] Aspect 31 may be combined with any one of Aspects 29 and / or 30, and includes: the multiple configurations for the PTRS include PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

[0178] Aspect 32 can be combined with any one of Aspects 29 to 31 and includes: the at least one processor is also configured to receive the PUSCH associated with one or more identified uplink PTRS configurations based on an uplink PTRS configuration identified as having a PTRS port in response to the sent DCI indicating the sTRP PUSCH.

[0179] Aspect 33 can be combined with any one of Aspects 29 to 32, and includes: the at least one processor is also configured to receive the PUSCH associated with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as using one of the first SRS resource set or the second SRS resource set in response to the sent DCI indicating the sTRP PUSCH.

[0180] Aspect 34 can be combined with any one of aspects 29 to 33, and includes: the at least one processor is also configured to receive the PUSCH associated with the identified one or more uplink PTRS configurations based on the association of one PTRS port with the first SRS resource set and the association of another PTRS port with the second SRS resource set in response to the transmitted DCI indicating the SDM PUSCH

[0181] Aspect 35 can be combined with any one of Aspects 29 to 34, and includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH.

[0182] Aspect 36 can be combined with any one of Aspects 29 to 35, and includes: the at least one processor is also configured to receive the PUSCH associated with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to receive the PUSCH associated with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the second PTRS port index configuration in response to the sent DCI indicating the SDM PUSCH.

[0183] Aspect 37 may be combined with any one of Aspects 29 to 36, and includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

[0184] Aspect 38 can be combined with any one of Aspects 29 to 37, and includes: the at least one processor is also configured to receive the PUSCH associated with the identified one or more uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration or the second PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to receive the PUSCH associated with the identified one or more uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration and the second PTRS port index configuration in response to the sent DCI indicating the SDM PUSCH.

[0185] Aspect 39 may be combined with any one of Aspects 29 to 38, and includes mapping the DMRS ports to beams based on at least one of the SRS resource sets.

[0186] Aspect 40 may be combined with any one of aspects 29 to 39, and includes: the multiple configurations for PTRS include at least one of a maximum number of ports, frequency domain density, time domain density, resource element (RE) offset, and PTRS power.

[0187] Aspect 41 may be combined with any one of aspects 29 to 40, and comprises associating the uplink PTRS with the DMRS port based on a number of bits included in a PTRS-DMRS association field of the DCI.

[0188] Aspect 42 can be combined with any one of Aspects 29 to 41, and includes: one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

[0189] Aspect 43 is a method for providing wireless communication for a network entity, the method comprising: sending multiple configurations for an uplink phase tracking reference signal (PTRS); sending downlink control information (DCI) for scheduling a PUSCH associated with transmission parameters indicating one of a single transmit receive point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; and receiving a PUSCH associated with one or more identified uplink PTRS configurations based on the transmission parameters, wherein the PUSCH is based on an association between the one or more identified uplink PTRS configurations and a demodulation reference signal (DMRS) port.

[0190] Aspect 44 may be combined with Aspect 43 and includes: the multiple configurations for the PTRS include a first sounding reference signal (SRS) resource set and a second SRS resource set.

[0191] Aspect 45 may be combined with any one of Aspects 43 and / or 44, and comprises: the plurality of configurations for the PTRS comprises PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

[0192] Aspect 46 can be combined with any one of Aspects 43 to 45, and also includes: in response to the sent DCI indicating the sTRP PUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on an uplink PTRS configuration identified as having a PTRS port.

[0193] Aspect 47 can be combined with any one of Aspects 43 to 46, and also includes: in response to the sent DCI indicating the sTRP PUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as using one of the first SRS resource set or the second SRS resource set.

[0194] Aspect 48 can be combined with any one of Aspects 43 to 47, and also includes: in response to the sent DCI indicating the SDM PUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the association of one PTRS port with the first SRS resource set and the association of another PTRS port with the second SRS resource set.

[0195] Aspect 49 can be combined with any one of Aspects 43 to 48, and also includes: the PTRS port index configuration includes a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH.

[0196] Aspect 50 can be combined with any one of Aspects 43 to 49, and also includes: in response to the DCI indicating the sTRPPUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration, and in response to the sent DCI indicating the SDMPUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the second PTRS port index configuration.

[0197] Aspect 51 may be combined with any one of Aspects 43 to 50, and further comprises: the PTRS port index configuration comprises a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

[0198] Aspect 52 can be combined with any one of Aspects 43 to 51, and also includes: in response to the DCI indicating the sTRPPUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration or the second PTRS port index configuration, and in response to the sent DCI indicating the SDM PUSCH, associating the PUSCH with one or more identified uplink PTRS configurations based on the uplink PTRS configuration identified as having the first PTRS port index configuration and the second PTRS port index configuration.

[0199] Aspect 53 may be combined with any one of Aspects 43 to 52, and further comprises: mapping the DMRS ports to beams based on at least one of the SRS resource sets.

[0200] Aspect 54 may be combined with any one of aspects 43 to 53, and further include: the multiple configurations for PTRS include at least one of a maximum number of ports, frequency domain density, time domain density, resource element (RE) offset, and PTRS power.

[0201] Aspect 55 may be combined with any one of aspects 43 to 54, and further comprises associating the uplink PTRS with the DMRS port based on a plurality of bits included in a PTRS-DMRS association field of the DCI.

[0202] Aspect 56 can be combined with any one of Aspects 43 to 55, and also includes: one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

Claims

1. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: one or more memories; as well as one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to: receiving a plurality of configurations for an uplink phase tracking reference signal (PTRS) from a network entity; receiving, from the network entity, downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) associated with transmission parameters indicating one of a single transmission reception point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; identifying one or more uplink PTRS configurations based on the transmitted parameters; as well as The PUSCH associated with the identified one or more uplink PTRS configurations is sent to the network entity based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port. 2 . The UE of claim 1 , wherein the plurality of configurations for the PTRS comprises a first sounding reference signal (SRS) resource set and a second SRS resource set. 3 . The UE of claim 2 , wherein the plurality of configurations for the PTRS comprises PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

4. The UE according to claim 3, wherein the at least one processor is further configured to identify the uplink PTRS configuration as having one PTRS port in response to the DCI indicating the sTRP PUSCH.

5. A UE according to claim 3, wherein the at least one processor is also configured to identify the one or more uplink PTRS configurations as using one of the first SRS resource set or the second SRS resource set in response to the DCI indicating the sTRP PUSCH.

6. The UE of claim 3, wherein the at least one processor is further configured to identify the one or more uplink PTRS configurations by associating one PTRS port with the first SRS resource set and associating another PTRS port with the second SRS resource set in response to the DCI indicating the SDM PUSCH.

7. The UE according to claim 3, wherein the PTRS port index configuration includes a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH.

8. A UE according to claim 7, wherein the at least one processor is also configured to identify the uplink PTRS configuration as having the first PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to identify the uplink PTRS configuration as having the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

9. The UE of claim 3, wherein the PTRS port index configuration comprises a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

10. A UE according to claim 9, wherein the at least one processor is further configured to identify the uplink PTRS configuration as having the first PTRS port index configuration or the second PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and to identify the uplink PTRS configuration as having the first PTRS port index configuration and the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

11. The UE of claim 2, wherein the at least one processor is further configured to map the DMRS ports to beams based on at least one of the SRS resource sets.

12. The UE of claim 1, wherein the plurality of configurations for PTRS comprises at least one of a maximum number of ports, a frequency domain density, a time domain density, a resource element (RE) offset, and a PTRS power.

13. The UE of claim 1, wherein the at least one processor is further configured to associate the uplink PTRS with the DMRS port based on a plurality of bits included in a PTRS-DMRS association field of the DCI.

14. The UE according to claim 13, wherein one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

15. A method for wireless communication of a user equipment (UE), the method comprising: receiving a plurality of configurations for an uplink phase tracking reference signal (PTRS) from a network entity; receiving, from the network entity, downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) associated with transmission parameters indicating one of a single transmission reception point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; identifying one or more uplink PTRS configurations based on the transmitted parameters; as well as The PUSCH associated with the identified one or more uplink PTRS configurations is sent to the network entity based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

16. The method of claim 15, wherein the plurality of configurations for the PTRS comprises a first sounding reference signal (SRS) resource set and a second SRS resource set. 17 . The method of claim 16 , wherein the plurality of configurations for the PTRS comprises PTRS port index configurations associated with the first SRS resource set and the second SRS resource set.

18. The method of claim 17, further comprising identifying the uplink PTRS configuration as having one PTRS port in response to the DCI indicating the sTRP PUSCH.

19. The method of claim 17, further comprising identifying the one or more uplink PTRS configurations as using one of the first SRS resource set or the second SRS resource set in response to the DCI indicating the sTRP PUSCH.

20. The method of claim 17, further comprising identifying the one or more uplink PTRS configurations by associating one PTRS port with the first SRS resource set and another PTRS port with the second SRS resource set in response to the DCI indicating the SDM PUSCH.

21. The method of claim 17, wherein the PTRS port index configuration comprises a first PTRS port index configuration associated with the sTRP PUSCH and a second PTRS port configuration associated with the SDM PUSCH.

22. The method according to claim 21 further includes identifying the one or more uplink PTRS configurations as having the first PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and identifying the one or more uplink PTRS configurations as having the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

23. The method of claim 17, wherein the PTRS port index configuration comprises a first PTRS port index configuration associated with the first SRS resource set and a second PTRS port configuration associated with the second resource set.

24. The method according to claim 23 further includes identifying the one or more uplink PTRS configurations as having the first PTRS port index configuration or the second PTRS port index configuration in response to the DCI indicating the sTRP PUSCH, and identifying the one or more uplink PTRS configurations as having the first PTRS port index configuration and the second PTRS port index configuration in response to the DCI indicating the SDM PUSCH.

25. The method of claim 16, further comprising mapping the DMRS ports to beams based on at least one of the SRS resource sets.

26. The method of claim 15, wherein the plurality of configurations for PTRS comprises at least one of a maximum number of ports, a frequency domain density, a time domain density, a resource element (RE) offset, and a PTRS power.

27. The method of claim 15, further comprising associating the uplink PTRS with the DMRS port based on a number of bits included in a PTRS-DMRS association field of the DCI.

28. The method of claim 27, wherein one or more first DMRS ports share a first PTRS port, and one or more second DMRS ports share a second PTRS port, and wherein the DMRS port is included in at least one of the one or more first DMRS ports or the one or more second DMRS ports.

29. A network entity configured for wireless communication, the network entity comprising: one or more memories; as well as one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to: transmitting a plurality of configurations for an uplink phase tracking reference signal (PTRS); transmitting downlink control information (DCI) for scheduling a PUSCH associated with transmission parameters indicating one of a single transmission reception point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; and A PUSCH associated with the identified one or more uplink PTRS configurations is received based on the transmission parameters, wherein the PUSCH is based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

30. A method for wireless communication by a network entity, the method comprising: transmitting a plurality of configurations for an uplink phase tracking reference signal (PTRS); transmitting downlink control information (DCI) for scheduling a PUSCH associated with transmission parameters indicating one of a single transmission reception point (sTRP) physical uplink shared channel (PUSCH) or a spatial division multiplexing (SDM) PUSCH; and A PUSCH associated with the identified one or more uplink PTRS configurations is received based on the transmission parameters, wherein the PUSCH is based on an association between the identified one or more uplink PTRS configurations and a demodulation reference signal (DMRS) port.

Images