GEOG 862
GPS and GNSS for Geospatial Professionals

GPS Time

PrintPrint
GPS Time
local 2020-09-09   14:37:04 Wednesday day 253 timezone UTC-6
UTC 2020-09-09   20:37:04 Wednesday day 253 MJD 59101.85907
GPS 2020-09-09   20:37:22   week 2122 333442 s cycle 2 week 0074 day 3
Loran 2020-09-09   20:37:31 GRI 9940 47 s until next TOC 20:37:51 UTC
TAI 2020-09-09   20:37:41 WEDNESDAY day 253 37 leap seconds
Source: LeapSecond

 

There is time-sensitive information in the NAV message in both subframe 1 and subframe 4. The information in subframe 4 helps a receiver relate two different time standards to one another. One of them is GPS Time and the other is Coordinated Universal Time (UTC).

GPS Time is the time standard of the GPS system. It is also known as GPS System Time (GPST). Coordinated Universal Time is the time standard for the world. The rates of these two standards are virtually the same. Specifically, the rate of GPS Time is kept within 1 microsecond, and usually less than 25 nanoseconds, of the rate of Coordinated Universal Time (UTC). The exact difference is in two constants, A0 and A1 in the NAV message which give the time difference and rate of system time against UTC.

The rate of UTC itself is carefully determined. It is steered by about 65 timing laboratories and hundreds of atomic clocks around the world and is remarkable in its stability. In fact, it is more stable than the rotation of the earth itself, such that UTC and the rotation gradually get out of sync with one another. Therefore, in order to keep the discrepancy between UTC and the earth’s actual motion under 0.9 seconds, corrections of 1 second, called leap seconds, are periodically introduced into UTC. In other words, the rate of UTC is consistent and stable all the time, but the numbers denoting the moment of time changes whenever a 1 second leap second is introduced.

However, leap seconds are not used in GPS Time. It is a continuous time scale. Nevertheless, there was a moment when GPS Time was identical to UTC. It was midnight, January 6, 1980. Since then, many leap seconds have been added to UTC, but none have been added to GPS Time. So, even though their rates are virtually identical, the numbers expressing a particular instant in GPS Time are different by some seconds from the numbers expressing the same instant in UTC. For example, GPS time was 16 seconds ahead of UTC on July 1, 2012 and 18 seconds ahead of UTC on September 11, 2020

Information in subframe 4 of the NAV message includes the relationship between GPS time and UTC, and it also notes future scheduled leap seconds. In this area, subframe 4 can accommodate 8 bits, 255 leap seconds, which should suffice until about 2330. The NAV message also contains information the receiver needs to come close to correlating its clock with that of the clock on the satellite. But because the time relationships in GPS are changing constantly, they can only be partially defined in these subframes. It takes more than a portion of the NAV message to define those relationships to the necessary degree of accuracy.

The Control Segment keeps track of time and uploads clock corrections to the satellites. However, the oscillators (clocks) in satellites have a tendency to drift. They're not perfect timekeepers, and they're affected by several things, moving in and out of the shadow of the Earth, gravitational changes, and so on. These effects cause the satellite's clocks to not oscillate perfectly.  Their rate can vary.  Nevertheless, the Control Segment does not constantly tweak the clocks in the satellites to keep them perfectly on GPS time. They let them wander a little bit but keep them within the limit of one millisecond of GPS Time. They find that by doing this, it keeps the clock in the satellites healthy longer. It extends their life. You will note that the first things to go on a satellite are its clocks. This is one reason that many of them have multiple oscillators.

So, the message is that the Control Segment introduces a clock correction into the Navigation Message that gives your receiver a way to correlate the drift of the oscillator(s) in the satellite with GPS time. This is one way to keep the time standard within limits.