EP4662823A1

EP4662823A1 - Multi burst trs measurement configuration

Info

Publication number: EP4662823A1
Application number: EP24704370.6A
Authority: EP
Inventors: Per ERNSTRÖM; Siva Muruganathan; Fredrik Athley; Jianwei Zhang
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-07
Filing date: 2024-02-07
Publication date: 2025-12-17
Also published as: WO2024165612A1; CN120660311A

Abstract

A method, system and apparatus are disclosed. According to some embodiments, a network node is configured to configure a wireless device to perform a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst, cause transmission of the first TRS burst and the second TRS burst where the first TRS burst is one of aperiodic and periodic and where the second TRS burst is one of aperiodic and periodic, and receive an indication of the TDCP measurement that is based on the configuration and the first and second TRS bursts.

Description

MULTI BURST TRS MEASUREMENT CONFIGURATION FIELD The present disclosure relates to wireless communications, and in particular, to multi-burst tracking reference signal (TRS) TRS measurement configurations. BACKGROUND The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks. Multi User-Multiple Input Multiple Output (MU-MIMO) With MU-MIMO, two or more users (e.g., wireless devices) in the same cell are co-scheduled on the same time-frequency resource(s). That is, two or more independent data streams are transmitted to different wireless devices at the same time, and the spatial domain can typically be used to separate the respective streams. By transmitting several streams simultaneously, the capacity of the system can be increased. This, however, comes at the cost of reducing the signal to interference-plus noise ration (SINR) per stream, as the power must be shared between streams and the streams may cause interference with each-other. Channel State Information Reference Signals (CSI-RS) For CSI measurement and feedback, CSI-RS is defined. A CSI-RS is transmitted on each antenna port and is used by a wireless device to measure a downlink channel between each of the transmit antenna ports and each of its receive antenna ports. The transmit antenna ports are also referred to as CSI-RS ports. The supported number of antenna ports in NR are {1, 2, 4, 8, 12, 16, 24, 32}. By measuring the received CSI-RS, a wireless device can estimate the channel that the CSI-RS is traversing, including the radio propagation channel and antenna gains. The CSI-RS for the above purpose is also referred to as Non-Zero Power (NZP) CSI-RS. CSI-RS can be configured to be transmitted in certain resource elements (REs) in a slot and certain slots. FIG.1 is a diagram of an example of CSI-RS REs for 12 antenna ports, where 1RE per resource block (RB) per port is shown. In addition, interference measurement resource (IMR) is also defined in NR for a wireless device to measure interference. An IMR resource contains 4 REs, either 4 adjacent REs in frequency in the same OFDM symbol or 2 by 2 adjacent REs in both time and frequency in a slot. By measuring both the channel based on NZP CSI- RS and the interference based on an IMR, a wireless device can estimate the effective channel and noise plus interference to determine the CSI, i.e. rank, precoding matrix, and the channel quality. Furthermore, a wireless device in NR may be configured to measure interference based on one or multiple NZP CSI-RS resources. Tracking Reference Signal (TRS) Due to oscillator imperfections, transmission and reception may not be synchronized in time and/or frequency, which can cause inter- and intra-symbol interference. In NR, tracking reference signal (TRS) was introduced that can be used by the wireless device for fine time/frequency synchronization. In NR 3GPP specifications, TRS can be configured when CSI report setting is not configured or when the higher layer parameter ‘reportQuantity’ in the CSI- ReportConfig information element (IE), associated with all the report settings linked with the CSI-RS resource set containing the TRS(s) is set to ‘none’. This means that CSI reporting based on measurements on TRS is not supported in NR. TRS is configured via ‘trs-Info’ in the NZP-CSI-RS-ResourceSet information element (IE) of 3GPP Technical Specification (TS) 38.331 which is associated with a CSI-RS resource set, for which the wireless device can assume that the antenna port with the same port index of the configured NZP CSI-RS resources in the resource set is the same. From a 3GPP specifications perspective, TRS is specified as a special kind of NZP CSI-RS where the corresponding NZP CSI-RS resource set containing the TRS(s) has a higher layer parameter ‘trs-info’ set to true. TRS is not really a CSI-RS, rather it is a resource set consisting of multiple periodic NZP CSI-RS. More specifically, a TRS consists of four one-port, density-3 CSI-RSs located within two consecutive slots. The CSI-RS within the resource set, can be configured with a periodicity of 10, 20, 40, or 80 ms. Note that the exact set of REs used for the TRS CSI-RS may vary. There may be a four-symbol time-domain separation between the two CSI-RS within a slot. FIG.2 is a diagram of an example of a TRS burst of 2 TRS symbols in 2 adjacent slots. NR also supports aperiodic TRS. For LTE, the cell-specific reference signal (CRS) served the same purpose as the TRS as LTE CRS can be used for synchronization but it can also be used for CSI reporting, which is not supported for TRS in NR. However, compared to the LTE CRS, the TRS in NR implies much less overhead, only having one antenna port and only being present in two slots every TRS period. FIG.3 is a diagram of configurability of TRS symbol positions and TRS burst periodicity. CSI framework in NR In NR, a wireless device can be configured with multiple CSI reporting settings and multiple CSI-RS resource settings. Each resource setting can contain multiple resource sets, and each resource set can contain up to 8 CSI-RS resources. For each CSI reporting setting, a wireless device feeds back a CSI report. Each CSI reporting setting contains at least the following information: • A CSI-RS resource set for channel measurement • An IMR resource set for interference measurement • Optionally, a CSI-RS resource set for interference measurement • Time-domain behavior, i.e. periodic, semi-persistent, or aperiodic reporting • Frequency granularity, i.e. wideband or subband • CSI parameters to be reported such as RI, PMI, CQI, and CSI-RS resource indicator (CRI) in case of multiple CSI-RS resources in a resource set • Codebook types, i.e. Type I or II, and codebook subset restriction • Measurement restriction • Subband size. One out of two possible subband sizes is indicated, the value range depends on the bandwidth of the BWP. One CQI/PMI (if configured for subband reporting) is fed back per subband). Type 1 and type 2 codebooks in NR Type 1 codebook (CB) is typically used by a wireless device to report CSI for single user MIMO (SU-MIMO) scheduling in NR. While type 2 CB is typically for more accurate CSI feedback for multi-user MIMO (MU-MIMO) scheduling. For both type 1 and type 2 CBs, for each rank, a precoding matrix ^ is defined in the form of ^ = ^_^^_^ matrix and contains information of L selected DFT beams {^_^ , ^ = ^, … , where ^_^ is a Nx1 DFT vector and N is the number of CSI-RS ports per polarization; while ^_^ is a 2^ × ^ matrix and contains the co-phasing coefficients between the selected beams and also between antenna ports with two different polarizations, where ^ is the number of layers or rank. is the same for the whole CSI bandwidth while ^_^ can be for the whole bandwidth or per subband. In case of type 1 CB, the precoding vector for each MIMO layer is associated with a single DFT beam. While for type 2 CB, the precoding vector for each layer is a linear combination of multiple DFT beams. Enhanced Type 2 codebook in NR In NR Rel-16, type 2 CB is enhanced by applying a frequency domain (FD) DFT basis across all subbands to reduced CSI feedback overhead and/or improve CSI accuracy. Instead of reporting ^_^ for each subband, linear combinations of DFT basis vectors are used to jointly represent ^_^ across the whole CSI bandwidth. For each layer, a precoding matrix ^ across all subbands is in the form of ^ = ^_^^^ ^ ^^_^ Where ^_^ = [^_^, … , ^_^] is a matrix containing M selected DFT basis vectors {^_^ , … , ^_^} , ^^_^ is 2L x M matrix containing the coefficients for each selected DFT beam and each selected FD basis vector. QCL and TCI states Several signals can be transmitted from different antenna ports of a same network node (e.g., base station). These signals can have the same large-scale properties such as Doppler shift/spread, average delay spread, or average delay. These antenna ports are then referred to be quasi co-located (QCL). If the wireless device knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the wireless device can estimate that parameter based on one of the antenna ports and apply that estimate for receiving signal on the other antenna port. Typically, the first antenna port is represented by a measurement reference signal such as TRS or SSB (known as source RS) and the second antenna port is a demodulation reference signal (DMRS) (known as target RS). For instance, if antenna ports A and B are QCL with respect to average delay, the wireless device can estimate the average delay from the signal received from antenna port A and assume that the signal received from antenna port B has the same average delay. This may be useful for demodulation since the wireless device can know beforehand the properties of the channel, which for instance helps the wireless device in selecting an appropriate channel estimation filter. Information about what assumptions can be made regarding QCL is signaled to the wireless device from the network node. In NR, four types of QCL relations between a transmitted source RS and transmitted target RS were defined: Type A: {Doppler shift, Doppler spread, average delay, delay spread} Type B: {Doppler shift, Doppler spread} Type C: {average delay, Doppler shift} Type D: {Spatial Rx parameter} Aperiodic CSI-RS/IM and CSI reporting For both aperiodic CSI-RS/IM resources and aperiodic CSI reports, the triggering is performed jointly by transmitting a DCI with Format 0_1 from the network node to the wireless device, using the downlink control channel, PDCCH. This is the DCI format which schedules PUSCH transmission where the aperiodic CSI report is to be carried. The DCI with Format 0_1 contains a CSI request field which can be configured to be between 0 and 6 bits wide using higher layer configuration (i.e., RRC) from network node to wireless device. The CSI request field can thus contain at most ^_^ = 2^{^} = 64 codepoints. If this field is set to all zeros, no CSI is requested, and the DCI format 0_1 only schedules a regular PUSCH transmission containing UL data. A non-zero codepoint on the other hand points to a so-called aperiodic trigger state configured by RRC from network node to wireless device. An aperiodic trigger state is defined as a list of up to at most 16 aperiodic CSI Report Settings, each identified by a CSI Report Setting ID, (but typically, a much lower number of report settings is used) for which the wireless device simultaneously may calculate CSI for and include in the scheduled PUSCH transmission. If a CSI Report Setting is linked with periodic/semi-persistent Resource Setting(s), no further information is needed since there is only one Resource Set included in the Resource Setting for channel/interference measurement in this case. However, if the CSI Report Setting is linked with an aperiodic Resource Setting (which can comprise multiple Resource Sets), which CSI-RS/IM Resource set should be used for measurement must be indicated in DCI Format 0_1. Hence, this allows the network node, for a given CSI Report Setting, to dynamically switch which CSI-RS/IM resource is to be used for measurement each time the aperiodic report is triggered by DCI with Format 0_1, by configuring by RRC and indicating by DCI Format 0_1 different aperiodic trigger states. This means that the aperiodic NZP CSI- RS Resource Set for channel measurement, the aperiodic CSI-IM Resource Set for interference measurement (if used) and the aperiodic NZP CSI-RS Resource Set for interference measurement (if used) to use for a given CSI Report Setting is also included in the aperiodic trigger state definition. For aperiodic NZP CSI-RS, the QCL source to use (i.e., the TCI state) is also configured in the aperiodic trigger state, which enables the network node to dynamically switch wireless device Rx beam assumptions for the reception of the NZP CSI-RS. FIG.4 is a diagram of example aperiodic trigger states and mapping from a DCI codepoint. It is possible to configure up to 128 aperiodic trigger states via radio resource control (RRC). However, the number of codepoints of the CSI request bitfield in DCI Format 0_1 only ranges between 0-63. Therefore, it is possible that more trigger states are configured in RRC than can be indicated with the DCI field. When this is the case, i.e., ^ aperiodic trigger states are configured in RRC but the CSI request bitfield (with bitwidth ^_^^ = 0, … ,6) only contains ^_^ = 2^{^^^} − 1 < ^ non-zero codepoints, an intermediary sub-selection, or mapping, between the ^_^ codepoints and the ^ RRC configured trigger states needs to be performed. This sub-selection is performed by transmitting a MAC CE sub-selection command. The aperiodic CSI-RS/IM is a one-shot measurement which is only present for a single time instance and is only used to determine CSI for a single aperiodic report. The position, in time, of the aperiodic CSI-RS/IM is defined as a slot offset relative to the slot where the DCI containing the trigger was received. The slot offset is defined on a CSI-RS resource set level and the offset allows the wireless device to use some time to complete the CSI measurements and calculation of the reports, and prepare the uplink transmission of the reports. For aperiodic CSI-IM, there is no explicit slot offset defined but rather it is assumed that the CSI-IM and CSI-RS is present in the same slot to enable efficient CSI processing at the wireless device. Channel correlation, Doppler spectrum, and Jakes Model The wireless channel ℎ⁽^⁾ between a network node and a wireless device can change over time as the wireless device moves. This is typically because the signals received at the wireless device comprise many paths of radio waves reflected from objects (such as trees and buildings) surrounding the wireless device, where each path has a different angle of arrival (AOA) at the wireless device and thus a different Doppler frequency as the wireless device moves. When the AOAs of the paths are uniformly distributed over [ -^, ^] in the azimuth direction, it is known that the Doppler power spectrum for the channel ℎ(^) can be modeled using the Jakes model (i.e., in two dimensions) as follows: The autocorrelation of the channel is defined as ^_^^(^) = ^[ℎ(^)ℎ^∗(^ + ^)]. The normalized autocorrelation ^_^^ ⁽^⁾/^_^^(0) =^_^ ⁽2^ ∙ τ ∙ ^_^^^ ⁾, which is the inverse Fourier transform of ^⁽^⁾, where ^_^ ⁽·⁾ is the zeroth order Bessel function of the first kind, ^[∙] denotes expectation. FIG.5 is a diagram of an example of the zeroth order Bessel function of the first kind. The y-axis shows the autocorrelation and the x-axis shows 2^ ∙ τ ∙ ^_^^^). It can be seen that it is monotonic only for when 2^ ∙ τ ∙ ^_^^^ < 3.8317, and within that range and for a given ^, there is a one-to-one mapping between a correlation value and an ^_^^^ . 3GPP Rel-18 specification of TRS based TDCP reporting In RAN1#109e meeting, the following was considered: The work scope of TRS-based TDCP reporting focuses on the following use cases for evaluation purposes: - Targeting medium and high wireless device speed, e.g.10-120km/h as well as HST speed - Aiding network node to determine - CSI reporting configuration and CSI-RS resource configuration parameters, - Precoding scheme, using one of the CSI feedback based precoding schemes or an UL-SRS reciprocity based precoding scheme - Aiding network node-side CSI prediction. As discussed above, there are several use cases for the network node to know the TDCP (time domain channel properties) based on TRS measurements. One use case for TDCP reporting is to enable the network node to select a transmission scheme that is more robust to channel ageing when the channel varies fast. For instance, based on the TRS-based TDCP reported by the wireless device to the network node, the network node may need to decide whether the precoder for the wireless device should be based on CSI obtained from uplink measurements or from CSI feedback obtained from the wireless device. Another example is that the network node may need to decide whether the precoder to schedule the wireless device should be based on Type I CSI feedback obtained from the wireless device or Type II CSI feedback obtained from the wireless device. FIGS.6a-6b are example diagrams of illustrating examples mean user throughput for a particular scheme relative to the mean throughput for feedback-based SU-MIMO precoding (the baseline). In particular, this figure illustrates relative mean user throughput vs. wireless devices speed for reciprocity-based and feedback-based CSI where FIG.6a illustrates 16 network node antenna ports, and FIG.6b illustrates 32 network node antenna ports.. The throughput is calculated for a traffic load corresponding to 70% resource utilization for the baseline case at each wireless devices speed. Results for both single user (SU)-MIMO and MU-MIMO are shown in FIGs.6a-6b. The scenario is UMa with 500 m inter-site distance. The carrier frequency is 2 GHz and the subcarrier spacing is 15 kHz. The CSI periodicity is 20 ms for both feedback and reciprocity-based CSI. The results show that reciprocity- based precoding has better performance at 3 km/h for both SU-MIMO and MU- MIMO. However, at wireless device speeds around 10 km/h the feedback-based precoding has better performance. Hence, the feedback-based precoding is more robust to rapidly varying channels. A speed of 10 km/h corresponds to a channel coherence time which is longer than two slots. FIGs.7a-7b are diagrams of example comparisons of the performance of precoding based on Type I and Type II CSI, respectively. The results show that Type II CSI provides better performance at 3 km/h but at wireless device speeds around 10 km/h and higher, type I provides better performance. These results show that it could be beneficial to select precoding scheme based on some parameter that is related to the wireless device speed. It is noted that it is not the wireless device speed per se that is the fundamental parameter in this context. Rather, it is how fast the channel varies which depends on the wireless device speed and also on the angle between the wireless device velocity vector and the propagation paths seen or experienced from the wireless device. Therefore, selection of precoding scheme based on some time domain channel property such as coherence time or autocorrelation may be a more suitable parameter. Wireless device measurement and reporting of time domain correlation based on TRS samples across different time lags is an efficient way to report TDCP based on TRS. In order to define the time domain correlation measurement across TRS samples, let ^_^ ^[^^], ^ = 0,1, … , ^ − 1 be the received frequency domain TRS samples after matched filtering and after removing the reference signal sequence. Index ^ denotes the different OFDM symbols carrying the TRSs used for the correlation estimation. Note that the TRSs used for the correlation estimation may be located in the same or different slots. The starting point in time of the OFDM symbol ^ is given by ^_^ (to be precise ^_^ denotes the start of the non-CP part of the OFDM symbol). Index n denote TRS sample index (assumed to be proportional to subcarrier index). Let ^_^ ⁽^⁾, ^ = 1 … ^, ^ = 1,2 be the ^-indices of ^ symbol pairs to use for the estimation of the correlation for a delay ^ = ^_^^(^) − ^_^^(^). It is assumed that the ^ symbol pairs are separated by the same distance in time. In one example, a low-complexity estimate of the normalized time domain correlation for a delay ^ is calculated in the frequency domain as In another example, the inverse DFT is calculated for each OFDM symbol ^: ^_^ ^[^^] = ^^^^⁽^_^ ^[^^]) The estimate of the normalized correlation for time delay ^ is calculated as where the sum over time samples is over sets Γ⁽^⁾ defined to suppress noise, e.g. by using a noise threshold such as e.g. where ^_^^(^) are noise estimates. Note that at low speeds the change in the channel is small and the change in correlation at different delays within a TRS burst is quite small (note that the TRS burst is defined in FIG.2). Within a TRS burst, correlation can be measured for delays of 4 symbol, 10 symbol, 14 symbol, and 18 symbols as shown in FIG.8. In particular, FIG.8 illustrates an example of delays ^_^ for which the correlation can be estimated based on intra TRS burst measurements using the TRS signal. Note that for = 4 ∙ ^_^^^^^^^ and for ^_^ = ^_^^^^ = 14 ∙ ^_^^^^^^^ there are two samples the TRS burst that can be used for the measurement, while for ^_^ = 18 ∙ ^_^^^^^^^ and ^_^ = 10 ∙ ^_^^^^^^^ there is only one sample within the TRS burst that can be used for the measurement. As the change in correlation at different delays within a TRS burst is quite small for low velocities, intra TRS burst measurements are not enough to distinguish between different velocities in the low velocity region. Therefore, support for measuring and reporting correlation for time delays corresponding to multiple TRS bursts is needed. CSI configuration signaling In 3GPP TS38.331, the information elements for CSI-RS-ResourceMapping, CSI-FrequencyOccupation, CSI-ResourcePeriodicityAndOffset are defined as follows: – CSI-RS-ResourceMapping The IE CSI-RS-ResourceMapping is used to configure the resource element mapping of a CSI-RS resource in time- and frequency domain. CSI-RS-ResourceMapping information element -- ASN1START -- TAG-CSI-RS-RESOURCEMAPPING-START CSI-RS-ResourceMapping ::= SEQUENCE { frequencyDomainAllocation CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)), row4 BIT STRING (SIZE (3)), other BIT STRING (SIZE (6)) }, nrofPorts ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32}, firstOFDMSymbolInTimeDomain INTEGER (0..13), firstOFDMSymbolInTimeDomain2 INTEGER (2..12) OPTIONAL, -- Need R cdm-Type ENUMERATED {noCDM, fd-CDM2, cdm4-FD2- TD2, cdm8-FD2-TD4}, density CHOICE { dot5 ENUMERATED {evenPRBs, oddPRBs}, one NULL, three NULL, spare NULL }, freqBand CSI-FrequencyOccupation, ... } -- TAG-CSI-RS-RESOURCEMAPPING-STOP -- ASN1STOP

CSI-RS-ResourceMapping field descriptions cdm-Type CDM type (see 3GPP TS 38.214, clause 5.2.2.3.1). density Density of CSI-RS resource measured in RE/port/PRB (see 3GPP TS 38.211, clause 7.4.1.5.3). Values 0.5 (dot5), 1 (one) and 3 (three) are allowed for X=1, values 0.5 (dot5) and 1 (one) are allowed for X=2, 16, 24 and 32, value 1 (one) is allowed for X=4, 8, 12. For density = 1/2, includes 1-bit indication for RB level comb offset indicating whether odd or even RBs are occupied by CSI-RS. firstOFDMSymbolInTimeDomain2 Time domain allocation within a physical resource block. See 3GPP TS 38.211, clause 7.4.1.5.3. firstOFDMSymbolInTimeDomain Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS. See 3GPP TS 38.211, clause 7.4.1.5.3. freqBand Wideband or partial band CSI-RS, (see 3GPP TS 38.214, clause 5.2.2.3.1). frequencyDomainAllocation Frequency domain allocation within a physical resource block in accordance with 3GPP TS 38.211, clause 7.4.1.5.3. The applicable row number in table 7.4.1.5.3-1 is determined by the frequencyDomainAllocation for rows 1, 2 and 4, and for other rows by matching the values in the column Ports, Density and CDMtype in table 7.4.1.5.3-1 with the values of nrofPorts, cdm-Type and density below and, when more than one row has the 3 values matching, by selecting the row where the column (k bar, l bar) in table 7.4.1.5.3-1 has indexes for k ranging from 0 to 2*n-1 where n is the number of bits set to 1 in frequencyDomainAllocation. nrofPorts Number of ports (see 3GPP TS 38.214, clause 5.2.2.3.1). - CSI-FrequencyOccupation The IE CSI-FrequencyOccupation is used to configure the frequency domain occupation of a channel state information measurement resource (e.g., NZP-CSI-RS- Resource, CSI-IM-Resource). CSI-FrequencyOccupation information element -- ASN1START -- TAG-CSI-FREQUENCYOCCUPATION-START CSI-FrequencyOccupation ::= SEQUENCE { startingRB INTEGER (0..maxNrofPhysicalResourceBlocks-1), nrofRBs INTEGER (24..maxNrofPhysicalResourceBlocksPlus1), ... } -- TAG-CSI-FREQUENCYOCCUPATION-STOP -- ASN1STOP CSI-FrequencyOccupation field descriptions nrofRBs Number of PRBs across which this CSI resource spans. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 24 and the width of the associated BWP. If the configured value is larger than the width of the corresponding BWP, the UE shall assume that the actual CSI-RS bandwidth is equal to the width of the BWP. startingRB PRB where this CSI resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. Only multiples of 4 are allowed (0, 4, ...) - CSI-ResourcePeriodicityAndOffset The IE CSI-ResourcePeriodicityAndOffset is used to configure a periodicity and a corresponding offset for periodic and semi-persistent CSI resources, and for periodic and semi-persistent reporting on PUCCH. both, the periodicity and the offset are given in number of slots. The periodicity value slots4 corresponds to 4 slots, value slots5 corresponds to 5 slots, and so on. CSI-ResourcePeriodicityAndOffset information element -- ASN1START -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-START CSI-ResourcePeriodicityAndOffset ::= CHOICE { slots4 INTEGER (0..3), slots5 INTEGER (0..4), slots8 INTEGER (0..7), slots10 INTEGER (0..9), slots16 INTEGER (0..15), slots20 INTEGER (0..19), slots32 INTEGER (0..31), slots40 INTEGER (0..39), slots64 INTEGER (0..63), slots80 INTEGER (0..79), slots160 INTEGER (0..159), slots320 INTEGER (0..319), slots640 INTEGER (0..639) } -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-STOP -- ASN1STOP Discussion of 3GPP TS 38.214 on TRS The description for TRS (i.e., CSI-RS for tracking) is provided in 3GPP TS 38.214 as shown below: 5.1.6.1.1 CSI-RS for tracking A wireless device in RRC connected mode is expected to receive the higher layer wireless device specific configuration of an NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info. For an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the wireless device assumes the antenna port with the same port index of the configured NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet is the same. - For frequency range 1, the wireless device may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet consists of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. If no two consecutive slots are indicated as downlink slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigDedicated, then the wireless device may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet consists of two periodic NZP CSI-RS resources in one slot. - For frequency range 2, the wireless device may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet consists of two periodic CSI-RS resources in one slot or with a NZP-CSI-RS-ResourceSet of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. A wireless device configured with NZP-CSI-RS-ResourceSet(s) configured with higher layer parameter trs-Info may have the CSI-RS resources configured as: - Periodic, with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with same periodicity, bandwidth and subcarrier location. - Periodic CSI-RS resource in one set and aperiodic CSI-RS resources in a second set, with the aperiodic CSI-RS and periodic CSI-RS resource having the same bandwidth (with same RB location) and the aperiodic CSI-RS being configured with qcl-Type set to 'typeA' and 'typeD', where applicable, with the periodic CSI-RS resources. For frequency range 2, the wireless device does not expect that the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources is smaller than beamSwitchTiming + d ∙ 2^{^^^^^^}/2^{^^^^^^} in CSI-RS symbols, where beamSwitchTiming is wireless device reported value defined in 3GPP TS 38.306, the reported value is one of the values of {14, 28, 48}∙ 2^{^^^(^,^^^^^^^^)}, and the beam switching timing delay d is defined in Table 5.2.1.5.1a-1 if µPDCCH < µCSIRS , else d is zero. The wireless device expects that the periodic CSI-RS resource set and aperiodic CSI-RS resource set are configured with the same number of CSI-RS resources and with the same number of CSI-RS resources in a slot. For the aperiodic CSI-RS resource set if triggered, and if the associated periodic CSI-RS resource set is configured with four periodic CSI- RS resources with two consecutive slots with two periodic CSI-RS resources in each slot, the higher layer parameter aperiodicTriggeringOffset indicates the triggering offset for the first slot for the first two CSI-RS resources in the set. A wireless device does not expect to be configured with a CSI-ReportConfig that is linked to a CSI-ResourceConfig containing an NZP-CSI-RS-ResourceSet configured with trs-Info and with the CSI-ReportConfig configured with the higher layer parameter timeRestrictionForChannelMeasurements set to 'configured'. A wireless device does not expect to be configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to other than 'none' for aperiodic NZP CSI-RS resource set configured with trs-Info. A wireless device does not expect to be configured with a CSI-ReportConfig for periodic NZP CSI-RS resource set configured with trs-Info. A wireless device does not expect to be configured with an NZP-CSI-RS- ResourceSet configured both with trs-Info and repetition. Each CSI-RS resource, defined in Clause 7.4.1.5.3 of 3GPP TS 38.211, is configured by the higher layer parameter NZP-CSI-RS-Resource with the following restrictions: - the time-domain locations of the two CSI-RS resources in a slot, or of the four CSI-RS resources in two consecutive slots (which are the same across two consecutive slots), as defined by higher layer parameter CSI-RS-resourceMapping, is given by - ...for frequency range 1 and frequency range 2, - ...for frequency range 2. - a single port CSI-RS resource with density given by Table 7.4.1.5.3-1 from 3GPP TS 38.211 and higher layer parameter density configured by CSI-RS- ResourceMapping. - if carrier = 52, = 52, ^ = 0 and the carrier is configured in paired spectrum, the bandwidth of the CSI-RS resource, as given by the higher layer parameter freqBand configured by CSI-RS-ResourceMapping, is X resource blocks, where ^ ≥ 28 resource blocks if the wireless device indicates trs- AddBW-Set1 for the trs-AdditionalBandwidth capability for CSI-RS for tracking or addBW-Set1 for the aperiodicCSI-RS-AdditionalBandwidth capability for aperiodic CSI-RS for fast SCell activation and ^ ≥ 32 if the wireless device indicates trs- AddBW-Set2 for the AdditionalBandwidth capability for CSI-RS for tracking or addBW-Set2 for the aperiodicCSI-RS-AdditionalBandwidth capability for aperiodic CSI-RS for fast SCell activation; in these cases, if the wireless device is configured with CSI-RS comprising X<52 resource blocks, the wireless device does not expect that the total number of PRBs allocated for DL transmissions but not overlapped with the PRBs carrying CSI-RS for tracking is more than 4, where all CSI-RS resource configurations shall span the same set of resource blocks; otherwise, the bandwidth of the CSI-RS resource, as given by the higher layer parameter freqBand configured by CSI-RS-ResourceMapping, is the minimum of 52 and N size B_WP,i resource blocks, or is equal to N size B_WP,i resource blocks. For operation with shared spectrum channel access in FR1, freqBand configured by CSI-RS-ResourceMapping, is the minimum of 48 and N size B_WP,i resource blocks, or is equal to resource blocks. - the wireless device is not expected to be configured with the periodicity of X slots if the bandwidth of CSI-RS resource is larger than 52 resource blocks. - the periodicity and slot offset for periodic NZP CSI-RS resources, as given by the higher layer parameter periodicityAndOffset configured by NZP-CSI-RS- Resource, is one of Y slots where Y is 10, 20, 40, or 80 and where µ is defined in Clause 4.3 of 3GPP TS 38.211. - same powerControlOffset and powerControlOffsetSS given by NZP- CSI-RS-Resource value across all resources. … Aperiodic CSI-RS for tracking for fast SCell activation A wireless device can be configured with aperiodic CSI-RS resources for tracking for an SCell for fast SCell activation using NZP-CSI-RS-ResourceSet(s) with the higher layer parameter scellActivationRS-ConfigToAddModList, with the QCL relation, provided by higher layer parameter qcl-Info given by SCellActivationRS- Config as with aperiodic CSI-RS for tracking in clause 5.1.6.1.1 (of 3GPP TS 38.214). Each CSI-RS resource, defined in clause 7.4.1.5.3 of 3GPP TS 38.211, for fast SCell activation is configured by the higher layer parameter NZP-CSI-RS- Resource with the same restrictions as defined for CSI-RS for tracking in clause 5.1.6.1.1. In existing NR specifications, the minimum supported periodicity of TRS is 10ms, which may not provide adequate autocorrelation for TDCP measurements. Accordingly, there is a need for techniques which allow for adequately performing TDCP measurements based on TRS. It is an object of the present disclosure to address such need. SUMMARY Some embodiments advantageously provide methods, systems, and apparatuses for multi-burst tracking reference signal (TRS) TRS measurement configurations. In one or more embodiments, different ways of configuring TRS measurement resources are proposed for computing autocorrelation values smaller than 10ms, as described herein. According to an embodiment, a method implemented by a wireless device (WD) is provided. The method comprises receiving a configuration for performing a time-domain channel properties (TDCP) measurement based on a first tracking reference signal (TRS) burst and a second TRS burst. Further, the method comprises receiving the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, the method comprises performing the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. According to a further embodiment, a method implemented by a network node is provided. The method comprises configuring a WD to perform a TDCP measurement based on a first TRS burst and a second TRS burst. Further, the method comprises causing transmission of the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, the method comprises receiving an indication of the TDCP measurement that is based on the configuration and the first TRS burst and second TRS burst. According to a further embodiment, a WD is provided. The WD is configured to receive a configuration for performing a TDCP measurement based on a first TRS burst and a second TRS burst. Further, the WD is configured to receive the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, the WD is configured to perform the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. According to a further embodiment, a WD is provided. The WD comprises processing circuitry and a memory storing instructions to be executed by the processing circuitry. Execution of the instructions by the processing circuitry causes the WD to receive a configuration for performing a TDCP measurement based on a first TRS burst and a second TRS burst. Further, execution of the instructions by the processing circuitry causes the WD to receive the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, execution of the instructions by the processing circuitry causes the WD to perform the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. According to a further embodiment, a network node is provided. The network node is configured to configure a WD to perform a TDCP measurement based on a first TRS burst and a second TRS burst. Further, the network node is configured to cause transmission of the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, the network node is configured to receive an indication of the TDCP measurement that is based on the configuration and the first TRS burst and second TRS burst. According to a further embodiment, a network node is provided. The network node comprises processing circuitry and a memory storing instructions to be executed by the processing circuitry. Execution of the instructions by the processing circuitry causes the network node to configure a WD to perform a TDCP measurement based on a first TRS burst and a second TRS burst. Further, execution of the instructions by the processing circuitry causes the network node to cause transmission of the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, execution of the instructions by the processing circuitry causes the network node to receive an indication of the TDCP measurement that is based on the configuration and the first TRS burst and second TRS burst. According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises computer-executable instructions that, when executed by the processing circuitry of a WD, cause the WD to receive a configuration for performing a TDCP measurement based on a first TRS burst and a second TRS burst. Further, execution of the instructions by the processing circuitry causes the WD to receive the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, execution of the instructions by the processing circuitry causes the WD to perform the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. According to a further embodiment, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises computer-executable instructions that, when executed by the processing circuitry of a network node, cause the network node to configure a WD to perform a TDCP measurement based on a first TRS burst and a second TRS burst. Further, execution of the instructions by the processing circuitry causes the network node to cause transmission of the first TRS burst and the second TRS burst. The first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Further, execution of the instructions by the processing circuitry causes the network node to receive an indication of the TDCP measurement that is based on the configuration and the first TRS burst and second TRS burst. BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG.1 is a diagram of an example RE allocation for a 12-port CSI-RS in NR; FIG.2 is a diagram of an example of RE allocation for a TRS burst with 2 TRS symbols in 2 adjacent slots; FIG.3 is a diagram of configurability of TRS symbol positions and TRS burst periodicity; FIG.4 is a diagram of an example aperiodic trigger states and mapping from a DCI codepoint; FIG.5 is a diagrams of a zeroth order Bessel function of the first kind; FIG.6a-6b are diagrams of examples of relative mean user throughput versus wireless device speed for reciprocity-based and feedback-based CSI; FIG.7a-7b are diagrams of a comparison of the performance of precoding based on Type I and Type I CSI. FIG.8 is a diagram of delays for which the correlation can be estimated based on intra TRS burst measurements using the TRS signal. FIG.9 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure; FIG.10 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure; FIG.11 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure; FIG.12 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure; FIG.13 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure; FIG.14 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure; FIG.15 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure; FIG.16 is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure; FIG.17 is a diagram of one embodiment of the present disclosure; FIG.18 is a diagram of an example of two bursts of periodic TRSs used for periodic TDCP measurement according to some embodiments of the present disclosure; FIG.19 is a diagram of an example of using two bursts of periodic TRSs used for aperiodic TDCP measurements according to some embodiments of the present disclosure; FIG.20 is a diagram of an example of using aperiodic TDCP measurement based on one periodic TRS and one aperiodic TRS according to some embodiments of the present disclosure; and FIG.21 is a diagram of an example aperiodic TDCP measurement based on two aperiodic TRSs according to some embodiments of the present disclosure. DETAILED DESCRIPTION As discussed above, in existing NR specifications, the minimum supported periodicity of TRS is 10ms. However, for TDCP measurements, autocorrelation may need to be computed for delay values much smaller than 10ms. One option is to reduce the periodicity of TRS to a value much smaller than 10ms. This will increase the TRS overhead and is not a suitable solution as TDCP measurements may not be triggered very frequently. Hence, how to support TDCP measurements using smaller delay values (delay values much smaller than 10ms) without increasing the TRS overhead is an existing problem. One or more embodiments described herein solves at least in part the problem with existing systems by providing different ways of configuring TRS measurement resources are proposed for computing autocorrelation values smaller than 10ms, as described herein. Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to multi-burst tracking reference signal (TRS) TRS measurement configurations. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description. As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections. The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node. In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc. Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or to one or both of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Some embodiments provide multi-burst tracking reference signal TRS measurement configurations. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG.9 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16. Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN. The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown). The communication system of FIG.9 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24. A network node 16 is configured to include a configuration unit 32 which is configured to perform one or more network node 16 functions as described herien such as with respect to multi-burst tracking reference signal TRS measurement configurations. A wireless device 22 is configured to include a measurement unit 34 which is configured to perform one or more wireless device 22 functions as described herien such as with respect to multi-burst tracking reference signal TRS measurement configurations. Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG.10. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to perform one or more of receive, transmit, forward, relay, process, store, analyze, etc. information related to multi-burst tracking reference signal TRS measurement configurations. The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10. In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include configuration unit 32 configured to perform one or more network node 16 functions as described herein such as with respect to multi-burst tracking reference signal TRS measurement configurations. The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides. The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a measurement unit 34 configured to one or more wireless device 22 functions as described herein such as with respect to multi-burst tracking reference signal TRS measurement configurations. In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG.10 and independently, the surrounding network topology may be that of FIG.9. In FIG.10, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, 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 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc. Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22. In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16. Although FIGS.9 and 10 show various “units” such as configuration unit 32, and measurement unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. FIG.11 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS.9 and 10, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG.10. In a first step of the method, the host computer 24 provides user data (Block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S104). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108). FIG.12 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG.9, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS.9 and 10. In a first step of the method, the host computer 24 provides user data (Block S110). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S112). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block S114). FIG.13 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG.9, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS.9 and 10. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block S116). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S118). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126). FIG.14 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG.9, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS.9 and 10. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132). FIG.15 is a flowchart of an exemplary process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configuration to configure (Block S134) a wireless device 22 to perform a time- domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS burst, and a second TRS burst, as described herein. Network node 16 is configured to cause (Block S136) transmission of the first TRS burst and the second TRS burst where the first TRS burst is one of aperiodic and periodic, and the second TRS burst is one of aperiodic and periodic. Network node 16 is configuration to receive (Block S138) an indication of the TDCP measurement that is based on the configuration and the first and second TRS bursts. According to one or more embodiments, the TDCP measurement is configured for a lag of a number of slots based on the first TRS burst and the second TRS burst. The number of slots may be predefined or configured, e.g., by RRC signaling. The number of slots corresponding to the lag is herein also denoted as L. According to one or more embodiments, the first TRS burst has a periodicity of P slots and a slot offset of S slots, where the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots, and where the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. According to one or more embodiments, the first TRS burst has a periodicity of P slots and a slot offset of S slots where the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots, and where the TDCP measurement being configured for a lag of L slots. According to one or more embodiments, the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. According to one or more embodiments, the first TRS burst is a periodic TRS, where the second TRS burst is an aperiodic TRS, and where the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. According to one or more embodiments, the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. According to one or more embodiments, the first and second TRS bursts are an aperiodic TRS, and where the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. According to one or more embodiments, the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. According to one or more embodiments, the first TRS burst and the second TRS burst are transmitted from a same antenna port. According to one or more embodiments, resources of the first TRS burst and resources of the second TRS burst are quasi-collocated. According to one or more embodiments, resources of the first TRS burst and resources of the second TRS burst have same time-domain indices and same subcarrier indices. According to one or more embodiments, the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets, and as part of a same NZP CSI- RS resource set. FIG.16 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the measurement unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 is configured to receive (Block S140) a configuration for performing time- domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst, as described herein. Wireless device 22 is configured to receive (Block S142) the first TRS burst and the second TRS burst where the first TRS burst is one of aperiodic and periodic and the second TRS burst is one of aperiodic and periodic, as described herein. Wireless device 22 is configured to perform (Block S144) the TDCP measurement based on the configuration and the first and second TRS bursts. According to one or more embodiments, the TDCP measurement is configured for a lag of a number of slots based on the first TRS burst and the second TRS burst. The number of slots may be predefined or configured, e.g., by RRC signaling. The number of slots corresponding to the lag is herein also denoted as L. According to one or more embodiments, the first TRS burst has a periodicity of P slots and a slot offset of S slots where the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots, and where the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. According to one or more embodiments, the first TRS burst has a periodicity of P slots and a slot offset of S slots where the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots, and where the TDCP measurement is configured for a lag of L slots. According to one or more embodiments, the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. According to one or more embodiments, the first TRS burst is a periodic TRS where the second TRS burst is an aperiodic TRS and where the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots. According to one or more embodiments, the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. According to one or more embodiments, the first and second TRS bursts are an aperiodic TRS and where the TDCP measurement is an aperiodic TDCP measurement that is configured for lag of L slots. According to one or more embodiments, the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. According to one or more embodiments, the first TRS burst and the second TRS burst are assumed to be transmitted from a same antenna port. According to one or more embodiments, resources of the first TRS burst and resources of the second TRS burst are assumed to be quasi-collocated. According to one or more embodiments, resources of the first TRS burst and resources of the second TRS burst have same time-domain indices and same subcarrier indices. According to one or more embodiments, the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets, and as part of a same NZP CSI- RS resource set. Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for multi-burst tracking reference signal TRS measurement configurations. Some embodiments provide for multi-burst tracking reference signal TRS measurement configurations. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, configuration unit 32, etc. One or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, measurement unit 34, etc. General Description of Some Embodiments Periodic TDCP measurement based on periodic TRSs (Embodiment 1) ^ Configure two TRS’s: o TRS 1 with periodicity P slots and slot offset S slots o TRS 2 with periodicity N*P slots and slot offset S+L slots ^ Configure a periodic TDCP measurement for a lag of L slots with periodicity Q*P based on TRS 1 and TRS 2. FIG.17 is a diagram of an example of Embodiment 1. Aperiodic TDCP measurement based on periodic TRSs (Embodiment 2) ^ Configure two TRS’s: o TRS 1 with periodicity P slots and slot offset S slots o TRS 2 with periodicity Q*P slots and slot offset S+L slots ^ Configure an aperiodic TDCP measurement for a lag of L slots ^ Trigger the aperiodic TDCP measurement for next TRS2 occasion Aperiodic TDCP measurement based on one periodic TRS and one aperiodic TRS (Embodiment 3) ^ Configure one periodic TRS ^ Configure one aperiodic TRS ^ Configure an aperiodic TDCP measurement for a lag of L slots ^ Trigger o one TRS bursts separated by L slots relative one occasion of the periodic TRS o a TDCP measurement for a lag of L slots based on the aperiodic TRS bursts triggered and the occasion of the periodic TRS, separated from the aperiodic TRS burst by L slots Aperiodic TDCP measurement based on aperiodic TRSs (Embodiment 4) ^ Configure an aperiodic TRS ^ Configure an aperiodic TDCP measurement for a lag of L slots ^ Trigger o two TRS bursts separated in time by L slots o a TDCP measurement for a lag of L slots based on the two TRS bursts triggered Embodiment 1: Periodic TDCP measurement based on periodic TRSs In this embodiment, periodic TDCP measurements are made based on two bursts of periodic TRSs. An example of using two bursts of periodic TRSs used for periodic TDCP measurements is shown in FIG.18. In FIG.18, TRS1 represents the first TRS burst consisting of four TRS resources in two consecutive slots (note that in NR, the four TRS resources are four NZP CSI-RS resources in an NZP-CSI-RS-Resource set with ‘trs-info’ configured to value ‘true’ as defined in 3GPP standards such as, for example, 3GPP TS 38.331 V17.3.0). Although FIG.18 shows the first TRS burst TRS1 that extends across 2 consecutive slots, in another case, the first TRS burst TRS1 may consists of two TRS resources within a single slot. All TRS resources within the first TRS burst are configured with periodicity ^ slots and slot offset ^ slots. TRS2 represents the second TRS burst consisting of four TRS resources in two slots. Although FIG.18 shows the second TRS burst TRS2 that extends across 2 consecutive slots, in another case, the second TRS burst TRS2 may consists of two TRS resources within a single slot. All TRS resources within the second TRS burst are configured with periodicity ^ × ^ slots and slot offset ^ + ^ slots, where ^ is a positive integer value. Note that the relative slot offset between TRS burst 1 and TRS burst 2 is given by ^ slots. In this embodiment, the wireless device 22 is configured to perform a periodic TDCP measurement for a delay ^ of ^ slots based on TRS1 and TRS2. When time domain correlation is used as the TDCP measurement, time domain correlation is computed using at least one of: ^ received frequency domain TRS samples ^_^^(^)[^], are measured from the first TRS burst TRS1; here, the time-domain sample index ^ = 1, … , ^, and subcarrier index ^ = 0, … , ^ − 1; and ^ received frequency domain TRS samples ^_^^(^) ^[^^], are measured from the second TRS burst TRS2; here, the time-domain sample index ^ = 1, … , ^, and subcarrier index ^ = 0, … , ^ − 1. In one embodiment, the delay value ^ = ^ to be used for computing time domain correlation may be explicitly configured in the CSI reporting configuration. In some other embodiments, the delay value ^ = ^ may be implicitly given by the relative slot offset between the first TRS burst and the second TRS burst (e.g., the relative slot offset between the first TRS resource in the first TRS burst and the first TRS resource in the second TRS burst). In another embodiment, the periodic TDCP measurements are performed every ^ × ^ slots. The periodicity of TDCP measurements may be explicitly configured in the CSI reporting configuration (e.g., CSI-ReportConfig) or CSI resource configuration (CSI-ResourceConfig). Alternatively, the periodicity of TDCP measurements may be implicitly given by the periodicity of the second TRS burst TRS2. In another embodiment, the TRS resources in the first and the second TRS bursts are assumed to be transmitted from the same antenna port in order for the wireless device 22 to measure the autocorrelation corresponding to that antenna port at two different delay or lag values. Hence, the following restriction may be added to 3GPP TS 38.214 to support the TDCP measurement feature: - When two NZP-CSI-RS-ResourceSets are configured with the higher layer parameter trs-Info in a CSI-ResourceConfig, the wireless device shall or may assume the antenna port with the same port index of the configured NZP CSI-RS resources in the two NZP-CSI-RS-ResourceSets is the same”. In some other embodiments, the TRS resources in the first and the second TRS bursts are assumed to be quasi-collocated (i.e., they have the same quasi-collocation source reference signal). In one embodiment, the two different TRS bursts may be configured as different NZP-CSI-RS resource sets both containing higher layer parameter ‘trs-info’ set to true. Hence, the CSI-ResourceConfig (or alternatively CSI resource setting) may be configured with two periodic NZP CSI-RS resource sets corresponding to the first TRS burst and the second TRS burst. In NR up to release 17 (e.g., 3GPP Release 17), two NZP CSI-RS resource sets are only allowed for periodic CSI resource settings when the wireless device 22 is configured with higher layer parameter groupBasaedBeamReporting-r17. 3GPP TS 38.214 V17.4.0 (clause 5.2.1.2) has the following restriction: - For periodic and semi-persistent CSI Resource Settings, when the wireless device 22 is configured with groupBasedBeamReporting-r17, the number of CSI Resource Sets configured is S=2, otherwise the number of CSI-RS Resource Sets configured is limited to S=1. The groupBasedBeamReporting-r17 feature is used for layer 1 RSRP (L1- RSRP) calculations on the two NZP CSI-RS resource sets separately wherein the separate L1-RSRP calculations are reported in a group. To distinguish the periodic TDCP measurement feature from the ‘groupBasedBeamReporting-r17’ feature, a higher layer parameter ‘periodicTdcpReporting’ may be higher layer configured to the wireless device 22. This higher layer parameter may be configured in CSI-ReportConfig in one embodiment. In another embodiment, this higher layer parameter may be configured in the CSI-ResourceConfig information element or in the NZP CSI-RS resource set. The changes needed to support periodic TDCP reporting feature in 3GPP TS 38.214 described below: 5.2.1.2 Resource settings (from 3GPP TS 38.214 V17.4.0) Each CSI Resource Setting CSI-ResourceConfig contains a configuration of a list of S≥1 CSI Resource Sets (given by higher layer parameter csi-RS- ResourceSetList), where the list is comprised of references to either or both of NZP CSI-RS resource set(s) and SS/PBCH block set(s) or the list is comprised of references to CSI-IM resource set(s). Each CSI Resource Setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI Resource Settings linked to a CSI Report Setting have the same DL BWP. The time domain behavior of the CSI-RS resources within a CSI Resource Setting are indicated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the wireless device 22 is configured with groupBasedBeamReporting- r17 or configured with periodicTdcpReporting-r18, the number of CSI Resource Sets configured is S=2, otherwise the number of CSI-RS Resource Sets configured is limited to S=1. For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP, as given by BWP-id. When a wireless device 22 is configured with multiple CSI-ResourceConfigs consisting of the same NZP CSI-RS resource ID, the same time domain behavior shall or may be configured for the CSI-ResourceConfigs. When a wireless device 22 is configured with multiple CSI-ResourceConfigs consisting of the same CSI-IM resource ID, the same time-domain behavior shall be configured for the CSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting shall or may have the same time domain behavior. Embodiment 2: Aperiodic TDCP measurement based on periodic TRSs In this embodiment, aperiodic TDCP measurements are made based on two bursts of periodic TRSs. An example of using two bursts of periodic TRSs used for aperiodic TDCP measurements is shown in FIG.19. The configuration of the two periodic TRSs is the same as in Embodiment 1. However, the TDCP measurement is aperiodic in this embodiment, and is triggered via DCI (e.g., with format 0_1 or 0_2). As shown in FIG.19, in one embodiment, the DCI triggers an aperiodic TDCP measurement (e.g., autocorrelation with delay or lag value of ^ slots using TRS1 and TRS2), and the wireless device 22 measures the TDCP measurement for the next TRS1 occasion and next TRS2 occasion. In an alternative embodiment, the wireless device 22 may compute or update TDCP measurement every ^ × ^ slots, and report the computed/updated TDCP measurement once receiving the DCI trigger. The computed/updated TDCP measurement is reported in a PUSCH that is triggered by the DCI. To trigger aperiodic TDCP measurements, the CSI-AperiodicTriggerStateList information element in 3GPP TS 38.331 may be modified as described below and/or as indicated below in bold. The first TRS burst may be configured via the NZP CSI- RS resource set parameter resourceSet under CSI-AssociatedReportConfigInfo -> resourcesForChannel. The second TRS burst may be configured via the second NZP CSI-RS resource set parameter resourceSet2-r17 under CSI- AssociatedReportConfigInfo -> resourcesForChannel2-r17. Note that in NR rel-17 the parameter resourceSet2-r17 is configured for the Rel-17 groupBasedBeamReporting-r17 feature. However, different from other configurations of this feature, in one or more embodiments, the wireless device 22 is configured with higher layer parameter aperiodicTdcpReporting-r18 as shown below. Hence, when the parameter aperiodicTdcpReporting-r18 is configured, the wireless device 22 computes aperiodic TDCP measurement using the first TRS burst in AssociatedReportConfigInfo -> resourcesForChannel->resourceSet and the second TRS burst in CSI-AssociatedReportConfigInfo -> resourcesForChannel2-r17- >resourceSet2-r17. If the parameter aperiodicTdcpReporting-r18 is configured (e.g., set to ‘enabled’), the wireless device 22 does not compute aperiodic TDCP measurement and follows release 17 behavior (i.e., computing L1-RSRP on the resourceSet1 and resourceSet2) for group based beam reporting. In an alternative embodiment, instead of reusing AssociatedReportConfigInfo - > resourcesForChannel2-r17->resourceSet2-r17, a resource set specific to the second TRS burst may be separately configured. In one embodiment, qcl-info2-r17 is omitted when aperiodicTdcpReporting- r18 is set to enabled as TRS resources in resourceSet1 and resourceSet2 need to be quasi-collocated as described above. Hence, in this embodiment, TRS resources in both resourceSet1 and resourceSet2 follow quasi-collocation information provided by higher layer parameter qcl-info shown below. CSI-AperiodicTriggerStateList information element -- ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-START CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI- AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI- AssociatedReportConfigInfo, ..., [[ ap-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]] CSI-AssociatedReportConfigInfo ::= SEQUENCE { reportConfigId CSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE { resourceSet INTEGER (1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS- ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic }, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB- ResourceSetsPerConfig) }, csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM- ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ..., [[ resourcesForChannel2-r17 CHOICE { nzp-CSI-RS2-r17 SEQUENCE { resourceSet2-r17 INTEGER (1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig), qcl-info2-r17 SEQUENCE (SIZE(1..maxNrofAP- ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic csi-SSB-ResourceSet2-r17 INTEGER (1..maxNrofCSI-SSB- ResourceSetsPerConfigExt) } OPTIONAL, -- Cond NoUnifiedTCI csi-SSB-ResourceSetExt INTEGER (1..maxNrofCSI-SSB- ResourceSetsPerConfigExt) OPTIONAL -- Need R ]] [[ aperiodicTdcpReporting-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP -- ASN1STOP Embodiment 3: Aperiodic TDCP measurement based on one periodic TRS and one aperiodic TRS In this embodiment, aperiodic TDCP measurements are made based on one burst of periodic TRS and another burst of aperiodic TRS. An example of using one periodic TRS burst and one aperiodic TRS burst for aperiodic TDCP measurements is shown in FIG.20. The configuration of the periodic TRS burst TRS1 is the same as in Embodiment 1. However, the second TRS burst is aperiodic in this case and the TDCP measurement is also aperiodic in this embodiment. Both the second burst of TRS (e.g., TRS2) and the aperiodic TDCP measurement are triggered via DCI (e.g., with format 0_1 or 0_2). As shown in FIG.20, in one embodiment, the DCI triggers an aperiodic TDCP measurement (e.g., autocorrelation with delay or lag value of ^ slots using TRS1 and TRS2) along with the second TRS burst TRS2 which is aperiodic, and the wireless device 22 measures the TDCP measurement for the closest preceding TRS1 occasion and triggered aperiodic TRS2 occasion. The computed/updated TDCP measurement is reported in a PUSCH that is triggered by the DCI. Since the two TRS bursts have different time domain behavior (i.e., one periodic and the other aperiodic), in one embodiment two different CSI- ResourceConfig (i.e., CSI resource settings or CSI resource configurations) may need to be linked to one CSI-Report configuration as show below in the modified CSI- ReportConfig information element. This is because time domain behavior for TRS is defined at the CSI-Resource Config level. The first TRS burst corresponds to an NZP CSI-RS resource set configured in the CSI-ResourceConfig pointed to by the identifier resourcesForChannelMeasurement. The second TRS burst corresponds to an NZP CSI-RS resource set configured in the CSI-ResourceConfig pointed to by the identifier resourcesForChannelMeasurement2. CSI-ReportConfig information element -- ASN1START -- TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId, carrier ServCellIndex OPTIONAL, -- Need S resourcesForChannelMeasurement CSI-ResourceConfigId, resourcesForChannelMeasurement2 CSI-ResourceConfigId, OPTIONAL, -- Need R csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R … The changes needed to CSI-AperiodicTriggerStateList information element to enable this embodiment are similar to embodiment 2. Embodiment 4: Aperiodic TDCP measurement based on two aperiodic TRSs In this embodiment, aperiodic TDCP measurements are made based on two bursts of aperiodic TRSs. An example of using two aperiodic TRS bursts for aperiodic TDCP measurements is shown in FIG.21. In this embodiment, the first and second burst of TRSs (e.g., TRS1 and TRS2) and the aperiodic TDCP measurement are triggered via the same DCI (e.g., with format 0_1 or 0_2). As shown in FIG.21, in one embodiment, the DCI triggers an aperiodic TDCP measurement (e.g., autocorrelation with delay or lag value of ^ slots using TRS1 and TRS2) along with the first TRS burst TRS1 and second TRS burst TRS2. The wireless device 22 measures the TDCP measurement for the triggered aperiodic TRS1 and TRS2 occasions. The computed/updated TDCP measurement is reported in a PUSCH that is triggered by the DCI. Alternative embodiments for configuring TDCP measurements with Multiple TRS bursts/lags In previous embodiments, it is assumed that different TRS bursts are configured as part of different NZP CSI-RS resource sets. In an alternative embodiment, multiple TRS bursts corresponding to different delays (or lags) are configured within a single NZP CSI-RS resource set. In a first example, the two TRS bursts in FIG.18 are configured multiple NZP CSI-RS resources in a single NZP CSI- RS resource set with ‘trs-info’ set to true as follows: ^ One or more NZP CSI-RS resources corresponding to the first TRS burst (e.g., TRS1 in FIG.18) are configured with periodicity ^ slots and slot offset ^ slots. If the first TRS burst extends across two slots, then the NZP CSI-RS resources in the first slot of the first TRS burst will have slot offset ^ slots, and the NZP CSI-RS resources in the second slot of the first TRS burst will have slot offset ^ + 1 slots. ^ One or more NZP CSI-RS resources corresponding to the second TRS burst (e.g., TRS2 in FIG.18) are configured with periodicity ^ × ^ slots and slot offset ^ slots. If the second TRS burst extends across two slots, then the NZP CSI-RS resources in the first slot of the second TRS burst will have slot offset ^ + ^ slots, and the NZP CSI-RS resources in the second slot of the second TRS burst will have slot offset ^ + ^ + 1 slots. If each TRS burst extends across ^ > 2 slots, then this embodiment can be extended by configuring ^ > 2 groups of NZP CSI-RS resources where the slot offset of the NZP CSI-RS resources in the ^^{^^} , (^ = 1, 2, … , ^) group will be ^ + ^̈ + ^ slots. Note that each of the ^ groups may consist of one or more NZP CSI-RS resources. Here, the value of ^̈ depends on the TRS burst number (e.g., ^̈ = 0 for first TRS burst, and ^̈ = ^ for second TRS burst). In some embodiments, the delay or lag value ^ to be considered for TDCP measurement may be configured as part of the NZP CSI-RS resource set. In another embodiment, a flag parameter ‘tdcpMeasurement’ may be configured in the NZP CSI- RS resource set to distinguish the NZP CSI-RS resource set containing the TRS resources corresponding to multiple TRS bursts from other types of NZP CSI-RS resource sets (e.g., NZP CSI-RS resource sets containing NZP CSI-RS resources for CSI measurement/reporting). The above alternative embodiment can also be extended to the example in FIG.19. In another alternative embodiment, instead of configuring multiple CSI-RS resources or CSI-RS resource sets for different TRS burst and associating them with a TDCP report as described in Embodiment 1 throughout Embodiment 4, one (or multiple) additional lag/burst offset(s) is added to the TRS(CSI-RS) configuration such that only one CSI-RS resource or CSI-RS resource set is associated with TDCP measurement report. In one or more embodiments, for periodic/aperiodic TDCP measurement report associated with periodic TRS(s), the scenarios are similar as illustrated in Embodiments 1 and 2 except for the configuration part. In the example below, a PeriodicityAndOffset2 is added to the NZP-CSI-RS-ResourceSet IE. This alternative corresponds to the case where a single NZP CSI-RS resource is used for different TRS bursts where a different Periodicity and offset values are configured for each of the TRS bursts. In other words, different instances (or repetitions) of the same NZP CSI-RS resource are used to represent different TRS bursts. Example RRC configuration with change indicated in bold: -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic PeriodicityAndOffset2-r18 CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent ... } Another extension of this alternative embodiment of using a single NZP CSI- RS resource for representing different TRS bursts is to configure offset between the first and second TRS burst by adding TDCPAdditionalOffset parameter as described below, with the value being numerology dependent. -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic TDCPAdditionalOffset-r18 INTEGER (0..3) OPTIONAL, -- Cond PeriodicOrSemiPersistent ... } In another alternative embodiment, for aperiodic TDCP measurement report associated with aperiodic TRS, the scenarios are similar as illustrated in the FIGS.20 and 21 of Embodiments 3-4, respectively. In the example configuration below, aperiodicTriggeringOffset-r18 can be used to indicate the offset between first and second TRS bursts as indicated by the bold. NZP-CSI-RS-ResourceSet information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS- ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, repetition ENUMERATED { on, off } OPTIONAL, -- Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S trs-Info ENUMERATED {true} OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S ]], [[ pdc-Info-r17 ENUMERATED {true} OPTIONAL, -- Need R cmrGroupingAndPairing-r17 CMRGroupingAndPairing-r17 OPTIONAL, -- Need R aperiodicTriggeringOffset-r17 INTEGER (0..124) OPTIONAL, -- Need S aperiodicTriggeringOffsetL2-r17 INTEGER(0..31) OPTIONAL -- Need R ]] AperiodicTriggeringOffset-r18 INTEGER (0..7) OPTIONAL } CMRGroupingAndPairing-r17 ::= SEQUENCE { nrofResourcesGroup1-r17 INTEGER (1..7), pair1OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL, -- Need R pair2OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL -- Need R } NZP-CSI-RS-Pairing-r17 ::= SEQUENCE { nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7), nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7) -- TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP Other embodiments In one additional embodiment for Embodiment 1 throughout Embodiment 4, the two TRS (or CSI-RS) configurations associated with TDCP measurement are expected to have the same bandwidth (with same RB location) and power offset of NZP-CSI-RS RE to SSS RE. Hence, one or more embodiments provide a flexible way to trigger TDCP measurements at a desired delay or lag value. At the same time, one or more embodiments keep the TRS overhead low compared to existing solutions. Although the embodiments presented in the disclosure cover TDCP measurements with two TRS bursts separated by a slot offset L, the embodiments can be extended to cover TDCP measurements with more than two TRS bursts. For example, if S TRS bursts corresponding to different delay or lags are to be used for TDCP measurements, then S different NZP CSI-RS resource sets may be configured in some embodiments. Each of the S different NZP CSI-RS resource sets corresponding to different TRS bursts may be configured with a different slot offset value where the respective slot offset value corresponds to the delay or lag to be assumed for TDCP measurements. If S TRS bursts corresponding to different delay or lags are to be used for TDCP measurements, then S different groups of NZP CSI-RS resources within a single NZP CSI-RS resource set may be configured in another embodiment. Each of the S different groups of NZP CSI-RS resources corresponding to different TRS bursts may be configured with a different slot offset value where the respective slot offset value corresponds to the delay or lag to be assumed for TDCP measurements. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination. It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings. In view of the above, embodiments of the present disclosure include: Embodiment A1. A network node configured to communicate with a wireless device, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: configure a wireless device to perform a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; cause transmission of the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and receive an indication of the TDCP measurement that is based on the configuration and the first and second TRS bursts. Embodiment A2. The network node of Embodiment A1, wherein the TDCP measurement is configured for a lag of a predefined number of slots based on the first TRS burst and the second TRS burst. Embodiment A3. The network node of Embodiment A1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. Embodiment A4. The network node of Embodiment A1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; the TDCP measurement being configured for a lag of L slots. Embodiment A5. The network node of Embodiment A4, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. Embodiment A6. The network node of Embodiment A1, wherein the first TRS burst is a periodic TRS; the second TRS burst is an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. Embodiment A7. The network node of Embodiment A6, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. Embodiment A8. The network node of Embodiment A1, wherein the first and second TRS bursts are an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. Embodiment A9. The network node of Embodiment A8, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. Embodiment A10. The network node of any one of Embodiments A1-A9, wherein the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets; and as part of a same NZP CSI-RS resource set. Embodiment B1. A method implemented by a network node configured to communicate with a wireless device, the method comprising: configuring a wireless device to perform a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; causing transmission of the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and receiving an indication of the TDCP measurement that is based on the configuration and the first and second TRS bursts. Embodiment B2. The method of Embodiment B1, wherein the TDCP measurement is configured for a lag of a predefined number of slots based on the first TRS burst and the second TRS burst. Embodiment B3. The method of Embodiment B1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. Embodiment B4. The method of Embodiment B1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; the TDCP measurement being configured for a lag of L slots. Embodiment B5. The method of Embodiment B4, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. Embodiment B6. The method of Embodiment B1, wherein the first TRS burst is a periodic TRS; the second TRS burst is an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. Embodiment B7. The method of Embodiment B6, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. Embodiment B8. The method of Embodiment B1, wherein the first and second TRS bursts are an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. Embodiment B9. The method of Embodiment B8, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. Embodiment B10. The method of any one of Embodiments B1-B9, wherein the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets; and as part of a same NZP CSI-RS resource set. Embodiment C1. A wireless device configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive a configuration for performing a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; receive the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and perform the TDCP measurement based on the configuration and the first and second TRS bursts. Embodiment C2. The wireless device of Embodiment C1, wherein the TDCP measurement is configured for a lag of a predefined number of slots based on the first TRS burst and the second TRS burst. Embodiment C3. The wireless device of Embodiment C1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. Embodiment C4. The wireless device of Embodiment C1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; and the TDCP measurement being configured for a lag of L slots. Embodiment C5. The wireless device of Embodiment C4, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. Embodiment C6. The wireless device of Embodiment C1, wherein the first TRS burst is a periodic TRS; the second TRS burst is an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. Embodiment C7. The wireless device of Embodiment C6, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. Embodiment C8. The wireless device of Embodiment C1, wherein the first and second TRS bursts are an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. Embodiment C9. The wireless device of Embodiment C8, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. Embodiment C10. The wireless device of any one of Embodiments C1-C9, wherein the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets; and as part of a same NZP CSI-RS resource set. Embodiment D1. A method implemented by wireless device that is configured to communicate with a network node, the method comprising: receiving a configuration for performing a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; receiving the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and performing the TDCP measurement based on the configuration and the first and second TRS bursts. Embodiment D2. The method of Embodiment D1, wherein the TDCP measurement is configured for a lag of a predefined number of slots based on the first TRS burst and the second TRS burst. Embodiment D3. The method of Embodiment D1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. Embodiment D4. The method of Embodiment D1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; and the TDCP measurement being configured for a lag of L slots. Embodiment D5. The method of Embodiment D4, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. Embodiment D6. The method of Embodiment D1, wherein the first TRS burst is a periodic TRS; the second TRS burst is an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. Embodiment D7. The method of Embodiment D6, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. Embodiment D8. The method of Embodiment D1, wherein the first and second TRS bursts are an aperiodic TRS; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. Embodiment D9. The method of Embodiment D8, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. Embodiment D10. The method of any one of Embodiments D1-D9, wherein the first and second TRS bursts are configured one of: as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets; and as part of a same NZP CSI-RS resource set.

Claims

CLAIMS 1. A method implemented by wireless device (22; 22a, 22b), the method comprising: receiving (S140) a configuration for performing a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; receiving (S142) the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and performing (S144) the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. 2. The method of claim 1, wherein the TDCP measurement is configured for a lag of a number of slots based on the first TRS burst and the second TRS burst. 3. The method of claim 2, wherein the number of slots is configured by Radio Resource Control signaling. 4. The method of claim 1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. 5. The method of claim 1, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; and the TDCP measurement being configured for a lag of L slots. 6. The method of claim 5, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. 7. The method of claim 1, wherein the first TRS burst is periodic; the second TRS burst is aperiodic; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. 8. The method of claim 7, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. 9. The method of claim 1, wherein the first TRS burst and the second TRS burst are aperiodic; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. 10. The method of claim 9, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. 11. The method of any one of claims 1-10, wherein the first TRS burst and the second TRS burst are assumed to be transmitted from a same antenna port. 12. The method of any one of claims 1-11, wherein resources of the first TRS burst and resources of the second TRS burst are assumed to be quasi-collocated. 13. The method of any one of claims 1-11, wherein resources of the first TRS burst and resources of the second TRS burst have same time-domain indices and same subcarrier indices. 14. The method of any one of claims 1-13, wherein the first TRS burst and the second TRS burst are configured as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets. 15. The method of any one of claims 1-13, wherein the first TRS burst and the second TRS burst are configured as part of a same NZP CSI-RS resource set. 16. A method implemented by a network node (16; 16a, 16b, 16c), the method comprising: configuring (S134) a wireless device (22; 22a, 22b) to perform a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; causing (S136) transmission of the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and receiving (S138) an indication of the TDCP measurement that is based on the configuration and the first TRS burst and the second TRS burst. 17. The method of claim 16, wherein the TDCP measurement is configured for a lag of a number of slots based on the first TRS burst and the second TRS burst. 18. The method of claim 17, wherein the number of slots is configured by Radio Resource Control signaling. 19. The method of claim 16, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of N*P slots and a slot offset of S+L slots; and the TDCP measurement is an aperiodic TDCP measurement that is configured for a lag of L slots with periodicity Q*P based on the first and second TRS bursts. 20. The method of claim 16, wherein the first TRS burst has a periodicity of P slots and a slot offset of S slots; the second TRS burst has a periodicity of Q*P slots and a slot offset of S+L slots; the TDCP measurement being configured for a lag of L slots. 21. The method of claim 20, wherein the trigger for the aperiodic TDCP measurement is a next occasion of the second TRS burst. 22. The method of claim 16, wherein the first TRS burst is periodic; the second TRS burst is aperiodic; the TDCP measurement being an aperiodic TDCP measurement that is configured for a lag of L slots. 23. The method of claim 22, wherein the trigger for the TDCP measurement is a TRS burst separated by L slots relative to one occasion of the first TRS burst. 24. The method of claim 16, wherein the first and second TRS bursts are aperiodic; the TDCP measurement being an aperiodic TDCP measurement that is configured for lag of L slots. 25. The method of claim 24, wherein the trigger for aperiodic TDCP measurement is two TRS bursts separated by L slots. 26. The method of any one of claims 16-25, wherein the first TRS burst and the second TRS burst are transmitted from a same antenna port. 27. The method of any one of claims 16-26, wherein resources of the first TRS burst and resources of the second TRS burst are quasi-collocated. 28. The method of any one of claims 16-27, wherein resources of the first TRS burst and resources of the second TRS burst have same time-domain indices and same subcarrier indices. 29. The method of any one of claims 16-28, wherein the first TRS burst and the second TRS bursts are configured as part of different non-zero power, NZP, channel state information-reference signal, CSI-RS, resource sets. 30. The method of any one of claims 16-28, wherein the first TRS burst and the second TRS burst are configured as part of a same NZP CSI-RS resource set. 31. A wireless device (22; 22a, 22b), configured to: receive a configuration for performing a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; receive the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and perform the TDCP measurement based on the configuration and the first TRS burst and the second TRS burst. 32. The wireless device (22; 22a, 22b) of claim 31, configured to perform a method of any one of claims 2-15. 33. The wireless device (22; 22a, 22b) of claim 31 or 32, comprising processing circuitry (84) and a memory (88) storing instructions to be executed by the processing circuitry (84), whereby execution of the instructions by the processing circuitry causes the wireless device (22; 22a, 22b) to perform a method of any one of claims 1-15. 34. A network node (16; 16a, 16b, 16c), configured to: configure a wireless device (22; 22a, 22b) to perform a time-domain channel properties, TDCP, measurement based on a first tracking reference signal, TRS, burst and a second TRS burst; cause transmission of the first TRS burst and the second TRS burst, the first TRS burst being one of aperiodic and periodic, the second TRS burst being one of aperiodic and periodic; and receive an indication of the TDCP measurement that is based on the configuration and the first TRS burst and the second TRS burst. 35. The network node (16; 16a, 16b, 16c) of claim 34, configured to perform a method of any one of claims 17-30. 36. The network node (16; 16a, 16b, 16c) of claim 34 or 35, comprising processing circuitry (68) and a memory (72) storing instructions to be executed by the processing circuitry (68), whereby execution of the instructions by the processing circuitry (68) causes the network node (16; 16a, 16b, 16c) to perform a method of any one of claims 16-30. 37. A computer program or computer program product comprising instructions to be executed by processing circuitry (84) of a wireless device (22; 22a, 22b), whereby execution of the instructions by the processing circuitry (84) causes the wireless device (22; 22a, 22b) to perform a method of any one of claims 1-15. 38. A computer program or computer program product comprising instructions to be executed by processing circuitry (68) of a network node (16; 16a, 16b, 16c), whereby execution of the instructions by the processing circuitry causes the network node (16; 16a, 16b, 16c) to perform a method of any one of claims 16-30.