Syncing Time Critical Processes Using NTP



Posted: Wednesday, May 07, 2008

by
TimeTools

Network Time Protocol, or NTP as it is most commonly known, provides a mechanism to synchronise the time of computer devices and other network infrastructure. The protocol was originally developed for the Linux operating system by Dr D Mills of the University of Delaware. For more than two decades, NTP has provided time synchronisation of critical devices on the Internet making it one of the oldest protocols still in continuous operation. This article provides a brief overview of NTP and some of the technical phrases used in computer timing.

NTP was originally developed to solve the requirement of synchronisation of critical time processes across the Internet. The NTP protocol is primarily intended for operation on LINUX servers; however, it has recently been ported to other operating systems such as Microsoft Windows. LINUX is still however the primary platform associated with the Network Time Protocol.

NTP is based upon the User Data-gram Protocol (UDP) which is in-turn reliant on the TCP/IP protocol. NTP messages are communicated using UDP port 23, which is reserved solely for the use of NTP traffic. The protocol basically consists of a number of fields, which specify: clock-offset, round-trip delay and dispersion relative to a precise time source. The information stored in each NTP packet allow a network time client to accurately synchronise time with a NTP server.

NTP is a structured protocol that operates in a hierarchical manner. At the top of the tree, a primary time reference is known as a stratum 1 time server. Servers that synchronise to a stratum 1 server are known as stratum 2 servers and so on down each level of the hierarchy. As the stratum increases, so generally precision decreases.

Over a number of years NTP has been enhanced to operate with a plethora of precision hardware clock devices, or reference clocks. NTP hardware reference clocks synchronise to precise external timing resources such as GPS, WWVB, MSF and DCF-77 timing standards. Many hardware reference clocks also provide backup precision timing outputs such as TCXO, OCXO and rubidium references to maintain accurate time in the event of signal loss.

A spin-off of the NTP protocol is SNTP or Simple Network Time Protocol, which is basically as the name implies, a simplified version of NTP. SNTP is generally used in small low-powered computing devices such as micro-controllers. It allows low-powered devices the ability to synchronise time to NTP servers over a network.

To summarise, NTP is a long-standing and widely used protocol for synchronising time between time critical processes. NTP has a linear heirarchical structure that can provide a timing resource for large numbers of clients. For applications that require critical timing, NTP provides a de-facto standard solution.

--------

D. Evans is an experienced technical author in the field of NTP and precision timing references. David is the auther of many white-papers and articles detailing the installation of computer network timing equipment. Please click here, if you would like more information on NTP Server systems.
This Article has been viewed 137 times. (Not updated in real-time.)
No comments yet.
We want your comments! If you can read this, you don't have javascript enabled, so you can't use this comment system. Please enable javascript.