Time Synchronisation

The NTP time server (Network Time Protocol) is an essential tool for keeping networks synchronised. Without adequate synchronization, computer networks can be left vulnerable to security threats, data loss, fraud and may find it impossible to interact with other networks across the globe.

Computer networks are normally synchronised to the global timescale UTC (Coordinated Universal Time) enabling them to communicate efficiently with other networks also running UTC.

Whilst UTC time sources are available across the Internet these are not secure (being outside the firewall) and many are either too far away to provide adequate precision or are too inaccurate to begin with.

The most secure methods of receiving a UTC time source are to use a dedicated NTP Time Server. These devices can receive a secure and accurate time signal either the GPS network (Global Positioning System) available anywhere across the globe with a good view of the sky or through specialist radio transmission broadcast by national physics laboratories.

In the US the National Institute for Standards and Time (NIST) broadcast a time signal from near Fort Collins, Colorado. The signal, known as WWVB can be received all over North America (including many parts of Canada) and provides an accurate and secure method of receiving UTC.

As the signal is derived from atomic clocks situated at the Fort Collins site, WWVB is a highly accurate method of synchronising time and is also secure as a dedicated NTP time server acts as an external source.

Accurate time using Atomic Clocks is available across North America using the WWVB Atomic Clock time signal transmitted from Fort Collins, Colorado; it provides the ability to synchronize the time on computers and other electrical equipment.

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).

Methods of keeping track of time have altered throughout history with ever increasing accuracy has being the catalyst for change.

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.

The way a computer deals with time is totally different to the ways humans perceive it. We arrange time into seconds, minutes, hours, days, weeks, months and years, while computers on the other hand arrange time as a single number representing the seconds that have passed from a single point in time, known as the prime epoch.

Most computers use NTP (Network Time Protocol) to deal with time and on networks many are synchronised using a dedicated NTP time server.  NTP knows nothing about days, years or centuries, only the seconds from the prime epoch.  This prime epoch is set (for most systems) at midnight at the turn of the century twentieth century that for a human would be recorded as something like: 00:00 – 01,01,1900.

Computers, however, count time as the number of seconds past this point. If a computer was around in 1900 its timestamp on midnight January 1 would be 0 while in 1972 at the same date the timestamp would be 2,272,060,800, which represents the number of seconds since 1900.

The timestamps restart every 136 years with the next wrap around due in 2036, this has caused uneasiness amongst some who fear a Millennium Bug type scenario, although most doubt such events would occur, however, when a wrap-around of the timestamp does happen an era integer will be added (+1), to allow computers to deal with time spans that cover more than one wrap-around.  If computers and NTP need to deal with time that spans before the prime epoch a negative integer is used (for the year 1500 a -3 will be used to represent three cycles of 136 years).

Timestamps are used in virtually every transaction that modern computers are tasked to do such as sending emails, debugging and programming. Because time is linear, a computer knows that each timestamp is always greater than the previous one and therefore computers and NTP find it difficult to deal with inaccuracies in time, particularly when time suddenly appears to go backwards.

This can happen if computers are not synchronised to the same time. If an email is sent to a machine with a slower clock, it appears to the computer to have been received before it has been sent.  Lack of synchronisation can serious problems and can even leave a system vulnerable to malicious attacks and even fraud.

Because of this, most computer networks are synchronised to UTC (Coordinated Universal Time). UTC is a global timescale and the same for everybody worldwide it is based on the time told by atomic clocks which are highly accurate, neither gaining nor losing a second in millions of years.

Most computer networks use a dedicated NTP time server to receive a UTC time to synchronise their computers too.  UTC is available from across the Internet (although unsecured), via the GPS network (Global Positioning System), or by receiving national time and frequency broadcasts via long wave.

NTP synchronises a computer by checking the received UTC time and adding to or holding a computer’s timestamp until it perfectly matches UTC. By using a dedicated NTP time server UTC can be maintained on a network to a few milliseconds of UTC time.