Initial Assessment of BDS PPP-B2b Service: Precision of Orbit and Clock Corrections, and PPP Performance

Abstract

On 31 July 2020, the Beidou global navigation satellite system (BDS-3) was officially announced as being commissioned. In addition to offering global positioning, navigation, and timing (PNT) services, BDS-3 also provides precise point positioning (PPP) augmentation services. The satellite orbit correction, clock correction and code bias correction of BDS-3 and other global navigation satellite systems (GNSS) are broadcast by the BDS-3 geostationary earth orbit (GEO) satellites through the PPP-B2b signal. The PPP-B2b service is available for users in China and the surrounding area. In this study, an initial assessment of the PPP-B2b service is presented, with collected 3-day PPP-B2b messages. Based on broadcast ephemeris and PPP-B2b messages, the precise satellite orbits and clock offsets can be recovered. This precision is evaluated with the precise ephemeris from the GeoForschungsZentrum Potsdam (GFZ) analysis center as references. The results indicate that the accuracy of BDS-3 satellite orbits in the direction of radial, along-track, and cross-track is 0.138, 0.131, and 0.145 m, respectively, and for GPS a corresponding accuracy of 0.104, 0.160, and 0.134 m, respectively, could be obtained. The precision of clock offsets can reach a level of several centimeters for both GPS and BDS-3. Both the performance of static PPP and kinematic PPP are evaluated using the observations from four international GNSS monitoring assessment service (iGMAS) stations. Regarding static PPP, the average convergence time is 17.7 min to achieve a horizontal positioning accuracy of better than 0.3 m, and a vertical positioning accuracy of better than 0.6 m. The average positioning accuracy in the direction of east, north, and up-directions are 2.4, 1.6, and 2.3 cm. As to kinematic PPP, the average RMS values of positioning errors in the direction of east, north, and up are 8.1 cm, 3.6 cm, and 8.0 cm after full convergence.

1. Introduction

The Beidou navigation satellite system (BDS) was independently developed by China to provide positioning, navigation, and timing (PNT) services [1,2]. A three-phase strategy has been adopted in the build-up of BDS, including the Beidou demonstration navigation satellite system (BDS-1), Beidou regional navigation satellite system (BDS-2), and Beidou global navigation satellite system (BDS-3). BDS-1 and BDS-2 have been put into use in 2000 and 2012, respectively [3,4], while the construction of BDS-3 was initiated in November 2017 [5]. By the end of June 2020, the whole constellation of BDS-3 was completed, consisting of 24 medium earth orbit (MEO) satellites, 3 geostationary earth orbit (GEO) satellites, and 3 inclined geosynchronous orbit (IGSO) satellites. On 31 July 2020, the BDS-3 system was officially announced as being commissioned. BDS-3 can offer PNT, short message communication (SMC), and international search and rescue (SAR) services. Besides the above services, BDS-3 also provides a precise point positioning (PPP) service [6,7].

PPP is a crucial high-precision global navigation satellite system (GNSS) positioning technology [8,9,10]. It can provide decimeter-level or even centimeter-level positioning accuracy with a standalone GNSS receiver, by utilizing precise ephemeris products. In the past decades, PPP techniques have been widely used for applications in oceanography [11,12,13], geoscience [14,15] and meteorology [16,17,18], and precision agriculture [19], etc. The international GNSS service (IGS) has been offering real-time service (RTS) through the internet since 2013 [20,21]. By adopting RTS products, the users can realize the real-time PPP application. However, this service depends on a standing internet access. In addition to the service offered via internet communication, a satellite broadcasting service has also been released by some commercial companies with a high-cost fee, such as StarFix from Furgo [22], StarFire from NavCom [23], and RTX from Trimble [24]. Additionally, PPP augmentation services based on the basic GNSS constellation have also been developed. The Japanese Quasi-Zenith Satellite System (QZSS) provides a centimeter-level accuracy augmentation service (CLAS) for users in Japan [25,26]. The European Galileo constellation is also designed to provide a high-precision PPP service worldwide, with an enabled positioning accuracy at decimeter-level [27,28].

BDS-3 is designed to provide a PPP augmentation service, which is an important innovation for BDS [29]. The satellite orbit correction, clock correction and code bias correction of BDS-3/GPS/GLONASS/GALILEO are supposed to be broadcast by BDS-3 GEO satellites through the PPP-B2b signal. However, the PPP-B2b service only provides corrections of BDS-3 and GPS satellites at present, and the service is only available for users in and around China. According to the structure of the PPP-B2b message, the size is 486 bits for each message, including 6 bits of message type, 456 bits of message data, and 24 bits of cycle redundancy check (CRC). The duration of each message is 1 s. The message type is defined to distinguish the broadcast correction contents. To match with the correction contents of different message types, the correction data are identified with a group of issue of data (IOD), including the issue of data of space state representation (IOD SSR), issue of data of pseudo-random noise mask (IODP), issue of data of orbit and clock correction (IOD Corr), and issue of the navigation data (IODN). The message types and the corresponding contents are summarized in

Table 1. The message types and their correction contents.

Message Type	Correction Content
1	Satellite mask
2	Satellite orbit correction and user range accuracy
3	Differential code bias
4	Satellite clock correction
5	User range accuracy index
6	Clock correction and orbit correction–combination 1
7	Clock correction and orbit correction–combination 2
8–62	Reserved
63	Null

[30].

In this contribution, we carry out an initial assessment of the BDS PPP-B2b service based on the collected 3-day message data. At first, the availability of PPP-B2b messages is analyzed. Then, the precision of PPP-B2b orbit correction and clock corrections are evaluated with the final precise multi-GNSS ephemeris products obtained from the GeoForschungsZentrum Potsdam (GFZ) analysis center as references. Finally, the PPP positioning performance in both static and kinematic mode is assessed, based on the observations from 4 international GNSS monitoring assessment service (iGMAS) stations [31]. The remaining contribution is organized as follows. In Section 2, the method to recover precise orbits and clock offsets from the PPP-B2b messages is described. In addition, the strategy to evaluate the precision of PPP-B2b orbits/clock offsets, and positioning performance with the recovered PPP-B2b orbits/clock offsets, are also introduced. In Section 3, the precision of the recovered PPP-B2b orbits/clock offsets are assessed, with GFZ precise ephemeris as reference. At the same time, the positioning performance is analyzed both in static and kinematic experiments. Finally, several conclusions are drawn in the last section.

2. Methodology

In this section, firstly, the method to calculate precise orbits and clock offsets by using PPP-B2b corrections is presented. Then, the method to evaluate the precision of PPP-B2b orbits and clock offsets is discussed. Finally, the PPP positioning model, based on the recovered PPP-B2b orbits and clock offsets, is described.

2.1. Recovery of Precise Orbits and Clock Offsets with PPP-B2b Corrections

The PPP-B2b orbit correction message contains the orbit correction parameters ($\delta O_{radial}, \delta O_{along}, \delta O_{cross}$) in the radial, along-track, and cross-track directions [30], while the satellite positions computed with broadcast ephemeris are given in the “Earth-center Earth-fixed” (ECEF) frame. Hence, the orbit corrections should be transformed to the ECEF frame. This transformation can be expressed as:

$$\left[\begin{array}{c}\delta O_x\\ \delta O_y\\ \delta O_z\end{array}\right]=\left[\begin{array}{ccc}{\mathit{e}}_{radial}& {\mathit{e}}_{along}& {\mathit{e}}_{cross}\end{array}\right]·\left[\begin{array}{c}\delta O_{radial}\\ \delta O_{along}\\ \delta O_{cross}\end{array}\right]$$

(1)

where ${\left[\begin{array}{ccc}\delta O_x& \delta O_y& \delta O_z\end{array}\right]}^T$ represents the orbit correction vector in the ECEF frame, and:

$$\{\begin{array}{c}{\mathit{e}}_{radial}=\frac{\mathit{r}}{\left|\mathit{r}\right|}\\ {\mathit{e}}_{cross}=\frac{\mathit{r}\times \dot{\mathit{r}}}{\left|\mathit{r}\times \dot{\mathit{r}}\right|}\\ {\mathit{e}}_{along}={\mathit{e}}_{cross}\times {\mathit{e}}_{radial}\end{array}$$

$\mathit{r}$ denotes the satellite position vector and $\dot{\mathit{r}}$ stands for the velocity vector; both are computed with broadcast ephemeris. By applying the satellite orbit correction to broadcast satellite positions, the precise satellite positions can be calculated as follows:

$${\left[\begin{array}{c}X\\ Y\\ Z\end{array}\right]}_{prec,B2b}={\left[\begin{array}{c}X\\ Y\\ Z\end{array}\right]}_{brdc}-\left[\begin{array}{c}\delta O_x\\ \delta O_y\\ \delta O_z\end{array}\right]$$

(2)

where ${\left[\begin{array}{ccc}X& Y& Z\end{array}\right]}_{prec,B2b}^T$ denotes the precise satellite position vector after applying PPP-B2b orbit corrections to the broadcast orbits; and ${\left[\begin{array}{ccc}X& Y& Z\end{array}\right]}_{brdc}^T$ represents the satellite position vector calculated with the broadcast ephemeris. It should be noted that IODN in the PPP-B2b message must match with the corresponding field of broadcast ephemeris in recovering a precise orbit.

The PPP-B2b clock correction message contains the correction parameter relative to the clock offset of broadcast ephemeris. The corrected precise satellite clock offset is given by:

$$d{t}_{prec, B2b}^{sat}=d{t}_{brdc}^{sat}-\frac{C_0}{c}$$

(3)

where $d{t}_{brdc}^{sat}$ is the satellite clock offset derived from the broadcast ephemeris; $d{t}_{prec,B2b}^{sat}$ denotes the precise PPP-B2b clock offset; $C_0$ is the PPP-B2b clock correction parameter; and $c$ is the velocity of light.

2.2. Assessment of the Recovered PPP-B2b Orbits and Clock Offsets

The precise orbits recovered with PPP-B2b messages are referred to the antenna phase center (APC), while the IGS precise products give the center-of-mass (CoM) of satellites [32]. Therefore, the satellite APC positions need to be converted to the satellite CoM positions by applying phase center offset (PCO) corrections [33]. Now the orbit differences can be computed as:

$$\left[\begin{array}{c}∆X\\ ∆Y\\ ∆Z\end{array}\right]=\left({\left[\begin{array}{c}X\\ Y\\ Z\end{array}\right]}_{prec,B2b}+\mathit{A}·d{\mathit{r}}_{PCO}\right)-{\left[\begin{array}{c}X\\ Y\\ Z\end{array}\right]}_{prec,GFZ}$$

(4)

where ${\left[\begin{array}{ccc}∆X& ∆Y& ∆Z\end{array}\right]}^T$ stands for the orbit error vector in ECEF Cartesian coordinates; $\mathit{A}$ denotes the satellite attitude matrix; and $d{\mathit{r}}_{PCO}$ represents the PCO correction vector for the satellite. ${\left[\begin{array}{ccc}X& Y& Z\end{array}\right]}_{prec,GFZ}^T$ denotes the precise position vector, calculated with GFZ final products.

The calculated orbit errors can be transformed from ECEF Cartesian coordinates to the satellite radial, along-track and cross-track directions:

$$\left[\begin{array}{c}∆O_{radial}\\ ∆O_{along}\\ ∆O_{cross}\end{array}\right]=\left[\begin{array}{ccc}{\mathit{e}}_{radial}& {\mathit{e}}_{along}& {\mathit{e}}_{cross}\end{array}\right]·\left[\begin{array}{c}∆X\\ ∆Y\\ ∆Z\end{array}\right]$$

(5)

where ${\left[\begin{array}{ccc}∆O_{radial}& ∆O_{along}& ∆O_{cross}\end{array}\right]}^T$ is the orbit error vector in the satellite orbital frame.

The BDS-3 PPP-B2b service adopts the Beidou coordinate system (BDCS) as a reference frame [34], while the precise products from IGS are referred to the IGS14 frame [35]. In order to eliminate the difference between these two reference frames mentioned above, a Helmert transformation should be applied.

In contrast to orbits, two different types of clock offset products cannot be compared directly. This is due to differences in hardware delays and GNSS-specific timescales. The hardware delay is caused by different tracking modes. To realize the synchronous processing at different tracking modes, a corresponding differential code bias (DCB) correction needs to be applied. The correction algorithm formula is shown below [30]:

$${\tilde{l}}_{sig}=l_{sig}-DC{B}_{sig}$$

(6)

where ${\tilde{l}}_{sig}$ is the value of $sig$ signal; $l_{sig}$ represents the observed clock offset; and $DC{B}_{sig}$ denotes the related DCB value.

After the application of DCBs, the differences between the GNSS-specific time-scales must also be eliminated [36]. Typically, a double-difference method is used to remove this bias [37]. In the double-difference method, a reference satellite clock is chosen from the recovered PPP-B2b precise clock offsets, and the single-difference between the reference clock and other satellite clocks can be formed. The same single-differences can also be obtained by using IGS precise clock offsets. Then, the corresponding double-difference values can be formed with the same single-difference pair. The double-difference clock offset can be expressed as:

$$\nabla ∆d{t}_{B2b,GFZ}^{sat}=d{t}_{prec,B2b}^{sat}-d{t}_{prec,B2b}^{refsat}-\left(d{t}_{prec,GFZ}^{sat}-d{t}_{prec,GFZ}^{refsat}\right)$$

(7)

where $\nabla ∆$ is a double-difference (DD) operator.

2.3. PPP Positioning with the Recovered PPP-B2b Orbits and Clocks

The GNSS code and phase observations at the $i$th frequency read as [38,39]:

$$\{\begin{array}{c}{P}_i=\rho +c·\delta t_r-c·\delta t^s+T+\frac{f_1^2}{f_i^2}·I_1+B_{r,i}-B_i^s+{\epsilon }_{P_i}\\ L_i=\rho +c·\delta t_r-c·\delta t^s+T-\frac{f_1^2}{f_i^2}·I_1+{\lambda }_i\left(N_i+b_{r,i}-b_i^s\right)+{\epsilon }_{L_i}\end{array}$$

(8)

where $P_i\mathrm{and}{L}_i$ are raw code/phase observation; $\rho$ represents the receiver-to-satellite geometry distance; $c$ stands for the speed of light; $\delta t_r$ and $\delta t^s$ are clock offsets at the receiver and the satellite, respectively; $T$ stands for the tropospheric delay; $f_i$ is the frequency value; $I_1$ denotes the ionospheric delay for $L_1$; ${\lambda }_i$ is the wavelength and $N_i$ is the integer ambiguity; $B_{r,i}$ and $b_{r,i}$ represent code/phase bias at the receiver; $B_i^s$ and $b_i^s$ denote code/phase bias at the satellite; and ${\epsilon }_{P_i}$ and ${\epsilon }_{L_i}$ are code/phase unmodelled errors, including thermal noise and multipath. It is noted that existing models should be applied to correct the relativistic effect, Sagnac effect, Shapiro time delay [40], phase windup effect [41] and site displacements [42].

Usually, the ionospheric-free combination is adopted by PPP to eliminate the first-order ionospheric delay. The dual-frequency code/phase ionospheric-free combinations can be expressed as:

$$\left\{\begin{array}{c}{P}_{IF}=\alpha P_1+\left(1-\alpha \right)P_2=\rho +c·\delta t_r-c·\delta t^s+T+{\epsilon }_{P_{IF}}\\ L_{IF}=\alpha L_1+\left(1-\alpha \right)L_2=\rho +c·\delta t_r-c·\delta t^s+T+{\lambda }_{IF}·N_{IF}+{\epsilon }_{L_{IF}}\end{array}\right.$$

(9)

where $\alpha =f_1^2/\left(f_1^2-f_2^2\right)$; ${\lambda }_{IF}{N}_{IF}=\alpha {\lambda }_1\left(N_1+b_{r,1}-b_1^s\right)+\left(1-\alpha \right){\lambda }_2\left(N_2+b_{r,2}-b_2^s\right)$; ${\epsilon }_{P_{IF}}=\alpha {\epsilon }_{P_1}+\left(1-\alpha \right){\epsilon }_{P_2}$ and ${\epsilon }_{L_{IF}}=\alpha {\epsilon }_{L_1}+\left(1-\alpha \right){\epsilon }_{L_2}$. It is well known that the tropospheric delay is composed of dry and wet components. The Saastamoinen model can be used to correct for the dry tropospheric delay, while the wet tropospheric delay is expressed as the product of a mapping function $M_W$ and a zenith wet delay $zwd$, and the zenith wet delay must be estimated due to its volatility. By applying PPP-B2b orbits and clock offsets, Equation (9) can be linearized as:

$$\left\{\begin{array}{c}{p}_{IF}=-\mathit{e}·\mathit{x}+c·\delta t_r+M_W·zwd+{\epsilon }_{P_{IF}}\\ l_{IF}=-\mathit{e}·\mathit{x}+c·\delta t_r+M_W·zwd+{\lambda }_{IF}·N_{IF}+{\epsilon }_{L_{IF}}\end{array}\right.$$

(10)

where $\mathit{e}$ denotes the unit vector in the receiver-to-satellite direction, and $\mathit{x}$ is the receiver position increment. As we can see from this equation, the unknown parameters only remain the receiver position increment vector $\mathit{x}$, the receiver clock offset $\delta t_r$, the zenith wet delay $zwd$ and the ionosphere-free ambiguity ${\lambda }_{IF}{N}_{IF}$. By adopting a Kalman filter scheme, the unknown parameters can be exactly estimated.

3. Experiments, Results and Discussion

To evaluate the precision of orbit and clock corrections and PPP performance, PPP-B2b messages over a 3-day period were collected from 5 October 2020 to 7 October 2020. The collected PPP-B2b messages were broadcast from C59 and C60. The PPP-B2b message types, as well as the corresponding sample rates and nominal validity time, over the selected 3-day period are listed in

Table 2. The PPP-B2b message information.

Message Type	Sample Rate (s)	Nominal Validity (s)
1	48	--
2	48	96
3	48	86,400
4	6	12
63	--	--

. There is only one message broadcast per second. Hence the total number of PPP-b2b messages is expected to be 86,400 in one day for each GEO satellite. We counted the number of received messages for each message type. The percentage of different message types is presented in Figure 1. There were just 3 epochs of PPP-B2b messages missing, and only PPP-B2b corrections of GPS and BDS-3 satellites were broadcast during the selected period.

Two sets of experiments were carried out to assess the BDS PPP-B2b service. Firstly, the precision of PPP-B2b orbit and clock corrections was evaluated by using precise products from GFZ (GBM) as references. Secondly, the PPP tests, including static mode and kinematic mode, were conducted to assess positioning performance.

3.1. Assessment Results of PPP-B2b Orbit/Clock Corrections

The availability of BDS-3/GPS satellites’ PPP-B2b orbit and clock offset corrections are depicted in Figure 2. BDS PPP-B2b service contains 29 GPS satellites and 27 BDS-3 satellites during the period from 5 October 2020 to 7 October 2020.

GBM precise orbit/clock products were downloaded from ftp://ftp.gfz-potsdam.de/GNSS/products/mgex/on 15 December 2020 and used as references. Up to October 2020, GBM precise products include BDS-3 satellites of C19-C30, C32-C46, C60. The orbit and clock accuracy for BDS-3 MEOs could reach centimeter-level, and that for BDS-3 GEOs and IGSOs is at decimeter-level [43]. Given that the accuracy of GBM orbits/clocks for BDS-3 GEOs and IGSOs is at decimeter-level, we excluded BDS-3 GEOs and IGSOs from the assessment. For GPS satellites, the GBM products exhibit an orbit/clock accuracy at 2–3 cm [44].

Firstly, we recovered the PPP-B2b precise orbits and clock offsets at a 30-s sampling rate by using PPP-B2b messages and broadcast ephemeris data. At the same time, the GBM precise ephemeris were interpolated to the same sample according to the algorithm described in [45]. The satellite PCOs were corrected according to Equation (4). Considering that there was only a three-day data arc, the Helmert transformation parameters, obtained from the China satellite navigation office (CSNO) [30], were directly adopted instead of estimated. The clock differences caused by different signals were also corrected according to Equation (6). Subsequently, the orbit/clock errors were calculated as described in Section 2. The orbit errors in the direction of along-track, cross-track and radial, as well as the clock offset errors, are shown in Figure 3 and Figure 4. Most of the PPP-B2b orbit errors are within the range of ±0.5 m. The GPS satellites show larger errors in the along-track component compared to the cross-track/radial components. For BDS-3 satellites, the errors in the cross-track component seem to be larger than for the other two directions.

The root mean square (RMS) of PPP-B2b orbit errors was counted to assess the precision of PPP-B2b precise orbit corrections. Considering that a common constant of clock offset errors can be absorbed into the receiver clock offset parameter, the standard deviation (STD) of PPP-B2b precise clock offset errors was adopted to evaluate the precision of PPP-B2b clock offset corrections. Figure 5 and Figure 6 show the RMS values of PPP-B2b orbit errors, and the STD value of PPP-B2b clock offset errors over a period of 3 days.

Table 3. The average STD and RMS of BDS-3/GPS PPP-B2b orbits and clock errors (unit: cm).

	RMS-A 1	RMS-C 2	RMS-R 3	STD-CLK 4
GPS	16.0	13.4	10.4	2.7
BDS	13.1	14.5	13.8	2.2

¹ RMS-A denotes the average RMS value of orbit errors in the direction of along-track. ² RMS-C denotes the average RMS value of orbit errors in the direction of cross-track. ³ RMS-R denotes the average RMS value of orbit errors in the direction of radial. ⁴ STD-CLK stands for the average STD value of clock offset errors.

further presents the average RMS values of orbit errors in the along-track/cross-track/radial components, and the average STD values of clock offset errors. In general, the accuracy of the PPP-B2b orbits can reach decimeter level for GPS satellites and BDS-3 MEOs. The accuracy of the PPP-B2b clock offsets is better than 3.0 cm.

3.2. PPP Tests

To investigate the positioning performance with the PPP-B2b service, PPP tests in static and kinematic mode were carried out. For comparison, the static and kinematic PPP solutions were also obtained by using GBM products. We collected BDS-3/GPS observations from 4 iGMAS stations. The geographical distribution of the 4 selected iGMAS stations, located between 20°N–40°N and 100°E–130°E, is shown in Figure 7. The daily observation files were split into 4-h sessions, and the PPP processing was restarted every 4 h. Once the data outage was larger than 1 min, the corresponding 4-h session would not be processed.

Table 4. Strategies of PPP processing.

Item	Models/Strategies
GNSS System	GPS and BDS-3
Signal selection	GPS: L1/L2 and BDS-3: B1C/B2a
Observables	Dual-frequency code/phase ionosphere-free combinations
Sampling rate	30 s
Cutoff elevation	10°
Observable noise	Raw code: 0.5 m in zenith direction Raw phase: 0.005 m in zenith direction
Weight method	Elevation dependent weight [38]
Phase windup	Corrected [41]
Relativistic effect	Corrected [40]
Sagnac effect	Corrected [40]
Shapiro time delay	Corrected [40]
Tidal effect	Solid tide, ocean loading and pole tide were corrected according to IERS Conventions 2010 [42]
Troposphere	Zenith dry delay: corrected with Saastamoinen model, while meteorological parameters were calculated by applying global pressure and temperature (GPT) model [47] Zenith wet delay: estimated for each epoch as a random walk noise with a process noise of 2 cm/sqrt(h) Mapping function: global mapping function (GMF) [48]
Phase Ambiguity	Estimated as a float constant for each ambiguity arc
Estimator	Kalman filter

summarized our PPP processing strategies. Notice that kinematic PPP was simulated by estimating positions independently epoch-by-epoch, which is similar to the estimation of the position in the kinematic PPP mode. The coordinates obtained from the iGMAS weekly SINEX solution file were used as references [46].

3.2.1. Static Mode

The RMS values of positioning errors of the final 10 min were counted to assess the positioning accuracy in the static mode. Figure 8, Figure 9, Figure 10 and Figure 11 show the PPP positioning accuracy at the stations of BJF1, KUN1, SHA1, and WUH1. Among these figures, several sessions‘ positioning accuracy are not provided because of the GNSS data outage. In general, the static PPP performance with the PPP-B2b service is slightly worse than that with GBM products. The positioning accuracy with the PPP-B2b service in the north component is better than those in the east/up components. The positioning accuracy with the PPP-B2b service in the north component is better than 3.5 cm, while a positioning accuracy of better than 4.5 cm can be achieved in the north/up components. The positioning accuracy with the PPP-B2b service of all sessions is at the centimeter level. The positioning accuracy with GBM products is better than 3.5 cm in the east/north/up components. For all four stations, the average positioning accuracy with PPP-B2b service varies by 2.5–3.1 cm in the horizontal component, and 1.9–2.5 cm in the vertical component. While the average positioning accuracy with GBM products varies by 1.5–1.8 cm in the horizontal, and 1.1–1.6 cm in the vertical direction. The detailed statistics are presented in

Table 5. The average positioning accuracy at the four stations (unit: cm).

	PPP-B2b Service					GBM Products
	E 1	N 2	U 3	H 4	3D 5	E 1	N 2	U 3	H 4	3D 5
BJF1	2.2	1.8	2.4	2.8	3.7	1.1	1.4	1.3	1.8	2.2
KUN1	2.1	1.3	2.2	2.5	3.3	1.1	1.0	1.1	1.5	1.9
SHA1	2.7	1.4	2.5	3.0	3.9	1.2	1.1	1.6	1.6	2.3
WUH1	2.4	1.8	1.9	3.0	3.6	1.0	1.4	1.5	1.7	2.3

¹ E/² N/³ U Stands for the directions of east, north and up; ⁴ H/⁵ 3D denote horizontal and 3-dimensional.

.

Convergence time (CT) is also a crucial factor to assess the static PPP performance. As described in the official document [7], the positioning performance with PPP-B2b service is better than 30 cm in the horizontal component and better than 60 cm in the vertical component with a confidence level of 95%. Hence, the convergence time was defined to achieve the horizontal positioning accuracy better than 30 cm, the vertical positioning accuracy better than 60 cm, and keep such a positioning accuracy at least 5 min in this paper. The convergence time of static PPP at each iGMAS station is shown in Figure 12. As visible, the convergence time with PPP-B2b service is 18.0/17.0/18.8/16.9 min at 4 iGMAS stations. When GBM products are used, the convergence time is 8.2/11.8/10.6/9.8 min, respectively.

3.2.2. Kinematic Mode

The kinematic PPP positioning errors at the stations of BJF1, KUN1, SHA1 and WUH1 are presented in Figure 13, Figure 14, Figure 15 and Figure 16, respectively. Similarly, there is also a lack of some sessions‘ positioning results, due to GNSS data outage. One can see that the positioning accuracy with the PPP-B2b service in the east/north/up components is all within one decimeter after convergence.

The RMS values of positioning errors were counted for 4 iGMAS stations, and the results are presented in

Table 6. The positioning accuracy of kinematic PPP at all four stations (unit: cm).

	PPP-B2b Service					GBM Products
	E	N	U	H	3D	E	N	U	H	3D
BJF1	8.0	3.8	8.6	8.8	12.3	3.3	2.5	3.5	4.1	5.4
KUN1	9.2	3.1	8.3	9.6	12.7	3.9	1.5	4.3	4.2	6.0
SHA1	7.1	3.6	7.5	8.0	10.9	3.5	2.4	4.5	4.2	6.2
WUH1	8.1	4.0	7.5	9.0	11.3	3.4	2.2	3.0	4.1	5.0

. It should be noted that the positioning errors of the first 30 min at each session have been removed, in order to exclude the positioning results before full convergence. For both types of products, the positioning accuracy in the north component is apparently better than those in the other two components. In term of PPP performance with the PPP-B2b service, the horizontal positioning accuracy ranges from 8.0 to 9.6 cm, with an average value of 8.9 cm, and the 3-dimensional positioning accuracy is all within 13 cm, with an average value of 11.8 cm. When using the GBM products, the average horizontal positioning accuracy can reach 4.2 cm, and the average 3-dimensional positioning accuracy is 5.7 cm.

4. Conclusions

At present, the PPP-B2b service is available for users in and around China. In this study, an initial assessment of the BDS PPP-B2b service was carried out based on the collected 3-day data. Firstly, the availability of PPP-B2b messages was analyzed. The PPP-B2b service only provided the satellite orbit correction, clock correction, and differential code bias of BDS-3/GPS. The availability of PPP-B2b messages was near to 100%; the missing number of PPP-B2b messages was only 3 epochs during the 3-day period. With GBM precise ephemeris products as references, the precision of PPP-B2b orbit and clock corrections were evaluated. The accuracy of PPP-B2b orbits in the direction of radial along-track and cross-track were 0.104/0.169/0.134 m for GPS. The corresponding accuracy obtained for BDS-3 MEOs was 0.138/0.131/0.145 m. Generally, the standard deviation of B2b clock offsets was better than 3.0 cm.

PPP tests, both in static and kinematic mode, were also conducted to further evaluate the positioning performance of the PPP-B2b service. Regarding static PPP, the convergence time was about 17.7 min, and the average positioning accuracy in the direction of east, north and up were 2.4/1.6/2.3 cm, respectively. As for simulated kinematic PPP, the average positioning accuracies were 8.1/3.6/8.0 cm in the east/north/up components, respectively. The results of PPP tests demonstrated that the positioning accuracy could reach centimeter-level for static applications, and decimeter-level positioning accuracy could be achieved for kinematic applications.