Time drift information associated with timing group delays

Abstract

In one aspect, a communication node (e.g., a TRP or a UE) obtains (e.g., measures) timing group delays associated with different positioning procedures to determine time drift information and reports the time drift information to an external entity for position estimation.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims the benefit of U.S. Provisional Application No. 63 / 022,273, entitled "TIME DRIFT INFORMATION ASSOCIATED WITH HARDWARE GROUP DELAYS," filed May 8, 2020, and U.S. Non-Provisional Application No. 17 / 245,422, entitled "TIME DRIFT INFORMATION ASSOCIATED WITH TIMING GROUP DELAYS," filed April 30, 2021, both of which are assigned to the assignee of the present application and are expressly incorporated by reference in their entireties herein.

[0002] Aspects of the present disclosure relate generally to wireless communications, and more particularly, to time drift information associated with timing group delays. [Background technology]

[0003] Wireless communication systems have evolved through various generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including interim 2.5G networks), third generation (3G) high speed data, Internet-enabled wireless service, and fourth generation (4G) service (e.g., LTE or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular systems and personal communication service (PCS) systems. Examples of known cellular systems include Cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Access (GSM) variants of TDMA, and the like.

[0004] The fifth generation (5G) wireless standard, called New Radio (NR), will allow, among other improvements, higher data rates, a larger number of connections, and better coverage. According to the Next Generation Mobile Network Alliance, the 5G standard is designed to provide data rates of tens of megabits per second to each of tens of thousands of users, providing 1 gigabit per second to dozens of workers on an office floor. To support large-scale wireless deployments, hundreds of thousands of simultaneous connections should be supported. Thus, the spectral efficiency of 5G mobile communications should be significantly increased compared to the current 4G standard. Furthermore, compared to the current standard, signaling efficiency should be increased and latency should be significantly reduced. Summary of the Invention [Means for solving the problem]

[0005] The following presents a simplified summary relevant to one or more aspects disclosed herein. As such, the following summary is not intended to be an extensive overview relevant to all contemplated aspects, nor is it intended to identify key or critical elements relevant to all contemplated aspects or to delineate the scope relevant to any particular aspect. As such, the following summary has the sole purpose of presenting some concepts relevant to one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0006] In one aspect, a method of operating a transmit receiving point (TRP) includes acquiring first timing information including a first timing group delay at a first time in association with a first positioning procedure between a first user equipment (UE) and the TRP, acquiring second timing information including a second timing group delay at a second time in association with a second positioning procedure between a second UE and the TRP, determining time drift information associated with the first and second timing group delays, and reporting the time drift information to an external entity.

[0007] In one aspect, a method of operating a user equipment (UE) includes acquiring first timing information including a first timing group delay at a first time in association with a first positioning procedure between the UE and a first transmit receiving point (TRP), acquiring second timing information including a second timing group delay at a second time in association with a second positioning procedure between the UE and a second TRP, determining time drift information associated with the first and second timing group delays, and reporting the time drift information to an external entity.

[0008] In one aspect, a method of operating an entity includes receiving, from a transmit receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information obtained at the TRP at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP and the second positioning procedure being between a second UE and the TRP; and determining a positioning estimate based at least in part on the time drift information.

[0009] In one aspect, a method of operating an entity includes receiving, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information obtained at the UE at first and second times in association with first and second positioning procedures, respectively, where the first positioning procedure is between the UE and a first transmit reception point (TRP) and the second positioning procedure is between the UE and the second TRP; and determining a position estimate for the UE based at least in part on the time drift information.

[0010] In one aspect, a transmit receiving point (TRP) includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, where the at least one processor is configured to obtain first timing information including a first timing group delay at a first time in association with a first positioning procedure between a first user equipment (UE) and the TRP, obtain second timing information including a second timing group delay at a second time in association with a second positioning procedure between a second UE and the TRP, determine time drift information associated with the first and second timing group delays, and report the time drift information to an external entity.

[0011] In one aspect, a user equipment (UE) includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to obtain first timing information including a first timing group delay at a first time in association with a first positioning procedure between the UE and a first transmit receiving point (TRP), obtain second timing information including a second timing group delay at a second time in association with a second positioning procedure between the UE and a second TRP, determine time drift information associated with the first and second timing group delays, and report the time drift information to an external entity.

[0012] In one aspect, the entity includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive, from a transmit receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information obtained at the TRP at first and second times in association with first and second positioning procedures, respectively, wherein the first positioning procedure is between a first user equipment (UE) and the TRP and the second positioning procedure is between a second UE and the TRP, and to determine a positioning estimate based at least in part on the time drift information.

[0013] In one aspect, the entity includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information obtained at the UE at first and second times in association with first and second positioning procedures, respectively, wherein the first positioning procedure is between the UE and a first transmit reception point (TRP) and the second positioning procedure is between the UE and a second TRP, and to determine a position estimate of the UE based at least in part on the time drift information.

[0014] In one aspect, a transmit receiving point (TRP) includes means for acquiring first timing information including a first timing group delay at a first time in association with a first positioning procedure between a first user equipment (UE) and the TRP, means for acquiring second timing information including a second timing group delay at a second time in association with a second positioning procedure between a second UE and the TRP, means for determining time drift information associated with the first and second timing group delays, and means for reporting the time drift information to an external entity.

[0015] In one aspect, a user equipment (UE) includes means for acquiring first timing information including a first timing group delay at a first time in association with a first positioning procedure between the UE and a first transmit receiving point (TRP), means for acquiring second timing information including a second timing group delay at a second time in association with a second positioning procedure between the UE and a second TRP, means for determining time drift information associated with the first and second timing group delays, and means for reporting the time drift information to an external entity.

[0016] In one aspect, the entity includes means for receiving, from a transmitting receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information obtained at the TRP at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP and the second positioning procedure being between a second UE and the TRP; and means for determining a positioning estimate based at least in part on the time drift information.

[0017] In one aspect, the entity includes means for receiving, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information obtained at the UE at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between the UE and a first transmit reception point (TRP) and the second positioning procedure being between the UE and a second TRP; and means for determining a position estimate of the UE based at least in part on the time drift information.

[0018] In one aspect, a non-transitory computer-readable medium storing a set of instructions comprising one or more instructions that, when executed by one or more processors of a transmit receiving point (TRP), cause the TRP to obtain first timing information including a first timing group delay at a first time in association with a first positioning procedure between a first user equipment (UE) and the TRP, obtain second timing information including a second timing group delay at a second time in association with a second positioning procedure between a second UE and the TRP, determine time drift information associated with the first and second timing group delays, and report the time drift information to an external entity.

[0019] In one aspect, a non-transitory computer-readable medium storing a set of instructions comprising one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to obtain first timing information including a first timing group delay at a first time in association with a first positioning procedure between the UE and a first transmit receiving point (TRP), obtain second timing information including a second timing group delay at a second time in association with a second positioning procedure between the UE and a second TRP, determine time drift information associated with the first and second timing group delays, and report the time drift information to an external entity.

[0020] In one aspect, a non-transitory computer-readable medium storing a set of instructions comprising one or more instructions that, when executed by one or more processors of an entity, cause the entity to receive, from a transmit receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information obtained at the TRP at first and second times in association with first and second positioning procedures, respectively, wherein the first positioning procedure is between a first user equipment (UE) and the TRP and the second positioning procedure is between a second UE and the TRP, and to determine a positioning estimate based at least in part on the time drift information.

[0021] In one aspect, a non-transitory computer-readable medium storing a set of instructions comprising one or more instructions that, when executed by one or more processors of an entity, cause the entity to receive, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information obtained at the UE at first and second times in association with first and second positioning procedures, respectively, where the first positioning procedure is between the UE and a first transmit reception point (TRP) and the second positioning procedure is between the UE and a second TRP, and determine a position estimate of the UE based at least in part on the time drift information.

[0022] Other objects and advantages associated with the embodiments disclosed herein will become apparent to one of ordinary skill in the art based on the accompanying drawings and detailed description.

[0023] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate the aspects and not to limit the aspects. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 illustrates an example wireless communication system in accordance with various aspects. [Figure 2A] FIG. 1 illustrates an example wireless network structure in accordance with various aspects. [Figure 2B] FIG. 1 illustrates an example wireless network structure in accordance with various aspects. [Diagram 3] 1 is a block diagram illustrating an example UE in accordance with various aspects. [Figure 4A] FIG. 2 illustrates an example frame structure according to an aspect of the present disclosure. [Figure 4B] FIG. 2 illustrates an example of channels within a frame structure according to an aspect of the present disclosure. [Diagram 5] FIG. 1 illustrates an example technique for determining a location of a UE using information obtained from multiple base stations. [Figure 6] 5 illustrates an example timing diagram of round trip time (RTT) measurement signals exchanged between a base station and a UE in accordance with an aspect of the present disclosure. [Figure 7] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 8] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 9] 4 illustrates an example timing diagram of RTT measurement signals exchanged between a base station and a UE in accordance with an aspect of the disclosure. [Figure 10] FIG. 1000 illustrates an example timing of RTT measurement signals exchanged between a base station (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) in accordance with another aspect of the present disclosure. [Figure 11] FIG. 1100 illustrates example timing of RTT measurement signals exchanged between a base station (gNB) (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) in accordance with an aspect of the present disclosure. [Figure 12] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 13] FIG. 1 illustrates a PRS resource allocation according to one embodiment of the present disclosure. [Figure 14] FIG. 13 illustrates a PRS resource allocation according to another embodiment of the present disclosure. [Figure 15] FIG. 2 illustrates an exemplary PRS instance configuration according to one embodiment of the present disclosure. [Figure 16] FIG. 2 illustrates a positioning session comprising a series of PRS instances according to one embodiment of the present disclosure. [Figure 17] FIG. 1 illustrates an example method of wireless communication according to an aspect of the present disclosure. [Figure 18] FIG. 1 illustrates an example method of wireless communication according to an aspect of the present disclosure. [Figure 19] FIG. 18 illustrates an example implementation of the process of FIG. 17 according to an aspect of the present disclosure. [Figure 20] FIG. 18 illustrates an example implementation of the process of FIG. 17 according to an aspect of the present disclosure. [Figure 21] FIG. 20 illustrates an example implementation of the process of FIG. 18 according to an aspect of the present disclosure. [Figure 22] FIG. 20 illustrates an example implementation of the process of FIG. 18 according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Aspects of the present disclosure are provided in the following description and associated drawings, directed to various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure.

[0026] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" should not necessarily be construed as preferred or advantageous over other aspects. Similarly, the term "aspects of the present disclosure" does not require that all aspects of the present disclosure include the described feature, advantage or mode of operation.

[0027] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0028] Furthermore, many aspects are described in terms of sequences of actions to be performed, for example, by elements of a computing device. It will be appreciated that various actions described herein may be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, a sequence of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or instruct the associated processors of the device to perform the functions described herein. Thus, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. Furthermore, for each of the aspects described herein, the corresponding form of any such aspect may be described herein, for example, as "logic configured to" perform the described actions.

[0029] The terms "user equipment" (UE) and "base station" as used herein are not intended to be specific or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable (e.g., a smart watch, smart glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., an automobile, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at some times) and may communicate with a radio access network (RAN). The term "UE" as used herein may be referred to interchangeably as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or UT, "mobile terminal", "mobile station", or variations thereof. In general, a UE may communicate with a core network via a RAN, through which the UE may be connected to external networks, such as the Internet, and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on IEEE 802.11, etc.), etc.

[0030] A base station may operate according to one of several RATs in communication with a UE depending on the network in which the base station is deployed and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), New Radio (NR) Node B (also referred to as gNB or gNode B), etc. Additionally, in some systems, the base station may simply provide edge node signaling functionality, while in other systems, the base station may provide additional control and / or network management functionality. A communication link through which a UE may send signals to a base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station may send signals to a UE is referred to as a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse traffic channel or a DL / forward traffic channel.

[0031] The term "base station" may refer to a single physical transmission point or multiple physical transmission points that may or may not be collocated. For example, when the term "base station" refers to a single physical transmission point, the physical transmission point may be an antenna of the base station corresponding to a cell of the base station. When the term "base station" refers to multiple collocated physical transmission points, the physical transmission point may be an array of antennas of the base station (e.g., in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical transmission points, the physical transmission point may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, a non-collocated physical transmission point may be a serving base station that receives measurement reports from the UE and neighboring base stations whose reference RF signals the UE is measuring.

[0032] An "RF signal" comprises electromagnetic waves of a given frequency that transport information through space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through a multipath channel. The same transmitted RF signal on different paths between a transmitter and a receiver is sometimes referred to as a "multipath" RF signal.

[0033] According to various aspects, FIG. 1 illustrates an exemplary wireless communication system 100. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In an aspect, the macrocell base stations may include eNBs, if the wireless communication system 100 corresponds to an LTE network, or gNBs, if the wireless communication system 100 corresponds to a 5G network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0034] The base stations 102 collectively form a RAN and may interface with a core network 170 (e.g., Evolved Packet Core (EPC) or Next Generation Core (NGC)) through the backhaul links 122 and through the core network 170 to one or more location servers 172. In addition to other functions, the base stations 102 may perform functions related to one or more of forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracing, RAN Information Management (RIM), paging, positioning, and distribution of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / NGC) via the backhaul links 134, which may be wired or wireless.

[0035] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base station 102 in each coverage area 110. A "cell" is a logical communication entity used to communicate with the base station (e.g., over some frequency resource called a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. In some cases, the term "cell" may refer to a geographic coverage area (e.g., a sector) of a base station as long as the carrier frequency can be detected and used for communication within some portion of the geographic coverage area 110.

[0036] The geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in handover regions) and some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that significantly overlaps with the coverage area 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include Home eNBs (HeNBs) that may serve restricted groups called Closed Subscriber Groups (CSGs).

[0037] The communication link 120 between the base station 102 and the UE 104 may include UL (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be through one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL).

[0038] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a WLAN station (STA) 152 over a communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in the unlicensed frequency spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform clear channel assessment (CCA) before communicating to determine if a channel is available.

[0039] The small cell base station 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or 5G technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE / 5G in an unlicensed frequency spectrum may extend coverage to and / or increase capacity of an access network. LTE in an unlicensed spectrum may be referred to as LTE Unlicensed (LTE-U), Licensed Assisted Access (LAA), or MulteFire.

[0040] The wireless communication system 100 may further include a mmW base station 180 in communication with the UE 182 and may operate in millimeter wave (mmW) and / or sub-mmW frequencies. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has wavelengths between 1 and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may extend down to frequencies of 3 GHz with wavelengths of 100 millimeters. The very high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW / sub-mmW radio frequency bands have high path losses and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely high path losses and short distances. It will be further appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or sub-mmW and beamforming. Therefore, it should be appreciated that the above illustrations are merely illustrative and should not be construed as limiting the various aspects disclosed herein.

[0041] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts it in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and launches a stronger downlink RF signal in that particular direction, thereby providing a faster and stronger RF signal (in terms of data rate) to the receiving device. To change the directionality of an RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship so that the radio waves from the separate antennas combine together to increase radiation in the desired direction while canceling out to suppress radiation in undesired directions.

[0042] A transmit beam may be quasi-collocated, meaning that the transmit beam appears to a receiver (e.g., a UE) to have the same parameters, regardless of whether the network node's own transmit antennas are physically collocated or not. In NR, there are four types of quasi-collocation (QCL) relationships. In particular, a QCL relationship of a given type means that some parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0043] In receive beamforming, a receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase its gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in a direction, it means that the beam gain in that direction is higher compared to the beam gains along other directions, or that the beam gain in that direction is the highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), etc.) of RF signals received from that direction.

[0044] The receive beams may be spatially related. The spatial relationship means that parameters for a transmit beam for a second reference signal may be derived from information about the receive beam for the first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for sending an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0045] It should be noted that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE forms a downlink beam, then it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms an uplink beam, then it is an uplink receive beam, and if the UE forms an uplink beam, then it is an uplink transmit beam.

[0046] In 5G, the frequency spectrum in which wireless nodes (e.g., base station 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges, namely, FR1 (from 450 MHz to 6000 MHz), FR2 (from 24250 MHz to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell on which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. Since both the primary uplink carrier and the primary downlink carrier are typically UE-specific, the secondary carrier may only include necessary signaling information and signals, e.g., signaling information and signals that are UE-specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether a PCell or an SCell) corresponds to the carrier frequency / component carrier over which some base station is communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0047] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (i.e., a "PCell"), and other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20 MHz carriers in a multi-carrier system would lead to a theoretical data rate increase of twice (i.e., 40 MHz) compared to that achieved by a single 20 MHz carrier.

[0048] The wireless communication system 100 may further include one or more UEs, such as UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of FIG. 1, the UE 190 has a D2D P2P link 192 in which one of the UEs 104 is connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 in which the WLAN STA 152 is connected to the WLAN AP 150 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

[0049] The wireless communication system 100 may further include a UE 164, which may communicate with the macrocell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164. In an aspect, the UE 164 may include a positioning component 166, which may enable the UE 164 to perform the UE operations described herein. It should be noted that although only one UE in FIG. 1 is shown as having a fully staggered SRS component 166, any of the UEs in FIG. 1 may be configured to perform the UE operations described herein.

[0050] According to various aspects, FIG. 2A illustrates an exemplary wireless network structure 200. For example, the NGC 210 (also referred to as "5GC") may be functionally viewed as a control plane function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane function 212 (e.g., UE gateway function, access to data network, IP routing, etc.) that work in concert to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the NGC 210, specifically to the control plane function 214 and the user plane function 212. In an additional configuration, the eNB 224 may also be connected to the NGC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of both the eNBs 224 and the gNBs 222. Either the gNBs 222 or the eNBs 224 may be in communication with the UEs 204 (e.g., any of the UEs shown in FIG. 1). Another optional aspect may include a location server 230, which may be in communication with the NGC 210 to provide location assistance for the UEs 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UEs 204 that may be connected to the location server 230 via the core network, the NGC 210, and / or the Internet (not shown). Additionally, the location server 230 may be integrated into components of the core network, or alternatively, may be external to the core network.

[0051] According to various aspects, FIG. 2B illustrates another exemplary wireless network structure 250. For example, the NGC 260 (also referred to as “5GC”) may be functionally viewed as a control plane function provided by an Access and Mobility Management Function (AMF) / User Plane Function (UPF) 264 and a user plane function provided by a Session Management Function (SMF) 262, which work in concert to form a core network (i.e., the NGC 260). A user plane interface 263 and a control plane interface 265 connect the eNB 224 to the NGC 260, specifically to the SMF 262 and the AMF / UPF 264, respectively. In an additional configuration, the gNB 222 may also be connected to the NGC 260 via a control plane interface 265 to the AMF / UPF 264 and a user plane interface 263 to the SMF 262. Additionally, eNB 224 may communicate directly with gNB 222 via backhaul connection 223, with or without gNB direct connectivity to NGC 260. In some configurations, New RAN 220 may have only one or more gNBs 222, while other configurations include one or more of both eNB 224 and gNB 222. Either gNB 222 or eNB 224 may communicate with UE 204 (e.g., any of the UEs shown in FIG. 1). The base stations of New RAN 220 communicate with the AMF side of AMF / UPF 264 via an N2 interface and with the UPF side of AMF / UPF 264 via an N3 interface.

[0052] The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between the UE 204 and the SMF 262, transparent proxy service for routing SM messages, access authentication and access permission, transport for short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and a security anchor function (SEAF). The AMF also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives intermediate keys established as a result of the UE 204 authentication process. In case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF retrieves security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives keys from the SEAF that the SCM uses to derive access network specific keys. The AMF functions also include location service management for regulated services, transport for location service messages between the UE 204 and the Location Management Function (LMF) 270 and between the New RAN 220 and the LMF 270, Evolved Packet System (EPS) bearer identifier allocation for interworking with EPS, and UE 204 mobility event notification. In addition, the AMF also supports functions for non-3GPP access networks.

[0053] The functions of the UPF include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, Quality of Service (QoS) handling for the user plane (e.g., UL / DL rate enforcement, reflective QoS marking in the DL), UL traffic validation (Service Data Flow (SDF) to QoS Flow mapping), transport level packet marking in the UL and DL, DL packet buffering and DL data notification triggering, as well as sending and forwarding one or more "end markers" to the source RAN node.

[0054] The functions of the SMF 262 include session management, allocation and management of UE Internet Protocol (IP) addresses, selection and control of user plane functions, configuration of traffic steering in the UPF to route traffic to the appropriate destination, control of policy enforcement and part of QoS, and downlink data notification. The interface through which the SMF 262 communicates with the AMF side of the AMF / UPF 264 is called the N11 interface.

[0055] Another optional aspect may include an LMF 270, which may be in communication with the NGC 260 to provide location assistance for the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may be connected to the LMF 270 via a core network, the NGC 260, and / or via the Internet (not shown).

[0056] FIG. 3 illustrates several example components (represented by corresponding blocks) that may be incorporated in a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF 270) to support file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include components similar to the illustrated components to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0057] The UE 302 and the base station 304 each include at least one wireless communication device (represented by communication devices 308 and 314 (and communication device 320 if the apparatus 304 is a relay)) for communicating with other nodes via at least one designated RAT. For example, the communication devices 308 and 314 may communicate with each other via a wireless communication link 360, which may correspond to the communication link 120 in FIG. 1. Each communication device 308 includes at least one transmitter (represented by transmitter 310) for transmitting and encoding signals (e.g., messages, instructions, information, pilots, etc.) and at least one receiver (represented by receiver 312) for receiving and decoding signals (e.g., messages, instructions, information, pilots, etc.). Similarly, each communication device 314 includes at least one transmitter (represented by transmitter 316) for transmitting signals (e.g., messages, instructions, information, pilots, etc.) and at least one receiver (represented by receiver 318) for receiving signals (e.g., messages, instructions, information, pilots, etc.). If the base station 304 is a relay station, each communication device 320 may include at least one transmitter (represented by transmitter 322) for transmitting signals (e.g., messages, instructions, information, pilots, etc.) and at least one receiver (represented by receiver 324) for receiving signals (e.g., messages, instructions, information, etc.).

[0058] The transmitter and receiver may in some implementations comprise an integrated device (e.g., embodied as transmitter and receiver circuits in a single communications device, commonly referred to as a "transceiver"), in some implementations may comprise separate transmitter devices and separate receiver devices, or in other implementations may be embodied in other manners. A wireless communications device (e.g., one of a plurality of wireless communications devices) of the base station 304 may also comprise a network listen module (NLM) or the like for performing various measurements.

[0059] The network entity 306 (and the base station 304 if it is not a relay station) includes at least one communication device (represented by communication device 326 and optionally 320) for communicating with other nodes. For example, the communication device 326 may comprise a network interface configured to communicate with one or more network entities via a wire-based or wireless backhaul 370 (which may correspond to the backhaul link 122 of FIG. 1). In some aspects, the communication device 326 may be implemented as a transceiver configured to support wire-based or wireless signal communication, and the transmitter 328 and the receiver 330 may be an integrated unit. This communication may involve, for example, sending and receiving messages, parameters, or other types of information. Thus, in the example of FIG. 3, the communication device 326 is shown as comprising a transmitter 328 and a receiver 330. Alternatively, the transmitter 328 and the receiver 330 may be separate devices within the communication device 326. Similarly, if the base station 304 is not a relay station, the communications device 320 may comprise a network interface configured to communicate with one or more network entities 306 via a wire-based or wireless backhaul 370. Like the communications device 326, the communications device 320 is shown as comprising a transmitter 322 and a receiver 324.

[0060] The devices 302, 304, and 306 also include other components that may be used in conjunction with file transmission operations as disclosed herein. The UE 302 includes a processing system 332, e.g., for providing functionality related to UE operations as described herein and for providing other processing functions. The base station 304 includes a processing system 334, e.g., for providing functionality related to base station operations as described herein and for providing other processing functions. The network entity 306 includes a processing system 336, e.g., for providing functionality related to network function operations as described herein and for providing other processing functions. The devices 302, 304, and 306 each include memory components 338, 340, and 342 (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Additionally, UE 302 includes a user interface 350 for providing instructions (e.g., audible and / or visual instructions) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, devices 304 and 306 may also include user interfaces.

[0061] Referring to the processing system 334 in more detail, on the downlink, IP packets from the network entity 306 may be provided to the processing system 334. The processing system 334 may implement functionality for a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The processing system 334 may provide RRC layer functions related to broadcasting of system information (e.g., Master Information Blocks (MIBs), System Information Blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0062] The transmitter 316 and receiver 318 may implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-ary quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas. The transmitter 316 may modulate an RF carrier with each spatial stream for transmission.

[0063] At the UE 302, the receiver 312 receives the signals through its respective antenna. The receiver 312 recovers the information modulated onto the RF carriers and provides the information to the processing system 332. The transmitter 310 and the receiver 312 implement Layer 1 functions related to various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation points that were most likely transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. The data and control signals are then provided to a processing system 332 that implements Layer 3 and Layer 2 functions.

[0064] In the UL, the processing system 332 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.

[0065] Similar to the functionality described with respect to DL transmission by the base station 304, the processing system 332 provides RRC layer functionality related to system information (e.g., MIBs, SIBs) acquisition, RRC connection, and measurement reporting; PDCP layer functionality related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality related to transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0066] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 310 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the transmitter 310 may be provided to different antennas. The transmitter 310 may modulate an RF carrier with each spatial stream for transmission.

[0067] The UL transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver functions at the UE 302. The receiver 318 receives the signals through its respective antenna. The receiver 318 recovers the information modulated onto the RF carrier and provides the information to the processing system 334.

[0068] In the UL, the processing system 334 performs demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 302. The IP packets from the processing system 334 may be provided to the core network. The processing system 334 is also responsible for error detection.

[0069] In one aspect, the devices 302, 304, and 306 may include positioning components 344, 348, and 349, respectively. It will be appreciated that the functionality of the various positioning components 344, 348, and 349 may vary based on the device in which it is implemented. The positioning components 344, 348, and 349 may be hardware circuits that are part of or coupled to the processing systems 332, 334, and 336, respectively, that, when executed, cause the devices 302, 304, and 306 to perform the functions described herein. Alternatively, the positioning components 344, 348, and 349 may be memory modules stored in the memory components 338, 340, and 342, respectively, that, when executed by the processing systems 332, 334, and 336, cause the devices 302, 304, and 306 to perform the functions described herein.

[0070] For convenience, devices 302, 304, and / or 306 are illustrated in Figure 3 as including various components that may be configured in accordance with various examples described herein, however, it will be appreciated that the depicted blocks may have different functions in different designs.

[0071] The various components of the devices 302, 304, and 306 may communicate with each other via data buses 352, 354, and 356, respectively. The components of FIG. 3 may be implemented in various ways. In some implementations, the components of FIG. 3 may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 308, 332, 338, 344, and 350 may be performed by the processor and memory components of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 314, 320, 334, 340, and 348 may be performed by the processor and memory components of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 326, 336, 342, and 349 may be performed by the processor and memory components of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, activities, and / or functions are described herein as being performed "by a UE," "by a base station," "by a positioning entity," etc. However, it will be appreciated that such operations, activities, and / or functions may actually be performed by a particular component or combination of components, such as a UE, a base station, a positioning entity, etc., such as the processing systems 332, 334, 336, the communications devices 308, 314, 326, the positioning components 344, 348, and 349.

[0072] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs).

[0073] 4A is a diagram 400 illustrating an example of a DL frame structure according to an embodiment of the disclosure. FIG. 4B is a diagram 430 illustrating an example of channels within a DL frame structure according to an embodiment of the disclosure. Other wireless communication technologies may have different frame structures and / or different channels.

[0074] LTE, and possibly NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR has the option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be 15 kHz, and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0075] LTE supports a single numerology (subcarrier spacing, symbol length, etc.). In contrast, NR may support multiple numerologies, e.g., subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 204 kHz or more may be available. Table 1 provided below lists some various parameters for the different NR numerologies.

[0076] [Table 1]

[0077] In the example of Figures 4A and 4B, a numerology of 15 kHz is used. Thus, in the time domain, a frame (e.g., 10 ms) is divided into 10 equal-sized subframes of 1 ms each, with each subframe containing one time slot. In Figures 4A and 4B, time is represented horizontally (e.g., on the X-axis), with time increasing from left to right, while frequency is represented vertically (e.g., on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0078] A resource grid may be used to represent a time slot, with each time slot including one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of Figures 4A and 4B, for a normal cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (OFDM symbols for DL ​​and SC-FDMA symbols for UL) in the time domain for a total of 84 REs. For an extended cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0079] As shown in Figure 4A, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include demodulation reference signals (DMRS) and channel state information reference signals (CSI-RS), example locations of which are labeled "R" in Figure 4A.

[0080] FIG. 4B shows an example of various channels in a DL subframe of a frame. A physical downlink control channel (PDCCH) carries DL control information (DCI) in one or more control channel elements (CCEs), each CCE containing 9 RE groups (REGs), each REG containing 4 consecutive REs in an OFDM symbol. The DCI carries information about UL resource allocation (persistent and non-persistent) and a description of DL data to be transmitted to the UE. Multiple (e.g., up to 8) DCIs may be configured in the PDCCH, and these DCIs may have one of multiple formats. For example, there are various DCI formats for UL scheduling, for non-MIMO DL scheduling, for MIMO DL scheduling, and for UL power control.

[0081] A Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and physical layer identity. A Secondary Synchronization Signal (SSS) is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the DL-RS mentioned above. A Physical Broadcast Channel (PBCH) carrying the MIB may be logically grouped with the PSS and SSS to form an SSB (also called SS / PBCH). The MIB provides the number of RBs in the DL system bandwidth and the system frame number (SFN). A Physical Downlink Shared Channel (PDSCH) carries user data and broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0082] In some cases, the DL RS shown in FIG. 4A may be a positioning reference signal (PRS). The set of resource elements used for the transmission of the PRS is called a "PRS resource." The set of resource elements may span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbols 460 in a slot 430 in the time domain. In a given OFDM symbol 460, the PRS resource occupies consecutive PRBs. The PRS resource is represented by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size N, resource element offset in the frequency domain, starting slot and starting symbol, number of symbols per PRS resource (i.e., duration of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying the PRS. For example, a comb size of comb-4 means that every fourth subcarrier of a given symbol carries the PRS.

[0083] A "PRS resource set" is a set of PRS resources used for transmission of a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same transmit reception point (TRP). A PRS resource ID in a PRS resource set is associated with a single beam transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus a "PRS resource" may also be referred to as a "beam." Note that this has no implication on whether the TRP and the beam on which the PRS is transmitted are known to the UE. A "PRS occasion" is one instance of a periodically repeating time window (e.g., a group of one or more consecutive slots) during which a PRS is expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion," a "positioning occasion," or simply an "occasion."

[0084] It should be noted that the terms "positioning reference signal" and "PRS" sometimes refer to a specific reference signal used for positioning in an LTE system. However, as used herein, unless otherwise specified, the terms "positioning reference signal" and "PRS" refer to any type of reference signal that may be used for positioning, such as, but not limited to, a PRS signal in LTE, a navigation reference signal (NRS) in 5G, a transmitter reference signal (TRS), a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a primary synchronization signal (PSS), a secondary synchronization signal (SSS), an SSB, etc.

[0085] FIG. 5 illustrates an example DL PRS 500 being processed through a wireless communication system according to an embodiment of the disclosure. In FIG. 5, the PRS transmit beams are PRS) over a series of beam-specific positioning occasions on respective slots / symbols. These PRS transmit beams are received at the UE as PRS receive beams and then processed (e.g., various positioning measurements are made by the UE, etc.).

[0086] FIG. 6 illustrates an example wireless communication system 600 according to an aspect of the present disclosure. In FIG. 6, eNB1, eNB2, and eNB3 are synchronized with each other so that TOA (e.g., TDOA) measurements (shown as T1, T2, and T3) can be used to generate a positioning estimate for a UE. Multiple TDOA measurements can be used for triangulation (e.g., four or more cells or eNBs). In a TDOA-based positioning scheme, network synchronization error is the main bottleneck with respect to positioning accuracy.

[0087] Another positioning technique that requires cell (or satellite) synchronization is based on Observed Time Difference of Arrival (OTDOA). One exemplary OTDOA-based positioning scheme is GPS, which is limited to an accuracy of 50-100 ns (e.g., 15-30 meters).

[0088] In NR, there is no requirement for precise timing synchronization across the network. Instead, it is sufficient to have coarse time synchronization across the gNB (e.g., within the cyclic prefix (CP) duration of an OFDM symbol). RTT-based methods generally require only coarse timing synchronization and are therefore the preferred positioning method in NR.

[0089] In network-centric RTT estimation, a serving base station (e.g., base station 102) instructs a UE (e.g., UE 104) to scan / receive RTT measurement signals (e.g., PRS) on serving cells of two or more neighboring base stations (and typically the serving base station, since at least three base stations are required). One or more base stations transmit the RTT measurement signals on low reuse resources (e.g., resources used by base stations to transmit system information) allocated by the network (e.g., location server 230, LMF 270). The UE records the arrival time (also called receive time, reception time, time of reception, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., derived by the UE from a DL signal received from its serving base station), transmits a common or individual RTT response message (e.g., SRS, UL-PRS) to one or more base stations (e.g., when commanded by its serving base station), and calculates the difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx (For example, T in Fig. 9 Rx→Tx 912) may be included in the payload of each RTT response message. The RTT response message will contain a reference signal from which the base station can infer the ToA of the RTT response. The difference T between the transmission time of the RTT measurement signal and the ToA of the RTT response Tx→Rx (For example, T in Fig. 9 Tx→Rx 922) by the difference T Rx→Tx (For example, T in Fig. 9 Rx→Tx 912), the base station can infer the propagation time between the base station and the UE, from which the base station can then determine the distance between the UE and the base station by assuming the speed of light during this propagation time.

[0090] The UE-centric RTT estimation is similar to the network-based method, except that the UE transmits an uplink RTT measurement signal (e.g., when instructed by the serving base station), which is received by multiple base stations in the vicinity of the UE. Each participating base station responds with a downlink RTT response message, which may include in the RTT response message payload the time difference between the ToA of the RTT measurement signal at the base station and the transmission time of the RTT response message from the base station.

[0091] For both network-centric and UE-centric procedures, the party performing the RTT calculation (network or UE) typically (but not always) sends a first message or signal (e.g., an RTT measurement signal) and the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0092] FIG. 7 illustrates an example wireless communication system 700 according to aspects of the disclosure. In the example of FIG. 7, a UE 704 (which may correspond to any of the UEs described herein) is attempting to calculate an estimate of its location or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location. The UE 704 may wirelessly communicate with multiple base stations 702-1, 702-2, and 702-3 (collectively base stations 702, which may correspond to any of the base stations described herein) using RF signals and a standardized protocol for modulation of the RF signals and exchange of information packets. By extracting different types of information from the exchanged RF signals and utilizing the layout of the wireless communication system 700 (i.e., base station locations, geometry, etc.), the UE 704 may determine, or assist in determining, its location in a predefined reference frame. In one aspect, the UE 704 may specify its location using a two-dimensional coordinate system, although the aspects disclosed herein are not so limited and may be applicable to determining location using a three-dimensional coordinate system if additional dimensions are desired. Additionally, while FIG. 7 shows one UE 704 and three base stations 702, it will be appreciated that there may be more UEs 704 and more base stations 702.

[0093] To support position estimation, base stations 702 may be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UEs 704 within their coverage areas to enable the UEs 704 to measure characteristics of such signals. For example, the UE 704 may measure the TOAs of particular reference RF signals (e.g., PRS, NRS, CRS, CSI-RS, etc.) transmitted by at least three different base stations 702 and report these TOAs (and additional information) back to the serving base station 702 or another positioning entity (e.g., location server 230, LMF 270) using an RTT positioning method.

[0094] In one aspect, the UE 704 has been described as measuring a reference RF signal from a base station 702, but the UE 704 may measure a reference RF signal from one of a number of cells supported by the base station 702. If the UE 704 measures a reference RF signal transmitted by a cell supported by the base station 702, the at least two other reference RF signals measured by the UE 704 to perform the RTT procedure will be from cells supported by a base station 702 different from the first base station 702 and may have good or poor signal strength at the UE 704.

[0095] In order to determine the position (x,y) of the UE 704, an entity that determines the position of the UE 704 needs to know the location of the base station 702, which is expressed as (x,y) in the reference coordinate system. k ,y k ), where k=1, 2, 3 in the example of FIG. 7. When one of the base stations 702 (e.g., a serving base station) or the UE 704 determines the location of the UE 704, the location of the involved base station 702 may be provided to the serving base station 702 or UE 704 by a location server (e.g., location server 230, LMF 270) with knowledge of the network geometry. Alternatively, the location server may determine the location of the UE 704 using the known network geometry.

[0096] Either the UE 704 or the respective base station 702 determines the distance (d k , where k=1, 2, 3). In one aspect, determining the RTT 710 of signals exchanged between the UE 704 and any base station 702 may be performed to determine the distance (d k) As described further below, RTT techniques can measure the time between sending a signaling message (e.g., a reference RF signal) and receiving a response. These methods can utilize calibration to remove any processing delay. In some environments, it may be assumed that the processing delays of the UE 704 and the base station 702 are the same. However, such an assumption may not be correct in practice.

[0097] each distance d k Once determined, the UE 704, base station 702, or location server (e.g., location server 230, LMF 270) can solve for the position (x,y) of the UE 704 by using various known geometric techniques, such as, for example, trilateration. From FIG. 7, it can be seen that the position of the UE 704 is ideally at the common intersection of three semicircles, each of which has a radius d k and center(x k ,y k ) where k=1, 2, 3.

[0098] In some instances, additional information may be obtained in the form of a linear direction (e.g., which may be in a horizontal plane or in three dimensions) or possibly an angle of arrival (AoA) or angle of departure (AoD), which define a range of directions (e.g., for the UE 704 from the location of the base station 702). The intersection of the two directions at or near a point (x,y) may provide another estimate of the location for the UE 704.

[0099] A position estimate (e.g., for a UE 704) may be referred to by other names, such as a location estimate, location, position, position fix, fix, etc. A position estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location. A position estimate may further be defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). A position estimate may include an expected error or uncertainty (e.g., by including an area or volume that is expected to contain the location with some specified or default confidence).

[0100] FIG. 8 illustrates an example wireless communication system 800 according to an aspect of the disclosure. FIG. 7 illustrates an example of a multi-cell RTT positioning scheme, while FIG. 8 illustrates an example of a single-cell RTT positioning scheme. In FIG. 8, RTT1 is measured along with AoD1 associated with the beam on which the DL PRS is transmitted from the cell to the UE. The overlapping area of ​​RTT1 and AoD1 illustrated in FIG. 8 provides a coarse location estimate for the associated UE.

[0101] 9 is a diagram 900 illustrating example timing of RTT measurement signals exchanged between a base station 902 (e.g., any of the base stations described herein) and a UE 904 (e.g., any of the UEs described herein) in accordance with an aspect of the disclosure. In the example of FIG. 9, the base station 902 sends an RTT measurement signal 910 (e.g., PRS, NRS, CRS, CSI-RS, etc.) to the UE 904 at time T1. The RTT measurement signal 910 travels from the base station 902 to the UE 904 after a certain propagation delay T Prop At time T2 (the ToA of the RTT measurement signal 910 at the UE 904), the UE 904 receives / measures the RTT measurement signal 910. After some UE processing time, the UE 904 transmits an RTT response signal 920 at time T3. The propagation delay T PropThereafter, the base station 902 receives / measures the RTT response signal 920 from the UE 904 at time T4 (the ToA of the RTT response signal 920 at the base station 902).

[0102] To identify the ToA (e.g., T2) of a reference signal (e.g., RTT measurement signal 910) transmitted by a given network node (e.g., base station 902), the receiver (e.g., UE 904) first jointly processes all resource elements (REs) on the channel on which the transmitter is transmitting the reference signal and performs an inverse Fourier transform to convert the received reference signal into the time domain. The conversion of the received reference signal into the time domain is called an estimation of the channel energy response (CER). The CER indicates the peaks on the channel over time, and therefore the earliest "prominent" peak should correspond to the ToA of the reference signal. In general, the receiver uses a noise-related quality threshold to filter out spurious local peaks, thereby accurately identifying the presumably prominent peaks on the channel. For example, the receiver may choose the ToA estimate that is the earliest local maximum of the CER that is at least X dB higher than the median CER and up to Y dB lower than the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA for each reference signal from a different transmitter.

[0103] The RTT response signal 920 is the difference between time T3 and time T2 (i.e., T Rx→Tx 912). Alternatively, the difference may be derived from the Timing Advance (TA), i.e., the relative UL / DL frame timing and the designated location of the UL reference signal. (Note that TA is typically the RTT between the base station and the UE, or twice the propagation time in one direction.) This measurement and the difference between time T4 and time T1 (i.e., T Tx→Rx922), the base station 902 (or other positioning entity, such as location server 230, LMF 270, etc.) can calculate the distance to the UE 904 as follows:

[0104]

number

[0105] where c is the speed of light.

[0106] 10 illustrates a diagram 1000 illustrating example timing of RTT measurement signals exchanged between a base station (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) in accordance with another aspect of the disclosure. In particular, 1002-1004 in FIG. 10 illustrate portions of frame delay associated with the Rx-Tx difference as measured at the gNB and the UE, respectively.

[0107] A further source of delay or error is due to UE and gNB timing group delay for position location. As used herein, "timing group delay" may include hardware group delay (e.g., due to internal hardware delays between baseband (BB) components and antennas in the UE and gNB). In some cases, timing group delay may further include some delay due to software and / or firmware specific to the UE or gNB.

[0108] FIG. 11 illustrates a diagram 1100 illustrating example timing of RTT measurement signals exchanged between a base station (gNB) (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) according to aspects of the disclosure. FIG. 11 is similar in some respects to FIG. 9. However, in FIG. 11, UE and gNB timing group delays (possibly due primarily to internal hardware delays between baseband (BB) components and antennas at the UE and gNB) are illustrated with respect to 1102-1108 (shown as □Rx and □Tx). As can be appreciated, path- or beam-specific delays on both the Tx and Rx sides affect the RTT measurements.

[0109] 12 illustrates an example wireless communication system 1200 according to an aspect of the disclosure. The wireless communication system 1200 is similar to the wireless communication system 600 of FIG. 6. However, the wireless communication system 1200 further illustrates beams associated with respective TOA (e.g., TDOA) measurements (shown as T1, T2, and T3). As can be appreciated, path- or beam-specific delays on the Rx side affect DL TDOA measurements. Although not explicitly illustrated, path- or beam-specific delays on the Tx side affect UL TDOA measurements as well.

[0110] The accuracy of the positioning estimate at the UE is limited by how fine the group delay / timing error can be maintained at the UE side. For example, 1 ns error for □Rx and □Tx can lead to an approximately 2 foot limit in accuracy. Some 3GPP standards target positioning accuracy of less than 3m (for Rel-16) and less than 1m (general commercial case for Rel-17). Knowledge of the UE and / or gNB timing group delay can thereby help improve location accuracy.

[0111] As used herein, a positioning session may comprise multiple PRS instances, with each PRS instance comprising a PRS resource set. The PRS resource set in turn comprises multiple PRS resources. For example, in some implementations, a positioning session may span approximately 20 seconds, while each PRS instance may span approximately 160 ms. DL PRS resources may be repeated to facilitate Rx beam sweeping across different repetitions, gain combining for coverage extension, and / or in-instance muting. In some designs, the PRS configuration may support a number of repetition counts (PRS-ResourceRepetitionFactor) and a number of time gaps (PRS-ResourceTimeGap), as shown in Table 2.

[0112] [Table 2]

[0113] 13 illustrates a PRS resource allocation 1300 according to one embodiment of the present disclosure. The PRS resource allocation 1300 reflects a DL-PRS resource set with four resources, a PRS-ResourceRepetitionFactor of 4, and a PRS-ResourceTimeGap of 1 slot.

[0114] 14 illustrates a PRS resource allocation 1400 according to another embodiment of the present disclosure. The PRS resource allocation 1400 reflects a DL-PRS resource set with four resources, a PRS-ResourceRepetitionFactor of 4, and a PRS-ResourceTimeGap of 4 slots.

[0115] FIG. 15 illustrates an exemplary PRS instance 1500 configuration according to one embodiment of the present disclosure. The PRS instance 1500 is configured with FR1 TDD, 8 PRS resources per TRP, 30KHz, and DDDSU format (2.5msec). For PRS resources with comb-6 / 6 symbols at a repetition factor of 4, all 8 PRS resources can span a 2.5*8=20msec time window. Assuming that the PRS resource is ON for one of X slots, the above 20msec "PRS instance" will fit all beams of 6*X beams from different TRPs fully muted, and the non-orthogonal remainder (e.g., X=4 would mean that the UE can sample all 8 beams of 24 TRPs fully muted). In FR2, the time span of the PRS instance can easily span a 40msec time window.

[0116] FIG. 16 illustrates a positioning session 1600 with a series of PRS instances according to one embodiment of the present disclosure. Ideally, all measurements used in generating a positioning fix should be made in parallel. If measurements are performed at different times to generate a positioning fix, UE movement and changes to the UE and gNB clocks can cause measurement errors that can ultimately result in position errors. For example, a UE clock drift of 10 parts-per-billion (ppb) can result in a measurement error of 1s*10ns / s=10ns, about 3m, for two measurements taken 1 second apart. UE movement, UE clock drift, and gNB clock drift can cause significantly larger errors for measurements that are all made at different times but are all used to generate the same position fix. In some designs, the central measurement and performance requirement for the UE Rx-Tx time difference applies when the configured SRS-Slot-offset and SRS-Periodicity parameters for SRS resources for positioning are such that any SRS transmission is within [-X,X] msec (e.g., in some designs, X=25 msec) of at least one DL PRS resource from each of the TRPs in the assistance data.

[0117] Differential RTT is another positioning scheme whereby the difference between two RTT measurements (or measurement ranges) is used to generate a positioning estimate for the UE. As an example, the RTT may be estimated between the UE and two gNBs. The positioning estimate for the UE may then be narrowed (e.g., hyperbolically) to the intersection of the geographic ranges that map to these two RTTs. The RTTs to additional gNBs (or to specific TRPs of such gNBs) can further narrow (or make more accurate) the positioning estimate for the UE.

[0118] In some designs, a positioning engine (e.g., at a UE, base station, or server / LMF) may select between whether an RTT measurement is to be used to calculate a positioning estimate using a typical RTT or a differential RTT. For example, if the positioning engine receives an RTT that is known to already account for the timing group delay, a typical RTT positioning is performed (e.g., as shown in FIGS. 6-7). Otherwise, in some designs, a differential RTT is performed so that the timing group delay can be offset. In some designs where the positioning engine is implemented at the network side (e.g., gNB / LMU / eSMLC / LMF), the timing group delay at the UE is not known (or vice versa).

[0119] An example of theoretical Rx-Tx delay measurements between the UE and base stations 1 and 2, respectively, is as follows:

[0120]

number

[0121] Thereby, w denotes the timing group delay.

[0122] As can be seen, the timing group delay w is

[0123]

number

[0124] If the timing group delay is the same for both

[0125]

number

[0126] However, a problem that can arise is that the timing group delay w does not actually remain constant, but rather varies over time, as follows:

[0127]

number

[0128] Thereby, w(t1) and w(t2) reflect times t1 and t2, respectively.

[0129] In this case, the difference is

[0130]

number

[0131] When w(t1) is taken between t1 and t2, there is a residual error due to the difference between w(t1) and w(t2). This residual error is due to a phenomenon referred to herein as time drift. As an example, time drift in the timing group delays can occur due to various environmental factors such as humidity, temperature, etc.

[0132] Embodiments of the present disclosure are directed to reducing errors due to time drift associated with a positioning procedure (e.g., RTT, differential RTT, or OTDOA) for a UE, thereby providing the technical advantage of obtaining a more accurate positioning estimate.

[0133] FIG. 17 illustrates an example process 1700 of wireless communication according to an aspect of the disclosure. Process 1700 may be performed by a communication node. In some designs, the communication node performing process 1700 is a UE (e.g., any of the UEs described herein). In other designs, the communication node performing process 1700 is a BS (e.g., any of the BSs or gNBs described herein). For example, in FIG. 11, the UE reports Rx-Tx measurements that are taken into account in the gNB's RTT measurements, in which case process 1700 would be performed by the UE. However, this process can be reversed, whereby the gNB reports Rx-Tx measurements that are taken into account in the UE's RTT measurements, in which case process 1700 would be performed by the BS (or gNB). Moreover, process 1700 is also applicable to non-RTT positioning techniques such as DL or UL TDOA (e.g., in which case only the Rx Timing Group Delay or the Tx Timing Group Delay is reported and / or taken into account in the positioning procedure), as described in more detail below.

[0134] At 1710, the communication node (e.g., transmitter 310, receiver 312, processing system 332, transmitter 316, receiver 318, and / or processing system 334) obtains first timing information including a first timing group delay at a first time relative to a first positioning procedure (e.g., TDOA, RTT, etc.) between a first UE and a first TRP. In some designs, the first timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 in FIG. 9 or t2 or t4 in FIG. 11. In other designs, the first timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in FIG. 9 or t1 or t3 in FIG. 11. In one example, the first timing group delay may comprise an Rx timing group delay (e.g., for UL / DL TDOA), a Tx timing group delay (e.g., for UL / DL TDOA), or an Rx-Tx timing group delay (e.g., for RTT).

[0135] At 1720, the communication node (e.g., transmitter 310, receiver 312, processing system 332, transmitter 316, receiver 318, and / or processing system 334) obtains second timing information including a second timing group delay at a second time relative to a second positioning procedure (e.g., TDOA, RTT, etc.) between the second UE and the second TRP. In some designs, the second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 in FIG. 9 or t2 or t4 in FIG. 11. In other designs, the second timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in FIG. 9 or t1 or t3 in FIG. 11. In one example, the first and second timing group delays may comprise an Rx timing group delay (e.g., for UL / DL TDOA, e.g., 1104 or 1106 in FIG. 11), a Tx timing group delay (e.g., for UL / DL TDOA, e.g., 1102 or 1108 in FIG. 11), or an Rx-Tx timing group delay (e.g., for RTT, e.g., 1104 to 1108 or 1106 to 1100 in FIG. 11). In some designs, the first and second TRPs correspond to the same TRP, while the first and second UEs correspond to different UEs. In other designs, the first and second TRPs correspond to different TRPs, while the first and second UEs correspond to the same UE.

[0136] At 1730, the communications node (e.g., processing system 332 or processing system 334) determines time drift information associated with the first and second timing group delays. As described in more detail below, the time drift information may comprise a variety of information, such as a direct or indirect indication of one or more time drift functions, a time period for which the time drift information remains valid, etc.

[0137] At 1740, the communication node (e.g., the transmitter 310, the transmitter 316, or the transmitter 322) reports the time drift information to an external entity. In one example, the external entity may correspond to the UE, one of the TRPs (e.g., a TRP associated with the UE's serving base station, which may have an integrated LMF), or a remote server, such as an LMF network entity.

[0138] 17, in some designs, a communication node (e.g., memory 338, 340, 342, etc.) may store the time drift information, either in addition to or instead of reporting at 1740. For example, the communication node may retain the time drift information for use in a subsequent positioning procedure. In a particular example, the communication node may correspond to a UE that stores the time drift information as part of a UE-based multi-cell RTT procedure.

[0139] FIG. 18 illustrates an example process 1800 of wireless communication according to an aspect of the disclosure. Process 1800 may be performed by an entity. In one example, the entity performing process 1800 may correspond to an external entity from 1740 of FIG. 17 to which the time drift information is reported. In some designs, the entity performing process 1800 is a UE (e.g., any of the UEs described herein). In other designs, the communication node performing process 1800 is a BS (e.g., any of the BSs or gNBs described herein). In other designs, the communication node performing process 1800 is a network entity such as an LMF network entity (e.g., 306 of FIG. 3). Similar to process 1700 of FIG. 17, process 1800 is applicable to non-RTT positioning techniques such as DL or UL TDOA (e.g., in which case only the Rx timing group delay or the Tx timing group delay is taken into account for the positioning procedure), as described in more detail below.

[0140] At 1810, an entity (e.g., receiver 312, receiver 318, or receiver 330) receives, from a communication node (e.g., a communication node performing process 1700 of FIG. 17), time drift information associated with first and second timing group delays included in first and second timing information obtained at the entity at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first UE and a first TRP, and the second positioning procedure being between a second UE and a second TRP. In some designs, the first and second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 in FIG. 9, or t2 or t4 in FIG. 11. In other designs, the first and second timing information may correspond to measurements (or determinations) of transmission times of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in FIG. 9 or t1 or t3 in FIG. 11. In one example, the first and second timing group delays may comprise an Rx timing group delay (e.g., for UL / DL TDOA, e.g., 1104 or 1106 in FIG. 11), a Tx timing group delay (e.g., for UL / DL TDOA, e.g., 1102 or 1108 in FIG. 11), or an Rx-Tx timing group delay (e.g., for RTT, e.g., 1104 to 1108, or 1106 to 1100 in FIG. 11). In some designs, the first and second TRP correspond to the same TRP, whereas the first and second UEs correspond to different UEs. In another design, the first and second TRPs correspond to different TRPs, while the first and second UEs correspond to the same UE.

[0141] In 1820, an entity (e.g., processing system 332 or positioning component 344, processing system 334 or positioning component 348, processing system 336 or positioning component 349) determines a positioning estimate (e.g., for a UE performing a positioning procedure with the first TRP or the second TRP) based at least in part on the time drift information. Various examples of 1820 are described in more detail below.

[0142] 17-18, in some designs, the first and second positioning procedures correspond to first and second RTT measurements. In a particular example, the first and second RTT measurements are part of a differential RTT measurement procedure. However, the first and second RTT measurements may alternatively be used as part of a so-called normal (or non-differential) RTT measurement procedure. In other designs, the first and second positioning procedures correspond to uplink or downlink TDOA measurements.

[0143] 17-18, in one example, the time drift information indicates a drift rate function, whereby a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times. In one example, the time drift function may specify a ppb clock drift (e.g., a UE ppb clock drift or a BS ppb clock drift) over a defined time interval. For example, the drift rate function may be r drift whereby first and second timing measurements are taken at t1 and t2 as follows:

[0144]

number

[0145] In some designs, r driftmay comprise a linear function, such as a piecewise linear function (e.g., such that different time gaps between t1 and t2 result in timing group delay offsets that are linearly scaled). In other designs, the drift rate function may comprise a nonlinear function (e.g., such that different time gaps between t1 and t2 result in timing group delay offsets that are not linearly scaled).

[0146] In some designs, r drift is calibrated at t1, so r drift but

[0147]

number

[0148] In other designs, only r drift may be calculated at a third time t0 prior to t1, where t0 corresponds to the time when the previous time drift calibration was performed by the communication node, in which case Equations 5 and 6 may be updated as follows:

[0149]

number

[0150] As will be understood, drift If is calibrated at t1, then t1=t0, and Equations 7 and 8 revert to Equations 5 and 6.

[0151] In a further example, the first time drift (e.g., r drift ·(t1-t0)), and the uncertainty level associated with the second time drift (e.g., r driftA second uncertainty level associated with the first time (t1) may be determined by the communication node and / or entity, the second uncertainty level being based in part on a first difference between the first time (t1) and the third time (t0), and the second uncertainty level being based in part on a second difference between the second time (t2) and the third time (t0). For example, a larger time gap from the third time (t0) may be associated with a larger uncertainty. In a further example, the first and second uncertainty levels may be configured to weight the first and second timing information in association with the first and second positioning procedures, respectively (e.g., timing measurements with greater certainty receive a greater weight in the respective positioning procedures). In some designs, the uncertainty levels may be determined in part on a first uncertainty level associated with the first time (t1) and the third time (t0), the second uncertainty level being based in part on a second difference between the second time (t2) and the third time (t0). For example, a larger time gap from the third time (t0) may be associated with a larger uncertainty. In a further example, the first and second uncertainty levels may be configured to weight the first and second timing information in association with the first and second positioning procedures, respectively (e.g., timing measurements with greater certainty receive a greater weight in the respective positioning procedures). In some designs, the uncertainty levels may be determined in part on a first uncertainty level associated with the first time (t1) and the third time (t0). drift The amount of, or how well drift is known. Below, example formulas are provided in terms of a first time (t1) and a second time (t2), but it will be appreciated that these times may be defined relative to another reference time (t0) in other examples, particularly in scenarios where drift affects timing measurements at both the first time (t1) and the second time (t2).

[0152] 17-18 , in a further example, the time drift information may be associated with a time period during which a drift rate function remains valid. For example, a linear drift rate may remain valid for a longer time period than a non-linear drift rate in some cases. In some designs, the time period may be dynamically determined based on one or more factors, such as the SCS, the UE capabilities, the PRS / SRS bandwidth, or a combination thereof. In a particular example, the time period may be associated with a time period during which a drift rate function remains valid. c *2 k / sec, where k may depend on one or more factors, such as SCS, UE capabilities, PRS / SRS bandwidth, or a combination thereof. cIn one example, the size of the various fields in the time domain for various embodiments of the present disclosure is in units of time T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f = 4096. The constant κ = T s / T c = 64, where T s =1 / (Δf ref N f,ref ), Δf ref =15 10 3 Hz and N f,ref =2048.

[0153] In some designs, the time period may be conveyed in the downlink direction via a downlink control indication (DCI) or MAC-CE signaling. In other designs, the time period may be conveyed in the uplink direction via an uplink control indication (UCI) or MAC-CE signaling. In some designs, the time period may be conveyed in the uplink direction via an uplink control indication (UCI) or MAC-CE signaling. drift may be indicated as the maximum time difference between t2-t1 for which is valid (e.g., if the time difference is larger than the reported value, then the accuracy requirement for the positioning estimate does not apply).

[0154] In some designs, the communication node may be configured to report how the timing group delay uncertainty variation drifts over time, eg, as follows:

[0155]

number

[0156] In some designs, a communication node may be configured to report a maximum time during which the uncertainty is within a configured or reported upper bound, eg, as follows:

[0157]

number

[0158] In other words, there is drift, but it is unknown, but what is known is that in the worst case scenario, the unknown error due to time drift is bounded by the value V for the maximum amount of time difference between t1 and t2.

[0159] For example, Var{} may be configured as a decay function such that longer time periods (or time gaps) are subject to a higher level of uncertainty.

[0160] Referring to FIG. 17-FIG. 18, in some designs, r drift And the reporting of Var{} may be separate for the Rx Timing Group Delay and the Tx Timing Group Delay, for example:

[0161]

number

[0162] In some designs, if the communication node corresponds to the UE, the UE may report the time drift information as part of a UE capability message. In other designs, the UE may report the time drift information as part of each positioning measurement report (in addition to the actual measurements). In other designs, the reporting of the time drift information may be implemented via RRC, LPP, MAC-CE, or DCI signaling.

[0163] 17-18 , the time drift information in some designs may comprise a set of drift rate functions, where the set of drift rate functions (r drift 1...N) By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them The drift rate function comprises one or more drift rate functions:

[0164] Referring to FIGS. 17-18, in some designs, the reference drift rate function is r drift_reference and one or more of the drift rate functions may be represented as r drift_reference This may be particularly beneficial in implementations with multiple drift rate functions (e.g., N>threshold).

[0165] 17-18, in one example, one or more of the drift rate functions may be included as part of the time drift information in some designs. However, in other designs, the time drift function may be indicated via a differential time drift function parameter that indirectly indicates the time drift function. In this case, the differential time drift function parameter functions as an offset to the previously reported time drift function. A benefit of this approach in some designs is that the differential time drift function parameter will generally occupy fewer bits (i.e., less overhead) compared to the time drift function.

[0166] While processes 1700-1800 in Figures 17-18 are described with respect to a communication node, which may correspond to either a UE or a TRP of a BS, Figures 19-22 provide example implementations of processes 1700-1800 in Figures 17-18 that are specific to either a UE mapping to a communication node or a TRP mapping to a communication node.

[0167] FIG. 19 illustrates an example implementation of the process 1700 of FIG. 17 according to an aspect of the disclosure. In FIG. 19, the communication node from FIG. 17 maps to a TRP of a BS, such as BS 304, in more detail. At 1910, the TRP obtains first timing information including a first timing group delay at a first time associated with a first positioning procedure between a first user equipment (UE) and the TRP. In some designs, the first timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 of FIG. 9, or t2 or t4 of FIG. 11. In other designs, the first timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 of FIG. 9, or t1 or t3 of FIG. 11. At 1920, the TRP obtains second timing information including a second timing group delay at a second time associated with a second positioning procedure between the second UE and the TRP. In some designs, the second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 in FIG. 9 or t2 or t4 in FIG. 11. In other designs, the second timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in FIG. 9 or t1 or t3 in FIG. 11. At 1930, the TRP determines time drift information associated with the first and second timing group delays. At 1940, the TRP reports the time drift information to an external entity.

[0168] FIG. 20 illustrates an example implementation of the process 1700 of FIG. 17 according to another aspect of the disclosure. In FIG. 20, the communication nodes from FIG. 17 map, in more detail, to a UE, such as UE 302. At 2010, the UE obtains first timing information including a first timing group delay at a first time associated with a first positioning procedure between the UE and a first transmitting reception point (TRP). In some designs, the first timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 of FIG. 9, or t2 or t4 of FIG. 11. In other designs, the first timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 of FIG. 9, or t1 or t3 of FIG. 11. At 2020, the UE acquires second timing information including a second timing group delay at a second time associated with a second positioning procedure between the UE and the second TRP. In some designs, the second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 in FIG. 9 or t2 or t4 in FIG. 11. In other designs, the second timing information may correspond to a measurement (or determination) of a transmission time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in FIG. 9 or t1 or t3 in FIG. 11. At 2030, the UE determines time drift information associated with the first and second timing group delays. At 2040, the UE reports the time drift information to an external entity.

[0169] FIG. 21 illustrates an example implementation of the process 1800 of FIG. 18 according to an aspect of the disclosure. In FIG. 21, the communication node from FIG. 18 maps to a TRP of a BS, such as BS 304, in more detail. At 2110, the entity receives from a transmitting receiving point (TRP) time drift information associated with first and second timing group delays included in first and second timing information acquired at the TRP at first and second times in association with a first and second positioning procedure, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP, and the second positioning procedure being between a second UE and the TRP. In some designs, the first and second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 of FIG. 9, or t2 or t4 of FIG. 11. In other designs, the first and second timing information may correspond to measurements (or determinations) of transmission times of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in Figure 9, or t1 or t3 in Figure 11. At 2120, the entity determines a positioning estimate (e.g., of a UE in a positioning session with a TRP) based at least in part on the time drift information.

[0170] FIG. 22 illustrates an example implementation of the process 1800 of FIG. 18 according to another aspect of the disclosure. In FIG. 21, the communication node from FIG. 18 maps to a UE, such as UE 302, in more detail. At 2210, the entity receives from a user equipment (UE) time drift information associated with first and second timing group delays included in first and second timing information acquired at the UE at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between the UE and a first transmission reception point (TRP), and the second positioning procedure being between the UE and a second TRP. In some designs, the first and second timing information may correspond to a measurement of a reception time of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T2 or T4 of FIG. 9, or t2 or t4 of FIG. 11. In other designs, the first and second timing information may correspond to measurements (or determinations) of transmission times of a reference signal (e.g., DL-PRS or UL-PRS or SL-PRS), such as T1 or T3 in Figure 9, or t1 or t3 in Figure 11. At 2220, the entity determines a position estimate for the UE based at least in part on the time drift information.

[0171] In the above detailed description, it can be seen that various features are grouped together in each example. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the disclosure may include fewer than all features of each exemplary clause disclosed. Thus, the following clauses should be considered hereby as being incorporated into this description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspects of that dependent clause are not limited to that specific combination. It will be appreciated that other exemplary clauses may also include combinations of aspects of the dependent clause with the subject matter of any other dependent clause or independent clause, or combinations of any features with other dependent clauses and independent clauses. Unless a specific combination is not intended (e.g., conflicting aspects such as defining an element as both an insulator and a conductor) is expressly expressed or can be easily inferred, the various aspects disclosed herein expressly include these combinations. It is further contemplated that aspects of a clause may be included within any other independent clause, even if that clause is not directly dependent on an independent clause.

[0172] Example implementations are described in the numbered clauses below.

[0173] Clause 1. A method of operating a transmit receiving point (TRP), comprising: obtaining first timing information including a first timing group delay at a first time in association with a first positioning procedure between a first user equipment (UE) and the TRP; obtaining second timing information including a second timing group delay at a second time in association with a second positioning procedure between a second UE and the TRP; determining time drift information associated with the first and second timing group delays; and reporting the time drift information to an external entity.

[0174] Clause 2. The method of clause 1, wherein the first and second positioning procedures correspond to first and second round trip time (RTT) measurements.

[0175] Clause 3. The method of clause 2, wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

[0176] Clause 4. Any of the methods of clauses 1 to 3, wherein the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements.

[0177] Clause 5. The method of any of clauses 1-4, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

[0178] Clause 6. Any of the methods of clauses 1 to 5, wherein the time drift information indicates a drift rate function, and a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

[0179] Clause 7. The method of clause 6, wherein the drift rate function comprises a linear function.

[0180] Clause 8. The method of clause 7, wherein the linear function comprises a piecewise linear function.

[0181] Clause 9. The method of any of clauses 6 to 8, wherein the drift rate function comprises a non-linear function.

[0182] Clause 10. Any of the methods of clauses 6 to 9, wherein the drift rate function is for a third time that a previous time drift calibration was performed by the TRP.

[0183] Clause 11. The method of clause 10, wherein the determining step includes determining a first time drift associated with the first timing information relative to a third time based on a drift rate function, and determining a second time drift associated with the second timing information relative to the third time based on the drift rate function, and wherein the relative time drift between the first and second timing group delays is based on a difference between the first and second time drifts.

[0184] Clause 12. The method of clause 11, further comprising determining a first uncertainty level associated with the first time drift and determining a second uncertainty level associated with the second time drift.

[0185] Clause 13. The method of clause 12, wherein the first uncertainty level is based in part on a first difference between the first time and the third time, and the second uncertainty level is based in part on a second difference between the second time and the third time.

[0186] Clause 14. The method of any of clauses 12 to 13, wherein the first and second uncertainty levels are configured to weight the first and second timing information in relation to the first and second positioning procedures, respectively.

[0187] Clause 15. The method of any of clauses 6 to 14, wherein the time drift information is associated with a time period during which the drift rate function remains valid.

[0188] Clause 16. The method of clause 15, wherein the time period is dynamically determined based on a subcarrier spacing (SCS), a UE capability, a positioning reference signal (PRS) or a sounding reference signal (SRS) bandwidth, or a combination thereof.

[0189] Clause 17. The method of any of clauses 6 to 16, wherein the drift rate function comprises a set of drift rate functions, the set of drift rate functions comprising one or more drift rate functions per SRS resource or SRS resource set ID, per band, per component carrier, per positioning technique, per panel, per Tx chain, per Rx chain, per downlink or uplink Rx, per downlink or uplink Tx, or any combination thereof.

[0190] Clause 18. The method of any of clauses 6 to 17, wherein the reporting step includes a time drift function in the reported time drift information or the reporting step includes a differential time drift function parameter that indirectly indicates the time drift function.

[0191] Clause 19. The method of any of clauses 1 to 18, wherein the external entity corresponds to a base station associated with the first UE, the second UE, the TRP, or a Location Management Function (LMF) network entity.

[0192] Clause 20. The method of any of clauses 1 to 19, wherein the time drift information comprises an upper limit on time drift between the first and second times.

[0193] Clause 21. A method of operating a user equipment (UE), comprising the steps of: obtaining first timing information including a first timing group delay at a first time in association with a first positioning procedure between the UE and a first transmit receiving point (TRP); obtaining second timing information including a second timing group delay at a second time in association with a second positioning procedure between the UE and a second TRP; determining time drift information associated with the first and second timing group delays; and reporting the time drift information to an external entity.

[0194] Clause 22. The method of clause 21, wherein the first and second positioning procedures correspond to first and second round trip time (RTT) measurements.

[0195] Clause 23. The method of clause 22, wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

[0196] Clause 24. The method of any of clauses 21 to 23, wherein the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements.

[0197] Clause 25. The method of any of clauses 22-24, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

[0198] Clause 26. The method of any of clauses 21-25, wherein the time drift information indicates a drift rate function, and a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

[0199] Clause 27. The method of clause 26, wherein the drift rate function comprises a linear function.

[0200] Clause 28. The method of any of clauses 25 to 27, wherein the linear function comprises a piecewise linear function.

[0201] Clause 29. The method of any of clauses 26 to 28, wherein the drift rate function comprises a non-linear function.

[0202] Clause 30. The method of any of clauses 26 to 29, wherein the drift rate function is for a third time that a previous time drift calibration was performed by the TRP.

[0203] Clause 31. The method of clause 30, wherein the determining step includes determining a first time drift associated with the first timing information relative to a third time based on a drift rate function, and determining a second time drift associated with the second timing information relative to the third time based on the drift rate function, wherein the relative time drift between the first and second timing group delays is based on a difference between the first and second time drifts.

[0204] Clause 32. The method of clause 31, further comprising determining a first uncertainty level associated with the first time drift and determining a second uncertainty level associated with the second time drift.

[0205] Clause 33. The method of clause 32, wherein the first uncertainty level is based in part on a first difference between the first time and the third time, and the second uncertainty level is based in part on a second difference between the second time and the third time.

[0206] Clause 34. The method of any of clauses 32 to 33, wherein the first and second uncertainty levels are configured to weight the first and second timing information in relation to the first and second positioning procedures, respectively.

[0207] Clause 35. The method of any of clauses 26 to 34, wherein the time drift information is associated with a time period during which the drift rate function remains valid.

[0208] Clause 36. The method of clause 35, wherein the time period is dynamically determined based on a subcarrier spacing (SCS), a UE capability, a positioning reference signal (PRS) or a sounding reference signal (SRS) bandwidth, or a combination thereof.

[0209] Clause 37. The method of any of clauses 26 to 36, wherein the drift rate function comprises a set of drift rate functions, the set of drift rate functions comprising one or more drift rate functions per SRS resource or SRS resource set ID, per band, per component carrier, per positioning technique, per panel, per Tx chain, per Rx chain, per downlink or uplink Rx, per downlink or uplink Tx, or any combination thereof.

[0210] Clause 38. The method of any of clauses 26 to 37, wherein the reporting step includes a time drift function in the reported time drift information or the reporting step includes a differential time drift function parameter that indirectly indicates the time drift function.

[0211] Clause 39. The method of any of clauses 21 to 38, wherein the external entity corresponds to a base station associated with the first TRP or the second TRP, or a Location Management Function (LMF) network entity.

[0212] Clause 40. The method of any of clauses 21 to 39, wherein the time drift information comprises an upper limit on time drift between the first and second times.

[0213] Clause 41. A method of operating an entity, the method comprising: receiving, from a transmit receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information obtained at the TRP at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP and the second positioning procedure being between a second UE and the TRP; and determining a positioning estimate based at least in part on the time drift information.

[0214] Clause 42. The method of clause 41, wherein the first and second positioning procedures correspond to first and second round trip time (RTT) measurements.

[0215] Clause 43. The method of clause 42, wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

[0216] Clause 44. The method of any of clauses 41 to 43, wherein the first and second positioning procedures correspond to uplink or downlink time difference of arrival (TDOA) measurements.

[0217] Clause 45. The method of any of clauses 41-44, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

[0218] Clause 46. The method of any of clauses 41 to 45, wherein the time drift information indicates a drift rate function, and a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

[0219] Clause 47. The method of clause 46, wherein the drift rate function comprises a linear function.

[0220] Clause 48. The method of clause 47, wherein the linear function comprises a piecewise linear function.

[0221] Clause 49. The method of any of clauses 46 to 48, wherein the drift rate function comprises a non-linear function.

[0222] Clause 50. The method of any of clauses 46 to 49, wherein the drift rate function is for a third time that a previous time drift calibration was performed by the UE.

[0223] Clause 51. The method of clause 50, wherein a relative time drift between the first and second timing group delays is based on a difference between the first and second time drifts, the first time drift is associated with the first timing information for the third time based on a drift rate function, and the second time drift is associated with the second timing information for the third time based on a drift rate function.

[0224] Clause 52. The method of clause 51, further comprising determining a first uncertainty level associated with the first time drift and determining a second uncertainty level associated with the second time drift.

[0225] Clause 53. The method of clause 52, wherein the first uncertainty level is based in part on a first difference between the first time and the third time, and the second uncertainty level is based in part on a second difference between the second time and the third time.

[0226] Clause 54. The method of any of clauses 52 to 53, wherein the first and second uncertainty levels are configured to weight the first and second timing information in relation to the first and second positioning procedures, respectively.

[0227] Clause 55. The method of any of clauses 46 to 54, wherein the time drift information is associated with a time period during which the drift rate function remains valid.

[0228] Clause 56. The method of clause 55, wherein the time period is dynamically determined based on a subcarrier spacing (SCS), a UE capability, a positioning reference signal (PRS) or a sounding reference signal (SRS) bandwidth, or a combination thereof.

[0229] Clause 57. The method of any of clauses 46 to 56, wherein the drift rate function comprises a set of drift rate functions, the set of drift rate functions comprising one or more drift rate functions per SRS resource or SRS resource set ID, per band, per component carrier, per positioning technique, per panel, per Tx chain, per Rx chain, per downlink or uplink Rx, per downlink or uplink Tx, or any combination thereof.

[0230] Clause 58. The method of any of clauses 46 to 57, wherein the time drift information includes a time drift function or the time drift information includes differential time drift function parameters that indirectly indicate the time drift function.

[0231] Clause 59. The method of any of clauses 41 to 58, wherein the entity corresponds to a first UE, a second UE, a base station associated with the TRP, or a Location Management Function (LMF) network entity.

[0232] Clause 60. The method of any of clauses 41 to 59, wherein the time drift information comprises an upper limit on time drift between the first and second times.

[0233] Clause 61. A method of operating an entity, comprising: receiving from a user equipment (UE) time drift information associated with first and second timing group delays included in first and second timing information obtained at the UE at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between the UE and a first transmit reception point (TRP) and the second positioning procedure being between the UE and a second TRP; and determining a position estimate for the UE based at least in part on the time drift information.

[0234] Clause 62. The method of clause 61, wherein the first and second positioning procedures correspond to first and second round trip time (RTT) measurements.

[0235] Clause 63. The method of clause 62, wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

[0236] Clause 64. The method of any of clauses 61 to 63, wherein the first and second positioning procedures correspond to uplink or downlink time difference of arrival (TDOA) measurements.

[0237] Clause 65. The method of any of clauses 61-64, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

[0238] Clause 66. The method of any of clauses 61 to 65, wherein the time drift information indicates a drift rate function, and a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

[0239] Clause 67. The method of clause 66, wherein the drift rate function comprises a linear function.

[0240] Clause 68. The method of clause 67, wherein the linear function comprises a piecewise linear function.

[0241] Clause 69. The method of any of clauses 66 to 68, wherein the drift rate function comprises a non-linear function.

[0242] Clause 70. The method of any of clauses 66 to 69, wherein the drift rate function is for a third time that a previous time drift calibration was performed by the UE.

[0243] Clause 71. The method of clause 70, wherein a relative time drift between the first and second timing group delays is based on a difference between the first and second time drifts, the first time drift is associated with the first timing information for the third time based on a drift rate function, and the second time drift is associated with the second timing information for the third time based on a drift rate function.

[0244] Clause 72. The method of clause 71, further comprising determining a first uncertainty level associated with the first time drift and determining a second uncertainty level associated with the second time drift.

[0245] Clause 73. The method of clause 72, wherein the first uncertainty level is based in part on a first difference between the first time and the third time, and the second uncertainty level is based in part on a second difference between the second time and the third time.

[0246] Clause 74. The method of any of clauses 72 to 73, wherein the first and second uncertainty levels are configured to weight the first and second timing information in relation to the first and second positioning procedures, respectively.

[0247] Clause 75. The method of any of clauses 66 to 74, wherein the time drift information is associated with a time period during which the drift rate function remains valid.

[0248] Clause 76. The method of clause 75, wherein the time period is dynamically determined based on a subcarrier spacing (SCS), a UE capability, a positioning reference signal (PRS) or a sounding reference signal (SRS) bandwidth, or a combination thereof.

[0249] Clause 77. The method of any of clauses 66 to 76, wherein the drift rate function comprises a set of drift rate functions, the set of drift rate functions comprising one or more drift rate functions per SRS resource or SRS resource set ID, per band, per component carrier, per positioning technique, per panel, per Tx chain, per Rx chain, per downlink or uplink Rx, per downlink or uplink Tx, or any combination thereof.

[0250] Clause 78. The method of any of clauses 66 to 77, wherein the time drift information includes a time drift function or the time drift information includes differential time drift function parameters that indirectly indicate the time drift function.

[0251] Clause 79. The method of any of clauses 61 to 78, wherein the entity corresponds to a base station associated with the first TRP or the second TRP, or a Location Management Function (LMF) network entity.

[0252] Clause 80. The method of any of clauses 61 to 79, wherein the time drift information comprises an upper limit on time drift between the first and second times.

[0253] Clause 81. An apparatus comprising a memory and at least one processor communicatively coupled to the memory, wherein the memory and the at least one processor are configured to perform a method according to any of clauses 1 to 80.

[0254] Clause 82. Apparatus comprising means for carrying out the method according to any of clauses 1 to 80.

[0255] Clause 83. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 80.

[0256] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0257] Moreover, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0258] The various example logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0259] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0260] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0261] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. [Explanation of symbols]

[0262] 100, 600, 700, 800, 1200 Wireless Communication Systems 102 Base station, macrocell base station 102' Small Cell Base Station 104, 164, 182, 190, 204, 704, 904 UE 110 Geographical Coverage Area, Coverage Area 110' Coverage Area 120, 154 Communication links 122, 134 backhaul links 150 WLAN Access Points (APs), WLAN APs 152 Wireless Local Area Network (WLAN) Station (STA), WLAN STA 166 Positioning components, SRS components 170 Core Network 172, 230 Location Server 180 mmW base station, base station 184 mmW communication link 192, 194 D2D P2P links 200, 250 Wireless Network Structure 210, 260 NGC 212 User Plane Functions 213 User Plane Interface (NG-U), NG-U 214 Control Plane Functions 215 Control Plane Interface (NG-C), NG-C 220 New RAN 222 gNB 223 Backhaul Connection 224 eNB 262 Session Management Facility (SMF), SMF 263 User Plane Interface 264 Access and Mobility Management Function (AMF) / User Plane Function (UPF), AMF / UPF 265 Control Plane Interface 270 Location Management Facility (LMF), LMF 302 UE, equipment 304 Base station, equipment, BS 306 Network entities, devices 308, 314, 320, 326 Communication devices, blocks 310, 316, 322, 328 Transmitters 312, 318, 324, 330 Receiver 332, 334, 336 Processing system, block 338, 340, 342 Memory components, blocks, memory 344, 348, 349 Positioning components, blocks 350 User Interface, Blocks 352, 354, 356 Data Bus 360 Wireless Communication Link 370 Wire-based or wireless backhaul 500 DL PRS 702 base station, serving base station, first base station 702-1, 702-2, 702-3, 902 base station 710 RTT 910 RTT measurement signal 912T Rx→Tx 920 RTT response signal 922T Tx→Rx 1300, 1400 PRS resource allocation 1500 PRS instances 1600 positioning sessions

Claims

1. 1. A method of operating a transmit receive point (TRP), comprising: obtaining first timing information including a first timing group delay at a first time in relation to a first positioning procedure between a first user equipment (UE) and the TRP; obtaining second timing information including a second timing group delay at a second time in relation to a second positioning procedure between a second UE and the TRP; determining time drift information associated with the first and second timing group delays; reporting the time drift information to an external entity; The method includes:

2. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; The method of claim 1.

3. The method of claim 2 , wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

4. 2. The method of claim 1, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

5. the time drift information being indicative of a drift rate function; The method of claim 1 , wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

6. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; The method of claim 5.

7. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them The method of claim 5 , comprising one or more drift rate functions:

8. The method of claim 1 , wherein the time drift information comprises an upper limit on time drift between the first and second times.

9. 1. A method of operating a user equipment (UE), comprising: obtaining first timing information at a first time in relation to a first positioning procedure between the UE and a first transmitting receiving point (TRP), the first timing information including a first timing group delay; obtaining second timing information including a second timing group delay at a second time in relation to a second positioning procedure between the UE and a second TRP; determining time drift information associated with the first and second timing group delays; reporting the time drift information to an external entity; The method includes:

10. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; The method of claim 9.

11. the time drift information being indicative of a drift rate function; 10. The method of claim 9, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

12. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; The method of claim 11.

13. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them The method of claim 11 , comprising one or more drift rate functions:

14. The method of claim 9 , wherein the time drift information comprises an upper limit on time drift between the first and second times.

15. 1. A method of operating an entity, comprising: receiving, from a Transmit Receiving Point (TRP), time drift information associated with first and second timing group delays included in first and second timing information acquired at the TRP at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP, and the second positioning procedure being between a second UE and the TRP; determining a positioning estimate based at least in part on the time drift information; The method includes:

16. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; The method of claim 15.

17. the time drift information being indicative of a drift rate function; 16. The method of claim 15, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

18. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; The method of claim 17.

19. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 20. The method of claim 17, comprising one or more drift rate functions:

20. The method of claim 15 , wherein the time drift information comprises an upper limit on time drift between the first and second times.

21. 1. A method of operating an entity, comprising: receiving, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information acquired at the UE at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between the UE and a first transmit reception point (TRP) and the second positioning procedure being between the UE and a second TRP; determining a position estimate for the UE based at least in part on the time drift information; The method includes:

22. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; The method of claim 21.

23. the time drift information being indicative of a drift rate function; 22. The method of claim 21, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

24. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or The method of claim 23 , wherein the drift rate function comprises a non-linear function.

25. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 24. The method of claim 23, comprising one or more drift rate functions:

26. The method of claim 21 , wherein the time drift information comprises an upper limit on time drift between the first and second times.

27. A transmission receiving point (TRP), Memory, and at least one processor communicatively coupled to the memory, the at least one processor comprising: Obtaining first timing information at a first time in relation to a first positioning procedure between a first user equipment (UE) and the TRP, the first timing information including a first timing group delay; obtaining second timing information including a second timing group delay at a second time in relation to a second positioning procedure between a second UE and the TRP; determining time drift information associated with the first and second timing group delays; and reporting said time drift information to an external entity. The TRP is configured to:

28. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; 28. The TRP of claim 27.

29. 30. The TRP of claim 28, wherein the first and second RTT measurements are part of a differential RTT measurement procedure.

30. 28. The TRP of claim 27, wherein the first and second timing group delays comprise a receive (Rx) timing group delay, a transmit (Tx) timing group delay, or an Rx-Tx timing group delay.

31. the time drift information being indicative of a drift rate function; 28. The TRP of claim 27, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

32. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or 32. The TRP of claim 31 , wherein the drift rate function comprises a non-linear function.

33. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 32. The TRP of claim 31 , comprising one or more drift rate functions:

34. 28. The TRP of claim 27, wherein the time drift information comprises an upper limit of time drift between the first and second times.

35. A user equipment (UE), Memory, and at least one processor communicatively coupled to the memory, the at least one processor comprising: obtaining first timing information including a first timing group delay at a first time in relation to a first positioning procedure between the UE and a first transmitting receiving point (TRP); obtaining second timing information including a second timing group delay at a second time in relation to a second positioning procedure between the UE and a second TRP; determining time drift information associated with the first and second timing group delays; and reporting said time drift information to an external entity. The UE is configured to:

36. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; The UE of claim 35.

37. the time drift information being indicative of a drift rate function; 36. The UE of claim 35, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

38. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; The UE of claim 37.

39. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 38. The UE of claim 37, comprising one or more drift rate functions:

40. The UE of claim 35, wherein the time drift information comprises an upper limit on time drift between the first and second times.

41. An entity, Memory, and at least one processor communicatively coupled to the memory, the at least one processor comprising: receiving, from a transmit receiving point (TRP), time drift information associated with first and second timing group delays included in first and second timing information acquired at the TRP at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between a first user equipment (UE) and the TRP, and the second positioning procedure being between a second UE and the TRP; and determining a positioning estimate based at least in part on the time drift information; An entity that is configured to:

42. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; 42. The entity of claim 41.

43. the time drift information being indicative of a drift rate function; 42. The entity of claim 41, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

44. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; 44. The entity of claim 43.

45. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 44. The entity of claim 43, comprising one or more drift rate functions:

46. The entity of claim 41 , wherein the time drift information comprises an upper limit on time drift between the first and second times.

47. An entity, Memory, and at least one processor communicatively coupled to the memory, the at least one processor comprising: receiving, from a user equipment (UE), time drift information associated with first and second timing group delays included in first and second timing information acquired at the UE at first and second times in association with first and second positioning procedures, respectively, the first positioning procedure being between the UE and a first transmit reception point (TRP) and the second positioning procedure being between the UE and a second TRP; determining a position estimate for the UE based at least in part on the time drift information. An entity that is configured to:

48. the first and second positioning procedures correspond to first and second round trip time (RTT) measurements; or the first and second positioning procedures correspond to uplink or downlink Time Difference of Arrival (TDOA) measurements; 48. The entity of claim 47.

49. the time drift information being indicative of a drift rate function; 48. The entity of claim 47, wherein a relative time drift between the first and second timing group delays is determined based on the drift rate function and a difference between the first and second times.

50. the drift rate function comprises a linear function; or the linear function comprises a piecewise linear function; or the drift rate function comprises a non-linear function; 50. The entity of claim 49.

51. The drift rate function comprises a set of drift rate functions, the set of drift rate functions being: By SRS resource or SRS resource set ID, For each band, For each component carrier, For each positioning technique, Each panel, For each Tx chain, For each Rx chain, For each downlink or uplink Rx, per downlink or uplink Tx, or Any combination of them 50. The entity of claim 49, comprising one or more drift rate functions:

52. 48. The entity of claim 47, wherein the time drift information comprises an upper limit on time drift between the first and second times.

Images