Method for reporting Doppler information

Abstract

A device is disclosed comprising means for receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; means for performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; means for determining whether at least one validity condition associated with the at least one measurement is valid; and means for reporting to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

Description

Technology Field

[0001] Examples and non-limiting exemplary embodiments generally relate to communication, and more specifically to methods for reporting Doppler information. Background Technology

[0002] It is known that Doppler measurements are performed in wireless communication networks. means of solving the problem

[0003] According to one embodiment, the device comprises means for receiving a trace reference signal configuration from a network, wherein the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; means for performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; means for determining whether at least one validity condition associated with the at least one measurement is valid; and means for reporting to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0004] According to one embodiment, the device comprises means for transmitting a trace reference signal configuration to user equipment, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; means for receiving a report from the user equipment comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid, wherein the at least one parameter is associated with the trace reference signal; and means for transmitting the at least one measurement and the determination of whether the at least one validity condition is valid to at least one transmission receiving point using a backhaul link.

[0005] According to one embodiment, the method comprises the steps of receiving a trace reference signal configuration from a network—the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured—and performing at least one measurement of the at least one parameter using the configuration—the at least one parameter is associated with a trace reference signal—and determining whether at least one validity condition associated with the at least one measurement is valid, and reporting to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0006] According to one embodiment, the method comprises the steps of: transmitting a trace reference signal configuration to user equipment—the configuration comprising at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured—and receiving a report from the user equipment comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid—the at least one parameter being associated with a trace reference signal—and transmitting the at least one measurement and the determination of whether the at least one validity condition is valid to at least one transmission receiving point using a backhaul link.

[0007] According to one embodiment, the device comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code together with the at least one processor are configured to enable the device to at least receive a trace reference signal configuration from a network—the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured—perform at least one measurement of the at least one parameter using the configuration—the at least one parameter is associated with a trace reference signal—determine whether at least one validity condition associated with the at least one measurement is valid, and report to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0008] According to one embodiment, the device comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code together with the at least one processor are configured to enable the device to transmit a trace reference signal configuration to at least one user device, wherein the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured, receive from the user device a report comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid, wherein the at least one parameter is associated with the trace reference signal, and transmit the determination of whether the at least one measurement and the at least one validity condition are valid to at least one transmission receiving point using a backhaul link.

[0009] According to one embodiment, a machine-readable non-transient program storage device is provided, which tangibly comprises a program of instructions executable to the machine for performing operations, the operations comprising: receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; determining whether at least one validity condition associated with the at least one measurement is valid; and reporting to the network the determination of whether the at least one measurement of the at least one parameter and the at least one validity condition are valid.

[0010] According to one embodiment, a machine-readable non-transient program storage device is provided, which tangibly comprises a program of instructions executable to the machine for performing operations, the operations comprising: an operation of transmitting a trace reference signal configuration to a user device, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; an operation of receiving a report from the user device comprising a determination of whether at least one measurement of the at least one parameter and at least one validity condition are valid, wherein the at least one parameter is associated with the trace reference signal; and an operation of transmitting the determination of whether the at least one measurement and at least one validity condition are valid to at least one transmission receiving point using a backhaul link. Brief explanation of the drawing

[0011] The aforementioned embodiments and other features are described in the following detailed description in conjunction with the attached drawings. FIG. 1 is a block diagram of one possible, non-limiting system in which an exemplary embodiment can be implemented. Figure 2 illustrates an example of a DL TRS for OFDM in NR Rel-15. Figure 3 shows the use of NZP CSI-RS symbols to measure Doppler information in the UE. Figure 4 illustrates Doppler estimation based on UL SRS. Figure 5 shows the signal of a UE-based Doppler estimation and correction method based on an example described in the present specification. FIG. 6 is an exemplary device configured to implement the example described in this specification. Figure 7 shows an example of a non-volatile memory medium. FIG. 8 is a method for performing the example described in this specification. FIG. 9 is a method for performing the example described in this specification. Specific details for implementing the invention

[0012] Referring to FIG. 1, this drawing shows a block diagram of a possible and non-limiting example to which the example can be implemented. User equipment (UE) (110), a wireless access network (RAN) node (170), and network element(s) (190) are illustrated. In the example of FIG. 1, the user equipment (UE) (110) communicates wirelessly with the wireless network (100). The UE is a wireless device capable of accessing the wireless network (100). The UE (110) includes one or more processors (120), one or more memories (125), and one or more transceivers (130) interconnected via one or more buses (127). Each of the one or more transceivers (130) includes a receiver (Rx) (132) and a transmitter (Tx) (133). One or more buses (127) may be address, data, or control buses and may include any interconnection mechanism such as a series of lines of a motherboard or integrated circuit, optical fiber, or other optical communication equipment. One or more transceivers (130) are connected to one or more antennas (128). One or more memories (125) contain computer program code (123). The UE (110) includes a module (140) comprising one or two parts (140-1 and / or 140-2) that can be implemented in various ways. The module (140) can be implemented in hardware as module (140-1), such as being implemented as part of one or more processors (120). Module (140-1) can also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module (140) can be implemented as module (140-2), which is implemented as computer program code (123) and executed by one or more processors (120). For example, one or more memories (125) and computer program code (123) may be configured together with one or more processors (120) to enable the user equipment (110) to perform one or more operations described in this specification.The UE (110) communicates with the RAN node (170) via a wireless link (111).

[0013] In this example, the RAN node (170) is a base station that provides access to the wireless network (100) to a wireless device such as a UE (110). The RAN node (170) may be, for example, a base station for 5G, i.e., a New Radio (NR). In 5G, the RAN node (170) may be an NG-RAN node defined as a gNB or an ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination for the UE and is connected to a 5GC (e.g., network element(s) (190)) via an NG interface (e.g., connection (131)). An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination for the UE and is connected to a 5GC via an NG interface (e.g., connection (131)). An NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) (196) and distributed unit(s) (DU) (gNB-DU), among which a DU (195) is illustrated. A DU (195) may include a radio unit (RU) or be coupled thereto to control it. A gNB-CU (196) is a logical node that hosts the radio resource control (RRC), SDAP, and PDCP protocols of a gNB or the RRC and PDCP protocols of an en-gNB, which control the operation of one or more gNB-DUs. A gNB-CU (196) terminates the F1 interface connected to a gNB-DU (195). The F1 interface is described by reference numeral 198, but reference numeral 198 also exemplifies a link between a remote element of a RAN node (170) and a centralized element of a RAN node (170), for example, a link between a gNB-CU (196) and a gNB-DU (195). A gNB-DU (195) is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by a gNB-CU (196). A single gNB-CU (196) supports one or more cells.A single cell may be supported by a single gNB-DU (195), or a single cell may be supported / shared by multiple DUs under RAN sharing. The gNB-DU (195) terminates the F1 interface (198) connected to the gNB-CU (196). The DU (195) is considered to include a transceiver (160) as part of, for example, the RU, but in some examples, the transceiver (160) may be connected to it as part of a separate RU, for example, under the control of the DU (195). The RAN node (170) may be an eNB (evolved NodeB) base station in the case of LTE (long term evolution) or another suitable base station, access point, access node, or node.

[0014] A RAN node (170) includes one or more processors (152), one or more memories (155), one or more network interfaces (N / WI / F(s)) (161), and one or more transceivers (160) interconnected via one or more buses (157). Each of the one or more transceivers (160) includes a receiver (Rx) (162) and a transmitter (Tx) (163). One or more transceivers (160) are connected to one or more antennas (158). One or more memories (155) include computer program code (153). A CU (196) may include processor(s) (152), memory(s) (155), and network interfaces (161). Note that a DU (195) may also include its own memory(s) and processor(s) and / or other hardware, but this is not illustrated.

[0015] A RAN node (170) includes a module (150) comprising one or two parts (150-1 and / or 150-2) which can be implemented in various ways. The module (150) may be implemented in hardware as module (150-1), such as being implemented as part of one or more processors (152). Module (150-1) may also be implemented through other hardware, such as an integrated circuit or a programmable gate array. In another example, the module (150) may be implemented as module (150-2), which is implemented as computer program code (153) and executed by one or more processors (152). For example, one or more memories (155) and computer program code (153) are configured to enable the RAN node (170) to perform one or more operations described herein, together with one or more processors (152). The function of the module (150) may be distributed between the DU (195) and the CU (196), or implemented only in the DU (195).

[0016] One or more network interfaces (161) communicate through a network such as through links (176 and 131). Two or more gNBs (170) may communicate, for example, using a link (176). The link (176) may be wired or wireless or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0017] As illustrated in FIG. 1, a RAN node (170) can communicate with a RAN node (170-2), a RAN node (170-3), and a RAN node (170-N) using a link (176). A UE (110) communicates with a RAN node (170-2) via a wireless link (111-2), a UE (110) communicates with a RAN node (170-3) via a wireless link (111-3), and a UE (110) communicates with a RAN node (170-N) via a wireless link (111-N). A RAN node (170-2) includes a TRP (61) and a TRP (62), a RAN node (170-3) includes a TRP (71) and a TRP (72), and a RAN node (170-N) includes a TRP (81) and a TRP (82). Each RAN node (170, 170-2, 170-3, and 170-N) may contain two or more TRPs.

[0018] One or more buses (157) may be address, data, or control buses and may include any interconnection mechanism such as a series of lines of a motherboard or integrated circuit, optical fiber or other optical communication equipment, a wireless channel, etc. For example, one or more transceivers (160) may be implemented as a remote radio head (RRH) (195) in the case of LTE or a distributed unit (DU) (195) in the case of a 5G gNB implementation, and other elements of the RAN node (170) may be physically located at a different location from the RRH / DU (195), and one or more buses (157) may be partially implemented as, for example, fiber optic cables or other suitable network connections for connecting other elements of the RAN node (170) (e.g., central unit (CU), gNB-CU (196)) to the RRH / DU (195). Reference numeral 198 also indicates such suitable network link(s).

[0019] A RAN node / gNB may include one or more TRPs to which the method described herein may be applied. FIG. 1 shows a RAN node (170) including two TRPs, TRP (51) and TRP (52). The RAN node (170) may host or include other TRPs not shown in FIG. 1. TRPs (51 and 52) may form part of the components of a transceiver (160).

[0020] In the present disclosure, two TRPs may be for one gNB (e.g., a serving cell), and the other two TRPs may be for different cells / gNBs (different PCIs from the serving cell). Alternatively, all TRPs may be associated with the same cell. Thus, as described in the specification, TRPs may be associated with the same or different PCIs.

[0021] The relay nodes of NR are referred to as integrated access and backhaul nodes. The mobile end portion of the IAB node facilitates backhaul (parent link) connections. The mobile end portion is responsible for transmitting UE functions. The distributed unit portion of the IAB node facilitates so-called access link (child link) connections (i.e., access link UEs and backhaul of other IAB nodes in the case of multi-hop IABs). The distributed unit portion is responsible for specific base station functions. The IAB scenario may follow a partitioned architecture where the central unit hosts upper-layer protocols for UEs and terminates control plane and user plane interfaces for the 5G core network.

[0022] Although the description in this specification indicates that a "cell" performs a function, it is clear that the equipment forming said cell can perform that function. A cell constitutes part of a base station. That is, there may be multiple cells per base station. For example, there may be three cells for a single carrier frequency and associated bandwidth, and each cell covers one-third of a 360-degree area, so that the coverage area of ​​a single base station covers an approximate ellipse or circle. Furthermore, each cell may correspond to a single carrier, and the base station may use multiple carriers. Thus, if there are three 120-degree cells per carrier and two carriers, the base station has a total of six cells.

[0023] A wireless network (100) may include network elements or elements (190) that may include core network functions, which provide connectivity via links or links (181) to additional networks such as telephone networks and / or data communication networks (e.g., the Internet). For 5G, these core network functions may include location management functions (LMF(s)) and / or access and mobility management functions (AMF(s)) and / or user plane functions (UPF(s)) and / or session management functions (SMF(s)). For LTE, these core network functions may include Mobility Management Entity (MME) / Serving Gateway (SGW) functions. These core network functions may include self-organizing / optimizing network (SON) functions. These are merely examples of functions that may be supported by network element(s) (190), and both 5G and LTE functions may be supported. A RAN node (170) is connected to a network element (190) via a link (131). The link (131) may be implemented, for example, as an NG interface for 5G, an S1 interface for LTE, or other suitable interfaces for other standards. The network element (190) includes one or more processors (175), one or more memories (171), and one or more network interfaces (N / WI / F(s)) (180), and is interconnected via one or more buses (185). One or more memories (171) contain computer program code (173). The computer program code (173) may include SON and / or MRO functions (172).

[0024] One or more network elements (190) include a module (177) that may include a Near-Real-Time RIC function. Computer program code (173) may include a Near-Real-Time RIC function. Module (150-1) and / or module (150-2) may include a Near-Real-Time RIC function.

[0025] A wireless network (100) can implement network virtualization, which is a process of combining hardware and software network resources and network functions into a single software-based management entity called a virtual network. Network virtualization includes platform virtualization and is often combined with resource virtualization. Network virtualization is classified into combining external, multiple networks or parts of networks into virtual units, or providing network-like functions to software containers within an internal, single system. The virtualized entities resulting from network virtualization are still implemented to some extent using hardware such as processors (152 or 175) and memory (155 and 171), and these virtualized entities produce technical effects.

[0026] Computer-readable memory (125, 155, and 171) may be of any type suitable for the local technology environment and may be implemented using any suitable data storage technology such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-transient memory, transient memory, fixed memory, and removable memory. Computer-readable memory (125, 155, and 171) may be means for performing storage functions. Processors (120, 152, and 175) may be of any type suitable for the local technology environment and may include, as non-limiting examples, one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors (120, 152, and 175) may be means for performing functions such as controlling the UE (110), RAN node (170), network element(s) (190), and other functions described herein. Generally, various exemplary embodiments of user equipment (110) may include, but are not limited to, cellular phones, e.g., smartphones, tablets, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices such as digital cameras with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablets with wireless communication capabilities, head-mounted displays such as those implementing virtual / augmented / mixed reality, and portable units or terminals that integrate combinations of these capabilities. The UE (110) may also be a vehicle such as a car, or a UE mounted on a vehicle, e.g., a UAV such as a drone, or a UE mounted on a UAV.

[0027] The UE (110), RAN node (170) and / or network element(s) (190) (and associated memory, computer program code and modules) may be configured (e.g., partially) to implement the method described herein, including a method for reporting Doppler information. Thus, the computer program code (123), module (140-1), module (140-2), and other elements / functions shown in FIG. 1 of the UE (110) may implement the user equipment-related aspects of the method described herein. The computer program code (153), module (150-1), module (150-2), and other elements / functions shown in FIG. 1 of the RAN node (170) may implement the gNB / TRP-related aspects of the method described herein. The computer program code (173) and other elements / functions shown in FIG. 1 of the network element(s) (190) may be configured to implement the network element-related aspects of the method described herein.

[0028] Therefore, having introduced an appropriate but non-limiting technical context for the implementation of exemplary embodiments, the exemplary embodiments are now described in more detail. The examples described herein relate to PHY layer enhancements considering MIMO-related environments that enable Doppler shift / spread / measurement. Certain components are implemented by the UE and gNB. The methods described herein relate to Rel.17 HST-SFN enhancements (e.g., R1-2101450 and R1-2202320) for UE-based Doppler measurement reporting (particularly explicit approaches). Also refer to RP-213517, RP-213598, and R1-2204143. The examples described herein relate to validity conditions for Doppler parameter measurements, including default and fallback reporting modes. In particular, what is described herein are conditions for the validity (e.g., power threshold or offset) and reporting of TRP-specific and inter-TRP Doppler parameter measurements. The examples described in this specification provide more accurate information and reliability.

[0029] While Rel-18 standardization focuses on improvements to uplink (UL) MIMO, there is still a need to introduce essential improvements to downlink (DL) MIMO to facilitate the use of large antenna arrays (applicable to FR1 as well as FR2) to meet the demand for the evolution of NR deployments [Tdoc No. RP-213517 - 'New WID: MIMO Evolution for Downlink and Uplink'].

[0030] Rel-16 / 17 MIMO supports multiple TRP deployments in the form of non-coherent joint transport (NC-JT). Additionally, Coherent Joint Transport (CJT), introduced in Rel-11 for LTE, can improve coverage and average throughput in commercial deployments through high-performance backhaul and synchronization. With this in mind, improvements in CSI acquisition for FDD and TDD targeting FR1 can be beneficial in extending the utility of CJT for NR multiple TRP deployments [Tdoc No. RP-213517 - 'New WID: MIMO Evolution for Downlink and Uplink']. Consequently, CJT is considered one of the potential technologies for 5G-advanced cellular systems targeting Rel-18. In CJT, multiple TRPs serve each UE in a coherent manner, which can significantly improve throughput for cell edge UEs. However, CJT requires synchronization of accurate channel state information (CSI), such as phase, timing, and frequency, for successful operation. For example, a change in the CSI phase can lead to destructive coupling at the target UE, resulting in a decrease in the UE's SINR (and consequently, a decrease in throughput).

[0031] When considering moving UEs, the effects of Doppler shift / diffusion are one of the reasons why the channel phase changes differently from multiple TRPs. Since the UE velocity varies depending on the multiple TRPs, the channel from each TRP to the UE is consequently affected by Doppler shift / diffusion. In the case of CJT-CoMP (coordinated multi-point), this causes interference in the UE, degrading throughput.

[0032] NR Rel-15 supports coarse downlink time and frequency synchronization based on the primary synchronization signal and the auxiliary synchronization signal located in the synchronization signal block (SSB). After receiving the SSB, the UE is intended to compensate for the residual time and frequency error offset and adjust the parameters of the DMRS channel estimator, namely the Wiener filter lengths for time and frequency, to match the coherence time and the frequency of the radio channel with the time and frequency tracking reference signal (TRS).

[0033] As mentioned above, NR Rel-15 provides a mechanism to support downlink TRS transmission using NZP-CSI-RS resources with CP-OFDM waveforms [TS 38.211]. In TS 38.214, two different NZP-CSI-RS resource set configurations are supported to allow the UE to perform time and frequency tracking. More specifically, according to [TS 38.214], for an NZP-CSI-RS-ResourceSet configured with the upper layer parameter trs-Info, the UE assumes that antenna ports having the same port index of the configured NZP-CSI-RS resources within the NZP-CSI-RS-ResourceSet are identical.

[0034] For frequency range 1 (i.e., less than 6 GHz), the UE may be composed of one or more NZP CSI-RS set(s), wherein the NZP-CSI-RS-ResourceSet is composed of four periodic NZP CSI-RS resources in two consecutive slots, with two periodic NZP CSI-RS resources in each slot.

[0035] For frequency range 2 (i.e., 6 GHz or higher), the UE may be composed of one or more NZP CSI-RS set(s), wherein the NZP-CSI-RS-ResourceSet is composed of two periodic CSI-RS resources in one slot, or wherein the NZP-CSI-RS-ResourceSet is composed of four periodic NZP CSI-RS resources in two consecutive slots, with two periodic NZP CSI-RS resources in each slot.

[0036] The UE expects that the periodic CSI-RS resource set and the non-periodic CSI-RS resource set are configured to have the same number of CSI-RS resources and the same number of CSI-RS resources within the slots. If the non-periodic CSI-RS resource set is triggered, and if the associated periodic CSI-RS resource set is configured with four periodic CSI-RS resources having two consecutive slots with two periodic CSI-RS resources in each slot, the upper-level parameter aperiodicTriggeringOffset represents the triggering offset with respect to the first slot for the first two CSI-RS resources within the set.

[0037] FIG. 2 shows an example of a CP-OFDM-based DL NZP-CSI-RS-based TRS transmission in NR Rel-15. As shown, the NZP CSI-RS resource is a single port with a density of 3. The maximum bandwidth of the CSI-RS resource is 52 physical resource blocks (PRB). The time-domain positions of two CSI-RS resources in a slot or four CSI-RS resources in two consecutive slots are provided as one of the following [TS 38.214]:

[0038] - For frequency ranges 1 and FR2, {4,8}, {5,9} or {6,10},

[0039] - For FR2, {0,4}, {1,5}, {2,6}, {3,7}, {7,11}, {8,12} or {9,13}.

[0040] As shown in FIG. 2, the first NZP-CSI-RS (202) and the second NZP-CSI-RS (204) are within the PDSCH (206). The M-IDFT (208) is applied to the PDSCH (206). The CP (210) is applied to the output of the M-IDFT (208). The system BW (212) is affected by the process and configuration shown in FIG. 2.

[0041] The Rel-17 NR specification supports both the previously described network and Rel-15 UE-based Doppler shift / spread tracing. The network-based method is used in High Speed ​​Train (HST) scenarios where DL PDSCH is transmitted via a Single Frequency Network (SFN) from multiple TRPs after compensating for Doppler based on uplink measurements. Details are described in this specification.

[0042] NR Rel-18 supports DL precoding (targeting FR1) utilizing time-domain correlation / Doppler domain information to specify CSI reporting enhancements for high / medium-speed UE rates as follows [Tdoc No. RP-213517 - 'New WID: MIMO Evolution for Downlink and Uplink']:

[0043] - Improvement of Rel-16 / 17 Type II codebooks without modifying the spatial and frequency domain basis

[0044] - UE reporting of time-domain channel attributes measured via CSI-RS for tracking.

[0045] According to the proposal in [Tdoc No. R1-2203151 - 'New WID: CSI Enhancement for Coherent JT and Mobility'], the UE can measure Doppler information from a uniformly separated set of NZP CSI-RS bursts as shown in Fig. 3. Bursts of NZP CSI-RS help the UE estimate more accurate and reliable Doppler information. Fig. 3 illustrates a set of CSI-RS resources (302, 304, 306) for P / SP CSI-RS (310) and a set of CSI-RS resources (308) for AP CSI-RS (320), each set of CSI-RS resources (302, 304, 306, 308) containing uniformly separated NZP CSI-RS bursts, wherein at least for the CSI-RS resource sets (302 and 308), the NZP CSI-RS bursts are separated into 1d time slots for a given time period d.

[0046] Doppler information extracted from the UE can be used to improve downlink throughput in the gNB, and the use case is as follows [Tdoc No. R1-2203229 - 'New WID: CSI Enhancement for Rel-18 NR MIMO Evolution']:

[0047] - The network can use UE reports to determine the configuration cycle or trigger time of CSI-RS, CSI reports, or SRS.

[0048] - The network determines whether to configure Type I or Type II CSI reporting using UE reporting.

[0049] - The network can use UE reports to determine whether to use mutual-based CSI acquisition or Type II-based CSI feedback for MU-MIMO scheduling.

[0050] - The network can use UE reports to determine the number of additional DMRS symbols required.

[0051] - The network uses reports as input to an open-loop link adaptation algorithm to coordinate robust MCS selection even in URLLC cases.

[0052] - The network uses the report as input for AI / ML algorithms in the network's upper layers or for beam management.

[0053] To achieve the benefits of coherent joint transmission using precoding for TDD-based DL multi-TRP operation in NR Rel-18 and later releases (i.e., inter-cell and MU-MIMO interference mitigation and improved spectral efficiency), the availability of accurate DL CSI information plays a critical role in this process. In practice, due to UE mobility, it can be difficult to obtain up-to-date DL CSI information through UL SRS sounding or DL ​​CSI reporting based on DL RS measurements. Indeed, there is always a time lag between the temporal case of UL / DL CSI measurement (and estimation) and the temporal moment when joint precoding between different TRPs is applied. There are also other potential sources of CSI inaccuracy, such as estimation errors, latency associated with backhauling, and the quantization of reported CSI information. To address some of these impacts, time-domain prediction of CSI information on the network side, based on UE Doppler information measurements and reporting, can be viewed as an attractive candidate for Rel-18 DL multi-TRP CJT and subsequent releases.

[0054] The problem of tracking radio channel time evolution was addressed in High Speed ​​Train (HST) scenarios, where a dominant LoS propagation path is always present and it is necessary to track only the Doppler shift for each TX-RX pair between the TRP and the UE. As previously discussed, Rel-17 supports both UE and network-based approaches for SFN HST scenarios, including networks utilizing UL SRS transmission with Doppler shift pre-compensation on the network side. The primary focus of the examples described herein is on the network-based approach.

[0055] A problem with the Rel-17 network-based approach is that multiple UL SRS transmissions from a single UE are required for Doppler estimation at each TRP. As a result, UL SRS resource overhead increases sharply, degrading UL PUSCH throughput. Additionally, due to limited UL TX power, the quality of Doppler information estimation based on UL SRS transmissions can be significantly degraded in some scenarios (e.g., when the UE is located at the edge of the TRP's service coverage).

[0056] In order to improve network-based pre-compensation schemes by reducing UL SRS overhead and delay, increase measurement reliability, and improve network efficiency, it is necessary to develop a new method for measuring and reporting Doppler information based on DL TRS measurements.

[0057] Figure 4 illustrates Doppler estimation based on UL SRS. Figure 4 is partially based on Tdoc No. RP-213517 - 'New WID: MIMO Evolution for Downlink and Uplink'.

[0058] Doppler estimation for the HST scenario is described in [Tdoc No. R1-2101450 - 'Improvement for HST-SFN deployment' R4], where the Doppler shift can be estimated using UL SRS. This is illustrated in FIG. 4 for the case of two TRPs (401, 402). Initially, TRS1 (404) and TRS2 (406) are transmitted from TRP1 (401) and TRP2 (402), respectively, and then the UE (110) measures 'fD1' associated with TRS1 (404) and compensates for it in the UL. At this stage, the UE (110) transmits UL SRS (408, 410) at 'Fc+fUE', which is received by TRP1 (401) at 'Fc+fUE+fD1' and by TRP2 (402) at 'Fc+fUE+fD2'. The Doppler shift difference between TRP1 (401) and TRP2 (402) can be calculated using a backhaul signal and can be pre-compensated during data transmission.

[0059] However, in some scenarios, UL SRS transmissions (408) for TRP1 (401) may result in larger estimation errors due to the UE (110)'s limited UL TX power budget (e.g., errors related to Doppler shift, CSI, etc.). In this regard, as mentioned in [Tdoc No. R1-2202320 - 'Maintaining improvements for HST-SFN deployments'], the number of other SRS transmissions associated with other TRPs must be increased. For example, to estimate a small Doppler shift, it is necessary to configure the timing of UL SRS transmissions across several symbols / slots. It should be noted that the coherence time of the radio is approximately inversely proportional to the Doppler spread / shift. This can lead to a decrease in UL data throughput by causing additional delays, UL reference signal resource overhead, and potential scheduling limitations. [Tdoc No. R1-2101450 - 'HST-SFN Deployment Improvements'] defines an alternative approach in which Doppler parameters are determined on the UE side by performing measurements on the TRS reference signal transmission and reporting them back to the network.

[0060] Accordingly, the validity conditions for Doppler parameter measurements and their reporting are described herein. Additionally, methods for default and fallback Doppler information reporting modes are described herein.

[0061] Compliance with the UE reporting mechanism for Doppler estimation and Doppler parameters (enhanced CSI parameters) in the UE is summarized as follows.

[0062] The following assumptions are made. A network can configure one or more sets of TRS resources via upper-layer signals (i.e., RRC) to function as "anchor" resources (used for calculating the Doppler difference). The network has K associated with each TRP-specific TRS resource to be measured via the upper-layer signals. TRP# - Strongest / Dominant Multipath Component (K TRP#-strongest / dominant multi-path components) can be configured. The network provides the UE with decision parameters (e.g., receive power threshold level, measurement time window, aging information, report time offset, maximum delay spread of TRP-specific links, maximum propagation delay or delay spread of each TRS, etc.) to enable the UE to determine the K associated with each TRP-specific TRS resource. TRP# - It is possible to verify the strongest / dominant multipath component. The network may configure different standalone Doppler parameter / information reporting formats. In this context, standalone means that the reporting does not rely on other codebook-based CSI reporting. Alternatively, the network may also configure non-standalone Doppler parameter / information reporting formats. The reporting format may include TRP-specific Doppler information (i.e., Doppler shift and / or plain Doppler shift and / or phase and / or plane phase and / or Doppler spread difference) and / or inter-TRP Doppler information. The network may configure the arrival times of the first multipath component associated with each configured TRS resource and the reporting format of each multipath component of the configured TRS resource. The network may configure Doppler reporting time offsets.

[0063] The primary target of standalone or non-standalone Doppler information reporting is to support gNBs in scheduling cycles of CSI-RS resources and CSI reporting, and in selecting reporting types (e.g., including the selection between mTRP CSI reporting and sTRP CSI reporting, such as Type-I NCJT and Type-II CJT). Additionally, Doppler information reporting can be used to support gNB-side predictions, such as DL precoding. This can be beneficial for both CSI feedback-based precoding schemes and UL SRS mutual-based precoding schemes. Both standalone and non-standalone Doppler information reporting can be used in the context of single and multiple TRP scenarios.

[0064] The validity of TRP-specific and inter-TRP Doppler information measurements (for one or more parameters) and reporting is defined as follows. Doppler information (e.g., Doppler information items) may be defined as the multipath-specific Doppler shift or the multipath-specific Doppler shift difference between a "anchor" TRP and a resource (e.g., TRS) associated with another TRP (sharing the same or different physical cell IDs (PCI)). The validity of Doppler parameter measurements is, for example, K TRP# It may be defined based on one of the following: Condition #1 based on the TRP-specific or inter-TRP multipath power difference between dominant multipath components; Condition #2 based on the TRP-specific or inter-TRP TRS resource application time for Doppler difference calculation; Condition #3 based on the TRP-specific or inter-TRP difference in measurement time for Doppler difference calculation; Condition #4 based on the arrival time calculation of each TRP-specific TRS; or Condition #5 based on the reporting time offset.

[0065] Accordingly, a new method for reporting Doppler information using default and fallback reporting modes is described. If all validation conditions or configured validation conditions are satisfied, the default operation mode is used, and if at least one of the configured validation conditions is not satisfied, the fallback operation mode is used.

[0066] In default operation mode (where all or configured validity conditions are met), the UE (110) reports parameters related to Doppler shift / diffusion and / or one or more TRP-specific TRS used in the measurement using a new CSI format.

[0067] In fallback operation mode (when at least one of the configured validity conditions is not met), the UE (110) reports at least one of a set of fallback parameters such as Doppler shift / spread value, indication of Doppler reporting format, indication of anchor resource set (if necessary), indication of the number of measured valid paths, indication of the number of valid TRS resources used for measurement, indication of aging validity for measurement, time difference between TRS resources, arrival time difference for each multipath, and anchor resource time difference for slot timing.

[0068] Initially, the network uses a downlink control signaling framework (e.g., RRC and / or physical and / or MAC level signals) to configure the Doppler reference signal (e.g., TRS) or signal (e.g., SSB) resources and parameters to be measured (or verified) at the UE. Then, the TRP transmits NZP-CSI-RS from the DL, and the UE performs the Doppler measurement with the validity of the measurement as requested by the network. Once the UE completes the calculation of the Doppler parameters, the UE reports the Doppler information with the configured validity conditions.

[0069] The network configures the UE with a set of predefined compliance requirements to measure Doppler parameters. To this end, it is assumed that the network configures the following parameters.

[0070] The network configures one or more sets of TRS resources to act as 'anchor' resources to calculate the Doppler difference.

[0071] The network is K associated with each TRP-specific TRS resource to be measured. TRP# - Configures the strongest / dominant multipath component. The UE has K of each TRP-specific TRS resource. TRP# - Calculate and select the strongest multipath component. A power threshold is defined, or the relative power difference for the first detected multipath component is defined, with K associated with each 1 antenna port TRS resource. TRP# - Determine the strongest multipath component. The default assumption is that the same number of multipath components are used for each TRP-specific TRS resource.

[0072] The network configures CSI / Doppler information related to the measurement time (or age) or the timing of the measurement. Aging information is configured by the network based on channel conditions and the timing at which the measurement is applied in the DL in relation to the measurement time. The network configures aging validity conditions for the UE, for example, as a P-continuous TRS transmission opportunity, for which the UE must perform a measurement and provide a corresponding report. Through this, the network can impose measurement limits on the UE, thereby forcing the UE to use a specific TRS measurement opportunity for a specific reporting instance. As a result, the gNB can be guaranteed that these measurements are actually associated with a specific time window rather than measurements accumulated over an undefined period. This can be useful, for example, when some periodic TRS resources are configured and supplemented by non-periodic TRS resources. The delay spread of each TRP-specific TRS resource can be configured by the network, where the UE is expected to receive all multipaths of the TRS within the delay spread. The maximum reporting time is configured by the network, within which the UE (110) must report Doppler information to the gNB (170). The maximum propagation delay of a specific TRS for each TRP is configured by the network. The UE is expected to receive the TRS within the maximum propagation delay.

[0073] By introducing validity conditions for measurements, the quality of Doppler parameter measurements is guaranteed, and ambiguity regarding how measurements are performed on the UE side can be avoided on the gNB side, for example, by Condition #1, so that all configured K dominant multipath components exceed a specific power threshold or power offset for anchor TRS resources (to distinguish them from the thermal noise floor) at some specific level of network usage (e.g., for Doppler parameter prediction on the network side and indication to the UE). Additionally, by introducing Condition #2, a limit on Doppler parameter measurements for the UE is introduced, requiring the UE to measure and calculate over P-continuous TRS transmission opportunities. If this limit is not introduced, ambiguity regarding the network is maintained in the TRS resources where the UE calculates Doppler parameters. A network, such as a RAN node (170) or network element(s) (190), may configure a Doppler (phase / frequency / time) parameter reporting format, for example, a format for reporting one or more Doppler parameters. TRP-specific Doppler parameters are K from each TRP-specific TRS resource. TRP# It may specifically include the actual Doppler shift value of the dominant path or the relative (differentially encoded) Doppler shift value with respect to the dominant path TRP. The inter-TRP Doppler parameter is the K between the reference TRP and the anchor TRP resource. TRP#It may include Doppler shift differences between dominant paths (the difference may also be differentially encoded). TRP-specific phase values ​​may include actual phase values ​​that can be calculated for one or more dominant path(s) of each TRS. TRP-inter-phase values ​​may include phase differences between TRP-specific TRS resources that can be calculated for the dominant multipath components of each TRP resource. TRP-specific time parameters may include actual arrival times of one or more dominant path component(s) of a TRS resource, and time difference(s) for specific multipaths may be calculated within the TRS and for each TRP-specific TRS resource. TRP-inter-time parameters may include time differences between multipath components, which can be calculated based on the anchor TRP-specific TRS resource.

[0074] Upon receiving a Doppler configuration frame from a network (associated TRP), the UE can appropriately perform Doppler measurements along with validity conditions for receiving DL NZP-CSI-RS signals from each TRP. The UE Doppler measurements and validity conditions are defined as follows.

[0075] The validity of measuring and reporting TRP-specific and inter-TRP Doppler parameters is defined as follows (for one or more Doppler parameters).

[0076] Doppler parameters may be defined as multipath-specific Doppler shifts or the difference in multipath-specific Doppler shifts between a resource associated with an "anchor" TRP and another TRP (sharing the same or different physical cell ID (PCI)). In the case of a multipath scenario, Doppler information may be reported in the form of a Doppler spectrum, and in this regard, the UE (110) calculates the Doppler spectrum with a given bandwidth and frequency resolution. The validity of the Doppler parameter measurement may be defined using at least one of the following conditions (conditions #1 through 5).

[0077] Condition #1 , K TRP# Multipath power difference between TRPs and dominant multipaths: The UE depends on K based on the associated reference signal receive power (RSRP) associated with the TRP-specific TRS resource. TRP# Determine the dominant multipath components and specifically sort / rank them for the TRPs (in descending order). To define the validity of Condition #1, all Ks of each TRP TRP# The dominant multipath component must exceed a configured power threshold [dBm / dB], which may be configured by the network, such as a RAN node (170) or one or more network element(s) (190). In an alternative implementation, the UE exceeds a configured power threshold (K UE ≤ K TRP# K exceeding ) UE (≥1) It is permitted to select the dominant component. Otherwise, the validity of Condition #1 is invalid. To define the validity of Condition #1 in the alternative approach, all K of each TRP TRP# The dominant multipath component is the maximum D for the first (most dominant) multipath component of the anchor TRP. power-offset-max It must be within the [dB] power offset. In an alternative implementation, the UE must be within the configured power threshold (K UE ≤ K TRP#D regarding anchoring ) power-offset-max [dB] Power offset K UE (≥1) A dominant component can be selected. Otherwise, the validity of Condition #1 is invalid. If Condition #1 is valid, the UE must determine the Doppler shift associated with each path and the corresponding Doppler difference between the anchor resource and the reference resource associated with the TRP. Similarly, the coherent phase of each dominant path of the TRS or the coherent phase difference between the TRSs is calculated.

[0078] Condition #2 , TRP-specific / inter-TRP TRS resource application time for Doppler difference calculation. The validity of Condition #2 is the configured time offset D of the receive time difference between two different DL TRS resources. time-offset It is defined as being within, for example, being in a P-continuous TRS transmission opportunity at time t. If validity is maintained between resources, the UE determines the corresponding Doppler parameters. Otherwise, the measurement is defined as invalid. One potential use case for this condition is when Doppler parameter measurements are performed between periodic / semi-permanent resources from different TRPs and / or between non-periodic resources from TRPs triggered via a single or multiple DCIs.

[0079] Condition #3Calculation of TRP-specific / inter-TRP time difference to verify / report the estimated time (or age) of CSI information. Validity condition #3 is defined when aging information is configured. At least one of the TRS resources from all configured TRPs arrives within the aging time. In this case, the UE (110) calculates the Doppler shift / spread using only one TRS resource from each TRP. Otherwise, this condition is invalid. If the UE (110) receives multiple TRS resources belonging to a single TRP within a predefined aging time, for example in the case of periodic TRS, the UE can estimate the Doppler parameters more accurately using multiple TRS resources from each TRP. The network may configure the aging time interval, for example, as a set of M periods of TRS transmission, and information measured thereafter is considered to no longer be coherent. Validity condition #3 is also related to the maximum delay spread of the TRP-specific TRP. If the UE (110) receives all multipaths (corresponding to a specific power threshold or lower) within the delay spread, the condition is valid, and if not, the condition is not valid.

[0080] Condition #4 , UE (110) checks the arrival times of one or more dominant path(s) of each TRP-specific TRS. If the dominant path of a TRP-specific TRS arrives later than the maximum propagation delay or delay spread, the TRS is invalid. In some cases, longer propagation delays are not allowed due to inter-symbol interference.

[0081] Condition #5 , UE tracks the reporting time. If UE (110) is unable to transmit the report within the reporting time, this condition is invalid. This may be if UE has not received all TRS or if UE (110) does not have spare resources to transmit the report on the uplink.

[0082] After completing the Doppler measurement, the UE reports the Doppler measurement to the network (associated TRP) along with validity conditions using the reporting method below.

[0083] The method for reporting Doppler information using the default operation mode is defined as follows.

[0084] Default operating mode and associated reporting format: (If all configured validity conditions are met). CSI reporting includes one of the following options with corresponding elements: Option A: Non-differential reporting using an L-bit quantized Doppler value and validity bit 1, and Option B: Differential reporting using an L-bit quantized Doppler difference value and validity bit 1. Reporting includes multiple TRP-specific TRS resources used for the measurement. Fallback operating mode and associated reporting format: (If at least one of the validity conditions is not met), configured as Case-1 or Case-2.

[0085] Case-1: The UE (110) may report by adding a validity condition to each measurement. The Doppler shift or Doppler difference is reported. The anchor TRS resource is valid or invalid, and this may be reported. If the anchor node is selected differently, an indication of the anchor TRS resource may be reported. A validity bit for each path measurement may be reported. A validity bit for each measured Doppler difference may be reported. A validity bit for the application time may be reported. A validity bit for aging information may be reported. An indication of the number of TRP-specific TRS resources used in the measurement may be reported. Alternatively, to reduce reporting overhead, the report may include only one validity bit indicating whether all measurements are valid. In another approach, a bit vector of length Q (=number of measurements) is defined to indicate whether the measurement is valid (=1) or invalid (=0). In Case-1, a network such as a RAN node (170) or one or more network elements (190) can infer the number of TRPs related to the measurement from the valid bits.

[0086] Case-2: The UE (110) may report parameters by encoding validity information for the measurement. Validity of the Doppler difference or Doppler shift measurement may be reported. The number of measured valid paths may be reported. An indication of the number of TRP-specific TRS resources used in the measurement may be reported, which may be used for aging information while the network applies DL compensation. An indication of the number of TRPs involved in the measurement may be reported, which may be used with these TRPs for CJT. An indication of the validity of the application time may be reported.

[0087] Additionally, the UE (110) may reuse existing beam management CSI reports by adding a validity bit or other bit for each measurement, or the UE (110) may use the reporting method described herein based on a validity condition.

[0088] If the configured validity conditions are not met on the UE side, a fallback behavior is defined, which may indicate whether one or more measurements are valid (or invalid). This can be accomplished by reserving some additional payload bits to indicate the validity of each configured measurement (e.g., 0=invalid or 1=valid) or by determining some values ​​(e.g., certain maximum / minimum values) that implicitly indicate whether a measurement is valid or invalid (enabling the use of a single reporting format for reporting valid and invalid measurements).

[0089] FIG. 5 illustrates an example / method (500) for reporting Doppler information for a LoS case. Assuming that a UE (110) is associated with TRP1 (501), initially, TRP1 (501) transmits a 'Doppler configuration' frame (510) to the UE (110), which includes network parameters and conditions to be measured. Then, each TRP (501, 502, 503) transmits a TRS using allocated resources. The UE (110) receives a TRS from a different TRP at a different frequency offset according to the associated Doppler.

[0090] As shown in Fig. 5, time F c At this time, TRP1 (501) transmits TRS1 (511) to UE (110), and UE (110) at time F c +f D1 Receives TRS1(511) at time F c At this time, TRP1 (501) transmits TRS1 (511) to UE (110), and UE (110) at time F c +f D1Receives TRS1(511) at time F c At this time, TRP2 (502) transmits TRS2 (512) to UE (110), and UE (110) at time F c +f D2 Receives TRS2(512) at time F c At this time, TRP3 (503) transmits TRS3 (513) to UE (110), and UE (110) at time F c +f D3 Receives TRS3(513) from.

[0091] The UE (110) performs the operation indicated by the 'Doppler configuration' frame transmitted from 510. In one case, the UE (110) is instructed to perform the Doppler difference between TRP1 (501) and TRP2 (502), and between TRP1 (501) and TRP3 (503) in a single path. In this case, the UE (110) performs the difference of the received frequencies 'f d1 -f d2 ' and 'f d1 -f d3 Calculate as (refer to 520 and 530 respectively) and use this information in the uplink UE report frame (550) at time F c +f UE It is transmitted to TRP1 (501) (associated TRP) along with the validity of the corresponding measurement. This information is shared between TRPs using a backhaul link, and the TRP pre-compensates the data as illustrated in FIG. 5. For example, as illustrated in FIG. 5, TRP1 (501) uses a backhaul link (560) to 'f d1 -f d2 Share the calculation of '(520) with TRP2 (502), and TRP1 (501) uses the backhaul link (570) to 'f d1 -f d3 Share the calculation of (530) with TRP3.

[0092] Time F c At this time, TRP1 (501) transmits PDSCH (581) to UE (110), which is at time Fc +f D1 It is received by the UE (110) at time F. c +f D1 -f D2 At this time, TRP2 (502) transmits PDSCH (582) to UE (110), which is at time F c +f D1 It is received by the UE (110) at time F. c +f D1 -f D3 At this time, TRP3 (503) transmits PDSCH (583) to UE (110), which is at time F c +f D1 It is received by the UE (110).

[0093] The Doppler parameter estimation and reporting method defined above has the following benefits and technical effects. This method reduces the UL SRS overhead used for Doppler measurements and provides improved CSI measurement reporting for UEs in motion. Doppler parameters are more accurate and reliable. Network efficiency is improved by utilizing Doppler information for any of the use cases mentioned in [Tdoc No. R1-2203229 - 'New WID: CSI Enhancement for Rel-18 NR MIMO Evolution' R3]. Additionally, the examples described herein may be relevant in the context of the Rel-18 work item for MIMO evolution for downlink and uplink.

[0094] FIG. 6 is an exemplary device (600) that may be implemented in hardware and is configured to implement the example described herein. The device (600) includes at least one processor (602) (e.g., FPGA and / or CPU) and at least one memory (604) containing computer program code (605), and the at least one memory (604) and the computer program code (605) together with the at least one processor (602) are configured to enable the device (600) to implement a circuit, process, component, module, or function (collectively referred to as control (606)) to implement the example described herein, including trust-based advanced trajectory prediction. The memory (604) may be non-transient memory, transient memory, volatile memory (e.g., RAM), or non-volatile memory (e.g., ROM).

[0095] The device (600) optionally includes a display and / or I / O interface (608), which may be used to display an aspect or state of the method described herein (e.g., while one of the methods is being performed or at a subsequent time) or to receive input from a user using a keypad, camera, touchscreen, touch area, microphone, biometric recognition, one or more sensors, etc. The device (600) includes one or more communication, e.g., network (N / W) interfaces (I / F(s)) (610). The communication I / F(s) (610) may be wired and / or wireless and communicate over the Internet / other networks via any communication technology. The communication I / F(s) (610) may include one or more transmitters and one or more receivers. The communication I / F(s) (610) may include well-known standard components such as amplifiers, filters, frequency converters, (inverse)modulators, encoder / decoder circuits, and one or more antennas.

[0096] The device (600) for implementing the function of control (606) may be a UE (110), a RAN node (170) (e.g., gNB) or a network element(s) (190), and may be one of the TRPs shown in FIG. 4 and FIG. 5. Accordingly, the processor (602) may correspond to processor(s) (120), processor(s) (152) and / or processor(s) (175), the memory (604) may correspond to memory(s) (125), memory(s) (155) and / or memory(s) (171), the computer program code (605) may correspond to computer program code (123), module (140-1), module (140-2) and / or computer program code (153), module (150-1), module (150-2) and / or computer program code (173) or module (177), and the communication I / F(s) (610) may correspond to transceiver (130), antenna(s) (128), transceiver (160), antenna(s) (158), N / WI / F(s) (161) and / or It may correspond to N / WI / F(s) (180). Alternatively, the device (600) may not correspond to any of the UE (110), RAN node (170), network element (190), or TRP shown in FIG. 4 and FIG. 5, and, for example, the device (600) may be part of a self-configuring / optimizing network (SON) node, such as one in the cloud.

[0097] The device (600) may also be distributed throughout the network (e.g., 100), including inside and between the device (600) and any network element (e.g., network control element (NCE) (190) and / or RAN node (170) and / or UE (110) and / or any of the TRPs shown in FIG. 4 and FIG. 5).

[0098] The interface (612) enables data communication between various items of the device (600) as illustrated in FIG. 6. For example, the interface (612) may be one or more buses, such as an address, data, or control bus, and may include any interconnection mechanism, such as a series of lines of a motherboard or integrated circuit, optical fibers, or other optical communication equipment. The computer program code (605) including control (606) may include object-oriented software configured to transmit data / messages between objects within the computer program code (605). The device (600) may not need to include each of the mentioned functions or may include other functions as well.

[0099] FIG. 7 shows a schematic representation of a non-volatile memory medium (700a (e.g., computer disk (CD) or digital multi-purpose disk (DVD)) and 700b (e.g., Universal Serial Bus (USB) memory stick)) that stores instructions and / or parameters (702) that, when executed by a processor, enable the processor to perform one or more steps of the method described above. The exemplary embodiment may be implemented as a circuit, software, hardware, application logic, or a combination of software, hardware, and application logic. In the exemplary embodiment, the application logic, software, or instruction set is maintained on any computer-readable medium. In the context of the present disclosure, "computer-readable medium" may be any medium or means capable of containing, storing, communicating, propagating, or transmitting instructions in connection with or used by an instruction execution system, device, or device, and may be, for example, a base station, TRP, network node, or user equipment of the exemplary embodiment described above.

[0100] FIG. 8 is an exemplary method (800). In 810, the method comprises the step of receiving a trace reference signal configuration from a network, wherein the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured. In 820, the method comprises the step of using the configuration to perform at least one measurement of at least one parameter, wherein at least one parameter is associated with a trace reference signal. In 830, the method comprises the step of determining whether at least one validity condition associated with at least one measurement is valid. In 840, the method comprises the step of reporting to the network the determination of whether at least one measurement of at least one parameter and at least one validity condition are valid. The method (800) may be performed with user equipment (e.g., UE (110)).

[0101] FIG. 9 is an exemplary method (900). In 910, the method comprises the step of transmitting a trace reference signal configuration to user equipment, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured. In 920, the method comprises the step of receiving a report from user equipment comprising at least one measurement of at least one parameter, at least one parameter associated with the trace reference signal, and a determination of whether at least one validity condition is valid. In 930, the method comprises the step of transmitting at least one measurement and a determination of whether at least one validity condition is valid to at least one transmitting receiving point using a backhaul link. The method (900) may be performed with a network node (e.g., a RAN node (170) or network element(s) (190)).

[0102] The following examples (1-25) are provided and described in this specification.

[0103] Example 1: A device comprising means for receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; means for performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; means for determining whether at least one validity condition associated with the at least one measurement is valid; and means for reporting to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0104] Example 2: In Example 1, the configuration comprises a representation of at least one resource including an anchor resource used for calculating Doppler information, and said anchor resource is a device associated with an anchor transmission receiving point.

[0105] Example 3: In Example 2, the Doppler information calculation comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency difference, a relative signal time difference, or an arrival time difference.

[0106] Example 4: In any one of Examples 1 to 3, the device wherein at least one parameter includes multipath Doppler information.

[0107] Example 5: In Example 4, the device comprises at least one of the following: the Doppler information, a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency, a Doppler spectrum, a quantized Doppler value having multiple bits, or a quantized Doppler difference value having multiple bits.

[0108] Example 6: In any one of Examples 1 to 5, the device wherein at least one validity condition is based on a transmission receiving point (TRP) specific or inter-TRP (inter-TRP) multipath power difference between a plurality of dominant multipath components.

[0109] Example 7: In any one of Examples 1 to 6, the device wherein at least one validity condition is based on the transmission receiving point (TRP) specific or inter-TRP trace reference signal resource application time for Doppler difference calculation.

[0110] Example 8: In any one of Examples 1 to 7, the device wherein at least one validity condition is based on a transmission receiving point (TRP) specific or the difference in measurement times between TRPs for calculating the Doppler difference.

[0111] Example 9: In any one of Examples 1 to 8, the device wherein at least one validity condition is based on the calculation of the arrival time of a transmission receiving point (TRP) specific trace reference signal.

[0112] Example 10: In any one of Examples 1 to 9, the device wherein at least one validity condition is based on a reporting time offset.

[0113] Example 11: In any one of Examples 1 to 10, the report of the determination of whether the at least one validity condition is valid includes a device that includes a default mode for the case where the at least one validity condition is valid.

[0114] Example 12: In any one of Examples 1 to 11, the report of the determination of whether the at least one validity condition is valid includes a fallback mode for the case where at least one of the at least one validity condition is invalid.

[0115] Example 13: A device comprising means for transmitting a trace reference signal configuration to user equipment, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; means for receiving from the user equipment a report comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid, wherein the at least one parameter is associated with a trace reference signal; and means for transmitting the at least one measurement and the determination of whether the at least one validity condition is valid to at least one transmission receiving point using a backhaul link.

[0116] Example 14: In Example 13, the configuration comprises a representation of at least one resource including an anchor resource used for calculating Doppler information, said anchor resource being a device associated with an anchor transmission receiving point.

[0117] Example 15: In Example 14, the Doppler information calculation comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency difference, a relative signal time difference, or an arrival time difference.

[0118] Example 16: In any one of Examples 13 to 15, the device wherein at least one parameter includes multipath Doppler information.

[0119] Example 17: In Example 16, the device comprises at least one of the following: the Doppler information, a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and the resource associated with another transmission receiving point, a Doppler frequency, a Doppler spectrum, a quantized Doppler value having multiple bits, or a quantized Doppler difference value having multiple bits.

[0120] Example 18: In any one of Examples 13 to 17, the device wherein the at least one validity condition is based on at least one of a transmission receiving point (TRP) specific or inter-TRP multipath power difference between a plurality of dominant multipath components, a time for applying TRP specific or inter-TRP trace reference signal resources for Doppler difference calculation, a difference in TRP specific or inter-TRP measurement times for Doppler difference calculation, and a time of arrival calculation or reporting time offset of a TRP specific trace reference signal.

[0121] Example 19: An apparatus in which, in any one of Examples 13 to 18, the report of the determination of whether the at least one validity condition is valid includes a default mode and a fallback mode, wherein the default mode is for the case where the at least one validity condition is valid and the fallback mode is for the case where at least one of the at least one validity condition is not valid.

[0122] Example 20: A device comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code together with the at least one processor are configured to enable the device to at least receive a trace reference signal configuration from a network—the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured—, perform at least one measurement of the at least one parameter using the configuration—the at least one parameter is associated with a trace reference signal—determine whether at least one validity condition associated with the at least one measurement is valid, and report to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0123] Example 21: A device comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code together with the at least one processor are configured to enable the device to transmit a trace reference signal configuration to at least one user device, wherein the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured, receive from the user device a report comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid, wherein the at least one parameter is associated with a trace reference signal, and transmit the determination of whether the at least one measurement and the at least one validity condition are valid to at least one transmission receiving point using a backhaul link.

[0124] Example 22: A machine-readable non-transient program storage device, wherein the machine-executable program of instructions is tangibly included to perform operations, the operations comprising: receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with the trace reference signal; determining whether at least one validity condition associated with the at least one measurement is valid; and reporting to the network the determination of whether the at least one measurement of the at least one parameter and the at least one validity condition are valid.

[0125] Example 23: A machine-readable non-transient program storage device, wherein the machine-executable program of instructions is tangibly included to perform operations, the operations comprising: an operation of transmitting a trace reference signal configuration to a user device, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; an operation of receiving a report from the user device comprising a determination of whether at least one measurement of the at least one parameter and at least one validity condition are valid, wherein the at least one parameter is associated with the trace reference signal; and an operation of transmitting the determination of whether the at least one measurement and at least one validity condition are valid to at least one transmission receiving point using a backhaul link.

[0126] Example 24: A method comprising the steps of receiving a trace reference signal configuration from a network, wherein the configuration includes at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; determining whether the at least one validity condition associated with the at least one measurement is valid; and reporting to the network the at least one measurement of the at least one parameter and the determination of whether the at least one validity condition is valid.

[0127] Example 25: In Example 24, the configuration comprises a representation of at least one resource including an anchor resource used for calculating Doppler information, and the anchor resource is associated with an anchor transmission receiving point.

[0128] Example 26: In Example 25, the Doppler information calculation comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency difference, a relative signal time difference, or an arrival time difference.

[0129] Example 27: A method in any one of Examples 24 to 26, wherein at least one parameter includes multipath Doppler information.

[0130] Example 28: A method in Example 27, wherein the Doppler information comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency, a Doppler spectrum, a quantized Doppler value having multiple bits, or a quantized Doppler difference value having multiple bits.

[0131] Example 29: A method in any one of Examples 24 to 28, wherein the at least one validity condition is based on a transmission receiving point (TRP) specific or inter-TRP (inter-TRP) multipath power difference between a plurality of dominant multipath components.

[0132] Example 30: In any one of Examples 24 to 29, the at least one validity condition is based on the transmission receiving point (TRP) specific or inter-TRP trace reference signal resource application time for Doppler difference calculation.

[0133] Example 31: In any one of Examples 24 to 30, the at least one validity condition is based on a transmission receiving point (TRP) specific or a difference in measurement time between TRPs for calculating the Doppler difference.

[0134] Example 32: In any one of Examples 24 to 31, the method wherein at least one validity condition is based on the calculation of the arrival time of a transmission receiving point (TRP) specific trace reference signal.

[0135] Example 33: In any one of Examples 24 to 32, the method wherein at least one validity condition is based on a reporting time offset.

[0136] Example 34: In any one of Examples 24 to 33, the reporting of the determination of whether the at least one validity condition is valid includes a default mode for the case where the at least one validity condition is valid.

[0137] Example 35: In any one of Examples 24 to 34, the reporting of the determination of whether the at least one validity condition is valid includes a fallback mode for the case where at least one of the at least one validity condition is invalid.

[0138] Example 36: A method comprising the steps of: transmitting a trace reference signal configuration to a user device, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured; receiving a report from the user device comprising at least one measurement of the at least one parameter and a determination of whether the at least one validity condition is valid, wherein the at least one parameter is associated with a trace reference signal; and transmitting the at least one measurement and the determination of whether the at least one validity condition is valid to at least one transmission receiving point using a backhaul link.

[0139] Example 37: In Example 36, the configuration comprises a representation of at least one resource including an anchor resource used for calculating Doppler information, and the anchor resource is associated with an anchor transmission receiving point.

[0140] Example 38: In Example 37, the Doppler information calculation comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency difference, a relative signal time difference, or an arrival time difference.

[0141] Example 39: A method in any one of Examples 36 to 38, wherein at least one parameter includes multipath Doppler information.

[0142] Example 40: A method in Example 39, wherein the Doppler information comprises at least one of a multipath Doppler shift, a multipath Doppler shift difference between the anchor resource associated with the anchor transmission receiving point and a resource associated with another transmission receiving point, a Doppler frequency, a Doppler spectrum, a quantized Doppler value having multiple bits, or a quantized Doppler difference value having multiple bits.

[0143] Example 41: In any one of Examples 36 to 40, the at least one validity condition is based on at least one of a transmission receiving point (TRP) specific or inter-TRP multipath power difference between a plurality of dominant multipath components, a time for applying TRP specific or inter-TRP trace reference signal resources for calculating Doppler difference, a difference in TRP specific or inter-TRP measurement times for calculating Doppler difference, and a time of arrival of a TRP specific trace reference signal, or a reporting time offset.

[0144] Example 42: A method in which, in any one of Examples 36 to 41, the report of the determination of whether the at least one validity condition is valid includes a default mode and a fallback mode, wherein the default mode is for the case where the at least one validity condition is valid and the fallback mode is for the case where at least one of the at least one validity condition is not valid.

[0145] References to "computer," "processor," etc., should be understood to include not only computers with various architectures, such as single / multi-processor architectures and sequential or parallel architectures, but also specialized circuits such as Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), signal processing devices, and other processing circuits. References to "computer program," "instruction," "code," etc., should be understood to include software for programmable processors or firmware, such as programmable content of hardware devices, whether it be instructions for a processor or configuration settings for fixed-function devices, gate arrays, or programmable logic devices.

[0146] The memory described herein may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-transient memory, transient memory, fixed memory, and removable memory. The memory(s) may include a database for storing data.

[0147] As used herein, the term “circuit” may refer to a circuit such as (a) a hardware circuit implementation, such as an implementation in an analog and / or digital circuit; (b) a combination of a circuit and software (and / or firmware), e.g. (where applicable): (i) a combination of processor(s) or (ii) a part of processor(s) / software including digital signal processor(s), software, and memory(s) that work together to enable a device to perform various functions; or (c) a circuit such as a microprocessor(s) or a part of a microprocessor(s) for which software or firmware is required for operation even if the software or firmware is not physically present. As another example, as used herein, the term “circuit” also encompasses an implementation of a processor (or a number of processors) or a part of a processor and the software and / or firmware accompanying it (or these). The term “circuit” also encompasses, for example, a baseband integrated circuit or an application processor integrated circuit for a mobile phone, or a similar integrated circuit within a server, a cellular network device, or other network device, where applicable to a specific element.

[0148] In the diagram, arrows between individual blocks indicate the operational coupling between them and the direction of data flow in that coupling.

[0149] It should be understood that the foregoing description is merely illustrative. A person skilled in the art may devise various alternatives and modifications. For example, features mentioned in various dependent claims may be combined with one another in any appropriate combination(s). Additionally, features of the various embodiments described above may optionally be combined into new embodiments. Accordingly, this detailed description is intended to encompass all alternatives, modifications, and variations that fall within the scope of the appended claims.

[0150] The following abbreviations and abbreviations found in the specifications and / or drawings are defined as follows (abbreviations and abbreviations may be joined together or joined using other characters, e.g., dashes or hyphens).

[0151] 4G 4th generation

[0152] 5G 5th generation

[0153] 5GC 5G Core Network

[0154] AI Artificial Intelligence

[0155] AMF Access and Mobility Management Features

[0156] AP aperioditic

[0157] ASIC Application-Specific Integrated Circuit

[0158] BW Bandwidth

[0159] CJT Coherent Joint Transmission

[0160] CoMP tuned multipoint

[0161] CP cyclic prefix

[0162] CP-OFDM cyclic prefix orthogonal frequency division multiplexing

[0163] CPU Central Processing Unit

[0164] CSI Channel Status / Status Information

[0165] CU central unit or centralized unit

[0166] DCI Downlink Control Information

[0167] DL Download Link

[0168] DMRS or DM-RS demodulation reference signal

[0169] DSP Digital Signal Processor

[0170] DU distribution unit

[0171] eNB evolved Node B (e.g., LTE base station)

[0172] EN-DC E-UTRAN New Radio - Dual Connection

[0173] A node that provides NR user plane and control plane protocol termination for the en-gNB UE and acts as an auxiliary node in the EN-DC.

[0174] E-UTRA, Evolved Universal Terrestrial Wireless Access, i.e., LTE Wireless Access Technology

[0175] E-UTRAN E-UTRA Network

[0176] Interface between F1 CU and DU

[0177] FDD Frequency Division Duplex

[0178] FPGA Field Programming Gate Array

[0179] FR frequency range

[0180] gNB is a base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination for UEs and is connected to the 5GC via the NG interface.

[0181] HST high-speed train

[0182] IAB Integrated Access and Backhaul

[0183] ID identifier

[0184] I / F interface

[0185] JT Joint Transmission

[0186] I / O Input / Output

[0187] L-bit L-bit number

[0188] LMF location management function

[0189] LoS Vision

[0190] LTE Long Term Evolution (4G)

[0191] MAC Media Access Control

[0192] max maximum

[0193] MCS Modulation and Coding Methods

[0194] M-IDFT: Inverse Discrete Fourier Transform of Size M

[0195] MIMO Multiple Input Multiple Output

[0196] ML Machine Learning

[0197] MME Mobility Management Entity

[0198] Optimization of MRO Mobility Robustness

[0199] mTRP Multi-TRP

[0200] MU Multi-User

[0201] NCE Network Control Element

[0202] NCJT or NC-JT non-coherent joint transmission

[0203] ng or NG new generation

[0204] ng-eNB New Generation eNB

[0205] NG-RAN New Generation Wireless Access Network

[0206] NR New Radio (5G)

[0207] N / W network

[0208] NZP non-zero power

[0209] OFDM Orthogonal Frequency Division Multiplexing

[0210] P, for example, the number of P-continuous TRS transmission opportunities

[0211] PCI physical cell identifier

[0212] PDA Personal Digital Assistant

[0213] PDCP Packet Data Convergence Protocol

[0214] PDSCH Physical Downlink Sharing Channel

[0215] PHY physical layer

[0216] PRB Physical Resource Block

[0217] pre-comp pre-compensation

[0218] PUSCH physical uplink sharing channel

[0219] P / SP periodic or semi-persistent

[0220] Q bit vector length

[0221] QCL quasi co-location

[0222] R1 Wireless Layer 1

[0223] RAM Random Access Memory

[0224] RAN wireless access network

[0225] Rel-Release

[0226] RIC RAN Intelligent Controller

[0227] RLC wireless link control

[0228] ROM read-only memory

[0229] RP RAN meeting

[0230] RRC Wireless Resource Control (Protocol)

[0231] RRH remote wireless head

[0232] RS reference signal

[0233] RSRP reference signal reception power

[0234] RU wireless unit

[0235] Rx or RX receiver or receiver

[0236] SDAP Service Data Adaptation Protocol

[0237] SFN single frequency network

[0238] SGW Serving Gateway

[0239] SINR Signal-to-Interference Noise Ratio

[0240] SMF Session Management Function

[0241] SON Self-Configured / Optimized Network

[0242] SP semi-permanent

[0243] SRS sounding reference signal

[0244] SSB synchronization signal block

[0245] sTRP single TRP

[0246] TCI transmission configuration display

[0247] TDD time-sharing duplex

[0248] Tdoc technical documentation

[0249] TRP transmission receiving point

[0250] TRS or TRS trace reference signal

[0251] TS Technical Specifications

[0252] Tx or TX transmitter or transmission

[0253] Existing dual codebook structure for Type I CSI feedback

[0254] Feedback targeting high-resolution CSI acquisition for Type II Multi-User Multi-Input and Multi-Output (MU-MIMO) operation

[0255] UAV (Unmanned Aerial Vehicle)

[0256] UE user equipment (e.g., wireless, typically mobile devices)

[0257] UL Uplink

[0258] UPF User Plane Function

[0259] URLLC ultra-reliable low-latency communication

[0260] WID Task Item Description

[0261] Network interfaces between X2 RAN nodes and between the RAN and the core network

[0262] Xn NG-RAN network interface between nodes

Claims

Claim 1 A device comprising: means for receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with said at least one parameter to be measured, and said at least one parameter comprises multipath Doppler information including a Doppler shift difference between transmission receiving points (TRPs); means for performing at least one measurement of said at least one parameter using said configuration, wherein said at least one parameter is associated with a trace reference signal; means for determining whether at least one validity condition associated with said at least one measurement is valid, wherein said at least one validity condition is based on at least one of (i) a TRP-specific or inter-TRP trace reference signal resource application time for calculating a Doppler difference, (ii) a difference in TRP-specific or inter-TRP measurement times for calculating a Doppler difference, or (iii) a calculation of the arrival time of a TRP-specific trace reference signal; and means for reporting to said network the determination of whether said at least one measurement of said at least one parameter and said at least one validity condition are valid. Claim 2 A device according to claim 1, wherein the at least one validity condition is based on a TRP-specific or TRP-inter-multipath power difference between a plurality of dominant multipath components. Claim 3 A device according to claim 1 or 2, wherein at least one validity condition is based on a reporting time offset. Claim 4 A device according to claim 1 or 2, wherein the report of the determination of whether the at least one validity condition is valid includes a default mode for the case where the at least one validity condition is valid. Claim 5 A device according to claim 1 or 2, wherein the report of the determination of whether at least one validity condition is valid includes a fallback mode for the case where at least one of the at least one validity condition is not valid. Claim 6 A device comprising: means for transmitting a trace reference signal configuration to user equipment, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with said at least one parameter to be measured, and said at least one parameter comprises multipath Doppler information including a Doppler shift difference between transmission receiving points (TRPs); means for receiving a report from said user equipment comprising a determination of whether at least one measurement of said at least one parameter and said at least one validity condition are valid, wherein said at least one parameter is associated with a trace reference signal, and said at least one validity condition is based on at least one of (i) a TRP-specific or inter-TRP trace reference signal resource application time for calculating a Doppler difference, (ii) a difference in TRP-specific or inter-TRP measurement times for calculating a Doppler difference, or (iii) a calculation of the arrival time of a TRP-specific trace reference signal; and means for transmitting said at least one measurement and said determination of whether said at least one validity condition are valid to at least one transmission receiving point using a backhaul link. Claim 7 A method comprising: receiving a trace reference signal configuration from a network, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured, wherein the at least one parameter comprises multipath Doppler information including a Doppler shift difference between transmission receiving points (TRPs); performing at least one measurement of the at least one parameter using the configuration, wherein the at least one parameter is associated with a trace reference signal; determining whether at least one validity condition associated with the at least one measurement is valid, wherein the at least one validity condition is based on at least one of (i) a TRP-specific or inter-TRP trace reference signal resource application time for calculating a Doppler difference, (ii) a difference in TRP-specific or inter-TRP measurement times for calculating a Doppler difference, or (iii) a calculation of the arrival time of a TRP-specific trace reference signal; and reporting to the network the determination of whether the at least one measurement of the at least one parameter and the at least one validity condition are valid. Claim 8 A method comprising the steps of: transmitting a trace reference signal configuration to a user device, wherein the configuration comprises at least one parameter to be measured and at least one validity condition associated with the at least one parameter to be measured, and wherein the at least one parameter comprises multipath Doppler information including a Doppler shift difference between transmission receiving points (TRPs); receiving a report from the user device comprising a determination of whether at least one measurement of the at least one parameter and at least one validity condition are valid, wherein the at least one parameter is associated with a trace reference signal, and the at least one validity condition is based on at least one of (i) a TRP-specific or inter-TRP trace reference signal resource application time for calculating a Doppler difference, (ii) a difference in TRP-specific or inter-TRP measurement times for calculating a Doppler difference, or (iii) a calculation of the arrival time of a TRP-specific trace reference signal; and transmitting the determination of whether the at least one measurement and at least one validity condition are valid to at least one transmission receiving point using a backhaul link. Claim 9 delete Claim 10 delete Claim 11 delete Claim 12 delete Claim 13 delete Claim 14 delete Claim 15 delete

Images