WO2022155388A1 - Enhanced timing error estimation and compensation for wireless device positioning - Google Patents

Abstract

This disclosure describes systems, methods, and devices related to determining wireless device positioning. A device may detect a signal received from a second device; determine a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the device; determine a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the device to receive the signal; and generate a report including a timing quality information element and a residual error information element.

Description

ENHANCED TIMING ERROR ESTIMATION AND COMPENSATION FOR WIRELESS DEVICE POSITIONING CROSS-REFERENCE TO RELATED PATENT APPLICATION(S) This application claims the benefit of U.S. Provisional Application No. 63/137,420, filed January 14, 2021, the disclosure of which is incorporated by reference as set forth in full. TECHNICAL FIELD This disclosure generally relates to systems and methods for wireless communications and, more particularly, to wireless device positioning for 5^th Generation (5G) communications. BACKGROUND Wireless devices are becoming widely prevalent and are increasingly using wireless channels. The 3^rd Generation Partnership Program (3GPP) is developing one or more standards for wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a network diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure. FIG.2 is a network diagram illustrating an example network environment for network- based timing error estimation, in accordance with one or more example embodiments of the present disclosure. FIG.3 illustrates a flow diagram of illustrative process for wireless device positioning, in accordance with one or more example embodiments of the present disclosure. FIG.4 illustrates a network, in accordance with one or more example embodiments of the present disclosure. FIG. 5 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure. FIG. 6 is a block diagram illustrating components, in accordance with one or more example embodiments of the present disclosure. DETAILED DESCRIPTION The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. Wireless devices may determine their positions relative to other wireless devices using positioning techniques defined by technical standards. For cellular telecommunications, the 3^rd Generation Partnership Program (3GPP) define communication techniques, including for device positioning. Time measurement based device positioning techniques defined by the 3GPP standards include time difference of arrival (TDOA) and round trip time (RTT) techniques. TDOA relies on a device identifying when a signal was sent by one device and when the signal arrives at another device. TDOA may be in the downlink (DL) direction and the uplink (UL) direction. RTT refers to the length of time needed for a signal to be sent to a destination plus the length of time needed for the sending device to receive an acknowledgment of the signal from the destination (e.g., a “round trip” from the original sender to the destination, and back to the original sender). Multi-RTT refers to RTT measurements at both the user equipment (UE) and 5^th Generation radio node (gNB) sides. Using a known velocity (e.g., the speed of light) as the velocity of the signal, the distance between sending and receiving devices may be determined (e.g., velocity = distance/time, where the time is the difference between the sending and receiving times of the signal). Performing this calculation for multiple reference points (e.g., multiple devices whose distance is respective to one device), a device's exact position may be determined. In Release 17 of the 3GPP standards, device positioning techniques may be improved to satisfy applications and services needing higher location accuracy and lower latency. For example, in an Industrial Internet of Things (I-IoT) use case, it may be required to achieve positioning accuracy of less than 0.2 meters in a horizontal dimension and less than 1.0 meter in a vertical dimension for 90 % of users with the total physical layer (PHY, e.g., for the communication stack) latency of less than 10 milliseconds. One of the challenges to achieving such high positioning accuracy is the timing errors existing between the transmit (TX) and receive (RX) antenna chains (e.g., chains) at the gNB and UE sides caused by non-ideal synchronization and Radio Frequency (RF) circuit impairments. The timing errors may lead to a significant degradation of the distance measurements, and as a result, the entire positioning accuracy may deteriorate. In particular, antenna elements at the gNB and/or UE may have some uncompensated timing errors that may undermine the positioning accuracy determination using current positioning techniques based on timing measurements. To achieve the required positioning accuracy defined for the I-IoT and other use cases, the UE TX/RX and gNB TX/RX timing errors may need to be estimated and compensated for. In one or more embodiments, the present disclosure considers an impact of the TX/RX timing errors on the accuracy of the DL-TDOA, UL-TDOA, and Multi-RTT positioning methods. The present disclosure provides a method for estimation and compensation of the UE TX/RX and gNB TX/RX timing errors, and Information Element (IE) formats to support the reporting of such measurements for use in enhanced positioning techniques. The enhancements herein apply to TDOA and RTT techniques. In one or more embodiments, the UE TX/RX and gNB TX/RX timing errors may be aggregated to determine the sum of the timing errors at any node. For example, using three gNBs or Transmission Reception Points (TRPs) comprising a network with known spatial coordinates, and each gnB_i node has an internal TX timing error – eTX,i and RX timing error – eRX, i. The timing errors errors can be different and potentially caused by the independent sources. The total TX-RX timing error of the gnB_i can be found as a sum of the transmit and receive timing errors as e_i = e_TX,i + e_RX,i. A UE has its own internal TX timing error – e_TX,UE and RX timing error – e_RX,UE. The total TX-RX timing error of a UE can be found as a sum of the transmit and receive timing errors as e_UE = e_TX,UE + e_RX,UE. A UE performing the positioning procedure may need to estimate the unknown propagation time between a UE and each gNBi denoted as T_UE,i. The estimation procedure is based on the propagation time measurements between a UE and each gnB_i. In the case of the DL-based methods, the gnB_i sends a reference signal to a UE, which measures the propagation time t_i-UE, that can be represented in the form: t_i-UE = T_UE,i + e_TX,i + e_RX,UE (1), where T_UE,i is the unknown propagation time to be estimated, e_TX,i is the gNBi TX timing error, and e_RX,UE is the UE RX timing error. In the case of the UL-based methods, a UE sends a reference signal to the gnB_i, which measures the propagation time T_UE-i , that can be represented in the form: T_UE-i = T_UE,i + e_TX,UE + e_RX,i (2), where T_UE,i is the unknown propagation time to be estimated, e_TX,UE is the UE TX timing error, and e_RX,i is the gnB_i RX timing error. The Multi-RTT technique combines both measurements (1) and (2) as a part of the estimate. The summary of introduced parameters is below: e_TX,i the timing error at the transmitter side of the gnB_i node; –the timing error at the receiver side of the gnB_i node;

–the timing error at the transmitter side of a UE; –the timing error at the receiver side of a UE;

–the total timing error at the gnB_i; –the total timing error at the UE;

–the propagation time between a UE and the gnB to be estimated;

_i

–the measured propagation time between the gnB_i (transmitter) and a UE (receiver);

–the measured propagation time between a UE (transmitter) and the gnB_i (receiver). In one or more embodiments, the DL-TDOA enhanced technique may perform time difference measurements in the form:

where ൯ is the propagation time difference between a UE and the gnB_i

and gnB_i and is the TX timing error difference of gnB_i and gnB . The UE

_i RX timing error is cancelled out and does not affect estimation in that case.

In one or more embodiments, the UL-TDOA enhanced technique may perform time difference measurements in the form:

where is the propagation time difference between a UE and the gnB

_i and gnB_i and is the RX timing error difference of gnB_i and gnB_i. The UE

TX timing error is cancelled out and does not affect estimation in that case.

In one or more embodiments, the Multi-RTT enhanced technique may perform time difference measurements in the form:

where is the propagation time difference between a UE and the gnB_i, e_UE is the UE total timing error, and e_i is the gnB_i total timing error. In this manner, the estimation accuracy of the Multi-RTT positioning method depends on both UE and gNB timing errors. In one or more embodiments, the Multi-RTT time difference enhanced technique uses the time difference measurements of Equation (5) above:

where is the propagation time difference between a UE and the gnB

_i and gnB_i and is the total timing error difference of gnB_i and gnB_i. The UE total

timing error is cancelled out and does not affect estimation in that case. In one or more embodiments, the timing errors estimation includes two stages. The first stage includes the network-based (or inter-gNB) timing errors estimation and compensation. The timing errors are computed between the gNB node pairs using the propagation time measurements, which are compared to the reference propagation time. A reference (e.g., calibrated) time is calculated based on the ideal knowledge of the gNB’s (or TRP’s) spatial coordinates (or geographical coordinates) and relative distance computations. The second stage includes the total timing error estimate at the UE side (e.g., for the Multi- RTT positioning method). In that case, the timing errors are computed between the UE and each gNB (or TRP) of the network. This measurement relies on the assumption that the associated network-based error has been estimated at the previous stage and can be potentially compensated to facilitate the UE side error estimate. In one or more embodiments, for network-based (e.g., inter-gNB) timing error estimation, additionally the described above calibration procedure can be applied for a set of gNBs and a set of Positioning Reference Units – PRU (e.g., UEs with exactly known coordinates and antenna orientation), where the measurements for calibration are used only from gNB - PRU links. An example may include three gNBs or TRPs of a network with known spatial coordinates, and each gnB_i has an internal TX timing error and an internal RX

timing error . The timing errors may be different and caused by different (e.g., independent) sources. The ideal propagation time

between each pair of gNBs with indexes ^ and ^ may be known (e.g., computed based on an ideal knowledge of the gNB coordinates). Each gNB node may estimate a propagation time with any other gNB node in the network. First, gnB_i may send a reference signal to node gnB_i, which may estimate the propagation time of the reference signal. Then, the nodes may change roles, and the gnB_i may send a reference signal to the node gnB_i, which may estimate the propagation time of the

reference signal. The three gNBs may repeat the process between one another, and based on the time measurements for the three gNBs (e.g., gNB0, gNB1, gNB2) with respect to one another, the system of propagation time equations may be generated as:

where is the time measurement performed between the gnB_i (transmitter) and gnB_i (receiver), estimated at the gnB_i, i.e. receiver side. The system of equations (7) can be written in a different form by moving the _^^^to the right side of the equations:

where is the time difference between the observed (measured) value and the

reference (known) value of the propagation time .

In one or more embodiments, for the enhanced DL-TDOA method, a device may apply a set of transformations according to the set of equations (8), where the fifth row is subtracted from the third row, the sixth row is subtracted from the first row, and the fourth row is subtracted from the second row, resulting in a solution for each timing error difference

) as follows:

The equations (9) may be generalized in the form:

In one or more embodiments, for the enhanced UL-TDOA method, a device may apply a set of transformations according to the set of equations (8), where the sixth row is subtracted from the fourth row, the fifth row is subtracted from the second row, and the third row is subtracted from the first row, resulting in a solution for each timing error difference

as follows:

The equations (11) may be generalized in the form:

In one or more embodiments, for the enhanced Multi-RTT positioning method, a device may apply a set of transformations according to the set of equations (8), where the first row is added to the second row, the third row is added to the fourth row, and the fifth row is added to the sixth row, resulting in a system of equations:

The total timing error of the set of equations (13) may be simplified as follows:

In matrix form, this equation may be represented by:

where matrix A, error vector e, and observation difference vector Δt may be represented by:

where matrix A is a 3x3 matrix for the total timing error, and includes zero and one elements, where ones correspond to the nodes used in the measurement and zeros for the nodes not used in the respective measurement. e is a 3x1 error vector, and includes the total error values for each gNB node (or TRP). Δt is the 3x1 observation difference vector, where its elements represent a sum of differences between the observed (e.g., measured) value

and the reference (e.g., known) value and the observed value and the reference value

In one or more embodiments, the matrix A may have a full rank of 3, and is therefore invertible, and the error estimate e may be found as:

where matrix A^-1 is the inverse 3x3 matrix of the original matrix A, and A may be found as:

In one or more embodiments, the total UE timing error

needed for multi-RTT positioning may be estimated based on a two-stage process. At the first stage, a device may apply the DL-TDOA, UL-TDOA or Multi-RTT time difference positioning method described above to estimate the UE spatial coordinates. The Multi-RTT time difference positioning accuracy (e.g., like DL/UL-TDOA) depends on the gNB total timing errors only. The device may apply the Multi-RTT time difference method to estimate the UE spatial coordinates. Using found UE coordinates, the device may estimate the distance and corresponding propagation time from a UE to each of the gNBi nodes. Then the UE total timing error bias

Equation (5) can be estimated by averaging the time difference observations over different gNBs:

where is introduced as defined in Equation (5) and is estimated using the

network-based (or inter-gNB) procedure described above. At the second stage, the device may use the estimated UE total timing error bias and, along with the gNB e_i total timing error,

compensate it in Equation (5). Then the device may perform the Multi-RTT positioning algorithm to enhance the performance of the Multi-RTT time difference method. In one or more embodiments, to support the enhanced measurements for positioning, enhanced measurement reports and two-measurement quality Information Elements may be used by the devices. The measurement report may be sent by a UE to a single serving gNB or a single serving gNBs and multiple neighbor gNBs (TRPs). The measurement report may be sent by a UE to the Location Management Function (LMF) entity (e.g., the LMF entity of the 5G architecture defined by 3GPP). The measurement report may be sent by a serving gNB or a serving gNB and multiple neighbor gNBs (TRPs) to the LMF entity. The measurement report may be sent by the LMF entity to a serving gNB or a serving gNB and multiple neighbor gNBs (TRPs). The measurement report may be sent by the LMF entity to a UE, The measurement report may be sent by a serving gNB or a serving gNB and multiple neighbor gNBs (TRPs) to a UE.

In one or more embodiments, the measurement report of type 1 contains Information Element (IE) NR-TimingError with the fields specified below. This measurement feedback may be used by LMF, gNB, or UE to reconstruct the system of equations (8). The IE NR- TimingError may be used by the target device to provide information about the time difference between the actual measured propagation time and the reference propagation time

between any two nodes in the network (e.g., see equation (8)). The nr- relativeTimeDifference may be the measured time difference value, and each value is

associated with a quality value nr-timing-Quality. An example of the IE format is provided below. Note, that in general k0-r17, k1-r17, …, k5-r17 can take any integer value. ASN1START NR-TimingError-r17 ::= SEQUENCE (SIZE(1..2)) OF NR-TimingError-r17 NR-TimingError-r17 ::= SEQUENCE { nr-relativeTimeDifference-r17 CHOICE { k0-r17 INTEGER(0..16351), k1-r17 INTEGER(0..8176), k2-r17 INTEGER(0..4088), k3-r17 INTEGER(0..2044), k4-r17 INTEGER(0..1022), k5-r17 INTEGER(0..511), } ... nr-timing-Quality-r17 NR-TimingQuality-r17 OPTIONAL, } ASN1STOP where nr-relativeTimeDifference may specify the WLPH^GLIIHUHQFH^

between the actual measured propagation time and the reference propagation time between any

two nodes in the network. A positive value indicates that the actual measured propagation time is larger than the reference propagation time; a negative value indicates that the measured propagation time is smaller than the reference propagation time. nr-timing-quality specifies the target devices best estimate of the quality of the measured time difference. In one or more embodiments, the measurement report of type 2 may include Information Element (IE) NR-TotalTimingError with the fields specified below. This measurement feedback may be used by LMF, gNB, or UE to reconstruct a system of equations defined in Equation (14). The IE NR-TotalTimingError is used by the target device to provide information about the total (roundtrip) time difference between the actual measured

propagation roundtrip time and the reference propagation roundtrip time

between any two nodes in the network (e.g . see Equation (14)). The nr-rekitlvel imeDifference is the measured roundtrip time difference value, and each value is associated with

a quality value nr-timing-Quality. An example of the IE format is provided below. Note, that in general k0-rl7, kl-rl7.. . k5-r!7 can take any integer value.

ASN1 STOP where nr-relativeTinieDifference specifies the roundtrip time difference

between the actual measured propagation roundtrip time and the reference propagation

roundtrip time between any two nodes in the network. A positive value indicates that the

actual measured roundtrip propagation time is larger than the reference propagation roundtrip time; a negative value indicates that the measured propagation roundtrip time is smaller than the reference propagation roundtrip time. nr-timing-quality specifies the target devices best estimate of the quality of the measured time difference. In one or more embodiments, the measurement report of type 3 may include Information Element (IE) NR-TxRxTimingError with the fields specified below. This measurement feedback may be used by LMF, gNB, or UE to compute the propagation time between a UE and gNBi with compensated network timing error. Then it may be used to solve the system of equations (15). The IE NR-TxRxTimingError may be used by the target device to provide information about the total timing error (e), comprising the sum of transmit and receive timing errors for any node in the network (e.g., see equation (15)). The

nr-txRxTimingError is the measured total timing error value, and each value is

associated with a quality value nr-timing-Quality. An example of the IE format is provided below. Note, that in general k0-r17, k1-r17, …, k5-r17 can take any integer value. r17

ASN1STOP nr-txRxl ImingError specifies the total timing error (e ), comprising the sum of transmit and receive timing errors for any node in the network. Alternatively, two

independent values can be reported for Tx timing error and Rx timing error. A positive value indicates that the absolute measured error should be subtracted from the actual measured propagation time to get a correct timing estimate, a negative value indicates that, the absolute measured error should be added to the actual measured propagation time to get a correct timing estimate. nrDiming-qnaliiy specifies the target devices best estimate of the quality of the measured timing error.

In one or more embodiments, the measurement report of type 4 may include Information Element (IE) NR-Tx7 ImingErr or Difference with the fields specified below. This measurement feedback may be used by I. ME gNB, or UE to compute the DL-TDOA measurement for UE, gNBz and gNB/ with compensated timing error. Then it may be used as a standard DL-TDOA measurement in positioning equations. The IE NR- TxTimingErrorDifference is used by the target device to provide information about the TX timing error difference for gNBi and gNBj

, comprising the difference of transmit errors on gNB/ and gNB; (e g., see equation (9)). The nr-

TxTimingErrorDifference is the measured TX timing error difference value and each value is associated with a quality value rm-timing-Qualiiy. An example of the IE format is provided below. Note, that in general kO-rl 7, kl-rl 7, . . . , k5-r17 can take any integer value.

ASN1 STOP nr- TxTimingErrorDifference specifies the TX timing error difference ,

comprising the difference of transmit timing error values for node i

and node j in the network , A positive value indicates that the absolute measured error should be subtracted from the actual measured DL-TDOA measurements to generate a correct reference signal time difference (RSTD) estimate; a negative value indicates that the absolute measured error should be added to the actual DL-TDOA measurements to generate a correct RSTD estimate.

In one or more embodiments, the measurement report of type 5 may include Information Element (IE) NR-RxTimingErrorDifference with the fields specified below. This measurement feedback may be used by LMF, gNB, or UE to compute the UL-TDOA measurement for UE, gNBz and gNB/ with compensated timing error. Then it may be used as a standard UL-TDOA measurement in positioning equaitons.

The IE NR-RxTimingErrorDifference is used by the target device to provide information about, the Rx timing error difference for gNB/ and gNBj

, comprising the difference of receive errors on gNBi and gNBj see equations (11).

The nr-RxTimingErrorDifference is the measured Rx timing error difference value and each value is associated with a quality value nr-timing-Quality. An example of the IE format is provided below. Note, that in general k0-r17, kl-r17, k5-r17 can take any integer value.

ASN1ST0P nr- Rx TimingErrorDijference specifies the Rx timing error difference

comprising the difference of receive timing error values for node i

and node j in the network , A positive value indicates that the absolute measured error should be subtracted from the actual measured UL-TDOA measurements to generate a correct RSTD estimate; a negative value indicates that the absolute measured error should be added to the actual UL-TDOA measurements to generate a correct RSTD estimate. nrEitmng-qriality specifi es the target devices best estimate of the quality of the measured timing error.

In one or more embodiments, the measurement report of type 6 may include Information Element (IE) NR-TxRxTimingError with the fields specified below. This feedback may be used by LMF, gNB, or UE for Tx/Rx timing error compensation in timing-based measurements such as DL-TDOA, UL-TDOA, Multi-RTT and others. The IE NR- TxRx 7 ImingEi ror is used by the target device to provide information about the TX timing error (e_TX) and Rx timing error (e_RX) for any node in the network. TxRxTiimngError is the measured TX timing error and RX timing error values, and each value is associated with a quality value nr-timing-Quality. An example of the IE format is provided below. Note, that in general k0- r17, k1-r17, …, k5-r17 can take any integer value. ASN1START NR-TxRxTimingError -r17 ::= SEQUENCE (SIZE(1..2)) OF NR-TxRxTimingError- r17 NR-TxRxTimingError -r17 ::= SEQUENCE { nr-TxRxTimingError -r17 CHOICE { k0-r17 INTEGER(0..16351), k1-r17 INTEGER(0..8176), k2-r17 INTEGER(0..4088), k3-r17 INTEGER(0..2044), k4-r17 INTEGER(0..1022), k5-r17 INTEGER(0..511), } ... nr-timing-Quality-r17 NR-TimingQuality-r17 OPTIONAL,

} ASN1STOP nr- RxTimingErrorDifference specifies the Tx timing error and Rx timing error

for any node in the network. A positive value indicates that the absolute measured error should be subtracted from the actual timing-based measurements; a negative value indicates that the absolute measured error should be added to the actual UL-TDOA measurements to generate a correct RSTD estimate. In one or more embodiments, a measurement quality field contains Information Element (IE) NR-Timing-Quality with the subfields specified below. This field may be used as a part of the measurement types specified above. An example of the IE format is provided below. Note, that in general timingQualityValue-r17 can take any integer value and timingQualityResolution-r17 may define any resolution, represented in meters, including any fractional parts.

ASN1STOP timingQualityValue provides an estimate of uncertainty of the timing value for which the IE NR-TimingQuality is provided in units of meters. timingQualityResolution provides the resolution used in the timingQualityValue field. Enumerated values x0, x1, x2, x3, x4 may correspond to the 0.001, 0.01, 0.1, 1, 10 meters, respectively. Any other resolution as a fractional part of meter is possible. In one or more embodiments, in addition to the measurement quality field, the average residual synchronization error Information Element (IE) NR-ResidualTimingError is introduced to provide the information about statistical timing error dependent on the non- compensated TX/RX timing error from TRP/UE incorporated in the distance measurements. The IE can have the subfields specified below. An example of the IE format is provided below. Note, that in general, residualTimingErrorValue-r17 can take any integer value and residualTimingErrorResolution-r17 may define any resolution, represented in meters, including any fractional parts.

ASN1STOP resisualTimingErrorValue provides an estimate of uncertainty of the residual timing error value for which the IE NR-ResidualTimingError is provided in units of meters. residualTimingErrorResolution provides the resolution used in the resisualTimingErrorValue field. Enumerated values x0, x1, x2, x3, x4 may correspond to the 0.001, 0.01, 0.1, 1, 10 meters, respectively. Any other resolution as a fractional part of meter is possible. The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures. FIG. 1 is a network diagram illustrating an example network environment 100, according to some example embodiments of the present disclosure. Referring to FIG. 1, the network environment 100 may include a UE 102 and three gNBs (gNB0104, gNB1106, and gNB2108), although additional gNBs may be included. Any of the gNBs may be TRPs (e.g., TRP0, TRP1, and/or TRP2), and the positioning techniques described herein would be the same. For the UE 102 to perform device positioning, the UE 102 may need to estimate the unknown propagation time between the UE 102 and each of the three gNBs, where the unknown propagation time for the i-th gNB is denoted as

(e.g., for the propagation time between the UE 102 and the gNB0104, for the propagation

time between the UE 102 and the gNB1106, and for the propagation time between the

UE 102 and the gNB2108). For DL positioning, the UE 102 may use Equation (1) above to determine the respective propagation times between the UE 102 and the i-th gNB, the respective propagation times represented by . For UL positioning, the UE 102 may use

Equation (2) above to determine the respective propagation times between the UE 102 and the i-th gNB, the respective propagation times represented by Each of the UE 102 and the

gNBs may have a sum of transmission and reception errors. For example, the antenna errors for the UE 102 may be represented by

where

is the transmission antenna error (e.g., for the antenna used to transmit to a gNB) and is the reception

antenna error (e.g., for the antenna used to receive from a gNB). In one or more embodiments, for DL-TDOA positioning, the UE 102 may use Equation (3) above. For UL-TDOA positioning, the UE 102 may use Equation (4) above. For multi- RTT positioning, the UE 102 may use Equation (5) above. For multi-RTT time difference positioning, the UE 102 may use Equation (6) above. The UE 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, the UE 102 may include, a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook^TM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a Blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list. As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light- emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.). Any of the UE 102 and the gNBs may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the UE 102 and the gNBs. Some non-limiting examples of suitable communications antennas include 3GPP antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple- input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the UE 102 and the gNBs. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. FIG. 2 is a network diagram illustrating an example network environment 200 for network-based timing error estimation, in accordance with one or more example embodiments of the present disclosure. Referring to FIG. 2, the network environment 200 may include the gNBs of FIG. 1 (e.g., the gNB0104, the gNB1106, and the gNB2108), which may perform network-based (e.g., inter-gNB or inter-TRP) timing error estimation for transmission and reception antennae. Each of the i-th gNBs may have an internal transmission timing error (^_்^,^) and an internal reception timing error

for it’s transmit and reception antennae. The transmission and reception timing errors for any gNB may be different and caused by different sources. The ideal timing propagation time between each pair of gNBs (e.g., an i-th gNB and a j-th gNB)

may be known by the gNBs (e.g., determined based on an ideal knowledge of the coordinates of the gNBs). For example, the ideal timing propagation time _^^^ represents the ideal propagation time between the gNB0104 and the gNB1106, the ideal timing propagation time ^_^ଶ represents the ideal propagation time between the gNB0104 and the gNB2108, and the ideal timing propagation time

represents the ideal propagation time between the gNB1106 and the gNB2108. The gNBs may measure the propagation time between one another. For example, the propagation time represents the propagation time between an i-th gNB and a

j-th gNB (e.g., and for the propagation times between the gNB0104 and the gNB1

106, and

for the propagation times between the gNB0104 and the gNB2108, and and for the propagation times between the gNB1106 and the gNB2108). In one or more embodiments, signal exchanges between the gNBs may result in the ideal propagation times and determined propagation times, which may be represented by the series of Equations (7) and (8) above. A gNB using DL TDOA positioning may use Equations (9) and (10) above. A gNB using UL TDOA positioning may use Equations (11) and (12). A gNB using multi-RTT positioning may use Equations (13)-(18). FIG. 3 illustrates a flow diagram of illustrative process 300 for wireless device positioning, in accordance with one or more example embodiments of the present disclosure. At block 302, a device (e.g., the UE 102, the gNB0104, the gNB1106, or the gNB2 108 of FIG. 1) may identify (e.g., detect and decode) a signal received from another device. The signal may be a reference signal received from a UE or gNB, or a signal sent in response to a reference signal sent by the second device in response to a reference signal sent by the device to the second device. At block 304, the device may determine a first propagation time based on the time difference between the transmission time of the signal from the second device and the reception time of the signal at the device. At block 306, the device may determine a second propagation time by using Equation (1) or Equation (2) above, depending on whether the device is a UE performing DL calculations or a gNB performing UL calculations. At block 308, the device may generate and send a report (e.g., a measurement report) to another device, either a gNB or an LMF (e.g., see FIG. 4). The device may be a UE that generates and sends the measurement report to a gNB or LMF, or the device may be a gNB that generates and sends the measurement report to an LMF or that receives the measurement report from a UE and sends the measurement report to the LMF on behalf of the UE. The measurement report may include a timing quality information element and a residual error element to be considered when determining and compensating for timing errors used in device positioning operations. At block 310, optionally, the device may determine device positioning and timing errors. The device may use Equations (7)-(19) based on the technique used to estimate timing errors and determine device position. The device may perform the calculations or may rely on the LMF to perform the calculations. The examples herein are not meant to be limiting. FIG.4 illustrates a network 400, in accordance with one or more example embodiments of the present disclosure. The network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. The UE 402 may be communicatively coupled with the RAN 404 by a Uu interface. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. In some embodiments, the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. In some embodiments, the UE 402 may additionally communicate with an AP 406 via an over-the-air connection. The AP 406 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources. The RAN 404 may include one or more access nodes, for example, AN 408. AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 408 may enable data/voice connectivity between CN 420 and the UE 402. In some embodiments, the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. Refer to the AN 408 as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 404 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. The ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access. The UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc. The RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol. In V2X scenarios, the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands. In some embodiments, the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418. The gNB 416 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface. In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 414 and an AMF 444 (e.g., N2 interface). The NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 402). The components of the CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice. In some embodiments, the CN 420 may be an LTE CN 422, which may also be referred to as an EPC. The LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows. The MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc. The SGW 426 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc. The S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states. The HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 420. The PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application/content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled with the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 436 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 432 may be coupled with a PCRF 434 via a Gx reference point. The PCRF 434 is the policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app/content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, AF 460, and LMF 462 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 440 may be briefly introduced as follows. The AUSF 442 may store data for authentication of UE 402 and handle authentication- related functionality. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 over reference points as shown, the AUSF 442 may exhibit an Nausf service-based interface. The AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402. The AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, and mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages. AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF. AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Furthermore, AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface. The SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436. The UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to support multi-homed PDU session. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 450 may select a set of network slice instances serving the UE 402. The NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 450, which may lead to a change of AMF. The NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface. The NEF 452 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc. In such embodiments, the NEF 452 may authenticate, authorize, or throttle the AFs. NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface. The NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface. The PCF 456 may provide policy rules to control plane functions to enforce them, and may support unified policy framework to govern network behavior. The PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458. In addition to communicating with functions over reference points as shown, the PCF 456 exhibit an Npcf service-based interface. The UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. The UDM 458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, and subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 458 may exhibit the Nudm service-based interface. The AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 440 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered a trusted entity, the network operator may permit AF 460 to interact directly with relevant NFs. Additionally; the AF 460 may exhibit an Naf service-based interface. The data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 438. The LMF 462 may receive measurement information (e.g., measurement reports) from the NG-RAN 414 and/or the UE 402 via the AMF 444. The LMF 462 may use the measurement information to determine device locations for indoor and/or outdoor positioning. FIG.5 schematically illustrates a wireless network 500, in accordance with one or more example embodiments of the present disclosure. The wireless network 500 may include a UE 502 in wireless communication with an AN 504. The UE 502 and AN 504 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 502 may be communicatively coupled with the AN 504 via connection 506. The connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. The UE 502 may include a host platform 508 coupled with a modem platform 510. The host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. The application processing circuitry 512 may run various applications for the UE 502 that source/sink application data. The application processing circuitry 512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506. The layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions. The modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or more antenna panels 526. Briefly, the transmit circuitry 518 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 522 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 518, receive circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc. In some embodiments, the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components. A UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 526. A UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526. In some embodiments, the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526. Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. The host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530. The modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546. The components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502. In addition to performing data transmission/reception as described above, the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. FIG.6 is a block diagram 600 illustrating components, in accordance with one or more example embodiments of the present disclosure. The components may be able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 6 shows a diagrammatic representation of hardware resources including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources. The processors 610 may include, for example, a processor 612 and a processor 614. The processors 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor’s cache memory), the memory/storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media. For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary. As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit. As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner. The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards. Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on- board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like. Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like. Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks. Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject- matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. Example 1 may be an apparatus for a device for determining wireless device positioning, the device comprising memory and processing circuitry configured to: detect a signal received from a second device; determine a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the device; determine a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the device to receive the signal; and generate a report to be transmitted, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the device or the second device based on the second propagation time, and the residual error information element indicative of the sum. Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the device is a radio node B, wherein the second device is a user equipment device, and wherein the processing circuitry is further configured to detect the report, the report received by the radio node B from the user equipment device, wherein the radio node B sends the report to a Location Management Function of a Fifth Generation Core Network (5GC). Example 3 may include the apparatus of example 1 and/or some other example herein, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B. Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC). Example 5 may include the apparatus of any of examples 1-4 and/or some other example herein, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the device to the second device, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the device to send a fifth signal. Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the device is a user equipment device, wherein the second device is a first radio node B, and wherein the processing circuitry is further configured to: detect a second signal received from a third device, wherein the third device is a second radio node B; determine a third propagation time of the second signal based on a difference between a third time when the second signal is sent by the third device and a fourth time when the second signal is received by the device; determine a fourth propagation time of the second signal based on a difference of the third propagation time and a sum of a third timing error of a third antenna used by the third device to send the second signal and a fourth timing error of the second antenna, the second antenna used by the device to receive the second signal; and determine a first sum of a first difference between the second propagation time and the fourth propagation time and a second difference between the first timing error and the third timing error, wherein to determine the position is further based on the first sum. Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the device is a first radio node B, wherein the second device is a user equipment device, and wherein to determine the position is further based on a first sum of a first difference between the second propagation time and a third propagation time and a second difference between second timing error and a third timing error of a third antenna used by a second radio node B to receive a second signal sent by the second device, wherein the third propagation time is based on the first timing error and the third timing error. Example 8 may include the apparatus of example 1 and/or some other example herein, wherein to determine the position is further based on a sum of the second propagation time, one half of a first total timing error associated with the device, and one half of a second total timing error associated with the second device, wherein the first total timing error comprises a sum of the second timing error and a third timing error of a third antenna of the device used to send a second signal to the second device in response to the signal, and wherein the second total timing error comprises a sum of the first timing error and a fourth timing error of a fourth antenna of the second device used to receive the second signal. Example 9 may include the apparatus of example 1 and/or some other example herein, wherein to determine the position is further based on a sum of a first difference between the second propagation time and a third propagation time associated with a third device, and one half of a second difference between a first total timing error associated with the device or the second device and a second total timing error associated with the third device, the third device being a radio node B device. Example 10 may include a computer-readable storage medium comprising instructions to cause processing circuitry of a device, upon execution of the instructions by the processing circuitry, to: detect a signal received from a second device; determine a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the first device; determine a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the first device to receive the signal; and generate a report to be transmitted, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the first device or the second device based on the second propagation time, and the residual error information element indicative of the sum. Example 11 may include the computer-readable medium of example 10 and/or some other example herein, wherein the device is a radio node B, wherein the second device is a user equipment device, and wherein the instructions further cause the processing circuitry to detect the report, the report received by the radio node B from the user equipment device, wherein the radio node B sends the report to a Location Management Function of a Fifth Generation Core Network (5GC). Example 12 may include the computer-readable medium of example 10 and/or some other example herein, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B. Example 13 may include the computer-readable medium of example 14 and/or some other example herein, wherein the first device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC). Example 14 may include the computer-readable medium of any of examples 10-13 and/or some other example herein, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the first device to the second device, a transmit timing error information element, a receive timing error information element, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the first device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the first device to send a fifth signal. Example 15 may include the computer-readable medium of example 10 and/or some other example herein, wherein the first device is a user equipment device, wherein the second device is a first radio node B, and the instructions further cause the processing circuitry to: detect a second signal received from a third device, wherein the third device is a second radio node B; determine a third propagation time of the second signal based on a difference between a third time when the second signal is sent by the third device and a fourth time when the second signal is received by the first device; determine a fourth propagation time of the second signal based on a difference of the third propagation time and a sum of a third timing error of a third antenna used by the third device to send the second signal and a fourth timing error of the second antenna, the second antenna used by the first device to receive the second signal; and determine a first sum of a first difference between the second propagation time and the fourth propagation time and a second difference between the first timing error and the third timing error, wherein to determine the position is further based on the first sum. Example 16 may include the computer-readable medium of example 10 and/or some other example herein, wherein the first device is a first radio node B, wherein the second device is a user equipment device, and wherein to determine the position is further based on a first sum of a first difference between the second propagation time and a third propagation time and a second difference between second timing error and a third timing error of a third antenna used by a second radio node B to receive a second signal sent by the second device, wherein the third propagation time is based on the first timing error and the third timing error. Example 17 may include the computer-readable medium of example 10 and/or some other example herein, wherein determining the position is further based on a sum of the second propagation time, one half of a first total timing error associated with the first device, and one half of a second total timing error associated with the second device, wherein the first total timing error comprises a sum of the second timing error and a third timing error of a third antenna of the first device used to send a second signal to the second device in response to the signal, and wherein the second total timing error comprises a sum of the first timing error and a fourth timing error of a fourth antenna of the second device used to receive the second signal. Example 18 may include the computer-readable medium of example 10 and/or some other example herein, wherein to determine the position is further based on a sum of a first difference between the second propagation time and a third propagation time associated with a third device, and one half of a second difference between a first total timing error associated with the first device or the second device and a second total timing error associated with the third device, the third device being a radio node B device. Example 19 may include a method for determining wireless device positioning, the method comprising: detecting, by processing circuitry of a first device, a signal received from a second device; determining, by the processing circuitry, a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the first device; determining, by the processing circuitry, a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the first device to receive the signal; and generating, by the processing circuitry, a report to transmit, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the first device or the second device based on the second propagation time, and the residual error information element indicative of the sum. Example 20 may include the method of example 19 and/or some other example herein, wherein the first device is a radio node B, wherein the second device is a user equipment device, and the method further comprising detecting the report, the report received by the radio node B from the user equipment device, wherein the radio node B transmits the report to a Location Management Function of a Fifth Generation Core Network (5GC). Example 21 may include the method of example 19 and/or some other example herein, wherein the first device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B. Example 22 may include the method of example 19 and/or some other example herein, wherein the first device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC). Example 23 may include the method of any of examples 19-23 and/or some other example herein, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the first device to the second device, a transmit timing error information element, a receive timing error information element, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the first device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the first device to send a fifth signal. Example 24 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-23 or any other method or process described herein. Example 25 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein. Example 26 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein. Example 27 may include a method, technique, or process as described in or related to any of examples 1-23, or portions or parts thereof. Example 28 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-23, or portions thereof. Example 29 may include a signal as described in or related to any of examples 1-23, or portions or parts thereof. Example 30 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure. Example 31 may include a signal encoded with data as described in or related to any of examples 1-23 or portions or parts thereof, or otherwise described in the present disclosure. Example 32 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure. Example 33 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-23 or portions thereof. Example 34 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-23, or portions thereof. Example 35 may include a signal in a wireless network as shown and described herein. Example 36 may include a method of communicating in a wireless network as shown and described herein. Example 37 may include a system for providing wireless communication as shown and described herein. Example 38 may include a device for providing wireless communication as shown and described herein. Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations. These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks. Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation. Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein. The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.” The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface. The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like. The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources. The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06) and/or any other 3GPP standard. For the purposes of the present document, the following abbreviations (shown in Table 1) may apply to the examples and embodiments discussed herein.

Table 1: Abbreviations:

Claims

CLAIMS What is claimed is: 1. An apparatus of a device for determining wireless device positioning, the apparatus comprising processing circuitry coupled to storage, the processing circuitry configured to: detect a signal received from a second device; determine a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the device; determine a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the device to receive the signal; and generate a report to be transmitted, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the device or the second device based on the second propagation time, and the residual error information element indicative of the sum.

2. The apparatus of claim 1, wherein the device is a radio node B, wherein the second device is a user equipment device, and wherein the processing circuitry is further configured to detect the report, the report received by the radio node B from the user equipment device, wherein the radio node B sends the report to a Location Management Function of a Fifth Generation Core Network (5GC).

3. The apparatus of claim 1, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B.

4. The apparatus of claim 1, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC).

5. The apparatus of any of claims 1-4, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the device to the second device, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the device to send a fifth signal.

6. The apparatus of claim 1, wherein the device is a user equipment device, wherein the second device is a first radio node B, and wherein the processing circuitry is further configured to: detect a second signal received from a third device, wherein the third device is a second radio node B; determine a third propagation time of the second signal based on a difference between a third time when the second signal is sent by the third device and a fourth time when the second signal is received by the device; determine a fourth propagation time of the second signal based on a difference of the third propagation time and a sum of a third timing error of a third antenna used by the third device to send the second signal and a fourth timing error of the second antenna, the second antenna used by the device to receive the second signal; and determine a first sum of a first difference between the second propagation time and the fourth propagation time and a second difference between the first timing error and the third timing error, wherein to determine the position is further based on the first sum.

7. The apparatus of claim 1, wherein the device is a first radio node B, wherein the second device is a user equipment device, and wherein to determine the position is further based on a first sum of a first difference between the second propagation time and a third propagation time and a second difference between second timing error and a third timing error of a third antenna used by a second radio node B to receive a second signal sent by the second device, wherein the third propagation time is based on the first timing error and the third timing error.

8. The apparatus of claim 1, wherein to determine the position is further based on a sum of the second propagation time, one half of a first total timing error associated with the device, and one half of a second total timing error associated with the second device, wherein the first total timing error comprises a sum of the second timing error and a third timing error of a third antenna of the device used to send a second signal to the second device in response to the signal, and wherein the second total timing error comprises a sum of the first timing error and a fourth timing error of a fourth antenna of the second device used to receive the second signal.

9. The apparatus of claim 1, wherein to determine the position is further based on a sum of a first difference between the second propagation time and a third propagation time associated with a third device, and one half of a second difference between a first total timing error associated with the device or the second device and a second total timing error associated with the third device, the third device being a radio node B device.

10. A computer-readable storage medium comprising instructions to cause processing circuitry of a device, upon execution of the instructions by the processing circuitry, to: detect a signal received from a second device; determine a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the device; determine a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the device to receive the signal; and generate a report to be transmitted, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the device or the second device based on the second propagation time, and the residual error information element indicative of the sum.

11. The computer-readable medium of claim 10, wherein the device is a radio node B, wherein the second device is a user equipment device, and wherein the instructions further cause the processing circuitry to detect the report, the report received by the radio node B from the user equipment device, wherein the radio node B sends the report to a Location Management Function of a Fifth Generation Core Network (5GC).

12. The computer-readable medium of claim 10, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B.

13. The computer-readable medium of claim 10, wherein the device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC).

14. The computer-readable medium of any of claims 10-13, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the device to the second device, a transmit timing error information element, a receive timing error information element, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the device to send a fifth signal.

15. The computer-readable medium of claim 10, wherein the device is a user equipment device, wherein the second device is a first radio node B, and the instructions further cause the processing circuitry to: detect a second signal received from a third device, wherein the third device is a second radio node B; determine a third propagation time of the second signal based on a difference between a third time when the second signal is sent by the third device and a fourth time when the second signal is received by the device; determine a fourth propagation time of the second signal based on a difference of the third propagation time and a sum of a third timing error of a third antenna used by the third device to send the second signal and a fourth timing error of the second antenna, the second antenna used by the device to receive the second signal; and determine a first sum of a first difference between the second propagation time and the fourth propagation time and a second difference between the first timing error and the third timing error, wherein to determine the position is further based on the first sum.

16. The computer-readable medium of claim 10, wherein the device is a first radio node B, wherein the second device is a user equipment device, and wherein to determine the position is further based on a first sum of a first difference between the second propagation time and a third propagation time and a second difference between second timing error and a third timing error of a third antenna used by a second radio node B to receive a second signal sent by the second device, wherein the third propagation time is based on the first timing error and the third timing error.

17. The computer-readable medium of claim 10, wherein determining the position is further based on a sum of the second propagation time, one half of a first total timing error associated with the device, and one half of a second total timing error associated with the second device, wherein the first total timing error comprises a sum of the second timing error and a third timing error of a third antenna of the device used to send a second signal to the second device in response to the signal, and wherein the second total timing error comprises a sum of the first timing error and a fourth timing error of a fourth antenna of the second device used to receive the second signal.

18. The computer-readable medium of claim 10, wherein to determine the position is further based on a sum of a first difference between the second propagation time and a third propagation time associated with a third device, and one half of a second difference between a first total timing error associated with the device or the second device and a second total timing error associated with the third device, the third device being a radio node B device.

19. A method for determining wireless device positioning, the method comprising: detecting, by processing circuitry of a first device, a signal received from a second device; determining, by the processing circuitry, a first propagation time of the signal based on a difference between a first time when the signal is sent by the second device and a second time when the signal is received by the first device; determining, by the processing circuitry, a second propagation time of the signal based on a difference of the first propagation time and a sum of a first timing error of a first antenna used by the second device to send the signal and a second timing error of a second antenna used by the first device to receive the signal; and generating, by the processing circuitry, a report to transmit, the report comprising a timing quality information element and a residual error information element, the timing quality information element indicative of an amount of positional uncertainty associated with determining a position of the first device or the second device based on the second propagation time, and the residual error information element indicative of the sum.

20. The method of claim 19, wherein the first device is a radio node B, wherein the second device is a user equipment device, and the method further comprising detecting the report, the report received by the radio node B from the user equipment device, wherein the radio node B transmits the report to a Location Management Function of a Fifth Generation Core Network (5GC).

21. The method of claim 19, wherein the first device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to the radio node B.

22. The method of claim 19, wherein the first device is a user equipment device, wherein the second device is a radio node B, and wherein the report is transmitted to a Location Management Function of a Fifth Generation Core Network (5GC).

23. The method of any of claims 19-22, wherein the report further comprises at least one of: a timing error information element indicative of a difference between the first propagation time and the second propagation time, a total timing error information element indicative of a total roundtrip time difference based on the first propagation time and a third propagation time of a second signal sent by the first device to the second device, a transmit timing error information element, a receive timing error information element, a transmit-receive timing error information element indicative of the sum, a transmit timing error difference based on a difference between the first timing error and a third timing error of a third antenna used to send a third signal to the first device, a receive timing error difference based on a difference between the second timing error and a fourth timing error of a fourth antenna used by a third device to receive a fourth signal, or a transmit-receive timing error information element indicative of the second timing error and a fifth timing error of a fifth antenna used by the first device to send a fifth signal.

24. A computer-readable storage medium comprising instructions to perform the method of any of claims 19-23.

25. An apparatus comprising means for performing any of the methods of claims 19-23.