Next Article in Journal
An Adaptive Track Segmentation Algorithm for a Railway Intrusion Detection System
Next Article in Special Issue
Geodesic-Based Method for Improving Matching Efficiency of Underwater Terrain Matching Navigation
Previous Article in Journal
MicroGal Gravity Measurements with MGS-6 Micro-g LaCoste Gravimeter
Previous Article in Special Issue
Floor Identification Using Magnetic Field Data with Smartphone Sensors
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

Precise Point Positioning Using World’s First Dual-Frequency GPS/GALILEO Smartphone

by
Abdelsatar Elmezayen
* and
Ahmed El-Rabbany
Department of Civil Engineering, Ryerson University, Toronto M5B 2K3, Canada
*
Author to whom correspondence should be addressed.
Sensors 2019, 19(11), 2593; https://doi.org/10.3390/s19112593
Submission received: 29 March 2019 / Revised: 21 May 2019 / Accepted: 3 June 2019 / Published: 6 June 2019
(This article belongs to the Special Issue Multi-Sensor Systems for Positioning and Navigation)

Abstract

:
The release of the world’s first dual-frequency GPS/Galileo smartphone, Xiaomi mi 8, in 2018 provides an opportunity for high-precision positioning using ultra low-cost sensors. In this research, the GNSS precise point positioning (PPP) accuracy of the Xiaomi mi 8 smartphone is tested in post-processing and real-time modes. Raw dual-frequency observations are collected over two different time windows from both of the Xiaomi mi 8 smartphone and a Trimble R9 geodetic-quality GNSS receiver using a short baseline, due to the lack of a nearby reference station to the observation site. The data sets are first processed in differential modes using Trimble business center (TBC) software in order to provide the reference positioning solution for both of the geodetic receiver and the smartphone. An in-house PPP software is then used to process the collected data in both of post-processing and real-time modes. Precise ephemeris obtained from the multi-GNSS experiment (MGEX) is used for post-processing PPP, while the new NAVCAST real-time GNSS service, Germany, is used for real-time PPP. Additionally, the real-time PPP solution is assessed in both of static and kinematic modes. It is shown that the dual-frequency GNSS smartphone is capable of achieving decimeter-level positioning accuracy, in both of post-processing and real-time PPP modes, respectively. Meter-level positioning accuracy is achieved in the kinematic mode.

1. Introduction

Precise point positioning (PPP) is a popular global navigation satellite system (GNSS) positioning technique, due to its ability to provide centimeter to decimeter positioning accuracy using a standalone GNSS receiver [1]. Unfortunately, this positioning accuracy level can only be achieved using a costly geodetic-quality GNSS receiver and antenna. Single frequency (SF) PPP has recently become an interesting research topic due to the relatively low cost of SF GNSS receivers and their usage for several market applications. However, the resulting positioning accuracy of SF-PPP is limited to a few decimeters [2]. In May 2016, Google announced the development of an application that makes the raw GNSS measurements available to Android-based smartphone users [3]. The release of such an application software has opened the way for the development of precise positioning techniques using ultra-low-cost sensors. SF GNSS smartphones were tested in rapid-static mode [4] and in network real-time kinematic (NRTK) mode [5]. GPS SF observations from a Nexus 9 smartphone were processed in carrier-phase-based differential mode with respect to continuous operating reference stations (CORS) with baselines ranging from 10 m to 8 km [4]. Decimeter-level position accuracy was achieved after processing of 15 min of data from the smartphone. SF GPS/GLONASS observations from a Samsung Galaxy S8+ and Huawei P10 plus smartphones were also tested and processed in NRTK positioning mode using virtual reference station (VRS) corrections from a CORS network with an inter-station distance of 50 km [5]. Each smartphone’s NRTK position precision was at the centimeter-level, but the true solution accuracy was at the meter-level due in part to the unknown position of the smartphone’s embedded antenna. The main challenge in applying rapid-static and NRTK techniques is the need for either a base station in the vicinity of the surveying area, which is relatively expensive, or a VRS, which is not available in remote regions. To overcome this limitation, the smartphone’s SF GNSS pseudorange and carrier-phase measurements were processed in PPP mode [6,7]. GPS-only pseudorange and carrier-phase measurements from a Nexus 9 smartphone along with precise ephemeris from the international GNSS service (IGS) were used for PPP processing [7]. The global ionospheric model (GIM) was used to account for the ionospheric delay. The obtained smartphone’s PPP solution precision was 25, 28, and 51 cm in East, North and Up directions, respectively. Moreover, the accuracy of the resulted PPP solution from the used SF smartphone could not be evaluated due to the lack of an exact reference solution.
In 2018, Xiaomi mobile brand released the world’s first dual-frequency GNSS smartphone, Xiaomi mi 8. This smartphone is fitted with Broadcom’s BCM47755 chip, which supports L1/L5 frequencies for GPS and E1/E5 frequencies for Galileo in addition to L1 frequency for GLONASS and BeiDou [8]. The availability of pseudorange and carrier phase measurements on L1/E1 and L5/E5 frequencies allows the user to linearly combine the observations to essentially remove the effect of ionospheric delay. This in turn leads to an enhanced PPP positioning solution. This smartphone is also fitted with several sensors such as accelerometers, gyroscopes, a compass, camera, and barometer, which enable it to produce a variety of georeferenced data sets critical for future smart cities [9], road surface monitoring [10], and for low-cost mobile mapping systems [11]. Real-time PPP can also be obtained by taking the advantage of the real-time precise ephemeris service offered, for example, by the IGS [12].
In this research, the performance of Xiaomi mi 8 smartphone is tested in post-processing PPP and real-time PPP modes using GPS/Galileo observations. The real-time positioning performance of the smartphone is assessed in both of static and kinematic modes. In order to provide the reference positioning solution for both of the geodetic receiver and the smartphone, the collected data are processed in differential mode. The broadcast ephemeris is used for differential mode processing, while precise ephemeris obtained from both of the multi GNSS experiment (MGEX) and the new NAVCAST real-time GNSS service are used for post-processing PPP and real-time PPP modes, respectively. Taking the advantage of the availability of dual-frequency observations from the smartphone, undifferenced ionosphere-free (IF) linear combinations of the pseudorange and carrier-phase measurements are formed and used for PPP. Additionally, the extended Kalman filter (EKF) is used as the core algorithm for PPP processing. As the quality of the smartphone’s GNSS observations are found to be relatively low, the carrier-to-noise (C/N) ratio was used as the basis for their weights. It is shown that the dual-frequency GPS/Galileo smartphone is capable of achieving decimeter positioning accuracy in both of the post-processing PPP and real-time PPP modes for the static case, respectively. However, meter-level positioning accuracy is achieved in the kinematic mode.

2. GPS/Galileo PPP Mathematical Model

The smartphone’s GPS L1/L5 pseudorange and carrier phase measurements and Galileo E1/E5a counterparts are used. In order to account for the ionospheric delay, un-differenced IF linear combinations of the smartphone’s GPS and Galileo measurements are employed in this research as described in Equations (1) to (4) [13].
C I F G = f 1 2 f 1 2 f 5 2 C 1 G f 5 2 f 1 2 f 5 2 C 5 G = ρ G + c d t r G c d t s G + T G + ε C I F G
Φ I F G = f 1 2 f 1 2 f 5 2 Φ 1 G f 5 2 f 1 2 f 5 2 Φ 5 G = ρ G + c d t r G c d t s G + T G + N I F G + ε Φ I F G
C I F E = f 1 2 f 1 2 f 5 2 C 1 E f 5 2 f 1 2 f 5 2 C 5 E = ρ E + c d t r G c d t s E + T E + I S B + ε C I F E
Φ I F E = f 1 2 f 1 2 f 5 2 Φ 1 E f 5 2 f 1 2 f 5 2 Φ 5 E = ρ E + c d t r G c d t s E + T E + N I F E + I S B + ε Φ I F E
where, G and E refer to GPS and Galileo respectively; C1 and C5 refer to the C/A pseudorange measurements on L1/ L5 for GPS and on E1/E5a for Galileo; Φ1 and Φ5 refer to the carrier phase measurements on L1/ L5 for GPS and on E1/E5a for Galileo; f1 and f5 are the L1/E1 and L5/E5a frequencies; ρG, ρE are the geometric range between the receiver and corresponding satellite; c is the speed of light; d t r G is the GPS receiver clock error, which includes the GPS IF linear combination of receiver code hardware delay; d t s G / d t s E are the GPS/Galileo satellite clock errors, which include the GPS/Galileo IF linear combination of satellite code hardware delay; TG and TE are the total tropospheric delay for the GPS and Galileo, respectively; N I F G / N I F E are the GPS/Galileo non-integer IF ambiguity terms, which are a combination of the GPS/Galileo IF linear combinations of satellite code hardware delay, satellite phase hardware delay, receiver code hardware delay, and receiver phase hardware delay; ISB refers to the inter-system bias between the Galileo and GPS satellite systems, which equal the difference between the GPS and Galileo IF linear combination of satellite code hardware delay; ε refers to the multipath effect and un-modeled errors.
GPS satellites clock correction includes IF linear combination of satellites code hardware delays on L1/L2 and Galileo satellites clock correction includes IF linear combination of satellites code hardware delays on E1/E5a [14]. In order to be consistent with GPS satellites clock correction, GPS IF linear combination of smartphone’s pseudorange measurements are corrected by DCBcorr.
D C B c o r r = ( 1.546 D C B P 1 P 2 + D C B P 1 C 1 1.26 D C B C 1 C 5 )
where, DBCcorr, is differential code bias (DCB) correction; DBCP1−P2, DBCP1−C1, DBCC1−C5 are daily GPS DCBs that can be extracted from the bias solution independent exchange format (Bias-SINEX) file.
Additionally, the zenith dry component of the tropospheric delay is accounted for using the Saastamoinen model [15]. Dry and wet mapping functions are determined using Vienna mapping function (VMF), which is based on coefficients derived from the global pressure and ‘temperature 2 wet’ (GPT2w) model [16]. The effects of relativity, sagnac delay, phase centre offset and variation, Earth tides, ocean loading, and phase wind up are modeled as described in [17]. The IF linear combination of pseudorange and carrier phase measurements after accounting for all mentioned errors for GPS and Galileo are summarized in Equations (6) to (9).
C ˜ I F G = ρ G + b r G + m w G z w d G + ε C I F G
Φ ˜ I F G = ρ G + b r G + m w G z w d G + N I F G + ε C I F G
C ˜ I F E = ρ E + b r G + m w E z w d E + I S B + ε C I F E
Φ ˜ I F E = ρ E + b r G + m w E z w d E + I S B + N I F E + ε C I F E
where, zwd is the zenith wet delay; mw is the wet mapping function; b r G = c dt r G .

3. Extended Kalman Filter Mathematical Models and Implementation

The EKF is employed in this research as the core algorithm for the estimation process. It can be implemented in two consequent stages, namely prediction and update [18]. The prediction stage is summarized in Equations (10) to (11).
x k ( ) = Φ k , k 1 x k 1
P k ( ) = Φ k , k 1 P k 1 ( + ) Φ k , k 1 T + Q k , k 1
where, (-) refers to the predicted state; (+) refers to the updated state; k and k-1 are two following epochs; x is the state vector which includes position, receiver clock error, zenith wet tropospheric delay, ISB, and ambiguity parameters; P is the state vector covariance matrix with initial variances as described in reference [19]; Φ is the transition matrix which is the identity matrix; Q is the covariance matrix of the process noise in which the static positon and ambiguity are modeled as constants, while receiver clock error, zenith wet delay, and ISB are modeled as random walk process [20]. The new pseudorange and carrier phase measurements are used to update the predicted state as in Equations (12) to (14).
K k = P k ( ) H k T [ H k P k ( ) H k T + R k ] 1
P k ( + ) = ( I K k H k ) P k ( )
x k ( + ) = x k ( ) + K k [ y k h ( x k ( ) ) ]
where, K is the Kalman gain; H is the matrix of partial derivatives with respect to the unknowns; Rk is the measurements covariance matrix, which is a diagonal matrix with the pseudorange and carrier phase measurements variances as the diagonal elements. Due to the low carrier to noise (C/N) ratio of smartphone’s measurements, the variances can be modeled as a function of C/N as in reference [21]; y includes the pseudorange and carrier phase measurements as in Equation (15).
y = [ C ˜ I F 1 .. C ˜ I F n C ˜ I F 1 .. C ˜ I F m Φ ˜ I F 1 .. Φ ˜ I F n Φ ˜ I F 1 .. Φ ˜ I F m ] T
where, n and m refer to GPS and Galileo satellites numbers; h is the measurement vector.
h = [ A B C D ] T
where,
A = [ ρ 1 , G + b r G + m w 1 , G z w d . . ρ n , G + b r G + m w n , G z w d ] T
B = [ ρ 1 , E + b r G + I S B + m w 1 , E z w d . . ρ 1 , E + b r G + I S B + m w m , E z w d ] T
C = [ ρ 1 , G + b r G + m w , G 1 z w d + N I F 1 , G . . ρ n , G + b r G + m w n , G z w d + N I F n , G ] T
D = [ ρ 1 , E + b r G + I S B + m w 1 , E z w d + N I F 1 , E . ρ 1 , E + b r G + I S B + m w m , E z w d + N I F m , E ] T

4. Data Collection

Two Trimble R9 geodetic receivers with the capability of tracking GPS and Galileo satellites were used in this research. GPS L1/L2 and Galileo E1/E5a pseudorange and carrier phase measurements were collected from the geodetic receivers. GNSS raw measurements from the smartphone can be produced in Rinex 3.03 format using the “Rinex ON” application, which has been developed by Nottingham Scientific Limited (NSL) as part of the Flamingo project [22]. The smartphone can receive only L1/L5 signals for GPS and E1/E5a for Galileo. The smartphone’s GPS L1/L5 and Galileo E1/E5a pseudorange and carrier phase measurements were collected as presented in Table 1.
As shown in Figure 1, one of the geodetic receivers was set over point A, which was the base station, and the other one was set over point B, which was the rover station, with a baseline of 1.30 m. As shown in Figure 2, the rover geodetic receiver was replaced with the smartphone placed horizontally on its back side using a surveying tribrach. Datasets from both of the geodetic receivers and the smartphone were collected in static mode at the Riverdale Park, Toronto, Ontario, Canada under an open sky environment. Three hours of static data from the base receiver were collected. Additionally, about one hour of data from each of the rover geodetic receiver and the smartphone were collected in order to be processed in the DGNSS mode and to ensure that these data were collected under the same environment. The same procedure was repeated for the second dataset collection.
The real-time precise ephemeris obtained from the NAVCAST GNSS PPP service were used in real-time PPP mode. It was announced on October 29, 2018 by Spaceopal Company in Germany [23] and it provides GPS and Galileo orbit and clock corrections to be used with the broadcast ephemeris in order to convert it to the precise ephemeris counterpart. These products are produced based on the RETICLE algorithm developed by the German Aerospace Centre (DLR) [24,25]. NAVCAST GPS/Galileo orbit and clock corrections that are broadcasted every 30 and 5 s, respectively. The NAVCAST real-time products are evaluated in this research by using the precise ephemeris form the MGEX as a reference. The differences between NAVCAST products and precise ephemeris are analyzed over two consecutive days (DOY 36 and 37 of the year 2019). The resulted clock differences are aligned to a reference satellite in order to remove any systematic biases [26]. In this research, GPS satellite PRN 32 and Galileo satellite PRN number 30 are chosen as reference satellites. For GPS satellites, the orbit accuracy is about 2.35 cm, 2.51 cm, 2.27 cm in x, y, and z directions with RMS of 2.67 cm, 3.04 cm, and 2.78 cm as presented in Figure 3. For Galileo satellites, the orbit accuracy is about 2.95 cm, 3.42 cm, 3.38 cm in x, y, and z directions with RMS of 3.95 cm, 3.98 cm, and 3.97 cm for x, y, and z directions as presented in Figure 4. The STD values of GPS satellites clock errors are generally smaller than 0.15 ns with mean STD of 0.064 ns, which is an indication of the accurate clock products, as shown in Figure 5. The STD values of Galileo satellites clock errors are smaller than 0.4 ns with mean RMS of 0.17 ns, as shown in Figure 6.

5. Smartphone’s Data Quality

The transmitted GNSS signals have right-handed circular polarization. As a result, the optimum choice of GNSS antenna is to be right-handed circularly polarized (RHCP) due to the fact that it can discriminate between direct GNSS signal and indirect GNSS signal, which is transformed to left-handed circularly polarized (LHCP) signal [27]. The embedded antennas in smartphones are linear-polarized antennas, which cannot discriminate between direct (RHCP) and indirect (LHCP) signals, leading to noisy measurements and lower carrier-to-noise (C/N) ratio [6]. The quality of the smartphone measurements are lower than the geodetic receiver counterpart, which is attributed to the quality of the receiver-antenna combination. The average C/N values obtained from the smartphone are low with about 10 dB-Hz compared to the geodetic receiver counterpart, as presented in Figure 7.
Additionally, the C/N values from the smartphone are highly variable, which is another indicator of the smartphone’s low quality measurements, as presented in Figure 8, Figure 9, Figure 10 and Figure 11.

6. Results and Analysis

6.1. GNSS Differential Solution

GPS/Galileo dual-frequency observations from both of the smartphone and rover geodetic receiver are processed in differential mode using the TBC software, due to its ability to process multi-constellation multi-frequency observations. The broadcast ephemeris for GPS and Galileo are used to account for satellite orbit and clock errors. The nearest CORS station to the data collection site is Port Weller (PWEL) station with about 47 km baseline. Unfortunately, the available observations from PWEL include only GPS L1/L2 measurements, which makes the use of PW EL as the base station is not applicable, since the smartphone provides only GPS L1/L5 observations. On the other hand, the Trimble R9 receiver can provide L1/L2/L5 measurements for GPS and E1/E5a measurements for Galileo. So, three hours of GNSS observations from the base geodetic receiver are uploaded to Natural Resource Canada (NRCAN) online PPP tool to determine the coordinates of the base station. The DGNSS solutions for the first dataset, which represent the final solutions for both of the geodetic receiver and smartphone, are presented in Table 2.

6.2. PPP Positioning Performance Using the Smartphone

The GPS/Galileo observations from both of the smartphone and rover geodetic receiver are processed using the PPP software developed at Ryerson University as described in Section 1 and Section 3. Precise ephemeris from the MGEX, initial state vector covariance matrix, and initial noise covariance matrix as described in reference [19] are used. However, the process noise variances for the position component are set to zeros because the processing mode is static. Since the exact location of the smartphone antenna is unknown, both of the smartphone and geodetic receiver PPP solutions accuracy are assessed compared to their DGNSS counterparts. PPP solution errors in East, North, and Up directions for both of the smartphone and the geodetic receiver are presented in Figure 12 and Figure 13, respectively.
As in Table 3, the smartphone’s PPP solution RMS errors are 0.507 m, 0.473 m, and 0.559 m in East, North, and Up directions compared to 0.208 m, 0.109 m, and 0.117 m for the geodetic receiver counterpart. The means of the positioning errors are 0.061, 0.056, and 0.100 m in East, North, and Up directions for geodetic receiver, compared to 0.364, 0.310, and 0.305 m for the smartphone’s counterpart.
Another parameter used in this research to assess the smartphone’s PPP solution, is its convergence behavior compared with the geodetic receiver’s PPP solution counterpart. Figure 14, Figure 15, and Figure 16 show the positioning errors at specific time tags for both of the PPP solutions. For the geodetic receiver’s PPP solution, about 8 minutes are needed to achieve less than 0.2 m accuracy for the East component compared to about 25 min for the smartphone’s PPP solution to achieve the same level of accuracy. Additionally, about 8 min are required for the smartphone’s PPP solution to achieve less than 0.3 m accuracy for the North component, compared to less than 0.2 m for the geodetic receiver counterpart. Moreover, about 8 min are needed to reach 0.2 m accuracy for the Up component for the smartphone’s PPP solution and about 0.1 m for the geodetic receiver counterpart.

6.3. Smartphone Real-time PPP Solution

The PPP solution is assessed in both of static and kinematic positioning modes. The real-time PPP processing is performed using the precise ephemeris resulted from the NAVACAT products. The resulted static real-time PPP (RT-PPP) positioning solution, using NAVCAST products, and the post-processed PPP solution of the first data set are presented in Figure 17, Figure 18, and Figure 19.
The RMS of the post-processed PPP solution errors are 0.507 m, 0.473 m, 0.559 m in East, North, and Up directions, respectively, compared to 0.558 m, 0.542 m, and 0.621 m for the RT-PPP counterpart as in Table 4.
For the kinematic test, the post-processed PPP and RT-PPP positioning solutions for the first dataset are presented in Figure 20, Figure 21, respectively. The RMS of the post-processed PPP solution errors are 2.20 m, 2.32 m, 2.03 m in East, North, and Up directions, respectively, compared to 2.28 m, 2.36 m, and 2.12 m for the RT-PPP counterpart.
The resulted static real-time PPP (RT-PPP) positioning solution, using NAVCAST products, and the post-processed PPP solution for the second data set are presented in Figure 22 and Figure 23. The RMS of the post-processed PPP solution errors are 0.668 m, 0.614 m, 0.589 m in East, North, and Up directions, respectively, compared to 0.844 m, 0.647 m, and 0.661 m for the RT-PPP counterpart as in Table 5.
For the kinematic test, the post-processed PPP and RT-PPP positioning solutions of the second dataset are presented in Figure 24, Figure 25, respectively. The RMS of the post-processed PPP solution errors are 2.13 m, 2.07 m, 2.03 m in East, North, and Up directions, respectively, compared to 2.18 m, 2.24 m, and 2.23 m for the RT-PPP counterpart.

7. Conclusions

The positioning performance of the new dual-frequency GNSS smartphone, Xiaomi mi 8, was assessed in both of post-processing and real-time PPP positioning modes. The analysis of the C/N ratio of the smartphone’s GNSS observations showed that it is lower than its geodetic receiver’s counterpart by about 10 dB-Hz. Ryerson University’s PPP software was used to process the smartphone’s dual-frequency GPS/Galileo observations. It was shown that, using the C/N ratio of the smartphone’s observations as the basis for their weights, its PPP solution achieved decimeter-level positioning accuracy in post-processing mode. The smartphone’s real-time PPP was assessed by employing the new NAVCAST real-time GNSS services and its real-time PPP solution showed decimeter-level positioning accuracy. The smartphone showed meter-level kinematic positioning accuracy in both of the real-time and post-processed modes.

Author Contributions

A.E. and A.E.-R. conceived the idea and wrote the paper. A.E. implemented the experimental tests and performed the assessment under the supervision of A.E.-R.

Acknowledgments

This research is supported by the Government of Ontario and Ryerson University through the Ontario Trillium Scholarship. The authors would like to thank the IGS-MGEX for making available the GNSS precise ephemeris, and NRCAN for their permission to use the GNSS PPP online tool. Additionally, the authors would like to thank the following: Trimble for providing them with the TBC software, the Spaceopal company support team for their valuable information and for making the NAVCAST products available, and Nottingham Scientific Limited (NSL) for making Rinex ON application available for free.

Conflicts of Interest

The authors declare no conflict of interest.

References

  1. Kouba, J.; Héroux, P. Precise point positioning using IGS orbit and clock products. GPS Solut. 2001, 5, 12–28. [Google Scholar] [CrossRef]
  2. de Bakker, P.F.; Tiberius, C.C. Real-time multi-GNSS single-frequency precise point positioning. GPS Solut. 2017, 21, 1791–1803. [Google Scholar] [CrossRef] [Green Version]
  3. European Global Satellite Navigation System Agency. WhitePaper on Using GNSS Raw Measurements on Android Devices; Luxembourg: Publications Office of the European Union, 2017. [Google Scholar]
  4. Realini, E.; Caldera, S.; Pertusini, L.; Sampietro, D. Precise gnss positioning using smart devices. Sensors 2017, 17, 2434. [Google Scholar] [CrossRef] [PubMed]
  5. Dabove, P.; Di Pietra, V. Towards high accuracy GNSS real-time positioning with smartphones. Adv. Space Res. 2018, 63, 94–102. [Google Scholar] [CrossRef]
  6. Banville, S.; Van Diggelen, F. Precise positioning using raw GPS measurements from Android smartphones. GPS World 2016, 27, 43–48. [Google Scholar]
  7. Gill, M.; Bisnath, S.; Aggrey, J.; Seepersad, G. Precise point positioning (PPP) using low-cost and ultra-low-cost GNSS receivers. In Proceedings of the ION GNSS, Portland, OR, USA, 25–29 September 2017; pp. 226–236. [Google Scholar]
  8. GPS World Staff. Dual-Frequency GNSS Smartphone Hits the Market GPS World [Online]. 2018. Available online: https://www.gpsworld.com/dual-frequency-gnss-smartphone-hits-the-market/ (accessed on 10 October 2018).
  9. Burch, T. Surveyors and Smart Cities—Partners in Technology GPS World [Online]. 2019. Available online: https://www.gpsworld.com/surveyors-and-smart-cities-partners-in-technology/ (accessed on 10 March 2019).
  10. Sattar, S.; Li, S.; Chapman, M. Road surface monitoring using smartphone sensors: A review. Sensors 2018, 18, 3845. [Google Scholar] [CrossRef] [PubMed]
  11. Al-Hamad, A.; Moussa, A.; El-Sheimy, N. Video-based Mobile Mapping System Using Smartphones. Int. Arch. Photogramm. Remote Sens. Spat. Inf. Scie. 2014, 40, 13. [Google Scholar] [CrossRef]
  12. IGS. International GNSS Real-time Service IGS [Online]. 2019. Available online: http://www.igs.org/rts (accessed on 24 February 2019).
  13. Li, X.; Zhang, X.; Ren, X.; Fritsche, M.; Wickert, J.; Schuh, H. Precise positioning with current multi-constellation global navigation satellite systems: GPS, GLONASS, Galileo and BeiDou. Sci. Rep. 2015, 5, 8328. [Google Scholar] [CrossRef] [PubMed]
  14. Afifi, A.; El-Rabbany, A. Precise point positioning using triple GNSS constellations in various modes. Sensors 2016, 16, 779. [Google Scholar] [CrossRef] [PubMed]
  15. Davis, J.; Herring, T.; Shapiro, I.; Rogers, A.; Elgered, G. Geodesy by radio interferometry: Effects of atmospheric modeling errors on estimates of baseline length. Radio Sci. 1985, 20, 1593–1607. [Google Scholar] [CrossRef]
  16. Böhm, J.; Möller, G.; Schindelegger, M.; Pain, G.; Weber, R. Development of an improved empirical model for slant delays in the troposphere (GPT2w). GPS Solut. 2015, 19, 433–441. [Google Scholar] [CrossRef]
  17. Kouba, J. A Guide to Using International Gnss Service (IGS) Products IGS [Online]. 2015. Available online: https://kb.igs.org/hc/en-us/articles/201271873-A-Guide-to-Using-the-IGS-Products (accessed on 17 December 2018).
  18. Noureldin, A.; Karamat, T.B.; Georgy, J. Fundamentals of Inertial Navigation, Satellite-Based Positioning and Their Integration; Springer Science & Business Media: Berlin, Germany, 2012. [Google Scholar]
  19. Rabbou, M.A.; El-Rabbany, A. Precise point positioning using multi-constellation GNSS observations for kinematic applications. J. Appl. Geod. 2015, 9, 15–26. [Google Scholar] [CrossRef]
  20. Cai, C.; Gao, Y. Modeling and assessment of combined GPS/GLONASS precise point positioning. GPS Solut. 2013, 17, 223–236. [Google Scholar] [CrossRef]
  21. Bona, P.; Tiberius, C. In An experimental comparison of noise characteristics of seven high-end dual frequency GPS receiver-sets. In IEEE 2000. Position Location and Navigation Symposium (Cat. No. 00CH37062); IEEE: Piscataway, NJ, USA, 2000; pp. 237–244. [Google Scholar]
  22. Nottingham Scientific Limited (NSL). NSL Launches a New Free Android App as Part of FLAMINGO–Discover RinexON. 2018. Available online: https://www.flamingognss.com/rinexon (accessed on 10 October 2018).
  23. Spaceopal. Spaceopal Launches Its Precise Point Positioning Service NAVCAST. 2018. Available online: https://spaceopal.com (accessed on 20 December 2018).
  24. Hauschild, A.; Montenbruck, O. In Real-time clock estimation for precise orbit determination of LEO-satellites. In Proceedings of the ION GNSS Meeting, Savannah, GA, USA, 16–19 September 2008; p. 581. [Google Scholar]
  25. Wermuth, M.; Hauschild, A.; Montenbruck, O.; Kahle, R. TerraSAR-X precise orbit determination with real-time GPS ephemerides. Adv. Space Res. 2012, 50, 549–559. [Google Scholar] [CrossRef] [Green Version]
  26. Wang, L.; Li, Z.; Ge, M.; Neitzel, F.; Wang, Z.; Yuan, H. Validation and assessment of multi-gnss real-time precise point positioning in simulated kinematic mode using igs real-time service. Remote Sens. 2018, 10, 337. [Google Scholar] [CrossRef]
  27. Rao, B.R.; Kunysz, W.; McDonald, K. GPS/GNSS Antennas; Artech House: Norwood, MA, USA, 2013. [Google Scholar]
Figure 1. Setup of Trimble R9 geodetic receivers.
Figure 1. Setup of Trimble R9 geodetic receivers.
Sensors 19 02593 g001
Figure 2. Setup of Trimble R9 geodetic receiver and smartphone.
Figure 2. Setup of Trimble R9 geodetic receiver and smartphone.
Sensors 19 02593 g002
Figure 3. RMS of GPS satellites’ orbits based on NAVCAST real-time products.
Figure 3. RMS of GPS satellites’ orbits based on NAVCAST real-time products.
Sensors 19 02593 g003
Figure 4. RMS of Galileo satellites’ orbits based on NAVCAST real-time products.
Figure 4. RMS of Galileo satellites’ orbits based on NAVCAST real-time products.
Sensors 19 02593 g004
Figure 5. STD of GPS satellites’ clocks based on NAVCAST real-time products.
Figure 5. STD of GPS satellites’ clocks based on NAVCAST real-time products.
Sensors 19 02593 g005
Figure 6. STD of Galileo satellites’ clocks based on NAVCAST real-time products.
Figure 6. STD of Galileo satellites’ clocks based on NAVCAST real-time products.
Sensors 19 02593 g006
Figure 7. Average C/N for GPS and Galileo satellites, respectively.
Figure 7. Average C/N for GPS and Galileo satellites, respectively.
Sensors 19 02593 g007
Figure 8. L1 C/N values from the geodetic receivers (geodetic) and the smartphone (smart) for GPS.
Figure 8. L1 C/N values from the geodetic receivers (geodetic) and the smartphone (smart) for GPS.
Sensors 19 02593 g008
Figure 9. L5 C/N values from the geodetic receivers (geodetic) and the smartphone (smart) for GPS.
Figure 9. L5 C/N values from the geodetic receivers (geodetic) and the smartphone (smart) for GPS.
Sensors 19 02593 g009
Figure 10. L1 C/N values from the geodetic receiver (geodetic) and the smartphone (smart) for Galileo.
Figure 10. L1 C/N values from the geodetic receiver (geodetic) and the smartphone (smart) for Galileo.
Sensors 19 02593 g010
Figure 11. L5 C/N values from the geodetic receiver (geodetic) and the smartphone (smart) for Galileo.
Figure 11. L5 C/N values from the geodetic receiver (geodetic) and the smartphone (smart) for Galileo.
Sensors 19 02593 g011
Figure 12. Smartphone PPP solution errors in East, North, and Up directions (dE, dN, dU).
Figure 12. Smartphone PPP solution errors in East, North, and Up directions (dE, dN, dU).
Sensors 19 02593 g012
Figure 13. Geodetic receiver PPP solution errors in East, North, and Up directions (dE, dN, dU).
Figure 13. Geodetic receiver PPP solution errors in East, North, and Up directions (dE, dN, dU).
Sensors 19 02593 g013
Figure 14. Position errors in East direction (meters).
Figure 14. Position errors in East direction (meters).
Sensors 19 02593 g014
Figure 15. Position errors in North direction (meters).
Figure 15. Position errors in North direction (meters).
Sensors 19 02593 g015
Figure 16. Position errors in Up direction (meters).
Figure 16. Position errors in Up direction (meters).
Sensors 19 02593 g016
Figure 17. Position errors in East direction (first dataset).
Figure 17. Position errors in East direction (first dataset).
Sensors 19 02593 g017
Figure 18. Position errors in North direction (first dataset).
Figure 18. Position errors in North direction (first dataset).
Sensors 19 02593 g018
Figure 19. Position errors in Up direction (first dataset).
Figure 19. Position errors in Up direction (first dataset).
Sensors 19 02593 g019
Figure 20. Position errors for the post-processed PPP solution (kinematic/first dataset).
Figure 20. Position errors for the post-processed PPP solution (kinematic/first dataset).
Sensors 19 02593 g020
Figure 21. Position errors for the RT-PPP solution (kinematic/first dataset).
Figure 21. Position errors for the RT-PPP solution (kinematic/first dataset).
Sensors 19 02593 g021
Figure 22. Position errors for the post-processed PPP solution (static/second dataset).
Figure 22. Position errors for the post-processed PPP solution (static/second dataset).
Sensors 19 02593 g022
Figure 23. Position errors for the RT-PPP solution (static/second dataset).
Figure 23. Position errors for the RT-PPP solution (static/second dataset).
Sensors 19 02593 g023
Figure 24. Position errors for the post-processed PPP solution (kinematic/second dataset).
Figure 24. Position errors for the post-processed PPP solution (kinematic/second dataset).
Sensors 19 02593 g024
Figure 25. Position errors for the RT-PPP solution (kinematic/second dataset).
Figure 25. Position errors for the RT-PPP solution (kinematic/second dataset).
Sensors 19 02593 g025
Table 1. Data collected.
Table 1. Data collected.
Receiver TypeGPSGalileo
Trimble R9C1C and L1C, C2W and L2WC1C and L1C, C5X and L5X
smartphoneC1C and L1C, C5X and L5XC1C and L1C, C5X and L5X
Table 2. Geodetic receiver and smartphone DGNSS solutions.
Table 2. Geodetic receiver and smartphone DGNSS solutions.
Receiver TypeDGNSS ITRF Solution (m)
XYZ
Geodetic85,3516.578-454,1447.832438,1617.828
Smartphone85,3516.507-454,1447.881438,1617.659
Table 3. Mean and RMS for East, North, and Up components.
Table 3. Mean and RMS for East, North, and Up components.
Receiver TypedE (m)dN (m)dU (m)
MeanRMSMeanRMSMeanRMS
Geodetic0.0610.2080.0560.1090.1000.117
Smartphone0.3640.5070.3100.4730.3050.559
Table 4. Mean and RMS of East, North, and Up errors for the first data set.
Table 4. Mean and RMS of East, North, and Up errors for the first data set.
PPP SolutiondE (m)dN (m)dU (m)
MeanRMSMeanRMSMeanRMS
post-processed0.3640.5070.3100.4730.3050.559
real-time0.4300.5580.4290.5420.4240.621
Table 5. Mean and RMS of East, North, and Up errors for the second data set.
Table 5. Mean and RMS of East, North, and Up errors for the second data set.
PPP SolutiondE (m)dN (m)dU (m)
MeanRMSMeanRMSMeanRMS
post-processed0.5820.6680.3250.6140.4660.589
real-time0.6500.8440.3900.6470.5550.661

Share and Cite

MDPI and ACS Style

Elmezayen, A.; El-Rabbany, A. Precise Point Positioning Using World’s First Dual-Frequency GPS/GALILEO Smartphone. Sensors 2019, 19, 2593. https://doi.org/10.3390/s19112593

AMA Style

Elmezayen A, El-Rabbany A. Precise Point Positioning Using World’s First Dual-Frequency GPS/GALILEO Smartphone. Sensors. 2019; 19(11):2593. https://doi.org/10.3390/s19112593

Chicago/Turabian Style

Elmezayen, Abdelsatar, and Ahmed El-Rabbany. 2019. "Precise Point Positioning Using World’s First Dual-Frequency GPS/GALILEO Smartphone" Sensors 19, no. 11: 2593. https://doi.org/10.3390/s19112593

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop