NTP (Network Time Protocol) is the protocol used to distribute the UTC time across a network it also ensures all time is accurate and stable. However, there are many pitfalls in setting up a NTP network, here are the most common:

Using the correct time source

Attaining the most suitable time source is fundamental in setting up a NTP network. The time source is going to be distributed amongst all machines and devices on a network so it is vital that it is not only accurate but also stable and secure.

Many system administrators cut corners with a time source. Some will decide to use an Internet based time source although these are not secure as the firewall will require an opening and also many internet sources are either wholly inaccurate or too far away to afford any useful precision.

There are two highly secure methods of receiving a UTC time source. The first is to utilise the GPS network which although doesn’t transmit UTC, GPS time is based on International atomic time and is therefore easy for NTP to convert. GPS time signals is also readily a

The second method is to use the long wave radio signals broadcast by some national physical laboratories. These signals, however, are not available in every country and they have a finite range and are susceptible to interference and local topography.

A version of NTP is installed on most versions of Windows (although a stripped down version called SNTP –Simplified NTP- is in older versions) and Linux but is free to download from NTP.org.

When synchronising a a network it is preferable to use a dedicated NTP server that receives a timing source from an atomic clock either via specialist radio transmissions or the GPS network. However, many Internet time references are available, some more reliable than others, although it must be noted Internet based time sources can’t be authenticated by NTP, leaving your computer vulnerable to threats.

NTP is hierarchical and arranged into stratum. Stratum 0 is timing reference, while stratum 1 is a server connected to a stratum 0 timing source and a stratum 2 is a computer (or device) attached to a stratum 1 server.

The Basic configuration of NTP is done using the /etc/ntp.conf file you have to edit it and place the IP address of stratum 1 and stratum 2 servers. Here is an example of a basic NTP.conf file:

server xxx.yyy.zzz.aaa prefer (time server address such as time.windows.com)

server 123.123.1.0

server 122.123.1.0 stratum 3

Driftfile /etc/ntp/drift

The most basic NTP.conf file will list 2 servers, one that it wishes to synchronise too and an IP address for itself. It is good housekeeping to have more than one server for reference in case one goes down.

A server with the tag ‘prefer’ is used for a trusted source ensuring NTP will always use that server when possible. The IP address will be used in case of problems when NTP will synchonise with itself is. The drift file is where NTP builds a record of the system clock’s drift rate and automatically adjusts for it.

NTP will adjust your system time but only slowly. NTP will await at least ten packets of information before trusting the time source. To test NTP simply change your system clock by half an hour at the end of the day and the time in the morning should be correct.

The North American WWVB signal is operated by NIST - the National Institute of Standards and Technology. WWVB has high transmitter power (50,000 watts), a very efficient antenna and an extremely low frequency (60,000 Hz). For comparison, a typical AM radio station broadcasts at a frequency of 1,000,000 Hz. The combination of high power and low frequency gives the radio waves from WWVB a lot of bounce, and this single station can therefore cover the entire continental United States plus much of Canada and Central America.

The time codes are sent from WWVB using one of the simplest systems possible, and at a very low data rate of one bit per second. The 60,000 Hz signal is always transmitted, but every second it is significantly reduced in power for a period of 0.2, 0.5 or 0.8 seconds: • 0.2 seconds of reduced power means a binary zero • 0.5 seconds of reduced power is a binary one. • 0.8 seconds of reduced power is a separator. The time code is sent in BCD (Binary Coded Decimal) and indicates minutes, hours, day of the year and year, along with information about daylight savings time and leap years.

The time is transmitted using 53 bits and 7 separators, and therefore takes 60 seconds to transmit. A clock or watch can contain an extremely small and relatively simple antenna and receiver to decode the information in the signal and set the clock’s time accurately. All that you have to do is set the time zone, and the atomic clock will display the correct time.

Dedicated NTP time servers that are tuned to receive the WWVB time signal are available. These devices connect o a computer network like any other server only these receive the timing signal and distribute it to other machines on the network using NTP (Network Time Protocol).

Leap Seconds have been added nearly every year since the inception of UTC (Coordinated Universal Time) in the 1970’s. The extra second is added to ensure UTC keeps in synch with GMT (Greenwich Meantime or sometimes called UT1). GMT is the traditional 24 hour clock system where a day is defined as the rotation of the Earth which takes 86,400 seconds for a complete revolution.

Unfortunately the Earth can often be a little tardy in its spin and if the extra seconds were no added at the end of the year to compensate eventually the two systems (UTC and GMT) would drift apart. In a millennium the time difference would only be an hour but many argue to a have a time system that does no correspond to the movement of the heavens would be irrational and occupations such as farming and astronomy would be made more difficult.

However, not everybody sees it that way wit some arguing that as te entire world’s computer networks are synchronised to UTC using NTP servers then the fudging of the extra second causes untold amounts of trouble.

Now a group within the International Telecommunications Union, called has recommended abolishing the leap second. Group member Elisa Felicitas Arias, of the International Bureau of Weights and Measures in Paris, France, argues that a timescale that doesn’t need regular tweaking is essential in an increasingly interconnected world. What’s more, she says, ships and aircraft now navigate via GPS rather than the old time system. GPS runs on a version of atomic time.

Next year, member states of the ITU are due to vote on the proposal. If 70 per cent support the idea, an official decision will be made at the World Radio Conference in 2011. According to a report co-authored by Felicitas Arias, most member states support the idea. The UK, however, is against reworking its laws, which include the solar timescale Greenwich Mean Time. Without the UK abolition may be difficult, says Felicitas Arias.

“In theory, adding a second is as easy as flipping a switch; in practice, it rarely works that way,” says Dennis McCarthy of the US Naval Research Laboratory, which provides the time standard used by the US military. Most likely to be affected are IT systems that need precision of less than a second. In 1998 - two leap seconds ago - cellphone communications blacked out over part of the southern US. Different regions of service had slipped into slightly different times, preventing proper relaying of signals.

All quotes attributed to the BBC

That would be fine if the earth was punctual but in fact it is not. The Earth’s rotation rate changes every day by thousands of nanoseconds, and this is due in a large part to wind and waves spinning around the Earth and causing drag.

Over the course of thousands of days, these changes in the rate of rotation can result in the Earth’s spin getting out of synch with the high-precision atomic clocks that we use to keep the UTC system (Coordinated Universal Time) ticking over. For this reason the Earth’s rotation is monitored and timed using the far off flashes from a type of collapsed star called a quasar that flash with an ultra precise rhythm many millions of light years away. By monitoring the Earth’s spin against these far away objects it can be worked out how much the rotation has slowed.

Once a second of slowing has been built up, The International Earth Rotation Service (IERS), recommends a Leap Second to be added, usually at the end of the year.

Other complications arise when it comes to synchronising the Earth to one timescale. In 1905, Albert Einstein’s theory of relativity showed that there is no such thing as absolute time. Every clock, everywhere in the universe, ticks at a different rate. For GPS, this is an enormous issue because it turns out that the clocks on the satellites drift by almost 40,000 nanoseconds per day relative to the clocks on the ground because they are high above the Earth’s surface (and therefore in a weaker gravitational field) and are moving fast relative to the ground.

And as light can travel Forty-thousand feet in that time, you can see the problem. Einstein’s equations first written down in 1905 and 1915 are used to correct for this time-shift, allowing GPS to work, planes to navigate safely and GPS NTP servers to receive the correct time.

Simple on-off carrier modulation is used, the rise and fall times of the carrier are determined by the combination of antenna and transmitter. The timing of these edges is governed by the seconds and minutes of Coordinated Universal Time (UTC), which is always within a second of Greenwich Mean Time (GMT). Every UTC second is marked by an ‘off’ preceded by at least 500 ms of carrier, and this second marker is transmitted with an accuracy better than ±1 ms.

The first second of the minute begins with a period of 500 ms with the carrier off, to serve as a minute marker. The other 59 (or, exceptionally, 60 or 58) seconds of the minute always begin with at least 100 ms ‘off’ and end with at least 700 ms of carrier. Seconds 01-16 carry information for the current minute about the difference (DUT1) between astronomical time and atomic time, and the remaining seconds convey the time and date code. The time and date code information is always given in terms of UK clock time and date, which is UTC in winter and UTC+1h when Summer Time is in effect, and it relates to the minute following that in which it is transmitted.

Dedicated MSF NTP Server devices are available that can connect directly to the MSF transmission.

Information Courtesy of NPL

The UK MSF signal is operated by NPL - the National Physical Laboratory. MSF has high transmitter power (50,000 watts), a very efficient antenna and an extremely low frequency (60,000 Hz). For comparison, a typical AM radio station broadcasts at a frequency of 1,000,000 Hz. The combination of high power and low frequency gives the radio waves from MSF a lot of bounce, and this single station can therefore cover most of Britain and some of continental Europe.

The time codes are sent from MSF using one of the simplest systems possible, and at a very low data rate of one bit per second. The 60,000 Hz signal is always transmitted, but every second it is significantly reduced in power for a period of 0.2, 0.5 or 0.8 seconds: • 0.2 seconds of reduced power means a binary zero • 0.5 seconds of reduced power is a binary one. • 0.8 seconds of reduced power is a separator. The time code is sent in BCD (Binary Coded Decimal) and indicates minutes, hours, day of the year and year, along with information about daylight savings time and leap years.

The time is transmitted using 53 bits and 7 separators, and therefore takes 60 seconds to transmit. A clock or watch can contain an extremely small and relatively simple antenna and receiver to decode the information in the signal and set the clock’s time accurately. All that you have to do is set the time zone, and the atomic clock will display the correct time.

Dedicated time servers that are tuned to receive the MSF time signal are available. These devices connect o a computer network like any other server only these receive the timing signal and distribute it to other machines on the network using NTP (Network Time Protocol).

Unfortunately modern PC’s are not designed to be perfect timekeepers. Their system clocks are simple electronic oscillators and are prone to drift. This is not normally a problem when the machines are working independently but when they are communicating across a network all sorts of problems can occur.

From emails arriving before they have been sent to entire system crashes, lack of synchronisation can causes untold problems across a network and it is for this reason that network time servers are used to ensure the entire network is synchronised together.

Network time servers come in two forms – The GPS time server and the radio referenced time server. GPS NTP servers use the time signal broadcast from GPS satellites. This is extremely accurate as it is generated by an atomic clock on board the GPS satellite. Radio referenced NTP servers use a long wave transmission broadcast by several national physics laboratories.

Both these methods are a good source of Coordinated Universal Time (UTC) the world’s global timescale. UTC is used by networks across the globe and synchronising to it allows computer networks to communicate confidently and partake of time sensitive transactions without error.

Some administrators use the Internet to receive a UTC time source. Whilst a dedicated network time server is not required to do this it does have security drawbacks in that a port is needed to be left open in the firewall for the computer to communicate with the NTP server, this can leave a system vulnerable and open to attack. Furthermore, Internet time sources are notoriously unreliable with many either too inaccurate or too far away to serve any useful purpose.

NTP was developed to solve the problem of multiple computers working together and having the different time. Whilst, time usually just advances, if programs are running on different computers time should advance even if you switch from one computer to another. However, if one system is ahead of the other, switching between these systems would cause time to jump forward and back.

As a consequence, networks may run their own time, but as soon as you connect to the Internet, effects become visible. Just Email messages arrive before they were sent, and are even replied to before they were mailed!

Whilst this sort of problem may seem innocuous when it comes to receiving email, however, in some environments a lack of synchronisation can have disastrous results this is why air traffic control was one of the first applications for NTP.

NTP uses a single time source and distributes it amongst all devices on a network it does this by using an algorithm that works out how much to adjust a system clock to ensure synchronisation.

NTP works on a hierarchical basis to ensure there are no network traffic and bandwidth problems. It uses a single time source, normally UTC (coordinated universal time) and receives time requests from the machines on the top of the hierarch which then pass the time on further down the chain.

Most networks that utilise NTP will use a dedicated network time server to receive their UTC time signal. These can receive the time from the GPS network or radio transmissions broadcast by national physics laboratories. These dedicated NTP time servers are ideal as they receive time direct from an atomic clock source they are also secure as they are situated externally and therefore do not require interruptions in the network firewall.

The attractive white mushroom is smaller than conventional GPS antennas and sits just 77.5mm or 3.05-inch in height and is easily fitted and installed thanks to the inclusion of a full installation guide and CD manual.

Whilst an ideal unit for a GPS NTP time server this industry standard antenna is also ideal for all GPS receiving needs including: Marine Navigation, Control Vehicle Tracking and NTP synchronisation
The main features of the Exactime 300 mushroom antenna are:

• Built-in patch antenna • 12 parallel tracking channels • Fast TTFF (Time to first fix) and low power consumption • On-board, rechargeable battery sustained Real-Time Clock and control • parameters memory for fast satellite acquisition during power-up • Interference filter to major VHF channels of marine radar • WAAS compliant with EGNOS support • Perfect Static Drift for both of speed and course •  Magnetic Declination compensation • Is protected against reverse polarity voltage • Support RS-232 or RS-422 interface, Support 1 PPS output.

A GPS NTP time server is an ideal time and frequency source because it can provide highly accurate time anywhere in the world using relatively cheap components.  Each GPS satellite transmits in two frequencies L2 for the military use and L1 for use by civilians transmitted at 1575 MHz, Low-cost GPS antennas and receivers are now widely available.

The radio signal transmitted by the satellite can pass through windows but can be blocked by buildings so the ideal location for a GPS antenna is on a rooftop with a good view of the sky. The more satellites it can receive from the better the signal. However, roof-mounted antennas can be prone to lighting strikes or other voltage surges so a suppressor is highly recommend being installed inline on the GPS cable.

The cable between the GPS antenna and receiver is also critical. The maximum distance that a cable can run is normally only 20-30 metres but a high quality coax cable combined with a GPS amplifier placed in-line to boost the gain of the antenna can allow in excess of 100 metre cable runs. This can provide difficulties in installation in larger buildings if the server is too far from the antenna.

An alternative solution is to use a radio referenced NTP time server. These rely on a number of national time and frequency radio transmissions that that broadcast UTC time. In Britain the signal (called MSF) is broadcast by the National Physics Laboratory in Cumbria which serves as the United Kingdom’s national time reference, there are also similar systems in the USA (WWVB) and in France, Germany and Japan.

A radio based NTP server usually consists of a rack-mountable time server, and an antenna, consisting of a ferrite bar inside a plastic enclosure, which receives the radio time and frequency broadcast. It should always be mounted horizontally at a right angle toward the transmission for optimum signal strength. Data is sent in pulses, 60 a second. These signals provides UTC time to an accuracy of 100 microseconds, however, the radio signal has a finite range and is vulnerable to interference.

IERS announced in Paris in July that a positive Leap Second was to be added to 2008, the first since Dec. 31, 2005. Leap Seconds were introduced to compensate for the unpredictability of the Earth’s rotation and to keep UTC (Coordinated Universal Time) with GMT (Greenwich Meantime).

The new extra second will be added on the last day of this year at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time — 6:59:59 pm Eastern Standard Time. 33 Leap Seconds have been added since 1972

NTP server systems controlling time synchronisation on computer networks are all governed by UTC (Coordinated Universal Time). When an additional second is added at the end of the year UTC will automatically be altered as the additional second. #

Whether a NTP server receives a time signal fro transmissions such as MSF, WWVB or DCF or from the GPS network the signal will automatically carry the Leap Second announcement.

Notice of Leap Second from the International Earth Rotation and Reference Systems Service (IERS)

SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE

SERVICE DE LA ROTATION TERRESTRE
OBSERVATOIRE DE PARIS
61, Av. de l’Observatoire 75014 PARIS (France)
Tel.      : 33 (0) 1 40 51 22 26
FAX       : 33 (0) 1 40 51 22 91
e-mail    : services.iers@obspm.fr
http://hpiers.obspm.fr/eop-pc

Paris, 4 July 2008

Bulletin C 36

To authorities responsible for the measurement and distribution of time

UTC TIME STEP
on the 1st of January 2009

A positive leap second will be introduced at the end of December 2008.
The sequence of dates of the UTC second markers will be:

2008 December 31,     23h 59m 59s
2008 December 31,     23h 59m 60s
2009 January   1,      0h  0m  0s

The difference between UTC and the International Atomic Time TAI is:

from 2006 January 1, 0h UTC, to 2009 January 1  0h UTC  : UTC-TAI = - 33s
from 2009 January 1, 0h UTC, until further notice       : UTC-TAI = - 34s

Leap seconds can be introduced in UTC at the end of the months of December

Most methods of timekeeping have traditionally been based on the movement of the Earth around the Sun. For millennia, a day has been divided into 24 equal parts that have become known as hours. Basing our timescales on the rotation of the Earth has been adequate for most of our historical needs, however as technology advances, the need for an ever increasingly accurate timescale has been evident.

The problem with the traditional methods became apparent when the first truly accurate timepieces - the atomic clock was developed in the 1950’s. Because these timepieces  was based on the frequency of atoms and were accurate to within a second every million years it was soon discovered that our day, that we had always presumed as being precisely 24 hours, altered from day to day.

The affects of the Moon’s gravity on our oceans causes the Earth to slow and speed up during its rotation - some days are longer than 24 hours whilst others are shorter. Whilst this minute differences in the length of a day have made little difference to our daily lives it this inaccuracy has implications for many of our modern technologies such as satellite communication and global positioning.

A timescale has been developed to deal with the inaccuracies in the Earth’s spin - Coordinated Universal Time (UTC). It is based on the traditional 24-hour Earth rotation known as Greenwich Meantime (GMT) but accounts for the inaccuracies in the earth’s spin by having so-called ‘Leap Seconds’ added (or subtracted).

As UTC is based on the time told by atomic clocks it is incredibly accurate and therefore has been adopted as the World’s civilian timescale and is used by business and commerce all over the globe.

Most computer networks can be synchronised to UTC by using a dedicated NTP time server.

Even when we all live on the same planet and experience the passing of time in a similar way, telling the time can be increasingly difficult. Our original method of using the Earth’s rotation has since been discovered to be inaccurate as the Moon’s gravity causes some days to be longer than 24 hours and a few to be shorter. In fact when the early dinosaurs were roaming the Earth a day was only 22 hours long!

Whilst mechanical and electronic clocks have provided us with some degree accuracy, our modern technologies have required far more accurate time measurements. GPS, Internet trading and air traffic control are just three industries were split second timing is incredibly important.

So how do we keep track of time? Using the Earth’s rotation has proven unreliable whilst electrical oscillators (quartz clocks) and mechanical clocks are only accurate to a second or two per day. Unfortunately for many of our technologies a second inaccuracy can be far too long. In satellite navigation, light can travel 300,000 km in just over a second, making the average sat-nav unit useless if there was one second of inaccuracy.

The solution to finding an accurate method of measuring time has been to examine the very small – quantum mechanics. Quantum mechanics is the study of the atom and its properties and how they interact. It was discovered that electrons, the tiny particles that orbit atoms changed the path that they orbit and released a precise amount of energy when they do so.

In the case of the caesium atom this occurs nearly nine billion times a second and this number never alters and so can be used as an ultra reliable method of keeping track of time. Caesium atoms are use din atomic clocks and in fact the second is now defined as just over 9 billion cycles of radiation of the caesium atom.

Atomic clocks are the foundation for many of our technologies. The entire global economy relies on them with the time relayed by NTP time servers on computer networks or beamed down by GPS satellites; ensuring the entire world keeps the same, accurate and stable time.

An official global timescale, Coordinated Universal Time (UTC) has been developed thanks to atomic clocks allowing the whole world to run the same time to within a few thousandths of a second from each other.

Most time servers use the protocol NTP (Network Time Protocol). NTP is one of the Internet’s oldest protocols and is used by the majority of machines that use a time server. NTP is often installed, in a basic form, in most operating systems.

A GPS time server, as the names suggests, receives a timing signal from the GPS network. GPS satellites are really nothing more than orbiting clocks. Onboard each GPS satellite is an atomic clock. The ultra-precise time from this clock is what is transmitted from the satellite (along with the satellite’s position).

A satellite navigation system works by receiving the time signal from three or more satellites and by working out the position of the satellites and how long the signals took to arrive, it can triangulate a position.

A GPS time server needs even less information and only one satellite is required in order to receive a timing reference. A GPS time server’s antenna will receive a timing signal from one of the 33 orbiting satellites via line of sight, so the best place to fix the antenna is the roof.

Most dedicated GPS NTP time servers require a good 48 hours to locate and get a steady fix on a satellite but once they have it is rare for communication to be lost.

The time relayed by GPS satellites is known as GPS time and although it differs to the official global timescale UTC (Coordinated Universal Time) as they are both based on atomic time (TAI) GPS time is easily converted by NTP.

A GPS time server is often referred to as a stratum 1 NTP device, a stratum 2 device is a machine that receives the time from the GPS time server. Stratum 2 and stratum 3 devices can also be used as a time servers and in this way a single GPS time server can operate as a timing source for an unlimited amount of computers and devices as long as the hierarchy of NTP is followed.

We are all used to having a different time from the rest of the world. When America is waking up, Honk Kong is going to bed which is why the world is divided into time zones. Even in the same time-zone there can still be differences. In mainland Europe for instance most countries are an hour ahead of the UK because of Britain’s seasonal clock changing.

However, when it comes to global communication, having different times all over the world can cause problem particularly if you have to conduct time sensitive transactions such as buying or selling shares.

For this purpose it was clear by the early 1970’s that a global timescale was required. It was introduced on 1 January 1972 and was called UTC – Coordinated Universal Time. UTC is kept by atomic clock but is based on Greenwich Meantime (GMT – often called UT1) which is itself a timescale based on the rotation of the Earth. Unfortunately the Earth varies in its spin so UTC accounts for this by adding a second once or twice a year (Leap Second).

Whilst controversial to many, leap seconds are needed by astronomers and other institutions to prevent the day from drifting otherwise it would be impossible to work out the position of the stars in the night sky.

UTC is now used all over the world. Not only is it the official global timescale but is used by hundreds of thousands of computer networks all over the world.

Computer networks use a network time server to synchronise all devices on a network to UTC. Most time servers use the protocol NTP (Network Time Protocol) to distribute time.

NTP time servers receive the time from atomic clocks by either long-wave radio transmissions from national physics laboratories or from the GPS network (Global Positioning System). GPS satellites all carry an onboard atomic clock that beams the time back to Earth. Whilst this time signal is not strictly speaking UTC (it is known as GPS time) because of the accuracy of the transmission it is easily converted to UTC by a GPS NTP server.

In terms of accuracy an atomic clock is unrivalled. Digital quartz clocks may keep accurate time for a week, not losing more than a second but an atomic clock can keep time for millions of years without drifting as much.

Atomic clocks work on the principle of quantum leaps, a branch of quantum mechanics which states that an electron; a negatively charged particle, will orbit a nucleus of an atom (the centre) in a certain plain or level. When it absorbs or releases enough energy, in the form of electromagnetic radiation, the electron will jump to a different plane - the quantum leap.

By measuring the frequency of the electromagnetic radiation corresponding to the transition between the two levels, the passage of time can be recorded. Caesium atoms (caesium 133) are preferred for timing as they have 9,192,631,770 cycles of radiation in every second. Because the energy levels of the caesium atom (the quantum standards) are always the same and is such a high number, the caesium atomic clock is incredibly precise.

The most common form of atomic clock used in the world today is the caesium fountain. In this type of clock a cloud of atoms is projected up into a microwave chamber and allowed to fall down under gravity. Laser beams slow these atoms down and the transition between the atom’s energy levels are measured.

The next generation of atomic clocks are being developed use ion traps rather than a fountain. Ions are positively charged atoms which can be trapped by a magnetic field. Other elements such as strontium are being used in these next generation clocks and it is estimated that the potential accuracy of a strontium ion trap clock could be 1000 times that of the current atomic clocks.

Atomic clocks are utilised by all sorts of technologies; satellite communication, the Global Positioning System and even Internet trading is reliant on atomic clocks. Most computers synchronise indirectly to an atomic clock by using a NTP server. These devices receive the time from an atomic clock and distribute around their networks ensuring precise time on all devices.

To allow global communication and time sensitive transactions such as the buying of stacks and shares a global timescale, based on the time told by atomic clocks, was developed in 1972. This timescale, Coordinated Universal Time (UTC) is governed and controlled by the International Bureau of weights and Measures (BIPM) who use a constellation of over 230 atomic clocks from 65 laboratories all over the world to ensure high levels of accuracy.

Atomic clocks are based on the fundamental properties of the atom, known as quantum mechanics.  Quantum mechanics suggest that an electron (negatively charged particle) that orbits an atom’s nucleus can exist in different levels or orbit planes depending if they absorb or release the correct amount of energy. Once an electron has absorbed or released enough energy in can ‘jump’ to another level, this is known as a quantum jump.

The frequency between these two energy states is what is used to keep time. Most atomic clocks are based on the caesium atom which has 9,192,631,770 periods of radiation corresponding to the transition between the two levels. Because of the accuracy of caesium clocks the BIPM now considers a second to be defined as 9,192,631,770 cycles of the caesium atom.

Atomic clocks are used in thousands of different applications where precise timing is essential. Satellite communication, air traffic control, internet trading and GPS all require atomic clocks to keep time. Atomic clocks can also be used as a method of synchronising computer networks.

A computer network using a NTP time server can use either a radio transmission or the signals broadcast by GPS satellites (Global Positioning System) as a timing source. The NTP program (or daemon) will then ensure all devices on that network will be synchronised to the time as told by the atomic clock.

By using a NTP server synchronised to an atomic clock, a computer network can run the identical coordinated universal time as other networks allowing time sensitive transactions to be conducted from across the globe.

A stratum 0 device is an atomic clock itself. These are highly expensive and delicate pieces of machinery and are only to be found in large scale physics laboratories. Unfortunately there are many rules governing who can access a stratum 1 server because of bandwidth considerations. Most stratum 1 NTP servers are set-up by universities or other non-profit organisations and so have to restrict who accesses them.

Fortunately stratum 2 time servers can offer decent enough accuracy as a timing source and any device receiving a time signal can itself be used as a time reference (a device receiving time from a stratum 2 device is a stratum 3 server. Devices that receive time from a stratum 3 server are stratum 4 devices, and so-on).

NTP.org, is the official home of the NTP pool project and by far the best place to go to find a public NTP server. There are two lists of public servers available in the pool; primary servers, which displays the stratum 1 servers (most of which are closed access) and secondary which are all stratum 2 servers.

When using a public NTP server is important to abide by the access rules as failure to do so can cause the server to become clogged with traffic and if the problems persist possibly discontinued as most public NTP servers are set-up as acts of generosity.

There are some important points to remember when using a timing source from over the Internet. First, Internet timing sources can’t be authenticated. Authentication is an in-built security measure utilised by NTP but unavailable over the net. Secondly, to use an Internet timing source requires an open port in your firewall. A hole in a firewall can be used by malicious users and can leave a system vulnerable to attack.

For those requiring a secure timing source or when accuracy is highly important, a dedicated NTP server that receives a timing signal from either long wave radio transmissions or the GPS network.

Obviously, if a thousand machines on a network all attempted to receive a timing signal from the NTP server at the same time the network would become bottlenecked and the NTP server would be rendered useless.

For this reason, the NTP stratum tree exists. At the top of the tree is the NTP time server which is a stratum 1 device (a stratum 0 device being the atomic clock that the server receives its time from). Below the NTP server, several servers or computers receive timing information from the stratum 1 device. These trusted devices become stratum 2 servers, which in turn distribute their timing information to another layer of computers or servers. These then become stratum 3 devices which in turn can distribute timing information to lower strata (stratum 4, stratum 5 etc).

In all NTP can support up to nine stratum levels although the further away from the original stratum 1 device they are the less accurate the synchronisation. For an example of how a NTP hierarchy is setup please see this stratum tree diagram:

The WWVB time signal can be utilised by anyone requiring accurate timing information although its main use is as a source of UTC time for administrators synchronising a computer network with a radio clock. Radio clocks are really another term for a network time server that utilises a radio transmission as a timing source.

Most radio based network time servers use NTP (Network Time Protocol) to distribute the timing information throughout the network.

The WWVB signal is broadcast from Fort Collins, Colorado. It is available 24 hours a day across most of the USA and Canada, although the signal is vulnerable to interference and local topography. Users of the WWVB service receive predominantly a ‘ground wave’ signal. However, there is also a residual ‘sky wave’ which is reflected off the ionosphere and is much stronger at night; this can result in a total received signal that is either stronger or weaker.

The WWVB signal is carried on a frequency of 60 kHz (to within 2 parts in 1012) and is controlled by a caesium atomic clock based at NIST

The signal’s field strength exceeds 100 µV/m (microvolts a meter) at a distance of 1000 km from Colorado - covering much of the USA.

The WWVB signal is in the form of a simple binary code containing time and date information The WWVB  time and date code includes the following information: year, month, day of month,  day of week,  hour, minute, Summer Time (in effect or imminent).

The main purpose of NTP is to ensure that all devices on a network are synchronised to the same time