Radio node, configuring node, and methods performed therein

Abstract

A method (1200) performed by a radio node (110) for handling communication in a wireless communication network (1), wherein the radio node is a user equipment (10) or a radio network node (12). The method comprises configuring (1201) the radio node with a configuration, the configuration comprising one or more zero-power, ZP, phase tracking reference symbols, PTRS, 5 ports. Alternatively, the method comprises receiving (1203) the configuration from a configuring node (120).

Description

[0001]RADIO NODE, CONFIGURING NODE, AND METHODS PERFORMED THEREIN TECHNICAL FIELDEmbodiments herein relate to a radio node such as a user equipment (UE) or a radio networknode, a configuring node and methods performed therein regarding wireless communication.Furthermore, a computer program product and a computer readable storage medium are alsoprovided herein. In particular, embodiments herein relate to handling communication, such asmeasurements, in a wireless communication network.BACKGROUNDIn a typical wireless communication network, UEs, also known as wireless communication devices,mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network(RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network nodesuch as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in somenetworks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area orcell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink(DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.A Universal Mobile Telecommunications System (UMTS) is a third generation (3G)telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP andcoming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as SystemArchitecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technologywherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such astransmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), User Plane Function (UPF), Access and Mobility Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the Network Repository Function (NRF). New radio (NR) standard in 3GPP is being designed to provide service for multiple use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.An NR slot consists of several orthogonal frequency division multiplexing (OFDM) symbols,according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing ≤ 60 kHz) and14 symbols (OFDM subcarrier spacing > 60 kHz). Figure 1 shows a slot with 14 OFDM symbols. InFigure 1, ^^ and ^^^^^ denote the slot and OFDM symbol duration, respectively.The difference of DFT-s-OFDM compared to Cyclic Prefix (CP)-OFDM is that DFT-s-OFDM has a DFT for converting modulated symbols, e.g., Binary Phase Shift Keying(BPSK) / Quadrature PhaseShift Keying(QPSK) / Quadrature Amplitude Modulation(QAM) symbols, to frequency domain beforemapping to subcarriers, while in CP-OFDM, modulated symbols are directly mapped to subcarriers in frequency domain. To support the many types of targeted use cases with varying requirements, different types of duplex communication modes are discussed in 3GPP standardization. Moreover, the same device may be capable of operating using different duplex modes, for e.g., to achieve different overall communication performance based on its needs. Transmission and reception from a wireless communication device, e.g., a base-station (BS) or a user equipment (UE) in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). The most relevant duplex modes are discussed below.Figure 2 shows different types of duplex communication modes.Frequency Division Duplex (FDD), as illustrated to the top left in Figure 2, implies that transmission(TX) and reception (RX) take place in different, sufficiently separated carriers. Thus, FDD requires paired spectrum. In case of FDD operation, there are two carrier frequencies, one for uplink (UL) transmission and one for downlink (DL) transmission. At least with respect to the UE in a cellular communication system, FDD can be either full duplex (FD-FDD) or half duplex (HD-FDD). In the FD-FDD case, a UE can transmit and receive simultaneously, while in HD-FDD operation, the UE cannot transmit and receive simultaneously (the BS is still capable of simultaneous RX / TX though, e.g. receiving from one UE while simultaneously transmitting to another UE). In LTE, a HD-FDD terminal is monitoring / receiving in the DL except when explicitly being instructed to transmit in acertain subframe. Paired Carrier 1, used for RX, and Paired Carrier 2, used for TX, are in Figure 2illustrated separated by a frequency guardband.Time Division Duplex (TDD), as illustrated to the top right in Figure 2, implies that TX and RX takeplace within the same carrier, Carrier 1, in different, non-overlapping time slots. Thus, TDD canoperate in unpaired spectrum. In case of TDD operation, there is only a single carrier frequency and UL and DL transmissions are always separated in time also on a cell basis. As the same carrier frequency is used for UL and DL transmission, both the BS and the UEs need to switch from TX to RX and vice versa. An aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither DL nor UL transmissions occur. This is required to avoid interference between UL and DL transmissions. For NR, this guard time is provided by special slots, which are split into three parts: symbols for DL, a guard period (GP), and symbols for UL.The remaining slots are either allocated to UL or DL transmission. In static TDD the ratio betweenUL and DL is allocated statically.Sub-Band Full Duplex (SBFD), as illustrated to the bottom left in Figure 2, is being studied in 3GPPRelease 18 as a part of the 5G-Advanced standardization. In case of SBFD operation, a portion of a wide bandwidth carrier, termed sub-band(s), may be used for a different communication direction than that of the rest of the carrier. An example of SBFD, illustrated to the bottom left in Figure 2,shows Carrier 1 divided in three sub carriers used for different communication directions, in a firsttime interval. The example further shows the use of multiple carriers in a second time interval. Thisis unlike the conventional TDD operation wherein the entire bandwidth of the carrier is always used either for DL or UL. SBFD operation can also be performed across different carriers within the same frequency band, wherein one or more carriers within a frequency band may be used for a different communication direction than that of the other carriers, which is again unlike conventional TDD operation wherein all carriers within a frequency band are always used for the same communication direction. In the 3GPP Release 18 study, the scope has been limited such that during SBFD operation, only BSs transmit DL and receive UL simultaneously using corresponding non-overlapping sub-bands. An individual UE is scheduled in only one direction (DL or UL) at a time, following conventional HD TDD operation, referred to as HD-SBFD. However, for future releases such as Release 19, SBFD operation at UEs is also being discussed as a potential studytopic, referred to as SBFD. Other similar duplex technologies being investigated are sub-band non-overlapping full duplex, and cross division duplex (XDD).Single frequency full duplex (SFFD), as illustrated to the bottom right in Figure 2, has also beenproposed to be studied in 3GPP standardization. It was discussed but excluded from the scope of Release 18, and it is now again being discussed during scoping discussions for Release 19. Incase of SFFD operation, the entire bandwidth of the same carrier, Carrier 1, in a single carriersystem or all carriers in a multi-carrier system can be simultaneously used for DL and UL operations. In other words, the same time and frequency resources can be used for both TX and RX at the same device. Similar to SBFD operation, SFFD operation is also being discussed as apotential study topic for both BSs and UEs. Other similar duplex technologies being investigatedare in-band full duplex (IBFD), and conventional full duplex.Since a gNodeB (gNB) transmits on the DL while at the same time receives on the UL, there is therisk of strong SBFD self-interference. In an ideal situation with no RF / analog imperfections intransmitter or receiver, the fact that DL and UL are transmitted on different subbands, combined with the orthogonality between OFDM subcarriers, will effectively lead to no self-interference between Tx and Rx. However, in real equipment with imperfections, there will be self-interference through two mechanisms: - The Tx signal is distorted due to transmitter-side imperfections, in particular non-linearities in the power amplifier (PA). This will lead to power being transmitted also in the UL subband, and hence cause interference to the desired UL signal. - The receiver analog components, e.g. the low-noise amplifier (LNA), have non-linearities. This makes the receiver capture power also from the DL subband. SUMMARYAn object of embodiments herein is to handle communication such as measurements in a wirelesscommunication network in an efficient manner, e.g., with respect to throughput.According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a radio node such as a radio network node or a user equipment(UE) for handling communication in a wireless communication network. The radio node isconfigured with a configuration, the configuration comprising one or more zero-power (ZP) phasetracking reference symbols (PTRS) ports. Alternatively, the radio node receives the configurationfrom a configuring node. The configuration may comprise one or more non-zero power, NZP,PTRS ports, and one or more ZP-PTRS ports, separately. The method may comprise comprising performing a measurement using the one or more ZP-PTRS ports. According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a configuring node, such as gNB, for handling communication,e.g., measurements, in a wireless communication network. The configuring node configures aradio node with a configuration, the configuration comprising one or more zero-power, ZP, phasetracking reference symbols, PTRS, ports. Alternatively, the configured node transmits theconfiguration to the radio node. The configuration may comprise one or more non-zero power,NZP, PTRS ports, and one or more ZP-PTRS ports, separately. The method may comprisecomprising exchanging the configuration with a radio network node. It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methodsherein, as performed by the radio node and the configuring node, respectively. It is additionallyprovided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at leastone processor to carry out the methods herein, as performed by the radio node and the configuringnode, respectively. According to another aspect the object is achieved by providing a radio node, and a configuring node configured to perform the methods herein, respectively.According to embodiments herein it is herein provided effective inter-node interferencemeasurement using one or more systematic muting patterns that are similar to existing reference symbol locations. This avoids potential conflicts of muting and existing signals, and also minimizes the implementation complexity and costs. Thus, embodiments herein handle an efficient communication in a wireless communication network. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments will now be described in more detail in relation to the enclosed drawings, in which:Figures 1, 2 are schematic overviews depicting prior art.Figure 3 illustrates resource elements muting in one OFDM symbol of a slot, either full-symbolmuting or muting of every 2nd subcarrier.Figure 4 illustrates an example of PTRS structure for a PUSCH with DFT-s-OFDM waveform.Figure 5 illustrates an example of a wireless communication network in accordance with someembodiments.Figure 6 shows a diagram depicting PUSCH throughput over an SBFD slot.Figure 7 is a schematic flowchart depicting a method performed by a radio node according toembodiments herein.Figure 8 is a schematic flowchart depicting a method performed by a configuring node according toembodiments herein.Figure 9 shows a block diagram depicting embodiments of a radio node according to embodimentsherein.Figure 10 illustrates a computer program product and a computer-readable storage medium.Figure 11 shows a block diagram depicting embodiments of a configuring node according toembodiments herein.Figure 12 illustrates a computer program product and a computer-readable storage medium.Figure 13 shows an example of a communication system in accordance with some embodiments.Figure 14 shows a UE in accordance with some embodiments.Figure 15 shows a network node in accordance with some embodiments.Figure 16 is a block diagram of a host.Figure 17 is a block diagram illustrating a virtualization environment in which functionsimplemented by some embodiments may be virtualized.Figure 18 shows a communication diagram of a host communicating via a network node with a UEover a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTIONFigure 3 illustrates resource elements (RE) muting in one OFDM symbol of a slot, either full-symbol muting or muting of every 2nd subcarrier.In 3GPP TR 38.858 v18.0.0 has been proposed that some REs of an Orthogonal FrequencyDivision Multiplexing (OFDM) symbol in uplink (UL) transmissions could be muted in order to allowthe gNodeB (gNB) to more accurately estimate downlink (DL) interference. The DL interference isestimated by measuring the DL interference on muted RE not influenced by UL signals. Muting canbe either a, or multiple of, full OFDM symbol or a subset of the subcarriers, e.g. every 2ndsubcarrier as illustrated in Figure 3, every 3rd subcarrier, every 4th subcarrier, etc. Data is supposedto be rate-matched around the muted RE, i.e. muting in principle does not change code rate, but does reduce the number of transmitted bits and hence decreases throughput.Phase tracking reference symbols (PTRS) are defined in the NR specifications to enable receiversto estimate effects of phase noises. These PTRS are particularly useful for NR carriers in higherfrequency ranges, such as the FR2. The PTRS are defined for both downlink and uplinktransmissions in NR. For a physical downlink shared channel (PDSCH) or physical uplink sharedchannel (PUSCH), the accompanying PTRS are confined to the scheduled bandwidth in thefrequency domain and the scheduled OFDM symbols in the time domain. For a PDSCH, orPUSCH, with cyclic prefix (CP)-OFDM waveform, different frequency domain density and timedomain density are supported. The time domain density can be one of ^^^^^^ = 1, 2 or 4. Thesedensities correspond to one PTRS presence every OFDM symbol, every two OFDM symbols, or every four OFDM symbols.The frequency domain density can be one of ^^^^^^ = 2 or 4. These densities correspond to onePTRS subcarrier every two RBs or every four RBs.In the current NR specifications, the time domain density is determined in two steps. First thenetwork can provide RRC configuration of a set of three threshold modulation and coding scheme (MCS): ptrs-MCS1, ptrs-MCS2 and ptrs-MCS3. If the configuration is not provided by the network,specific threshold values are listed in the NR TS 38.213 v18.1.0. The actual time domain densityaccompanying a PDSCH or a PUSCH is determined by comparing the MCS for the scheduled PDSCH or PUSCH, which is denoted by IMCS, to the three MCS thresholds. Table 1 illustrates the time density of PTRS as a function of scheduled MCS. Table 1Scheduled MCS Time density (^^^^^^)IMCS < ptrs-MCS1 PTRS is not presentptrs-MCS1 ^ IMCS < ptrs-MCS2 4ptrs-MCS2 ^ IMCS < ptrs-MCS3 2ptrs-MCS3 ^ IMCS < ptrs-MCS4 1In the current 3GPP NR specifications, the frequency domain density is determined in two steps. First the network can provide RRC configuration of a set of two threshold RB sizes: NRB0 and NRB1. If the configuration is not provided by the network, specific threshold values are listed in theNR TS 38.213. The actual frequency domain density accompanying a PDSCH or a PUSCH isdetermined by comparing the allocated number of RBs for the schedule PDSCH or PUSCH, whichis denoted by NRB, to the two RB size thresholds. Table 2 illustrates the frequency density ofPTRS as a function of scheduled bandwidth. Table 2Scheduled bandwidth Frequency density (^^^^^^)NRB < NRB0 PTRS is not presentNRB0 ^ NRB < NRB1 2NRB1 ^ NRB 4Figure 4 illustrates an example of PTRS structure for a PUSCH with DFT-s-OFDM waveform. For aPUSCH with DFT-S-OFDM waveform, the PTRS are inserted in the time domain amongst the modulated symbols of the PUSCH data. The time density of a PTRS for a DFT-s-OFDM waveformis either ^^^^^^ = 2 if the network provides such time density configuration, or ^^^^^^ = 1 if thenetwork does not provide a configuration of time density. In the current NR specifications, thesample density of the PTRS for a DFT-s-OFDM waveform within an OFDM symbol is a function of the number of PTRS groups and the number of samples per group. The sample density is determined in two steps. First the network provides RRC configuration of aset of five threshold RB sizes: NRBi, where i=0, 1, …, 5. The actual sample density accompanyingthe PUSCH with DFT-S-OFDM waveform is determined by comparing the allocated number of RBs for the schedule PUSCH, which is denoted by NRB, to the five RB size thresholds as shown inTable 3. This determines the number of PTRS groups and number of samples per group. Table 3illustrates the sample density of PTRS for PUSCH with DFT-S-OFDM waveform within an OFDM symbol as a function of scheduled bandwidth. Table 3 Number of PTRS groups Number of samples per group Scheduled bandwidth ^gP rT oR upS ^ group sampleNRB0 ^NRB < NRB1 2 2NRB1 ^ NRB < 2 4NRB2NRB2 ^ NRB < 4 2NRB3NRB3 ^ NRB < 4 4NRB4NRB4 ^ NRB 8 4 When a PTRS is configured for a PDSCH or a PUSCH, the PTRS is associated with the demodulation reference signal (DMRS) port of the scheduled PDSCH or PUSCH. A UE receives the PTRS using a suitable receiver setting corresponding to the antenna port associated with the PTRS. In the current NR specifications, at most two PTRS ports, i.e., antenna ports associatedwith the PTRS, can be configured for PDSCH or PUSCH with CP-OFDM waveform.The current higher layer configuration for downlink PTRS is shown below:-- ASN1STARTPTRS-DownlinkConfig ::= SEQUENCE {frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need StimeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29 OPTIONAL, -- Need Sepre-Ratio INTEGER (0..3)OPTIONAL, -- Need SresourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need S..., [[maxNrofPorts-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R]] }-- ASN1STOPThe current higher layer configuration for uplink PTRS is shown below for both CP-OFDM (transformPrecoderDisabled) and DFT-s-OFDM (transformPrecoderEnabled):-- ASN1STARTPTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need StimeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2},resourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need Sptrs-Power ENUMERATED {p00, p01, p10, p11}} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity SEQUENCE (SIZE (5)) OF INTEGER (1..276),timeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S} OPTIONAL, -- Need R..., [[ maxNrofPorts-SDM-r18 ENUMERATED {n1, n2} OPTIONAL -- Need R]] }-- ASN1STOPNR PTRS and DMRS port association for PDSCH or PUSCH with CP-OFDM waveform. ForPDSCH reception, in case one PTRS port is configured, and the user equipment (UE) is scheduledwith a single codeword, the PTRS port is associated with the lowest indexed DMRS port amongst the DMRS antenna ports indicated by the ‘Antenna port(s)’ field in the scheduling DCI, e.g., DCI 1_1. If the UE is scheduled with two codewords, the PTRS antenna port is associated with the lowest indexed DMRS antenna port among the DMRS antenna ports assigned for the codeword with the higher MCS. If the MCS indices of the two codewords are the same, the PTRS antenna port is associated with the lowest indexed DMRS antenna port assigned for codeword 0. For DL, the UE can be configured with two PTRS ports for the case of multi-Transmission andReception Point (TRP) operation for which either one or two Transmission Configuration Indication(TCI) states can be indicated. The number of actual PTRS ports that the UE receives is 1 or 2depending on whether 1 or 2 TCI states are indicated by the 'Transmission Configuration Indication' field in the scheduling DCI, respectively. Each of the PTRS antenna ports is associated with the lowest indexed DMRS antenna port among the DMRS antenna ports of the Code DivisionMultiplexing (CDM) group associated with an indicated TCI state.In all cases above, the specific sub-carrier within a PRB occupied by a PTRS antenna port varies dynamically depending on the specific DMRS antenna ports indicated by the ‘Antenna port(s)’ field in the DCI that schedules PDSCH, e.g., DCI 1_1. For PUSCH transmission with transform precoding disabled, i.e., for CP-OFDM, the UE can be configured with either one or two PTRS ports. In the case that two PTRS ports are configured, thenumber of actual PTRS ports, 1 or 2, depends on the DMRS port(s) indicated by the ‘Antennaport(s)’ field and the number of layers and precoding matrix indicated by the ‘Precoding information and number of layers’ field in the scheduling DCI, e.g., DCI 0_1. For a given PTRS antenna port, the associated DMRS port is determined dynamically based on the scheduling DCI in a different way than for the DL described above. As an example, thescheduling DCI, e.g., DCI 0_1, indicates, in the case of codebook-based precoding for UL, thefollowing: -The “Precoding information and number of layers” field indicates a number of layers (i.e.,the transmission rank) and a precoding matrix. In particular, the “Precoding information andnumber of layers” field indicates a row in a particular table specified in 3GPP TS 38.212v18.1.0, e.g., Table 7.3.1.1.2-2 for up to 4-port PUSCH, where each row contains adifferent combination of number of layers and precoding matrix index (TPMI).- The “Antenna port(s)” field indicates a number of DMRS antenna ports. In particular, the“Antenna port(s)” field indicates a row in a particular table specified in 3GPP TS 38.212 v18.1.0, e.g., Tables 7.3.1.1.2-8 / 9 / 10 / 11 for up to 4-port PUSCH, where the specific table out of these 4 tables is determined by the number of layers indicated in the “Precoding information and number of layers” field in the scheduling DCI. Each row contains a differentcombination of DMRS antenna ports. -The “PTRS-DMRS association” field indicates an indicator of a DMRS-PTRS association. Inparticular, the “PTRS-DMRS association” field indicates a row in a particular table specifiedin 3GPP TS 38.212 v18.1.0, e.g., Table 7.3.1.1.2-25 / 26 for up to 4-port PUSCH, where thespecific table out of these 2 tables is determined by the number of actual PTRS ports which is a function of the number of layers indicated in the “Precoding information and number of layers” field in the scheduling DCI, and the specific DMRS ports indicated by the “Antennaport(s)” field in the scheduling DCI. Each row indicates a different DMRS-PTRSassociation. Table 7.3.1.1.2-2: Bit codebookSubset = Bit codebookSubset = Bit codebookSubse field fullyAndPartialAndNonCohe field partialAndNonCoher field t= nonCoherent mappe rent mappe ent mappe d to d to d to index index index0 1 layer: TPMI=0 0 1 layer: TPMI=0 0 1 layer: TPMI=01 1 layer: TPMI=1 1 1 layer: TPMI=1 1 1 layer: TPMI=1… … … … … …3 1 layer: TPMI=3 3 1 layer: TPMI=3 3 1 layer: TPMI=34 2 layers: TPMI=0 4 2 layers: TPMI=0 4 2 layers:TPMI=0… … … … … …9 2 layers: TPMI=5 9 2 layers: TPMI=5 9 2 layers:TPMI=510 3 layers: TPMI=0 10 3 layers: TPMI=0 10 3 layers:TPMI=011 4 layers: TPMI=0 11 4 layers: TPMI=0 11 4 layers:TPMI=012 1 layer: TPMI=4 12 1 layer: TPMI=4 12-15 reserved… … … …19 1 layer: TPMI=11 19 1 layer: TPMI=1120 2 layers: TPMI=6 20 2 layers: TPMI=6… … … …27 2 layers: TPMI=13 27 2 layers: TPMI=1328 3 layers: TPMI=1 28 3 layers: TPMI=129 3 layers: TPMI=2 29 3 layers: TPMI=230 4 layers: TPMI=1 30 4 layers: TPMI=131 4 layers: TPMI=2 31 4 layers: TPMI=232 1 layers: TPMI=12… …47 1 layers: TPMI=2748 2 layers: TPMI=14… …55 2 layers: TPMI=2156 3 layers: TPMI=3… …59 3 layers: TPMI=660 4 layers: TPMI=361 4 layers: TPMI=462-63 reservedTable 7.3.1.1.2-8:Value Number of DMRS CDM group(s) without data DMRS port(s)0 1 01 1 12 2 03 2 14 2 25 2 36-7 Reserved ReservedTable 7.3.1.1.2-9:Value Number of DMRS CDM group(s) without data DMRS port(s)0 1 0,11 2 0,12 2 2,33 2 0,24-7 Reserved ReservedTable 7.3.1.1.2-10:Value Number of DMRS CDM group(s) without data DMRS port(s)0 2 0-21-7 Reserved ReservedTable 7.3.1.1.2-11:Value Number of DMRS CDM group(s) without data DMRS port(s)0 2 0-31-7 Reserved ReservedTable 7.3.1.1.2-25:Value DMRS port0 1st scheduled DMRS port1 2nd scheduled DMRS port2 3rd scheduled DMRS port3 4th scheduled DMRS portTable 7.3.1.1.2-26: Value ofDMRS port Value ofDMRS port MSB LSB0 1st DMRS port which shares 0 1st DMRS port which sharesPTRS port 0 PTRS port 11 2nd DMRS port which shares 1 2nd DMRS port which sharesPTRS port 0 PTRS port 1 For example, the scheduling DCI indicates rank = 4 with TPMI = 1 and DMRS ports {0,1,2,3}. Asper TS 38.21118.1.0, DMRS ports {0,1} share PTRS port 0 and DMRS ports {2,3} share PTRSport 1. Hence, since DMRS ports are indicated in both of these port groups, the actual number of PTRS ports is 2, hence the DMRS association is based on Table 7.3.1.1.2-26. For example, if the scheduling DCI indicates bit value ‘01’, then the two PTRS ports are associated with DMRS ports 0 and 3, respectively.Similarly, as for the DL, the specific sub-carrier within a PRB occupied by a PTRS antenna portvaries dynamically depending on the specific DMRS antenna port(s) indicated by the scheduling DCI, e.g., DCI 0_1. For the UL, this port association is based on 3 fields in the scheduling DCI: ‘Precoding information and number of layers’ field, ‘Antenna port(s)’ field, and ‘PTRS-DMRS association’ field. For an OFDM symbol carrying PTRS in PUSCH with DFT-S-OFDM waveform, five different sample densities for the PTRS are defined in NR. The corresponding placement patterns for thesefive sample densities are provided in NR TS 38.21118.1.0, which is reproduced in Table 4.Number of Number ofIndex ^ of PTRS samples in OFDM symbol l prior toPTRS groups samples per transform precoding ^gP rT ou-R pS PTRS group ^ group samp2 2 ^^^PUSCHsc ⁄ 4 ^ + ^ − 1 where ^ = 1,3 and ^ = 0,12 4^^PUSCHsc + ^ where ^^ = 0 and ^ = 0,1,2,3^ = 1 and ^ = −4, −3, −2, −14 2 ^^ ^PUSCHsc ⁄ 8 ^ + ^ − 1 where ^ = 1,3,5,7 and ^ = 0,14 4 ^^PUSCHsc ⁄ 4 + ^ + ^ where^ = 0 and ^ = 0,1,2,3 ^ = 0^^ = 1,2 and ^ = −2, −1,0,1 ^ = ^^PUSCHsc ⁄ 8 ^^ = 4 and ^ = −4, −3, −2, −1 ^ = 08 4 ^^ ^PUSCHsc ⁄ 8 ^ + ^ + ^ where^ = 0 and ^ = 0,1,2,3 ^ = 0^^ = 1,2,3,4,5,6 and ^ = −2, −1,0,1 ^ = ^^PUSCHsc ⁄ 16 ^^ = 8 and ^ = −4, −3, −2, −1 ^ = 0Frequency domain RE muting has been discussed to enable inter-node interference measure during SBFD operations. However, there are several drawbacks. The frequency domain RE muting solutions are applicable to the OFDM waveform. However, NR has adopted the low cubic metric DFT-S-OFDM waveform to ensure good uplink coverage. Performing RE muting on the DFT-S- OFDM waveform will cause the cubic metric to rise, which limits the transmission power. As a result, Frequency domain RE muting will cause reduction of uplink coverage. This is particularly undesirable since the uplink transmissions are already under heavy interference from DLtransmissions during SBFD operations. Furthermore, these ad-hoc RE muting proposals provideno clear systematic muting patterns for the case in which both frequency domain muting locationsand time domain muting locations are available. Since the interference levels from DL transmissions may change from one OFDM symbol to the next, frequency domain RE muting in a single OFDM symbol within a slot may not enable measurement of the correct interference. Furthermore, new ad hoc designed muting patterns can interfere with existing physical layer channels and signals. New muting patterns can also increase implementation complexity and costs. It is an object of some embodiments to solve one or more of the problems mentioned above.Figure 5 illustrates an example of a wireless communication network 1 in accordance with someembodiments.In the wireless communication network 1, one or more UEs such as a user equipment (UE) 10exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and / or a wireless terminal, are comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN).It should be understood by the skilled in the art that “UE” is a non-limiting term which means anyterminal, wireless communications terminal, user equipment, narrowband internet of things (NB-IoT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node. The wireless communication network 1 comprises a first radio network node 12, providing radiocoverage over a geographical area, a first service area 11, or first cell of a first radio accesstechnology (RAT), such as NR, LTE, or similar. The first radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, aNext Generation (NG)-Radio Access Network (RAN) node, e.g. a radio base station such as aNodeB, an evolved Node B (eNodeB, eNB), a gNodeB (gNB), a base transceiver station, a radioremote unit, an Access Point Base Station, a NG-RAN-Centralized Unit (CU)-User plane (UP) node, base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminologyused. The first radio network node may be referred to as a primary node, primary radio networknode wherein the service area may be referred to as a primary serving cell, and the primary nodecommunicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.The wireless communication network 1 comprises one or more RANs and one or more CNs. Thewireless communication network 1 may use one or more different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).The wireless communication network 1 comprises a first radio network node 12 providing radiocoverage over a geographical area, a first service area 11, or first cell of a first radio access technology (RAT), such as NR, LTE, or similar. Further, the wireless communication network 1comprises a second radio network node 13, providing radio coverage over a geographical area, asecond service area 14, or second cell of a second radio access technology (RAT), such as NR,LTE, or similar. The second radio network node 13 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as aNodeB, an evolved Node B (eNB, eNodeB), gNodeB (gNB), a base transceiver station, a radioremote unit, a NG-RAN-CU-CP node, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the second radio network node depending e.g. on the first radio access technology and terminology used. Thesecond radio network node may be referred to as a secondary or secondary serving radio networknode, wherein the service area may be referred to as a secondary cell or secondary serving cell,and the second radio network node communicates with the UE in form of DL transmissions to the UE and UL transmissions from the UE. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. The first RAT may be thesame RAT as the second RAT, or the first RAT may be a different RAT than the second RAT. Thewireless communication network 1 may further comprise a number of network nodes providing network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first network node 15, for example, an AMF. The different NF instances may have different tasks.Other functions may be for LTE such as MME or similar. The network node may be a standaloneserver, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks. In some embodiments a more general term “network node” or “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node. In some embodiments the non-limiting term wireless device or user equipment (UE) is used, and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), IoT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.According to embodiments herein a radio node 110 (shown in figure 9) such as the UE 10 or theradio network node 12, is configured to mute one or more PTRS ports for performing measurements by a configuring node such as the radio network node 12 or a scheduling node such as the first network node 15. Embodiments herein enable effective inter-node interference measurement using systematic muting patterns that are similar to existing reference symbol locations. This avoids potential conflicts of muting and existing signals, and also minimizes the implementation complexity and costs.Figure 6 illustrates an example throughput performance without muting resource measurement andwith different muting resource measurements (measurement from one OFDM symbol or frommultiple OFDM symbols). In the figure, the PUSCH throughput over an SBFD slot with or withoutdifferent muting resource measurement approaches, is represented. The evaluation assumes an interfering PDSCH is also transmitted in the same slot but with duration only in OFDM symbol #6 to #11. Without interference measurement from muting resources (shown by the line with circles), higher PUSCH throughput is only possible for UE closer to the gNB. The performance can be improved by increasing the DMRS overhead (shown by the line with crosses) to aid better channel andinterference estimation. If the muting resources are only available in one OFDM symbol, the timevariation of the interference cannot be correctly captured. As a results, the PUSCH throughput isstill degraded (shown by the line with squares) even when an entire OFDM symbol is muted. Usinga zero power PTRS (ZP-PTRS), interference can be measured in every OFDM symbol with lowoverhead, one subcarrier per RB. This allows the receiver to derive the correct interference pattern to suppress and achieve much better throughput performance, shown by the line with triangles, at lower SNRs. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME etc),O&M, OSS, SON, positioning node (e.g. E-SMLC), etc.The non-limiting term UE refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, PDA, tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles etc. The term radio access technology, or RAT, may refer to any RAT e.g. UTRA, E-UTRA, narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, New Radio (NR), 4G, 5G, etc. Any of the equipment denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.Figure 7 illustrates a method 1200 for handling communication in a wireless communicationnetwork performed by a radio node 110 according to some embodiments.A method performed by the radio node 110, such as the UE 10 and / or the radio network node 12,for handling communications, such as measurements, in the wireless communication networkaccording to embodiments herein will now be described. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.The radio node 110 configures 1201 the UE or is configured with one or more zero-power PTRSports. The radio node 110 may further be configured with one or more PTRS ports, with power, and one or more zero-power PTRS ports separately. For example, the radio node 110 receives1203 a configuration from the configuring node 120 (shown in figure 11) such as the radio networknode 12. Thus, the radio node 110 is configured to mute one or more PTRS ports for performing measurements by a configuring node such as the radio network node 12 or a scheduling node such as the network node 15.The radio node 110 may then perform 1202 measurement using the one or more PTRS ports, withpower, and the one or more zero-power PTRS ports.Figure 8 illustrates a method 1300 for handling communication in a wireless communicationnetwork performed by the configuring node 120 according to some embodiments.A method performed by the configuring node 120 for handling communication, such asmeasurements, in the wireless communication network according to embodiments herein will now be described. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.The configuring node 120 configures 1301 the radio node with one or more zero-power PTRSports. The configuring node 120 may further configure the radio node with one or more PTRS portswith power, and one or more zero-power PTRS ports separately. For example, the configuringnode 120 transmits 1303 a configuration to the radio node 110 such as the radio network node 12.The configuring node 120 may further transmit and / or exchange 1302 PTRS configurationsbetween radio nodes such as radio network nodes. To enable a radio network node to perform inter-node interference measurement, the configuration information of the ZP PTRS according to any of the above embodiments may be exchanged between the radio network nodes.According to an embodiment, the UE 10, being an example of the radio node 110, may beconfigured with PTRS ports with power, and zero-power PTRS ports separately. A PTRS port withpower may also be referred to as non-zero power PTRS (NZP-PTRS) port. As an example, the UE10 may be configured with up to two PTRS ports with power, and at least one zero-power PTRSport.In another embodiment, the time density of the zero-power PTRS port can be determined usingexisting higher layer configuration and a scheduled MCS. The frequency density of the zero-power PTRS port can be determined using existing higher layer configuration and the allocated number of RBs. In another embodiment, the time density, ^ZP-PTRS, of the zero-power PTRS port can be directly specified via higher layer configuration. In a further embodiment, the frequency density, ^ZP-PTRS, of the zero-power PTRS port can be directly specified via higher layer configuration. Additional frequency density such as one or more PTRS subcarrier for every allocated RB can be introduced.A nonlimiting example of higher layer configuration for downlink ZP-PTRS is shown below:-- ASN1STARTZPPTRS-DownlinkConfig ::=SEQUENCE {frequencyDensity ENUMERATED {oneSixth, oneFourth, oneThird, oneHalf, d1, d2, d4}OPTIONAL, -- Need StimeDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need SresourceElementOffset ENUMERATED {offset01, offset10, offset11 } OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2} OPTIONAL -- Need R..., }-- ASN1STOPThe frequencyDensity configuration is used by the UE 10 to determine the frequency density,^ZP-PTRS, via the following nonlimiting example of mapping table:frequencyDensity Frequency density (^ZP-PTRS)d1 1d2 2d4 4oneHalf 1 / 2oneThird 1 / 3oneFourth 1 / 4oneSixth 1 / 6When the frequency density ^ZP-PTRS is less than one, there will be 12 ⋅ ^ZP-PTRS PTRS subcarriersin a resource block (RB). In one embodiment, the first PTRS subcarrier location within the RB is determined by the associated DMRS port and the resourceElementOffset configuration, if provided, as per current NR specifications. The additional PTRS subcarriers within the RB is offset from said first PTRS subcarrier by 1 / ^ZP-PTRSsubcarriers. As a nonlimiting example, let the RE location of the first PTRS subcarrier be ^^^^^,^, then the RE location of the other PTRS subcarriers are determined as: ^^^^^,^ = ^^^^^,^ + ^ ⋅ 12 ⋅ ^ZP-PTRS mod 12where ^ = 1,2, … , 1⁄ ^ZP-PTRS − 1, and mod is a modulo operation.The timeDensity configuration is used by the UE 10 to determine the time density, ^ZP-PTRS, via thefollowing nonlimiting example of mapping table:timeDensity Frequency density (^ZP-PTRS)d1 1d2 2d4 4In one further embodiment, the sample density of the zero-power PTRS for PUSCH with DFT-S- OFDM waveform can be directly specified via higher layer configuration.A nonlimiting example of higher layer configuration for uplink ZP-PTRS is shown below:-- ASN1STARTZP-PTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need StimeDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2},resourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need S} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity ENUMERATED {sd1, sd2, sd3, sd4, sd5} OPTIONAL, -- Need StimeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S} OPTIONAL, -- Need R…, }-- ASN1STOPThe sampleDensity configuration is used by the UE 10 to determine the Number of zero-power PTRS groups, ^ZP-PTRS, and the Nu group groupmber of samples per group, ^sample, via the followingnonlimiting example of mapping table:ConfiguredNumber of PTRS groupsNumber of samples per group sampleDensity ^gZ rP o- uP pTRS ^ group samplesd1 2 2sd2 2 4sd3 4 2sd4 4 4sd5 8 4Below is provided a non-limiting example of a semi-static DMRS-PTRS association configurationfor zero power PTRS for the case of transform precoding disabled, i.e., for PUSCH with CP-OFDM.The same can be applied to the ZP-PTRS for PDSCH by one skilled in the art.Depending on if it is desired to configure one or two ZP-PTRS ports, two new parameters are defined: -dmrs-ptrs-association- dmrs-ptrs-association2This is illustrated in the sample ASN.1 code as shown here.-- ASN1STARTZP-PTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need StimeDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need Sdmrs-ptrs-association INTEGER (0..maxNrofDMRSPorts),dmrs-ptrs-association2 INTEGER (0..maxNrofDMRSPorts),OPTIONAL, -- Need RresourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need S} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity SEQUENCE (SIZE (5)) OF INTEGER (1..276),timeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S} OPTIONAL, -- Need R}-- ASN1STOPIf one ZP-PTRS port is desired, only the first parameter is configured. If two ZP-PTRS ports are desired, the second parameter is configured in addition to the first one. Each parameter provides an integer value that refers semi-statically to a DMRS port. In this way, both the number of PTRS ports and the frequency location within a PRB can be semi-statically configured, in contrast to the current standard where the number and location is dynamic. The parameter resourceElementOffset indicates one or a pair of a sub-carrier offsets from thesubcarrier location of the associated DMRS ports that are indicated by dmrs-ptrs-association anddmrs-ptrs-association2 in the same way as non-zero power PTRS; however, the offset is configured with different values than the non-zero power PTRS port(s) so that ZP-PTRS and NZP- PTRS do not collide. In a variation of the above embodiment, the semi-static configuration of ZP-PTRS also includes a slot periodicity and slot offset that define a periodic time domain pattern. For example, if the periodicity is P slots and the slot offset is O slots with respect to a reference slot, then every slotwith slot index s which satisfies mod(s - O, P) = 0 contains ZP-PTRS, where mod(x, y) is a modulofunction returning the remainder of x divided by y. In this way, the time density of ZP-PTRS across slots can be controlled. In an alternative embodiment to the above, two different parameters are defined instead of dmrs- ptrs-association and dmrs-ptrs-association2. Each of these two parameters provides a row indexinto a table for selecting (1) the ^ DMRS ports for a hypothetical rank ^ PUSCH transmission, and(2) a subset of 1 or 2 of these 4 ports that are associated with the 1 or 2 PTRS ports. In this way, these two row indicices function in the same way as the ‘Antenna port(s)’ field and ‘PTRS-DMRS association’ field in DCI 1_1 for indicating the PTRS-DMRS association. In this way, rather than indicating the DMRS-PTRS association dynamically, the association is indicated semi-statically by providing the row indices in RRC. In one embodiment, the zero-power PTRS configuration according to any of the above embodiments is part of at least DMRS-DownlinkConfig or DMRS-UplinkConfig. In another embodiment, the zero-power PTRS configuration according to any of the above embodiments is part of at least PDSCH-Config or PUSCH-Config.One implementation issue with ZP PTRS for DFT-s-OFDM, i.e. for UL transmission, is that in caseof time-dispersive radio propagation channel, power from the non-PTRS Tx sample may leak into the ZP PTRS samples. When estimating the interference covariance, the receiver will need to correct / suppress such leakage to avoid biased interference measurement. If the node performing the interference estimation is also the intended receiver of the PUSCH, then the receiver may demodulate and / or decode the data symbols. The receiver may then correctly cancel or suppress the time-dispersion into the ZP-PTRS. However, if the node performing the interference estimation is not the intended receiver of the PUSCH, additional embodiments are disclosed below. As disclosed in other embodiments, the impact of this leakage can be mitigated by allocating longer consecutive ZP-PTRS samples such that a low-complexity receiver can simply ignore the early ZP PTRS in such a set when estimating the interference. One embodiment is to configure both legacy PTRS and ZP-PTRS for the PUSCH with DFT-S- OFDM waveform and place the ZP-PTRS samples right next to the PTRS samples. For most cases where the legacy PTRS samples are not at the end of the samples, the ZP PTRS samples are placed right after the legacy PTRS samples. This will allow the receiver with knowledge of the configuration to correct / suppress time-dispersive leakage from the legacy PTRS into the ZP-PTRS. More specifically, before estimating the interference, the leakage could be effectively estimatedand cancelled based on knowledge of the transmitted legacy PTRS samples in combination with achannel estimate, typically obtained based on DMRS and legacy PTRS. For some cases where the legacy PTRS samples are at the end of the samples, the ZP PTRS samples are placed right before the legacy PTRS samples. A nonlimiting embodiment of the ZP-PTRS sample placement following the legacy PTRS samplesis shown in Table 5. The general teaching of this embodiment is to add an offset Δ to the sample indices in Table 4. Taking the ^^^^^^^^^^^ = 2, ^^^^^^ ^^^^ = 2 row from Table 4 as an example, the sampleindices for ZP PTRS are given by: 1,3 and ^ = 0,1The offset is given by: Δ= ^group samplefor a group of ZP PTRS samples not located at the end of the samples, and: for a group of ZP PTRS samples located at the end of the samples. Table 5 illustrates proposed ZP-PTRS placement indices for an OFDM symbol carrying ZP-PTRS in PUSCH with DFT-S-OFDM waveform corresponding to the five sample densities in NR. Table 5 Number NumberIndex ^ of ZP-PTRS samples in OFDM symbol l prior to transformof of precoding PTRS samples groups per ^^^ ^^ ^^ ^^ ^^^^ PTRS group ^ group sample2 2 ^^^PUSCHgroup sc ⁄ 4 ^ + ^ − 1 + ^sample where ^ = 1,3 and ^ = 0,12 4 ^^PUSCHsc + ^ + ^ where^ = 0 and ^ = 0,1,2,3 ^ = ^group ^sample^ = 1 and ^ = −4, −3, −2, −1 ^ = −^group sample4 2 ^^ ^PUSCHsc ⁄ 8 ^ + ^ − 1 + ^group sample where ^ = 1,3,5,7 and ^ = 0,14 4 ^^PUSCHsc ⁄ 4 + ^ + ^ where^ = 0 and ^ = 0,1,2,3 ^ = ^group ìsample^ = 1,2 and ^ = −2, −1,0,1 ^ = ^^PUSCHsc ⁄ 8 ^ + ^group ísamplegr î^ = 4 and ^ = −4, −3, −2, −1 ^ = −^oup sample8 4 ^^ ^PUSCHsc ⁄ 8 ^ + ^ + ^ where ì^ = 0 and ^ = 0,1,2,3 ^ = ^group sample^ = 1,2,3,4,5,6 and ^ = −2, −1,0,1 ^ = ^^PUSCHsc ⁄ 16 ^ + ^group ísample^ = 8 and ^ = −4, −3, −2, −1group î^ = −^sampleSince ZP-PTRS need to be coordinated between different radio network nodes, and such coordination is rather slow, taking several milliseconds or even tens of milliseconds, while legacy PTRS could potentially be allocated on the time scale of PUSCH scheduling, e.g. depending on the SNR of the scheduled UE, one could expect legacy PTRS to have a more dynamic allocation than ZP-PTRS. In a further embodiment, the ZP-PTRS use the sample placement of the legacy PTRS sample placement and the legacy PTRS are instead move forward to precede the ZP-PTRS. The following embodiments will focus primarily on this case. It should, however, be clear, that adapting ZP-PTRS allocation to legacy allocation could be done according to the same principles, and might be useful in order to have legacy PTRS placement agree as much as possible with legacy specifications. A unified placement of the moved legacy PTRS and the new ZP-PTRS can be computed by adding an offset ∆ to the indices in Table 4 from the existing NRspecifications. Taking the ^^^^^^^^^^^ = 2, ^^^^^^ ^^^^ = 2 row from Table 4 as an example, the sampleindices for the legacy PTRS and / or ZP-PTRS are given by: 1,3 and ^ = 0,1In one nonlimiting embodiment, the offset is given by: for legacy PTRS. for ZP PTRSfor a group of legacy or ZP-PTRS samples not located at the beginning of the samples, and: for a group of legacy or ZP-PTRS samples located at the beginning of the samples, where ^ is aparameter that is one if the shift is to be applied and zero otherwise. ^ can be configurable or fixedin the specifications. This shift, if applied, causes the legacy PTRS to fall immediately before ZP- PTRS assuming both legacy PTRS and ZP-PTRS have the same values of ^^^^^^^^^^^and ^ ^^^^^ ^^^^. In one nonlimiting embodiment, the parameter ∆ ^^^^^^^^^^^ , ^ ^ is instead determined based onhigher-level parameter sampleOffset: ∆^^^^^^^ ^^^^^^^^^^ , ^ −sampleOffset for legacy PTRS and sampleOffset defined^^^^ ^ = ^0 otherwise. A nonlimiting higher-layer configuration for uplink ZP-PTRS is as follows:-- ASN1STARTPTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need StimeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2},resourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need Sptrs-Power ENUMERATED {p00, p01, p10, p11}} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity SEQUENCE (SIZE (5)) OF INTEGER (1..276),timeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S} OPTIONAL, -- Need R..., [[maxNrofPorts-SDM-r18 ENUMERATED {n1, n2} OPTIONAL -- Need R]] [[sampleOffset ENUMERATED {so1, so2} OPTIONAL -- Cond transformPrecoder]] }-- ASN1STOPThe field sampleOffset is optionally present if transformPrecoderEnabled, need S. In a variant, thefield sampleOffset is only present for legacy PTRS configuration, and otherwise set to 0. If the fieldsampleOffset is absent, the value so0 = 0 is applied. The enumeration values may, e.g., be definedas so1 = 2 and so2 = 4 if these are the possible values but the sampleOffset could in other variant embodiments encompass a larger set of values, e.g., for finer-granular control. If ZP-PTRS are supposed to be shifted, instead of legacy PTRS, a simpler formulation using a ZP-PTRS-specific IE could be used, as in some earlier embodiments:-- ASN1STARTZPPTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need StimeDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2},resourceElementOffset ENUMERATED {offset01, offset10, offset11}OPTIONAL, -- Need S} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity ENUMERATED {sd1, sd2, sd3, sd4, sd5} OPTIONAL, -- Need StimeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need SsampleOffset ENUMERATED {so1, so2} OPTIONAL -- Need S} OPTIONAL, -- Need R…, }-- ASN1STOPThe above embodiments should cover cases where the same ^^^^^^^^^^^is configured for both legacy PTRS and ZP-PTRS but might not achieve the desirable placement if different ^^^^^^^^^^^are configured. Therefore, in some nonlimiting embodiment, the samples to be allocated for legacy PTRS are determined not by the row in Table 4 corresponding to its ^^^^^^^^^^^, but rather by new rows. For example, if ZP-PTRS is configured using ^^^^^^^^^^^^^and ^ ^^^^^ ^^^^ , and legacy PTRS is configuredusing ^^^^^^^^^^^ < ^^^^^^^^^^^^^and ^ ^^^^^ ^^^^, then the legacy PTRS may instead be allocated based on the row corresponding to group setting of ^^^^^^^^^^^^^and ^ ^^^^^ ^^^^ , but with ^ assuming only every m-th value listed in the table, where ^ = ^^^^^^^^^^^ / ^^^^^^^^^^^^^. In some nonlimiting embodiments, it is further possible to use a higher-layer parameter to allocateZP-PTRS based on every n-th listed value of ^ in the row ^^^^^^^^^^^^^and . In combination with the afore-mentioned allocation of legacy PTRS based on every m-th listed value of ^, this gives the flexibility to allocated legacy PTRS immediately before ZP-PTRS for any combination of values for ^^^^^^^^^^^for legacy and ^^^^^^^^^^^for ZP-PTRS. In some embodiments, if the resulting allocation for legacy PTRS ends up at negative sample indices ^, wrap-around to all-positive indices ^^^^^^is achieved through a modulo operation: ^^^^^^ = ^ mod ^^^^^^^^. It is to be understood, that the same effect has here described in terms of the offset ∆^^^^^^^^^^^^ , ^^^^^^ ^^^^ ^ can alternatively be achieved in other ways.The first or last, legacy or ZP-PTRS group of an OFDM symbol, i.e. the group with the smallest orlargest s may, after shifting in accordance with some of the above embodiments, come to overlapwith the samples of an unshifted, legacy or ZP, PTRS group or another shifted, legacy or ZP,PTRS group. In such cases, one may in some embodiments modify the shift of the first and / or the last group, e.g. change the direction of the shift and / or increase the shift so that the overlap is avoided. In some nonlimiting embodiments, the minimum shift that results in the ZP-PTRS group being located immediately after a legacy PTRS group or another ZP-PTRS group is used. In some other embodiments, instead the minimum shift that just avoids overlap with another PTRS group is used. In yet some embodiments, an overlapping PTRS group is omitted entirely to avoid overlap. In some embodiments, the shifts in any of the preceding embodiments are applied only if both legacy PTRS and ZP-PTRS are configured. In some embodiments, the shifts are applied even ifonly one of the types, legacy or ZP, is configured. The latter variant has the advantage that thePTRS shift can be more stable over time, which can facilitate coordination between different radio links. In one embodiment, additional sample densities can be introduced such as using fewer groups but more samples per group for ZP-PTRS for PUSCH with DFT-S-OFDM waveform. A nonlimiting higher layer configuration for uplink ZP-PTRS is shown below:-- ASN1STARTZPPTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabled SEQUENCE {frequencyDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need StimeDensity ENUMERATED {d1, d2, d4} OPTIONAL, -- Need SmaxNrofPorts ENUMERATED {n1, n2},resourceElementOffset ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need S} OPTIONAL, -- Need RtransformPrecoderEnabled SEQUENCE {sampleDensity ENUMERATED {sd1, sd2, sd3, sd4, sd5, sd6, sd6, sd8, sd9, sd10, sd11, sd12,sd13, sd14, sd15} OPTIONAL, -- Need StimeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S} OPTIONAL, -- Need R..., }-- ASN1STOPThe sampleDensity configuration is used by the UE 10 to determine the Number of zero-power PTRS groups, ^ZP-PTRS, and the Number of sample group groups per group, ^sample, via the followingnonlimiting example of mapping table:ConfiguredNumber of PTRS groupsNumber of samples per group sampleDensity ^gZ rP o- uP pTRS ^ group samplesd1 2 4sd2 2 8sd3 2 16sd4 2 32sd5 2 64sd6 4 8sd7 4 16sd8 4 32sd9 1 ^^sPcUSCH / 64^sd10 1 ^^sPcUSCH / 32^sd11 1 ^^sPcUSCH / 16^sd12 1 ^^sPcUSCH / 8^sd13 1 ^sPcUSCH / 4sd14 1 ^sPcUSCH / 2sd15 1 ^sP cUSCH In one nonlimiting embodiment, the indices of the zero-power PTRS samples for sd1, sd2, sd3, sd4 or sd5 are determined as: ^^PUSCHsc + ^where ^sPcUSCHis the number of subcarriers allocated to the PUSCH, and: ^= 0 and ^ = 0,1, … , ^group sa − 1^mple Said nonlimiting embodiment discloses ZP-PTRS sample placements at the beginning and the endof the samples. Hence, through cyclic prefix attachment, an extended muting period can be created. In a further nonlimiting embodiment, the indices of the ZP-PTRS samples for sd6, sd7 or sd8 are determined as: ^^PUSCHsc ⁄ 4 + ^ + ^Where: ^= 0,2 and ^ = 0,1, … , ^group sam − 1 and ^ = 0^ple^ = 1,3 and ^ = −^group sample , −^group sample + 1, … , −1 and ^ = ^^PUSCHsc ⁄ 4 ^Said nonlimiting embodiment discloses ZP-PTRS sample placements for the middle two groups to be consecutive to each other, thus creating an extended muting period. In another nonlimiting embodiment, the indices of the ZP-PTRS samples for sd9, sd10, sd11, sd12, sd13, sd14, sd15 are determined as: ^PUSCHsc + ^Where: Said nonlimiting embodiment discloses ZP-PTRS sample placements in one single large group at the end of the samples. Hence, through cyclic prefix attachment, an extended muting period can be created. Note that more than one PUSCH may be scheduled during the same slot. For instance, if a first UE is scheduled a PUSCH with ^PUSCHsc = 120 subcarriers and ZP-PTRS configuration of ^gZrPou-PpTRS=2 and ^group sample = 8, then the initial and last 1 / 15 durations of the DFT-S-OFDM waveform containsmuted and low values. If a second UE is scheduled a PUSCH in the same slot with ^PUSCHsc = 240subcarriers, it is necessary to configure the second UE with a ZP-PTRS configuration of ^ZP-PTRSgroup = 2 and ^group sample = 16 in order to ensure the same initial and last 1 / 15 durations of the DFT-S-OFDM waveform contains muted and low values. Since ZP-PTRS configurations are via higher layer signaling, it cannot be modified quickly based on scheduling decision to ensure such muted zone alignment amongst multiple UEs. The nonlimiting embodiment for sd9, sd10, sd11, sd12, sd13, sd14, sd15 further discloses ZP- PTRS sample density settings that result in aligned zones of muting and low value samples in a DFT-S-OFDM waveform regardless of the scheduled PUSCH bandwidth. That is, the group size ^ group sampleautomatically scale with the scheduled bandwidth ^sPcUSCH. This automatic scaling of the group size ensures the zones of muted and low value samples of PUSCH of different scheduled bandwidths to be aligned. It should be clear to one skilled in the art that the teaching of automatic scaling of the number of muted samples with the scheduled bandwidth to align the muted zones for transmissions with different bandwidths can be applied to muting patterns other than those based the PTRS patterns. In another nonlimiting embodiment, the indices of the zero-power PTRS samples for sd6, sd7 or sd8 are determined as: ^^PUSCHsc ⁄ 4 + ^ + ^Where: For a PDSCH or PUSCH with the presence of zero-power PTRS port(s), the UE 10 may follow NRrate matching procedures to prepare the required number of modulated symbols for said PDSCH or PUSCH, and NR mapping procedures to place said required number of modulated symbols to the scheduled radio resource. Said NR procedures ensure the radio resources for the zero-power PTRS port(s) are not occupied by said required number of modulated symbols. The radio sources for the zero-power PTRS port(s) shall carry zero values. In one embodiment, when a zero-power PTRS port is configured for a PUSCH, the UE 10 may transmit a PUSCH with the configured zero-power PTRS port for PUSCH transmitted during SBFDsymbols. When a zero-power PTRS port is configured for a PDSCH, the UE 10 may receive aPDSCH with the configured zero-power PTRS port for PDSCH transmitted during SBFD symbols. In yet another embodiment, when a zero-power PTRS port is configured for a PDSCH or aPUSCH, the UE 10 transmits a PUSCH or receive a PDSCH with the configured zero-power PTRSport based on which search space the scheduling downlink control information (DCI) is received in.As one nonlimiting embodiment, the UE 10 transmits a PUSCH or receive a PDSCH with the configured zero-power PTRS port if the scheduling DCI is received in a UE-specific search space.The UE 10 may not transmit a PUSCH or receive a PDSCH with the configured zero-power PTRSport if the scheduling DCI is received in a common search space. In another embodiment, when a zero-power PTRS port is configured for a PUSCH, the UE 10 may transmit a PUSCH with the configured zero-power PTRS port for PUSCH transmitted during SBFD symbols based on an indicator included in the scheduling DCI. When a zero-power PTRS port isconfigured for a PDSCH, the UE 10 may receive a PDSCH with the configured zero-power PTRSport for PDSCH transmitted during SBFD symbols based on an indicator included in the scheduling DCI. As a nonlimiting example, said indicator can be of value one to indicate to the UE 10 to include ZP PTRS in the scheduled PUSCH. Said indicator can be of value zero to indicate to the UE to transmit the scheduled PUSCH without ZP PTRS. The network signalling for inter-node interference measurements may be between first radio network node 12 and second radio network node 13. In one embodiment, to enable a radio network node to perform inter-node interference measurement, the configuration information of the ZP PTRS according to any of the above embodiments is exchanged between the radio network nodes. Said configuration information of the ZP-PTRS include one or more of: the frequency density, timedensity, sample density, DMRS-PTRS port association, and / or sample offset configurations.Said configuration information of the ZP-PTRS include the waveform choice for PUSCH transmissions during SBFD symbols. Said waveform choice include at least the CP-OFDM and DFT-S-OFDM waveforms. Said information of the waveform choice for PUSCH transmissions during SBFD symbols is a bitmap of the slots containing SBFD symbols. Each bit of said bitmap indicates the waveform to be scheduled during the corresponding the slots containing SBFD symbols. As a nonlimiting example, said bit can be of value one to indicate the CP-OFDM waveform and of value zero to indicate the DFT-S-OFDM waveform. Said information of the waveform choice for PUSCH transmissions during SBFD symbols is a bitmap of the SBFD symbols. Each bit of said bitmap indicates the waveform to be scheduled during the corresponding SBFD symbols. In a further embodiment, the configuration information of the legacy PTRS is exchanged between the radio network nodes to enable a radio network node to perform improved inter-node interference measurement.Figure 9 is a block diagram depicting the radio node 110 such as the UE or the radio network nodefor handling communication in the wireless communication network according to embodiments herein. The radio node 110 may comprise processing circuitry 1501, e.g., one or more processors, configured to perform the methods herein.The radio node 110 and / or the processing circuitry 1501 is configured with one or more zero-powerPTRS ports. The radio node 110 and / or the processing circuitry 1501 may be configured to useone or more PTRS ports with power, and one or more zero-power PTRS ports separately. Forexample, the radio node 110 and / or the processing circuitry 1501 may be configured to receive aconfiguration from the configuring node such as the radio network node. Thus, the radio node 110and / or the processing circuitry 1501 may be configured to mute one or more PTRS ports forperforming measurements by a configuring node such as the radio network node or a scheduling node such as the network node.The radio node 110 and / or the processing circuitry 1501 may be configured to performmeasurement using the one or more PTRS ports with power, and the one or more zero-powerPTRS ports. The radio node 110 may comprise a memory 1505. The memory 1505 comprises one or moreunits to be used to store data on, such as data packets, indications, PTRS configurations,reference signal information, assistance information, application information, messages,measurement, events, and applications to perform the methods disclosed herein when beingexecuted, and similar. Furthermore, the radio node 110 may comprise a communication interface 1506 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.Embodiments herein may disclose the radio node 110 for handling communication in a wirelesscommunication network, wherein radio node 110 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio node 110 is operative to perform any of the methods herein.Figure 10 illustrates a computer program product 1507 and a computer-readable storage medium1508. The methods according to the embodiments described herein for the radio node are respectively implemented by means of e.g. a computer program product 1507 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio node. The computer program product 1507 may be stored on a computer- readable storage medium 1508, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1508, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio node. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.Figure 11 is a block diagram depicting the configuring node 120 for handling communication in thewireless communication network 1 according to embodiments herein. The configuring node 120 may comprise processing circuitry 1601, e.g., one or more processors, configured to perform the methods herein. The configuring node 120 and / or the processing circuitry is configured to configure the radio node with one or more zero-power PTRS ports. The configuring node 120 and / or the processing circuitrymay be configured to configure the radio node with one or more PTRS ports with power, and oneor more zero-power PTRS ports separately. The configuring node 120 and / or the processing circuitry may be configured to transmit and / or exchange PTRS configurations between radio nodes such as radio network nodes. To enable a radio network node to perform inter-node interference measurement, the configuration information of the ZP PTRS according to any of the above embodiments may be exchanged between the radio network. The configuring node 120 may comprise a memory 1605. The memory 1605 comprises one or more units to be used to store data on, such as data packets, indications, PTRS configurations, reference signal information, assistance information, application information, messages,measurement, events, and applications to perform the methods disclosed herein when beingexecuted, and similar. Furthermore, the configuring node 120 may comprise a communication interface 1606 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas. Embodiments herein may disclose the configuring node 120 for handling communication in a wireless communication network, wherein configuring node 120 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said configuring node 120 is operative to perform any of the methods herein.Figure 12 illustrates a computer program product 1607 and a computer-readable storage medium1608. The methods according to the embodiments described herein for the configuring node are respectively implemented by means of e.g. a computer program product 1607 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the configuring node. The computer program product 1607 may be stored on a computer-readable storage medium 1608, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1608, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the configuring node. In some embodiments, the computer-readable storage medium may be a transitory or a non- transitory computer-readable storage medium. Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receivesand / or transmit signals, e.g. data. Examples of RAT are NR, Wi-Fi, LTE, LTE-Advanced, WidebandCode Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB).As will be readily understood by those familiar with communications design, functions means orcircuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.Alternatively, several of the functional elements of the processing means discussed may beprovided through the use of dedicated hardware, while others are provided with hardware forexecuting software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices. Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.Figure 13 shows an example of a communication system 100 in accordance with someembodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110) being examples of the first radio network node 12 and second radio network node 13, or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node, being examples of the entities herein, 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 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 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 102, including one or more network nodes 110 and / or core network nodes 108. 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 ServiceManagement and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance orcomparable technologies. The network nodes 110 facilitate direct or indirect connection of the user equipment (UE) 10, such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections. 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 100 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 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 112 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 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 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 102. In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. 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 106 includes one more core network nodes (e.g., core network node 108) such as network node 15 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 108. 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 a User Plane Function (UPF). The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 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.As a whole, the communication system 100 of Figure 13 enables connectivity between the UEs,network nodes, and hosts. In that sense, the communication system 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 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 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. In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 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 IoT services to yet further UEs. In some examples, the UEs 112 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 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured foroperating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with anyone or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) NewRadio – Dual Connectivity (EN-DC).In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 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 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 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 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114may be a dedicated hub – that is, a hub whose primary function is to route communications to / fromthe UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications betweenthe UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.Figure 14 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers toa 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 IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. 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). The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 14. 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. The processing circuitry 202 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 210. The processing circuitry 202 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 202 may include multiple central processing units (CPUs). In the example, the input / output interface 206 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 200. 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. In some embodiments, the power source 208 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 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied. The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems. The memory 210 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 random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or 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 ‘SIM card.’ The memory 210 may allow the UE 200 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 210, which may be or comprise a device-readable storage medium. The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 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 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222)and may share circuit components, software, or firmware, or alternatively be implementedseparately. In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, 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 in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, 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). 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. A UE, when in the form of an Internet of Things (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 TV, 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 Virtual Reality (VR), a wearable fortactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-trackingdevice, 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 200 shown in Figure 14. 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 and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. 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.Figure 15 shows a network node 300 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, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). 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 remote radio units 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). 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 base station 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). The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a 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 300 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 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, 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 network node 300. The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 300 components, such as the memory 304, to provide network node 300 functionality. In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 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 RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units. The memory 304 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, random access memory (RAM), read-only memory (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 302. The memory 304 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 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated. The communication interface 306 is used in wired or wireless communication of signalling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 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 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 300 does not include separate radio front- end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and isconnected to the antenna 310. Similarly, in some embodiments, all, or some of the RF transceivercircuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port. The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may bereceived from a UE, another network node, and / or any other network equipment. Similarly, theantenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another networknode, and / or any other network equipment.The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 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. Embodiments of the network node 300 may include additional components beyond those shown inFigure 15 for providing certain aspects of the network node’s functionality, including any of thefunctionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.Figure 16 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure13, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations 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 400 may provide one or more services to one or more UEs. The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. 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 asFigures 18 and 19, such that the descriptions thereof are generally applicable to the correspondingcomponents of host 400. The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 mayutilize only a subset, or all of the components shown. The host application programs 414 may beimplemented 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), MPEG, VP9) and audio codecs (e.g., 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, heads-up display systems). The host application programs 414 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 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 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 (MPEG- DASH), etc.Figure 17 is a block diagram illustrating a virtualization environment 500 in which functionsimplemented 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 500 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 500 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. Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508. The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, 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. In the context of NFV, a VM 508 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 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, 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 508 on top of the hardware 504 and corresponds to the application 502. Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 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 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 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 radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.Figure 18 shows a communication diagram of a host 602 communicating via a network node 604with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE112a of Figure 13 and / or UE 200 of Figure 14), network node (such as network node 110a ofFigure 13 and / or network node 300 of Figure 15), and host (such as host 116 of Figure 13 and / orhost 400 of Figure 16) discussed in the preceding paragraphs will now be described with reference to Figure 18. Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 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 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650. The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 13) 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. The UE 606 includes hardware and software, which is stored in or accessible by UE 606 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 UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. 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 650 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 650. The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection 650, in step 608, the host 602 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 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602. In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 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 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606. One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the lastsegment. More precisely, the teachings of these embodiments may improve measurements andthereby provide benefits such as better communication, better responsiveness, and / or better battery life.In an example scenario, factory status information may be collected and analysed by the host 602.As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect andanalyse real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). Asanother example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 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 602 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,analysing and / or transmitting data.In some examples, a measurement procedure may be provided for the purpose of monitoring datarate, latency, and other factors on which the one or more embodiments improve. There may furtherbe an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling that facilitates measurementsof throughput, propagation times, latency, and the like, by the host 602. The measurements maybe implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc. 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 performthe tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining orsimilar 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. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on 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 functionalities may be provided by the processingcircuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired 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. Modifications and other embodiments of the disclosed embodiments will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiment(s) is / are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.Some examples of embodiments are described below.A1. A method performed by a radio node for handling communication in a wireless communicationnetwork, the method comprising configuring the radio node with one or more zero-power PTRSports.A2. The method according to embodiment A1, wherein the radio node is configured with one ormore PTRS ports (with power) and one or more zero-power PTRS ports separately.A3. The method according to any of the embodiments A1-A2, comprising performing ameasurement using the one or more zero-power PTRS ports. B1. A method performed by a configuring node for handling communication in a wirelesscommunication network, the method comprising configuring a radio node with one or more zero-power PTRS ports.B2. The method according to embodiment B1, further comprising exchanging PTRS configurationwith a radio network node. C1. A UE for handling communication in a wireless communication network, wherein the UE is configured with one or more zero-power PTRS ports. D1. A radio network node for handling communication in a wireless communication network,wherein the radio network node is configured to configure a radio node with one or more zero-power PTRS ports. E1. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of theembodiments A1-A3, and B1-B2, as performed by the radio node and the configuring node,respectively. F1. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the embodiments A1-A3, and B1-B2, asperformed by the radio node and the configuring node, respectively.

Claims

CLAIMS1. A method (1200) performed by a radio node (110) for handling communication in a wirelesscommunication network (1), wherein the radio node is a user equipment (10) or a radio networknode (12), the method comprising:configuring (1201) the radio node with a configuration, the configuration comprising one ormore zero-power, ZP, phase tracking reference symbols, PTRS, ports, orreceiving (1203) the configuration from a configuring node (120).

2. The method (1200) according to claim 1, wherein the configuration comprises one or morenon-zero power, NZP, PTRS ports, and one or more ZP-PTRS ports, separately.

3. The method (1200) according to any one of claims 1 to 2, comprising performing (1202) ameasurement using the one or more ZP-PTRS ports.

4. A method (1300) performed by a configuring node (120) for handling communication in awireless communication network (1), the method comprising:configuring (1301) a radio node (110), wherein the radio node is a user equipment (10) or aradio network node (12), with a configuration, the configuration comprising one or more zero-power, ZP, phase tracking reference symbols, PTRS, ports, ortransmitting (1303) the configuration to the radio node.

5. The method (1300) according to claim 4, wherein the configuration comprises one or morenon-zero power PTRS ports, and one or more zero-power PTRS ports separately.

6. The method (1300) according to any one of claims 4 to 5, comprising exchanging (1302)the configuration with a radio network node (110).

7. A user equipment, UE, (10) for handling communication in a wireless communicationnetwork (1), wherein the UE is configured with one or more zero-power phase tracking referencesymbols, PTRS, ports.

8. A radio network node (12) for handling communication in a wireless communicationnetwork (1), wherein the radio network node is configured to configure a radio node with one ormore zero-power PTRS ports.

9. A computer program product (1507) comprising instructions, which, when executed on atleast one processor, cause the at least one processor to carry out the method according to any of claims 1 to 3.

10. A computer program product (1607) comprising instructions, which, when executed on atleast one processor, cause the at least one processor to carry out the method according to any of claims 4 to 6.

11. A computer-readable storage medium (1508), having stored thereon a computer programproduct (1507) comprising instructions which, when executed on at least one processor, cause theat least one processor to carry out the method according to any of claims 1 to 3.

12. A computer-readable storage medium (1608), having stored thereon a computer programproduct (1607) comprising instructions which, when executed on at least one processor, cause theat least one processor to carry out the method according to any of claims 4 to 6.

Images