Parameter reporting for selected NZP CSI-RS resource sets

Abstract

A UE receives first configuration information from a network node. The configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the UE receives second configuration information from the network node. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. The UE selects all or a subset of the plurality of NZP CSI-RS resource sets for which the UE is to report the one or more reporting quantities and computes the one or more parameters for each selected NZP CSI-RS resource set. Further, the UE reports the computed one or more reporting quantities for the selected NZP CSI-RS resource sets. This reporting the computed one or more parameters for the selected NZP CSI-RS resource sets comprises reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected.

Description

[0001] PARAMETER REPORTING FOR SELECTED NZP CSI-RS RESOURCE SETS TECHNICAL FIELD The present disclosure relates to a wireless (e.g., cellular) communications system and, more particularly, reporting of one or more parameters for selected subsets of Non-Zero Power (NZP) Channel State Information Reference Signal (CSI-RS) resource sets, e.g., in the context of Coherent Joint Transmission (CJT) from multiple Transmission and Reception Points (TRPs) in a wireless communications system. BACKGROUND The next generation mobile wireless communication system (i.e., 5thGeneration (5G)) or New Radio (NR) will support a diverse set of use cases and a diverse set of deployment scenarios. The later includes deployment at both low frequencies (100s of Megahertz (MHz)), similar to Long Term Evolution (LTE), and very high frequencies (millimeter (mm) waves in the tens of Gigahertz (GHz)). Similar to LTE, NR will use Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) (i.e., from a network node, gNodeB (gNB), evolved NodeB (eNB), or base station, to a user equipment or UE). In the uplink (UL) (i.e., from UE to gNB), both OFDM and Discrete Fourier Transform (DFT)-spread OFDM (DFT-S-OFDM), also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) in LTE, will be supported. The basic NR physical resource can thus be seen as a time-frequency grid as illustrated in Figure 1, where a resource block (RB) in a 14-symbol slot is shown. A resource block corresponds to 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth. Each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval. Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values(also referred to as different numerologies) are given by ∆^^^^ = (15 × 2^^^^) ^^^^^^^^^^^^ where ^^^^ is a non-negative integer and can be one of {0,1,2,3,4}. ∆^^^^ = 15^^^^^^^^^^^^ (e.g., ^^^^ = 0 ) is the basic (orreference) subcarrier spacing that is also used in LTE. ^^^^ is also referred to as the numerology. In the time domain, DL and UL transmissions in NR will be organized into equally sized subframes of 1 millisecond (ms) each similar to LTE. A subframe is further divided into multiple slots of equal duration. The slot length is dependent on the subcarrier spacing or numerology and is given by12^^^^ms. Each slot consists of 14 OFDM symbols for normal Cyclic Prefix (CP). It is understood that data scheduling in NR can be in slot basis. An example is shown in Figure 2 with a 14-symbol slot, where the first two symbols contain control channel (i.e., Physical Downlink Control Channel (PDCCH)) and the rest contains data channel (i.e., Physical Downlink Shared Channel (PDSCH)). For convenience, subframe is referred throughout the following sections. DL transmissions can be dynamically scheduled, i.e., in each slot the gNB transmits Downlink Control Information (DCI) about which UE data is to be transmitted to and which resource blocks in the current DL slot the data is transmitted on. This control signaling is typically transmitted in the first one or two OFDM symbols in each slot in NR. The control information is carried on PDCCH and data is carried on PDSCH. A UE first detects and decodes PDCCH and, if a PDCCH is decoded successfully, it then decodes the corresponding PDSCH based on the decoded control information in the PDCCH. UL data transmission can also be dynamically scheduled using PDCCH. Similar to downlink, a UE first decodes uplink grants in PDCCH and then transmits data over the Physical Uplink Shared Channel (PUSCH) based the decoded control information in the uplink grant such as modulation order, coding rate, uplink resource allocation, and etc. Tracking Reference Signal (TRS) Similar to LTE, Channel State Information Reference Signal (CSI-RS) was introduced in NR for channel measurement in the DL. A CSI-RS is transmitted over an antenna port (either a physical or virtual antenna) on certain Resource Elements (REs) for a UE to measure the DL channel associated with the antenna port. CSI-RS for this purpose is also referred to as Non-Zero Power (NZP) CSI-RS. The supported number of antenna ports or CSI-RS ports in NR are {1,2,4,8,12,16,24,32}. A Tracking Reference Signal (TRS) is a special NZP CSI-RS with one port and is used for time and frequency tracking in the DL. Figure 3 shows an example of a TRS resource configuration in a Physical Resource Block (PRB) and 2 slots. A UE can be configured with one or more periodic TRSs, or one or more periodic TRSs and aperiodic TRSs in NR. For a periodic TRS, it has a periodicity and a slot offset. The periodicity can one of 2^^^^^^^^^^^^slots where ^^^^^^^^=10, 20, 40, or 80. A TRS occupies multiple RBs. When a NZP CSI-RS resource set contains “trs- info”, then the NZP CSI-RS resource set is for TRS. Quasi Co-Location Demodulation Reference Signals (DM-RS) are used for coherent demodulation of PDSCH. A PDSCH can be associated with one or multiple DMRS antenna ports or simply DMRS ports, each associated with a spatial layer or a Multi-Input-Multiple-Output (MIMO) layer. Multiple layers can be multiplexed in a same time and frequency resource, where different data are carried in different layers. The DMRS ports used for a PDSCH transmission are indicated in DCI scheduling the PDSCH. Several signals can be transmitted from different antenna ports. These signals can have the same large-scale properties, for instance in terms of Doppler shift / spread, average delay spread, or average delay, when measured at a UE receiver. These antenna ports are then said to be Quasi Co- Located (QCL). If the UE knows that two antenna ports, a first and second antenna ports, are QCL with respect to a certain channel property (e.g., Doppler spread), the UE can obtain the channel property of the first antenna port (e.g., DM-RS) from the second antenna port (e.g., TRS). The reference signal (e.g., TRS) associated with the second antenna port is known as the QCL source RS and the reference signal (e.g., DM-RS) associated with the first antenna port is known as the QCL target Reference Signal (RS). The supported QCL types in NR are: • 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread} • 'QCL-TypeB': {Doppler shift, Doppler spread} • 'QCL-TypeC': {Doppler shift, average delay} • 'QCL-TypeD': {Spatial Rx parameter} QCL relations are specified by Transmission Configuration Indicator (TCI) states. A TCI state contains one or two source RS and the associated QCL types. In case two QCL types are configured, one is QCL type-D. A UE can be configured by Radio Resource Control (RRC) signaling with a list of TCI states. For PDSCH, one or two TCI states from the list can be activated for each of up to 8 TCI codepoints by a Medium Access Control (MAC) Control Element (CE) command. Up to 8 TCI states can be activated. One of the TCI codepoints is indicated in DCI scheduling a PDSCH. UE performs PDSCH reception according to the TCI state(s) indicated in the TCI codepoint. Table 1 is a summary of possible source RS and target RS in NR. Synchronization Signal Block (SSB) refers to synchronization signal and broadcast channel, CSI-RS (BM) refers to CSI-RS for beam management in Frequency Range 2 (FR2). Table 1: Target and source RS supported in NR. Target RS QCL source RS QCL type A QCL type B QCL type C QCL type D CSI-RS (CSI) TRS TRS TRS SSB TRS CSI-RS (BM) TRS DMRS for TRS TRS PDSCH TRS CSI-RS (BM) CSI-RS for CSI-RS for CQI CSI CSI Framework in NR In NR, a UE can be configured with one or multiple Channel State Information (CSI) report configurations for DL CSI feedback by the UE. A CSI report may contain one or more of • Channel Rank Indicator (RI) • Antenna Precoding Matrix Indicator (PMI) • Channel Quality Indicator (CQI) • DL Reference Signal Received Power (RSRP) or Signal to Interference and Noise Ratio (SINR) • CSI Reference Signal (CSI-RS) Resource Indicator (CRI) Each CSI report configuration is associated with a Bandwidth Part (BWP) and contains all necessary information required for a CSI report, including • a CSI resource configuration for channel measurement • reporting type, i.e., aperiodic CSI (on PUSCH), periodic CSI (on Physical Uplink Control Channel (PUCCH)) or semi-persistent CSI (on PUCCH, and DCI activated on PUSCH). • report quantity specifying what to be reported, such as RI, PMI, CQI, RSRP, etc. A UE can be configured with one or multiple CSI resource configurations for channel measurement. Each CSI resource configuration for channel measurement can contain one or more NZP CSI-RS resource sets. For each NZP CSI-RS resource set, it can further contain one or more NZP CSI-RS resources. A NZP CSI-RS resource can be periodic, semi-persistent, or aperiodic. Periodic CSI starts after it has been configured by RRC and is reported on PUCCH, the associated NZP CSI-RS resource(s) are also periodic. For aperiodic CSI, it is reported on PUSCH and is activated by a CSI request bit field in DCI. The associated NZP CSI-RS resource(s) can be either periodic, semi-persistent, or aperiodic. The linkage between a code point of the CSI request field and a CSI report configuration is via an aperiodic CSI trigger state. A UE is configured by higher layer a list of aperiodic CSI trigger states, where each of the trigger states contains an associated CSI report configuration. The CSI request field is used to indicate one of the aperiodic CSI trigger states and thus, one CSI report configuration. If there are more than one NZP CSI-RS resource set and / or more than one CSI for Interference Management (CSI-IM) resource set are associated with a CSI report configuration, only one NZP CSI-RS resource set is selected in the aperiodic CSI trigger state. Thus, each aperiodic CSI report is based on a single NZP CSI-RS resource set. CQI and PMI can be reported per subband or wideband. In case of wideband CQI or PMI, the CQI or PMI is for the whole bandwidth configured for CSI report. In case of subband QCI or PMI, the CQI or PMI is reported for each subband. The subband size in NR can be from 4 RBs to 32 RBs, depending on the size of the BWP as shown in Table 2 below. Table 2: Configurable subband sizes Bandwidth part (PRBs) Subband size (PRBs) 24 – 72 4, 8 73 – 144 8, 16 145 – 275 16, 32 PDSCH Transmission from Multiple TRPs In NR Rel-16, non-coherent joint PDSCH transmission from two Transmission and Reception Points (TRPs) was introduced in which a subset of MIMO layers of a PDCCH to a UE are transmitted from a first TRP and the rest of layers of the PDSCH are transmitted from a second TRP in the same time and frequency resource. Different layers are separated and received at the UE with MIMO capable receiver. An example is shown in Figure 4, where a PDSCH with two layers are scheduled with the first layer transmitted from TRP1 and the second layer from TRP2. This is signaled in the corresponding DCI by indicating a TCI codepoint associated with two TCI states, a first and second TCI states, and DMRS ports x and y in two Code Division Multiplexing (CDM) groups, where DMRS port x in the first CDM group is associated with the first TCI state and DMRS port y in the second CDM group is associated with the second TCI state. The first TCI state may contain TRS1 as the QCL source RS and the second TCI state may contain TRS1 as the QCL source RS. Coherent Joint transmission of PDSCH over Multiple TRPs In NR Rel-18, coherent joint downlink transmission (i.e., Coherent Joint Transmission (CJT)) from multiple TRPs is supported by extending the Rel-16 enhanced type II codebook and Rel-17 further enhanced type II port selection codebook across multiple TRPs. The Rel-16 enhanced type II codebook is specified in clause 5.2.2.2.5 of 3rdGeneration Partnership Project (3GPP) 3GPP Technical Specification (TS) 38.214 V18.0.0, and the enhanced type II codebook for CJT is specified in clause 5.2.2.2.8 of 3GPP TS 38.214 V18.0.0. The Rel-17 enhanced type II port selection codebook is specified in clause 5.2.2.2.7 of 3GPP TS 38.214 V18.0.0, and the enhanced type II port selection codebook for CJT is specified in clause 5.2.2.2.9 of 3GPP TS 38.214 V18.0.0. In CJT, all layers are transmitted from the multiple TRPs used for CJT. An example with two layers and two TRPs is shown in Figure 5, where data symbols of the two layers are transmitted from two TRPs by applying two different precoding matrices at TRP1 and TRP2. The two precoders are designed such that for each layer, the signals received from the two TRPs are phase aligned at the UE and thus, are coherently combined. There are a number of challenges in supporting CJT. Firstly, propagation delays between different TRPs and a UE can be quite different. These large delay differences would result in a large frequency selective composite channel, i.e., the channel amplitude and phase vary rapidly across frequency. In existing NR CSI feedback, a precoding matrix per subband is reported. The subband size can vary between 2 RBs to 32 RBs as specified in 3GPP TS 38.214. Figure 6 shows phase variation within a subband for different subband sizes with one microsecond (1 µs) delay difference between two TRPs. It can be seen that even with 2 RB subband size, the phase variation exceeds 130 degrees. For constructive combining of two signals, their phase difference should be less than 90 degrees. Therefore, with current subband size and per subband CSI feedback, signals from multiple TRPs cannot be coherently combined with even 1µs delay difference. Secondly, even though a same nominal transmit frequency may be used at multiple TRPs, due to local oscillator stability, there will be some actual transmit frequency difference between the multiple TRPs. In 3GPP RAN4, the maximum transmit frequency error for a base station is specified in 3GPP TS 38.104, e.g., V18.4.0 and is copied in Figure 7. For the most stringent + / - 0.05 parts per million (ppm) requirement, there will be some residual frequency errors. These frequency errors mean that the phase of a signal will change over time. Delay Difference and Frequency Difference Pre-Compensation for CJT over Multiple TRPs Figure 8 shows an example of transmission of a signal ^^^^(^^^^) from two TRPs. ^^^^(^^^^) is multiplied by two co-phasing / pre-compensation coefficients ^^^^1and ^^^^2at the two TRPs before being transmitted to the UE. The effective propagation channels from the two TRPs to the UE, including transmitter and receiver circuitries and antenna patterns associated with the two TRPs, are denoted by ℎ1and ℎ2, respectively. ^^^1^ and ^^^2^ are the transmit frequencies and ^^^^1and ^^^^2are the randominitial phases at the two TRPs. ^^^^ is the propagation delay (including possible timing offsets)difference between the two TRPs. The composite signal at the UE can be expressed as ^^^^(^^^^) = ℎ ^^^^(2^^^1^^^^1^^^^(^^^^)^^^^ ^^^^1^ ^^^^+^^^^1) + ℎ ^^^^(2^^^^^^^2^^^^2^^^^(^^^^ − ^^^^)^^^^ 2^ (^^^^−^^^^)+^^^^2) (eq.1) For narrow-i.e., ^^^^(^^^^ − ^^^^) ≈ ^^^^(^^^^). Thus, we can revise (eq. 1) as^^^^(^^^^) ≈ ℎ ^^^^(2^^^^^^^^ ^^^^+^^^^ ) ^^^^(2^^^^^^^^ (^^^^−^ ) )1^^^^1^^^^(^^^^)^^^^ 1 1 + ℎ2^^^^2^^^^(^^^^)^^^^ 2 ^^^ +^^^^2 (eq. 2) or ^^^^(^^^^) ≈ (ℎ ^^^^ ^^ ^^^^^^^^1 ^^^^(2^^^^(^^^2^ −^^^1^ )^^^^−2^^^^^^^2^ ^^^^+^^^^2) ( ) ^^^^2^^^^^^^1^ ^^^^1 1 ^^ + ℎ2^^^^2^^^^ )^^^^ ^^^^ ^^^^ (eq. 3) To co- coefficients may be used ^^^^ = ^^^ −^^^^(∠ℎ1+^^^^1)1 ^ (eq. 4a) where a above co-phasing / pre-compensation coefficients in eq.4a-4b are applied, is then^^^^∗(^^^^) = (|ℎ1| + |ℎ2|)^^^^(^^^^)^^^^^^^^2^^^^^^^1^ ^^^^ (eq. 5)Alternatively, the co-phasing / pre-compensation coefficients can be as follows ^^^^1 = 1 (eq. 6a)^^^^ = ^^^^−^^^^(∠ℎ2+^^^^2−∠ℎ1+^^^^1+2^^^^(^^^2^ −^^^1^ )^^^^−2^^^^^^^2^ ^^^^)2 (eq. 6b) The co- eq. 6a-6b are applied, is then ^^^^∗(^^^^) = (|ℎ ^^^^(2^^^^^^^1| + |ℎ2|)^^^^(^^^^)^^^^ 1^ ^^^^+^^^^1) (eq. 7) Note case areIn that case, additional precoding or beamforming is applied to ^^^^(^^^^), where ^^^^(^^^^)is data associatedwith a MIMO layer of PDSCH or DMRS. For a given MIMO layer, the signal received from TRP1 would become ^^^^1^^^1^ ^^^^1^^^^(^^^^)^^^^^^^^(2^^^^^^^1^ ^^^^+^^^^1), where ^^^^1is a ^^^^1by M channel matrix, ^^^1^ is a ^^^^1by 1 precoding vector associated with the layer, ^^^^1is the ports deployed at TRPs and M is the number of receive antennas at UE. Similarly, for the given MIMO layer, the signal received from TRP2 would become ^^^^2^^^^2^^^^2^^^^(^^^^)^^^^^^^^(2^^^^^^^2^ (^^^^−^^^^)+^^^^2), where ^^^^2is a ^^^^2by M channel matrix, ^^^^2is a ^^^^2by 1 precoding vector associated with the corresponding MIMO layer, ^^^^2is the number of antenna ports deployed at TRP2. CJT from multiple TRPs is possible for the case of multiple PDSCH layers. For R PDSCH layers, each TRP will use a corresponding N1x R precoding matrix wherein each column in the precoding matrix corresponds to one of the R MIMO layers. In the case of R PDSCH layers, the transmitted data ^^^^(^^^^)will consists of R different symbols (i.e., one symbol corresponding to each of the R PDSCH layers). For CJT, it is envisioned that precoding matrices / vectors and the co-phasing / pre-compensation coefficients {^^^^1,^^^^2} are reported by the UE to the network. In order to derive the co-phasing / pre-compensation coefficients ^^^^1and ^^^^2, one or more of the following need to be reported from the UE to the network: • transmit frequency associated with a TRP, • transmit frequency difference between two TRPs, • delay associated with a TRP, • delay difference between two TRPs. Accordingly, there is a need for technologies that allow for efficient reporting of parameters, such as delay(s) / delay difference(s) and / or transmit frequency(ies) / transmit frequency difference(s) from the UE to the network. With such reporting, the network can pre-compensate for the delay difference(s) and / or frequency difference(s) between the TRPs such that coherent combining (i.e., as shown in eq.7) is achieved. SUMMARY According to an embodiment, a method performed by a UE is provided. According to the method the UE receives first configuration information from a network node. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the UE receives second configuration information from the network node. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. The UE selects all or a subset of the plurality of NZP CSI-RS resource sets for which the UE is to report the one or more reporting quantities and computes the one or more parameters for each selected NZP CSI-RS resource set. Further, the UE reports the computed one or more reporting quantities for the selected NZP CSI-RS resource sets. This reporting the computed one or more parameters for the selected NZP CSI-RS resource sets comprises reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. According to a further embodiment, a method performed by a network node is provided. According to the method, the network node transmits first configuration information to a UE. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the network node transmits second configuration information to the UE. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, the network node receives a report from the UE. The report comprises computed parameters for one or more selected NZP CSI-RS resource sets. The one or more selected NZP CSI-RS resource sets are all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE. The report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. According to a further embodiment, a UE is provided. The UE is configured to receive first configuration information from a network node. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the UE is configured to receive second configuration information from the network node. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, the UE is configured to select all or a subset of the plurality of NZP CSI-RS resource sets for which the UE is to report the one or more parameters. Further, the UE is configured to compute the one or more parameters for each selected NZP CSI-RS resource set. Further, the UE is configured to report the computed parameters for the selected NZP CSI-RS resource sets, by reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. According to a further embodiment, a UE is provided. The UE comprises processing circuitry and power supply circuitry configured to supply power to the processing circuitry. The processing circuitry is configured to receive first configuration information from a network node. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the processing circuitry is configured to receive second configuration information from the network node. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, the processing circuitry is configured to select all or a subset of the plurality of NZP CSI- RS resource sets for which the UE is to report the one or more parameters. Further, the processing circuitry is configured to compute the one or more parameters for each selected NZP CSI-RS resource set. Further, the processing circuitry is configured to report the computed parameters for the selected NZP CSI-RS resource sets, by reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. In some embodiments, the above configuration of the UE’s processing circuitry may be accomplished by execution of program code by the processing circuity. Such program code may be stored in a memory of the UE. According to a further embodiment, a network node is provided. The network node is configured to transmit first configuration information to a UE. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the network node is configured to transmit second configuration information to the UE. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, the network node is configured to receive, from the UE, a report comprising computed parameters for one or more selected NZP CSI-RS resource sets. The one or more selected NZP CSI-RS resource sets are all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE. The report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. According to a further embodiment, a network node is provided. The network node comprises processing circuitry and power supply circuitry configured to supply power to the processing circuitry. The processing circuitry is configured to transmit first configuration information to a UE. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, the processing circuitry is configured to transmit second configuration information to the UE. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, the processing circuitry is configured to receive a report from the UE. The report comprises computed parameters for one or more selected NZP CSI-RS resource sets, and the one or more selected NZP CSI-RS resource sets are all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE. The report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. In some embodiments, the above configuration of the network node’s processing circuitry may be accomplished by execution of program code by the processing circuity. Such program code may be stored in a memory of the network node. According to a further embodiment, a computer program or computer program product is provided which comprises instructions to be executed by processing circuitry of a UE. Execution of the instructions causes the UE to receive first configuration information from a network node. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, execution of the instructions causes the UE to receive second configuration information from the network node. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, execution of the instructions causes the UE to select all or a subset of the plurality of NZP CSI-RS resource sets for which the UE is to report the one or more parameters. Further, execution of the instructions causes the UE to compute the one or more parameters for each selected NZP CSI-RS resource set. Further, execution of the instructions causes the UE to report the computed parameters for the selected NZP CSI-RS resource sets, by reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. According to a further embodiment, a computer program or computer program product is provided which comprises instructions to be executed by processing circuitry of a network node. Execution of the instructions causes the network node to transmit first configuration information to a UE. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Further, execution of the instructions causes the network node to transmit second configuration information to the UE. The second configuration information configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. Further, execution of the instructions causes the network node to receive, from the UE, a report comprising computed parameters for one or more selected NZP CSI-RS resource sets. The one or more selected NZP CSI-RS resource sets are all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE. The report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. Figure 1 illustrates New Radio (NR) physical resources; Figure 2 illustrates the NR time-domain structure with 15kHz subcarrier spacing; Figure 3 illustrates an example of Resource Element (RE) allocation for a Tracking Reference Signal (TRS) in NR; Figure 4 illustrates an example of Physical Downlink Shared Channel (PDSCH) transmission from multiple Transmission and Reception Points (TRPs); Figure 5 illustrates an example of Coherent Joint Transmission (CJT) over two TRPs; Figure 6 illustrates an example showing phase variation over a subband for 1 microsecond (µs) delay difference; Figure 7 illustrates the 3rdGeneration Partnership Project (3GPP) minimum requirement on transmit frequency error; Figure 8 illustrates an example of CJT from two TRPs; Figure 9 is a flow chart that illustrates a process performed by a User Equipment (UE) for reporting of delay(s) and / or delay difference(s) for CJT with TRP subset selection, in accordance with one embodiment of the present disclosure; Figure 10 shows an example of one embodiment of the present disclosure; Figure 11 shows an example of one embodiment of the present disclosure; Figure 12 shows an example of one embodiment of the present disclosure; Figure 13 shows an example of one embodiment of the present disclosure; Figure 14 shows an example of one embodiment of the present disclosure; Figure 15 is a flow chart that illustrates a method performed by a network node in accordance with an embodiment of the present disclosure; Figure 16 shows a flowchart for illustrating a UE-based method according to an embodiment of the present disclosure. Figure 17 shows a flowchart for illustrating a network-node based method according to an embodiment of the present disclosure. Figure 18 shows an example of a communication system in accordance with some embodiments of the present disclosure; Figure 19 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure; Figure 20 shows a network node in accordance with some embodiments of the present disclosure; Figure 21 is a block diagram of a host, which may be an embodiment of the host of Figure 16, in accordance with various aspects of the present disclosure described herein; Figure 22 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized; and Figure 23 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. There currently exist certain challenge(s) in regard to Coherent Joint Transmission (CJT) of Physical Downlink Shared Channel (PDSCH) over Multiple Transmission and Reception Points (TRPs). How the User Equipment (UE) is configured to report propagation delay(s) / propagation delay difference(s) for CJT is disclosed. Furthermore, what quantities (i.e., propagation delay differences and / or transmit frequency differences) are reported and how a subset of TRPs (or Tracking Reference Signals (TRSs)) are selected for which these reporting quantities are reported have also been disclosed. However, how the UE reports the delay differences, frequency differences, and / or phase differences for CJT for the selected subset of TRPs is an open problem to be solved. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Considering multi-TRP setups, systems and methods for a detailed reporting format for reporting quantities, e.g., delay, frequency and / or phase difference, with TRP subset selection are disclosed. Different reporting formats including one-part and two-part reporting are disclosed. In an embodiment of two-part reporting, first the selected sub-set of TRPs is indicated (e.g., via a bitmap) in part 1, followed by the reporting quantity for the selected TRPs in part 2. In an embodiment of one-part reporting, the network node (e.g., gNB in the case of New Radio (NR)) is provided with the Channel State Information (CSI) quantity of the selected TRPs in one part, where the CSI quantity of the selected TRPs are indicated with valid (e.g., non-zero) values (and, invalid / default values are used for the non-selected TRPs). Embodiments of the present disclosure relate to how the reporting quantities for a subset of selected TRPs are reported: • In a first set of solutions, a two-part reporting is proposed, wherein a bitmap or identifiers in a first part of the report indicate which TRPs are selected, and the second part of the report includes the reporting quantities for the subset of selected TRPs. • In a second set of solutions, a single-part reporting is proposed, wherein the report includes valid and / or non-zero reporting quantities only for the subset of selected TRPs, and an invalid or reserved value is reported for each non-selected TRP. Certain embodiments may provide one or more of the following technical advantage(s). Considering TRP subset selection, embodiments of various reporting format methods for reporting of inter-TRP delay, frequency, and / or phase differences for CJT are disclosed. The proposed one- and two-part reporting schemes provide flexibility in reporting the information that the network node (e.g., gNB) desires for compensating the delay / frequency / phase differences between the TRPs. Moreover, the signaling overhead is reduced as these reporting quantities are only reported for a subset of TRPs. In this way, the proposed scheme addresses one of the topics of interest in Rel-19 as well as in future generations (e.g., 6thGeneration (6G)) of the 3GPP system. Now, a more detailed description of embodiments of the present disclosure will be provided. Although the term TRP is used in this disclosure, the term TRP might not be captured in 3GPP specifications. Instead, a TRP can be represented by any one of ‘NZP CSI-RS resource set’, ‘NZP CSI-RS resource’, ‘TRS resource set’, and / or ‘TRS resource’, or in general downlink reference signal (DL-RS). The terminologies ‘delay(s)’ and ‘propagation delay(s)’ may be used interchangeably in the disclosure. In 6G, other terms than NZP CSI-RS might be used. For example, a new downlink reference signal or downlink synchronization signal might be introduced in 6G which then can be used instead of NZP CSI-RS. The 6G downlink reference signals and / or downlink synchronization signals might be aperiodically, semi-persistently, or periodically transmitted. Although the embodiments below are written with respect to NZP CSI-RS resource sets, the below embodiments are non-limiting and are equally applicable when NZP CSI-RS resource sets are replaced by NZP CSI-RS resource(s), TRS(s), TRS resource set(s), and / or DL-RS(s). In 6G, CSI reports might be transmitted in Medium Access Control (MAC) messages, which means that the CSI report can be included in a single message and where the message can vary in size. A flowchart of the method at the UE for reporting the delay(s) and / or delay difference(s) for CJT with TRP subset selection is shown in Figure 9. Although Figure 9 is written from the perspective of reporting delay(s) and / or delay difference(s), the embodiments presented herein are non- limiting and are also equally applicable to one or more of the following cases: • the UE reports frequency(ies) and / or frequency difference(s) instead of delay(s) and / or delay difference(s); To arrive at the UE steps for the case when the UE reports frequency(ies) and / or frequency difference(s), the terms ‘delay(s)’ and ‘delay difference(s)’ in Figure 9 can be respectively replaced with ‘frequency(ies)’ and ‘frequency difference(s)’. • the UE reports phase(s) and / or phase difference(s) instead of delay(s) and / or delay difference(s); To arrive at the UE steps for the case when the UE reports phase(s) and / or phase difference(s), the terms ‘delay(s)’ and ‘delay difference(s)’ in Figure 9 can be respectively replaced with ‘phase(s)’ and ‘phase difference(s)’. • the UE reports derivatives of phase(s) instead of phase(s). To arrive at the UE steps for the case when UE reports derivatives phase(s), the terms ‘delay(s)’ in Figure 9 can be replaced with derivatives of phase(s). The derivative of phase is referred to the amount of change in phase, at each TRP, within a (relative) time period e.g., a number of symbols / slots / ms. The steps involved in the flowchart of Figure 9 are elaborated below: Step 1: A UE receives configuration from a network node (e.g., a gNB for the description of this example embodiment) of N > 1 different NZP CSI-RS resource sets. Each of the NZP CSI-RS resource sets contain at least one NZP CSI-RS resource. • In one case, the N different NZP CSI-RS resource sets may be configured as part of a CSI- ResourceConfig Information Element (IE) as defined in 3GPP TS 38.33118.0.0, where a new report quantity for reporting delay(s) or delay difference(s) is introduced. In this case, a parameter that points to the Identity (ID) of the CSI-ResourceConfig IE that contains the different NZP CSI-RS resource sets is configured in a CSI reporting configuration used for configuring propagation delay / propagation delay difference reporting. • In another case, the CSI report for the delays or delay differences is aperiodic and is triggered by a Downlink Control Information (DCI) format, where the N > 1 different NZP CSI-RS resource sets are configured as part of CSI-AssociatedReportConfigInfo in the CSI- AperiodicTriggerStateList IE as defined in 3GPP TS 38.331 V18.0.0. • In some cases, each of the N NZP CSI-RS resource sets is configured with parameter ‘trs- Info’ set to true which means the NZP CSI-RS resources in each of the N NZP CSI-RS resource sets is a Tracking Reference Signal (TRS). Step 2: The UE receives configuration (e.g., via RRC configuration) from the gNB requesting the UE to report one or more propagation delay(s) or propagation delay difference(s) based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. • In one case, a new reporting quantity may be configured as part of the CSI reporting configuration (e.g., via higher layer parameter reportQuantity as defined in 3GPP TS 38.331 V18.0.0) in the reporting configuration used for configuring propagation delay / propagation delay difference reporting. The new reporting quantity will be set to a value of either ‘propagation delay’ or ‘propagation delay difference’ which means the UE is requested to report to the value requested. • In another case, the number of propagation delay(s) or propagation delay difference(s) to be reported by the UE is configured to the UE by the gNB. This number may be configured as part of the reporting configuration used for configuring propagation delay / propagation delay difference reporting. Step 3 (Optional): The UE optionally determines a reference resource set for computing and reporting propagation delay difference(s) between one or more of the multiple resource sets and the reference resource set. • In some cases, the UE chooses (i.e., selects) one of the N different NZP CSI-RS resource sets to be used as the reference resource set. • In some other case, the UE receives explicit configuration or indication of the reference resource set to be used. In one case, an ID of the reference resource set is configured as part of the reporting configuration used for configuring propagation delay / propagation delay difference reporting. • In some other cases, the reference resource set may be given by an implicit rule specified in 3GPP specifications. In one example, the reference resource set may be given by the one NZP CSI-RS resource set that has the lower ID (e.g., lower nzp-CSI-ResourceSetId as defined in 3GPP TS 38.331 V18.0.0) among the N configured NZP CSI-RS resource sets. In another example of an implicit rule, the reference resource set may be given by the first NZP CSI-RS resource set in a list of N configured NZP CSI-RS resource sets. Alternatively, the reference resource set may be given by the last NZP CSI-RS resource set in a list of N configured NZP CSI-RS resource sets. Step 4: The UE selects a subset of the NZP CSI-RS resource sets for which the UE is to compute / report propagation delay(s) or propagation delay difference(s) wherein the UE computes / reports one propagation delay value or one propagation delay difference value for each selected NZP CSI-RS resource set. Note that the NZP CSI-RS resource sets are selected from the configured N NZP CSI-RS resource sets configured in Step 1. For instance, the UE may select of subset of TRSs which have a received power higher than a pre-defined threshold. Alternatively, the UE may select a subset of M TRSs with the highest received power. In one embodiment, the same or different subsets of TRPs may be selected for different delay, frequency and / or phase CSI quantities. Step 5: Considering the selected subset of the NZP CSI-RS resource sets, the UE computes propagation delay(s) or propagation delay difference(s) wherein the UE computes one propagation delay value or one propagation delay difference value for each selected NZP CSI-RS resource set in Step 4. Step 6: The UE reports propagation delay(s) or propagation delay difference(s) according to at least one of the following solutions, which are referred to as “Solution 1”, “Solution 2”, and “Solution 3”. Solution 1: In Solution 1, the reporting of Step 6 includes two parts wherein: • In a first part of the report, a bitmap indicates which NZP CSI-RS resource sets are selected. Given that there are N NZP CSI-RS resource sets configured to the UE as part of the CSI reporting configuration configured for delay(s) and / or delay difference(s) reporting, the bitmap will have N bits wherein each bit in the bitmap indicates whether an NZP CSI-RS resource set is selected or not. When the ^^^^^^^^ℎbit in the bitmap is set to a first value (e.g., a value of 1), it indicates to the network that the ^^^^^^^^ℎNZP CSI-RS resource set is selected. When the ^^^^^^^^ℎbit in the bitmap is set to a second value (e.g., a value of 0), it indicates to the network that the ^^^^^^^^ℎNZP CSI-RS resource set is not selected. • In one embodiment, the delay, frequency, and phase differences are reported jointly or separately, where the same or different bitmaps are used, respectively, to indicate the selected NZP CSI-RS resource set(s) for the delay, frequency, and phase report. For instance, if multiple reporting quantities among delay, frequency, and phase differences are reported in the same report, then in one embodiment, different bitmaps may be included in part one dedicated to each reporting quantity for selecting NZP CSI-RS resource sets specific to each of the reporting quantities. In another example, one bitmap that is common for all reporting quantities is included in part one for selecting NZP CSI-RS resource sets. o In 6G where new downlink reference signals and / or downlink synchronization signals with aperiodic or semi-persistent behavior might be introduced and used for frequency / delay / phase reporting, some of the downlink reference signals and / or downlink synchronization signals associated with a report might not have been triggered and / or transmitted within a certain time window before the frequency / delay / phase report is triggered or transmitted. In one detailed embodiment, the UE shall set the corresponding downlink reference signals resource set(s) and / or downlink synchronization signal resource set(s) to 0 in the bitmap (i.e., the UE can omit any reporting associated with these resource sets from the report). • In a second part of the report, in one embodiment, one propagation delay value for each NZP CSI-RS resource set indicated as selected in the first part is included. Alternatively, in another embodiment, one propagation delay difference value for each NZP CSI-RS resource set indicated as selected in the first part is included wherein the delay difference is with respect to the reference resource set(s). o In one embodiment, if report quantity in the CSI report configuration specifying more than one quantity, e.g., delay difference (quantity#1) and frequency difference (quantity#2), the reporting order can be determined according to the specification or is configurable by the higher layer signaling. In one example, the reporting is in order of the configured NZP CSI-RS resource sets (or TRPs): TRP#1(quantity#1, quantity#2), TRP#2(quantity#1, quantity#2). In another example, the reporting is in order of the report quantities: quantity#1(TRP#1, TRP#2), quantity#2(TRP#1, TRP#2). One example is given in Figure 11. Figure 10 shows an example of Solution 1 where six NZP CSI-RS resource sets are configured to the UE and the UE reports delay(s) or delay difference(s) corresponding to three of the NZP CSI- RS resource sets. In CSI part 1, a bitmap of length 6 is included wherein bits 1, 2 and 6 are set to a value of 1 which means NZP CSI-RS resource sets 1, 2, and 6 (respectively corresponding to TRPs 1, 2, and 6) are selected. Then, according to one embodiment, in CSI part 2, the quantizedversions of measured / computed delays ^^^^1, ^^^^2, and ^^^^6 corresponding to NZP CSI-RS resource sets1, 2, and 6 are reported. According to an alternative embodiment, in CSI part 2, the quantizedversions of measured / computed delay difference(s) (^^^^2 − ^^^^1) and (^^^^6 − ^^^^1) are reported, whereinthe 1stNZP CSI-RS resource set (corresponding to TRP #1) is used as the reference NZP CSI-RS resource set. Figure 11 shows another example of Solution 1 where six NZP CSI-RS resource sets are configured to the UE and the UE reports both delay difference(s) and frequency difference(s) corresponding to three of the NZP CSI-RS resource sets. In CSI part 1, a bitmap of length 6 is included wherein bits 1, 2 and 6 are set to a value of 1 which means NZP CSI-RS resource sets 1, 2, and 6 (respectively corresponding to TRPs 1, 2, and 6) are selected. Then, according to one embodiment, in CSI part 2, the quantized versions of measured / computed delay difference(s)(^^^^2 − ^^^^1) and (^^^^6 − ^^^^1) , and frequency difference(s) (^^^2^ − ^^^1^ ) and (^^^6^ − ^^^1^ ), are reported,wherein the 1stNZP CSI-RS resource set (corresponding to TRP #1) is used as the reference NZPCSI-RS resource set. In one example, the reporting order is (^^^^2 − ^^^^1), (^^^2^ − ^^^1^ ), (^^^^6 − ^^^^1), (^^^6^ −^^^1^ ). In another example, the reporting order is (^^^^2 − ^^^^1), (^^^^6 − ^^^^1), (^^^2^ − ^^^1^ ), (^^^6^ − ^^^1^ ).Solution 2: In Solution 2, the reporting of Step 6 includes a single part wherein: • In one embodiment, for each selected NZP CSI-RS resource set, the single part CSI report includes one valid and / or non-zero propagation delay value wherein the valid non-zero propagation delay value may be quantized to X bits. A valid and non-zero propagation delay value is a codepoint in the X bit field that represents a non-zero propagation delay value that may be predefined in a table in 3GPP specifications. • In this embodiment, for each non-selected NZP CSI-RS resource set, the single part CSI report includes one invalid, reserved, or void propagation delay value. The invalid, reserved, or void propagation delay corresponds to one or more reserved codepoints in the X bit field that are not associated with any propagation delay value. • In an alternative embodiment, for each selected NZP CSI-RS resource set, the single part CSI report includes one valid and / or non-zero propagation delay difference value with respect to the reference resource set wherein the valid non-zero propagation delay difference value may be quantized to Y bits. A valid and non-zero propagation delay difference value is a codepoint in the Y bit field that represents a non-zero propagation delay difference value that may be predefined in a table in 3GPP specifications. • In the alternative embodiment, for each non-selected NZP CSI-RS resource set, the single part CSI report includes one invalid, reserved, or void propagation delay difference value. The invalid, reserved, or void propagation delay corresponds to one or more reserved codepoints in the Y bit field that are not associated with any propagation delay difference value. Figure 12 shows a first example of Solution 2 where six NZP CSI-RS resource sets are configured to the UE and the UE reports delay(s) or delay difference(s) corresponding to three of the NZP CSI-RS resource sets. NZP CSI-RS resource sets 1, 2, and 6 (i.e., TRPs 1, 2, and 6) are selected for delay value reporting. An X=3 bit table of quantized values of propagation delay is predefined. The valid non-zero propagation delays are given by codepoints 000, 001, 010, 011, 100, 101, and 110. The codepoint 111 is reserved. Then, in the single part CSI, ^ codepoint 000 is reported which corresponds to the quantized value of ^^^^1; ^ codepoint 010 is reported which corresponds to the quantized value of ^^^^2; ^ codepoint 101 is reported which corresponds to the quantized value of ^^^^6; ^ the reserved codepoint 111 is reported for non-selected NZP CSI-RS resource sets 3, 4, and 5. Figure 13 shows a second example of Solution 2 where six NZP CSI-RS resource sets are configured to the UE and the UE reports delay(s) or delay difference(s) corresponding to three of the NZP CSI-RS resource sets. NZP CSI-RS resource sets 1, 2, and 6 (i.e., TRPs 1, 2, and 6) are selected for delay value reporting. An Y=2 bit table of quantized values of propagation delay differences is predefined. The valid non-zero propagation delay differences are given by codepoints 00, 01, and 10. The codepoint 11 is reserved. In this example, it is assumed NZP CSI- RS resource set 1 (corresponding to TRP 1) is used as the reference resource set. Then, in the single part CSI, ^codepoint 00 is reported which corresponds to the quantized value of ^^^^2 − ^^^^1;^ codepoint 10 is reported which corresponds to the quantized value of ^^^^6 − ^^^^1; ^ the reserved codepoint 11 is reported for non-selected NZP CSI-RS resource sets 3, 4, and 5. In a further embodiment, the single part CSI report can indicate more than one quantity for each of the selected TRP. Figure 14 shows a third example of Solution 2 where six NZP CSI-RS resource sets are configured to the UE and the UE reports both delay(s) and frequency(ies) in the same single part CSI reporting corresponding to three of the NZP CSI-RS resource sets. NZP CSI- RS resource sets 1, 2, and 6 (i.e., TRPs 1, 2, and 6) are selected for delay value reporting. An X=3 bit table of quantized values of propagation delay is predefined. In addition, an X=2 bit table of quantized values of frequency is also predefined. Each codepoint of the single part CSI report carries indications for both delay and frequency. As illustrated in the figure, the starting 3 bits (marked in blue) is used to indicate the propagation delay. The remaining 2 bits to the right (marked in black) is used to indicate the frequency. Solution 3: In Solution 3, the reporting of Step 6 consists of a single message (e.g., a single MAC message in this example), wherein the MAC message includes one or more of: • A bitmap or a set of fields indicating which NZP CSI-RS resource sets are selected. Given that there are N NZP CSI-RS resource sets configured to the UE as part of the CSI reporting configuration configured for delay(s) and / or delay difference(s) reporting, the bitmap or set of fields will have N bits wherein each bit in the bitmap indicates whether an NZP CSI- RS resource set is selected or not. When the ^^^^^^^^ℎbit in the bitmap or the ^^^^^^^^ℎfield in the set of fields is set to a first value (e.g., a value of 1), it indicates to the network that the ^^^^^^^^ℎNZP CSI-RS resource set is selected. When the ^^^^^^^^ℎbit in the bitmap or the ^^^^^^^^ℎfield in the set of fields is set to a second value (e.g., a value of 0), it indicates to the network that the ^^^^^^^^ℎNZP CSI-RS resource set is not selected. o In 6G where new downlink reference signals and / or downlink synchronization signals with aperiodic or semi-persistent behavior might be introduced and used for frequency / delay / phase reporting, some of the downlink reference signals and / or downlink synchronization signals associated with a report might not have been triggered and / or transmitted within a certain time window before the frequency / delay / phase report is triggered or transmitted. In one detailed embodiment, the UE shall set the corresponding downlink reference signals resource set(s) and / or downlink synchronization signal resource set(s) to 0 in the bitmap (i.e. the UE can omit any reporting associated with these resource sets from the report). • A propagation delay value for each NZP CSI-RS resource set indicated as selected by the bitmap or field described above is included in the MAC message. Alternatively, in another embodiment, one propagation delay difference value for each NZP CSI-RS resource set indicated as selected is included in the MAC message wherein the delay difference is with respect to the reference resource set(s). Figure 15 is a flow chart that illustrates a method performed by a network node (e.g., a gNB in this example embodiment) in accordance with an embodiment of the present disclosure. Note that this process is complementary to the process performed by the UE described above, e.g., with respect to Figure 9. As such, details above provided in relation to Figures 9-14 are equally applicable to Figure 15. As illustrated, the gNB sends, to the UE, a configuration of N > 1 different NZP CSI- RS resource sets, as described above (step 1). Each of the NZP CSI-RS resource sets contain at least one NZP CSI-RS resource. The gNB sends, to the UE, configuration (e.g., via RRC configuration) requesting the UE to report one or more propagation delay(s) or propagation delay difference(s) based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets (step 2). The gNB receives, from the UE, a report of the propagation delay(s) or propagation delay difference(s) in accordance with Solution 1, Solution 2, or Solution 3, as described above (step 3). Figure 16 shows a flowchart illustrating a method according to an embodiment, which may be used to implement the illustrated concepts in a UE. If a processor-based implementation of the UE is used, at least some of the steps of the method of Fig.16 may be performed and / or controlled by processing circuitry of the UE, e.g., by one or more processors. Such UE may also include a memory storing program code for implementing at least some of the steps of the method of Fig. 16. At step 1610, the UE receives first configuration information from a network node, e.g., by RRC signaling. The network node may for example correspond to a radio access node or base station of a wireless communication network, e.g., a gNB. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Each selected NZP CSI-RS resource set may correspond to a selected TRP. The number of NZP CSI-RS resource sets may be denoted by N, with N > 1. Each of the NZP CSI-RS resource sets may comprise at least one NZP CSI-RS resource. In one example, step 1610 may involve that N different NZP CSI-RS resource sets are configured as part of a CSI-ResourceConfig Information Element (IE) as defined in 3GPP TS 38.331 V18.0.0. At step 1620, the UE receives second configuration information from the network node, e.g., by RRC signaling. The second configuration configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. The one or more parameters may for example include propagation delays, propagation delay differences, frequencies, frequency differences (or frequency offsets), phases, phase differences, and / or derivatives of phases. The one or more parameters may also be denoted as “reporting quantity” or “report quantity”, e.g., like in the above description. The differences may be with respect to a value measured for a reference NZP CSI-RS resource set. For example, the propagation delay differences may be propagation delay differences with respect to a propagation delay value measured for a reference NZP CSI-RS resource set, and / or the frequency differences may be frequency differences with respect to a frequency value measured for a reference NZP CSI-RS resource set. In some scenarios, the second configuration information may request the UE to report one or more propagation delay(s) or propagation delay difference(s) based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. In some cases, a new reporting quantity may be configured as part of a CSI reporting configuration (e.g., via higher layer parameter reportQuantity as defined in 3GPP TS 38.331 V18.0.0) in a reporting configuration used for configuring propagation delay / propagation delay difference reporting. The new reporting quantity may be set to a value of either ‘propagation delay’ or ‘propagation delay difference’, and the UE may report the value as requested. In some cases, the number of propagation delay(s) or propagation delay difference(s) to be reported by the UE is configured by the network node. This number may be configured as part of the reporting configuration. At optional step 1630, the UE may optionally determine a reference resource set for computing and reporting the one or more parameters in terms of difference(s) of measured values between one or more of the multiple NZP CSI-RS resource sets and the reference resource set. In some cases, the UE may choose or select one of the N different NZP CSI-RS resource sets to be used as the reference resource set (step 1631). For example, if there are N TRPs, each corresponding to one of the NZP CSI-RS, the UE could select one of the NZP CSI-RS (which corresponds to selecting one of the TRPs) as reference, and then report N-1 (or less) values of delay difference and / or frequency difference with respect to the delay / frequency measured for the reference NZP CSI-RS. Further, the UE may also indicate, e.g., as part of the report, which NZP CSI-RS / TRP was selected as the reference. In other cases, the UE may receive explicit configuration or indication of the reference resource set to be used (step 1632). In one case, an ID of the reference resource set may be configured as part of the reporting configuration. In some other cases, the reference resource set may be given by an implicit rule specified in 3GPP specifications (step 1633). In one example, the reference resource set may be given by the one NZP CSI-RS resource set that has the lower ID (e.g., lower nzp-CSI-ResourceSetId as defined in 3GPP TS 38.331 V18.0.0) among the N configured NZP CSI-RS resource sets. In another example of an implicit rule, the reference resource set may be given by the first NZP CSI-RS resource set in a list of N configured NZP CSI-RS resource sets. Alternatively, the reference resource set may be given by the last NZP CSI-RS resource set in a list of N configured NZP CSI-RS resource sets. At step 1640, the UE selects all or a subset of the NZP CSI-RS resource sets for which the UE is to compute the one or more parameters. The UE may compute one parameter value or one parameter difference value for each selected NZP CSI-RS resource set. The NZP CSI-RS resource sets are selected from the NZP CSI-RS resource sets configured in step 1610. For instance, the UE may select a subset of TRSs which have a received power higher than a pre-defined threshold. Alternatively, the UE may select a subset of M TRSs with the highest received power. Each selected NZP CSI-RS resource set may correspond to a selected TRP. In some scenarios, the same or different NZP CSI-RS resource sets may be selected for different parameters to be reported. For example, the same or different subsets of NZP CSI-RS may be selected for reporting delay, frequency, and / or phase. If the configuration information received from the network node at step 1620 configured the UE to report two or more parameters, step 1640 may involve that the UE selects the same NZP CSI- RS resource sets are selected for all of the two or more parameters. Alternatively, the NZP CSI- RS resource sets selected for at least two of the two or more parameters could be different. At step 1650, the UE computes the one or more parameters for each selected NZP CSI-RS resource set, e.g., one propagation delay value or one propagation delay difference value for each selected NZP CSI-RS resource set. At step 1660, the UE reports the computed one or more parameters, which may be accomplished in a single message. The UE may report the one or more parameters on a physical channel, e.g., in UCI (Uplink Control Information) transmitted on the PUCCH. In step 1660, the UE reports: - for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set, e.g., in terms of a valid value; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected, e.g., in terms of an invalid or reserved value. Figures 12, 13, and 14 illustrate examples of report formats which may be used in the reporting of step 1660. In some scenarios, the reporting of the computed parameters for the selected NZP CSI-RS resource sets may involve reporting a bit field for each of the NZP CSI-RS resource sets. For each selected NZP CSI-RS resource set, the bit field may then represent a respective value of the one or more parameters, and for each non-selected NZP CSI-RS resource set, the bit field may represent a reserved value indicating that the NZP CSI-RS resource set is not selected. In some scenarios, quantized values of the one or more parameters may be mapped to codepoints of the bit field, and a reserved codepoint of the bit field may indicate that the NZP CSI-RS resource set is not selected. The mapping of the codepoints to the quantized values may be predefined, e.g., by 3GPP specification. In some scenarios, the UE may be configured to report two or more parameters for each of the selected NZP CSI-RS sets and quantized values of the two or more parameters may be mapped to one codepoint of the bit field. Figure 17 shows a flowchart illustrating a method according to an embodiment, which may be used to implement the illustrated concepts in a network node. The network node may for example correspond to a radio access node or base station of a wireless communication network, e.g., a gNB. If a processor-based implementation of the network node is used, at least some of the steps of the method of Fig.17 may be performed and / or controlled by processing circuitry of the network node, e.g., by one or more processors. Such node may also include a memory storing program code for implementing at least some of the steps of the method of Fig.17. At step 1710, the network node transmits first configuration information to a UE, e.g., by RRC signaling. The first configuration information configures the UE with a plurality of NZP CSI-RS resource sets. Each selected NZP CSI-RS resource set may correspond to a selected TRP. The number of NZP CSI-RS resource sets may be denoted by N, with N > 1. Each of the NZP CSI-RS resource sets may comprise at least one NZP CSI-RS resource. In one example, step 1710 may involve that N different NZP CSI-RS resource sets are configured as part of a CSI-ResourceConfig Information Element (IE) as defined in 3GPP TS 38.331 V18.0.0. At step 1720, the network node transmits second configuration information to the UE, e.g., by RRC signaling. The second configuration configures the UE to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. The one or more parameters may for example include propagation delays, propagation delay differences, frequencies, frequency differences (or frequency offsets), phases, phase differences, and / or derivatives of phases. The one or more parameters may also be denoted as “reporting quantity” or “report quantity”, e.g., like in the above description. The differences may be with respect to a value measured for a reference NZP CSI-RS resource set. For example, the propagation delay differences may be propagation delay differences with respect to a propagation delay value measured for a reference NZP CSI-RS resource set, and / or the frequency differences may be frequency differences with respect to a frequency value measured for a reference NZP CSI-RS resource set. In some scenarios, the second configuration information may request the UE to report one or more propagation delay(s) or propagation delay difference(s) based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets. In some cases, a new reporting quantity may be configured as part of a CSI reporting configuration (e.g., via higher layer parameter reportQuantity as defined in 3GPP TS 38.331 V18.0.0) in a reporting configuration used for configuring propagation delay / propagation delay difference reporting. The new reporting quantity may be set to a value of either ‘propagation delay’ or ‘propagation delay difference’, and the UE may report the value as requested. In some cases, the number of propagation delay(s) or propagation delay difference(s) to be reported by the UE is configured by the network node. This number may be configured as part of the reporting configuration. At step 1730, the network node receives a report from the UE. The network node may receive the report from a physical channel, e.g., in UCI transmitted on the PUCCH. The report includes computed one or more parameters for one or more selected NZP CSI-RS resource sets. Theses selected NZP CSI-RS resource sets are selected from the NZP CSI-RS resource sets configured for the UE at step 1710. The network node may receive the report in a single message. The report includes: - for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set, e.g., in terms of a valid value; and for each non-selected NZP CSI-RS resource set configured for the UE, information that indicates that the non-selected NZP CSI-RS resource set is not selected, e.g., in terms of an invalid or reserved value. Figures 12, 13, and 14 illustrate examples of report formats which may be used in the report of step 1660. In some scenarios, the report may include a bit field for each of the NZP CSI-RS resource sets. For each selected NZP CSI-RS resource set, the bit field may then represent a respective value of the one or more parameters, and for each non-selected NZP CSI-RS resource set, the bit field may represent a reserved value indicating that the NZP CSI-RS resource set is not selected. In some scenarios, quantized values of the one or more parameters may be mapped to codepoints of the bit field, and a reserved codepoint of the bit field may indicate that the NZP CSI-RS resource set is not selected. The mapping of the codepoints to the quantized values may be predefined, e.g., by 3GPP specification. In some scenarios, the UE may be configured to report two or more parameters for each of the selected NZP CSI-RS sets and quantized values of the two or more parameters may be mapped to one codepoint of the bit field. In some scenarios, the same or different NZP CSI-RS resource sets may be selected for different parameters to be reported. For example, the same or different subsets of NZP CSI-RS may be selected for reporting delay, frequency, and / or phase. If the configuration information received from the network node at step 1620 configured the UE to report two or more parameters, step 1640 may involve that the UE selects the same NZP CSI- RS resource sets are selected for all of the two or more parameters. Alternatively, the NZP CSI- RS resource sets selected for at least two of the two or more parameters could be different. Figure 18 shows an example of a communication system 1800 in which embodiments of the present disclosure may be implemented. In the example, the communication system 1800 includes a telecommunication network 1802 that includes an access network 1804, such as a Radio Access Network (RAN), and a core network 1806, which includes one or more core network nodes 1808. The access network 1804 includes one or more access network nodes, such as network nodes 1810A and 1810B (one or more of which may be generally referred to as network nodes 1810), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1802 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 1802, including one or more network nodes 1810 and / or core network nodes 1808. Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O-CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1810 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1812A, 1812B, 1812C, and 1812D (one or more of which may be generally referred to as UEs 1812) to the core network 1806 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 1800 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 1800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 1812 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 1810 and other communication devices. Similarly, the network nodes 1810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1812 and / or with other network nodes or equipment in the telecommunication network 1802 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 1802. Note that the functionality of the network node or gNB described above (e.g., with respect to Figures 9-16) may be implemented in any one of the network nodes 1810, and the functionality of the UE described above (e.g., with respect to Figures 9-16) may be implemented in any one of the UEs 1812. In this regard, the network node 1810 may be a multi-TRP network node (e.g., a gNB having multiple TRPs). In the depicted example, the core network 1806 connects the network nodes 1810 to one or more hosts, such as host 1816. 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 1806 includes one more core network nodes (e.g., core network node 1808) 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 1808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and / or the telecommunication network 1802, and may be operated by the service provider or on behalf of the service provider. The host 1816 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 1800 of Figure 18 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 1802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1802. For example, the telecommunication network 1802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / or massive Machine Type Communication (mMTC) / massive Internet of Things (IoT) services to yet further UEs. In some examples, the UEs 1812 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 1804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1804. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC). In the example, a hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812C and / or 1812D) and network nodes (e.g., network node 1810B). In some examples, the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs. As another example, the hub 1814 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 1810, or by executable code, script, process, or other instructions in the hub 1814. As another example, the hub 1814 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 1814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1814 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 1814 may have a constant / persistent or intermittent connection to the network node 1810B. The hub 1814 may also allow for a different communication scheme and / or schedule between the hub 1814 and UEs (e.g., UE 1812C and / or 1812D), and between the hub 1814 and the core network 1806. In other examples, the hub 1814 is connected to the core network 1806 and / or one or more UEs via a wired connection. Moreover, the hub 1814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 1804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1810 while still connected via the hub 1814 via a wired or wireless connection. In some embodiments, the hub 1814 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1810B. In other embodiments, the hub 1814 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 1810B, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Figure 19 shows a UE 1900 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. 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 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input / output interface 1906, a power source 1908, memory 1910, a communication interface 1912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 19. 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 1902 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 1910. The processing circuitry 1902 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 1902 may include multiple Central Processing Units (CPUs). In the example, the input / output interface 1906 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 1900. 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 1908 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 1908 may further include power circuitry for delivering power from the power source 1908 itself, and / or an external power source, to the various parts of the UE 1900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1908 to make the power suitable for the respective components of the UE 1900 to which power is supplied. The memory 1910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1910 includes one or more application programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by the UE 1900, any of a variety of various operating systems or combinations of operating systems. The memory 1910 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 1910 may allow the UE 1900 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 1910, which may be or comprise a device-readable storage medium. The processing circuitry 1902 may be configured to communicate with an access network or other network using the communication interface 1912. The communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922. The communication interface 1912 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 1918 and / or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., the antenna 1922) and may share circuit components, software, or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 1912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1912, 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 IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1900 shown in Figure 19. As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. 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. It is noted that the functionality of the UE described above (e.g., with respect to Figures 9-16) may be implemented by the UE 1700. Figure 20 shows a network node 2000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS). Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self- Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The network node 2000 includes processing circuitry 2002, memory 2004, a communication interface 2006, and a power source 2008. The network node 2000 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 2000 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 2000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 2000. The processing circuitry 2002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 2000 components, such as the memory 2004, to provide network node 2000 functionality. In some embodiments, the processing circuitry 2002 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of Radio Frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units. The memory 2004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 2002. The memory 2004 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 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and / or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and the memory 2004 are integrated. The communication interface 2006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 2006 comprises port(s) / terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. The communication interface 2006 also includes radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, the antenna 2010. The radio front-end circuitry 2018 comprises filters 2020 and amplifiers 2022. The radio front-end circuitry 2018 may be connected to the antenna 2010 and the processing circuitry 2002. The radio front-end circuitry 2018 may be configured to condition signals communicated between the antenna 2010 and the processing circuitry 2002. The radio front-end circuitry 2018 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 2018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 2020 and / or the amplifiers 2022. The radio signal may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface 2006 may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 2000 does not include separate radio front- end circuitry 2018; instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes the one or more ports or terminals 2016, the radio front- end circuitry 2018, and the RF transceiver circuitry 2012 as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown). The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through an interface or port. The antenna 2010, the communication interface 2006, and / or the processing circuitry 2002 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 2000. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 2010, the communication interface 2006, and / or the processing circuitry 2002 may be configured to perform any transmitting operations described herein as being performed by the network node 2000. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment. The power source 2008 provides power to the various components of the network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2008. As a further example, the power source 2008 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 2000 may include additional components beyond those shown in Figure 20 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2000. It is noted that the functionality of the network node or gNB described above (e.g., with respect to Figures 9-16) may be implemented by the network node 2000. In this regard, the network node 2000 may be a multi-TRP network node (e.g., a gNB having multiple TRPs). Figure 21 is a block diagram of a host 2100, which may be an embodiment of the host 1816 of Figure 18, in accordance with various aspects described herein. As used herein, the host 2100 may be or comprise various combinations of hardware and / or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 2100 may provide one or more services to one or more UEs. The host 2100 includes processing circuitry 2102 that is operatively coupled via a bus 2104 to an input / output interface 2106, a network interface 2108, a power source 2110, and memory 2112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 19 and 20, such that the descriptions thereof are generally applicable to the corresponding components of the host 2100. The memory 2112 may include one or more computer programs including one or more host application programs 2114 and data 2116, which may include user data, e.g. data generated by a UE for the host 2100 or data generated by the host 2100 for a UE. Embodiments of the host 2100 may utilize only a subset or all of the components shown. The host application programs 2114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 2114 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 2100 may select and / or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 2114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc. Figure 22 is a block diagram illustrating a virtualization environment 2200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 2200 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 2200 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 2202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 2200 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 2204 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 2206 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 2208A and 2208B (one or more of which may be generally referred to as VMs 2208), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 2206 may present a virtual operating platform that appears like networking hardware to the VMs 2208. The VMs 2208 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 2206. Different embodiments of the instance of a virtual appliance 2202 may be implemented on one or more of the VMs 2208, 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 2208 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 2208, and that part of the hardware 2204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 2208, 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 2208 on top of the hardware 2204 and corresponds to the application 2202. The hardware 2204 may be implemented in a standalone network node with generic or specific components. The hardware 2204 may implement some functions via virtualization. Alternatively, the hardware 2204 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 2210, which, among others, oversees lifecycle management of the applications 2202. In some embodiments, the hardware 2204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 2212 which may alternatively be used for communication between hardware nodes and radio units. Figure 23 shows a communication diagram of a host 2302 communicating via a network node 2304 with a UE 2306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 1812A of Figure 18 and / or the UE 1900 of Figure 19), the network node (such as the network node 1810A of Figure 18 and / or the network node 2000 of Figure 20), and the host (such as the host 1816 of Figure 18 and / or the host 2100 of Figure 21) discussed in the preceding paragraphs will now be described with reference to Figure 23. Like the host 2100, embodiments of the host 2302 include hardware, such as a communication interface, processing circuitry, and memory. The host 2302 also includes software, which is stored in or is accessible by the host 2302 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 2306 connecting via an OTT connection 2350 extending between the UE 2306 and the host 2302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2350. The network node 2304 includes hardware enabling it to communicate with the host 2302 and the UE 2306. The connection 2360 may be direct or pass through a core network (like the core network 1806 of Figure 18) 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 2306 includes hardware and software, which is stored in or accessible by the UE 2306 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 2306 with the support of the host 2302. In the host 2302, an executing host application may communicate with the executing client application via the OTT connection 2350 terminating at the UE 2306 and the host 2302. 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 2350 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 2350. The OTT connection 2350 may extend via the connection 2360 between the host 2302 and the network node 2304 and via a wireless connection 2370 between the network node 2304 and the UE 2306 to provide the connection between the host 2302 and the UE 2306. The connection 2360 and the wireless connection 2370, over which the OTT connection 2350 may be provided, have been drawn abstractly to illustrate the communication between the host 2302 and the UE 2306 via the network node 2304, 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 2350, in step 2308, the host 2302 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 2306. In other embodiments, the user data is associated with a UE 2306 that shares data with the host 2302 without explicit human interaction. In step 2310, the host 2302 initiates a transmission carrying the user data towards the UE 2306. The host 2302 may initiate the transmission responsive to a request transmitted by the UE 2306. The request may be caused by human interaction with the UE 2306 or by operation of the client application executing on the UE 2306. The transmission may pass via the network node 2304 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2312, the network node 2304 transmits to the UE 2306 the user data that was carried in the transmission that the host 2302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2314, the UE 2306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2306 associated with the host application executed by the host 2302. In some examples, the UE 2306 executes a client application which provides user data to the host 2302. The user data may be provided in reaction or response to the data received from the host 2302. Accordingly, in step 2316, the UE 2306 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 2306. Regardless of the specific manner in which the user data was provided, the UE 2306 initiates, in step 2318, transmission of the user data towards the host 2302 via the network node 2304. In step 2320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2304 receives user data from the UE 2306 and initiates transmission of the received user data towards the host 2302. In step 2322, the host 2302 receives the user data carried in the transmission initiated by the UE 2306. One or more of the various embodiments improve the performance of OTT services provided to the UE 2306 using the OTT connection 2350, in which the wireless connection 2370 forms the last segment. More precisely, the teachings of these embodiments may improve, e.g., data rate, latency, and / or power consumption and thereby provide benefits such as, e.g., reduced user waiting time, related restriction on file size, improved content resolution, better responsiveness, and / or extended battery lifetime. In an example scenario, factory status information may be collected and analyzed by the host 2302. As another example, the host 2302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2302 may store surveillance video uploaded by a UE. As another example, the host 2302 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 2302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data. In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2350 between the host 2302 and the UE 2306 in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 2350 may be implemented in software and hardware of the host 2302 and / or the UE 2306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2350 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 2304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 2302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2350 while monitoring propagation times, errors, etc. It is noted that the functionality of the network node or gNB described above (e.g., with respect to Figures 9-16) may be implemented in the network node 2304, and the functionality of the UE described above (e.g., with respect to Figures 9-16) may be implemented in the UE 2306. In this regard, the network node 2304 may be a multi-TRP network node (e.g., a gNB having multiple TRPs). Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non- computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and a wireless network generally. Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein. In view of the above, example embodiments covered by the present disclosure include the following:

[0002] EMBODIMENTS Group A Embodiments 1. A method performed by a User Equipment, UE, the method comprising any one or more of the following: receiving (Fig.9, step 1) configuration information from a network node, wherein the configuration information configures the UE with a plurality of resource sets, resources, and / or downlink reference signals (e.g., NZP CSI-RS resource sets, NZP CSI-RS resources, TRS resource sets, TRSs, and / or downlink reference signals); receiving (Fig.9, step 2) configuration information from the network node that configures the UE to report one or more parameters (e.g., delay, delay offset, frequency, frequency offset, and / or derivative(s) of phase) based on measurements on all or a subset of the plurality of resource sets, resources, and / or downlink reference signals; selecting (Fig.9, step 4) all or a subset of the plurality of resource sets, resources, and / or downlink reference signals for which the UE is to compute and / or report the one or more parameters; computing (Fig.9, step 5) a parameter(s) (e.g., delay, delay offset, frequency, frequency offset, and / or derivative(s) of phase) for each selected resource set, resource, or downlink reference signal; and reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals. 2. The method of embodiment 1, wherein reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals comprises reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals in two parts comprising: a first part comprising information (e.g., a bitmap) that indicates which of the plurality of resource sets, resources, and / or downlink reference signals are selected; and a second part comprising information that indicates the computed parameter(s) for each of the selected resource sets, resources, and / or downlink reference signals. 3. The method of embodiment 1, wherein reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals comprises reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals in a single part (e.g., a single message) comprising: for each selected resource set, resource, or downlink reference signal, information (e.g., a valid value) that indicates the computed parameter(s) for the selected resource set, resource, or downlink reference signal; and for each non-selected resource set, resource, or downlink reference signal from among the plurality of resource sets, resources, and / or downlink reference signal configured for the UE, information (e.g., an invalid value) that indicates that the non-selected resource set, resource, or downlink reference signal is not selected. 4. The method of embodiment 1, wherein reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals comprises reporting (Fig.9, step 6) the computed parameters for the selected resource sets, resources, and / or downlink reference signals in a single message (e.g., a single MAC message) comprising: information (e.g., a bitmap) that indicates which of the plurality of resource sets, resources, and / or downlink reference signals are selected; and information that indicates the computed parameter(s) for each of the selected resource sets, resources, and / or downlink reference signals. 5. The method of any of embodiments 1 to 4, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of NZP CSI-RS resource sets each comprising at least one NZP CSI-RS resource. 6. The method of any of embodiments 1 to 4, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of NZP CSI-RS resources. 7. The method of any of embodiments 1 to 6, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of TRS resource sets each comprising at least one TRS resource. 8. The method of any of embodiments 1 to 6, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of TRSs. 9. The method of any of embodiments 1 to 8, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of downlink reference signals. 10. The method of any of embodiments 1 to 9, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise propagation delays. 11. The method of any of embodiments 1 to 10, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise propagation delay differences. 12. The method of any of embodiments 1 to 11, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise frequencies. 13. The method of any of embodiments 1 to 12, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise frequency offsets. 14. The method of any of embodiments 1 to 13, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise phases. 15. The method of any of embodiments 1 to 14, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise phase differences. 16. The method of any of embodiments 1 to 15, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise one or more derivates of phases. 17. The method of any of embodiments 1 to 16, wherein the configuration information received from the network node configures the UE to report two or more parameters, and the same resource sets, resources, and / or downlink reference signals that the UE is to use to compute the two or more parameters are selected for all of the two or more parameters. 18. The method of any of embodiments 1 to 16, wherein the configuration information received from the network node configures the UE to report two or more parameters, and the different resource sets, resources, and / or downlink reference signals are selected for at least two of the two or more parameters. 19. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Group B Embodiments 20. A method performed by a network node, the method comprising one or more of the following: transmitting (Fig.15, step 1) configuration information to a User Equipment, UE, wherein the configuration information configures the UE with a plurality of resource sets, resources, and / or downlink reference signals (e.g., NZP CSI-RS resource sets, NZP CSI-RS resources, TRS resource sets, TRSs, and / or downlink reference signals); transmitting (Fig.15, step 2) configuration information to the UE that configures the UE to report one or more parameters (e.g., delay, delay offset, frequency, frequency offset, and / or derivative(s) of phase) based on measurements on all or a subset of the plurality of resource sets, resources, and / or downlink reference signals; and receiving (Fig.15, step __), from the UE, a report comprising computed parameters for one or more selected resource sets, resources, and / or downlink reference signals, the one or more selected resource sets, resources, and / or downlink references being all or a subset of the plurality of resource sets, resources, and / or downlink reference signals configured for the UE. 21. The method of embodiment 20, wherein the report comprises two parts comprising: a first part comprising information (e.g., a bitmap) that indicates which of the plurality of resource sets, resources, and / or downlink reference signals are selected; and a second part comprising information that indicates the computed parameter(s) for each of the selected resource sets, resources, and / or downlink reference signals. 22. The method of embodiment 20, wherein the report comprises a single part (e.g., a single message) comprising: for each selected resource set, resource, or downlink reference signal, information (e.g., a valid value) that indicates the computed parameter(s) for the selected resource set, resource, or downlink reference signal; and for each non-selected resource set, resource, or downlink reference signal from among the plurality of resource sets, resources, and / or downlink reference signal configured for the UE, information (e.g., an invalid value) that indicates that the non-selected resource set, resource, or downlink reference signal is not selected. 23. The method of embodiment 20, wherein receiving the report comprises receiving the report in a single message (e.g., a single MAC message) comprising: information (e.g., a bitmap) that indicates which of the plurality of resource sets, resources, and / or downlink reference signals are selected; and information that indicates the computed parameter(s) for each of the selected resource sets, resources, and / or downlink reference signals. 24. The method of any of embodiments 20 to 23, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of NZP CSI-RS resource sets each comprising at least one NZP CSI-RS resource. 25. The method of any of embodiments 20 to 23, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of NZP CSI-RS resources. 26. The method of any of embodiments 20 to 25, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of TRS resource sets each comprising at least one TRS resource. 27. The method of any of embodiments 20 to 25, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of TRSs. 28. The method of any of embodiments 20 to 27, wherein the plurality of resource sets, resources, and / or downlink reference signals comprise a plurality of downlink reference signals. 29. The method of any of embodiments 20 to 28, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise propagation delays. 30. The method of any of embodiments 20 to 29, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise propagation delay differences. 31. The method of any of embodiments 20 to 30, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise frequencies. 32. The method of any of embodiments 20 to 31, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise frequency offsets. 33. The method of any of embodiments 20 to 32, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise phases. 34. The method of any of embodiments 20 to 33, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise phase differences. 35. The method of any of embodiments 20 to 34, wherein the one or more parameters computed and reported for the selected resource sets, resources, and / or downlink reference signals comprise one or more derivates of phases. 36. The method of any of embodiments 20 to 35, wherein the configuration information configures the UE to report two or more parameters, and the same resource sets, resources, and / or downlink reference signals that the UE used to compute the two or more parameters are selected for all of the two or more parameters. 37. The method of any of embodiments 20 to 36, wherein the configuration information received from the network node configures the UE to report two or more parameters, and the different resource sets, resources, and / or downlink reference signals are selected and used by the UE to compute at least two of the two or more parameters. 38. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Embodiments 39. A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. 40. A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry. 41. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. 42. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 43. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. 44. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 45. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. 46. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. 47. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE. 48. The communication system of the previous embodiment, further comprising: the network node; and / or the UE. 49. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host. 50. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 51. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 52. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. 53. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host. 54. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host. 55. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host. 56. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 57. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host. 58. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application. 59. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 60. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host. 61. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. 62. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 63. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host. 64. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 65. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Claims

Claims 1. A method performed by a User Equipment, UE (1812; 1900; 2306), the method comprising: receiving (1610) first configuration information from a network node (1810; 2000; 2304), wherein the first configuration information configures the UE (1812; 1900; 2306) with a plurality of Non-Zero Power, NZP, Channel State Information Reference Signal, CSI-RS, resource sets; receiving (1620) second configuration information from the network node, wherein the second configuration information configures the UE (1812; 1900; 2306) to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets; selecting (1640) all or a subset of the plurality of NZP CSI-RS resource sets for which the UE (1812; 1900; 2306) is to report the one or more parameters; computing (1650) the one or more parameters for each selected NZP CSI-RS resource set; and reporting (1660) the computed parameters for the selected NZP CSI-RS resource sets, wherein said reporting (1660) the computed parameters for the selected NZP CSI-RS resource sets comprises reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE (1812; 1900; 2306), information that indicates that the non-selected NZP CSI-RS resource set is not selected.

2. The method of claim 1, wherein said reporting (1660) the computed parameters for the selected NZP CSI-RS resource sets is accomplished in a single message.

3. The method of claim 1 or 2, wherein the plurality of NZP CSI-RS resource sets each comprise at least one NZP CSI-RS resource.

4. The method of any one of claims 1 to 3, wherein said reporting (1640) the computed parameters for the selected NZP CSI-RS resource sets comprises reporting a bit field for each of the NZP CSI-RS resource sets.

5. The method of claim 4, wherein for each selected NZP CSI-RS resource set the bit field represents a respectivevalue of the one or more parameters; and wherein for each non-selected NZP CSI-RS resource set the bit field represents a reserved value indicating that the NZP CSI-RS resource set is not selected.

6. The method of claim 5, wherein quantized values of the one or more parameters are mapped to codepoints of the bit field, and wherein a reserved codepoint of the bit field indicates that the NZP CSI-RS resource set is not selected.

7. The method of claim 6, wherein the mapping of the codepoints to the quantized values is predefined.

8. The method of claim 6 or 7, wherein the reserved codepoint is predefined.

9. The method of any of claims 6 to 8, wherein the UE (1812; 1900; 2306) is configured to report two or more parameters for each of the selected NZP CSI-RS sets and quantized values of the two or more parameters are mapped to one codepoint of the bit field.

10. The method of any of claims 1 to 9, wherein the one or more parameters computed and reported for the selected NZP CIS-RS resource sets comprise propagation delays.

11. The method of any of claims 1 to 10, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise propagation delay differences.

12. The method of to claim 11, wherein the propagation delay differences are with respect to a reference NZP CSI-RS resource set.

13. The method of any of claims 1 to 12, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise frequencies.

14. The method of any of claims 1 to 13, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise frequency differences.

15. The method of claim 14, wherein the frequency differences are with respect to a reference NZP CSI-RS resource set.

16. The method of any of claims 1 to 15, wherein the second configuration information configures the UE (1812; 1900; 2306) to report two or more parameters, and the same NZP CSI- RS resource sets are selected for all of the two or more parameters.

17. The method of any of embodiments 1 to 16, wherein the second configuration information configures the UE (1812; 1900; 2306) to report two or more parameters, and the NZP CSI-RS resource sets selected for at least two of the two or more parameters are different.

18. A method performed by a network node (1810; 2000; 2304), the method comprising one or more of the following: transmitting (1710) first configuration information to a User Equipment, UE (1812; 1900; 2306), wherein the first configuration information configures the UE (1812; 1900; 2306) with a plurality of Non-Zero Power, NZP, Channel State Information Reference Signal, CSI-RS, resource sets; transmitting (1720) second configuration information to the UE(1812; 1900; 2306), wherein the second configuration information configures the UE (1812; 1900; 2306) to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI- RS resource sets; and receiving (1730), from the UE (1812; 1900; 2306), a report comprising computed parameters for one or more selected NZP CSI-RS resource sets, the one or more selected NZP CSI-RS resource sets being all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE (1812; 1900; 2306), wherein the report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE (1812; 1900; 2306), information that indicates that the non-selected NZP CSI-RS resource set is not selected.

19. The method of claim 18, wherein receiving the report comprises receiving the report in a single message.

20. The method of claim 18 or 19, wherein the plurality of NZP CSI-RS resource sets each comprise at least one NZP CSI-RS resource.

21. The method of any one of claims 18 to 20, wherein the report comprises a bit field for each of the NZP CSI-RS resource sets.

22. The method of claim 21, wherein for each selected NZP CSI-RS resource set the bit field represents a respective value of the one or more parameters; and wherein for each non-selected NZP CSI-RS resource set the bit field represents a reserved value indicating that the NZP CSI-RS resource set is not selected.

23. The method of claim 22, wherein quantized values of the one or more parameters are mapped to codepoints of the bit field, and wherein a reserved codepoint of the bit field indicates that the NZP CSI-RS resource set is not selected.

24. The method of claim 23, wherein the mapping of the codepoints to the quantized values is predefined.

25. The method of claim 23 or 24, wherein the reserved codepoint is predefined.

26. The method of any of claims 23 to 25, wherein second configuration information configures the UE to report two or more parameters for each of the selected NZP CSI-RS set and quantized values of the two or more parameters are mapped to one codepoint of the bit field.

27. The method of any of claims 18 to 26, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise propagation delays.

28. The method of any of claims 18 to 29, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise propagation delay differences.

29. The method of claim 28, wherein the propagation delay differences are differences with respect to a reference NZP CSI-RS resource set.

30. The method of any of claims 18 to 29, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise frequencies.

31. The method of any of claims 18 to 30, wherein the one or more parameters computed and reported for the selected NZP CSI-RS resource sets comprise frequency differences.

32. The method of claim 14, wherein the frequency differences are differences with respect to a reference NZP CSI-RS resource set.

33. The method of any of claims 18 to 32, wherein the second configuration information configures the UE to report two or more parameters, and the same NZP CSI-RS resource sets are selected for all of the two or more parameters.

34. The method of any of claims 18 to 33, wherein the second configuration information configures the UE to report two or more parameters, and the NZP CSI-RS resource sets selected for at least two of the two or more parameters are different.

35. A user equipment, UE (1812; 1900; 2306), configured to: receive first configuration information from a network node (1810; 2000; 2304), wherein the first configuration information configures the UE (1812; 1900; 2306) with a plurality of Non- Zero Power, NZP, Channel State Information Reference Signal, CSI-RS, resource sets; receive second configuration information from the network node, wherein the second configuration information configures the UE (1812; 1900; 2306) to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets; select all or a subset of the plurality of NZP CSI-RS resource sets for which the UE (1812; 1900; 2306) is to report the one or more parameters; compute the one or more parameters for each selected NZP CSI-RS resource set; and report the computed parameters for the selected NZP CSI-RS resource sets, by reporting: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE (1812; 1900; 2306),information that indicates that the non-selected NZP CSI-RS resource set is not selected.

36. The UE (1812; 1900; 2306) of claim 35, further configured to perform a method according to any of claims 2 to 17.

37. The UE (1812; 1900; 2306) of claim 35 or 36, comprising: processing circuitry (1902) configured to perform the steps of the method according to any of claims 1 to 17; and power supply circuitry (1908) configured to supply power to the processing circuitry (1902).

38. A network node (1810; 2000; 2304), configured to: transmit first configuration information to a User Equipment, UE (1812; 1900; 2306), wherein the first configuration information configures the UE (1812; 1900; 2306) with a plurality of Non-Zero Power, NZP, Channel State Information Reference Signal, CSI-RS, resource sets; transmit second configuration information to the UE (1812; 1900; 2306), wherein the second configuration information configures the UE (1812; 1900; 2306) to report one or more parameters based on measurements on all or a subset of the plurality of NZP CSI-RS resource sets; and receive, from the UE (1812; 1900; 2306), a report comprising computed parameters for one or more selected NZP CSI-RS resource sets, the one or more selected NZP CSI-RS resource sets being all or a subset of the plurality of NZP CSI-RS resource sets configured for the UE (1812; 1900; 2306), wherein the report comprises: for each selected NZP CSI-RS resource set, information that indicates the computed one or more parameters for the selected NZP CSI-RS resource set; and for each non-selected NZP CSI-RS resource set configured for the UE (1812; 1900; 2306), information that indicates that the non-selected NZP CSI-RS resource set is not selected.

39. The network node (1810; 2000; 2304) of claim 38, further configured to perform a method according to any of claims 19 to 34.

40. The network node (1810; 2000; 2304) of claim 38 or 39, comprising: processing circuitry (2002) configured to perform the steps of the method according to any of claims 18 to 34; andpower supply circuitry (2008) configured to supply power to the processing circuitry (2002).

41. A computer program or computer program product comprising instructions to be executed by processing circuitry of a User Equipment, UE (1812; 1900; 2306), whereby execution of the instructions causes the UE (1812; 1900; 2306) to perform a method according to any of claims 1 to 17.

42. A computer program or computer program product comprising instructions to be executed by processing circuitry of a network node (1810; 2000; 2304), whereby execution of the instructions causes the network node (1810; 2000; 2304) to perform a method according to any of claims 18 to 34.

Images