Holdover in synchronization applications
Holdover in Synchronization Applications
Introduction
“Synchronization is as important as power at the cell site.” [1]
The quote above suggests that we can think of holdover in synchronization applications as analogous to running on backup power.
Modern wireless communication systems require at least knowledge of frequency and often knowledge of phase as well in order to work correctly. Base stations need to know what time it is, and they usually get this knowledge from the outside world somehow (from a GPS Time and Frequency receiver, or from a synchronization source somewhere in the network they are connected to).
But if the connection to the reference is lost then the base station will be on its own to establish what time it is. The base station needs a way to establish accurate frequency and phase (to know what time it is) using internal (or local) resources, and that’s where the function of holdover becomes important.
The Importance of GPS Derived Timing
GPS as a source of timing is a key component in not just Synchronization in telecommunications but to critical infrastructure in general.[2] Of the 18 Critical Resource and Key infrastructure (CIKR[3])sectors, 15 use GPS derived timing to function correctly.[4]
A key application for GPS in Synchronization in telecommunications is to provide synchronization in wireless basestations. Base stations depend on timing to operate correctly, particularly for the handoff that occurs when a user moves from one cell to another.[5] In these applications holdover is used in base stations to ensure continued operation while GPS is unavailable and to reduce the costs associated with emergency repairs, since holdover allows the site to continue to function correctly until maintenance can be performed at a convenient time.[6]
Some of the most stringent requirements come from the newer generation of wireless base stations, where phase accuracy targets as low as 1μs need to be maintained for correct operation.[7] However the need for accurate timing has been an integral part of the history of wireless communication systems, and it has been suggested that the search for reliable and cost effective timing soluctions was spurred on by the need for CDMA to compete with lower cost solutions.[8]
Within the base station, besides standard functions, accurate timing and the means to maintain it through holdover is vitally important for services such as E911[9]
As mentioned above there are key applications for GPS derived timing in other critical infrastructure applications. One notable application where timing accuracy (and the means to maintain it through holdover) is of importance is in the use of Synchrophasors in the power industry to detect line faults.[10]
How GPS Derived Timing Can Fail
GPS is sensitive to jamming and interferance because the signal levels the system levels are so low[11] and can easily be swamped by other sources, that can be accidental or deliberate.[12] Also since GPS depends on line of sight signals can be disrupted by Urban canyon effects, making GPS only available to some locations at certain times of the day, for example.
A GPS outage however is not initially an issue because clocks can go into holdover[13], allowing the interference to be alleviated as much as the stability of the oscillator providing holdover will allow.[14] The more stable the oscillator, the longer the system can operate without GPS.
Defining Holdover
In Synchronization applications holdover can be defined as:
An operating condition of a clock which has lost its controlling input and is using stored
data, acquired while in locked operation, to control its output. The stored data are used to control phase and frequency variations, allowing the locked condition to be reproduced within specifications. Holdover begins when the clock output no longer reflects the influence of a connected external reference, or transition from it. Holdover terminates when the output of the clock reverts to locked mode condition.[15]
We can regard Holdover then as a measure of accuracy or error acquired by a clock when there is no controlling external reference to correct for any errors.
MIL-PRF-55310[16] defines Clock Accuracy as:
Where is the synchronization error at ; is the fractional frequency differenct between two clocks under comparison; is the error due to random noise; is at ; is the linear aging rate and is the frequency difference due to environmental effects.
Similarly ITU G.810[17] defines Time Error as:
Where is the time error; is the time error at ; is the fractional frequency error at ; is the linear fractional frequency drift rate; is the random phase deviation component and is the nominal frequency.
Implementing Holdover
Two independent clocks once synchronized will walk away from one another without limit.[18] To have them display the same time it would be necessary to re-synchronize them at regular intervals. The periods between synchronizations is referred to as Holdover and performance under Holdover relies on the quality of the reference oscillator (usually an OCXO), the PLL design and the correction mechanisms employed.[19]
The dominant factors influencing the quality of the reference oscillator are taken to be aging and temperature stability. During Holdover the clock error caused by aging and temperature instability can be corrected by control mechanisms.[20] A combination of quartz based reference oscillator (such as an OCXO) and modern correction algorithms can get good results in Holdover applications.[21]
GPS Clocks are used and in this context are often known as a GPSDO or GPS TFS.[22]
Definition of a Disciplined Oscillator[23]
Amongst the building blocks of a GPS Time and Frequency solution the oscillator is a key component[24]
Usually built around an Oven Controlled Crystal Oscillator (OCXO).
How a GPSDO works[25]
GPS clock block diagram[26]
The holdover capability is provided by either by a free running local oscillator, or a local oscillator that is steered with software that retains knowledge of its past performance.[27]
An addition of a Microprocessor can improve temperature stability and aging[28]
Aging can be effectively compensated for [29]
Basic aim of a control mechanism is to improve the stability of a clock or oscillator while minimizing the number of times it needs calibration [30]
In Holdover the learned behaviour of the OCXO is used to anticipate and correct for future behavior [31]
Holdover problem solved by predicting current errors from past history.[32] Prediction allows the system to remain stable in holdover.[33] All sort of choices for algorithms and techniques to do this correction extrapolation, interpolation, predictive filters, including the Kalman filters. [34]
Kalman filters are used to generate correction signals [35]
Designers have found that a high quality quartz oscillator matched with a Kalman filter algorithm seems to be able to provide the best compromise between quality and reliability versus cost.[36]
Once the barriers of aging and environmental effects are removed the only theoretical limitation to holdover performance in such a GPSO is irregularity or noise in the drift rate, which we detect using a metric like Allan deviation.[37]
Allan variance can measure instabilities
Time deviation can measure instabilities
Stability definitions have been around for a long time [38]
Random Walk in an oscillator mostly from outside[39]
Complexity in trying to implement has resulted in tailor made Holdover solutions in the market[40]
References
- ^ http://www.juniper.net/us/en/local/pdf/whitepapers/2000400-en.pdf
- ^ http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA503921
- ^ http://training.fema.gov/EMIWeb/IS/IS860a/CIKR/sectorMenu.htm
- ^ http://www.swpc.noaa.gov/sww/SWW_2011_Presentations/Wed_830/GPS-PNTTimingStudy-SpaceWeather4-27.pptx
- ^ http://www.gmat.unsw.edu.au/snap/publications/khan&dempster2007b.pdf
- ^ http://www.eetimes.com/design/communications-design/4213947/Understanding-the-concepts-of-synchronization-and-holdover
- ^ http://www.telecom-sync.com/pdf/2008/Day1/WCDMA_and_LTE_Synchronisation_Aspects_(Stefano_Rufini,_Ericsson).pdf
- ^ http://www.4timing.com/SyncGPS.pdf
- ^ http://www.eetimes.com/design/communications-design/4213947/Understanding-the-concepts-of-synchronization-and-holdover
- ^ http://tf.nist.gov/general/pdf/2193.pdf
- ^ http://tf.nist.gov/sim/2010_Seminar/SIM_2010_GPS_Lombardi.ppt
- ^ http://www.pnt.gov/advisory/recommendations/2010-11-jammingwhitepaper.pdf
- ^ http://www.syncuniversity.org/drsync/q45.php
- ^ http://www.gmat.unsw.edu.au/snap/publications/khan&dempster2007b.pdf
- ^ http://www.etsi.org/deliver/etsi_i_ets/300400_300499/30046201/01_60/ets_30046201e01p.pdf
- ^ http://standards.gsfc.nasa.gov/reviews/mil/mil-prf-55310d/mil-prf-55310d.pdf
- ^ http://www.itu.int/rec/T-REC-G.810-199608-I
- ^ http://tf.nist.gov/general/pdf/988.pdf
- ^ http://www.analog.com/static/imported-files/application_notes/AN-1002.pdf
- ^ http://kunz-pc.sce.carleton.ca/thesis/CrystalOscillators.pdf
- ^ http://tf.nist.gov/general/pdf/2297.pdf
- ^ http://www.trak.com/Files/News/GPSTime&FrequencySystems.pdf
- ^ http://tf.nist.gov/general/enc-d.htm
- ^ http://www.swpc.noaa.gov/sww/SWW_2011_Presentations/Wed_830/GPS-PNTTimingStudy-SpaceWeather4-27.pptx
- ^ http://tf.nist.gov/sim/2010_Seminar/SIM_2010_GPS_Lombardi.ppt
- ^ http://www.4timing.com/SyncGPS.pdf
- ^ http://tf.nist.gov/general/pdf/2297.pdf
- ^ http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4622980
- ^ http://www.gmat.unsw.edu.au/snap/publications/tappero_etal2007c.pdf
- ^ http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=199433
- ^ http://www.analog.com/static/imported-files/application_notes/AN-1002.pdf
- ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
- ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
- ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
- ^ http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=1418510
- ^ http://www.trimble.com/timing/cdma.aspx
- ^ http://www.leapsecond.com/pages/adev/adev-why.htm
- ^ http://tf.nist.gov/general/pdf/868.pdf
- ^ http://tf.nist.gov/general/enc-q.htm
- ^ http://www.vectron.com/products/modules/MD-023.pdf