Category: Time Synchronisation

The Effect of Solar Flares on GPS

  |   By

Forthcoming space weather may affect GPS devices including satellite navigation and NTP GPS time servers.

Whilst many of us have had to cope with some extreme weather last winter, further storms are on their way – this time from space.

Solar flares are a regular occurrence on the surface of the sun. Whilst scientists are not completely sure what causes them we know two things about solar flares: – they are cyclical – and are related to sunspot activity.

For that last eleven years the sun’s sunspot activity – small dark depressions that appear on the surface of the sun – has been very minimal. But this eleven year cycle has come to an end and there has been a rise in sun spots at the end of last year meaning 2010 will be a bumper year for both sunspots and solar flares.

But there is no need to worry about becoming toasted by solar flares as these bursts of hot gases that flare from the sun never get far enough to reach the Earth, however, they can effect us in different ways.

Solar flares are bursts of energy and as such emit radiation and high energy particles. On earth, we are protected by these blasts of energy and radiation by the earth’s magnetic field and ionosphere, however, satellite communications are not and this can lead to trouble.

Whilst the effect of solar flare radiation is very weak, it can slow down and reflect radio waves as they travel through the ionosphere towards Earth. This interference can cause GPS satellites in particular extreme problems as they are reliant on accuracy to provide navigational information.

While the effects of solar flares are mild, it is possible GPS devices will encounter brief periods of no signal and also the problem of inaccurate signals meaning positing information may become unreliable.

This will not just affect navigation either as the GPS system is used by hundreds and thousands of computer networks as a source of reliable time.

Whilst most dedicated GPS time servers should be able to cope with periods of instability without losing precision, for worried network administrators not wanting to go into work to find their systems have crashed because of a lack of synchronisation may want to consider using a radio referenced Network time server that uses broadcast transmission such as MSF or WVBB.

Dual NTP time servers (Network Time Protocol) are also available that can receive both radio and GPS, ensuring a source of time is always constantly available.

A Guide to Synchronising a Network with NTP

  |   By

Network Time Protocol (NTP) is a TCP/IP protocol developed when the internet was in its infancy. It was developed by David Mills of the University of Delaware who was trying to synchronise computers across a network with a degree of precision.

NTP is a UNIX based protocol but it has been ported to operate just as effectively on PCs and a version has been included with operating systems since Windows 2000 (including Windows 7, Vista and XP).

NTP, and the daemon (application) that controls it, is not just a method of passing the time around. Any system running the NTP daemon can act as a client by querying the reference time from other servers or it can make its own time available for other devices to use which in effect turns it into a time server itself. It can also act as a peer by collaborating with other peers to find the most stable and accurate time source to use.

One of the most flexible aspects of NTP is its hierarchical nature. NTP divides devices into strata, each stratum level is defined by its proximity to the reference clock (atomic clock). The atomic clock itself is a stratum 0 device, the closest device to it (often a dedicated NTP time server) is a stratum 1 device whilst other devices that connect to that become stratum 2. NTP can maintain accuracy to within 16 stratum levels.

Any network that needs to be synchronised, has to first identify and locate a time source for NTP to distribute. Internet sources of time are available but thee are often taken from stratum 2 devices that operate through the firewall. The only way NTP can peer the time is if the TCP/IP port is left open to allow the traffic through. This could lead to security issues as malicious users can take advantage of this firewall hole.

Dedicated NTP time servers find a source of time via GPS or radio signals and so don’t leave a network vulnerable to attack. By attaching a NTP time server to a router and entire network of hundreds and even thousands of devices can be synchronised thanks to NTP’s hierarchical structure.

New Technologies and the Growing Importance of Time Synchronisation

  |   By

The NTP protocol (Network Time Protocol) has since the earliest days of the internet been responsible for synchronising the time across computer networks. Not only is NTP effective at this, but when connected to a source of UTC (Coordinated Universal Time) NTP is also extremely accurate.

Most computer networks connect to UTC via a dedicated NTP time server. These devices use an external connection to an atomic clock to receive the time and then distribute it across a network. By connecting externally, via GPS (Global Positioning System) or long wave radio , not only are NTP time servers incredibly accurate but they are also very secure as they don’t rely on an internet connection for the time.
NTP time servers are also increasingly being used for other new innovations. Not only have traditional technologies such as CCTV, traffic lights, air traffic control and the stock exchange, become reliant on time synchronisation with time servers but an increasing amount of modern technologies are too.

NTP time servers are now common in modern digital signage systems (the use of flat screen TVs for out of home advertising). These networked screens are often synchronised to allow scheduled and orchestrated campaigns.

A synchronized digital signage campaign is one method of making an out of home advertising campaign stand-out. This is increasingly important as more and more digital signage is being implemented making a conventional digital signage campaign difficult to engage and catch the eye.

By synchronising multiple screens together with a NTP time server and running a scheduled and timed campaign. This allows content to be scheduled or timed to maximise its impact.

Small time servers can eben be installed directly into the digital signage of LCD enclosure although as most of these tiem synchnisation devices require a GPS or long wave signal the antenna can be problamtic. A better solution is to network the digtal signage and use a single NTP server as a method fo synchonisation.

NTP may be the oldest protocol on the internet and NTP time servers have been around for nearly two decades but this comparatively antique technology and software has never been so much in demand.

The Atomic Clock Scientific Precision

  |   By

Precision is becoming increasingly important in modern technologies and none more so than accuracy in time keeping. From the internet to satellite navigation, precise and accurate synchronicity is vital in the modern age.

In fact many of the technologies that we take for granted in today’s world, would not be possible if it wasn’t for the most accurate machines invented – the atomic clock.

Atomic clocks are just timekeeping devices like other clocks or watches. But what stands them apart is the accuracy they can achieve. As a crude example your standard mechanical clock, such as a town centre clock tower, will drift by as much as a second a day. Electronic clocks such as digital watches or clock radios are more accurate. These types of clock drift a second in about a week.

However, when you compare the precision of an atomic clock in which a second will not be lost or gained in 100,000 years or more the accuracy of these devices is incomparable.

Atomic clocks can achieve this accuracy by the oscillators they use. Nearly all types of clock have an oscillator. In general, an oscillator is just a circuit that regularly ticks.

Mechanical clocks use pendulums and springs to provide a regular oscillation while electronic clocks have a crystal (usually quartz) that when an electric current is run through, provides an accurate rhythm.

Atomic clocks use the oscillation of atoms during different energy states. Often caesium 133 (and sometimes rubidium) is used as its hyperfine transitional oscillation is over 9 billion times a second (9,192,631,770) and this never changes. In fact, the International System of Units (SI) now officially regards a second in time as 9,192,631,770 cycles of radiation from the caesium atom.

Atomic clocks provide the basis for the world’s global timescale – UTC (Coordinated Universal Time). And computer networks all over the world stay in sync by using time signals broadcast by atomic clocks and picked up on NTP time servers (Network Time Server).

Network Time Protocol And Network Time Synchronization

  |   By

Synchronization of computer networks is something that many administrators take for granted. Dedicated network time servers can receive a time source and distribute it amongst a network, accurately, securely and precisely.

However, accurate time synchronization is only made possible thanks the time protocol NTP – Network Time Protocol.

NTP was developed when the internet was still in its infancy and Professor David Mills and his team from Delaware University were trying to synchronise the time on a network of a few machines. They developed the very earliest rendition of NTP which has continued to be developed to this very day, nearly thirty years after its first inception.

NTP was not then, and is not now, the only time synchronisation software, there are other applications and protocol that do a similar task but NTP is the most widely used (by far with over 98% of time synchronisation applications using it). It is also packaged with most modern operating systems with a version of NTP (usually SNTP – a simplified version) installed on the latest Windows 7 operating system.

NTP has played an important part in creating the internet we know and love today. Many online applications and tasks would not be possible without accurate time synchronization and NTP.

Online trading, internet auctions, banking and debugging of networks all rely on accurate time synchronisation. Even sending an email requires time synchronisation with email server – otherwise computers would not be able to handle emails coming from unsynchronised machines as they may arrive before they were sent.

NTP is a free software protocol and is available online from NTP.org However, most computer networks that require secure and accurate time mostly use dedicated NTP servers that operate external to the network and firewall obtaining the time from atomic clock signals ensuring millisecond accuracy with the world’s global timescale UTC (Coordinated Universal Time).

Using GPS as a source of Accurate Time

  |   By

The Global Positioning System (GPS) is an increasingly popular tool, used throughout the world as a source of wayfinding and navigation. However, there is much more to the GPS network than just satellite navigation as the transmissions broadcast by the GPS satellites can also be used as a highly accurate source of time.

GPS satellites are actually just orbiting clocks as each one contains atomic clocks that generate a time signal. It is the time signal that is broadcast by the GPS satellites that satellite navigation receivers in cars and planes use to work out distance and position.

Positioning is only possible because thee time signals are so accurate. Vehicle sat navs for instance use the signals from four orbiting satellites and triangulate the information to work out the position. However, if there is just one second inaccuracy with one of the time signals then the positing information could be thousands of miles out – proving useless.

It is testament to the accuracy of atomic clocks used to generate GPS signals that currently a GPS receiver can work out its position on earth to within five metres.

Because GPS satellites are so accurate, they make an ideal source of time to synchronise a computer network to. Strictly speaking GPS time differs from the international timescale UTC (coordinated Universal Time) as UTC has had additional leap seconds added to it to ensure parity with the earth’s rotation meaning it is exactly 18 seconds ahead of GPS but is easily converted by NTP the time synchronisation protocol (Network Time Protocol).

GPS time servers receive the GPS time signal via a GPS antenna which has to be placed on the roof to receive the line of sight transmissions. Once the GPS signal is received the NTP GPS time server will distribute the signal to all devices on the NTP network and corrects any drift on individual machines.

GPS time servers are dedicated easy to use devices and can ensure millisecond accuracy to UTC without any of the security risks involved in using an internet time source.

Atomic Clock Synchronization made easy with a NTP Time Server

  |   By

Atomic clocks are the ultimate in timekeeping devices. Their accuracy is incredible as an atomic clock will not drift by as much as a second within a million years, and when this is compared to the next best chronometers, such as electronic clock that can drift by a second in a week, an atomic clock is incredibly more precise.

Atomic clocks are used the world over and are the heart of many modern technologies making capable a multitude of applications that we take for granted. Internet trading, satellite navigation, air traffic control and international banking are all industries that rely heavily on

They also govern the world’s timescale, UTC (Coordinated Universal Time) which is kept true by a constellation of these clocks (although UTC has to be adjusted to accommodate the slowing of the Earth’s spin by adding leap seconds).

Computer networks are often required to run synchronized to UTC. This synchronisation is vital in networks that conduct time sensitive transactions or require high levels of security.

A computer network without adequate time synchronization can cause many issues including:

Loss of data

  • Difficulties in identifying and logging errors
  • Increased risk of security breaches.
  • Unable to conduct time sensitive transactions

For these reasons many computer networks have to be synchronized to a source of UTC and kept as accurate as possible. And although atomic clocks are large bulky devices kept in the confines of physics laboratories, using them as a source of time is incredibly simple.

Network Time Protocol (NTP) is a software protocol designed solely for the synchronisation of networks and computer systems and by using a dedicated NTP server the time from an atomic clock can be received by the time server and distributed around the network using NTP.

NTP servers use radio frequencies and more commonly the GPS satellite signals to receive the atomic clock timing signals which is then spread throughout the network with NTP regularly adjusting each device to ensure it is as accurate as possible.

MSF Outages for 2010

  |   By

Users of the National Physical Laboratory’s (NPL) MSF time and frequency signal are probably aware that the signal is occasionally taken off-air for scheduled maintenance.

NPL have published there scheduled maintenance for 2010 where the signal will be temporarily taken off-air. Usually the scheduled downtimes lasts for less than four hours but users need to be aware that while NPL and VT Communications, who service the antenna, make every effort to ensure the transmitter is off for a brief amount of time as possible, there can be delays.

And while NPL like to ensure all users of the MSF signal have advanced warning of possible outages, emergency repairs and other issues may lead to unscheduled outages. Any user receiving problems receiving the MSF signal should check the NPL website in case of unscheduled maintenance before contacting your time server vendor.

The dates and times of the scheduled maintenance periods for 2010 are as follows:

* 11 March 2010 from 10:00 UTC to 14:00 UTC

* 10 June 2010 from 10:00 BST to 14:00 BST (UTC + 1 hr)

* 9 September 2010 from 10:00 BST to 14:00 BST (UTC + 1 hr)

* 9 December 2010 from 10:00 UTC to 14:00 UTC

As these scheduled outages should take no longer than four hours, users of MSF referenced time servers should not notice any drop off in accuracy of their network as their shouldn’t be enough time for any device to drift.

However, for those users concerned about accuracy or require a NTP time server (Network Time Server) that doesn’t succumb to regular outages, they may wish to consider investing in a GPS time server.

GPS time servers receive the time from the orbiting navigational satellites. As these are available anywhere on the globe and the signals are never down for outages they can provide a constant accurate time signal (GPS time is not the same as UTC but is easily converted by NTP as it is exactly 17 seconds behind due to leap seconds being added to UTC and not GPS).

Why a GPS Time Server is the Number One Choice for Time Synchronization

  |   By

When it comes to synchronizing a computer network there are several choice to ensure each device is running the same time. NTP (Network Time Protocol) is the preferred choice of time synchronization protocols but there are a multitude of methods in how NTP receives the time.

The NTP Daemon is installed on most operating systems such as windows and applications such as Windows Time are quite capable of receiving a source of UTC time (Coordinated Universal Time) from across the internet.

UTC time is the preferred time source used by computer networks as it is kept true by atomic clocks. UTC, as the name suggests, is also universal and is used by computer networks all over the world as a source to synchronize too.

However, internet sources of UTC are to recommended for any organisation where security and accuracy are a concern. Not only can the distant from host (internet time server) to the client (your computer network) can never be accurately measured leading to a drop in precision. Furthermore, any source of internet time will need access through the firewall (usually through the UDP 123 port). And by leaving this port open, malicious users and hackers can take advantage and gain access to the system.

Dedicated NTP time servers are a better solution as they receive the time from an external source. There are really two types of NTP server, the radio reference time server and the GPS time server.
Radio reference time servers use signals broadcast by places like NPL (National Physical Laboratory in the UK) or NIST (National Institute of Standards and Time). While these signals are extremely accurate, precise and secure they are affected by regular maintenance on the transmitters that broadcast the signal. Also being long wave they are vulnerable to local interference.

GPS time servers on the other hand receive the time directly from GPS satellites. This GPS time is easily converted to UTC by NTP (GPS time is UTC – 17 seconds exactly as no leap seconds have been added.) As the GPS signal is available everywhere on the earth 24 hours a day, 365 days a week, there is never a risk of a loss of signal.
A single dedicated GPS time server can synchronize a computer network of hundreds, and even thousands of machines to within a few of milliseconds of UTC time.

How to Synchronise a Computer Network using the Time Protocol (NTP)

  |   By

Synchronisation of modern computer networks is vitally important for a multitude of reasons, and thanks to the time protocol NTP (Network Time Protocol) this is relatively straightforward.

NTP is an algorithmic protocol that analyses the time on different computers and compares it to a single time reference and adjusts each clock for drift to ensure synchronisation with the time source. NTP is so capable at this task that a network synchronised using the protocol can realistically obtain millisecond accuracy.

Choosing the time source

When it comes to establishing a time reference there really is no alternative than to find a source of UTC (Coordinated Universal Time). UTC is the global timescale, used throughout the world as a single timescale by computer networks. UTC is kept accurate by a constellation of atomic clocks throughout the world.

Synchronising to UTC

The most basic method of receiving a UTC Time source is to use a stratum 2 internet time server. These are deemed stratum 2 as they distribute the time after first receiving it from a NTP server (stratum 1) that is connected to an atomic clock (stratum 0). Unfortunately this is not the most accurate method of receiving UTC because of the distance the data has to travel from host to the client .

There are also security issues involved in using an internet stratum 2 time source in that the firewall UDP port 123 has to be left open to receive the time code but this firewall opening can, and has been, exploited by malicious users.

Dedicated NTP Servers

Dedicated NTP time servers, often referred to as network time servers, are the most accurate and secure method of synchronising a computer network. They operate externally to the network so there are no firewall issues. These stratum 1 devices receive the UTC time direct from an atomic clock source by either long wave radio transmissions or the GPS network (Global Positioning System). Whilst this does require an antenna, which in the case of GPS has to be placed on a rooftop, the time server itself will automatically synchronise hundreds and indeed thousands of different devices on the network.