PT-RS for UL multi-beam transmission scheme

Abstract

The present disclosure provides systems, apparatus, apparatuses, and methods, including computer programs encoded on a storage medium, for using PT-RS (202) in an uplink multi-beam transmission scheme. The UE (102) receives (408a, 808a) a configuration for a multi-beam PUSCH transmission from a network entity (104). The UE (102) transmits (412, 812) the multi-beam PUSCH transmission and the PT-RS to the network entity (104) based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to a Phase Tracking Reference Signal (PT-RS) for uplink multi-beam transmission. Background Art

[0002] The Third Generation Partnership Project (3GPP) has specified a radio interface called Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes the 5G Core (5GC) network, the 5G Radio Access Network (5G-RAN), and user equipment (UE). Compared to previous generation cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems may generally be configured to provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasting, etc.) based on multiple access technologies (such as orthogonal frequency division multiple access (OFDMA) technologies) that support communication with multiple UEs. The advancement of mobile broadband continues the development of such wireless communication technologies. For example, a phase tracking reference signal (PT-RS) may be implemented for physical uplink shared channel (PUSCH) transmissions to perform phase offset tracking in symbols that do not have a demodulation reference signal (DMRS). However, for PUSCH transmissions using multiple beams, the complexity associated with determining which PT-RS ports and which DMRS ports correspond to different beams of a multi-beam PUSCH transmission may increase. Summary of the Invention

[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0005] A user equipment (UE) may utilize a physical uplink shared channel (PUSCH) transmission to transmit a phase tracking reference signal (PT-RS) so that a network entity, such as a base station or a cell of a base station, may perform phase offset tracking in symbols without a demodulation reference signal (DMRS). For example, the network entity compares the phase offset between the PT-RS symbol and the DMRS symbol to estimate and / or compensate for the phase offset that may be caused by phase noise and / or frequency offset. The UE may transmit the PT-RS from a single PT-RS port or multiple PT-RS ports.

[0006] The UE can determine the number of PT-RS ports used to send PT-RS based on the configuration and the indicated precoder from the network entity. The network entity can also indicate one or more DMRS ports associated with one or more PT-RS ports so that the UE can use the same precoder for the PT-RS port and the DMRS port to send PT-RS and DMRS. The network entity can schedule the UE to use multiple beams to transmit on the PUSCH. For example, the network entity sends two transmission configuration indicators (TCIs) for the PUSCH, which configure the UE to transmit using different beams based on spatial domain multiplexing (SDM) technology or single frequency network (SFN) technology. However, since the network entity can indicate multiple precoders for multiple beams, the UE may have to determine which PT-RS ports and DMRS ports correspond to different beams for multi-beam transmission.

[0007] Aspects of the present disclosure address the above and other deficiencies by configuring a UE to determine the number of PT-RS ports and the associated DMRS ports for each of the PT-RS ports for multi-beam transmissions, such as SFN PUSCH transmissions and SDM PUSCH transmissions. The resulting techniques can improve the phase offset tracking and estimation / compensation process for decoding multi-beam PUSCH transmissions, which can further improve overall decoding performance.

[0008] In accordance with some aspects, the UE receives a configuration for multi-beam PUSCH transmission from a network entity and sends the multi-beam PUSCH transmission and PT-RS to the network entity based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports.

[0009] According to some aspects, a network entity sends a configuration for multi-beam PUSCH transmission to a UE, as described above. The network entity receives the multi-beam PUSCH transmission and PT-RS from the UE based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A diagram of a wireless communication system including multiple user equipments (UEs) and network entities communicating through one or more cells is shown.

[0011] Figure 2 A diagram showing phase tracking reference signal (PT-RS) resource mapping is shown.

[0012] Figures 3A to 3B A diagram is shown for determining the number of PT-RS ports used for uplink transmission.

[0013] Figure 4 A signaling diagram of PT-RS transmission based on single frequency network (SFN) technology is shown.

[0014] Figure 5A A diagram is shown for determining one or more demodulation reference signal (DMRS) ports associated with one or more PT-RS ports.

[0015] Figure 5B A diagram is shown for precoder reordering to provide improved PT-RS and DMRS association.

[0016] Figure 6 A diagram is shown for determining one or more DMRS ports associated with one or more PT-RS ports.

[0017] Figure 7 A diagram showing example resource mapping patterns for a first beam and a second beam is shown.

[0018] Figure 8 A signaling diagram of PT-RS transmission based on spatial domain multiplexing (SDM) technology is shown.

[0019] Figure 9 A diagram showing example resource mapping patterns for a first beam and a second beam is shown.

[0020] Figure 10 A diagram showing example resource mapping patterns for a first beam and a second beam is shown.

[0021] Figure 11 is a flow chart of a method of wireless communication at a UE.

[0022] Figure 12 is a flow chart of a method of wireless communication at a network entity.

[0023] Figure 13 is a diagram illustrating a hardware implementation of an example UE equipment.

[0024] Figure 14 is a diagram illustrating a hardware implementation of one or more example network entities. DETAILED DESCRIPTION

[0025] Figure 1A diagram 100 of a wireless communication system associated with multiple cells 190 is shown. The wireless communication system includes a user equipment (UE) 102 and a base station / network entity 104. Some base stations may include a converged base station architecture, while other base stations may include a disaggregated base station architecture. The converged base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized unit (CU) 110, which are configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. The disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed across two or more units (e.g., RU 106, DU 108, CU 110). For example, CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RUs 106. Each of the RU 106, DU 108, and CU 110 may be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / network entity 104 (e.g., a converged base station or a disaggregated unit of a base station, such as the RU 106, DU 108, or CU 110) may be referred to as a transmission reception point (TRP).

[0026] The operation and / or network design of the base station 104 can be based on the aggregated nature of base station functionality. For example, a disaggregated base station architecture is utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtualized radio access network (vRAN) (which may also be referred to as a cloud radio access network (C-RAN)). Decomposition can include distributing functionality between two or more units located at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. Various units of the disaggregated base station architecture or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit. For example, the RUs 106a-106d can communicate with respective UEs 102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In an example, multiple RUs 106 and / or base stations 104 may concurrently serve a UE 102, such as UE 102a in cell 190a being concurrently served by an access link of RU 106a in cell 190a and an access link of base station 104c in cell 190e.

[0027] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to send or receive information / signals via a wired or wireless transmission medium. Base station 104 or any of the one or more decomposed base station units may be configured to communicate with one or more other base stations 104 or one or more other decomposed base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with executable instructions of the interface may be configured to provide communication between base stations 104 and / or one or more decomposed base station units via a wired or wireless transmission medium. For example, a wired interface may be configured to send or receive information / signals via a wired transmission medium, such as via a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. The BBU 112 includes the DU 108 and the CU 110, and may also have a wired interface (e.g., a midhaul link) configured between the DU 108 and the CU 110 to transmit or receive information / signals between the DU 108d and the CU 110d. In a further example, a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver), may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between the RU 106a of the cell 190a and the base station 104 of the cell 190e via the cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0028] The RU 106 may be configured to implement lower layer functions. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node hosting RF processing functions or lower layer PHY functions, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functions of the RU 106 may be based on functional partitioning, such as lower layer functional partitioning.

[0029] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beam set 132 of RU 106b and a second communication beam set 134b of UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beam set 134a of UE 102b and a fourth communication beam set 136 of RU 106a. Both real-time and non-real-time features of control and user plane communications of RU 106 can be controlled by the associated DU 108.

[0030] Any combination of RU 106, DU 108, and CU 110, or any reference to any of them individually, may correspond to base station 104. Thus, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides access to the core network for UE 102. Base station 104 may relay communications between UE 102 and the core network. Base station 104 may be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femto cells, pico cells, micro cells, and the like. A cell structure including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network."

[0031] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from a base station 104 / RU 106 to a UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions, and downlink transmissions may also be referred to as forward link transmissions. For example, RU 106 d utilizes an antenna of base station 104 d in cell 190 d to transmit downlink / forward link communications to or receive uplink / reverse link communications from UE 102 d over a Uu interface associated with an access link between UE 102 d and base station 104 d / RU 106 d.

[0032] The communication link between the UE 102 and the base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. The UE 102 and the base station 104 / RU 106 can utilize a spectrum bandwidth of Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) per carrier, allocated in a carrier aggregation of up to a total of Yx MHz, with x component carriers (CCs) used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In an example, uplink and downlink carriers can be allocated in an asymmetric manner, with more or fewer carriers allocated for the uplink or downlink. The component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

[0033] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via a sidelink. For example, the sidelink communication / D2D link utilizes the spectrum of a wireless wide area network (WWAN) associated with uplink and downlink communications. The sidelink communication / D2D link can also 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 / or a physical sidelink control channel (PSCCH) to transmit information between UEs 102a and 102s. Such sidelink / D2D communication can be performed via various wireless communication systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, long term evolution (LTE) systems, new radio (NR) systems, and the like.

[0034] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc. based on the different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is typically associated with two operating frequency bands (FRs), referred to as Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 ranges from 410 MHz to 7.125 GHz, and FR2 ranges from 24.25 GHz to 71.0 GHz, including FR2-1 (24.25 GHz to 52.6 GHz) and FR2-2 (52.6 GHz to 71.0 GHz). Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is distinct from the "extremely high frequency" (EHF) band, but is a close subset of it. The EHF band ranges from 30 GHz to 300 GHz and is sometimes also referred to as the "millimeter wave" band. Frequencies between FR1 and FR2 are often referred to as "mid-band" frequencies. The operating band for mid-band frequencies may be referred to as Frequency Range 3 (FR3), which ranges from 7.125 GHz to 24.25 GHz. Frequency bands within FR3 may include characteristics of FR1 and / or FR2. Thus, the features of FR1 and / or FR2 may be extended to mid-band frequencies. Higher operating bands have been identified to extend 5G NR communications above the 52.6 GHz associated with the upper limit of FR2. Three of these higher operating bands include FR2-2 (which ranges from 52.6 GHz to 71.0 GHz), FR4 (which ranges from 71.0 GHz to 114.25 GHz), and FR5 (which ranges from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF band. Therefore, unless otherwise expressly stated herein, the term "sub-6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Further, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies that may be within FR2-1, FR4, FR2-2, and / or FR5, or frequencies that may be within the EHF band.

[0035] UE 102 and base station 104 / RU 106 may each include multiple antennas. The multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, RU 106b may transmit downlink beamformed signals to UE 102b based on a first communication beam set 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamformed signals from RU 106b based on a second communication beam set 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamformed signals to RU 106b based on a second communication beam set 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamformed signals from UE 102b in one or more receive directions of RU 106b.

[0036] UE 102b may perform beam training to determine optimal receive and transmit directions for beamformed signals. The transmit and receive directions of UE 102 and base station 104 / RU 106 may be the same or different. In a further example, beamformed signals may be transmitted between a first base station / RU 104a and a second base station 104e. For example, base station 104e of cell 190e may transmit beamformed signals to RU 106a based on communication beam 138 in one or more transmit directions of base station 104e. RU 106a may receive beamformed signals from base station 104e of cell 190e based on RU communication beam 136 in one or more receive directions of RU 106a.

[0037] The base station 104 may include and / or be referred to as a network entity. That is, a “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB), a first generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network device, or other related terms. The base station 104 or an entity at the base station 104 may be implemented as an IAB node, a relay node, a sidelink node, a converged (monolithic) base station having the RU 106 and the BBU 112 including the DU 108 and the CU 110, or as a decomposed base station including one or more RUs 106, DUs 108, and / or CUs 110. A converged or disaggregated set of base stations may be referred to as a next generation radio access network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such a case, base station 104e may be the primary node, while base station / RU 160a may be the secondary node.

[0038] Uplink / downlink signaling may also be communicated via a satellite positioning system (SPS) 114. In an example, the SPS 114 of cell 190c may communicate with one or more UEs 102, such as UE 102c, and one or more base stations 104 / RUs 106, such as RU 106c. The SPS 114 may correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round-trip time (RTT) and / or multiple RTTs), wireless local area network (WLAN) signals, a terrestrial beacon system (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink angle of departure (DL-AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), uplink angle of arrival (UL-AoA), and / or other systems, signals, or sensors.

[0039] Still refer to Figure 1In certain aspects, the UE 102 may include a multi-beam physical uplink shared channel (PUSCH) transmission component 140 configured to receive a configuration for a multi-beam PUSCH transmission from a network entity; and to send a multi-beam PUSCH transmission and a phase tracking reference signal (PT-RS) to the network entity based on a number of PT-RS ports and a demodulation reference signal (DMRS) port associated with the number of PT-RS ports.

[0040] In certain aspects, the base station 104 or a network entity of the base station 104 may include a multi-beam PUSCH configuration component 150 configured to send a configuration for a multi-beam PUSCH transmission to the UE; and receive a multi-beam PUSCH transmission and a PT-RS from the UE based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports.

[0041] therefore, Figure 1 A wireless communication system is described that can incorporate aspects of one or more of the other figures described herein—such as Figures 2 to 10 Further, although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-Advanced (LTE-A), and other wireless technologies such as 6G.

[0042] Figure 2 A diagram 200 of PT-RS resource mapping is shown. UEs and network entities, such as base stations or units of base stations, utilize PT-RS 202 to track the phase of local oscillators at receivers and transmitters. Tracking the phase can enable suppression of phase noise and / or common phase errors, such as at high subcarrier frequencies (e.g., millimeter wave (mmW) frequencies). PT-RS 202 can be transmitted by a network entity on the downlink, such as on the physical downlink shared channel (PDSCH), or by a UE on the uplink, such as on the PUSCH.

[0043] When a network entity configures a UE to transmit PT-RS 202 on the PUSCH, PT-RS 202 is used as a reference to compensate for errors in symbols without DMRS 204. For example, diagram 200 shows DMRS 204 in the third symbol of a time slot, while the other 13 symbols of the time slot include PT-RS 202 in at least one subcarrier. The UE can transmit PT-RS 202 from a single port, such as PT-RS 202a from port 0, or from multiple ports, such as also transmitting PT-RS 202b from port 1. Resource elements (REs) of diagram 200 that are not used for PT-RS 202 and DMRS 204 can include data 206 for the PUSCH. The network entity can compare the phase offset between PT-RS 202 in one symbol and DMRS 204 in another symbol to estimate and compensate for the phase offset of each symbol, which may be caused by phase noise and / or frequency offset.

[0044] Figures 3A to 3B Diagrams 300 to 350 are shown for determining the number of PT-RS ports for uplink transmission. Figure 3A Applicable to codebook-based transmission, while Figure 3B Applicable to non-codebook based transmission.

[0045] The UE may determine 308-310 the number of PT-RS ports based on a configuration from a network entity. The UE may transmit a single-port PT-RS or a dual-port PT-RS based on the configuration. Therefore, the UE initially determines 302 whether the maximum number of PT-RS ports is configured as 1 or 2. If the network entity configures the maximum number of PT-RS ports (e.g., maxNrofPorts) in PTRS-UplinkConfig as 1, the UE transmits a single-port PT-RS based on the determination 308 that the number of PT-RS ports is 1.

[0046] For codebook-based transmission, if the network entity configures the maximum number of PT-RS ports (e.g., maxNrofPorts) in PTRS-UplinkConfig to 2, the UE determines 304 whether the indicated precoder associated with the configuration is for partially coherent transmission. If the indicated precoder is for coherent transmission, the UE transmits a single-port PT-RS based on a determination 308 that the number of PT-RS ports is 1. If the indicated precoder is for incoherent transmission or partially coherent transmission, the UE determines 306 the number of PT-RS ports based on whether the precoder includes non-zero power (NZP) ports from two antenna port groups used for PUSCH transmission.

[0047] If the NZP ports are not from two different antenna port groups, the UE transmits a single-port PT-RS based on the determination 308 that the number of PT-RS ports is 1. If the NZP ports are from two different antenna port groups, the UE transmits a dual-port PT-RS based on the determination 310 that the number of PT-RS ports is 2. The first port of the dual-port PT-RS corresponds to the first antenna port group, and the second port of the dual-port PT-RS corresponds to the second antenna port group. In the example of a four-port PT-RS, the first and third ports correspond to the first antenna port group, and the second and fourth ports correspond to the second antenna port group.

[0048] For non-codebook-based transmission, the UE similarly determines 302 whether the maximum number of PT-RS ports is configured as 1 or 2, and similarly transmits a single-port PT-RS based on the determination 308 that the number of PT-RS ports is 1. However, if the network entity configures the maximum number of PT-RS ports (e.g., maxNrofPorts) in the PTRS-UplinkConfig as 2, the UE determines 355 the number of PT-RS ports based on the indicated sounding reference signal (SRS) resources for non-codebook-based transmission. For example, the UE determines 355 whether the PT-RS port index is the same for all indicated SRS resources. If the PT-RS port index is the same for all indicated SRS resources, the UE transmits a single-port PT-RS based on the determination 308 that the number of PT-RS ports is 1. If the PT-RS port index for all indicated SRS resources is not the same, the UE transmits a dual-port PT-RS based on the determination 310 that the number of PT-RS ports is 2.

[0049] The network entity may indicate the DMRS port for a PT-RS port via scheduling downlink control information (DCI). For example, the network entity may schedule PUSCH via DCI and may indicate the PT-RS / DMRS association for the PT-RS port. When a PT-RS port is associated with a DMRS port, the UE uses the same precoder for transmission on the PT-RS port and the DMRS port. Therefore, the network entity may indicate the DMRS port with the best / highest quality precoder among multiple DMRS ports sharing the same PT-RS port.

[0050] The network entity can schedule the UE to transmit from multiple beams on the PUSCH. For example, the network entity indicates two transmission configuration indicators (TCIs) for the PUSCH. That is, the network entity can indicate a first TCI for the first PUSCH and a second TCI for the second PUSCH. The network entity can also configure the UE to transmit on the PUSCH using different beams based on spatial domain multiplexing (SDM) technology or single frequency network (SFN) technology.

[0051] For SDM technology, the UE transmits on the PUSCH using different beams from different layers. Therefore, the PUSCH information for each beam is different. For codebook-based transmission, the network entity uses two DCI fields or configures two radio resource control (RRC) parameters to indicate the precoder used for each beam. The first field or parameter indicates the precoder and the number of layers used for the first beam, and the second field or parameter indicates the precoder and the number of layers used for the second beam. For non-codebook-based transmission, the network entity indicates or configures two sets of SRS resource indicators (SRIs) via DCI or RRC signaling. The UE determines the precoder and the number of layers for the first beam based on the first set of SRIs, and determines the precoder and the number of layers for the second beam based on the second set of SRIs.

[0052] For SFN technology, the UE transmits based on PUSCH repetition using different beams. Therefore, the PUSCH information for each beam is the same. For codebook-based transmission, the network entity uses two DCI fields or configures two RRC parameters to indicate the precoder used for each beam. The first field or parameter indicates the precoder used for the first beam and the number of layers used for both the first beam and the second beam, and the second field or parameter indicates the precoder used for the second beam. For non-codebook-based transmission, the network entity indicates or configures two sets of SRIs via DCI or RRC signaling. The UE determines the precoder used for the first beam and the number of layers used for both the first beam and the second beam based on the first set of SRIs, and determines the precoder used for the second beam based on the second set of SRIs.

[0053] The network entity configures single-beam based transmission or multi-beam based transmission by indicating the SRS resource set and beam indication for the precoder in the scheduling DCI or RRC signaling. If the network entity indicates one SRS resource set, the UE transmits on the PUSCH based on a single-beam transmission scheme. If the network entity indicates more than one SRS resource set, the UE transmits on the PUSCH based on multi-beam transmission (e.g., SDM or SFN technology). Since the network entity can indicate more than one precoder for more than one beam in multi-beam transmission, the UE may have to determine the number of PT-RS ports for SFN and / or SDM transmission schemes and the associated DMRS ports for each PT-RS port. PT-RS transmission on the PUSCH for the multi-beam process can improve phase offset tracking and compensation for decoding the multi-beam PUSCH, which can further improve decoding performance. Figures 2 to 3B PT-RS resource and port determination is shown. Figures 4 to 10 The PT-RS for multi-beam PUSCH transmission is described. Specifically, Figures 4 to 7 PT-RS and SFN PUSCH transmission techniques are described. Figures 8 to 10 The PT-RS and PUSCH transmission based on SDM technology is described.

[0054] Figure 4 A signaling diagram 400 for PT-RS transmission based on SFN technology is shown. In some implementations, the UE 102 reports 406 to the network entity 104 its UE capabilities for SFN PUSCH transmission and the maximum number of PT-RS ports for SFN procedures. In other implementations, the network entity 104 receives one or more UE capabilities from the core network (e.g., an access and mobility management function (AMF)). In still other implementations, the network entity 104 receives one or more UE capabilities from another base station / network entity (e.g., a gNB or eNB). The UE capabilities may indicate whether the UE 102 supports SFN PUSCH transmission and / or the supported maximum number of PT-RS ports for SFN procedures. The UE 102 may report 406 the UE capabilities per feature set, per frequency band, per frequency band combination, or per UE.

[0055] The network entity 104 may configure 408a the UE 102 with one or more parameters via first control signaling (e.g., RRCReconfiguration) to implement SFN PUSCH transmission. The configuration 408a for SFN PUSCH transmission may also optionally indicate a maximum number of PT-RS ports to be used for the SFN process. The RRC signaling may indicate an RRCReconfiguration message or a system information block (SIB) from the network entity 104 to the UE 102, where the SIB may be a traditional type of SIB (e.g., SIB1) sent by the network entity 104 or a different SIB (e.g., SIB J, where J corresponds to an integer greater than 21).

[0056] The network entity 104 may send 408b second control signaling (e.g., DCI) to the UE 102, the second control signaling including a trigger indication for SFN PUSCH transmission. The second control signaling may indicate time and frequency domain transmission resources, at least two precoders, a DMRS port for each PT-RS port used for PUSCH, and / or the number of PT-RS ports. In some implementations, the network entity 104 may send 408 the information indicated in the second control signaling via the first control signaling (i.e., within the same control signaling). In other implementations, the network entity 104 sends 408a-408b separate control signals to the UE 102.

[0057] Based on the control signaling received 408 from the network entity 104, the UE 102 determines 410 the number of PT-RS ports and the DMRS ports for each PT-RS port to use for SFN PUSCH transmission. Based on the determined number of PT-RS ports and the associated DMRS ports for each PT-RS port, the UE 102 sends 412 the SFN PUSCH and PT-RS to the network entity 104. The network entity 104 receives 414 the SFN PUSCH and PT-RS based on the configuration and trigger indication sent 408 to the UE 102.

[0058] Figure 5A A diagram 500 is shown for determining one or more DMRS ports associated with one or more PT-RS ports. A UE may transmit PT-RS, DMRS, and data on PUSCH from multiple beams based on SFN technology. For example, the UE transmits the same PT-RS, DMRS, and PUSCH transmission from each beam with the same resource mapping pattern. Accordingly, the UE determines 502 whether the PUSCH transmission is based on SFN technology.

[0059] The number of PT-RS ports may be fixed or indicated by a network entity. In an example, the number of PT-RS ports for SFN PUSCH transmission may be fixed to 1, such that 1 PT-RS port may be associated with a fixed DMRS port (e.g., a first DMRS port). In other examples, the network entity configures or indicates the DMRS port associated with the PT-RS port via control signaling sent to the UE. If the UE determines 502 that the PUSCH transmission is not based on SFN technology, the UE may determine 504 the number of PT-RS ports for PUSCH associated with a different scheme. Alternatively, as also described with respect to Figure 4 As described for SFNPUSCH transmission, if the UE determines 502 that the PUSCH transmission is based on SFN technology, the UE may determine 308 that the number of PT-RS ports is 1. The UE may further determine 508 a fixed or indicated DMRS port associated with one PT-RS port based on control signaling received from a network entity.

[0060] In some implementations, for single-layer PUSCH transmission, the number of PT-RS ports used for SFN PUSCH transmission is fixed to 1, and for multi-layer transmission, the number is fixed to 2 or more. Thus, if the UE determines 502 that the PUSCH transmission is based on SFN technology, the UE may further determine 506 whether the PUSCH transmission is for a single layer or multiple layers. If the UE determines 506 that the PUSCH is for a single layer, the UE sends the PUSCH based on the determination 308-310 of the PT-RS and DMRS ports. If the UE determines 506 that the PUSCH is for multiple layers, the UE may determine 310 that the number of PT-RS ports is 2, such that the UE may determine 510 2 fixed or 2 indicated DMRS ports associated with two PT-RS ports based on control signaling received from the network entity. In some examples, the network entity only configures SFN PUSCH transmission for up to two layers.

[0061] Each PT-RS port can be associated with a fixed DMRS port. In an example for a single-port PT-RS, the PT-RS port is associated with a first DMRS port. In another example of a dual-port PT-RS, the first PT-RS port is associated with a first DMRS port and the second PT-RS is associated with a second DMRS port. The network entity may also configure or indicate the associated DMRS port for each PT-RS port jointly (e.g., through a single DCI field or RRC parameter) or individually (e.g., through two different DCI fields or RRC parameters) via control signaling sent to the UE. The network entity may avoid indicating precoders for beams corresponding to different numbers of PT-RS ports. For example, the network entity avoids configuring more than one maximum number of PT-RS ports for the SFN process. Therefore, when the network entity configures SFN PUSCH transmission, the network entity configures maxNrofPorts in PTRS-UplinkConfig to n1.

[0062] Figure 5B Diagram 550 illustrates precoder reordering to provide improved PT-RS and DMRS association. Different shading patterns in diagram 550 represent different precoders (e.g., precoder 1 551, precoder 2 552, precoder 3 553, and precoder 4 554), with precoder 3 553 corresponding to the optimal precoder in the example illustrated by diagram 550. A network entity may configure or indicate a precoder swap or precoder reordering indicator for the first PUSCH beam and / or the second PUSCH beam. The indicator may indicate the order of precoders used for each layer, enabling the network entity to provide the optimal precoder to the SFN DMRS port, the optimal precoder providing the highest received power among the precoders applied to all scheduled DMRS ports.

[0063] In diagram 550 , the precoder order for PUSCH beam 2 is reordered to align with the precoder order for PUSCH beam 1. That is, the precoder order for PUSCH beam 2 is reordered to {3, 4, 2, 1} so that the best precoders for PUSCH beam 1 and PUSCH beam 2 are aligned with layer 1 DMRS port 0. Therefore, the PT-RS is associated with DMRS port 0. The remaining precoders for PUSCH beam 2 are also reordered to align with layer 2 DMRS port 1, layer 3 DMRS port 2, and layer 4 DMRS port 3, respectively.

[0064] In some implementations, the network entity sends a 1-bit indicator indicating whether the UE should swap the precoders for the first and second layers. In other implementations, the network entity sends an indicator indicating the order of the precoders used for each layer based on predefined candidate values. In the example for 2-layer transmission, the candidate values ​​for the order of the precoders for the layers can be {1, 2} and {2, 1}. In the example for 3-layer transmission, the candidate values ​​for the order of the precoders for the layers can be {1, 2, 3}, {1, 3, 2}, {2, 1, 3}, {2, 3, 1}, {3, 1, 2}, and {3, 2, 1}. In the example for 4-layer transmission, the candidate values ​​for the order of the precoders for the layers can be arranged in all 24 different possible combinations of the candidate values ​​{1, 2, 3, 4}, including the combination {3, 4, 2, 1}, as shown in diagram 550.

[0065] In other implementations, the network entity sends an indicator for indicating the order of the precoders used for each layer based on a candidate value configured by the network entity via RRC signaling. The network entity may use a single indicator to jointly indicate the precoder order indicator and the precoder used for the beam. For codebook-based transmission, the codebook may include precoders with different orders, so that the network entity may indicate precoders with different orders by indicating different transmit precoder matrix indicators (TPMIs). For non-codebook-based transmission, the network entity may use different values ​​for the SRI field to indicate different orders of the indicated SRS resources. For example, the SRI field may indicate SRS resources {1, 2} or {2, 1}.

[0066] Figure 6 A diagram 600 is shown for determining one or more DMRS ports associated with one or more PT-RS ports. Figure 5A Elements 502 and 504 are described. However, if the UE determines 502 that the PUSCH transmission is based on SFN technology, the UE may perform 606, 608, 612, 616 other procedures.

[0067] In a first example, for a codebook-based SFN transmission scheme, the UE determines 606 the number of PT-RS ports for each beam based on the indicated precoder for each beam. The UE then determines 610 the number of PT-RS ports for SFN PUSCH transmission as the minimum number or maximum number of PT-RS ports for each beam, so that the UE can further determine 620 DMRS ports for the PT-RS ports based on received control signaling (e.g., DCI signaling). If the UE determines that the number of PT-RS ports for a first beam is 1 based on a first indicated precoder and that the number of PT-RS ports for a second beam is 2 based on a second indicated precoder, the UE can determine 610 the number of PT-RS ports for SFN PUSCH transmission as min{1, 2} = 1 or max{1, 2} = 2.

[0068] In a second example, for a non-codebook-based SFN transmission scheme, the UE determines 608 the number of PT-RS ports based on the indicated SRS resources. For example, the UE may determine 608 the number of PT-RS ports for each beam based on the indicated SRS resources for each beam. The determination 608 of the number of PT-RS ports may be based on one of the indicated precoders used for SFN PUSCH transmission. The UE determines 608 the number of PT-RS ports for each beam based on the indicated SRS resources for each SRS resource set, such that the UE may determine 610 the number of PT-RS ports for SFN PUSCH transmission as the minimum or maximum number of PT-RS ports for each beam. The UE further determines 620 DMRS ports for the PT-RS ports based on the received control signaling. If the PT-RS port index for the indicated SRS resources across SRS resource sets is the same, the UE determines the number of PT-RS ports to be 1. Otherwise, the UE may determine the number of PT-RS ports to be 2. In other implementations, after the UE determines 608 the number of PT-RS ports for each beam based on the indicated SRS resources for each SRS resource set, the UE may directly determine 620 the DMRS ports for the PT-RS ports based on the received control signaling.

[0069] In a third example, for a codebook-based SFN transmission scheme, the UE selects 612 an indicated precoder to determine the number of PT-RS ports. For example, the UE may select 612 an indicated precoder for a first beam to determine the number of PT-RS ports for the first beam, and select 612 an indicated precoder for a second beam to determine the number of PT-RS ports for the second beam. The determination 614 of the number of PT-RS ports is based on one of the indicated precoders for SFN PUSCH transmission. The network entity may configure or indicate which precoder should be used to determine the number of PT-RS ports through control signaling. After selecting 612 one of the indicated precoders, the UE determines 614 the number of PT-RS ports based on the selected precoder, so that the UE may further determine 620 DMRS ports for the PT-RS ports based on the received control signaling.

[0070] In a fourth example, for a non-codebook-based SFN transmission scheme, the UE selects 616 an SRS resource set based on the indicated SRS resources to determine the number of PT-RS ports. The UE determines 618 the number of PT-RS ports based on the indicated SRS resources from the selected SRS resource set, so that the UE can further determine 620 DMRS ports for the PT-RS ports based on the received control signaling. The UE can identify the associated DMRS ports. The network entity can also configure or indicate the order of the precoders, as described above.

[0071] Figure 7Illustrations 700 to 750 illustrate example resource mapping patterns for a first beam and a second beam. Illustration 700 corresponds to a first resource mapping pattern for the first beam. Illustration 750 corresponds to a second resource mapping pattern for the second beam. The UE transmits PT-RS 202 (e.g., PT-RS 202a from port 0 and PT-RS 202b from port 1) based on a non-SFN technique, but transmits DMRS 204 and data 206 for the PUSCH using multiple beams based on an SFN technique. That is, the UE transmits different PT-RSs 202a / 202b using different beams (e.g., PT-RS 202a on beam 1 and PT-RS 202b on beam 2), and transmits DMRS 204 and data 206 using the same resource mapping pattern on multiple beams (e.g., beam 1 and beam 2). In other implementations, the UE may also transmit DMRS 204 based on a non-SFN technique. The number of PT-RS ports for each beam may be predefined (e.g., the number of PT-RS ports for each beam may be fixed to 1). Non-SFN transmission techniques for PT-RS 202 may result in some REs 708a / 708b for each beam being empty, which otherwise may have been used for additional PT-RS 202 in the SFN process.

[0072] The network entity may indicate a common DMRS port index to the UE to associate the DMRS port for each beam with the PT-RS port for each beam based on an indicator in the control signaling. In some implementations, the network entity indicates the PT-RS port for each beam that is associated with the first DMRS port or the second DMRS port applied to the beam. The network entity may further configure a precoder reordering indicator for one or more of the indicated precoders.

[0073] The network entity uses a joint indicator or a separate indicator to associate a different DMRS port for each beam with a PT-RS port for each beam. The joint indicator of the PT-RS port for multi-beam transmission can be associated with up to 2 layers. For example, the joint indicator includes 2 bits, where the first bit indicates whether the PT-RS 202 for the first beam is associated with the first DMRS port or the second DMRS port applied to the first beam, and the second bit indicates whether the PT-RS 202 for the second beam is associated with the first DMRS port or the second DMRS port applied to the second beam. In another example with separate indicators for PT-RS ports for multi-beam transmission (e.g., with up to 2 layers), each of the separate indicators may include 1 bit indicating whether the PT-RS 202 for the beam is associated with the first DMRS port or the second DMRS port applied to the beam.

[0074] The DMRS ports for PT-RS 202 in each beam may be predefined. The UE may transmit PT-RS 202 in each beam via power boosting. For example, the UE may transmit PT-RS 202 with a power boost of X dB such that the energy per resource element (EPRE) ratio between PT-RS 202 and PUSCH is X dB. X may be a predefined value (e.g., , where K corresponds to the number of indicated beams). The network entity may configure the value of X through control signaling. In some examples, the UE reports the supported or preferred values ​​of X to the network entity in a UE capability report.

[0075] The network entity may indicate K*N DMRS ports for the PUSCH, where N corresponds to the number of layers and K corresponds to the number of beams indicated. The DMRS port grouping for each beam may be predefined. For example, if a UE transmits on the PUSCH using two beams, the UE may transmit on the PUSCH using a first beam for the first N DMRS ports and a second beam for the remaining N DMRS ports. The network entity may configure or indicate the DMRS port grouping for each beam through control signaling. In an example, the network entity jointly indicates the DMRS port grouping and the DMRS port.

[0076] The DMRS port and DMRS port grouping indication for rank-2 SFN PUSCH transmission with two beams of non-SFN DMRS may be based on the following table: Type 1 DMRS (e.g., dmrs-Type = 1) may include one front-loading symbol (e.g., maxLength = 1). The UE may transmit the PT-RS 202, data 206 on the PUSCH, and DMRS 204 for each beam at the same transmission power. The network entity may configure the transmission power ratio for the PT-RS 202, data 206 on the PUSCH, and DMRS 204 for each beam through control signaling. The UE may report the transmission power ratio to the network entity via a UE capability report, a media access control element (MAC-CE), uplink control information (UCI), or based on UE assistance information.

[0077] The network entity may configure or indicate whether to determine the number of PT-RS ports based on multiple indicated precoders (e.g., all indicated precoders) or based on one of the indicated precoders. The network entity may also configure or indicate, through control signaling, whether to determine the number of PT-RS ports based on a predefined number of PT-RS ports. The UE may transmit PT-RS 202 and DMRS 204 based on SFN or non-SFN technology. The UE may report UE capabilities to the network entity, indicating whether the UE supports determining the number of PT-RS ports based on the indicated precoder or based on a predefined number of PT-RS ports. The UE may also report UE capabilities to the network entity indicating whether the UE supports transmission of PT-RS 202 and DMRS 204 based on SFN or non-SFN technology. The network entity may configure the UE to transmit PT-RS 202 and PUSCH based on the UE capability report. Figures 4 to 7 PT-RS and SFN PUSCH transmission techniques are described. Figures 8 to 10 The PT-RS and PUSCH transmission based on SDM technology is described.

[0078] Figure 8A signaling diagram 800 for PT-RS transmission based on SDM techniques is shown. In some implementations, the UE 102 reports 806 to the network entity 104 the UE capabilities for SDM PUSCH transmission and the maximum number of PT-RS ports for SDM procedures. In other implementations, the network entity 104 receives one or more UE capabilities from the core network (e.g., AMF). In still other implementations, the network entity 104 receives one or more UE capabilities from another base station / network entity (e.g., gNB or eNB). The UE capabilities may indicate whether the UE 102 supports SDM PUSCH transmission, the maximum number of PT-RS ports supported for SDM procedures, and / or whether two indicated beams share the same PT-RS port or different PT-RS ports. The UE 102 may report 806 the UE capabilities by feature set, by frequency band, by frequency band combination, or by UE.

[0079] The network entity 104 may configure 808a the UE 102 with one or more parameters via first control signaling (e.g., RRCReconfiguration) to implement SDM PUSCH transmission. The configuration 808a for SDM PUSCH transmission may also optionally indicate a maximum number of PT-RS ports to be used for the SDM process. The RRC signaling may indicate an RRCReconfiguration message or a SIB from the network entity 104 to the UE 102, where the SIB may be a traditional type of SIB (e.g., SIB1) sent by the network entity 104 or a different SIB (e.g., SIB J, where J corresponds to an integer greater than 21).

[0080] The network entity 104 may send 808b second control signaling (e.g., DCI) to the UE 102, the second control signaling including a trigger indication for SDM PUSCH transmission. The second control signaling may indicate time and frequency domain transmission resources, at least two precoders, a DMRS port for each PT-RS port used for PUSCH, and / or the number of PT-RS ports. In some implementations, the network entity 104 may send 808 the information indicated in the second control signaling via the first control signaling (i.e., within the same control signaling). In other implementations, the network entity 104 sends 808a-808b separate control signals to the UE 102.

[0081] Based on the control signaling received 808 from the network entity 104, the UE 102 determines 810 the number of PT-RS ports and the DMRS port for each PT-RS port to use for SDM PUSCH transmission. Based on the determined number of PT-RS ports and the associated DMRS port for each PT-RS port, the UE 102 sends 812 the SDM PUSCH and PT-RS to the network entity 104. The network entity 104 receives 814 the SDM PUSCH and PT-RS based on the configuration and trigger indication sent 808 to the UE 102.

[0082] Figure 9 Diagrams 900 to 940 illustrate example resource mapping patterns for a first beam and a second beam. The UE may transmit PT-RS 202 from a single port for beam 1 (e.g., PT-RS 202a from port 0) and transmit DMRS 204 and data 206 from different layers for multiple beams (e.g., beam 1 and beam 2). The example resource mapping may be applied to UEs that support 1-port PT-RS for multi-beam PUSCH. The UE may transmit PT-RS 202 in association with a predefined DMRS port corresponding to the first indicated beam. In other implementations, a network entity may send control signaling to the UE to configure or indicate the DMRS port associated with PT-RS 202. An example PT-RS / DMRS port association for a 1-port uplink PT-RS 202 for SDM PUSCH transmission may be based on the following table, where the network entity may indicate the associated DMRS port for PT-RS port 0, and the DMRS port is selected from the DMRS ports scheduled by the control signaling for scheduling the PUSCH: An example PT-RS / DMRS port association for a 1-port uplink PT-RS 202 for SDM PUSCH transmission, where the first beam is indicated by the first SRI or SRS resource set, may be based on the following table:

[0083] As shown in diagram 900, the UE may transmit PT-RS 202a, DMRS 204, and data 206 on the PUSCH in a first beam, but as shown in diagram 920, the UE may also transmit the data 206 on the PUSCH in a second beam at the REs used for PT-RS 202a in the first beam, in addition to other REs used for data 206 on the PUSCH. In other examples, as shown in diagram 900, the UE may also transmit PT-RS 202a, DMRS 204, and data 206 on the PUSCH in a first beam, and as shown in diagram 940, the UE may also transmit the data 206 on the PUSCH in the second beam, in addition to DMRS 204, at the same REs used only for data 206 on the PUSCH in the first beam. That is, in diagram 940, the UE does not transmit data 206 or PT-RS 202 at the same REs as when the UE transmitted PT-RS 202a in diagram 900. The network entity may configure or indicate, through control signaling, whether the REs used for the PT-RS 202a of the first beam are available or unavailable for PUSCH rate matching in the second beam. In some implementations, the UE indicates to the network entity in a UE capability report whether the REs used for the PT-RS 202a of the first beam are available or unavailable for PUSCH rate matching in the second beam.

[0084] The network entity may send control signaling to configure the power boost ratio of the PT-RS 202. For example, the network entity configures the EPRE ratio between the PT-RS 202 and the data 206 on the PUSCH associated with the same SRI or SRS resource set. An example EPRE ratio configuration between the PT-RS 202 and the data 206 on the PUSCH for the same beam may be based on the following table: The power boost ratio of the PT-RS 202 may be predefined. The EPRE ratio between the PT-RS 202 and the data 206 on the PUSCH for the same SRI or SRS resource set may also be a predefined value corresponding to the above table.

[0085] Figure 10 Diagrams 1000 through 1060 illustrate example resource mapping patterns for a first beam and a second beam. A UE can transmit PT-RS 202 from multiple ports (e.g., PT-RS 202a from port 0 and PT-RS 202b from port 1), where different PT-RS ports correspond to different beams. The UE transmits DMRS 204 and data 206 on different layers for the multiple beams. The example resource mapping can be applied to UEs that support more than one PT-RS port (e.g., two PT-RS ports) for multi-beam PUSCH transmission.

[0086] The PT-RS port for a beam can be associated with a predefined DMRS port for the beam. In other examples, the network entity configures or indicates the DMRS port for each PT-RS port individually or jointly through control signaling. An example DMRS port association indication for a 2-port uplink PT-RS 202 for SDM PUSCH transmission using two SRI or SRS resource sets can be based on the following table:

[0087] As shown in diagram 1020, the UE may transmit data 206 on the PUSCH at the same REs in the second beam that are used for PT-RS 202a in the first beam (as shown in diagram 1000), or vice versa (e.g., as shown in diagram 1000, the UE may transmit data 206 on the PUSCH at the same REs in the first beam that are used for PT-RS 202b in the second beam (as shown in diagram 1000). In other implementations, the UE transmits data 206 on the PUSCH in the second beam at REs that are used only for data 206 on the PUSCH in the first beam (as shown in diagram 1040), or vice versa, as shown in diagram 1060. The UE determines that the REs used for PT-RS 202 in one beam are not available for data 206 on the PUSCH in another beam. Therefore, in diagram 1040, the UE does not transmit data 206 at the REs corresponding to PT-RS 202b in diagram 1060. The UE similarly does not transmit data 206 in diagram 1060 at the RE corresponding to the PT-RS 202 a in diagram 1040 .

[0088] The UE may transmit PT-RS 202 based on K predefined DMRS ports. For example, a first indicated DMRS port among the plurality of DMRS ports corresponds to each indicated beam, where K corresponds to the number of indicated beams, the number of SRIs, or the number of precoders. The network entity may configure or indicate the associated DMRS ports of the PT-RS 202 via control signaling. An example DMRS port association indication for a 1-port uplink PT-RS 202 for SDM PUSCH transmission may be based on the following table:

[0089] In some implementations, the UE transmits PT-RS 202 based on the same sequence at the same REs for both beams. For example, the UE may repeat the resource mapping pattern used for beam 1 for both beam 1 and beam 2 based on the PT-RS sequence and REs for beam 1, such as repeating the resource mapping pattern of diagram 1000. The UE determines the PT-RS sequence and REs based on one of the associated DMRS ports. The UE transmits PT-RS 202 for each beam based on the same precoder as for the DMRS port for the same beam. The UE may also transmit PT-RS 202 based on the EPRE being the same across both beams.

[0090] The network entity may configure or indicate the number of PT-RS ports used for SDM PUSCH transmission via control signaling. For a single-port PT-RS, the network entity may further configure or indicate whether PT-RS 202 is transmitted based on an SDM technique or a non-SDM scheme, so that the UE can determine how to transmit PT-RS 202. The UE may also report to the network entity UE capabilities indicating the supported number of PT-RS ports used for SDM PUSCH transmission. For a single-port PT-RS, the UE may further report UE capabilities indicating whether PT-RS based on an SDM technique or a non-SDM technique is supported, so that the network entity can configure the UE to transmit PT-RS 202. Figures 4 to 10 A multi-beam PUSCH transmission technique is described. Figures 11 to 12 Shown for implementation Figures 4 to 10 Specifically, Figure 11 UE 102 is shown Figures 4 to 10 Implementation of one or more aspects. Figure 12 The network entity 104 is shown Figures 4 to 10 implementation of one or more aspects of .

[0091] Figure 11 A flow chart 1100 of a wireless communication method at a UE is shown. Figure 4 、 Figure 8 and Figure 13 , the method can be performed by UE 102, UE equipment 1302, etc., which may include memory 1326', 1306', 1316, and may correspond to the entire UE 102 or the entire UE equipment 1302, or components of the UE 102 or UE equipment 1302 (such as wireless baseband processor 1326 and / or application processor 1306).

[0092] UE 102 sends 1106 to the network entity a UE capability report indicating the UE's capability for multi-beam PUSCH transmission. Figure 4 , the UE 102 sends 406 to the network entity 104 the UE capabilities regarding the SFN PUSCH transmission technology and the maximum number of PT-RS ports for SFN multi-beam PUSCH. Figure 8 , the UE 102 sends 806 to the network entity 104 the UE capability regarding the maximum number of PT-RS ports for SDM multi-beam PUSCH.

[0093] UE 102 receives 1108a a configuration for multi-beam PUSCH transmission from a network entity. Figure 4 , the UE 102 receives 408a a configuration for SFN PUSCH transmission from the network entity 104 and optionally receives a maximum number of PT-RS ports for SFN multi-beam PUSCH. Figure 8 , the UE 102 receives 808a a configuration for SDM PUSCH transmission and optionally a maximum number of PT-RS ports for SDM multi-beam PUSCH from the network entity 104.

[0094] UE 102 receives 1108b a trigger indication for multi-beam PUSCH transmission from a network entity. Figure 4 , the UE 102 receives 408b a trigger indication for SFN PUSCH transmission from the network entity 104 (e.g., indicating resources, at least two precoders, DMRS ports for each PT-RS port used for PUSCH, and / or the number of PT-RS ports). Figure 8 , the UE 102 receives 808b a trigger indication for an SDM scheme for PUSCH from the network entity 104 (e.g., indicating resources, at least two precoders, a DMRS port for each PT-RS port for PUSCH, and / or the number of PT-RS ports).

[0095] The UE 102 sends 1112 a multi-beam PUSCH transmission and PT-RS to a network entity based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports. Figure 4 And as Figure 7 As shown, UE 102 sends 412 SFN PUSCH and PT-RS 202 to network entity 104. Figure 8 And as Figures 9 and 10 As shown, the UE 102 transmits 812 a PUSCH and a PT-RS 202 to the network entity 104 using an SDM scheme. Figure 11 A method is described from the UE side of a wireless communication link, and Figure 12 A method is described from the network side of a wireless communication link.

[0096] Figure 12 1200 is a flow chart of a method of wireless communication at a network entity. Figure 4 、 Figure 8 and Figure 14 The method may be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station, such as the RU 106, the DU 108, the CU 110, the RU processor 1406, the DU processor 1426, the CU processor 1446, etc. The one or more network entities 104 may include a memory 1406' / 1426' / 1446', which may correspond to the entirety of the one or more network entities 104 or a component of the one or more network entities 104, such as the RU processor 1406, the DU processor 1426, or the CU processor 1446.

[0097] The network entity 104 receives 1206 a UE capability report from the UE indicating the UE's capability for multi-beam PUSCH transmission. Figure 4 , the network entity 104 receives 406 from the UE 102 information regarding the SFN PUSCH transmission technique and the UE capability of the maximum number of PT-RS ports for SFN multi-beam PUSCH. Figure 8 , the network entity 104 receives 806 from the UE 102 UE capabilities regarding the maximum number of PT-RS ports for SDM multi-beam PUSCH.

[0098] The network entity 104 sends 1208a the configuration for multi-beam PUSCH transmission to the UE. Figure 4 , the network entity 104 sends 408a to the UE 102 a configuration for SFN PUSCH transmission and optionally a maximum number of PT-RS ports for SFN multi-beam PUSCH. Figure 8 , the network entity 104 sends 808a to the UE 102 a configuration for SDM PUSCH transmission and optionally a maximum number of PT-RS ports for SDM multi-beam PUSCH.

[0099] The network entity 104 sends 1208b a trigger indication for multi-beam PUSCH transmission to the UE. Figure 4 , the network entity 104 sends 408b a trigger indication for SFN PUSCH transmission to the UE 102 (eg, indicating resources, at least two precoders, DMRS ports for each PT-RS port used for PUSCH, and / or the number of PT-RS ports). Figure 8, the network entity 104 sends 808b to the UE 102 a trigger indication for the SDM scheme for PUSCH (e.g., indicating resources, at least two precoders, DMRS ports for each PT-RS port for PUSCH, and / or the number of PT-RS ports).

[0100] The network entity 104 receives 1212 multi-beam PUSCH transmission and PT-RS from the UE based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports. Figure 4 And as Figure 7 As shown, the network entity 104 receives 412 SFN PUSCH and PT-RS 202 from the UE 102. Figure 8 And as Figures 9 and 10 As shown, the network entity 104 receives 812 PUSCH and PT-RS 202 using the SDM scheme from the UE 102. Figure 13 As described in FIG. 1 , the UE equipment 1302 may perform the method of the flowchart 1100. Figure 14 As described in , one or more network entities 104 may perform the method of flowchart 1200 .

[0101] Figure 13 13 is a diagram 1300 illustrating an example of a hardware implementation of a UE device 1302. The UE device 1302 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE device 1302 may include an application processor 1306, which may have on-chip memory 1306′. In an example, the application processor 1306 may be coupled to a secure digital (SD) card 1308 and / or a display 1310. The application processor 1306 may also be coupled to a sensor module 1312, a power supply 1314, an additional memory module 1316, a camera 1318, and / or other related components. For example, the sensor module 1312 may control a barometric pressure sensor / altimeter, a motion sensor (such as an inertial management unit (IMU), a gyroscope, an accelerometer), a light detection and ranging (LIDAR) device, a radio-aided detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.

[0102] UE equipment 1302 may further include a wireless baseband processor 1326, which may be referred to as a modem. Wireless baseband processor 1326 may have on-chip memory 1326'. Like and similar to application processor 1306, wireless baseband processor 1326 may also be coupled to sensor module 1312, power supply 1314, additional memory module 1316, camera 1318, and / or other related components. Wireless baseband processor 1326 may also be coupled to one or more subscriber identity module (SIM) cards 1320 and / or one or more transceivers 1330 (e.g., wireless RF transceivers).

[0103] Within one or more transceivers 1330, the UE equipment 1302 may include a Bluetooth module 1332, a WLAN module 1334, an SPS module 1336 (e.g., a GNSS module), and / or a cellular module 1338. The Bluetooth module 1332, the WLAN module 1334, the SPS module 1336, and the cellular module 1338 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1332, the WLAN module 1334, the SPS module 1336, and the cellular module 1338 may each include a dedicated antenna and / or utilize an antenna 1340 to communicate with one or more other nodes. For example, the UE equipment 1302 can communicate with another UE 102 (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication) via the antenna 1340 via the transceiver 1330, where the network entity 104 can correspond to a base station or a unit of a base station, such as a RU 106, a DU 108, or a CU 110.

[0104] The wireless baseband processor 1326 and the application processor 1306 may each include a computer-readable medium / memory 1326′, 1306′, respectively. The additional memory module 1316 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1326′, 1306′, 1316 may be non-transitory. The wireless baseband processor 1326 and the application processor 1306 may each be responsible for general processing, including executing software stored on the computer-readable medium / memory 1326′, 1306′, 1316. This software, when executed by the wireless baseband processor 1326 / application processor 1306, causes the wireless baseband processor 1326 / application processor 1306 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the wireless baseband processor 1326 / application processor 1306 when executing the software. The wireless baseband processor 1326 / application processor 1306 may be a component of the UE 102. UE equipment 1302 may be a processor chip (e.g., modem and / or applications) and include only the radio baseband processor 1326 and / or the application processor 1306. In other examples, UE equipment 1302 may be the entire UE 102 and include additional modules of the equipment 1302.

[0105] like Figure 1 Discussed in and about Figure 11 As implemented, the multi-beam PUSCH transmission component 140 is configured to receive a configuration for a multi-beam PUSCH transmission from a network entity; and send the multi-beam PUSCH transmission and the PT-RS to the network entity based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports. The multi-beam PUSCH transmission component 140 can be within the application processor 1306 (e.g., at 140a), the radio baseband processor 1326 (e.g., at 140b), or both the application processor 1306 and the radio baseband processor 1326. The multi-beam PUSCH transmission components 140a-140b can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0106] Figure 1414 is a diagram 1400 illustrating an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include or may correspond to at least one of the RU 106, the DU 108, or the CU 110. The CU 110 may include a CU processor 1446, which may have on-chip memory 1446'. In some aspects, the CU 110 may further include an additional memory module 1456 and / or a communication interface 1448, both of which may be coupled to the CU processor 1446. The CU 110 may communicate with the DU 108 via a midhaul link 162, such as an F1 interface between the communication interface 1448 of the CU 110 and the communication interface 1428 of the DU 108.

[0107] The DU 108 may include a DU processor 1426, which may have on-chip memory 1426'. In some aspects, the DU 108 may further include an additional memory module 1436 and / or a communication interface 1428, both of which may be coupled to the DU processor 1426. The DU 108 may communicate with the RU 106 via a fronthaul link 160 between the communication interface 1428 of the DU 108 and the communication interface 1408 of the RU 106.

[0108] The RU 106 may include a RU processor 1406, which may have on-chip memory 1406'. In some aspects, the RU 106 may further include an additional memory module 1416, a communication interface 1408, and one or more transceivers 1430, all of which may be coupled to the RU processor 1406. The RU 106 may further include an antenna 1440, which may be coupled to the one or more transceivers 1430, such that the RU 106 may communicate with the UE 102 via the antenna 1440 through the one or more transceivers 1430.

[0109] On-chip memory 1406', 1426', 1446' and additional memory modules 1416, 1436, 1456 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1406, 1426, 1446 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor 1406, 1426, 1446, causes the processor 1406, 1426, 1446 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processor 1406, 1426, 1446 when executing the software. In an example, the multi-beam PUSCH configuration component 150 can be located at any one of the one or more network entities 104, such as at the CU 110; at both the CU 110 and the DU 108; at each of the CU 110, DU 108, and RU 106; at the DU 108; at both the DU 108 and the RU 106; or at the RU 106.

[0110] like Figure 1 Discussed and about Figure 12 As implemented, the multi-beam PUSCH configuration component 150 is configured to send a configuration for multi-beam PUSCH transmission to a UE; and receive a multi-beam PUSCH transmission and a PT-RS from the UE based on the number of PT-RS ports and the DMRS ports associated with the number of PT-RS ports. The multi-beam PUSCH configuration component 150 can be within one or more processors of one or more network entities 104, such as the RU processor 1406 (e.g., at 150a), the DU processor 1426 (e.g., at 150b), and / or the CU processor 1446 (e.g., at 150c). The multi-beam PUSCH configuration components 150a-150c can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors 1406, 1426, 1446 configured to perform the stated processes / algorithms, stored on a computer-readable medium for implementation by one or more processors 1406, 1426, 1446, or a combination thereof.

[0111] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is illustrative of example methods. Therefore, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be merged or deleted. Dashed lines may indicate optional elements of a diagram. The accompanying method claims present elements of each block in an example order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0112] The detailed description set forth herein, in conjunction with the accompanying drawings, describes various configurations and does not represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details to provide a comprehensive explanation of the various concepts. However, these concepts may be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0113] Various aspects of wireless communication systems (such as telecommunication systems) are presented with reference to various apparatus and methods. These apparatus and methods are described in the detailed description that follows and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0114] Element, or any part of an element or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other similar hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software, which can be referred to as software, firmware, middleware, microcode, hardware description language, or other. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, processes, functions, or any combination thereof.

[0115] If the functions described herein are implemented in software, these functions may be stored on a computer-readable medium (such as a non-transitory computer-readable storage medium) or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is accessible to the computer.

[0116] The various aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the various aspects, implementations, and / or use cases can be generated via integrated chip implementations and other non-module component-based devices such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, and the like. The various aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein.

[0117] Devices incorporating aspects and features described herein may also include additional components and features for implementing and practicing the aspects and features claimed and described. For example, the transmission and reception of wireless signals necessarily include many components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., in various configurations.

[0118] The description herein is provided to enable those 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 may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be interpreted in view of the full scope of the disclosure consistent with the language of the claims.

[0119] Unless expressly stated, references to singular elements do not mean "one and only one", but rather "one or more". Terms such as "if", "when" and "at" do not imply an immediate temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a certain condition is met, a certain action will occur, but no specific or immediate time constraint is required for the occurrence of the action. The terms "may", "might" and "can" as used in this disclosure generally carry certain meanings. For example, "may" refers to a permissible feature that may or may not occur, "might" refers to a feature that is likely to occur, and "can" refers to an ability (e.g., to be able to). The phrase "for example" generally carries a similar meaning to "may", and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0120] Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A, B, and C, and may include multiple A's, multiple B's, and / or multiple C's, or may include only A's, only B's, or only C's. A set should be interpreted as a set of elements where the number of elements is one or more.

[0121] Unless otherwise expressly indicated, ordinal terms such as "first" and "second" do not necessarily imply an order in time, sequence, value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. Figure numerals as used in the specification and drawings are sometimes cross-referenced between the drawings to indicate the same or similar features. Features that are identical in multiple drawings may be labeled with the same figure numerals in the multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with figure numerals having different leading digits but one or more of the same trailing digits (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Sometimes, "X" is used to generally indicate multiple variations of a feature. For example, "X06" may generally refer to all reference numbers ending in "06" (e.g., 206, 306, 406, etc.).

[0122] Structural equivalents and functional equivalents of the elements of various aspects described in the entire present disclosure that are known or later learned by those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. The words "module", "mechanism", "element", "device" and the like may not be substitutes for the word "component". Therefore, unless the phrase "component for ..." is used to expressly state the claim elements, any claim element shall not be interpreted as a means plus function. As used herein, the phrase "based on" should not be interpreted as a reference to a closed information set, one or more conditions, one or more factors, etc. In other words, unless explicitly stated differently, the phrase "based on A" (wherein "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

[0123] The following examples are illustrative only and may be combined with other examples or teachings described herein without limitation.

[0124] Example 1 is a method of wireless communication at a UE, comprising: receiving a configuration for a multi-beam PUSCH transmission from a network entity; and sending the multi-beam PUSCH transmission and PT-RS to the network entity based on the number of PT-RS ports and DMRS ports associated with the number of PT-RS ports.

[0125] Example 2 can be combined with Example 1 and include: the multi-beam PUSCH transmission includes one of the following: SFNPUSCH transmission or SDM PUSCH transmission.

[0126] Example 3 can be combined with any one of Examples 1 to 2 and further includes: sending a UE capability report to the network entity indicating at least one of: the UE's capability for the multi-beam PUSCH transmission, the maximum number of PT-RS ports associated with the multi-beam PUSCH transmission, the shared PT-RS ports for the multi-beam PUSCH transmission, or the different PT-RS ports for the multi-beam PUSCH transmission.

[0127] Example 4 can be combined with Example 3 and include that the configuration for the multi-beam PUSCH transmission indicates a maximum number of PT-RS ports.

[0128] Example 5 can be combined with any one of Examples 1 to 4 and further include: receiving a trigger indication from the network entity indicating at least one of the following for the multi-beam PUSCH transmission: one or more SRIs, multiple precoders, the order of the multiple precoders, an EPRE ratio between the multi-beam PUSCH transmission and the PT-RS, the number of PT-RS ports, a DMRS port index, or a DMRS port associated with the number of PT-RS ports.

[0129] Example 6 may be combined with Example 5 and include the trigger indication and configuration for the multi-beam PUSCH transmission being included in the same message.

[0130] Example 7 can be combined with any one of Examples 1 to 6 and includes: the sending further includes: using multiple beams to send PUSCH data, PT-RS and DMRS, and the number of PT-RS ports used to send the PT-RS is based on at least one of the following: the multiple precoders or predefined DMRS ports.

[0131] Example 8 can be combined with any one of Examples 1 to 6 and includes: the transmission further includes: using multiple beams to send PUSCH data and DMRS, and using a single beam to send the PT-RS, and the number of PT-RS ports used for sending the PT-RS is based on at least one of the following: multiple precoders or one or more SRIs.

[0132] Example 9 can be combined with any one of Examples 1 to 6 and includes: the sending further includes: sending PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and sending the PT-RS from a single PT-RS port for a single SRI and a single precoder.

[0133] Example 10 can be combined with any one of Examples 1 to 6, and includes: the sending further includes: sending PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and sending the PT-RS from multiple PT-RS ports for the multiple SRIs and the multiple precoders.

[0134] Example 11 can be combined with any one of Examples 1 to 6 and includes: the sending further includes: sending PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and sending the PT-RS from a single PT-RS port for the multiple SRIs and the multiple precoders.

[0135] Example 12 can be combined with any one of Examples 1 to 11, and includes: the multi-beam PUSCH transmission includes a first beam associated with a first TCI and a second beam associated with a second TCI, the first beam being different from the second beam.

[0136] Example 13 is a method of wireless communication at a network entity, comprising: sending a configuration for a multi-beam PUSCH transmission to a UE; and receiving the multi-beam PUSCH transmission and PT-RS from the UE based on the number of PT-RS ports and DMRS ports associated with the number of PT-RS ports.

[0137] Example 14 can be combined with Example 13, and include: the multi-beam PUSCH transmission includes one of the following: SFN PUSCH transmission or SDM PUSCH transmission.

[0138] Example 15 can be combined with any one of Examples 13 to 14 and further include: receiving a UE capability report from the UE indicating at least one of: the UE's capability for the multi-beam PUSCH transmission, the maximum number of PT-RS ports associated with the multi-beam PUSCH transmission, the shared PT-RS ports for the multi-beam PUSCH transmission, or different PT-RS ports for the multi-beam PUSCH transmission.

[0139] Example 16 can be combined with Example 15, and include the configuration for the multi-beam PUSCH transmission indicating a maximum number of PT-RS ports.

[0140] Example 17 can be combined with any one of Examples 13 to 16, and further includes: sending a trigger indication to the UE indicating at least one of the following for the multi-beam PUSCH transmission: one or more SRIs, multiple precoders, the order of the multiple precoders, the EPRE ratio between the multi-beam PUSCH transmission and the PT-RS, the number of PT-RS ports, a DMRS port index, or a DMRS port associated with the number of PT-RS ports.

[0141] Example 18 may be combined with Example 17 and include the trigger indication and the configuration for the multi-beam PUSCH transmission being included in the same message.

[0142] Example 19 can be combined with any one of Examples 13 to 18 and includes: the receiving further includes: receiving PUSCH data, PT-RS and DMRS using multiple beams, and the number of PT-RS ports for receiving the PT-RS is based on at least one of the following: the multiple precoders or predefined DMRS ports.

[0143] Example 20 can be combined with any one of Examples 13 to 18 and includes: the receiving further includes: receiving PUSCH data and DMRS using multiple beams, and receiving the PT-RS using a single beam, the number of PT-RS ports for receiving the PT-RS being based on at least one of: multiple precoders or one or more SRIs.

[0144] Example 21 can be combined with any one of Examples 13 to 18, and includes: the receiving further includes: receiving PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and receiving the PT-RS from a single PT-RS port for a single SRI and a single precoder.

[0145] Example 22 can be combined with any one of Examples 13 to 18, and includes: the receiving further includes: receiving PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and receiving the PT-RS from multiple PT-RS ports for the multiple SRIs and the multiple precoders.

[0146] Example 23 can be combined with any one of Examples 13 to 18, and includes: the receiving further includes: receiving PUSCH data and DMRS from different layers for multiple SRIs and multiple precoders, and receiving the PT-RS from a single PT-RS port for the multiple SRIs and the multiple precoders.

[0147] Example 24 can be combined with any one of Examples 13 to 23, and includes: the multi-beam PUSCH transmission includes a first beam associated with a first TCI and a second beam associated with a second TCI, the first beam being different from the second beam.

[0148] Example 25 is an apparatus for wireless communication, for implementing a method as described in any one of Examples 1 to 24.

[0149] Example 26 is an apparatus for wireless communication, comprising means for implementing the method of any one of Examples 1 to 24.

[0150] Example 27 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to implement the method of any one of Examples 1 to 24.

Claims

1. A method of wireless communication at a user equipment (UE) (102), comprising: Receiving (408a, 808a) a configuration for multi-beam physical uplink shared channel (PUSCH) transmission from a network entity (104); as well as The multi-beam PUSCH transmission and PT-RS are sent (412, 812) to the network entity (104) based on a number of phase tracking reference signal (PT-RS) ports and a demodulation reference signal (DMRS) port associated with the number of PT-RS ports.

2. The method according to claim 1, wherein The multi-beam PUSCH transmission includes one of the following: Single Frequency Network (SFN) PUSCH transmission, or Spatial domain multiplexing SDM PUSCH transmission.

3. The method according to any one of claims 1 to 2, further comprising: Sending (406, 806) to the network entity (104) a UE capability report indicating at least one of: the UE's capability for the multi-beam PUSCH transmission, the maximum number of PT-RS ports associated with the multi-beam PUSCH transmission, a shared PT-RS port for the multi-beam PUSCH transmission, or Different PT-RS ports used for the multi-beam PUSCH transmission.

4. The method according to claim 3, wherein: The configuration (408a, 808a) for the multi-beam PUSCH transmission indicates the maximum number of PT-RS ports.

5. The method according to any one of claims 1 to 4, further comprising: Receiving (408b, 808b) from the network entity (104) a trigger indication for the multi-beam PUSCH transmission indicating at least one of: One or more sounding reference signal SRS resource indicators SRI, Multiple precoders, the order of the plurality of precoders, an energy per resource element (EPRE) ratio between the multi-beam PUSCH transmission and the PT-RS, the number of PT-RS ports, DMRS port index, or The DMRS ports are associated with the number of PT-RS ports.

6. The method according to claim 5, wherein: The trigger indication (408b, 808b) and the configuration (408a, 808a) for the multi-beam PUSCH transmission are included in the same message.

7. The method according to any one of claims 1 to 6, wherein The sending (412, 812) further includes: PUSCH data (206), the PT-RS (202), and the DMRS (204) are transmitted (412, 812) using multiple beams, the number of PT-RS ports used to transmit (412, 812) the PT-RS (202) is based on at least one of: the multiple precoders or predefined DMRS ports.

8. The method according to any one of claims 1 to 6, wherein The sending (412, 812) further includes: PUSCH data (206) and DMRS (204) are transmitted (412, 812) using multiple beams, and the PT-RS (202) is transmitted (412, 812) using a single beam, the number of PT-RS ports used to transmit (412, 812) the PT-RS (202) being based on at least one of: the plurality of precoders or the one or more SRIs.

9. The method according to any one of claims 1 to 6, wherein The sending (812) further comprises: PUSCH data (206) and DMRS (204) are transmitted (812) from different layers for multiple SRIs and multiple precoders, and the PT-RS (202) is transmitted (812) from a single PT-RS port for a single SRI and a single precoder.

10. The method according to any one of claims 1 to 6, wherein The sending (812) further comprises: PUSCH data (206) and DMRS (204) are transmitted (812) from different layers for multiple SRIs and multiple precoders, and the PT-RS (202) is transmitted (812) from multiple PT-RS ports for the multiple SRIs and the multiple precoders.

11. The method according to any one of claims 1 to 6, wherein The sending (812) further comprises: PUSCH data (206) and DMRS (204) are transmitted (812) from different layers for multiple SRIs and multiple precoders, and the PT-RS (202) is transmitted (812) from a single PT-RS port for the multiple SRIs and the multiple precoders.

12. The method according to any one of claims 1 to 11, wherein The multi-beam PUSCH transmission includes a first beam associated with a first transmission configuration indicator TCI and a second beam associated with a second TCI, the first beam being different from the second beam.

13. A method of wireless communication at a network entity (104), comprising: Sending (408a, 808a) a configuration for multi-beam physical uplink shared channel (PUSCH) transmission to a user equipment (UE) (102); as well as The multi-beam PUSCH transmission and PT-RS are received (412, 812) from the UE (102) based on the number of phase tracking reference signal PT-RS ports and demodulation reference signal DMRS ports associated with the number of PT-RS ports.

14. The method of claim 13, wherein: The multi-beam PUSCH transmission includes one of the following: Single Frequency Network (SFN) PUSCH transmission, or Spatial domain multiplexing SDM PUSCH transmission.

15. An apparatus for wireless communication, comprising a memory, a transceiver, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method according to any one of claims 1 to 14.

Images