Network Time Server – One Time Fits All

A network time server is responsible for ensuring that all devices on a network are synchronised to the same time. Without synchronisation problems with time sensitive applications can occur and can leave a network open to security issues and even fraud.

A network time server can synchronise a network to any timing source but to ensure security and accuracy a UTC (Coordinated Universal Time) time source is essential.

UTC was developed after the invention of the atomic clock. It is based on International Atomic Time (TAI) and Greenwich Mean Time (GMT). After atomic clocks were developed and the accuracy of a few nanoseconds that they can maintain it was discovered that the Earth was not as reliable in its rotation as the clocks.

UTC allows for the adding of leap seconds (and potential subtracting of them although that hasn’t happened yet) to allow UTC time to match up with GMT. If these leap seconds were not added then eventual day would creep into night (albeit in several millennia)

There are several possible sources for a UTC time source. Either the Internet, although these sources vary in accuracy and are not secure, the GPS network (Global Positioning System) through a roof mounted aerial or a national time and frequency transmission that are broadcast throughout several countries including the US, UK, Germany, France and Japan.

A network time server uses the protocol NTP (Network Time Protocol) to synchronise devices to UTC. NTP works by accounting for drift on the system clock and then adding or subtracting time depending on the difference. By utilising a network time server that uses a timing source from either the GPS network or radio transmission millisecond and even nanosecond accuracy to UTC is possible.

This entry was posted in [New]. Bookmark the permalink.

Leave a Reply