2.1. Mathematical modelling

In the process of multi-GNSS real-time kinematic (RTK) positioning, satellite orbit bias, satellite and receiver clock bias, ionospheric delay and tropospheric delay have spatial correlation between base and rover stations, especially in short or medium baselines. Therefore, most of these correlation biases can be eliminated or weakened by the DD observation model in relative positioning.

For GPS or BDS, given the adoption of CDMA technology, all signals transmitted by satellites have the same wavelength on each frequency band, which are processed through a series of identical components at the RF front-end. The hardware delay of the phase and pseudorange observations only contains the same constant part, which can be eliminated by DD processing. Therefore, IFPB and IFCB do not occur in GPS/BDS observations. The GPS/BDS DD pseudorange and phase observation equation can be described as follows:

(1)$$\begin{cases} \rho _{rb,f}^{ij,G/C} =r_{rb,f}^{ij,G/C} +I_{rb,f}^{ij,G/C}+T_{rb,f}^{\,ij,G/C} +\varepsilon _{\rho, rb}^{ij,G/C} \\ \lambda \cdot \phi_{rb,f}^{ij,G/C} =r_{rb,f}^{ij,G/C} -\lambda \cdot N_{rb,f}^{ij,G/C} -I_{rb,f}^{ij,G/C} +T_{rb,f}^{\,ij,G/C} +\varepsilon _{\phi,rb}^{ij,G/C} \end{cases}$$

where superscripts i and j refer to satellites; superscript G/C indicates the GPS or BDS system; subscripts b and r stand for base and rover stations, respectively; subscript f refers to the signal frequency; $\rho_{rb, f}^{ij, G/C} $ and $\phi _{rb, f}^{ij, G/C} $ refer to DD pseudorange and phase observation of GPS/BDS on frequency f, respectively; $r_{rb, f}^{ij, G/C} $ is the DD range between satellite and receiver; $I_{rb, f}^{ij, G/C} $ and $T_{rb, f}^{\, ij, G/C} $ represent DD ionospheric and tropospheric delay, respectively; λ is the signal wavelength; $N_{rb, f}^{ij, G/C} $ represents DD phase ambiguity; $\varepsilon _{\rho, rb}^{ij, G/C} $ and $\varepsilon _{\phi, rb}^{ij, G/C} $ represent the sum of all uncorrected systematic and random errors in the DD pseudorange and phase observation, respectively. In addition, satellite orbit bias and multipath errors are not represented in Equation (1).

Unlike GPS or BDS, the GLONASS system employs FDMA technology, which causes all signals transmitted by GLONASS satellites to have different wavelengths on each frequency band, and different satellites are identified by various frequencies. Therefore, the hardware delay of GLONASS observations varies with signals' frequencies, and these hardware delays consist of a constant part and a frequency-dependent part (Wanninger, Reference Wanninger2012). The constant part can be absorbed by the receiver clock bias similar to GPS and BDS, and the residuary hardware delay of the frequency-dependent part causes IFPB and IFCB after DD processing.

IFPB is primarily related to receiver manufacturer and has a linear relationship with signal frequency. The SD and DD IFPB can be expressed as follows:

(2)$$\begin{cases} b_{b,f}^{i,R} -b_{b,f}^{\,j,R} =(b_{b,f}^R +k^i\cdot \delta b_{b,f}^R )-(b_{b,1}^R +k^j\cdot \delta b_{b,f}^R )=(k^i-k^j)\cdot \delta b_{b,f}^R \\ (b_{r,f}^{i,R} -b_{r,f}^{\,j,R} )-(b_{b,f}^{i,R} -b_{b,f}^{\,j,R} )=(k^i-k^j)\cdot (\delta b_{r,f}^R -\delta b_{b,f}^R )=k^{ij}\cdot \delta b_{rb,f}^R \end{cases}$$

where superscript R indicates the GLONASS system; $b_{b, f}^{i, R} $ refers to the hardware delay of the phase observation of satellite i received by the receiver of station b on frequency f; $b_{b, f}^{R} $ represents the constant part of the hardware delay; k is the GLONASS frequency number; $k^{i}\cdot \delta b_{b, f}^{R} $ represents the frequency-dependent part of the hardware delay; $k^{ij}\cdot \delta b_{rb, f}^{R} $ stands for IFPB after DD process; and $\delta b_{rb, f}^{R} $ is mainly related to receiver manufacturer, which is usually called the IFPB rate between stations r and b on frequency f.

Calibrating the effects of IFCB is difficult, however, due to the complicated characteristics of IFCB compared with IFPB. No obvious linear relationship can be observed between IFCB and GLONASS frequency numbers, and IFCB is extremely susceptible to receiver firmware version, antenna type and other factors. In addition, IFCB still occurs even with a homogeneous baseline that consists of receivers from the same manufacturer. Therefore, the IFCB should be estimated on each satellite (Shi et al., Reference Shi, Yi, Song, Lou, Yao and Zhang2013; Song et al., Reference Song, Yi, Lou, Shi, Yao, Liu, Mao and Xiang2014; Liu et al., Reference Liu, Li, Zhang, Zhu and Ren2016). Considering IFPB and IFCB, GLONASS DD phase and pseudorange observation equations can be described as

(3)$$\begin{cases} \rho _{rb,f}^{ij,R} =r_{rb,f}^{ij,R} +B_{rb,f}^i -B_{rb,f}^j +I_{rb,f}^{ij,R} +T_{rb,f}^{\,ij,R} +\varepsilon _{\rho, rb}^{ij,R} \\ \Phi _{rb,f}^{ij,R} =r_{rb,f}^{ij,R} -(\lambda _i^R -\lambda _j^R )\cdot N_{rb,f}^{\,j,R} -\lambda _i^R \cdot N_{rb,f}^{ij,R} +k^{ij}\cdot \delta b_{rb,f} -I_{rb,f}^{ij,R} +T_{rb,f}^{\,ij,R} +\varepsilon _{\phi, rb}^{ij,R} \end{cases}$$

where $\Phi _{rb, f}^{ij, R} =\lambda _{i} \cdot \phi _{rb, f}^{i, R} -\lambda _{j} \cdot \phi _{rb, f}^{\, j, R} $ represents GLONASS phase observation after DD processing, $( \lambda _{i}^{R} -\lambda _{j}^{R} ) \cdot N_{rb, f}^{\, j, R} -\lambda _{i}^{R} \cdot N_{rb, f}^{ij, R} $ is the transformation form of GLONASS DD ambiguity to obtain integer characteristics of GLONASS ambiguity (Wang, Reference Wang2000; Takac, Reference Takac2009), $N_{rb, f}^{\, j, R} $ refers to SD ambiguity of GLONASS reference satellite, and $B_{rb, f}^{i} $ is the IFCB of satellite i between stations b and r. Other variables have the meanings stated previously.

During the process of calculating GLONASS measurements, the DD ionospheric delay will be eliminated by Klobuchar model correction instead of estimation. The DD zenith tropospheric dry delay will be eliminated by Saastamoinen model correction and DD zenith tropospheric wet delay will be provided by the estimation results of GPS/BDS. From Equation (3), the IFPB rate and IFCB, station coordinates and DD ambiguity need to be estimated. The station coordinates and IFCB do not need to be estimated simultaneously in GLONASS pseudorange observation equations due to multi-GNSS assistance and IFCB calibration.

Different estimations and calibration strategies need to be implemented due to various statistical characteristics (Yamada et al., Reference Yamada, Takasu, Kubo and Yasuda2010; Reussner and Wanninger, Reference Reussner and Wanninger2011). In this study, the IFPB rates for all GLONASS satellites and the IFCB for each GLONASS satellite are estimated and calibrated.

2.2. IFPB estimation and calibration

In the algorithm of GLONASS IFPB estimation based on multi-GNSS assistance, the fixed solution of the GPS/BDS system will be calculated initially as rover approximate coordinates, and the parameters of float ambiguity and IFPB rate estimated using GLONASS DD observation by Kalman filter. The IFPB rates on L1 and L2 frequencies are estimated as different parameters, and the calculation model is shown as Equation (4). The constant IFPB rate will be obtained when GLONASS DD ambiguity can be accurately fixed by the LAMBDA algorithm. The initialisation verification will be completed if the ambiguity is successfully fixed for more than 10 epochs and the differences of IFPB estimation value between two epoch are less than 2 mm. After verifying the correctness and stability of the constant IFPB rate, the initialisation process of estimation IFPB is accomplished.

(4)$$\Phi_{rb,f}^{ij,R} =k^{ij}\cdot \delta b_{rb,f}^R -(\lambda _i^R -\lambda_j^R )\cdot N_{rb,f}^{\,j,R} -\lambda _i^R \cdot N_{rb,f}^{ij,R}+l_{rb,f}^{ij,R}$$

where $l_{rb, f}^{ij, R} =( r_{r, f}^{i, R} ) _{0}^{G/C} -r_{b, f}^{i, R} -( r_{r, f}^{\, j, R} ) _{0}^{G/C} +r_{b, f}^{\, j, R} -I_{rb, f}^{ij, R} +T_{rb, f}^{\, ij, R}$ represents the constant portion after subtracting the known geometric distance and atmospheric delay.

After accomplishing the IFPB initialisation process, the constant IFPB calibration and real-time calibration method can be selected. In the method of constant IFPB calibration, given that most of the effects caused by IFPB can be eliminated by constant IFPB rate, GLONASS phase observations can be directly corrected with constant IFPB rate as a constant in Equation (3) and participate in the Kalman filter together with Equation (1) to obtain a highly accurate fixed solution of multi-GNSS. In the method of real-time IFPB calibration, the parameters of the IFPB rate can be estimated by Kalman filter together with coordinate components and ambiguity to obtain accurate fixed solutions and real-time IFPB rate due to the existence of the constant IFPB rate.

The flow chart of IFPB estimation and calibration is shown in Figure 1. If initialisation is not completed, only GPS/BDS positioning results are output, which are used as rover approximate coordinates to rapidly estimate the constant IFPB rate. Multi-GNSS positioning results will not be output until the IFPB initialisation process is correctly verified. Then constant IFPB calibration and real-time IFPB calibration method can be selected conveniently to meet the different requirements.

Figure 1.

Flow chart of IFPB estimation and calibration.

2.3. IFCB estimation and calibration

Similar to the IFPB estimation method, IFCB estimation is also based on multi-GNSS assistance, and the fixed solution of GPS/BDS is used as rover approximate coordinates, which are no longer estimated in the process of estimating IFCB. The IFCB of each satellite at each frequency needs to be estimated, however, because the IFCB for different satellites cannot be represented by a linear model (Shi et al., Reference Shi, Yi, Song, Lou, Yao and Zhang2013; Liu et al., Reference Liu, Gu and Li2018). The IFCB estimation model on the frequency f is expressed as follows:

(5)$$\rho _{rb,f}^{ij,R} =\delta B_{rb,f}^{ij} +l_{rb,f}^{ij,R}$$

where $\delta B_{rb, f}^{ij} $ represents the IFCB difference between satellites i and j and stations b and r on frequency f, which will be replaced by IFCB in this study and can be represented by Equation (6). The meaning of the constant term $l_{rb, f}^{ij, R} $ is the same as in Equation (5). The initialisation verification will be completed if the ambiguity is successfully fixed for more than 10 epochs and the differences of IFCB estimation value between two epochs are less than 10 cm.

(6)$$\delta B_{rb,f}^{ij} =B_{rb,f}^i -B_{rb,f}^j$$

The IFCB cannot be calibrated directly as a constant similar to a constant IFPB rate because satellite lifting or changes in reference satellites is often encountered during positioning. Figure 2 shows the flow chart of IFCB estimation and calibration. The IFCB estimation process is performed based on the fixed solution provided by GPS and BDS to rapidly obtain the current epoch IFCB, which will not used for the next epoch GLONASS measurements calibration until the IFPB initialisation process is correctly verified. The next epoch IFCB continues to be updated, and the entire cycle process of IFCB estimation and calibration is implemented.

Figure 2.

Flow chart of IFCB estimation and calibration.

3.1. Analysis of IFB estimation results

We calculate the GLONASS IFPB rate for all GLONASS satellites and IFCB for each GLONASS satellite of the four types of baselines on L1 frequency to analyse the stability of IFPB and IFCB rates estimated by the algorithm presented in Section 2. The differences between the constant IFPB rates and the mean values of real-time IFPB rates and the STD of IFPB rate and IFCB are analysed. The situations of reference satellite change are also considered in these experiments.

The constant IFPB rate, real-time IFPB rate and IFCB of the four types of baselines are estimated, and each type of baseline contains inhomogeneous and homogeneous baselines. The sequence diagrams of the IFPB rate and IFCB of four types of baselines are shown in Figures 3–6. In each diagram in Figures 3–6, the two top subgraphs represent the IFPB rate, and red and blue represent the constant IFPB and IFPB rate, respectively. The two bottom subgraphs represent the IFCB between satellites and their reference satellite. The left and right subgraphs represent the inhomogeneous and homogeneous baselines, respectively. In Figure 6, the IFPB initialisation process was restarted after the failure of ambiguity resolution in the medium baseline HKKT-HKKS.

Figure 3.

IFPB rate and IFCB for zero baselines (CUT0-CUT1 and CUT0-CUT2).

Figure 4.

IFPB rate and IFCB for ultra-short baselines (WUS1-WUU1 and WUS1-WUS2).

Figure 5.

IFPB rate and IFCB for short baselines (HKWS-HKKS and HKWS-HKSS).

Figure 6.

IFPB rate and IFCB for medium baselines (HKKT-HKKKS and HKKT-HKWS).

In the two top subgraphs from Figures 3–6, whether the baseline is short or medium, the estimated real-time IFPB rates are so stable that their change range is less than 3 mm. The differences between constant and real-time IFPB rates are also within 3 mm. Figure 7 shows the statistical results of constant IFPB rate and the mean value of real-time IFPB rate of the four types of inhomogeneous and homogeneous baselines. In Figure 7, the differences between the constant IFPB rates and the mean value of real-time IFPB rates are extremely small, both being less than 2 mm. The IFPB rates of the inhomogeneous baselines are generally at the centimetre level. By contrast, the IFPB rates of the homogeneous baselines are generally less than 1 mm, indicating that their IFPB has been eliminated during the DD process. Figure 8 shows the STD statistics for real-time IFPB rates estimated from all baselines, which are less than 0·3 mm. Moreover, the stability of IFPB rates will be improved when the baseline is shortened.

Figure 7.

IFPB rates for the four types of baselines (zero, ultra-short, short and medium baselines).

Figure 8.

IFPB rate STD for all types of baselines (zero, ultra-short, short and medium baselines).

The initialisation process is implemented every 3 min to analyse the IFPB initialisation time of IFPB estimation. Table 2 shows the average times of 20 initialisation processes for all types of baselines for 1 h. Table 2 shows that the initialisation process of IFPB estimation can be implemented within several seconds for short baseline and several minutes for medium baseline.

Table 2.

Average initialisation time of IFPB estimation for four types of baselines.

The two subgraphs from Figures 3–6 show that the IFCB between inhomogeneous baselines can converge to a stable value within 200–400 epochs. Figure 9 shows the statistical results for the IFCBs of four types of inhomogeneous and homogeneous baselines. The IFCBs of inhomogeneous baselines can be as high as several metres, whereas the IFCBs of homogeneous baselines are generally within 5 cm. Figure 10 shows the variance statistics for real-time IFCB estimated from all baselines. The variances in IFCB are within 0·2 m for all homogeneous baselines. Similar to the IFPB rate, IFCB also shows remarkable stability with short baselines. Moreover, even for medium baselines, the STD of IFCB between homogeneous baselines remains small.

Figure 9.

IFCB for four types of baselines.

Figure 10.

IFCB STD for four types of baselines.

The IFCB of all satellites will change with the switch of the reference satellite. Therefore, to analyse the stability of the IFCB, 1 h observation data with no change in the reference satellite was used in this study. Figure 11 shows the estimation of the IFPB rate and IFCB for baseline CUT0-CUT1 with 3 h observation data. In Figure 11, when the reference satellite changes, IFPB rate varies slightly and IFCB remains stable after the conversion of reference satellite IFCB.

Figure 11.

IFPB rate and IFCB for baseline CUT0-CUT1 with 3 h observations.

3.2. Positioning performance analysis

After the estimation of stable results for the IFPB rate and IFCB in previous sections, we will analyse the positioning performance in this section. First, the positioning results with IFB calibration will be compared with no IFB calibration and with GPS/BDS to verify the necessity of IFB calibration. The influence of IFPB accuracy on positioning results and fixed rates is analysed to verify the availability of constant and real-time IFPB rates estimated by this algorithm. The positioning results and fixed rates with two calibration methods (real-time and constant IFPB and IFCB calibration) are then analysed and contrasted with GPS/BDS. Finally, the enhancements of calibrated GLONASS observations for GPS/BDS positioning performance will be verified with different satellite cut-off elevation angles to simulate satellite-deprived environments.

The multi-GNSS positioning results calculated with IFB calibration will be compared with no IFB calibration to verify the necessity of IFB calibration in this algorithm. Moreover, we also calculate the positioning results of GPS/BDS to reflect the significance of GLONASS measurements separately. Figure 12 shows the GNSS position errors of two inhomogeneous baselines with IFB calibration compared with no IFB calibration and GPS/BDS. The three subgraphs indicate the positioning results of baseline CUT0-CUT1, and the three subgraphs indicate the positioning results of baseline HKWS-HKKS. In Figure 12, without IFB calibration, the zero-baseline GLONASS ambiguity can be fixed because the IFPB rate of baseline CUT0-CUT1 is only a few millimetres, but the positioning results are affected by IFPB rate. GLONASS satellites cannot be positioned normally due to the influence of millimetre-level IFPB rate, which means that positioning results are exactly the same as GPS/BDS. After IFB calibration, the positioning results of baseline CUT0-CUT1 can be significantly improved, and the GLONASS ambiguity of baseline HKWS-HKKS can be substantially fixed. In addition, the GNSS positioning results with IFB calibration are 10%–20% better than GPS/BDS due to the calibrated GLONASS measurements.

Figure 12.

Position errors with IFB calibration compared with no IFB calibration and GPS/BDS for baseline CUT0-CUT1 (top three subgraphs) and baseline HKWS-HKKS (bottom three subgraphs).

Although the constant and real-time IFPB rates estimated by this algorithm exhibit remarkable accuracy and stability, the effects of IFPB rate accuracy on positioning results need to be further analysed to ensure the availability of constant and real-time IFPB rates. The mean values of real-time IFPB rates are used as the accurate IFPB rate, and certain errors (several millimetres) are added on this accurate rate to calculate the positioning results with constant IFPB calibration. Figure 13 shows the influence of IFPB accuracy on the positioning results and ambiguity fixed rates for baselines CUT0-CUT1 and HKWS-HKKS. In Figure 13, when the errors of IFPB rates are within 5 mm, the positioning root mean square (RMS) will slightly decrease as the errors of the IFPB rate increase, but the ambiguity fixed rates are unaffected. When the errors of IFPB rate exceed 5 mm, the ambiguity fixed rates decrease sharply with poor positioning results. Therefore, the accuracy of constant and real-time IFPB rates estimated by this algorithm can meet the requirements of precise positioning.

Figure 13.

Influence of IFPB accuracy on the positioning results and ambiguity fixed rates for baselines CUT0-CUT1 and HKWS-HKK.

The positioning results and ambiguity fixed rates for the four types of inhomogeneous baselines are calculated separately to analyse the influence of two IFPB and IFCB calibration methods. Table 3 shows the statistics of position RMS and ambiguity fixed rates with two IFPB and IFCB calibration methods compared with GPS/BDS. Method 1 indicates constant IFPB and IFCB calibration, and Method 2 indicates real-time IFPB and IFCB calibration. In Table 3, with two IFPB and IFCB calibration methods, the position RMS of the multi-GNSS in the horizontal direction are about 1 cm, and the position RMS in the vertical direction are better than 4 cm. Ambiguity fixed rates are also more than 97% for short baseline and more than 88% for medium baseline, which are better than the positioning results of GPS/BDS. The positioning results with real-time IFPB and IFCB calibration are 10%–20% better than those with constant IFPB and IFCB calibration due to the influence of IFPB residual errors, especially on long baselines.

Table 3.

Position RMS and ambiguity fixed rate with two IFPB and IFCB calibration methods compared with GPS/BDS.

Note: Method 1: real-time IFPB and IFCB calibration; Method 2: constant IFPB and IFCB calibration.

When real-time calibration cannot be implemented under satellite-deprived environments, the enhancements of constant IFB calibrated GLONASS observations for GPS/BDS positioning performance will be verified with different satellite cut-off elevation angles. Figure 14 shows the number of GLONASS satellites with different cut-off elevation angles (from 10^° to 40^°). Figure 15 shows the position RMS of multi-GNSS and GPS/BDS with different cut-off elevation angles. Figure 16 shows the improvement of multi-GNSS positioning accuracy with IFB calibration compared with GPS/BDS with different satellite cut-off elevation angles. In Figure 14, when cut-off elevation angle is set to less than 20^°, the number of GLONASS satellites is from four to six, when cut-off elevation angle is set to more than 20^°, the number of GLONASS satellites is two or three. The participation of the GLONASS system can still increase the number of visible satellites as appropriate.

Figure 14.

Number of GLONASS satellites with different satellite cut-off elevation angles for baselines CUT0-CUT1 and HKWS-HKKS (from 10^° to 40^°).

Figure 15.

Position RMS of multi-GNSS and GPS/BDS with different cut-off elevation angles for baselines CUT0-CUT1 and HKWS-HKKS.

Figure 16.

The improvement of multi-GNSS positioning accuracy with IFB calibration compared with GPS/BDS with different satellite cut-off elevation angles for baselines CUT0-CUT1 and HKWS-HKKS.

As shown in Figures 15 and 16, under open-sky environments, the number of GPS/BDS satellites is so large that the multi-GNSS positioning accuracy with GLONASS IFB calibration can be only improved by a few millimetres compared with GPS/BDS when the cut-off elevation angle is set to less than 20^°. However, under satellite-deprived environments, for example, an urban canyon with tall buildings, GPS/BDS positioning results are significantly reduced when cut-off elevation angle is increased from 20^° to 40^°, especially in the vertical direction. When calibrated GLONASS measurements participate in the solution process, the improvement of multi-GNSS positioning accuracy gradually increases as the satellite cut-off elevation angle increases compared with GPS/BDS in Figure 16. This improvement is up to 0·4 cm for zero baseline and 0·9 cm for short baseline in the vertical direction when the cut-off elevation angle rises to 40^°.