Category: advanced NTP

Why the Need for NTP

  |   By

Network Time Protocol is an Internet protocol used to synchronize computer clocks to a stable and precise time reference. NTP was originally developed by Professor David L. Mills at the University of Delaware in 1985 and is an Internet standard protocol and is used in most network time servers, hence the name NTP server.

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

NTP has been an astronomical success and is now used in nearly 99 per cent of time synchronisation devices and a version of it is included in most operating system packages.

NTP owes much of its success to the development and support it continues to receives nearly three decades after its inception which is why t is now used throughout the world in NTP servers.

WWVB Explained

  |   By

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.

Increased Accuracy of Dual NTP Server Systems

  |   By

The NTP time server has revolutionised the synchronisation of computer networks over the last twenty years. NTP (Network Time Protocol) is the software  that  is responsible for distributing time from the time server to the entire network, adjusting machines for drift and assuring accuracy.

NTP can reliable maintain system clocks to within a few millimetres of UTC (Coordinated Universal Time) or whatever timescale it is fed with.

However NTP can only be as reliable as the time source that it receives and as UTC  is the global civil timescale it depends on where the UTC source comes from.

National time and frequency transmissions from physics labs like NIST in the USA or NPL in the UK are extremely reliable sources of UTC and NTP time servers are designed specifically for them. However, the time signals are not guaranteed, they can drop off throughout the day and are susceptible to interference; they are also regularly turned of for maintenance.

For most applications a few hours of your network relying on crystal oscillators will probably not cause too much problems in synchronisation. However, GPS (Global Positioning System) is far more reliable source for UTC time in that a GPS satellite is always overhead. They do require a line-of-sight reception which means an antenna has to go on the roof or outside an open window.

For applications where accuracy and reliability are essential the safest solution is to invest in a dual system NTP time server, these device can receive both the radio transmissions such  as MSF, DCF-77 or WWVB and the GPS signal.

On a dual system NTP server, NTP will take both time sources and to synchronise a network to ensuring increased accuracy and reliability.

Common GPS Queries

  |   By

Is the GPS time signal the same as the GPS positioning signal?

Yes. The signals that are broadcast by GPS satellites contain time information and the position of the satellite it came from (and its velocity). The timing information is generated by an onboard caesium atomic clock. It is this information used by satellite navigation devices (sat navs) that enables global positioning. Sat Navs use these signals from multiple satellites to triangulate a position.

How accurate is GPS positioning?

Because the time signal generated by GPS comes from an atomic clock it is accurate to within 16 nanoseconds (16 billionths of a second). As light travels nearly 186 000 miles in a second this equates to around 16 feet (5+metres) which means a GPS positioning system is usually accurate to this much.

Is GPS time the same as UTC?

No. GPS time, like UTC (Coordinated Universal Time)is based on International Atomic Time (TAI) – the time told by atomic clocks. However as the GPS system was developed several decades ago it is now 14 seconds (and soon to be 15) behind UTC because it has missed out on the Leap Seconds added to UTC to calibrate for the Earth’s slowing rotation.

How can I use GPS as a source of UTC then?

Fortunately a GPS time server will convert GPS to the current UTC time, which as od 1 January 2009 will mean it has to add exactly 15 seconds.

Galileo and the GPS NTP Server

  |   By

Currently there is only one Global Navigation Satellite System (GNSS) the NAVSTAR GPS which has been open for civilian use since the late 1980’s.

Most commonly, the GPS system is thought to provide navigational information allowing drivers, sailors and pilots to pinpoint their position anywhere in the world.

In fact, the only information beamed from a GPS satellite is the time which is generated by the satellites internal atomic clock. This timing signal is so accurate that a GPS receiver can use the signal from three satellites and pinpoint the location to within a few metres by working out how long each precise signal took to arrive.

Currently a GPS NTP server can use this timing information to synchronise entire computer networks to providing accuracy to within a few milliseconds.

However, the European Union is currently working on Europe’s own Global Navigation Satellite System called Galileo, which will rival the GPS network by providing its own timing and positioning information.

However, Galileo is designed to be interoperable with GPS meaning that a current GPS NTP server will be able to receive both signals, although some software adjustments may have to be made.

This interoperability will provide increased accuracy and may make national time and frequency radio broadcasts obsolete as they will not be able to produce a comparable accuracy.

Furthermore, Russia, China and India are currently planning their own GNSS systems which may provide even more accuracy. GPS has already revolutionised the way the world works not only by allowing precise positioning but also enabling entire globe to synchronise to the same timescale using a GPS NTP server. It is expected that even more advances in technology will emerge once the next generation of GNSS begin their transmissions.

Choosing the Right Time Signal for Your Network

  |   By

Computer network synchronisation is essential in the modern world. Many of the world’s computer networks are all synchronised to the same global timescale UTC (Coordinated Universal Time).

To govern synchronisation the protocol NTP (Network Time Protocol) is used in most cases as it is able to reliably synchronise a network to a few milliseconds off UTC time.

However, the accuracy of time synchronisation is solely dependent on the accuracy of whatever time reference is selected for NTP to distribute and here lies one of the fundamental errors made in synchronising computer networks.

Many network administrators rely on Internet time references as a source of UTC time, however, apart from the security risks they pose (being as they are on the wrong side of a network firewall) but also their accuracy can not be guaranteed and recent studies have found less than half of them providing any useful accuracies at all.

For a secure, accurate and reliable method of UTC there really are just two choices. Utilise the time signal from the GPS network or rely on the long wave transmissions broadcast by national physics laboratories such as NPL and NIST.

To select which method is best then the only factor to consider is the location of the NTP server that is to receive the time signal.

GPS is the most flexible in that the signal is available literally everywhere on the planet but the only downside to the signal is that a GPS antenna has to be situated on the roof as it needs a clear view of the sky. This may prove problematic if the time server is located in the lower floors of a sky scraper but on the whole most users of GPS time signals find that they are very reliable and incredibly accurate.

If GPS is impractical then the national time and frequencies provide an equally accurate and secure method of UTC time. These longwave signals are not broadcast by every country however, although the US WWVB signal broadcast by NIST in Colorado is available in most of North America including Canada.

There are various versions of this signal broadcast throughout Europe including the German DCF and the UK MSF which prove to be the most reliable and popular. These signals can often be picked up outside the nation’s borders too although it must be noted long wave transmissions are vulnerable to local interference and topography.

For complete peace of mind, dual system NTP servers that receive signals from both the GPS and national physics laboratories are available although they tend to be a little more expensive than single systems although utilising more than one time signal makes them doubly reliable.

The World in Synchronisation

  |   By

Time synchronisation plays an ever more important role in the modern world with more and more technologies reliant on accurate and reliable time.

Time synchronisation is not just important but can also be crucial in the safe running of systems such as air traffic control that simply couldn’t function without accurate synchronisation. Think of the catastrophes that could happen in the air of aircraft were out of synchronisation with each other?

In global commerce too accurate and reliable time synchronisation is highly important. When the world’s stock markets open in the morning and traders from across the world buy stock on their computers. As stock fluctuates second by second if machines are out of synchronisation it could cost millions.

But synchronisation is also imperative in modern computer networking; it keeps systems secure and enables proper control and debugging of systems. Even if a computer network is not involved in any time sensitive transactions a lack of synchronisation can leave it vulnerable to malicious attacks and can also be susceptible to data loss.

Accurate synchronisation is possible in computer networking thanks to two developments: UTC and NTP.

UTC is a timescale -coordinated universal time, it is based on GMT but is controlled by an array of atomic clocks making it accurate to within a few nanoseconds.

NTP is a software protocol – Network Time Protocol, designed to accurately synchronise computer networks to a single time source. Both of these implementations come together in a single device which is relied upon the world over to synchronise computer networks – the NTP server.

An NTP time server or network time server is a device that receives the time from an atomic clock, UTC source and distributes it across a network. Because the time source is continually checked by the time server and is from an atomic clock it makes the network accurate to within a few milliseconds of UTC providing synchronisation on a global scale.

The Clocks to Spring Forward at the Weekend

  |   By

It’s that time of year again when we lose an hour over the weekend as the clocks go forward to British Summer Time. Twice a year we alter the clocks but in an age of UTC (Coordinated Universal Time) and time server synchronisation is it really necessary?

The changing of the clocks is something that was discussed just before World War I when London builder William Willet suggested the idea as a way of improving the nation’s health (although his initial idea was to advance the clocks twenty minutes on each Sunday in April).

His idea wasn’t taken up although it sowed the seed of an idea and when the First World War erupted it was adopted by many nations as a way to economise and maximise daylight although many of these nations discarded the concept after the war, several including the UK and USA kept it.

Daylight saving has altered over the years but since 1972 it has remained as British Summer Time (BST) in the summer and Greenwich Meantime in the winter (GMT). However, despite is use for nearly a century the changing of the clocks remains controversial. For four years Britain experimented without daylight changing but it was proved unpopular in Scotland and the North where the mornings were darker.

This timescale hopping does cause confusion (I for one will miss that hour extra in bed on Sunday) but as the world of commerce adopts the global civil timescale (which fortunately is the same as GMT as UTC is adjusted with leap seconds to ensure GMT is unaffected by the slowing of the Earth’s rotation) is it still necessary?

The world of time synchronisation certainly doesn’t need to adjust for daylight saving. UTC is the same the world over and thanks to devices such as the NTP server can be synchronised so the entire world runs the same time.

NTP Synchronization and FAQ

  |   By

With a variety of acronyms and timescales the world of time synchronisation can be quite confusing here are some frequently asked questions we hope will help enlighten you.

What is NTP?

NTP is a protocol designed to synchronize computer networks across the internet or LAN (Local Area Networks). It is not the only time synchronization protocol available but it is the most widely used and the oldest having been conceived in the late 1980’s.

What are UTC and GMT?

UTC or Coordinated Universal Time is a global timescale, it is controlled by highly accurate atomic clocks but kept the same as GMT (Greenwich Meantime) by the use of leap seconds, added when the Earth’s rotation slows down. Strictly speaking GMT is the old civil timescale and based on when the sun is above the meridian line, however, as the two systems are identical in time thanks to leap seconds, UTC is often referred to as GMT and vice versa.

And a NTP Time Server?

These are devices that synchronize a computer network to UTC by receiving a time signal and distributing it with the protocol NTP which ensures all devices are running accurately to the timing reference.

Where to get UTC time from?

There are two secure methods of receiving UTC. The first is to utilize the long wave time signals broadcast by NIST (WWVB) NPL in the UK (MSF) and the German NPL (DCF) The other method is to use a the GPS network. GPS satellites broadcast an atomic clock signal that can be utilised and converted to UTC by the GPS NTP server.

NTP GPS Server Using Satellite Time Signals

  |   By

The NTP GPS server is a dedicated device that uses the time signal from the GPS (Global Positioning System) network. GPS is now a common tool for motorists with satellite navigation devices fitted to most new cars. But GPS is far more than just an aid for positioning, at the very heart of the GPS network is the atomic clocks that are inside each GPS satellite.

The GPS system works by transmitting the time from these clocks along with the position and velocity of the satellite. A satellite navigation receiver will work out when it receives this time how long it took to arrive and therefore how far the signal travelled. Using three or more of these signals the satellite navigation device can work out exactly where it is.

GPS can only do this because of the atomic clocks that it uses to transmit the time signals. These time signals travel, like all radio signals, at the speed of light so an inaccuracy of just 1 millisecond (1/1000 of a second) could result in the satellite navigation being nearly 300 kilometres out.

Because these clocks have to be so accurate, they make an ideal source of time for a NTP time server. NTP (Network Time Protocol) is the software that distributes the time from the time server to the network. GPS time and UTC (Coordinated Universal Time) the civil timescale is not quite the same thing but are base don the same timescale so NTP has no trouble converting it. Using a dedicated NTP GPS server a network can be realistically synchronised to within a few milliseconds of UTC

The GPS clock is another term often given to a GPS time server. The GPS network consists of 21 active satellites (and a few spare) 10,000 miles in orbit above the Earth and each satellite circles the Earth twice a day. Designed for satellite navigation, A GPS receiver needs at least three satellites to maintain a position. However, in the case of a GPS clock just one satellite is required making it far easier to obtain a reliable signal.

Each satellite continuously transmits its own position and a time code. The time code is generated by an onboard atomic clock and is highly accurate, it has to be as this information is used by the GPS receiver to triangulate a position and if it was just half a second out the Sat Nav  unit would be inaccurate by thousands of miles.