Abstract
Here we test the capability of the Broadcast Ephemeris Message, in both its GPS-like (Keplerian ellipse with secular and periodic perturbations) and Glonass-like (numerical integration of a 9D state vector) formats, to reproduce a corresponding precise ephemeris. We start from a daily Rinex 3.04 navigation file for multiple GNSS and the corresponding SP3 precise orbits computed by CNES (Centre National d’Etudes Spatiales) for GPS, Glonass, Galileo and CODE (Center for Orbit Determination in Europe) for Beidou, and compute broadcast ECEF coordinates and clocks. The pre-fit discrepancies are converted by least squares to corrections to the broadcast ephemeris parameters in two-hour consecutive arcs (for GPS, Galileo and Beidou) and to a set of seven Helmert parameters for the entire day, to align in origin, orientation and scale to the common GNSS IGS14 Reference Frame. The test cases suggest that the Broadcast Ephemeris Message, complemented with Reference Frame information, can reproduce the precise ephemeris and clocks with centimetric accuracy for intervals at least equal to the respective validity times, typically 2 h. The broadcast ephemeris of Glonass consists of three initial positions and velocities at epoch, three constant Lunisolar accelerations for the satellite position, and of three polynomial coefficients for the satellite clock. The 9D vector of state is numerically integrated to generate position and velocity data within the validity time (0.5 h) of the message. To test the capability of this model to reproduce the corresponding values of a precise ephemeris, the 9D vector of state and clock polynomials are adjusted until the rms (root mean squared spread) of the post-fit residuals relative to a precise orbit (CNES’s in our case) is minimum. We show in one example (one satellite for one day) that the Glonass type of message can reproduce a precise ephemeris and clock with a rms spread of 0.025 m over one-hour arcs. Volume computations on one month of data with all available satellites confirm the test results. For GPS, Glonass, Galileo and Beidou, the best fitting clock values predicted by our second order polynomials, based on a 15 min sampling, are shown to fit the corresponding high rate clocks (30 s sampling) of MGEX with zero bias and a rms spread of 0.062 ns (GPS G01), 0.023 ns (Galileo E01), 0.43 ns (Glonass R01), 0.086 ns (Beidou C07) and 0.086 ns (Beidou C12). Modifications to the GPS-like message structure and Glonass algorithm are proposed to increase the validity time by including the effect of the 3rd zonal harmonic of the Earth’s gravity field. The potential of the RTCM messages for broadcasting the improved navigation message is reviewed.
Highlights
Is the limited accuracy of the broadcast ephemeris caused by inherent limitations of the model to compute the spacecraft coordinates and clock offset, or by the model coefficients in the broadcast message being insufficiently accurate? In this paper we provide arguments based first on detailed test cases and on volume computations that the broadcast ephemeris can provide spacecraft coordinates and clock offsets as accurate as the corresponding precise ephemeris provided that the coefficients of the broadcast ephemeris are appropriately tuned
We address here C07, an example of Beidou GNSS, that is an Space Vehicle (SV) in an IGSO orbit: this is a geosynchronous orbit with an inclination comparable to that of GPS or Galileo
The SV C12 belongs to the part of the Beidou GNSS which is in Medium Earth Orbit (MEO), like GPS
Summary
Comparisons between ECEF coordinates and clock offsets computed with merged Broadcast Ephemeris files (BRDM) and SP3 values taken as reference have been the subject of several investigations. XYZT(BRDM) and XYZT(SP3), the ECEF coordinates and satellite time correction computed from the broadcast message and the precise SP3 data file, show clear systematics and discontinuities at the crossover between two contiguous ephemeris blocks. Atives, using as a priori the broadcast values of the parameters which are indexed with Toe for the following, we use this model for data referring to 2 January 2020, as an arbitrary coordinates and Toc for In thethe clock. Epoch-dependent departures from the results described here could for example be caused by a different angle between the Sun’s geocentric vector and the satellite orbital plane (beta angle), which controls the force caused by the solar radiation pressure
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
