Holdover in synchronization applications

This is an old revision of this page, as edited by Pjdm6842 (talk | contribs) at 15:29, 12 September 2011 (Introduction). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.


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 derived timing is to provide synchronization in wireless basestations and in these applications Holdover is used in base stations to ensure continued operation while GPS is unavailable and to reduce the costs associated with repairs [5]

Base stations depend on timing to operate correctly, particularly for the handoff that occurs when a user moves from one cell to another.[6]

1us for base-stations [7]

Search for reliable timing based on something other than $3k Rubidium spurred on by the need for CDMA to compete. [8]

Holdover is important for E911 for example. Most critical telecom applications require precise time and frequency and synchronization to operate properly such as VoIP, video streaming, TDM (time division multiplex) services, voice switching, mobile services, and any LBS (___location based services, with E911 being the most important).[9]

1us for synchrophasors [10]

How GPS Derived Timing Can Fail

GPS is sensitive to jamming etc because the signal levels are so low [11]

GPS outage not initially an issue because clocks can go into Holdover [12]

GPS suffers from interference which can be alleviated by a GPSDO, up to the stability of the GPSDO[13]

Defining Holdover

Synchronization

Clock Accuracy in MIL-PRF-55310[14]

Time Error Model in ITU G.810[15]

Definition of Holdover[16]

Definition of a Disciplined Oscillator[17]

Holdover Performance Aspects

Two independent clocks once synchronized will walk away from one another without limit. How fast this happens depends on the quality of the oscillator [18]

Holdover relies on the OCXO, the PLL design, and correction mechanisms[19]

Aging and temp stability are taken to be the dominant factors. During Holdover the maximum error due to the OCXO is limited by control mechanisms. [20]

Algorithms and quartz get good results[21]

Allan variance can measure instabilities

Time deviation can measure instabilities

Implementing Holdover Solutions

GPS Clocks are used and in this context are often known as a GPSDO or GPS TFS.[22]

Amongst the building blocks of a GPS Time and Frequency solution the oscillator is a key component[23]

Usually built around a GPSDO

How a GPSDO works[24]

GPS clock block diagram[25]

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.[26]

An addition of a Microprocessor can improve temperature stability and aging[27]

Aging can be effectively compensated for [28]

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 [29]

In Holdover the learned behaviour of the OCXO is used to anticipate and correct for future behavior [30]

Holdover problem solved by predicting current errors from past history.[31] Prediction allows the system to remain stable in holdover.[32] All sort of choices for algorithms and techniques to do this correction extrapolation, interpolation, predictive filters, including the Kalman filters. [33]

Kalman filters are used to generate correction signals [34]

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.[35]

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.[36]

Stability definitions have been around for a long time [37]

Random Walk in an oscillator mostly from outside[38]

Complexity in trying to implement has resulted in tailor made Holdover solutions in the market[39]

References

  1. ^ http://www.juniper.net/us/en/local/pdf/whitepapers/2000400-en.pdf
  2. ^ http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA503921
  3. ^ http://training.fema.gov/EMIWeb/IS/IS860a/CIKR/sectorMenu.htm
  4. ^ http://www.swpc.noaa.gov/sww/SWW_2011_Presentations/Wed_830/GPS-PNTTimingStudy-SpaceWeather4-27.pptx
  5. ^ http://www.eetimes.com/design/communications-design/4213947/Understanding-the-concepts-of-synchronization-and-holdover
  6. ^ http://www.gmat.unsw.edu.au/snap/publications/khan&dempster2007b.pdf
  7. ^ http://www.telecom-sync.com/pdf/2008/Day1/WCDMA_and_LTE_Synchronisation_Aspects_(Stefano_Rufini,_Ericsson).pdf
  8. ^ http://www.4timing.com/SyncGPS.pdf
  9. ^ http://www.eetimes.com/design/communications-design/4213947/Understanding-the-concepts-of-synchronization-and-holdover
  10. ^ http://tf.nist.gov/general/pdf/2193.pdf
  11. ^ tf.nist.gov/sim/2010_Seminar/SIM_2010_GPS_Lombardi.ppt
  12. ^ http://www.syncuniversity.org/drsync/q45.php
  13. ^ http://www.gmat.unsw.edu.au/snap/publications/khan&dempster2007b.pdf
  14. ^ http://standards.gsfc.nasa.gov/reviews/mil/mil-prf-55310d/mil-prf-55310d.pdf
  15. ^ http://www.itu.int/rec/T-REC-G.810-199608-I
  16. ^ http://www.etsi.org/deliver/etsi_i_ets/300400_300499/30046201/01_60/ets_30046201e01p.pdf
  17. ^ http://tf.nist.gov/general/enc-d.htm
  18. ^ http://tf.nist.gov/general/pdf/988.pdf
  19. ^ http://www.analog.com/static/imported-files/application_notes/AN-1002.pdf
  20. ^ http://kunz-pc.sce.carleton.ca/thesis/CrystalOscillators.pdf
  21. ^ http://tf.nist.gov/general/pdf/2297.pdf
  22. ^ http://www.trak.com/Files/News/GPSTime&FrequencySystems.pdf
  23. ^ http://www.swpc.noaa.gov/sww/SWW_2011_Presentations/Wed_830/GPS-PNTTimingStudy-SpaceWeather4-27.pptx
  24. ^ tf.nist.gov/sim/2010_Seminar/SIM_2010_GPS_Lombardi.ppt
  25. ^ http://www.4timing.com/SyncGPS.pdf
  26. ^ http://tf.nist.gov/general/pdf/2297.pdf
  27. ^ http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4622980
  28. ^ http://www.gmat.unsw.edu.au/snap/publications/tappero_etal2007c.pdf
  29. ^ http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=199433
  30. ^ http://www.analog.com/static/imported-files/application_notes/AN-1002.pdf
  31. ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
  32. ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
  33. ^ http://www.eftf.org/proceedings/PDFs/FPE-0031.pdf
  34. ^ http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=1418510
  35. ^ http://www.trimble.com/timing/cdma.aspx
  36. ^ http://www.leapsecond.com/pages/adev/adev-why.htm
  37. ^ http://tf.nist.gov/general/pdf/868.pdf
  38. ^ http://tf.nist.gov/general/enc-q.htm
  39. ^ http://www.vectron.com/products/modules/MD-023.pdf