The white paper discusses precision clock synchronization using IEEE 1588 (Precision Time Protocol, or PTP). PTP allows distributed clocks connected via Ethernet networks to synchronize with sub-microsecond accuracy. It describes PTP's applications in automation, measurement, and other fields. PTP achieves high accuracy through boundary clocks in switches, hardware time stamping, and two-way delay measurement between master and slave clocks. Accuracies below 100 nanoseconds have been achieved in tests.
This document discusses using IEEE 1588 Precision Time Protocol (PTP) for time synchronization in power substations and smart grids. It recommends having a timing strategy that uses PTP according to defined profiles like IEEE C37.238 for power systems. This provides more accurate time synchronization than older methods like IRIG-B, with redundancy and management capabilities. The document also warns that relying solely on GPS for timing leaves systems vulnerable and that a single timing solution will not scale for power grids of the future.
The document summarizes precision time synchronization techniques. It begins with an overview of time synchronization and its applications in fields like industrial automation, stock trading, and cloud computing. It then provides details on IEEE 1588, including its objectives to achieve sub-microsecond synchronization across networked devices and support for heterogeneous clock systems. The document discusses PTP communication ports, roles, and the Best Master Clock Algorithm for determining roles. It also outlines PTP message types and how hardware-assisted time stamping increases accuracy. Lastly, it promotes participation in the 2012 International Symposium on Precision Clock Synchronization for Measurement, Control and Communication.
Getting clocks to agree on the time is tricky. Getting them to agree on the time better than 100 nanoseconds is even trickier.
In this talk I will provide an introduction to the basic principles of the Precision Time Protocol (PTP) and how it can be used to precisely synchronize computers over a LAN.
http://www.nycbug.org/index.cgi?action=view&id=10361
IEEE 1588 Timing for Mobile Backhaul webinar sponsored by Cisco. By 2015 there will be 5 billion mobile devices and 1.5 billion M2M nodes. Global mobile traffic will grow 26 times to 6.3 exabytes per month. Video will make up 66% of mobile traffic. Ethernet backhaul costs less per bit than TDM and has a flat cost structure. Mobile networks are transforming from linear TDM architectures to distributed IP/Ethernet architectures to scale with demand. Migration to Ethernet requires time synchronization which can be achieved using 1588v2 and SyncE technologies. 1588v2 supports both frequency and phase synchronization required for 4G/LTE networks.
This document provides an overview of IEEE 1588 precision time protocol (PTP). It describes IEEE 1588-2002 and 1588-2008 standards, including clock types, message types, best master clock algorithm, and synchronization methods. It also discusses message transport and some open source software implementations of PTP on Linux.
IEEE Standard 1588 defines the Precision Time Protocol (PTP) to synchronize clocks over packet networks. PTP is needed for applications that require precise timing such as Time Division Multiplexing (TDM) over IP. PTP uses network messages and timestamps to synchronize slave clocks to a master clock with nanosecond precision. PTP messages include sync, delay request, follow up, and delay response. Hardware time stamping is often required to achieve high precision with low delay and jitter. PTP is a cheaper and more scalable solution than alternatives like GPS or atomic clocks for synchronizing networks to within 50 parts per billion.
High Definition On MPEG In Internet Protocol (Wbm Comments)Kelly Daniels
The document discusses considerations for transporting high definition video over IP networks using MPEG encoding. It notes that IP networks have struggled with inter-packet jitter, which is a bigger problem for high definition video than standard definition. The presentation will look at solutions for meeting jitter requirements in network elements, operations systems, and the costs of doing so.
The document discusses technologies for improving jitter for broadcaster content delivery over broadband networks. It summarizes that IEEE 1588 Grandmaster and Slave Clock and RTP are still solutions for multicast video transport. It also discusses Precision Timing Protocol versus Synchronized Ethernet and developments in their adoption. Recent test results showed that HD video in MPEG-4 at 8-10 Mbps performs similarly to MPEG-2, and at 18 Mbps is comparable to SD in MPEG-2. Future work on incorporating carrier grade synchronization into IP is suspended.
This document discusses using IEEE 1588 Precision Time Protocol (PTP) for time synchronization in power substations and smart grids. It recommends having a timing strategy that uses PTP according to defined profiles like IEEE C37.238 for power systems. This provides more accurate time synchronization than older methods like IRIG-B, with redundancy and management capabilities. The document also warns that relying solely on GPS for timing leaves systems vulnerable and that a single timing solution will not scale for power grids of the future.
The document summarizes precision time synchronization techniques. It begins with an overview of time synchronization and its applications in fields like industrial automation, stock trading, and cloud computing. It then provides details on IEEE 1588, including its objectives to achieve sub-microsecond synchronization across networked devices and support for heterogeneous clock systems. The document discusses PTP communication ports, roles, and the Best Master Clock Algorithm for determining roles. It also outlines PTP message types and how hardware-assisted time stamping increases accuracy. Lastly, it promotes participation in the 2012 International Symposium on Precision Clock Synchronization for Measurement, Control and Communication.
Getting clocks to agree on the time is tricky. Getting them to agree on the time better than 100 nanoseconds is even trickier.
In this talk I will provide an introduction to the basic principles of the Precision Time Protocol (PTP) and how it can be used to precisely synchronize computers over a LAN.
http://www.nycbug.org/index.cgi?action=view&id=10361
IEEE 1588 Timing for Mobile Backhaul webinar sponsored by Cisco. By 2015 there will be 5 billion mobile devices and 1.5 billion M2M nodes. Global mobile traffic will grow 26 times to 6.3 exabytes per month. Video will make up 66% of mobile traffic. Ethernet backhaul costs less per bit than TDM and has a flat cost structure. Mobile networks are transforming from linear TDM architectures to distributed IP/Ethernet architectures to scale with demand. Migration to Ethernet requires time synchronization which can be achieved using 1588v2 and SyncE technologies. 1588v2 supports both frequency and phase synchronization required for 4G/LTE networks.
This document provides an overview of IEEE 1588 precision time protocol (PTP). It describes IEEE 1588-2002 and 1588-2008 standards, including clock types, message types, best master clock algorithm, and synchronization methods. It also discusses message transport and some open source software implementations of PTP on Linux.
IEEE Standard 1588 defines the Precision Time Protocol (PTP) to synchronize clocks over packet networks. PTP is needed for applications that require precise timing such as Time Division Multiplexing (TDM) over IP. PTP uses network messages and timestamps to synchronize slave clocks to a master clock with nanosecond precision. PTP messages include sync, delay request, follow up, and delay response. Hardware time stamping is often required to achieve high precision with low delay and jitter. PTP is a cheaper and more scalable solution than alternatives like GPS or atomic clocks for synchronizing networks to within 50 parts per billion.
High Definition On MPEG In Internet Protocol (Wbm Comments)Kelly Daniels
The document discusses considerations for transporting high definition video over IP networks using MPEG encoding. It notes that IP networks have struggled with inter-packet jitter, which is a bigger problem for high definition video than standard definition. The presentation will look at solutions for meeting jitter requirements in network elements, operations systems, and the costs of doing so.
The document discusses technologies for improving jitter for broadcaster content delivery over broadband networks. It summarizes that IEEE 1588 Grandmaster and Slave Clock and RTP are still solutions for multicast video transport. It also discusses Precision Timing Protocol versus Synchronized Ethernet and developments in their adoption. Recent test results showed that HD video in MPEG-4 at 8-10 Mbps performs similarly to MPEG-2, and at 18 Mbps is comparable to SD in MPEG-2. Future work on incorporating carrier grade synchronization into IP is suspended.
This document provides an overview of the PTP Telecom Profile for Frequency Synchronization (G.8265.1). It defines key aspects of the profile including its objectives to enable frequency distribution over packet networks, use of unicast messaging, support for traceability of timing sources, and master selection and protection schemes aligned with telecom network practices. The profile tailors PTP to meet timing accuracy needs for telecom applications over managed packet networks.
In Service Monitoring and Assurance at ITSF 2014 ADVA
1) Synchronization assurance is important for mobile backhaul networks to ensure synchronization quality as network conditions can affect timing.
2) In-service monitoring tools are needed to continuously monitor synchronization sources and the network to detect errors early, as using lab equipment for each location is too expensive.
3) Examples of in-service monitoring include monitoring a slave clock against GNSS while it is available, then against the secondary source; and monitoring boundary clocks and the network connecting synchronization sources.
The ability to synchronise security equipment is becoming ever more important. This is not only for ensuring consistency, but also for evidential purposes.
1) IEEE 1588 is a standard protocol that enables precise time synchronization of networked devices over Ethernet at the sub-microsecond level.
2) It works by having one device act as the master clock that synchronizes the time of all other slave devices by exchanging time synchronization messages.
3) Many industrial automation companies are adopting IEEE 1588 to enable real-time deterministic applications that require highly synchronized networked devices.
Machine Learning Based Session Drop Prediction in LTE Networks and its SON As...Ericsson
Abnormal bearer session release (i.e. bearer session drop) in cellular telecommunication networks may seriously impact the quality of experience of mobile users. The latest mobile technologies enable high granularity real-time reporting of all conditions of individual sessions, which gives rise to use data analytics methods to process and monetize this data for network optimization. One such example for analytics is Machine Learning (ML) to predict session drops well before the end of session.
The document discusses network time servers and synchronization. It describes how most electronic clocks in devices are inaccurate and drift over time, causing issues for file systems, billing, security, and more. It recommends using a dedicated time server running NTP behind a firewall to provide the most accurate and secure synchronization for a local network. It also discusses Meinberg as a leading manufacturer of NTP servers and their LANTIME M1000 time and frequency synchronization platform.
This document discusses several proposed solutions for getting data from a wireless sensor network gateway with no internet connection to a remote repository that does have internet access. It describes experiments testing RadioTFTP, RadioTunnel, and Soundmodem protocols over UHF frequencies. The results show that RadioTFTP has the highest throughput but other solutions may be preferable depending on requirements like easy setup or standardization. Future work could improve RadioTFTP queues and timers or move Soundmodem to use Radiometrix devices.
Arduino microcontroller and nRF24L01+ transceiversPavlos Kallis
This document describes the implementation of a wireless sensor network using Arduino microcontrollers and nRF24L01+ radio transceivers. It discusses how the nodes in the network receive sensor measurements and forward them to a central node. It provides details on the Arduino Leonardo microcontroller and nRF24L01+ transceiver specifications, including data rates, frequency range, and modulation used. It also describes the RF24 library for communicating between transceivers and proposes a mechanism for packet retransmission with randomized backoff to avoid collisions.
The DTS 4138.timeserver is a precise time server and master clock that can synchronize devices over NTP, serial outputs, and pulse/frequency outputs. It offers high redundancy through dual power supplies, fiber optic synchronization between servers, and multiple time/communication outputs. It provides accurate time synchronization down to 10 microseconds for LAN devices, processes, and systems.
The document describes the design and implementation of a new high performance data transport protocol called UDT. UDT is implemented at the application layer over UDP to provide reliable, high-speed data transfer capabilities. It includes a new congestion control algorithm based on AIMD with decreasing increases that aims for efficiency, fairness and friendliness. Experimental results show UDT achieves high throughput and good fairness compared to TCP. The document also introduces a configurable framework called Composable UDT that allows new congestion control algorithms to be easily implemented and evaluated.
Essentials of jitter part 1 The Time Interval Error: TIEteledynelecroy
This document discusses jitter and its measurement. Jitter is measured as the time interval error (TIE) between the actual and expected arrival times of signal edges. TIE values over time form the TIE track waveform, which can be analyzed statistically, in the frequency domain, and through histograms to identify different jitter sources. Proper jitter measurement requires determining the expected edge times, which may involve clock data recovery for signals without a reference clock.
USB 3.1 Gen 2 Compliance Testing and Debug Webinarteledynelecroy
Join Teledyne LeCroy for this free webinar as we analyze the major changes in the standard compared to its previous versions and offer solutions for compliance testing and debug to help in analysis and characterization of USB 3.1 Gen 2 signals and interfaces.
Practical issues to be considered in PHY layer of 802.11 standard specEalwan Lee
This document discusses practical issues to consider in the PHY layer of 802.11 standards, including: multi-station scenarios of peak-to-peak packet swings and SIFS spaced sequences, ACS issues, imperfect transmitter quality like RF turn-on time and preamble EVM not tested in equipment, stress testing packet headers, and changes from 802.11-2012 to 802.11-2016 removing PMD/PLCP concepts. It concludes some imperfections are possible within standard specifications due to the uncoordinated ISM band, and proprietary features can disadvantage followers.
ContikiMAC : Radio Duty Cycling ProtocolSalah Amean
ContikiMAC is a radio duty cycling protocol that uses periodic wake-ups to listen for packet transmissions from neighbors. It keeps the radio on only when needed to receive packets, sending acknowledgments and retransmitting packets as necessary. The timing of transmissions and wake-ups is precise to enable efficient communication while minimizing energy usage. Phase awareness allows senders to transmit packets just before expected receiver wake-ups. ContikiMAC is implemented using real-time timers in Contiki to ensure stable and accurate timing.
In this slide deck we cover:
- Understanding the relationship between OFDM theory and practice
- Starting from a Matlab script through to automatic HDL code/bitstream generation
- Introduction to Nutaq’s PicoSDR hardware and software
- Creating host applications to exchange data with the PicoSDR in real-time
Network time sync for power generation, transmission and distributionMohd Amir
Meinberg offers solutions for synchronizing networks in power generation, transmission and distribution systems. Their products include NTP servers, frequency monitors, GPS clocks, and modular synchronization platforms that provide accurate timing via satellite receivers, radio clocks, and network time protocol. The solutions synchronize IT networks, reliably monitor power line frequency, and ensure accurate frequency control critical to preventing outages in power systems.
Clock jitter refers to the timing variations of signal edges from their ideal positions. It is typically caused by noise or disturbances in a system. The main sources of jitter include thermal noise, power supply variations, loading conditions, device noise, and interference. Jitter can be measured and expressed in terms of RMS, spectral density, picoseconds, or Unit Intervals. There are different types of jitter including period jitter, cycle-to-cycle jitter, long-term jitter, phase jitter, and time interval error.
The document summarizes the UDT protocol, which is a high performance transport protocol designed for data-intensive applications over high-speed networks. It discusses the limitations of TCP for these applications and high bandwidth-delay product networks. It then provides an overview of the design and implementation of the UDT protocol, including its congestion control algorithm, APIs, and composable framework. It evaluates UDT's performance in terms of efficiency, fairness, and stability compared to TCP. The goal of UDT is to enable efficient, fair, and friendly transport of data for distributed applications over high-speed networks.
WaveGuru is a software defined radio platform and test and measurement tool that can be programmed to transmit and receive different waveforms. It supports standards like GSM, WCDMA, WiMAX, LTE and LTE-Advanced. It provides signal generation and analysis capabilities. WaveGuru also supports concepts like cognitive radio and can avoid the need to carry multiple radios. It is suited for defense, manufacturing, research and academics for tasks like protocol testing, research projects and lab experiments.
This document describes the implementation of a lock-in amplifier using LabVIEW software and a data acquisition board. A lock-in amplifier can measure very small input signals even in the presence of noise much larger than the signal. It works by multiplying the input signal with a reference signal and then filtering out signals at all frequencies other than the reference frequency. The implemented lock-in amplifier uses a National Instruments DAQ card and pre-amplifier to digitize and process signals on a computer running LabVIEW. It is shown to be effective at measuring low-level signals and analyzing their amplitude and phase characteristics.
Telecordia NIST/WSTS Workshop: Mobile Backhaul SynchronizationADVA
Check out the Mobile Backhaul Synchronization slides that Gil Biran will be presenting at this week's Telecordia NIST/WSTS workshop in San Jose, California
This document provides an overview of the PTP Telecom Profile for Frequency Synchronization (G.8265.1). It defines key aspects of the profile including its objectives to enable frequency distribution over packet networks, use of unicast messaging, support for traceability of timing sources, and master selection and protection schemes aligned with telecom network practices. The profile tailors PTP to meet timing accuracy needs for telecom applications over managed packet networks.
In Service Monitoring and Assurance at ITSF 2014 ADVA
1) Synchronization assurance is important for mobile backhaul networks to ensure synchronization quality as network conditions can affect timing.
2) In-service monitoring tools are needed to continuously monitor synchronization sources and the network to detect errors early, as using lab equipment for each location is too expensive.
3) Examples of in-service monitoring include monitoring a slave clock against GNSS while it is available, then against the secondary source; and monitoring boundary clocks and the network connecting synchronization sources.
The ability to synchronise security equipment is becoming ever more important. This is not only for ensuring consistency, but also for evidential purposes.
1) IEEE 1588 is a standard protocol that enables precise time synchronization of networked devices over Ethernet at the sub-microsecond level.
2) It works by having one device act as the master clock that synchronizes the time of all other slave devices by exchanging time synchronization messages.
3) Many industrial automation companies are adopting IEEE 1588 to enable real-time deterministic applications that require highly synchronized networked devices.
Machine Learning Based Session Drop Prediction in LTE Networks and its SON As...Ericsson
Abnormal bearer session release (i.e. bearer session drop) in cellular telecommunication networks may seriously impact the quality of experience of mobile users. The latest mobile technologies enable high granularity real-time reporting of all conditions of individual sessions, which gives rise to use data analytics methods to process and monetize this data for network optimization. One such example for analytics is Machine Learning (ML) to predict session drops well before the end of session.
The document discusses network time servers and synchronization. It describes how most electronic clocks in devices are inaccurate and drift over time, causing issues for file systems, billing, security, and more. It recommends using a dedicated time server running NTP behind a firewall to provide the most accurate and secure synchronization for a local network. It also discusses Meinberg as a leading manufacturer of NTP servers and their LANTIME M1000 time and frequency synchronization platform.
This document discusses several proposed solutions for getting data from a wireless sensor network gateway with no internet connection to a remote repository that does have internet access. It describes experiments testing RadioTFTP, RadioTunnel, and Soundmodem protocols over UHF frequencies. The results show that RadioTFTP has the highest throughput but other solutions may be preferable depending on requirements like easy setup or standardization. Future work could improve RadioTFTP queues and timers or move Soundmodem to use Radiometrix devices.
Arduino microcontroller and nRF24L01+ transceiversPavlos Kallis
This document describes the implementation of a wireless sensor network using Arduino microcontrollers and nRF24L01+ radio transceivers. It discusses how the nodes in the network receive sensor measurements and forward them to a central node. It provides details on the Arduino Leonardo microcontroller and nRF24L01+ transceiver specifications, including data rates, frequency range, and modulation used. It also describes the RF24 library for communicating between transceivers and proposes a mechanism for packet retransmission with randomized backoff to avoid collisions.
The DTS 4138.timeserver is a precise time server and master clock that can synchronize devices over NTP, serial outputs, and pulse/frequency outputs. It offers high redundancy through dual power supplies, fiber optic synchronization between servers, and multiple time/communication outputs. It provides accurate time synchronization down to 10 microseconds for LAN devices, processes, and systems.
The document describes the design and implementation of a new high performance data transport protocol called UDT. UDT is implemented at the application layer over UDP to provide reliable, high-speed data transfer capabilities. It includes a new congestion control algorithm based on AIMD with decreasing increases that aims for efficiency, fairness and friendliness. Experimental results show UDT achieves high throughput and good fairness compared to TCP. The document also introduces a configurable framework called Composable UDT that allows new congestion control algorithms to be easily implemented and evaluated.
Essentials of jitter part 1 The Time Interval Error: TIEteledynelecroy
This document discusses jitter and its measurement. Jitter is measured as the time interval error (TIE) between the actual and expected arrival times of signal edges. TIE values over time form the TIE track waveform, which can be analyzed statistically, in the frequency domain, and through histograms to identify different jitter sources. Proper jitter measurement requires determining the expected edge times, which may involve clock data recovery for signals without a reference clock.
USB 3.1 Gen 2 Compliance Testing and Debug Webinarteledynelecroy
Join Teledyne LeCroy for this free webinar as we analyze the major changes in the standard compared to its previous versions and offer solutions for compliance testing and debug to help in analysis and characterization of USB 3.1 Gen 2 signals and interfaces.
Practical issues to be considered in PHY layer of 802.11 standard specEalwan Lee
This document discusses practical issues to consider in the PHY layer of 802.11 standards, including: multi-station scenarios of peak-to-peak packet swings and SIFS spaced sequences, ACS issues, imperfect transmitter quality like RF turn-on time and preamble EVM not tested in equipment, stress testing packet headers, and changes from 802.11-2012 to 802.11-2016 removing PMD/PLCP concepts. It concludes some imperfections are possible within standard specifications due to the uncoordinated ISM band, and proprietary features can disadvantage followers.
ContikiMAC : Radio Duty Cycling ProtocolSalah Amean
ContikiMAC is a radio duty cycling protocol that uses periodic wake-ups to listen for packet transmissions from neighbors. It keeps the radio on only when needed to receive packets, sending acknowledgments and retransmitting packets as necessary. The timing of transmissions and wake-ups is precise to enable efficient communication while minimizing energy usage. Phase awareness allows senders to transmit packets just before expected receiver wake-ups. ContikiMAC is implemented using real-time timers in Contiki to ensure stable and accurate timing.
In this slide deck we cover:
- Understanding the relationship between OFDM theory and practice
- Starting from a Matlab script through to automatic HDL code/bitstream generation
- Introduction to Nutaq’s PicoSDR hardware and software
- Creating host applications to exchange data with the PicoSDR in real-time
Network time sync for power generation, transmission and distributionMohd Amir
Meinberg offers solutions for synchronizing networks in power generation, transmission and distribution systems. Their products include NTP servers, frequency monitors, GPS clocks, and modular synchronization platforms that provide accurate timing via satellite receivers, radio clocks, and network time protocol. The solutions synchronize IT networks, reliably monitor power line frequency, and ensure accurate frequency control critical to preventing outages in power systems.
Clock jitter refers to the timing variations of signal edges from their ideal positions. It is typically caused by noise or disturbances in a system. The main sources of jitter include thermal noise, power supply variations, loading conditions, device noise, and interference. Jitter can be measured and expressed in terms of RMS, spectral density, picoseconds, or Unit Intervals. There are different types of jitter including period jitter, cycle-to-cycle jitter, long-term jitter, phase jitter, and time interval error.
The document summarizes the UDT protocol, which is a high performance transport protocol designed for data-intensive applications over high-speed networks. It discusses the limitations of TCP for these applications and high bandwidth-delay product networks. It then provides an overview of the design and implementation of the UDT protocol, including its congestion control algorithm, APIs, and composable framework. It evaluates UDT's performance in terms of efficiency, fairness, and stability compared to TCP. The goal of UDT is to enable efficient, fair, and friendly transport of data for distributed applications over high-speed networks.
WaveGuru is a software defined radio platform and test and measurement tool that can be programmed to transmit and receive different waveforms. It supports standards like GSM, WCDMA, WiMAX, LTE and LTE-Advanced. It provides signal generation and analysis capabilities. WaveGuru also supports concepts like cognitive radio and can avoid the need to carry multiple radios. It is suited for defense, manufacturing, research and academics for tasks like protocol testing, research projects and lab experiments.
This document describes the implementation of a lock-in amplifier using LabVIEW software and a data acquisition board. A lock-in amplifier can measure very small input signals even in the presence of noise much larger than the signal. It works by multiplying the input signal with a reference signal and then filtering out signals at all frequencies other than the reference frequency. The implemented lock-in amplifier uses a National Instruments DAQ card and pre-amplifier to digitize and process signals on a computer running LabVIEW. It is shown to be effective at measuring low-level signals and analyzing their amplitude and phase characteristics.
Telecordia NIST/WSTS Workshop: Mobile Backhaul SynchronizationADVA
Check out the Mobile Backhaul Synchronization slides that Gil Biran will be presenting at this week's Telecordia NIST/WSTS workshop in San Jose, California
Chapter 5 discusses synchronization in distributed systems. Synchronization mechanisms are needed to enforce correct interaction between processes that share resources and run concurrently. Clock synchronization and event ordering are important synchronization techniques. Clock synchronization aims to keep clocks across distributed nodes close together despite unpredictable delays. It can be achieved through centralized or distributed algorithms. Event ordering ensures a total order of all events in a distributed system through happened-before relations and logical clocks.
Random broadcast based distributed consensus clock synchronization for mobile...LogicMindtech Nologies
NS2 Projects for M. Tech, NS2 Projects in Vijayanagar, NS2 Projects in Bangalore, M. Tech Projects in Vijayanagar, M. Tech Projects in Bangalore, NS2 IEEE projects in Bangalore, IEEE 2015 NS2 Projects, WSN and MANET Projects, WSN and MANET Projects in Bangalore, WSN and MANET Projects in Vijayangar
This presentation discusses time synchronization and the Network Time Protocol (NTP). It provides an introduction to time synchronization, explaining that NTP is an internet standard protocol used to synchronize computer clocks over networks. It then discusses how NTP works, describing its hierarchical structure and use of UDP port 123. The presentation also covers GPS time synchronization and evaluates NTP's accuracy compared to GPS.
This document discusses synchronization in telecommunications networks. It describes:
1. The hierarchy of synchronization sources from primary reference clocks (PRCs) down to slave clocks in network elements. PRCs provide the highest level of synchronization reference signals.
2. The transport of synchronization signals along chains of synchronous digital hierarchy (SDH) network elements between synchronization supply units (SSUs). Network elements recover clocks and regenerate transport signals.
3. Requirements for avoidance of timing loops and maintenance of synchronization quality levels down the chain. Signals are squelched if quality falls below certain levels. Chains can switch to downstream synchronization under faults.
For enterprise software applications and related processes, highly accurate and synchronized time is a necessity. An inaccurate
computer clock can cause significant problems. A discrepancy of a minute or two could cause a significant and unacceptable margin of error, since many applications require that the time be kept accurate to the nearest second or less.
This document discusses timing and synchronization in digital communication systems. It explains that digital signals are transmitted as pulses or clocks, and receivers must detect these signals accurately by synchronizing to the transmitter's clock. Five methods of clock exchange are described to achieve synchronization between machines: free running, line-timed, loop-timed, external, and through-timed. Maintaining accurate synchronization is important to avoid errors that can reduce throughput or cause audible clicks in signals like voice and video.
This is the third part of the mini-series of synchronization in the Topics in Digital Communication Presentations.
Timing synchronization is another key component in modem design and implementation. However, this subject, especially its practical aspects, were not covered in details in text books. The materials covered in this presentation are not really new, but discussed in the literature published over past forty years. I hope that putting them in a single slide deck can help people who want to learn more on this subject.
Fuyun Ling
The 8284 clock generator IC provides clock signals and synchronization for the 8086/8088 microprocessors. It generates the CLK signal from either an internal crystal oscillator or external clock source. It also produces a divided PCLK signal and synchronizes the READY signal based on the RDY1 and RDY2 pins. The 8284 ensures proper reset timing for the 8086/8088 by holding the RESET signal low for at least 4 clock cycles after power on.
Synchronization and timing loop presentation -mapyourtechMapYourTech
The document discusses synchronization in telecommunications networks. It defines key terms like synchronization status message (SSM), synchronization supply unit (SSU), primary reference clock (PRC), and timing loops. It explains that synchronization is important to avoid loss of information and describes the effects of poor synchronization. Slips, which are the deletion or repetition of data blocks, are discussed as well their impact on different traffic types. Maintaining synchronization across networks is necessary to minimize slips.
Synchronization Pradeep K Sinha
Introduction
Issues in Synchronization
Clock synchronization
Event Ordering
Mutual Exclusion
Deadlock
Election algorithms
Clock Synchronization
How Computer Clocks are Implemented
Drifting of Clocks
Types of Clock Synchronization and issues in them
Clock Synchronization Algorithms
Distributed and Centralized Algorithms
Case Study
Event Ordering
Happened Before Relation
Logical Clocks Concept and Implementation
Mutual Exclusion
Centralized Approach, Distributed Approach, Token Passing Approach
Deadlocks
Election algorithms
This document discusses various topics related to synchronization in distributed systems, including distributed algorithms, logical clocks, global state, and leader election. It provides definitions and examples of key synchronization concepts such as coordination, synchronization, and determining global states. Examples of logical clock algorithms like Lamport clocks and vector clocks are provided. Challenges around clock synchronization and calculating global system states are also summarized.
Synchronisation and Time Distribution in Modern Telecommunications Networks3G4G
By Sébastien Jobert & Kenneth Hann
The past decade has witnessed a race for networks to provide ever faster communications, interconnecting people via applications used every day by billions of users. Radio spectrum utilisation and synchronisation plays a key role here. But now that Ethernet has won the bandwidth and cost per bit wars, how are base stations being synchronised today?
*** Shared with Permission from ITP Journal Volume 10 | Part 1 - 2016 ***
This document discusses the implementation and simulation of Precision Time Protocol (PTP) stacks. PTP is used to synchronize clocks over Ethernet networks with less than 1 microsecond accuracy. It works by exchanging timing messages between a master and slave clock to determine offsets. The document outlines the basic components and message types of PTP including synchronization, delay request, delay response, and boundary clocks. It also discusses analyzing network packets between the master and slave using a protocol analyzer. The goal of the research is to design an implementation of PTP that can achieve sub-microsecond accuracy on an FPGA by building the protocol stack and simulating message passing.
Design of Real-time Self Establish Wireless Sensor For Dynamic NetworkIJTET Journal
Abstract— Wireless sensor network in the recent trend engaged with high speed responsive real time system. This type of real time system requires reliable and compatible sensor to work in an environment where the sensor is dynamic in nature. Sensor network is to design to perform a set of high level information processing tasks such as detection, tracking or classification. Application of sensor networks is wide ranging and can vary significantly in application requirements, modes of deployment, sensing modality, power supply. Dynamic configuring of wireless sensor involves timing constraints to configure the sensor or to switch an adaptive sensor when working node failure due to energy, data rate, packet loss and range of the sensor. So the network, with such dynamic nature needs a background sensor which is able to be switched when the active sensor has a problem and improper functioning due to the network deploy environment. The background sensor lies inactive inside the range of the active sensor; ensure that the sensor is about to die and make sure the last data transfer successful find delay time to switch. Fault tolerance is achieved by switching the background sensor with the active sensor, where the background sensor self establish themselves in the network and perform similar routing metrics and configure them self with the network as soon they are switched. Once, the actual sensor retained back to the active condition then the background sensor will go to inactive state during this switching process the sensor will not loss data packet.
Synchronization For High Frequency Trading Networks: A How To Guidejeremyonyan
For many financial institutions, high frequency trading volume is growing at an accelerating pace and demanding new requirements on their IT infrastructure. Drivers in their business such as pricing of equities moving from decimal to penny resolution and the growing need for markets to provide improved liquidity are resulting in huge opportunities for financial gain. Taking advantage of these opportunities is, in part, dependent on the care taken in the network’s time synchronization and the management of latency. Wall Street firms who were involved in the early phases of High Frequency Trading have been early adopters of high performance timing solutions utilizing a variety of signals including GPS, IRIG, 1PPS, NTP and now the Precision Time Protocol (PTP) which allows for precision time transfer on Ethernet networks. The implementation of specific timing solutions depends on the trading infrastructure and the network topology. Through a combination of hardware, software, and careful network management, it is reasonable to expect microsecond level time-transfer from traceable time sources to Linux applications.
The document discusses Network Time Protocol (NTP). It provides details on how NTP synchronizes time across systems using a client-server model over UDP. NTP is important for applications that require accurate timekeeping to avoid errors. It has features like hierarchical architecture and redundancy. NTP has advantages like accuracy, flexibility, and security but also has disadvantages like vulnerability to attacks and complexity of configuration. The document also explains NTP stratum levels and concludes with discussing the utility of a listening bug.
Stepping up to the Challenge on Tighter Time Accuracy.3G4G
By Tommy Cook & Tim Frost
Frequency synchronisation has been important in telecoms networks ever since the 1930s when techniques such as Frequency Division Multiplexing were introduced to transmit multiple voice calls over a single cable. With the advent of digitised Time Division Multiplexing in the 1960s, it became more important to avoid “slips”, where data is lost because the transmit and receive clocks are running at different frequencies.
*** Shared with Permission from ITP Journal Volume 10 | Part 1 - 2016 ***
Time is everywhere but it's implementation in #5G is not easy. Unlike #4G, #TDD is more common in 5G especially in mid-bands [ #3.5Ghz (CBRS) and #Sub6Ghz ] to higher bands (as in mmWave) spectrums and also in spectrum overlays. TDD provides #spectrum efficiency but requires precision time synchronization.
Read this article to learn more about 5G synchronization challenges and how to address it.
Distributed Approach for Clock Synchronization in Wireless Sensor NetworkEditor IJMTER
Time synchronization is an important service in WSNs. existing time synchronization algorithms
provide on average good synchronization between arbitrary nodes, however, as we show in this paper, close-by
nodes in a network may be synchronized poorly. We propose the Distributed Time Synchronization Algorithm
(DTSA) which is designed to provide accurately synchronized clocks between nearest-neighbours. DTSA works
in a completely decentralized fashion: Every node periodically broadcasts its time information. Synchronization
messages received from direct neighbours are used to calibrate the logical clock. The algorithm requires neither a
tree topology nor a reference node, which makes it robust against link and node failures.
Comparative study of Different Time synchronization Techniques in WSNIRJET Journal
This document provides an overview and comparison of different time synchronization techniques in wireless sensor networks (WSNs). It begins with an abstract that introduces time synchronization as an important research area for WSN applications and outlines different protocols, methods, and parameters involved. The document then presents sections on the introduction, related work, two specific time synchronization protocols (TPSN and PBS), and conclusions. In summary, it examines time synchronization challenges in WSNs, describes existing protocols like TPSN and PBS, and provides a framework for comparing new and existing synchronization methods to better understand time synchronization characteristics in WSNs.
Stable Ethernet TCP/IP Real Time Communication In Industrial Embedded Applica...IJRES Journal
This paper discusses using Ethernet for real-time communication in industrial embedded applications. It first reviews using switched Ethernet to eliminate collisions and enable real-time data transmission. It then examines different industrial Ethernet technologies like EtherCAT and how priority scheduling and other techniques can enhance real-time performance. Various simulation results are presented showing the impact of parameters like packet processing rate and non-real-time traffic on latency. Finally, it concludes that industrial Ethernet networks using intelligent switching can offer advantages over traditional networks while enabling Internet connectivity if techniques like traffic shaping and multicasting are used.
This document provides an overview of time synchronization over Ethernet for power applications using Precision Time Protocol (PTP). It discusses the IEEE 1588-2008 standard which specifies PTP, and how industry-specific PTP profiles have been developed, including IEEE C37.238-2011 which specified the initial profile for power system applications. It describes how IEEE C37.238-2011 was later split into two standards: IEC/IEEE 61850-9-3:2016 which specifies a base profile, and IEEE C37.238-2017 which specifies an extended profile with additional functionality. The document outlines some of the key aspects and changes between these standards, and discusses testing and certification efforts through the IEEE ICAP program to help facilitate
Simulation-Based Fault Injection as a Verification Oracle for the Engineering...RealTime-at-Work (RTaW)
The document summarizes a study on using simulation-based fault injection to evaluate the precision and robustness of the clock synchronization algorithm in Time-Triggered Ethernet (TTE) networks. A CPAL model of a TTE network with switches, end systems, and links was developed and validated. Experiments were run in fault-free scenarios and with permanent link failures or transient transmission errors. Results showed that TTE maintains high clock precision in fault-free cases but precision degraded significantly with transmission errors outside the fault assumptions. The study demonstrated the value of simulation models with fault injection for comprehensive evaluation of critical network technologies.
Soft Real-Time Guarantee for Control Applications Using Both Measurement and ...CSCJournals
This document presents a probabilistic admission control algorithm for supporting soft real-time control applications over switched Ethernet networks. The algorithm uses both measurement and analytical techniques. It measures baseline delays with no competing traffic to characterize fixed delay components. It then provides an efficient method to estimate queueing delays for heterogeneous periodic flows in order to determine admission probabilities that ensure flow deadlines are met with high probability. The algorithm was implemented on Windows and experiments validated its effectiveness in admitting new flows while maintaining soft real-time guarantees for existing flows.
There is a pressing need to distribute accurate timing, i.e., frequency and/or Time of Day (ToD), across Packet Switched Networks (PSNs) for applications such as cellular backhaul. This paper reviews the main issues involved in timing over packet (ToP) demarcation and provides best practices for ToP demarcation and performance monitoring.
Realtime wether station for monitoring and control of agricultreBhushan Deore
This document provides an overview of a project to develop a real time weather station for monitoring and controlling agriculture. The project aims to provide accurate and timely weather data through sensors measuring temperature, humidity, CO2 levels and light intensity. This data will be displayed on a webpage in real time. The system uses a DSPIC processor and Ethernet controller chip to gather sensor data and connect to the webpage. This will allow farmers and others to remotely monitor weather conditions. It discusses the scope, objectives and organization of the project report, as well as introducing real time weather stations and the basic concepts involved like the use of sensors, networking protocols and webpage display of data.
why time synchronization is important in power generation, transmission and ...Mohd Amir
Meinberg products make frictionless power transportation possible. By accurately synchronizing your IT-Network and reliably monitoring your power line frequency
International Journal of Engineering and Science Invention (IJESI) is an international journal intended for professionals and researchers in all fields of computer science and electronics. IJESI publishes research articles and reviews within the whole field Engineering Science and Technology, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online.
About TrueTime, Spanner, Clock synchronization, CAP theorem, Two-phase lockin...Subhajit Sahu
TrueTime is a service that enables the use of globally synchronized clocks, with bounded error. It returns a time interval that is guaranteed to contain the clock’s actual time for some time during the call’s execution. If two intervals do not overlap, then we know calls were definitely ordered in real time. In general, synchronized clocks can be used to avoid communication in a distributed system.
The underlying source of time is a combination of GPS receivers and atomic clocks. As there are “time masters” in every datacenter (redundantly), it is likely that both sides of a partition would continue to enjoy accurate time. Individual nodes however need network connectivity to the masters, and without it their clocks will drift. Thus, during a partition their intervals slowly grow wider over time, based on bounds on the rate of local clock drift. Operations depending on TrueTime, such as Paxos leader election or transaction commits, thus have to wait a little longer, but the operation still completes (assuming the 2PC and quorum communication are working).
Simulation model of dc servo motor controlEvans Marshall
This document describes a simulation model of a DC servo motor control system using the TrueTime simulator and WirelessHART communication protocol. The model includes three nodes - a sensor, controller, and actuator - connected via a WirelessHART network. The document provides details on configuring the TrueTime kernel blocks for each node, implementing the control algorithm, and setting up the WirelessHART network simulation. Simulation results are presented showing the data transfer between the nodes for controlling the motor position.
4 realtime wether station for monitoring and control of agricultreBhushan Deore
This document describes a project to create a real-time weather station for monitoring and controlling agriculture. The weather station will use sensors to measure temperature, humidity, CO2 levels, and light intensity in agricultural fields. It will send the sensor data in real-time to a webpage using Ethernet and TCP/IP protocols so farmers can remotely monitor environmental conditions. The system also allows farmers to control devices like pumps and sheds through the webpage to automatically regulate the field's temperature, if needed.
Similar to Precision clock synchronization_wp (20)
Resumes, Cover Letters, and Applying OnlineBruce Bennett
This webinar showcases resume styles and the elements that go into building your resume. Every job application requires unique skills, and this session will show you how to improve your resume to match the jobs to which you are applying. Additionally, we will discuss cover letters and learn about ideas to include. Every job application requires unique skills so learn ways to give you the best chance of success when applying for a new position. Learn how to take advantage of all the features when uploading a job application to a company’s applicant tracking system.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
Learnings from Successful Jobs SearchersBruce Bennett
Are you interested to know what actions help in a job search? This webinar is the summary of several individuals who discussed their job search journey for others to follow. You will learn there are common actions that helped them succeed in their quest for gainful employment.
IT Career Hacks Navigate the Tech Jungle with a RoadmapBase Camp
Feeling overwhelmed by IT options? This presentation unlocks your personalized roadmap! Learn key skills, explore career paths & build your IT dream job strategy. Visit now & navigate the tech world with confidence! Visit https://www.basecamp.com.sg for more details.
5 Common Mistakes to Avoid During the Job Application Process.pdfAlliance Jobs
The journey toward landing your dream job can be both exhilarating and nerve-wracking. As you navigate through the intricate web of job applications, interviews, and follow-ups, it’s crucial to steer clear of common pitfalls that could hinder your chances. Let’s delve into some of the most frequent mistakes applicants make during the job application process and explore how you can sidestep them. Plus, we’ll highlight how Alliance Job Search can enhance your local job hunt.
Jill Pizzola's Tenure as Senior Talent Acquisition Partner at THOMSON REUTERS...dsnow9802
Jill Pizzola's tenure as Senior Talent Acquisition Partner at THOMSON REUTERS in Marlton, New Jersey, from 2018 to 2023, was marked by innovation and excellence.
Job Finding Apps Everything You Need to Know in 2024SnapJob
SnapJob is revolutionizing the way people connect with work opportunities and find talented professionals for their projects. Find your dream job with ease using the best job finding apps. Discover top-rated apps that connect you with employers, provide personalized job recommendations, and streamline the application process. Explore features, ratings, and reviews to find the app that suits your needs and helps you land your next opportunity.
Joyce M Sullivan, Founder & CEO of SocMediaFin, Inc. shares her "Five Questions - The Story of You", "Reflections - What Matters to You?" and "The Three Circle Exercise" to guide those evaluating what their next move may be in their careers.
1. White Paper
Precision Clock Synchronization
The Standard IEEE 1588
Precision Clock Synchronization – IEEE 1588
White Paper Rev. 1.2
Hirschmann. Simply a Good Connection.
2. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 2 / 20
Table of contents
Precision Clock Synchronization
The Standard IEEE 1588
1 Introduction 3
2 Why time synchronization 3
3 Previous solutions 4
4 PTP applications 4
5 The functional principle of PTP 6
6 Implementation of PTP 7
7 Results 8
8 Cooperation between Hirschmann and the Zurich University of Winterthur 9
9 Further developments 9
10 Summary 10
Annex 1: The PTP protocol in detail 11
Annex 2 – The implementation of PTP in detail 14
3. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 3 / 20
Precision Clock Synchronization
The Standard IEEE 1588
1 Introduction
Precise time information is especially important for distributed systems in automation technology. With the
Precision Time Protocol (PTP) described in IEEE 1588, it is possible to synchronize distributed clocks with
an accuracy of less than 1 microsecond via Ethernet networks for the very first time. The demands on the
local clocks and the network and computing capacity are relatively low.
This White Paper provides you with an overview of the application possibilities and function of the Precision
Time Protocol. Further technical information can be found additionally in the annex which explains details
of the functional principle and hints on implementing PTP in devices.
2 Why time synchronization
We use clocks to synchronize ourselves with persons or processes. The necessary accuracy of the clock
depends on the application. Anyone wanting to catch a train has to have his eye on the clock to within a
minute. In competitive sport, a hundredth of a second can be decisive and drives in a packing machine
need a synchronization in the microsecond range.
Many technical systems have a sense of time. An implicit system time exists when there is no actual clock
and the timing behavior is determined by processes in the hardware and software. This is often sufficient in
a lot of systems. An implicit time system is implemented, for example, by regular trigger events to every
user which indicate the beginning of a unit of time and then trigger the appropriate actions.
The system time is explicitly available when it is represented by a clock. This is often necessary in complex
systems especially. This decouples the communication from the execution. But not every clock is exact.
Now and again it has to be checked whether the deviation is tolerable and whether the clock needs to be
corrected. Communication between the individual clocks is necessary for this.
Two effects are in evidence when setting or synchronizing clocks: independent clocks initially run at an
offset for one thing. To synchronize them, the more inaccurate clock is set to the more accurate one (offset
correction). Another thing is that real clocks do not run at exactly the same speed. Therefore, the speed of
the more inaccurate cock has to be regulated constantly (drift correction).
4. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 4 / 20
3 Previous solutions
There have previously been different ways to synchronize distributed clocks through a network. The most
common of these are the Network Time Protocol (NTP) and the simpler Simple Network Time Protocol
(SNTP) derived from it. These methods are widely distributed in LANs (Local Area Networks) or in the
Internet and allow accuracies into the millisecond range. Another possibility is the use of radio signals from
GPS satellites. However, this necessitates relatively expensive GPS receivers in every clock as well as the
appropriate antennae. This theoretically gives you high-precision clocks but the high costs and effort often
prevent it.
Another solution is to send a high-precision time pulse (e.g. pulse per second signal) to every user on
separate lines. However, this entails an enormous additional wiring effort.
This is where the Precision Time Protocol (PTP) described in IEEE 1588 comes in. It has been developed
with the following aims:
• Synchronization accuracy in the sub-microsecond range
• Minimum requirements of the processor performance and network bandwidth which enables it to be
implemented on simple and low-cost devices
• Low administration effort
• Use via Ethernet networks but also via other multicast-capable networks
• Specification as an international standard
4 PTP applications
The idea for PTP was born at the end of the 90s in the USA at Agilent Technologies in the field of
measuring technology. The process principle developed there was submitted to the IEEE as a suggestion
and created the basis for the IEEE 1588 standard. At the end of 2002 PTP was passed as a standard
under the name of "1588TM
- IEEE Standard for a Precision Clock Synchronization Protocol for Networked
Measurement and Control Systems". In addition, PTP was also adopted as an IEC standard in May 2004
and was published under the name of IEC 61588.
5. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 5 / 20
PTP is arousing interest in many different applications. In automation technology, PTP is in demand
wherever processes need to be synchronized exactly. Here Motion Control is an important field of
application in the broadest sense. Because PTP helps to synchronize drives in a robot or a printing,
packing or paper processing machine for example. Interactive robots are also connected by high-precision
clocks or whole machine or plant parts are linked closely by PTP so that the processes that run can be
synchronized exactly. Clocks running synchronously in every component enable distributed structures to be
set up and the processes to be decoupled from the communication and processing of the control
commands.
For this reason, the time synchronization according to IEEE 1588 has since become a part of almost all
future real-time automation protocols. CIPsync, part of the Ethernet/IP frameworks of the ODVA, relies
totally on PTP for Motion Control applications. PROFInet (PNO) has PTP as a synchronization protocol on
its roadmap and ETHERNET Powerlink (EPSG) will also use PTP for synchronizing real-time segments.
Also, many companies are working on the evaluation and implementation of PTP outside of automation
technology. Wherever measured values are detected and need to be put in relation to each other, PTP is a
popular solution. In energy distribution systems, parameters such as currents and voltages are measured
in distributed sensors, linked centrally and evaluated. Turbine controls use the PTP protocol to set up even
more efficient plants. And, for monitoring processes, decentrally detected events are marked with precise
time stamps and transferred to the control station for logging and analysis.
PTP is used in measuring technology for correlating decentrally detected physical variables, for example in
high-frequency measuring technology. Geo-scientists use PTP to synchronize seismic measuring
instruments over great distances and to be able to localize earthquake epicenters more exactly. In
telecommunications, PTP is being considered for synchronizing networks or supplying mobile radio base
stations with precise time pulses. There is also interest in time synchronization in accordance with IEEE
1588 in the fields of safety technology, automotive technology or military applications.
All these applications are currently in the development or prototype stage. However, in the next few years,
many of these applications will come onto the market in regular products and PTP will find wide distribution.
6. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 6 / 20
5 The functional principle of PTP
PTP knows two types of clocks, masters and slaves. A clock in a terminating device is known as an
ordinary clock, a clock in a transmission component like an Ethernet Switch as a boundary clock. A master
which is controlled ideally by a radio clock or a GPS receiver, synchronizes the respective slaves
connected to it.
The synchronization process is divided into two phases. First the time difference between the master and
the slave is corrected, this is the offset correction. To do this, the master sends a synchronization message
– SYNC message – with an estimated value of the time cyclically to the connected slaves. Parallel to this,
the time at which the message leaves the sender is measured as precisely as possible, if possible by
hardware support directly on the medium. The master then sends this actual exact transmission time of the
corresponding sync message to the slaves in a second message - follow-up message. These also measure
the reception time of these messages as exactly as possible and can correct the correction value (offset) to
the master from it. The slave clock is then corrected by this offset. If the transmission line were to have no
delay, both clocks would be synchronized.
Figure 1: Boundary clock switches works as slaves in relation to the master clock
and supply the other connected slaves as a master.
The second phase of the synchronization, the delay measurement, determines the run time between slave
and master. This is determined by so-called Delay Request and Delay Response messages in a similar
way and the clocks adjusted accordingly.
However, it is a symmetrical delay between the master and slave, i.e. same values for there and back, that
is decisive for a delay measurement and its accuracy. This is satisfied practically by a direct connection
with a length of cable. However, if there are network components such as switches or routers between the
users, this is no longer the case. The so-called boundary clock was defined for such devices for this
reason. Such a switch contains a clock which is synchronized to a connected master and then behaves as
7. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 7 / 20
a master at every other port and synchronizes the connected slaves. In this way, the synchronization
always takes place in a point to point connection which exhibits very symmetrical run times and practically
no jitter. Therefore, wait times or jitter when passing through the switches have no influence on the
accuracy of the synchronization.
A detailed description of the functional principle can be fund in annex 1.
6 Implementation of PTP
If the Precision Time Protocol is to be used in a system, the PTP protocol stack must be implemented. This
can be implemented very compactly and only makes minimum demands on the processor performance
and the network bandwidth. This is very important for the implementation in simple and low-cost devices.
PTP can even be implemented without any trouble in embedded systems with simple 16 or 32 bit
microcontrollers. The only requirement for achieving a high precision is as exact a measurement of the
PTP message transmission and reception times as possible. This must take place very close to the
hardware (e.g. directly in the driver software) and with as great an accuracy as possible. In
implementations as a purely software solution, therefore, the architecture and performance of the system
restrict the attainable accuracy directly.
When using additional hardware support for time stamping, the precision can be increased considerably
and effected virtually independently of the software. A little logic is necessary for this which can be
integrated, for example, as FPGA or in ASICs directly at the network input.
If PTP is used through Ethernet networks, special attention must be paid to the network infrastructure.
Since hubs have almost no influence on the accuracy of the protocol due to their practically constant
throughput time, the run times must be taken into account when using switches, as already described in
chapter 5. PTP measures the run times in the network and measures the clocks accordingly. However, run
time variations, as they always occur in switches, lead to inaccuracy.
Since switches save the received data packets completely and queue effects can considerably delay the
transmission under certain circumstances, great fluctuations may occur here. At low network load, this
effect hardly has an influence, but at greater network load or in temporary load situations, this can
considerably worsen the synchronization accuracy.
8. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 8 / 20
This is counteracted by using so-called boundary clock switches. These contain their own PTP instance
which operates as a PTP slave in relation to the connected master clock and is therefore exactly
synchronized by it. In relation to the connected terminating devices, the PTP slaves, every single switch
port then operates in turn as a PTP master and synchronizes these slaves with its internal time. This
compensates all run time fluctuations and wait times in the switches and enables maximum accuracy to be
achieved even through larger Ethernet networks.
7 Results
Hirschmann was one of the first manufacturers to implement and optimize the Precision Time Protocol.
A software stack was developed which implements the protocol very efficiently and a chip which supports
the process for maximum precision.
The implementation achieves accuracies of about 5 to 50 us as a pure software solution. The precision is
even higher with the hardware support for the time stamp detection.
Figure 2: The Precision Time Protocol achieves accuracies of
below 100ns with hardware support
In a pilot system in which several ordinary clocks are connected by an Ethernet switch with boundary clock
function, a typical accuracy of +/-60ns was achieved, practically independently of the network load or
workload of the CPU. Variants of the PTP boundary clock are available for the Industrial-Ethernet switches
of the MICE family from Hirschmann.
Distribution of accuracy
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
10000
-104 -88 -72 -56 -40 -24 -8 8 24 40 56 72 88 104
Offset [ns]
probability
9. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 9 / 20
Figure 3: The Industrial Ethernet switches of the MICE series support the Precision Time Protocol according
to IEEE 1588
8 Cooperation between Hirschmann and the Zurich University of
Winterthur
In cooperation with the Zurich University of Winterthur (ZHW), Hirschmann has been working for some time
of the further development and optimization of IEEE 1588. In the scope of this cooperation, the ZHW offers
interested users support in the implementation of PTP ordinary clocks. This includes software stacks and
VHDL designs which are based on the technology developed by Hirschmann and additional services such
as evaluation kits, training or design support. For further information, see the web site
"http://ines.zhwin.ch/ieee1588/index.html".
9 Further developments
IEEE 1588 has a wide acceptance on the automation and measuring technology market. But the method's
potential is also of interest to other branches. To meet additional requirements, the P1588 project was
started in February 2005 in the IEEE Committee with the aim of extending the standard in the following
directions:
• Greater accuracy: The aim is to achieve accuracies in the nanosecond range and below. The prerequisite
for this are higher quality oscillators, shorter sync intervals, higher resolution of the time stamp and better
symmetry.
• Fail safety: If the master clock fails, the reconfiguration must take place in such a way that the
synchronization is not impaired.
• SNMP Management: SNMP is the most widely used network management protocol in Ethernet networks.
A PTP MIB should therefore be specified.
• Different Ethernet headers: The inclusion of Tagged Ethernet Frames (VLAN), IPv6 packets and fields for
protocol extension should be enabled.
10. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 10 / 20
• Transparent Clock: Topologies with linear and ring structure are often used in automation technology. The
rowing of boundary clocks which each represent their own control circuit is a problem because of the
accumulation of errors. The Transparent Clock is suggested as an alternative. This implements an end-to-
end control (unlike the cascade of single regulators). The switches measure the throughput time of the PTP
messages and manipulate the time stamps contained in the messages accordingly. With the aid of the
Transparent Clock, the fast reconfiguration of the network in the case of an error is possible.
• Application in other network types: A few details such as message format, addressing and reference point
of the time stamp must be specified for this. Candidates are WLAN, DeviceNet and Telekom networks.
• Security: The synchronization mechanism must be protected against undesirable access in open
networks.
10 Summary
PTP has already proven its capabilities in the lab and is now ready to make the leap to practically
applications. You can be assured that PTP will find further distribution over the next few years and that
many applications can be implemented much easier and more efficiently than with existing technology.
Further information:
http://www.hirschmann.de Hirschmann Automation and Control GmbH
http://ieee1588,nist.gov/ IEEE 1588 Standardization Group
http://ines.zhwin.ch/ieee1588/ Zurich University of Winterthur, PTP Stacks and Services
11. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 11 / 20
Annex 1: The PTP protocol in detail
The IEEE 1588 standard describes the Precision Time Protocol (PTP) including the basic synchronization
algorithms. An initialization phase is described additionally which selected the most accurate clock in the
network as the dominant system clock by means of the so-called Best Master Clock algorithm.
The behavior of the clocks is described in the standard on status machines, data types and their
representation are defined in addition. For management and configuration of the clocks in the network, the
standard defines its own simple management protocol via which the user can request the states of all the
participating clocks on the one hand but can also configure them on the other. For example, he can
determine which clock he prefers to assume the function of grand master.
The procedures for regulating the clocks and the user interface (API) through which the clock can be
addressed by the application are not specified.
PTP is based on IP Multicast communication and is not restricted to Ethernet but can be used in principle
on any multicast-capable bus system. The multicast communication offers the advantage of simplicity
because no IP address management needs to be implemented on the PTP nodes. PTP can be scaled for a
high number of PTP nodes specially by using IP Multicast.
Figure 4: PTP synchronization domain
(time source)
synchronized
synchronized
synchronized
synchronized
synchronized
PTP cascading depth
Control unit
(e.g. PLC)
OC: Ordinary Clock (source or sink, 1 port)
BC: Boundary Clock (switch or router, 1-n ports)
GM: Grand Master (synchronization source)
12. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 12 / 20
Time synchronization, the algorithm
For time synchronization, the time of the master is reported to the slave as accurately as possible in PTP.
The trick is to compensate all the processing times and run times by this method so that the most optimum
possible synchronization can be established. The synchronization is divided into two processes for this.
First the masters and slaves correct their time difference with the offset measurement. In this offset
correction, the master sends a clear synchronization message - the SYNC message - to the connected
slave cyclically at defined intervals (every 2 seconds in the basic setting). This sync message contains the
current time of the master clock. However, since the reading out of the clock, the processing of the log, the
handling of the communication stack and the transmission of the data via the Ethernet controller require an
undefined time, the time information in the sync message is already out of data when it leaves the master.
Therefore the actual transmission time of the message is measured as close as possible to the physical
interface (ideally directly at the Ethernet port by hardware) and this information is sent to the slave by
means of a second message, the follow-up message.
Upon reception of the follow-up message, the slave calculates the correction value (offset Θ) to the master
under consideration of the reception time stamp of the sync message. The slave clock must then be
corrected by this offset. These precise time stamps now render the time fluctuations of the protocol stacks -
protocol jitter - above insignificant.
If there were no delay on the transmission line, both clocks would now be in sync.
The second phase of the synchronization process determines the delay time – (the run time on the
network) – between slave and master, the delay measurement. For this, the slave sends a so-called "Delay
Request" packet to the master and determines the exact transmission time of the message. The master
generates a time stamp on receiving the packet and sends the reception time back to the slave in a "Delay
Response" packet. From the local transmission and reception time stamp of the master, the slave
determines the delay time between the slave and the master. The delay measurement is made irregularly
and at greater intervals (4 - 60 seconds) than an offset measurement. This relives the load on the network
and especially on the terminating devices. However, it is a symmetrical delay (TDelay_Snd
= TDelay_Ret
= TDelay
)
between master and slave that is decisive for a delay measurement and its accuracy..
Figure 5 illustrates the synchronization algorithm.
13. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 13 / 20
Figure 5: Synchronization algorithm
Automatic master selection – Best Master Clock algorithm
The Precision Time Protocol determines master-slave relations between communicating PTP
synchronization elements. Determination of the states (master/slave)is the job of the Best Master Clock
(BMC) algorithm which compares the properties (accuracy, stratum, drift, variance, ...) of the
communicating clocks and derives the states for all local ports of the PTP element. Every PTP element
runs the BMC algorithm locally and therefore determines the status of all local ports. This transfer the
current properties of the master clock to the slaves cyclically in synchronization messages. The advantage
of this algorithm is that the nodes doe not have to negotiate these statuses but can calculate them
individually. This guarantees that the PTP network can be configured automatically in a tree structure
starting with the best available clock, the grand master. A configuration with several or no master and
unstable statuses are prevented by this algorithm.
14. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 14 / 20
Annex 2 – The implementation of PTP in detail
The special thing about the architecture of PTP is the separation of the time-critical part implemented in the
hardware and the protocol decoupled from hard time conditions, the software part. The protocol therefore
runs in a low priority process for example on a processor with low performance requirements.
The hardware unit consists of a high-precision real-time clock and a time stamp unit (TSU) for generating
the time stamp. The software component implements the actual IEEE1588 protocol with the link to the real-
time clock and the HW time stamp unit. Figure 6 illustrates the interaction of the hardware and software
components of an IEEE1588 synchronization element.
TX
RX
HW
Real-time
Clock
TSU
TSU - TimeStamp Unit
PHY
Sync & Delay_Req
sending and receipt time
(x)MII
Synchronization element
Set/Get
time
IEEE1588
Precision Time Protocol
TimeStamp
Interface
Clock
Interface
Port
Interface
MAC
Network
Protocol
stack
HW
SW
Important for a generic portable implementation of the PTP protocol is a software component modeling
which is as independent as possible from the operating system. To achieve this, Hirschmann has
introduced three layers with different levels of abstraction in its solution. The protocol layer implements
the operating system-independent Precision Time Protocol. The OS Abstraction Layer forms the interface
between PTP and the used operation system. The functions - tasks / processes, semaphores, timers,
sockets, etc. - offered by the operating system are integrated through the OS Layer. The following figure
shows the interaction of the individual steps.
Figure 6: Component layout of a
synchronization element
15. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 15 / 20
Protocol Layer,
OS independent
OS Layer
IEEE1588
Precision Time Protocol
Call
dispatcher
Protocol
Inputs
PTP
Clock
Interface
PTP
Timestamp
Interface
PTP
Port
Interface
Queue
PTP API
OS abstraction Layer
Timer RX/TX
PTP messages
Sync and DelayRequest
time stamp
Read and Set time
Synchronisation
PTP Management
Dispatcher
Best Master Clock
Algorithm
push
pop
Figure 7: Interaction diagram
The top layer implements PTP for synchronization of clocks in a network and can be used on different
communication elements (PC, Switch, Router, etc.). This is where the actual intelligence for synchronizing
the individual communication elements is to be found. Within the protocol layer only ANSI/ISO C-conform
functions have been used. This ensures that the log can be ported on different platforms without great
intervention in the functional principle. A protocol dispatcher guarantees the atomic execution of functions
in a single process. The communication between the protocol and the OS Abstraction Layer is made by a
queue and three defined interfaces.
The middle layer encapsulates operating system-dependent functions which have to be adapted if
necessary.
The Timestamp Interface provides the Precision Time Protocol with the detected time stamps for Sync
and DelayRequest messages. Depending on the expansion stage (precision requirement), the time stamp
is generated either by a HW unit (TSU) or by the software itself. "Software time stamps" are best generated
in the operating system-dependent NIC driver (RX-ISR, send process) as close to the transport medium as
possible.
The local clock is read and modified via the Clock Interface. These functions may also have to be adapted
depending on the platform. Applications which do not provide a real-time clock use the operating system
clock or optimized solutions such as the nanokernel under UNIX derivates. In addition to control of the local
clock, this interface also contains the control algorithms which are responsible for the quality [accuracy,
stability, transient behavior, etc. ] of the time synchronization.
The Port Interface is used to send or receive PTP messages. The IEEE1588 telegrams exclusively use
UDP/IP Multicast packets and therefore enable them to be sent and received via the socket interface of the
IP protocol stack. Time requirements can be neglected because the time stamp is generated directly at the
transport medium.
16. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 16 / 20
The inputs to the protocol ( configuration, diagnosis, PTP telegrams) run through the PTP API.
Low porting effort when changing over to a different platform
This process has meant that only the bottom two layers need to be adapted when porting the protocol to a
different platform which leaves the actual protocol (~ 90 - 95 % of the source texts) unaffected.
The software section of the described PTP reference architecture has been changed to object-based C.
This has meant that the advantages of object-oriented analysis/design/programming could be applied
despite using the C programming language: methodology, encapsulation, reusability, etc.
To check the easy portability of the software, Hirschmann has effected reference implementations of
ordinary and boundary clocks under the platforms Linux, VxWorks and Windows.
The precision of a software implementation
After completing the work, it was first examined what precision can be achieved with a purely software
implementation. Measurements both on Linux platforms and on Windows and VxWorks platforms gave a
typical synchronization accuracy of ±10µs to ±200 µs.
The achieved accuracy is basically dependent on the used platform, the network load, system
workload/internal bus load and the place where the time stamp is generated. The nearer to the hardware
the time stamp is generated, the higher the precision.
Hardware for maximum precision
A software implementation is inadequate for synchronization accuracies in the sub-microsecond range,
therefore the necessary time stamps must be generated in a so-called hardware time stamp unit directly on
the transport medium.
CPU Interface
xMII Interface
FIFO
Offset
TimeStamp Unit (TSU)
Drift TimeTime stampConfiguration
Access to
Network
RXTX
PTP HW
HW real-time clock Oscillator
The Timestamp Unit (TSU) has also been converted into hardware. It is based on the Media Independent
Interface (MII). If the TSU detects a Sync or DelayRequest message, it notes the time of occurrence. In
Figure 8: Hardware block diagram
17. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 17 / 20
addition, it extracts information for clear identification of the message. The TSU buffers this information in a
FIFO and therefore enables the detected time stamp to be assigned to the corresponding PTP message
later.
The absolute time of the synchronization element is managed by the HW real-time clock and serves as a
high precision metronome. The HW clock counts oscillator ticks which the clock driver converts into
seconds and nanoseconds. An integral part of the digital real-time clock is the offset (phase) and drift
(frequency) correction unit. It enables the adjustment of a real-time clock to a reference clock in the sub-
microsecond range. The separation of the phase and frequency unit enables the specific setting
intervention of the control which achieves a fast convergence of the system. The system can therefore
control phase jumps – caused by a change in the topology for example – independently of the drift
correction unit. This has the advantages that the local clock does not have to change the frequency and a
phase jump is soon compensated.
The offset compensation adjusts the absolute value of the local clock to the reference clock.
The drift correction causes frequency synchronization of the local real-time clock with the reference clock.
The result is that the local clock "ticks" with the frequency of the master. The challenge is now to determine
the relative drift δ of the local clock to the reference clock. The following equation can be assumed for the
drift correction by way of simplification.
nQuatizatioMasterSlave tftf εδ ++= )()(
Whereby )(tf represents the present frequency of the appropriate clock and onQuantizatiε the quantization error.
The whole hardware can be implemented in a FPGA at the first attempt whereby the application requires
about 20,000 to 30,000 Logic Array Gates.
The basic conditions for high-precision time synchronization
With regard to the synchronization accuracy, PTP defines the minimum requirements of a local clock and
gives recommendations for improving the precision. The following aspects must be considered.
• Operating system and network Stack Jitter
Jitter within a synchronization element can be avoided by time stamps in the hardware.
• Latency between master and slave
Symmetrical latency (send and return direction identical) between masters and slaves compensates the
delay measurement. But asymmetry causes an unncompensatable time difference between master and
slave.
• Jitter in network coupling elements (repeaters, switches, routers)
Jitter tests with network coupling elements have shown that the jitter of hubs and repeaters is negligible. If,
however, you observe switches in high load or overload, you will see that these have a considerable delay
jitter. Values up to one millisecond are no rarity. The jitter in a switch depends on the message length and
the number of packets which are already buffered. Even if only one long packet has preceded the
synchronization packet in the switch, this can cause a jitter of up to 125µs. Therefore it is recommended to
18. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 18 / 20
equip switches with the boundary clock function for a high-precision network. In this way, the user ensures
that the synchronization is always made only by a point to point connection, i.e. by a physical connection,
the jitter of which is negligible.
• Resolution and stability of the local clock
If you consider the above aspects, the local clock of the synchronization element largely determines the
accuracy of synchronization. The first limiting factor is the resolution of the local clock which is determined
by the crystal frequency of the oscillator. However, the decisive aspect is down to the stability, especially
the short-term stability of the oscillator. The quality of the synchronization accuracy in the transient state
(drift compensated) is therefore dependent on the relative drift between the master and slave between two
consecutive synchronization telegrams.
Regulation, the distinguishing feature
PTP describes the process by which master and slave determine their time difference (offset). But the
protocol cannot set this variable directly. Different algorithms must be used to determine the offset and the
drift or to verify the value. The higher the precision of the local clock in relation to the reference clock, the
more these algorithms have to be improved. The verification of the offset could be achieved simply for
example by comparing the new value with the previous one. When this then exceeds a certain difference, it
is assumed to be invalid. However, it must be considered that something may really have changed and the
new values should be accepted if they appears several times in succession.
The drift compensation (frequency synchronization) is rather more complex and takes place over a longer
period of time.
The quality of the implementation of the control will differentiate the providers in future. The users can base
their evaluation of a control on the following criteria.
• The transient behavior of a control characterizes its quality. The decisive variable here is the
transient time. That is the time a local clock requires to synchronize to the reference clock (frequency and
phase).
• Interference immunity and stability of a transient clock. If the clock is synchronized, the control
should have a certain inertia in order not to counteract minimum outliers with a high setting intervention of
the controller. Nevertheless, the control must respond quickly to permanent changes (topology change or
master change) to restore the synchronization. This is achieved for example by an adaptive control.
19. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 19 / 20
Results
Two ordinary clocks implemented in Hirschmann Ethernet switches of the MICE family were connected in a
first attempt in a laboratory set-up. A high network load was applied additionally with a generator for
rigorous testing of the protocol.
In order to be able to test the difference between the local clock and the reference clock as application
realistically as possible, both units were given a Pulse Per Second (PPS) signal output and connected to
an oscilloscope (figure 9). The deviation of the two signals was measured and the frequency adjustment of
the deviation represented very elegantly in this way.
The synchronization accuracy achieved was about ± 60 ns (max. jitter). The measurement was made over
a period of 84 hours.
Figure 9: Measuring set-up
Figure 10 shows the frequency distribution of the offset values between the master and slave in
nanoseconds. The standard deviations is 14.9 ns and the average value 4.2 ns.
synchronized
Grandmaster
Fast Ethernet
PPS Out PPS Out
Slave
20. Precision Clock Synchronization – IEEE 1588 Rev. 1.2
White Paper 20 / 20
Figure 10: Achieved accuracy
The drift setting of the oscillators restricts the synchronization accuracy in the existing prototypes. A quartz
frequency of 50 MHz (± 50 ppm) gives a resolution of 20 ns. The system can therefore only set the drift in
the range of ±20 ns per second. If you now look at the relative drift between the local clock and the master
clock during two consecutive synchronization telegrams, it soon becomes clear that the short-term stability
of the oscillators has a decisive influence on the synchronization accuracy in the transient state.
Andreas Dreher, Dirk Mohl
Hirschmann Automation and Control GmbH
Neckartenzlingen, Germany