Large-scale GPS interruption Effect on NTP Pool

They need an oscillator to execute their basic function of positioning. Positioning is based on trilateration, i.e., they need to accurately measure the time it takes for a signal from a satellite to reach them as a measure of how far away the satellite is. To allow cost effective (and small) devices, use of low-cost oscillators is possible. To get the accuracy needed for positioning, the low cost oscillators are disciplined by the timing derived from the GNSS signal.

Yes, there is nothing to prevent a manufacturer from using higher-grade/more expensive oscillators to improve positioning accuracy/stability, and time/frequency accuracy/stability (with time being a by-product of the positioning process, see above about trilateration).

Apart from some software and other hardware features specific to timing/frequency receivers, that is what makes specialized time/frequency receivers noticeably more expensive than the “standard precision” (SPG) devices (in that manufacturer’s parlance).

Yes, because it is a timing/frequency receiver. But some sort of reference frequency is anyhow available internally, and the point here is that it is made available externally.

Standard-precision devices do not typically provide a frequency output, except programmable PPS derived from the internal reference frequency.

Yes, that is what the PPS quantization error that those devices report is all about.

Yes, because it is a dedicated timing/frequency device. That functionality can benefit from holdover functionality. It does not make sense in the context of positioning, where various other approaches to deal with, e.g., loss of signal, are used instead, e.g., dead reckoning. And it is due to those features that a dedicated timing/frequency receiver is more expensive than “standard precision” devices.

Not sure about others off the top of my head, but I believe the European Galileo system is not military, but primarily for civilian use, and it offers related capabilities for civilian use cases. And I think neither is, e.g., the Japanese QZSS system.

That is not to say that there couldn’t be military use cases, or additional functions for military use, like with GPS. But the basic setup is civilian.

For GPS, this used to be true. But Selective Availability was disabled a while ago, and recent satellites do not even support that anymore.

That does not impact however that there always was a separate feature set dedicated/limited to military use, though. And it is still operated by the military of the USA.

Sure, but with civilian systems, it is at least a political decision, rather than purely military.

Putting wrong time in a system will give problems. But GNSS can still be locked with GPS-PPS.

So it will be on time.

What is the problem?

You can not mess with PPS when time-date is known.

Military or not. I doesn’t matter.