Holdover in synchronization applications

From HandWiki
Revision as of 15:10, 6 February 2024 by Carolyn (talk | contribs) (fixing)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Two independent clocks, once synchronized, will walk away from one another without limit.[1] To have them display the same time it would be necessary to re-synchronize them at regular intervals. The period between synchronizations is referred to as holdover and performance under holdover relies on the quality of the reference oscillator, the PLL design, and the correction mechanisms employed.[2]

Importance

The quote above suggests that one 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

A key application for GPS 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.[4] 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.[5]

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.[6] However the need for accurate timing has been an integral part of the history of wireless communication systems as well as wireline,[7] and it has been suggested that the search for reliable and cost effective timing solutions 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[5]

GPS as a source of timing is a key component in not just Synchronization in telecommunications but to critical infrastructure in general.[9] Of the 18 Critical Resource and Key infrastructure (CIKR[10])sectors, 15 use GPS derived timing to function correctly.[11] One notable application where highly accurate 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.[12]

How GPS-derived timing can fail

GPS is sensitive to jamming and interference because the signal levels are so low[13] and can easily be swamped by other sources, that can be accidental or deliberate.[14] Also since GPS depends on line of sight signals it 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,[15] allowing the interference to be alleviated as much as the stability of the oscillator providing holdover will allow.[4] The more stable the oscillator, the longer the system can operate without GPS.

Defining holdover

In Synchronization in telecommunications applications holdover is defined by ETSI 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.[16]

One 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[17] defines Clock Accuracy as:

[math]\displaystyle{ T(t) = T_0 + \int_0^t R(t)\,dt\ + \epsilon(t) = T_0+(R_0t + \frac{1}{2}At^2+...) + \int_0^t E_t(t)\, dt + \epsilon(t) }[/math]

Where [math]\displaystyle{ T_0 }[/math] is the synchronization error at [math]\displaystyle{ t = 0 }[/math]; [math]\displaystyle{ R(t) }[/math] is the fractional frequency difference between two clocks under comparison; [math]\displaystyle{ \epsilon(t) }[/math] is the error due to random noise; [math]\displaystyle{ R_0 }[/math] is [math]\displaystyle{ R(t) }[/math] at [math]\displaystyle{ t=0 }[/math]; [math]\displaystyle{ A }[/math] is the linear aging rate and [math]\displaystyle{ E_1(t) }[/math] is the frequency difference due to environmental effects.

Similarly ITU G.810[18] defines Time Error as:

[math]\displaystyle{ x(t) = x_0 + y_0t + \frac{D}{2}t^2 + \frac{\phi(t)}{2\pi\nu_{nom}} }[/math]

Where [math]\displaystyle{ x(t) }[/math] is the time error; [math]\displaystyle{ x_0 }[/math] is the time error at [math]\displaystyle{ t=0 }[/math]; [math]\displaystyle{ y_0 }[/math] is the fractional frequency error at [math]\displaystyle{ t=0 }[/math]; [math]\displaystyle{ D }[/math] is the linear fractional frequency drift rate; [math]\displaystyle{ \phi(t) }[/math] is the random phase deviation component and [math]\displaystyle{ \nu_{nom} }[/math] is the nominal frequency.

Implementing holdover

In applications that require synchronization (such as wireless base stations) GPS Clocks are often used and in this context are often known as a GPSDO (GPS Disciplined Oscillator) or GPS TFS (GPS Time and Frequency Source).[19]

NIST defines a Disciplined Oscillator as:

An oscillator whose output frequency is continuously steered (often through the use of a phase locked loop) to agree with an external reference. For example, a GPS disciplined oscillator (GPSDO) usually consists of a quartz or rubidium oscillator whose output frequency is continuously steered to agree with signals broadcast by the GPS satellites.[20]

In a GPSDO a GPS or GNSS signal is used as the external reference that steers an internal oscillator.[13] In a modern GPSDO the GPS processing and steering function are both implemented in a Microprocessor allowing a direct comparison between the GPS reference signal and the oscillator output.[8]

A Modern GPSDO

Amongst the building blocks of a GPS Time and Frequency solution the oscillator is a key component[11] and typically they are built around an Oven Controlled Crystal Oscillator (OCXO) or a Rubidium based clock. The dominant factors influencing the quality of the reference oscillator are taken to be aging and temperature stability. However, depending upon the construction of the oscillator, barometric pressure and relative humidity can have at least as strong an influence on the stability of the quartz oscillator.[citation needed] What is often referred to as "random walk" instability is actually a deterministic effect of environmental parameters. These can be measured and modeled to vastly improve the performance of quartz oscillators. An addition of a Microprocessor to the reference oscillator can improve temperature stability and aging performance[21] During Holdover any remaining clock error caused by aging and temperature instability can be corrected by control mechanisms.[22] A combination of quartz based reference oscillator (such as an OCXO) and modern correction algorithms can get good results in Holdover applications.[23]

The holdover capability then is provided either by a free running local oscillator, or a local oscillator that is steered with software that retains knowledge of its past performance.[23] The earliest documentation of such an effort comes from the then National Bureau of Standards in 1968 [Allan, Fey, Machlan and Barnes, "An Ultra Precise Time Synchronization System Designed By Computer Simulation", Frequency], where an analog computer consisting of ball-disk integrators implemented a third order control loop to correct for the frequency ageing of an oscillator. The first microprocessor implementation of this concept occurred in 1983 [Bourke, Penrod, "An Analysis of a Microprocessor Controlled Disciplined Frequency Standard", Frequency Control Symposium] where Loran-C broadcasts were used to discipline very high quality quartz oscillators as a caesium replacement in telecommunications wireline network synchronization. The basic aim of a steering mechanism is to improve the stability of a clock or oscillator while minimizing the number of times it needs calibration.[1] In Holdover the learned behaviour of the OCXO is used to anticipate and correct for future behavior.[2] Effective aging and temperature compensation can be provided by such a mechanism[24] and the system designer is faced with a range of choices for algorithms and techniques to do this correction including extrapolation, interpolation and predictive filters (including Kalman filters).[25][26]

Once the barriers of aging and environmental effects are removed the only theoretical limitation to holdover performance in such a GPSDO is irregularity or noise in the drift rate, which is quantified using a metric like Allan deviation or Time deviation.[27][unreliable source?]

The complexity in trying to predict the effects on Holdover due to systematic effects like aging and temperature stability and stochastic influences like Random Walk noise has resulted in tailor-made Holdover Oscillator solutions being introduced in the market.[28]

See also

References

  1. ↑ 1.0 1.1 Smart Clock: A New Time. IEEE. 1992-12-06. http://tf.nist.gov/general/pdf/988.pdf. Retrieved 2012-10-21. 
  2. ↑ 2.0 2.1 "AN-1002 (Rev. 0)". http://www.analog.com/static/imported-files/application_notes/AN-1002.pdf. 
  3. ↑ Synchronization Deployment Considerations for IP RAN Backhaul Operators. Juniper Networks. 2011. http://www.juniper.net/us/en/local/pdf/whitepapers/2000400-en.pdf. Retrieved 2012-10-21. 
  4. ↑ 4.0 4.1 Faisal A. Khan (December 2007). Impacts of GPS-Based Synchronization Degradation on Cellular Networks. IGNSS. http://www.gmat.unsw.edu.au/snap/publications/khan&dempster2007b.pdf. Retrieved 2012-10-21. 
  5. ↑ 5.0 5.1 "Understanding the concepts of synchronization and holdover". Eetimes.com. http://www.eetimes.com/design/communications-design/4213947/Understanding-the-concepts-of-synchronization-and-holdover. 
  6. ↑ "WCDMA and LTE Synchronization Aspects". http://www.telecom-sync.com/pdf/2008/Day1/WCDMA_and_LTE_Synchronisation_Aspects_(Stefano_Rufini,_Ericsson).pdf. 
  7. ↑ "Clocks for the Synchronized Network". http://telecom-info.telcordia.com/site-cgi/ido/docs.cgi?ID=SEARCH&DOCUMENT=GR-1244&. 
  8. ↑ 8.0 8.1 Peter Kuykendall; Dr. Peter V. W. Loomis. In Sync with GPS: GPS Clocks for the Wireless Infrastructure. http://www.4timing.com/SyncGPS.pdf. Retrieved 2012-10-21. 
  9. ↑ Dr. James Carroll; Mr. Kirk Montgomery. Global Positioning System Timing Criticality Assessment - Preliminary Performance Results. https://apps.dtic.mil/sti/pdfs/ADA503921.pdf. Retrieved 2012-10-21. 
  10. ↑ "CIKR Resource Center". http://training.fema.gov/EMIWeb/IS/IS860a/CIKR/sectorMenu.htm. 
  11. ↑ 11.0 11.1 R. James Caverly (2011-04-27). "GPS Critical Infrastructure". http://www.swpc.noaa.gov/sww/SWW_2011_Presentations/Wed_830/GPS-PNTTimingStudy-SpaceWeather4-27.pptx. 
  12. ↑ "Signal". http://tf.nist.gov/general/pdf/2193.pdf. 
  13. ↑ 13.0 13.1 "The Global Positioning System (GPS) and Satellite Time Transfer". March 2010. http://tf.nist.gov/sim/2010_Seminar/SIM_2010_GPS_Lombardi.ppt. 
  14. ↑ "GPS.gov: National Space-Based Positioning, Navigation, and Timing Advisory Board". Pnt.gov. 2012-08-21. http://www.pnt.gov/advisory/recommendations/2010-11-jammingwhitepaper.pdf. 
  15. ↑ "Sync University". Sync University. 2004-12-15. http://www.syncuniversity.org/drsync/q45.php. 
  16. ↑ "ETS 300 462-1 - Edition 01 - Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 1: Definitions and terminology for synchronization networks". http://www.etsi.org/deliver/etsi_i_ets/300400_300499/30046201/01_60/ets_30046201e01p.pdf. 
  17. ↑ "Performance specification: Oscillator, Crystal-Controlled, General Specification For". 1998. http://standards.gsfc.nasa.gov/reviews/mil/mil-prf-55310d/mil-prf-55310d.pdf. 
  18. ↑ tsbmail. "G.810 : Definitions and terminology for synchronization networks". Itu.int. http://www.itu.int/rec/T-REC-G.810-199608-I. 
  19. ↑ "GPS Time and Frequency Systems". http://www.trak.com/Files/News/GPSTime&FrequencySystems.pdf. 
  20. ↑ "Time and Frequency from A to Z". Tf.nist.gov. http://tf.nist.gov/general/enc-d.htm. 
  21. ↑ Wacker, Mike F.; Villella, A. (2008). "Improvements in OCXO performance by the use of an on-board microprocessor". 2008 IEEE International Frequency Control Symposium. Ieeexplore.ieee.org. pp. 159–164. doi:10.1109/FREQ.2008.4622980. ISBN 978-1-4244-1794-0. 
  22. ↑ Hui Zhou; Charles Nicholls; Thomas Kunz; Howard Schwartz (November 2008). Frequency Accuracy & Stability Dependencies of Crystal Oscillators. http://kunz-pc.sce.carleton.ca/thesis/CrystalOscillators.pdf. Retrieved 2012-10-21. 
  23. ↑ 23.0 23.1 Michael A. Lombardi (September 2008). The Use of GPS Disciplined Oscillators as Primary Frequency Standards for Calibration and Metrology Laboratories. NCSL International. http://tf.nist.gov/general/pdf/2297.pdf. Retrieved 2012-10-21. 
  24. ↑ Fabrizio Tappero; Andrew G. Dempster; Toshiaki Iwata (2007). Phase error reduction method for free-run QZSS clock. IEEE. http://www.gmat.unsw.edu.au/snap/publications/tappero_etal2007c.pdf. Retrieved 2012-10-21. 
  25. ↑ Proceedings[|permanent dead link|dead link}}]
  26. ↑ c.w.t. Nicholls, G.C. Carleton (2004). "Adaptive OCXO drift correction algorithm". Proceedings of the 2004 IEEE International Frequency Control Symposium and Exposition, 2004. Ieeexplore.ieee.org. pp. 509–517. doi:10.1109/FREQ.2004.1418510. ISBN 0-7803-8414-8. 
  27. ↑ Leap second
  28. ↑ "MD-023: Extended Holdover Crystal Oscillator". Vectron International. June 2011. http://www.vectron.com/products/modules/MD-023.pdf. 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Holdover_in_synchronization_applications&oldid=3361781"