Origin of Synchronisation (Part 2)

  |   By

Continued…

Most towns and cities would have a main clock, such as Big Ben in London, and for those living near-by, it was fairly easy to look out the window and adjust the office or factory clock to ensure synchronicity; however, for those not in view of these tower clocks, other systems were used.

Commonly, somebody with a pocket watch would set the time by the tower clock in the morning and then go around businesses and for a small fee, let people know exactly what the time was, thus enabling them to adjust the office or factory clock to suit.

When, however, the railways began, and timetables became important it was clear a more accurate method of time keeping was needed, and it was then that the first official time-scale was developed.

As clocks were still mechanical, and therefore inaccurate and prone to drift, society again turned to that more accurate chronometer, the sun.

It was decided that when the sun was directly above a certain location, that would signal noon on this new time-scale. The location: Greenwich, in London, and the time-scale, originally called railway time, eventually became Greenwich Meantime (GMT), a time-scale that was used until the 1970’s.

Now of course, with atomic clocks, time is based on an international time-scale UTC (Coordinated Universal Time) although its origins are still based on GMT and often UTC is still referred to as GMT.

Now with the advent of international trade and global computer networks, UTC is used as the basis of nearly all international time. Computer networks deploy NTP servers to ensure that the time on their networks are accurate, often to a thousandth of a second to UTC, which means all around the world computers are ticking with the same accurate time – whether it is in London, Paris, or New York, UTC is used to ensure that computers everywhere can accurately communicate with each other, preventing the errors that poor time synchronisation can cause.

Origin of Synchronisation (Part 1)

  |   By

Part One

With modern NTP servers (Network Time Protocol) synchronisation is made easy. By receiving a signals from GPS or radio signals such as MSF or WWVB, computer networks consisting of hundreds of machines can easily be synchronised together, ensuring trouble free networking and accurate time-stamping.

Modern NTP time servers are reliant on atomic clocks, accurate to billions of parts of a second, but atomic clocks have only been around for the last sixty years and synchronisation has not always been so easy.

In the early days of chronology, clocks mechanical in nature, were not very accurate at all. The first time-pieces could drift by up to an hour a day so the time could differ from town clock to town clock, and most people in the agricultural based society regarded them as a novelty, relying in stead on sunrise and sunset to plan their days.

However, following the industrial revolution, commerce became more important to society and civilisation, and with it, the need to know what the time was; people needed to know when to go to work, when to leave and with the advent of railways, accurate time became even more crucial.

In the early days if industry, workers were often woken for work by people paid to wake them up. Known as ‛knocker-uppers.’ Relying on the factory time-peice, they would go around town and tap on people’s windows, alerting them to the start of the day, and the factory hooters signalled the beginning and end of shifts.

However, as commerce developed time became even more crucial, but as it would take another century or so for more accurate timepieces to develop (until at least the invention of electronic clocks), other methods were developed.

To follow…

MSF Downtime No Signal 26th and 27th July

  |   By

The UK’s time and frequency signal MSF, provided by the National Physical Laboratory out of Cumbria, will be down for essential maintenance on 26 and 27 July.

The unplanned downtime is to allow essential maintenance to be carried out in safety. The MSF transmitter will stop broadcasting the MSF signal on 26 and 27 July between 08.00 and 20.00 (BST – 07:00 GMT/UTC) although it is possible the maintenance may be finished ahead of schedule in which case the signal will be turned on earlier.

Future maintenance is scheduled for the following times when the signal will also be turned off:

• 9 September 2010 from 10:00 BST to 14:00 BST
• 9 December 2010 from 10:00 UTC to 14:00 UTC
• 10 March 2011 from 10:00 UTC to 14:00 UTC

Problems for Time Synchronisation

Generally, most NTP time servers should be able to maintain a stable time during these brief outages and users of MSF time synchronisation devices should not experience any difficulties with the lack of MSF signal.

However, those users who require high levels of accuracy and reliability and find the MSF outages affect them should perhaps look to a GPS NTP server.

GPS time servers receive their time signals from the GPS network which is available 24 hours a day, 365 days a year and never experiences any outages.

MSF Downtime – No Signal 26/27 July

NTP Time Servers Keeping Technology Precise

  |   By

Atomic clocks are much underrated technologies their development has revolutionised the way we live and work and has made possible technologies that would be impossible without them.

Satellite navigation, mobile phones, GPS, the internet, air traffic control, traffic lights and even CCTV cameras are reliant on the ultra precise timekeeping of an atomic clock.

The accuracy of an atomic clock is incomparable to other time keeping devices as they don’t drift by even a second in hundreds of thousands of years.

But atomic clocks are large sensitive devices that need team of experienced technicians and optimum conditions such as those found in a physics laboratory. So how do all these technologies benefit from the high precision of an atomic clock?

The answer is quite simple, the controllers of atomic clocks, usually national physics laboratories, broadcast via long wave radio the time signals that their ultra precise clocks produce.

To receive these time signals, servers that use the time synchronization protocol NTP (Network Time Protocol) are employed to receive and distribute these timestamps.

NTP time servers, often referred to as network time servers, are a secure and accurate method of ensuring any technology is running accurate atomic clocks time. These time synchronization devices can synchronise single devices or entire networks of computers, routers and other devices.

NTP servers that use GPS signals to receive the time from the atomic clock satellites are also commonly used. These NTP GPS time servers are as accurate as those that receive the time from physics laboratories but use the weaker, line of sight GPS signal as their source.

Quantum Atomic Clocks The precision of the future

  |   By

The atomic clock is not a recent invention. Developed in the 1950’s, the traditional caesium based atomic clock has been providing us with accurate time for half a century.

The caesium atomic clock has become the foundation of our time – literally. The International System of Units (SI) define a second as a certain number of oscillations of the atom caesium and atomic clocks govern many of the technologies that we live with an use on a daily basis: The internet, satellite navigation, air traffic control and traffic lights to name but a few.

However, recent developments in optical quantum clocks that use single atoms of metals like aluminium or strontium are thousands of times more accurate than traditional atomic clocks. To put this in perspective, the best caesium atomic clock as used by institutes like NIST (National Institute for Standards and Time) or NPL (National Physical Laboratory) to govern the world’s global timescale UTC (Coordinated Universal Time), is accurate to within a second every 100 million years. However, these new quantum optical clocks are accurate to a second every 3.4 billion years – almost as long as the earth is old.

For most people, their only encounter with an atomic clock is receiving its time signal is a network time server or NTP device (Network Time Protocol) for the purposes of synchronising devices and networks and these atomic clock signals are generated using caesium clocks.

And until the world’s scientists can agreed on a single atom to replace caesium and a single clock design for keeping UTC, none of us will be able to take advantage of this incredible accuracy.

Atomic Clock to be attached to International Space Station

  |   By

One of the world’s most accurate atomic clocks is to be launched into orbit and attached to the International Space Station (ISS) thanks to an agreement signed by the French space agency.

The PHARAO (Projet d’Horloge Atomique par Refroidissement d’Atomes en Orbite) atomic clock is to attached to the ISS in an effort to more accurately test Einstein’s theory of relatively as well as increasing the accuracy of Coordinated Universal Time (UTC) amongst other geodesy experiments.

PHARAO is a next generation caesium atomic clock with an accuracy that corresponds to less than a second’s drift every 300,000 years. PHARAO is to be launched by the European Space Agency (ESA) in 2013.

Atomic clocks are the most accurate timekeeping devices available to mankind yet they are susceptible to changes in gravitational pull, as predicted by Einstein’s theory, as time itself is slewed by the Earth’s pull. By placing this accurate atomic clock into orbit the effect of Earth’s gravity is lessened allowing PHARAO to be more accurate than Earth based clock.

While atomic clocks are not new to orbit, as many satellites; including the GPS network (Global Positioning System) contain atomic clocks, however, PHARAO will be among the most accurate clocks ever launched into space, allowing it to be used for far more detailed analysis.

Atomic clocks have been around since the 1960’s but their increasing development has paved the way for more and more advanced technologies. Atomic clocks form the basis of many modern technologies from satellite navigation to allowing computer networks to communicate effectively across the globe.

Computer networks receive time signals from atomic clocks via NTP time servers (Network Time Protocol) which can accurately synchronise a computer network to within a few milliseconds of UTC.

The Way an Atomic Clock Works

  |   By

Atomic clocks are the most accurate chronometers we have. They are millions of times more accurate than digital clocks and can keep time for hundreds of millions of years without losing as much as a second. Their use has revolutionised the way we live and work and they have enabled technologies such as satellite navigation systems and global online commerce.

But how do they work? Strangely enough, atomic clocks work in the same way as ordinary mechanical clocks. But rather than have a coiled spring and mass or pendulum they use the oscillations of atoms. Atomic clocks are not radioactive as they do not rely on atomic decay instead they rely on the tiny vibrations at certain energy levels (oscillations) between the nucleus of an atom and the surrounding electrons.

When the atom receives microwave energy at exactly the right frequency, it changes energy state, this state is constant an unchanging and the oscillations can be measured just like the ticks of a mechanical clock. However, while mechanical clocks tick every second, atomic clocks ‘tick’ several billion times a second. In the case of caesium atoms, most commonly used in atomic clocks, they tick 9,192,631,770 per second – which is now the official definition of a second.

Atomic clocks now govern the entire global community as a universal timescale UTC (Coordinated Universal Time) based on atomic clock time has been developed to ensure synchronization. UTC atomic clock signals can be received by network time servers, often referred to as NTP Servers, that can synchronize computer networks to within a few milliseconds of UTC.

Seven Reasons why your Network needs a Time Server

  |   By

Time servers, often referred to as NTP time servers after the protocol (Network Time Protocol) used to distribute time are an increasingly important part of any computer network. The NTP server receives a timing signal from an accurate source (such as an atomic clock) and then distributes it to all devices on the network.

However, despite the increasing importance of these time synchronisation devices, many network administrators still fail to accurately synchronise their networks and can leave their entire computer system vulnerable.

Here are seven reasons why a NTP time server is a crucial piece of equipment for YOUR network:

• Security: NTP servers use an external source of time and don’t rely on an open firewall port. An unsynchronized server will also be vulnerable to malicious users who can take advantage of time differences.

• Error logging: failing to adequately synchronize a computer network may mean that it is near impossible to trace errors or malicious attack, especially if the times on the log files from different machine do not match.

• Legal Protection: Not being able to prove the time can have legal implications if somebody has committed fraud or other illegal activity against your company.

• Accuracy: NTP Time Servers ensure that all networked computers are synchronized automatically to the exact time throughout your network so everybody in your company can have access to the exact time.

• Global Harmony: A global timescale known as UTC (Coordinated Universal Time) has been developed to ensure that systems across the globe can run the exact same time. By utilising a NTP server not only will every device on you network be synchronised together but your network will be synchronised with every other network on Earth that is hooked up to UTC.

• Control: With a NTP server you have control of the configuration. You can allow automatic changes each spring and autumn for daylight saving time or set your server time to be locked to UTC time only – or indeed, any time zone you choose.

• Automatic update of time. No user intervention required, a NTP time server will account for leap seconds and time zones ensuring trouble free synchronisation.

Parking Tickets and the NTP Server

  |   By

There is nothing worse than returning to your car only to discover that your parking meter time limit has expired and you’ve got a parking ticket slapped on to your windscreen.

More-often-than-not it’s only a matter of being a couple of minutes late before an over eager parking attendant spots your expired meter or ticket and issues you a fine.

However, as the people of Chicago are discovering, whilst a minute may be the difference between getting back to the car in time or receiving a ticket, a minute may also be the difference between different parking meters.

It seems the clocks on the 3000 new parking meter pay boxes in Cale, Chicago have been discovered to be unsynchronized. In fact, of the nearly 60 pay boxes observed, most are off at least a minute and in some cases, nearly 2 minutes from what is “actual” time.

This has posed a headache to the firm in charge of parking in the Cale district and they could face legal challenges from the thousands of motorists that have been given tickets from these machine.

The problem with the Cale parking system is that while they claim they regularly calibrate their machine there is no accurate synchronization to a common time reference. In most modern applications UTC (Coordinated Universal Time) is used as a base timescale and to synchronize devices, like Cale’s parking meters, a NTP server, linked to an atomic clock will receive UTC time and ensure every device has the exact time.

NTP servers are used in the calibration of not just parking meters but also traffic lights, air traffic control and the entire banking system to name but a few applications and can synchronize every device connected to it to within a few milliseconds of UTC.

It’s a shame Cale’s parking attendants didn’t see the value of of a dedicated NTP time server – I’m sure they are regretting not having one now.

Configuring a Network to use a NTP Server Part two: Distributing the Time

  |   By

NTP (Network Time Protocol) is the protocol designed for time distribution amongst a network. NTP is hierarchical. It organises a network into strata, which are the distance from a clock source and the device.

A dedicated NTP server that receives the time from a UTC source such as GPS or the national time and frequency signals is regarded as a stratum 1 device. Any device that is connected to a NTP server becomes a stratum 2 device and devices farther down the chain become stratum 2, 3 and so on.

Stratum layers exist to prevent cyclical dependencies in the hierarchy. But the stratum level is not an indication of quality or reliability.

NTP checks the time on all devices on the network it then adjusts the time according to how much drift it discovers. Yet NTP goes further than just checking the time on a the reference clock, the NTP program exchanges time information by packets (blocks of data) but refuses to believe the time it is told until several exchanges have taken place, each passing a set of tests known asprotocol specifications. It often takes about five good samples until a NTP server is accepted as a timing source.

NTP uses timestamps to represent the current time the day. As time is linear, each timestamp is always greater than the previous one. NTP timestamps are in two formats but they relay the seconds from a set point in time (known as the prime epoch, set at 00:00 1 January 1900 for UTC) The NTP algorithm then uses this timestamp to determine the amount to advance or retreat the system or network clock.

NTP analyses the timestamp values including the frequency of errors and the stability. A NTP server will maintain an estimate of the quality of both its reference clocks and itself.