WO2025079001A1 - Enhanced ptrs to dmrs port mapping for three tx ues - Google Patents

Abstract

Systems and methods for enhanced Phase Tracking Reference Signals (PTRS) to Demodulation Reference Signal (DMRS) mapping for a three Transmit (TX) User Equipment (UE) are provided. In some embodiments, a method performed by a UE includes: being configured with two PTRS for a three TX chain UE; and determining a PTRS to DMRS association for the UE. In this way, by introducing an overhead efficient and flexible "PTRS-to-UL-layer"-mapping, the overhead signaling can be decreased for UL transmissions for which tracking of phase noise is needed or the PTRS to layer mapping flexibility can be increased which will increase the phase tracking performance.

Description

ENHANCED PTRS TO DMRS PORT MAPPING FOR THREE TX UEs RELATED APPLICATIONS [0001] This application claims the benefit of provisional patent application serial number 63/589,232, filed October 10, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety. TECHNICAL FIELD [0002] The present disclosure relates generally to port mapping. BACKGROUND [0003] NR Frame Structure and Resource Grid [0004] NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both downlink (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (i.e., from UE to gNB). DFT spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally-sized subframes of 1ms each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing. For subcarrier spacing of ∆^ = 15 ^^^, there is only one slot per subframe and each slot consists of 14 OFDM symbols. [0005] Data scheduling in NR is typically in slot basis (an example is shown in Figure 1: which illustrates a NR time-domain structure with 15 kHz subcarrier spacing with a 14-symbol slot) where the first two symbols contain physical downlink control channel (PDCCH) and the rest contains physical shared data channel, either physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH). [0006] Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by ∆^ = ^15 × 2^{^}^^^^ where ^ ∈ 0, 1, 2, 3, 4. ∆^ = 15 ^^^ is the basic subcarrier spacing. The slot durations at different subcarrier spacings are given by ^{^} ^_^ ms. [0007] In the frequency domain, a system bandwidth is divided into resource blocks (RBs), each corresponding to 12 contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time-frequency resource grid is illustrated in Figure 2, where only one resource block (RB) within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE). [0008] Downlink (DL) PDSCH transmissions can be either dynamically scheduled, i.e., in each slot the gNB transmits downlink control information (DCI) over Physical Downlink Control Channel (PDCCH) about which UE data is to be transmitted to and which RBs in the current downlink slot the data is transmitted on, or semi-persistently scheduled (SPS) in which periodic PDSCH transmissions are activated or deactivated by a DCI. Different DCI formats are defined in NR for DL PDSCH scheduling including DCI format 1_0, DCI format 1_1, and DCI format 1_2. [0009] Similarly, uplink (UL) PUSCH transmission can also be scheduled either dynamically or semi-persistently with uplink grants carried in PDCCH. NR supports two types of semi- persistent uplink transmission, i.e., type 1 configured grant (CG) and type 2 configured grant, where Type 1 configured grant is configured and activated by Radio Resource Control (RRC) while type 2 configured grant is configured by RRC but activated/deactivated by DCI. The DCI formats for scheduling PUSCH include DCI format 0_0, DCI format 0_1, and DCI format 0_2. [0010] DMRS configuration [0011] Demodulation reference signals (DM-RS) are used for coherent demodulation of physical layer data channels, i.e., Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH), as well as of Physical Downlink Control Channel (PDCCH). The DM-RS is confined to resource blocks carrying the associated physical layer channel and is mapped on allocated resource elements of the time-frequency resource grid such that the receiver can efficiently handle time/frequency-selective fading radio channels. [0012] The mapping of DM-RS to resource elements is configurable in both frequency and time domain. There are two mapping types in the frequency domain, i.e., type 1 and type 2. In addition, there are two mapping types in the time domain, i.e., mapping type A and type B, which defines the symbol position of the first OFDM symbol containing DM-RS within a transmission interval. [0013] The DM-RS mapping in time domain can further be single-symbol based or double- symbol based, where the latter means that DM-RS is mapped in pairs of two adjacent OFDM symbols. For single symbol based DMRS, a UE can be configured with one, two, three, or four single-symbol DM-RS (also referred to as additional DM-RS) in a slot. For double-symbol based DMRS, a UE can be configured with one or two such double-symbol DM-RS in a slot. In scenarios with low Doppler, it may be sufficient to configure front-loaded DM-RS only, i.e., one single-symbol DM-RS or one double-symbol DM-RS, whereas in scenarios with high Doppler additional DM-RS will be required in a slot. [0014] Figure 3 illustrates a front-loaded DM-RS for configuration type 1 and type 2 where different CDM groups indicated by different shades. Figure 3 shows an example of type 1 and type 2 front-loaded DM-RS with single-symbol and double-symbol DM-RS and time domain mapping type A with first DM-RS in the third OFDM symbol of a transmission interval of 14 symbols. It is observes from this figure that type 1 and type 2 differs with respect to both the mapping structure and the number of supported DM-RS CDM groups where type 1 support 2 CDM groups and Type 2 support 3 CDM groups. [0015] A DM-RS antenna port is mapped to the resource elements within one CDM group only. For single-symbol DM-RS, two antenna ports can be mapped to each CDM group whereas for double-symbol DM-RS four antenna ports can be mapped to each CDM group. Hence, for DM-RS type 1 the maximum number of DM-RS ports is four for a single-symbol based DMRS configuration and eight for double-symbol based DMRS configuration. For DM-RS type 2, the maximum number of DM-RS ports is six for a single-symbol based DMRS configuration and twelve for double-symbol based DMRS configuration. [0016] An orthogonal cover code (OCC) of length 2 (i. e. , ^+1, +1^ or ^+1, −1^) is used to separate antenna ports mapped in the same two resource elements within a CDM group. The OCC is applied in frequency domain (FD) as well as in time domain (TD) when double-symbol DM-RS is configured. This is illustrated in Figure 3 for CDM group 0. [0017] In NR Rel-15, the mapping of a PDSCH DM-RS sequence !^{^}"^{^}, " = 0,1, … on antenna port $ and subcarrier ^ in OFDM symbol % for the numerology index ^ is specified in 3GPP TS38.211 as: ( p ^{, µ )} ₌ ^{DMRS ′ ′} 2 ₊ ^′ 1 2

l= l + l ^′ n = 0,1,... [0018] where w_'^k⁾^ represents a frequency domain length 2 OCC code andw_*^l⁾^ represents a time domain length 2 OCC code. Table 1 and Table 2 show the PDSCH DM-RS mapping parameters for configuration type 1 and type 2, respectively. Table 1. PDSCH DM-RS mapping parameters for configuration type 1. p CDM w_f ( k ′ ) w_t( l ′ ) g_{roup λ} ∆ k^′= 0 k^′= 1 l^′= 0 l^′= 1 1000 0 0 +1 +1 +1 +1 1001 0 0 +1 -1 +1 +1 1002 1 1 +1 +1 +1 +1 1003 1 1 +1 -1 +1 +1 1004 0 0 +1 +1 +1 -1 1005 0 0 +1 -1 +1 -1 1006 1 1 +1 +1 +1 -1 1007 1 1 +1 -1 +1 -1 Table 2. PDSCH DM-RS mapping parameters for configuration type 2. p CDM w ( k ∆ _f ^′ ) w_t( l ^′ ) group λ k′= 0 k′= 1 l′= 0 l′= 1 1000 0 0 +1 +1 +1 +1 1001 0 0 +1 -1 +1 +1 1002 1 2 +1 +1 +1 +1 1003 1 2 +1 -1 +1 +1 1004 2 4 +1 +1 +1 +1 1005 2 4 +1 -1 +1 +1 1006 0 0 +1 +1 +1 -1 1007 0 0 +1 -1 +1 -1 1008 1 2 +1 +1 +1 -1 1009 1 2 +1 -1 +1 -1 1010 2 4 +1 +1 +1 -1 1011 2 4 +1 -1 +1 -1 [0019] For PDSCH mapping type A, DM-RS mapping is relative to slot boundary. That is, the first front-loaded DM-RS symbol in DM-RS mapping type A is in either the 3^rd or 4^th symbol of the slot. In addition to the front-loaded DM-RS, type A DM-RS mapping can consist of up to 3 additional DM-RS. Some examples of DM-RS for mapping type A are shown in Figure 4 (note that PDSCH length of 14 symbols is assumed in the examples). [0020] For PDSCH mapping type B, DM-RS mapping is relative to transmission start. That is, the first DM-RS symbol in DM-RS mapping type B is in the first symbol in which type B PDSCH starts. Some examples of DM-RS for mapping type B are shown in Figure 5. The same DMRS design for PDSCH is also applicable for PUSCH when transform precoding is not enabled, where the sequence r ( m ) shall be mapped to the intermediate quantity ,-^{^0-1,^^} ._,/ for DMRS port $-₂ according to a %⁽p % _j ^, µ ⁾ k _{, l =} w _f ( k ^′ ) w _t ( l ^′ ) r ( 2 n ₊ k ^′ ) 1 2 which

quantity ,-^{^0-1,^^} ._,/ = 0 if Δ corresponds to any other antenna ports than $-₂. [0021] intermediate quantity ,-^{^0-1,^^} ._,/ shall be precoded, multiplied with the amplitude DMR caling factor β S s _PUSCH in order to

to the transmit power specified in clause 6.2.2 of TS 38.214, and mapped to physical resources according to: ,^{^06,^^ ,-^0-6,^^ .,/ .,/} =. [0022] Here,

[0023] the precoding matrix ? is given by clause 6.3.1.5 of TS 38.211, _[0024] {^p _0,..., ^p _{ρ −1} } _{is a set of physical antenna ports used for transmitting the PUSCH,} and [0025] _{ ^~ _p0,..., ^~ _{pυ −1 }} is a set of DMRS ports for the PUSCH; Table 6.4.1.1.3-1: Parameters for PUSCH DM-RS configuration type 1. ~ ^p _CDM w_f ( k ^′ ) w_t( l ^′ ) g^{roup B} k^′= 0 k^′= 1 l^′= 0 l^′= 1 A 0 0 0 +1 +1 +1 +1 1 0 0 +1 -1 +1 +1 2 1 1 +1 +1 +1 +1 3 1 1 +1 -1 +1 +1 4 0 0 +1 +1 +1 -1 5 0 0 +1 -1 +1 -1 6 1 1 +1 +1 +1 -1 7 1 1 +1 -1 +1 -1 Table 6.4.1.1.3-2: Parameters for PUSCH DM-RS configuration type 2. ~ ^p _CDM w_f ( k ^′ ) w_t( l ^′ ) g^{roup B} k′= 0 k′= 1 l′= 0 l′= 1 A 0 0 0 +1 +1 +1 +1 1 0 0 +1 -1 +1 +1 2 1 2 +1 +1 +1 +1 3 1 2 +1 -1 +1 +1 4 2 4 +1 +1 +1 +1 5 2 4 +1 -1 +1 +1 6 0 0 +1 +1 +1 -1 7 0 0 +1 -1 +1 -1 8 1 2 +1 +1 +1 -1 9 1 2 +1 -1 +1 -1 10 2 4 +1 +1 +1 -1 11 2 4 +1 -1 +1 -1 [0026] Phase-tracking reference signals (PTRS) for PUSCH in NR [0027] In NR, phase tracking reference signal (PTRS) can be configured for PUSCH transmissions in order for the receiver to correct phase-noise-related errors. PTRS can be configured with the higher layer parameter PTRS-UplinkConfig in DMRS-UplinkConfig for PUSCH scheduled by DCI format 0_1or DCI format 0_2. [0028] In NR Release 15, for CP-OFDM based waveform, either one or two PTRS ports for PUSCH are supported. Each PTRS port is associated with one of the DM-RS ports for the PUSCH. [0029] If more than one DM-RS port is scheduled, i.e., multi-layer MIMO transmission of PUSCH, then it is desirable from performance perspective if the PTRS is transmitted in the layer having the highest SINR. This will maximize the phase-tracking performance. The network knows which layer has best SINR, based on measurements on the multi-port SRS. Hence, the network can, when scheduling the PUSCH from the UE, indicate which layer the UE shall transmit the PTRS on. This is signaled using PTRS-DMRS association, as defined by the table further down. [0030] The maximum number of configured PTRS ports is given by the higher layer parameter maxNrofPorts in PTRS-UplinkConfig based on the UE reported need. If a UE has reported the capability of supporting full-coherent UL transmission, one PTRS port is expected to be configured if needed. [0031] In the frequency domain, for CP-OFDM based waveform, a PTRS can be in at most one subcarrier per 2 PRBs. Also, the subcarrier used for a PTRS port must be one of the subcarriers also used for the DM-RS port associated with the PTRS port. For DM-RS configuration type 1, a DM-RS port is mapped to every second subcarrier. Consequently, an associated PTRS can only be mapped to one out of 6 subcarriers. An offset can be configured to determine which subcarrier the DM-RS is mapped to (see Table 6.4.1.2.2.1-1 in 3GPP TS 38.211). [0032] In the time domain, a PTRS can be configured with a time density of 1, 2, or 4, corresponding to PTRS in every OFDM symbol, every second OFDM symbols, or every fourth OFDM symbols in a slot, respectively. The modulated symbol used for the PTRS is the same as the associated DM-RS at the same subcarrier. [0033] A PTRS example, for CP-OFDM based waveform, is shown in Figure 6, where the PTRS port is associated with DM-RS port 0 and has a subcarrier offset of 4 and a time density of 2. [0034] For codebook- or non-codebook-based UL transmission, the association between UL PTRS port(s) and DM-RS port(s) is signaled by a “PTRS-DMRS association” field in DCI format 0_1 and DCI format 0_2. [0035] If the UE is configured with one PTRS port, the DM-RS port associated with the PTRS port is indicated by DCI parameter “PTRS-DMRS association” in DCI format 0_1 and DCI format 0_2 in Table 7.3.1.1.2-25 of 3GPP TS 38.212, which is reproduced below. As discussed above the purpose is to schedule the PTRS to be transmitted on the strongest layer/DMRS port (since there is one DMRS port per layer). Value DMRS Port 0 1^st scheduled DMRS port 1 2^nd scheduled DMRS port 2 3^rd scheduled DMRS port 3 4^th scheduled DMRS port [0036] For non-codebook-based UL transmission, the actual number of PTRS port(s) to transmit is determined based on SRI(s) in DCI format 0_1 and DCI format 0_2. A UE is configured with the PTRS port index for each configured SRS resource by the higher layer parameter ptrs-PortIndex configured by SRS-Config. If the PTRS port index associated with different SRIs are the same, the corresponding UL DM-RS ports are associated to the one PTRS port. [0037] For partial-coherent and non-coherent codebook-based UL transmission, the actual number of UL PTRS port(s) is determined based on TPMI and/or number of layers which are indicated by 'Precoding information and number of layers' field in DCI format 0_1 and DCI format 0_2. If the UE is configured with 2 PTRS ports, the actual PTRS port(s) and the associated transmission layer(s) are derived from indicated TPMI as: [0038] PUSCH antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 and 1003 in indicated TPMI share PTRS port 1. [0039] PTRS port 0 is associated with a DM-RS port which are transmitted with PUSCH antenna port 1000 and PUSCH antenna port 1002 in indicated TPMI, and PTRS port 1 is associated with another DM-RS port which are transmitted with PUSCH antenna port 1001 and PUSCH antenna port 1003 in indicated TPMI, where the two DM-RS ports are given by DCI parameter 'PTRS-DMRS association' in DCI format 0_1 and DCI format 0_2 in Table 7.3.1.1.2- 26 of 3gpp TS 38.212, which is reproduced below. [0040] Table 3 PTRS-DMRS association for UL PTRS port 0 and port 1 Value of MSB DMRS Port Value of LSB DMRS Port 0 1^st DMRS port which 0 1^st DMRS port which shares PTRS port 0 shares PTRS port 1 1 2^nd DMRS port which 1 2^nd DMRS port which shares PTRS port 0 shares PTRS port 1 SUMMARY [0041] Systems and methods for enhanced Phase Tracking Reference Signals (PTRS) to Demodulation Reference Signal (DMRS) mapping for a three Transmit (TX) User Equipment (UE) are provided. In some embodiments, a method performed by a UE includes: being configured with two PTRS for a three TX chain UE; and determining a PTRS to DMRS association for the UE. In this way, by introducing an overhead efficient and flexible “PTRS-to- UL-layer”-mapping, the overhead signaling can be decreased for UL transmissions for which tracking of phase noise is needed or the PTRS to layer mapping flexibility can be increased which will increase the phase tracking performance. [0042] In some embodiments, the method also includes: indicating, with a new separate UE capability, support for two PTRS for a three TX chain UE. In some embodiments, the three TX chains are non-coherent or partially coherent. [0043] In some embodiments, two antenna ports are associated with a first PTRS port, and a single antenna port is associated with a second PTRS port. In some embodiments, Physical Uplink Shared Channel (PUSCH) antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1. [0044] In some embodiments, one PTRS port is always associated with one antenna port and that the second PTRS port is associated with one of the other two antenna ports. [0045] In some embodiments, for a partially coherent UE with three TX, where two antenna ports are coherent, and a third antenna port is non-coherent, one of the two PTRS ports is always associated with the non-coherent antenna port and the second PTRS port is always associated with the two coherent PTRS Ports. [0046] In some embodiments, the same PTRS-DMRS association table as illustrated in Table 3 is reused for three TX UE, however, the bit that is associated with the PTRS port associated with a single antenna port is reserved. In some embodiments, when receiving the bitfield, ignoring the reserved bit. In some embodiments, the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. [0047] In some embodiments, the PTRS-DMRS association field in DCI is used for dynamically switching between one or two PTRS ports, for the case when max number of PTRS ports is set to two and when the maximum rank is larger than one. [0048] In some embodiments, a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS-DMRS association for the PTRS port that is associated with two antenna ports. [0049] In some embodiments, if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. In some embodiments, a new PTRS-DMRS association table is used where the two PTRS ports are associated with all combinations of UL layer pairs. BRIEF DESCRIPTION OF THE DRAWINGS [0050] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. [0051] Figure 1 illustrates a NR time-domain structure with 15 kHz subcarrier spacing with a 14-symbol slot; [0052] Figure 2 illustrates a system bandwidth is divided into resource blocks (RBs), each corresponding to 12 contiguous subcarriers; [0053] Figure 3 illustrates a front-loaded DM-RS for configuration type 1 and type 2 where different CDM groups indicated by different shades; [0054] Figure 4 illustrates some examples of DM-RS for mapping type A; [0055] Figure 5 illustrates some examples of DM-RS for mapping type B; [0056] Figure 6 illustrates a PTRS example, for CP-OFDM based waveform, where the PTRS port is associated with DM-RS port 0 and has a subcarrier offset of 4 and a time density of 2; [0057] Figure 7 illustrates a method performed by a UE, according to some embodiments discussed herein; [0058] Figure 8 illustrates a method performed by a network node, according to some embodiments discussed herein; [0059] Figure 9 shows an example of a communication system 900 in accordance with some embodiments; [0060] Figure 10 shows a UE in accordance with some embodiments; [0061] Figure 11 shows a network node in accordance with some embodiments; [0062] Figure 12 is a block diagram of a host, which may be an embodiment of the host of Figure 9, in accordance with various aspects described herein; [0063] Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and [0064] Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION [0065] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. [0066] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [0067] There currently exist certain challenges. In legacy NR specification, when two PTRS ports are configured for a UE, each PTRS ports is associated to two antenna ports as can be seen the below description: “PUSCH antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 and 1003 in indicated TPMI share PTRS port 1.” [0068] For a UE with 3Tx, only the three first three ports will exist (1000, 1001, 1002), which makes the PTRS-DMRS association table (Table 3) incorrect and sub-optimal. [0069] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The invention describes several methods on how to perform an overhead-efficient and flexible indication of a PTRS to DMRS association for a UE with 3 Tx chains. [0070] Certain embodiments may provide one or more of the following technical advantage(s). By introducing an overhead efficient and flexible “PTRS-to-UL-layer”-mapping in DCI the DCI overhead signaling can be decreased for UL transmissions for which tracking of phase noise is needed or the PTRS to layer mapping flexibility can be increase which will increase the phase tracking performance. [0071] First group of embodiments [0072] In one embodiment, the specification text is updated such that two antenna ports are associated with one antenna port, and a single antenna port is associated with a second PTRS port. One example of such specification text is illustrated below: [0073] “PUSCH antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1.” [0074] Please note that other antenna port mappings to PTRS port mappings are possible, the key idea here is that a one PTRS ports always are associated with one antenna port (and hence only is transmitted if that antenna port is used) and that the second PTRS port is associated with one of the other two antenna ports. In one embodiment, for a partially coherent UE with 3 TX, where two antenna ports are coherent (PUSCH port 1000 and PUSCH port 1002), and a third antenna port is non-coherent (PUSCH port 1001), one of the two PTRS ports is always associated with the non-coherent antenna port (PUSCH port 1001) and the second PTRS port is always associated with the two coherent PTRS Ports (PUSCH port 1000 and PUSCH port 1002). The reason for doing this is that two antennas that are mutually coherent and hence precode a layer across both antenna ports only need a single PTRS port. [0075] In one related embodiment, the same PTRS-DMRS association table as illustrated in Table 3 is reused for 3TX UE, however, the bit that is associated with the PTRS port associated with a single antenna port is reserved (since it is no longer needed). In one embodiment, when the UE receives the bitfield, the UE ignores the reserved bit. [0076] In one embodiment, the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. Hence, the PTRS-DMRS association field in DCI can be used for dynamically turning PTRS on/off. [0077] In one embodiment, for the case of 3 Tx UE, the PTRS-DMRS association field in DCI can be used for dynamically switching between 1 or 2 PTRS ports, for the case when max number of PTRS ports is set to 2 (i.e., maxNrofPorts in PTRS-UplinkConfig IE is set to ‘n2’) and when the maximum rank is larger than one. • One example is provided in Table 4, where NW can dynamically switch from using two PTRS ports. Here, for the case of two PTRS ports, a first PTRS port is mapped to the first or second PUSCH port associated with the two coherent antenna ports and a second PTRS port is mapped to the PUSCH port associated with the non-coherent antenna port, or, for the case of one PTRS port, the one PTRS port is associated with a fixed one of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. • Another example is provided in Table 5, where the difference compared to the example in Table 4 is that, for the case of one PTRS port, the one PTRS port is associated with one of (first or second DMRS port which shares PTRS port 0) the PUSCH ports associated with the two coherent antenna ports. [0078] Table 4 Example of PTRS-DMRS association table where a twobit bitfield is used to indicate the association between one or two PTRS ports and up to three DMRS ports for a 3 TX UE configured with 2 PTRS ports. Max #PTRS ports =2 Value DMRS Port 0 _{2 PTRS ports: 1}st st DMRS port which shares PTRS port 0 and 1 DMRS port which shares PTRS port 1 1 _{2 PTRS ports: 2}nd st DMRS port which shares PTRS port 0 and 1 DMRS port w^{hich shares PTRS port 1 2} _{1 PTRS port: 1}st DMRS port which shares PTRS port 0 3 _{1 PTRS port: 1}st D^{MRS port which shares PTRS port 1} [0079] Table 5 Another example of PTRS-DMRS association table where a two-bit bitfield is used to indicate the association between one or two PTRS ports and up to three DMRS ports for a 3 TX UE configured with 2 PTRS ports. Max #PTRS ports =2 V^{alue DMRS Port} 0 _{2 PTRS ports: 1}st st DMRS port which shares PTRS port 0 and 1 DMRS port which shares PTRS port 1 1 _{2 PTRS ports: 2}nd st DMRS port which shares PTRS port 0 and 1 DMRS port which shares PTRS port 1 2 _{1 PTRS port: 1}st DMRS port which shares PTRS port 0 3 _{1 PTRS port: 2}nd D^{MRS port which shares PTRS port 0} [0080] Second group of embodiments [0081] One drawback with the first group of embodiments is that one bit of the PTRS- DMRS association bitfield is unused and hence causes unnecessary overhead. Hence, in one embodiment, a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS-DMRS association for the PTRS port that is associated with two antenna ports. • If one PTRS port is configured (i.e., maxNrofPorts in PTRS-UplinkConfig IE is set to ‘n1’), and two DMRS ports are transmitted from the two coherent antenna ports, the PTRS-DMRS association table in Table 6 is used to indicate the association between the one PTRS port and the two DMRS ports that are transmitted from the two coherent antenna ports. • If two PTRS port is configured (i.e., maxNrofPorts in PTRS-UplinkConfig IE is set to ‘n2’), and two DMRS ports are transmitted from the two coherent antenna ports, the PTRS-DMRS association table in Table 6 is used to indicate the association between a first PTRS port and the two DMRS ports are transmitted from the two coherent antenna ports, and the second PTRS port is mapped to the DMRS port transmitted from the non- coherent antenna port. [0082] Table 6 Example of PTRS-DMRS association table where a single bit is used to indicate the association between one PTRS port and two DMRS ports for a 3 TX UE configured with 1 or 2 PTRS ports. #PTRS ports = 1 or #PTRS ports = 2 V^{alue DMRS Port 0} ₁st DMRS port which shares PTRS port 0 1 ₂nd D^{MRS port which shares PTRS port 0} [0083] In another embodiment, if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, to save 1 bit of overhead compared to legacy NR (Table 7.3.1.1.2-25), the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non- coherent antenna port. One example of how this can look is illustrated in Table 7. [0084] Table 7 Example of PTRS-DMRS association table where a single bit is used to indicate the association between one PTRS port and two DMRS ports (transmitted from different sets of antennas) for a 3 TX UE configured with 1 PTRS port. #PTRS ports = 1 Value DMRS Port 0 ₁st D^{MRS port which shares PTRS port 0 1} ₂nd DMRS port which shares PTRS port 1 [0085] Third group of embodiments [0086] One drawback with the first group and second group of embodiments is that for a non-coherent UE, one PTRS port always is associated with one of the antenna ports, regardless of if the layer transmitted on that antenna port has worse link budget (e.g., worse SINR) than the other two layers. Hence, in one embodiment, to maximize the flexibility of PTRS to DMRS layer indication, a new PTRS-DMRS association table is introduced where the two PTRS ports can be associated with all combinations of UL layer pairs. One example of how this can look is illustrated in Table 8. [0087] Table 8 Example of PTRS-DMRS association table where a two-bit bitfield is used to indicate the association between two PTRS ports and two out of three DRMS ports for a 3 TX UE configured with 2 PTRS ports. #PTRS ports = 2: V^{alue DMRS Port} 0 ₁st nd DMRS port and 2 ^{DMRS port 1} ₁st rd DMRS port and 3 ^{DMRS 2} ₂nd rd DMRS port and 3 3 Reserved [0088] UE capability signaling [0089] In one embodiment the UE indicates with a new separate UE capability support for 2 PTRS for a 3 TX UE. [0090] Figure 7 illustrates a method performed by a UE, according to some embodiments discussed herein. In some embodiments, the UE indicates (step 700) (e.g., with a new separate UE capability) support for 2 PTRS for a 3 TX UE. In some embodiments, the UE determines (step 702) a PTRS to DMRS association for the UE. [0091] Figure 8 illustrates a method performed by a network node, according to some embodiments discussed herein. In some embodiments, the network node receives an indication (step 800) (e.g., with a new separate UE capability) that a UE has support for 2 PTRS for a 3 TX UE. In some embodiments, the network node determines (step 802) a PTRS to DMRS association for the UE. [0092] Figure 9 shows an example of a communication system 900 in accordance with some embodiments. [0093] In the example, the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a Radio Access Network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910A and 910B (one or more of which may be generally referred to as network nodes 910), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 902 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 902 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 902, including one or more network nodes 910 and/or core network nodes 908. [0094] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 910 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 912A, 912B, 912C, and 912D (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections. [0095] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 900 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0096] The UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 910 and other communication devices. Similarly, the network nodes 910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 912 and/or with other network nodes or equipment in the telecommunication network 902 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 902. [0097] In the depicted example, the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0098] The host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and/or the telecommunication network 902 and may be operated by the service provider or on behalf of the service provider. The host 916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0099] As a whole, the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 900 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox. [0100] In some examples, the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunication network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (IoT) services to yet further UEs. [0101] In some examples, the UEs 912 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e., being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC). [0102] In the example, a hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912C and/or 912D) and network nodes (e.g., network node 910B). In some examples, the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 914 may be a broadband router enabling access to the core network 906 for the UEs. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 910, or by executable code, script, process, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 914 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 914 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. [0103] The hub 914 may have a constant/persistent or intermittent connection to the network node 910B. The hub 914 may also allow for a different communication scheme and/or schedule between the hub 914 and UEs (e.g., UE 912C and/or 912D), and between the hub 914 and the core network 906. In other examples, the hub 914 is connected to the core network 906 and/or one or more UEs via a wired connection. Moreover, the hub 914 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 904 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection. In some embodiments, the hub 914 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 910B. In other embodiments, the hub 914 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 910B, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0104] Figure 10 shows a UE 1000 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle- mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0105] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0106] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a power source 1008, memory 1010, a communication interface 1012, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0107] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1002 may include multiple Central Processing Units (CPUs). [0108] In the example, the input/output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0109] In some embodiments, the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and/or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied. [0110] The memory 1010 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems. [0111] The memory 1010 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 1010 may allow the UE 1000 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium. [0112] The processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1018 and/or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., the antenna 1022) and may share circuit components, software, or firmware, or alternatively be implemented separately. [0113] In the illustrated embodiment, communication functions of the communication interface 1012 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth. [0114] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0115] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0116] A UE, when in the form of an IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1000 shown in Figure 10. [0117] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0118] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators. [0119] Figure 11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O- CU). [0120] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS). [0121] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0122] The network node 1100 includes processing circuitry 1102, memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1100 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 1100 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 1100. [0123] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 1100 components, such as the memory 1104, to provide network node 1100 functionality. [0124] In some embodiments, the processing circuitry 1102 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of Radio Frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units. [0125] The memory 1104 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and/or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and the memory 1104 are integrated. [0126] The communication interface 1106 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1106 comprises port(s)/terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. The radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 may be configured to condition signals communicated between the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1120 and/or the amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface 1106 may comprise different components and/or different combinations of components. [0127] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118; instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes the one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112 as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown). [0128] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port. [0129] The antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1100. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node 1100. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment. [0130] The power source 1108 provides power to the various components of the network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0131] Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100. [0132] Figure 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein. As used herein, the host 1200 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1200 may provide one or more services to one or more UEs. [0133] The host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and memory 1212. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of the host 1200. [0134] The memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by a UE for the host 1200 or data generated by the host 1200 for a UE. Embodiments of the host 1200 may utilize only a subset or all of the components shown. The host application programs 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1200 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc. [0135] Figure 13 is a block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 1300 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1300 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. [0136] Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0137] Hardware 1304 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1308A and 1308B (one or more of which may be generally referred to as VMs 1308), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein. The virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308. [0138] The VMs 1308 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1306. Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of the VMs 1308, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment. [0139] In the context of NFV, a VM 1308 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1308, and that part of the hardware 1304 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1308, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1308 on top of the hardware 1304 and corresponds to the application 1302. [0140] The hardware 1304 may be implemented in a standalone network node with generic or specific components. The hardware 1304 may implement some functions via virtualization. Alternatively, the hardware 1304 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1310, which, among others, oversees lifecycle management of the applications 1302. In some embodiments, the hardware 1304 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 1312 which may alternatively be used for communication between hardware nodes and radio units. [0141] Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 912A of Figure 9 and/or the UE 1000 of Figure 10), the network node (such as the network node 910A of Figure 9 and/or the network node 1100 of Figure 11), and the host (such as the host 916 of Figure 9 and/or the host 1200 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14. [0142] Like the host 1200, embodiments of the host 1402 include hardware, such as a communication interface, processing circuitry, and memory. The host 1402 also includes software, which is stored in or is accessible by the host 1402 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1406 connecting via an OTT connection 1450 extending between the UE 1406 and the host 1402. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1450. [0143] The network node 1404 includes hardware enabling it to communicate with the host 1402 and the UE 1406. The connection 1460 may be direct or pass through a core network (like the core network 906 of Figure 9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0144] The UE 1406 includes hardware and software, which is stored in or accessible by the UE 1406 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1406 with the support of the host 1402. In the host 1402, an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and the host 1402. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1450 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1450. [0145] The OTT connection 1450 may extend via the connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide the connection between the host 1402 and the UE 1406. The connection 1460 and the wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0146] As an example of transmitting data via the OTT connection 1450, in step 1408, the host 1402 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1406. In other embodiments, the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction. In step 1410, the host 1402 initiates a transmission carrying the user data towards the UE 1406. The host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406. The request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406. The transmission may pass via the network node 1404 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402. [0147] In some examples, the UE 1406 executes a client application which provides user data to the host 1402. The user data may be provided in reaction or response to the data received from the host 1402. Accordingly, in step 1416, the UE 1406 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1406. Regardless of the specific manner in which the user data was provided, the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404. In step 1420, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402. In step 1422, the host 1402 receives the user data carried in the transmission initiated by the UE 1406. [0148] One or more of the various embodiments improve the performance of OTT services provided to the UE 1406 using the OTT connection 1450, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc. [0149] In an example scenario, factory status information may be collected and analyzed by the host 1402. As another example, the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1402 may store surveillance video uploaded by a UE. As another example, the host 1402 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host 1402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and/or transmitting data. [0150] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1450 between the host 1402 and the UE 1406 in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1450 may be implemented in software and hardware of the host 1402 and/or the UE 1406. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1450 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1404. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1402. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 while monitoring propagation times, errors, etc. [0151] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0152] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally. [0153] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein. [0154] EMBODIMENTS [0155] Group A Embodiments [0156] Embodiment 1: A method performed by a user equipment, UE, the method comprising one or more of: indicating (700) (e.g., with a new separate UE capability) support for 2 PTRS for a 3 TX UE; determining (702) a PTRS to DMRS association for the UE. [0157] Embodiment 2: The method of any of the previous embodiments wherein: the UE has 3 Tx chains. [0158] Embodiment 3: The method of any of the previous embodiments wherein: the UE has 3 TX chains that are non-coherent or partially coherent, and that are configured with two PTRS ports. [0159] Embodiment 4: The method of any of the previous embodiments wherein: two antenna ports are associated with one antenna port, and a single antenna port is associated with a second PTRS port. [0160] Embodiment 5: The method of any of the previous embodiments wherein: PUSCH antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1. [0161] Embodiment 6: The method of any of the previous embodiments wherein: one PTRS ports always are associated with one antenna port (e.g., and hence only is transmitted if that antenna port is used) and that the second PTRS port is associated with one of the other two antenna ports. [0162] Embodiment 7: The method of any of the previous embodiments wherein: for a partially coherent UE with 3 TX, where two antenna ports are coherent (e.g., PUSCH port 1000 and PUSCH port 1002), and a third antenna port is non-coherent (e.g., PUSCH port 1001), one of the two PTRS ports is always associated with the non-coherent antenna port (e.g., PUSCH port 1001) and the second PTRS port is always associated with the two coherent PTRS Ports (e.g., PUSCH port 1000 and PUSCH port 1002). [0163] Embodiment 8: The method of any of the previous embodiments wherein: the same PTRS-DMRS association table as illustrated in Table 3 is reused for 3TX UE, however, the bit that is associated with the PTRS port associated with a single antenna port is reserved. [0164] Embodiment 9: The method of any of the previous embodiments wherein: when the UE receives the bitfield, the UE ignores the reserved bit. [0165] Embodiment 10: The method of any of the previous embodiments wherein: the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. [0166] Embodiment 11: The method of any of the previous embodiments wherein: for the case of 3 Tx UE, the PTRS-DMRS association field in DCI can be used for dynamically switching between 1 or 2 PTRS ports, for the case when max number of PTRS ports is set to 2 (e.g., maxNrofPorts in PTRS-UplinkConfig IE is set to ‘n2’) and when the maximum rank is larger than one. [0167] Embodiment 12: The method of any of the previous embodiments wherein: a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS-DMRS association for the PTRS port that is associated with two antenna ports. [0168] Embodiment 13: The method of any of the previous embodiments wherein: if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, to save 1 bit of overhead compared to legacy NR, the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. [0169] Embodiment 14: The method of any of the previous embodiments wherein: to maximize the flexibility of PTRS to DMRS layer indication, a new PTRS-DMRS association table is introduced where the two PTRS ports can be associated with all combinations of UL layer pairs. [0170] Embodiment 15: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. [0171] Group B Embodiments [0172] Embodiment 16: A method performed by a network node, the method comprising one or more of: receiving (800) an indication (e.g., with a new separate UE capability) that a UE support for 2 PTRS for a 3 TX UE; determining (802) a PTRS to DMRS association for the UE. [0173] Embodiment 17: The method of any of the previous embodiments wherein: the UE has 3 Tx chains. [0174] Embodiment 18: The method of any of the previous embodiments wherein: the UE has 3 TX chains that are non-coherent or partially coherent, and that are configured with two PTRS ports. [0175] Embodiment 19: The method of any of the previous embodiments wherein: two antenna ports are associated with one antenna port, and a single antenna port is associated with a second PTRS port. [0176] Embodiment 20: The method of any of the previous embodiments wherein: PUSCH antenna port 1000 and 1002 in indicated TPMI share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1. [0177] Embodiment 21: The method of any of the previous embodiments wherein: one PTRS ports always are associated with one antenna port (e.g., and hence only is transmitted if that antenna port is used) and that the second PTRS port is associated with one of the other two antenna ports. [0178] Embodiment 22: The method of any of the previous embodiments wherein: for a partially coherent UE with 3 TX, where two antenna ports are coherent (e.g., PUSCH port 1000 and PUSCH port 1002), and a third antenna port is non-coherent (e.g., PUSCH port 1001), one of the two PTRS ports is always associated with the non-coherent antenna port (e.g., PUSCH port 1001) and the second PTRS port is always associated with the two coherent PTRS Ports (e.g., PUSCH port 1000 and PUSCH port 1002). [0179] Embodiment 23: The method of any of the previous embodiments wherein: the same PTRS-DMRS association table as illustrated in Table 3 is reused for 3TX UE, however, the bit that is associated with the PTRS port associated with a single antenna port is reserved. [0180] Embodiment 24: The method of any of the previous embodiments wherein: when the UE receives the bitfield, the UE ignores the reserved bit. [0181] Embodiment 25: The method of any of the previous embodiments wherein: the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. [0182] Embodiment 26: The method of any of the previous embodiments wherein: for the case of 3 Tx UE, the PTRS-DMRS association field in DCI can be used for dynamically switching between 1 or 2 PTRS ports, for the case when max number of PTRS ports is set to 2 (e.g., maxNrofPorts in PTRS-UplinkConfig IE is set to ‘n2’) and when the maximum rank is larger than one. [0183] Embodiment 27: The method of any of the previous embodiments wherein: a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS-DMRS association for the PTRS port that is associated with two antenna ports. [0184] Embodiment 28: The method of any of the previous embodiments wherein: if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, to save 1 bit of overhead compared to legacy NR, the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. [0185] Embodiment 29: The method of any of the previous embodiments wherein: to maximize the flexibility of PTRS to DMRS layer indication, a new PTRS-DMRS association table is introduced where the two PTRS ports can be associated with all combinations of UL layer pairs. [0186] Embodiment 30: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. [0187] Group C Embodiments [0188] Embodiment 31: A user equipment, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. [0189] Embodiment 32: A network node, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry. [0190] Embodiment 33: A UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. [0191] Embodiment 34: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. [0192] Embodiment 35: The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. [0193] Embodiment 36: A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. [0194] Embodiment 37: The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. [0195] Embodiment 38: The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. [0196] Embodiment 39: A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. [0197] Embodiment 40: The communication system of the previous embodiment, further comprising: the network node; and/or the UE. [0198] Embodiment 41: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host. [0199] Embodiment 42: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. [0200] Embodiment 43: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. [0201] Embodiment 44: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. [0202] Embodiment 45: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host. [0203] Embodiment 46: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host. [0204] Embodiment 47: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host. [0205] Embodiment 48: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. [0206] Embodiment 49: A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host. [0207] Embodiment 50: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application. [0208] Embodiment 51: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. [0209] Embodiment 52: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host. [0210] Embodiment 53: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. [0211] Embodiment 54: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. [0212] Embodiment 55: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host. [0213] Embodiment 56: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. [0214] Embodiment 57: The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

ABBREVIATIONS At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). 1x RTT CDMA2000 1x Radio Transmission Technology 3GPP 3rd Generation Partnership Project 5G 5th Generation 6G 6th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band CQI Channel Quality information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DCI Downlink Control Information DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services E-SMLC Evolved-Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PTRS Phase Tracking Reference Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR Reference Signal Received Power RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TMPI Transmitted Precoding Matrix Indicator TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wide CDMA WLAN Wide Local Area Network

Claims

CLAIMS 1. A method performed by a User Equipment, UE, the method comprising: being configured with two Phase Tracking Reference Signals, PTRSs, for a three Transmit, TX, chain UE; and determining a PTRS to Demodulation Reference Signal, DMRS, association for the UE. 2. The method of claim 1 further comprising: indicating, with a new separate UE capability, support for two PTRSs for a three TX chain UE. 3. The method of any of claims 1-2 wherein: the three TX chains are non-coherent or partially coherent. 4. The method of any of claims 1-3 wherein: two antenna ports are associated with a first PTRS port, and a single antenna port is associated with a second PTRS port. 5. The method of claim 4 wherein: Physical Uplink Shared Channel, PUSCH, antenna port 1000 and 1002 in an indicated Transmitted Precoding Matrix Indicator, TPMI, share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1. 6. The method of any of claims 1-5 wherein: one PTRS port is always associated with one antenna port and that the second PTRS port is associated with one of the other two antenna ports. 7. The method of any of claims 1-6 wherein: for a partially coherent UE with three TXs where two antenna ports are coherent and a third antenna port is non-coherent, one of the two PTRS ports is always associated with the non-coherent antenna port, and the second PTRS port is always associated with the two coherent PTRS Ports. 8. The method of any of claims 1-7 wherein: the same PTRS-DMRS association table as illustrated in Table 3 is reused for three TX UE, however, a bit that is associated with the PTRS port associated with the single antenna port is reserved.

9. The method of claim 8 further comprising: when receiving a bitfield, ignoring the reserved bit. 10. The method of any of claims 8-9 wherein: the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. 11. The method of any of claims 1-10 wherein: the PTRS-DMRS association field in Downlink Control Information, DCI, is used for dynamically switching between one or two PTRS ports, for the case when a maximum number of PTRS ports is set to two and when a maximum rank is larger than one. 12. The method of any of claims 1-11 wherein: a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS- DMRS association for the PTRS port that is associated with two antenna ports. 13. The method of any of claims 1-12 wherein: if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. 14. The method of any of claims 1-13 wherein: a new PTRS-DMRS association table is used where the two PTRS ports are associated with all combinations of Uplink, UL, layer pairs. 15. A method performed by a network node, the method comprising: configuring a three Transmit, TX, chain User Equipment, UE, with two Phase Tracking Reference Signals, PTRSs; and determining a PTRS to Demodulation Reference Signal, DMRS, association for the UE. 16. The method of claim 15 further comprising: receiving an indication, with a new separate UE capability, that a UE supports two PTRSs for a three TX chain UE. 17. The method of any of claims 15-16 wherein: the three TX chains are non-coherent or partially coherent.

18. The method of any of claims 15-17 wherein: two antenna ports are associated with a first PTRS port, and a single antenna port is associated with a second PTRS port. 19. The method of claim 18 wherein: Physical Uplink Shared Channel, PUSCH, antenna port 1000 and 1002 in an indicated Transmitted Precoding Matrix Indicator, TPMI, share PTRS port 0, and PUSCH antenna port 1001 is associated with PTRS port 1. 20. The method of any of claims 15-19 wherein: one PTRS port is always associated with one antenna port and that the second PTRS port is associated with one of the other two antenna ports. 21. The method of any of claims 15-20 wherein: for a partially coherent UE with three TX where two antenna ports are coherent and a third antenna port is non-coherent, one of the two PTRS ports is always associated with the non-coherent antenna port and the second PTRS port is always associated with the two coherent PTRS Ports. 22. The method of any of claims 15-21 wherein: the same PTRS-DMRS association table as illustrated in Table 3 is reused for three TX UEs, however, a bit that is associated with the PTRS port associated with the single antenna port is reserved. 23. The method of claim 22 further comprising: when the UE receives a bitfield, the UE ignores the reserved bit. 24. The method of any of claims 22-23 wherein: the reserved bit is re-used to indicate that no PTRS transmission shall be transmitted for the scheduled PUSCH transmission. 25. The method of any of claims 15-24 wherein: the PTRS-DMRS association field in Downlink Control Information, DCI, is used for dynamically switching between one or two PTRS ports, for the case when a maximum number of PTRS ports is set to two and when the maximum rank is larger than one. 26. The method of any of claims 15-25 wherein: a new PTRS-DMRS association table is introduced as illustrated in Table 6 where a single-bit bitfield is used to indicate the PTRS- DMRS association for the PTRS port that is associated with two antenna ports.

27. The method of any of claims 15-26 wherein: if one PTRS port is configured and PUSCH is transmitted from antenna ports associated with both PTRS ports, the one PTRS port is associated with the first of the PUSCH ports associated with the two coherent antenna ports or the PUSCH port associated with the non-coherent antenna port. 28. The method of any of claims 15-27 wherein: a new PTRS-DMRS association table is used where the two PTRS ports are associated with all combinations of Uplink, UL, layer pairs. 29. A User Equipment, UE, (1000) comprising processing circuitry (1002) and memory (1010), the memory (1010) comprising instructions to cause the UE (1000) to: be configured with two Phase Tracking Reference Signals, PTRSs, for a three Transmit, TX, chain UE; and determine a PTRS to Demodulation Reference Signal, DMRS, association for the UE. 30. The UE (1000) of claim 29 further operable to implement the features of any of claims 2- 14. 31. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 14. 32. A network node (1100) comprising processing circuitry (1102) and memory (1104), the memory (1104) comprising instructions to cause the network node (1100) to: configure a three Transmit, TX, chain User Equipment, UE, with two Phase Tracking Reference Signals, PTRS; and determine a PTRS to Demodulation Reference Signal, DMRS, association for the UE. 33. The network node (1100) of claim 32 further operable to implement the features of any of claims 16-28.

46. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 15-28.