G
Guest
Guest
Archived from groups: alt.cellular.verizon (More info?)
Slobby Don <reply@thru.ng> wrote:
> I was looking at one of the three atomic clocks I have at home, (two set by
> WWVB, one by internet timeserver) and noticed it was 30 seconds behind the
> time on my VZW phone that is set up to use the digital signal. The atomic
> clocks are all in agreement of course. Why is VZW shifting the time by 30
> seconds? The last time I checked it was within a second of the correct
> time. Do they reckon that the average time is more meaningful than the
> current minute? Does this aberration persist everywhere in the country? I
> am in San Diego.
The atomic clocks use the TAI time standard; civil time is based on UTC,
which is currently 32 seconds off from TAI due to leap-seconds. The GPS
system time reference does not use leap seconds, and may differ from both
UTC and TAI. So, in order to get the "correct" time, the receiving device
would need to translate from one time standard into the other. Perhaps
VZW's system doesn't do this, or doesn't do it everywhere; or perhaps it's
up to the phone, and some do it and some don't. I don't know the answer
to that, but the difference could explain the behavior you're seeing.
--
Jeremy | jeremy@exit109.com
Slobby Don <reply@thru.ng> wrote:
> I was looking at one of the three atomic clocks I have at home, (two set by
> WWVB, one by internet timeserver) and noticed it was 30 seconds behind the
> time on my VZW phone that is set up to use the digital signal. The atomic
> clocks are all in agreement of course. Why is VZW shifting the time by 30
> seconds? The last time I checked it was within a second of the correct
> time. Do they reckon that the average time is more meaningful than the
> current minute? Does this aberration persist everywhere in the country? I
> am in San Diego.
The atomic clocks use the TAI time standard; civil time is based on UTC,
which is currently 32 seconds off from TAI due to leap-seconds. The GPS
system time reference does not use leap seconds, and may differ from both
UTC and TAI. So, in order to get the "correct" time, the receiving device
would need to translate from one time standard into the other. Perhaps
VZW's system doesn't do this, or doesn't do it everywhere; or perhaps it's
up to the phone, and some do it and some don't. I don't know the answer
to that, but the difference could explain the behavior you're seeing.
--
Jeremy | jeremy@exit109.com