Ieee 1588 Anew Vocabulary

IEEE 1588-2008
A NEW VOCABULARY
UNDERSTANDING THE IEEE 1588 PRECISION TIME PROTOCOL

Overview
Introduction to IEEE 1588

Unicast Messages & Flow
Multicast Principles
On-Path Support
Management Messages
1588 Modes
Influences on Time/Frequency Accuracy
IEEE 1588, The Road Ahead …
© COPYRIGHT SYMMETRICOM (2009) PAGE 2

Why IEEE 1588?
Industry needed a new means
to deliver:
► Accurate timing at sensors,
Sensor
data collectors & recorders,
► without the need for a point- Data Collector
Sensor
to point parallel timing
system (out of band),
► without a separate physical
Sensor
distribution system. Switch Switch
► over the industrial Ethernet
Timing
(in-band),
Sensor
Master Clock

Why IEEE 1588?
Image courtesy of National Instruments

F-18 Aircraft Static Fatigue Test System (Boeing)
IEEE 1588-2008, The Standard
IEEE 1588-2008 …
► Is a protocol definition, not a product,
► is known as Precision Time Protocol (PTP)
► -2008 is also referred to as version 2 (v2)
► is intended to synchronize independent
clocks on separate nodes of a distributed
system to a high degree of precision,
► is the second version of a IEEE standard,
► defines how to transfer precise time over
networks. It does not define how to recover
frequency or high precision time of day.
► The key challenge is to convert packets to
Time & Frequency, and cost effectively.
Protocol ref. Oxford English Dictionary

• noun a set of rules governing the exchange or transmission of
data between devices
IEEE 1588-2008 …
 -2008 defined for all applications and
environments… barrier to interoperability
 1588 profiles narrow choices, facilitates
interoperability
Default Profile
Defined in Annex J. of 1588 specification
LAN/Industrial Automation Application
Telecom Profile
Defined by ITU-T (G.8264.1)
Telecom WAN Applications
Future Profile(s)
Defined by application specific bodies
Protocol set for particular application

Version 2 (-2008 version) includes ITU sponsored changes for the Telecom
Industry with a specific Telecom *profile. These include:
► Layer 3 transport option;
► Separate announce message (lower frequency);
► Reduced Sync message size & higher update rates (up to 128 Hz versus
64 Hz in version one);
► Unicast for the Telecom profile (with sync rate & duration negotiation);
► Configuration mechanisms;
► Fault Tolerance
► Provision for Grandmaster and network failures
► ACCEPTABLE_MASTER_TABLE support;
► Transparent clocking through 1588-aware network equipment.
* The set of required options, prohibited options, and the ranges and defaults of configurable
attributes for the Telecom Application of IEEE 1588.

Setting Expectations …
What Does 1588 Aim To Achieve? What Do Mobile Networks Need?
Version 1 Application Frequency Time
► 1 microsecond time-of-day precision Goal: <3µs
CDMA2000 ±50 ppb
over Industrial Ethernet (±0.5 µS) Must Meet: <10µs
GSM 50 ppb N/A
Version 2*
WCDMA 50 ppb N/A
► less than 100 nanosecond (target
50nS) time-of-day precision over 3µs inter-cell

TD-SCDMA 50 ppb
phase difference
Ethernet LAN.
LTE (FDD) 50 ppb N/A
► Less than 1µs time-of-day precision
**3µs inter-cell
over switched Ethernet WAN. LTE (TDD) 50 ppb
phase difference
-8
► stable frequency (1.6x10 or 16ppb) **5µs inter-cell
LTE MBMS 50 ppb
recovery (from time-of-day reference). phase difference
FemtoCell 250 ppb N/A
2 ppm
WE CAN MEET & EXCEED MOBILE absolute, ~50 Typically
NETWORK REQUIREMENTS WiMAX (TDD)
ppb between 1 – 1.5 µs
base stations
* Needs driven requirements.
Backhaul N/W 16 ppb N/A
** Standard still under development.

How Is Precision Possible?
Message Exchange Technique
► Frequent “Sync” messages broadcast between
master & slaves, and

► delay measurement between slaves and master.
Hardware-Assisted Time Stamping

► Time stamp leading edge of IEEE 1588 message
as it passes between the PHY and the MAC.

► Removes O/S and stack processing delays.
► Master & Slave use hardware-
assisted time stamping.
Best Master Clock (BMC) Algorithm.

IEEE 1588 In The Stack
PackeTime (IEEE 1588 & NTP) Clock Recovery Layer
Transport
WIDE AREA NETWORK

IEEE 1588-2008 NTP V3/V4
Layer
(Layer 4)
UDP TCP
Network
Layer IP V4/V6
(Layer 3)
MPLS
Carrier Ethernet
Data Link
LOCAL AREA NETWORK

Layer ATM IEEE 802.3 (Ethernet)
(Layer 2)
xDSL Transport xPON
Synchronous Ethernet Microwave Transport

Physical
Layer Copper/Coaxial Transport Fiber Optic Transport
(Layer 1)
PHY Timestamp
TDM & SyncE Clock Recovery Layer
Deterministic Results

Introducing The New Elements
TDM Synchronization Elements IEEE 1588 Elements
1. Primary Reference Clock/Source 1. Ordinary clocks (consisting of the
Serves as a master clock for a Grandmaster & Slave)
network, office or network element.
Based on Cesium or GPS.
2. Boundary Clock
2. Slave Clock Regenerates PTP message,
A timing device that selects one eliminating earlier path delays.
synchronization reference, attenuates 3. Transparent Clock
jitter and wander, distributes reference Adjusts the correction field in the sync
signals, and provides holdover. and delay_req event messages.
4. Management Node
Human/programmatic interface to PTP
management messages.

IEEE 1588-2008 Message Overview
The Grandmaster (Server) sends the The Slave (Client) sends the following
following messages: messages:
► Signaling (2 types) ► Signaling (3 types)
► Acknowledge TLV (ACK) ► Request announce
► Negative Acknowledge TLV (NACK) ► Request sync
► Announce message ► Request delay_resp(onse)
► Sync message ► Delay_Req(uest)
► Follow_Up message
► Delay_Resp(onse)
Message Headers entering the PHY are the “on-time” marker

Overview

On-Path Support
Management Messages
1588 Modes

Unicast Startup Sequence
Master/Server Master Clock Slave Clock Slave/Client
IEEE 1588 Processor IEEE 1588 Processor

10
PROCESS SET’S UP THE

20
Network protocol stack Network protocol stack
& OS Processing & OS Processing 30
RESERVATION.
40
Switch/Router Layer
Sync detector & Sync detector &
50
timestamp generator timestamp generator
60
70
Physical layer Physical layer
80
90
Server clock sends: Client clock sends:
100
2. Signaling (Announce granted) 1. Signaling (Request Announce)
110
4. Signaling (Sync granted) 3. Signaling (Request Sync)
120
6. Signaling (delay_resp granted) 5. Signaling (Request delay_resp)
130
Time
Time
140
Network 150
The process is repeated before the lease expires

(typically halfway through the lease period). © COPYRIGHT SYMMETRICOM (2009) PAGE 16
Unicast Startup Sequence
Switch/Router Layer
Master Clock
Slave Clock
Time
Time
Lease Duration in Bytes (10-1000s for Telecom Profile)

Sync Interval (2X), where x = 0,1,2,3,-1,-2,-3
Signaling Type
-b0 announce request
-00 sync request
-90 delay_resp(onse) request
Time Transfer Technique
Master Clock Slave Clock Data At Round Trip Delay
Slave Clock RTD = (t2 - t1) + (t4 - t3)
Offset:
(slave clock error and one-way path delay)
OffsetSYNC = t2 – t1
t1 Leap second offset
OffsetDELAY_REQ = t4 – t3
Switch/Router Layer
t2 t2 (& t1 for 1-step)

We assume path symmetry, therefore
t1,t2 One-Way Path Delay = RTD ÷ 2
t3 t1, t2, t3 Slave Clock Error = (t2 - t1) - (RTD ÷ 2)
t4
Notes:
1. One-way delay cannot be calculated
exactly, but there is a bounded error.
t1, t2, t3, t4
2. The protocol transfers TAI (Atomic Time).
UTC time is TAI + leap second offset from
the announce message.
Time
Time
The process is repeated up to 128 times per second.

(Announce rate is lower than Sync rate)
Time Transfer Example
Master Clock Slave Clock Data At Assume at an instant in time:
Slave Clock
Master clock value = 100 seconds
Slave clock value = 150 seconds
(the slave clock error = 50 seconds)
One way path delay = 2 seconds
t1 Sync message is sent at t = 100 seconds

2s
For illustration, Delay_Req is sent 5 seconds
Switch/Router Layer
t2 t1 = 100 seconds after the Sync message is received:

t2 = 152 seconds
(150+2)
Round Trip Delay
RTD = (t2 - t1) + (t4 - t3)
t3 t3 = 157 seconds RTD = (152 - 100) + (109 - 157)
(152+5) RTD = 4 seconds
t4
Slave clock error eliminated.
Slave Clock Error = (t2 - t1) - (RTD ÷ 2)

= (152 - 100) - (4 ÷ 2)
t4 = 109 seconds
= 50 seconds
(100+2+2+5)
Time
Time
Round trip error eliminated
If the slave clock is adjusted by -50 seconds,

the Master & Slave will be synchronized.
Announce Message
The announce message carries no Sync information.
Master Clock Slave Clock
It does transport the leap second offset.
t1
Switch/Router Layer
t2
t3 Flags
t4
Leap Second Information
Grandmaster clockClass
Time
Time
Grandmaster Accuracy
Grandmaster Clock Type

Announce Message Flags
Master Clock Slave Clock The flags are transported in all IEEE 1588 messages.
t1
Switch/Router Layer
t2
t3
t4
Unicast/Multicast
1-step or 2-step
Time
Time

Best Master Clock (BMC)
Ordinary Clocks select the Best Grandmaster, based on information received in
the announce message:
► Grandmaster priority (set in the master by the user)
► 1588 clockClass (or stratum) number
► PTP variance (declared by master)
► Steps removed from the Grandmaster
► The unique clockID is the tie-breaker.

Sync Message
t1
Switch/Router Layer
t2
t3
Flags (same as announce)
t4
t1
Time
Time

Delay_Req(uest) Message
Master Clock Slave Clock The delay_req(uest) message optionally carries timing information in
the Timestamp field.
t1
Switch/Router Layer
t2
t3
t4
Time
Time

Delay_Resp(ponse) Message
t1
Switch/Router Layer
t2
t3
t4
t4
Time
Time

Managing Accuracy
2-Step 1-Step
Master Clock Slave Clock Master Clock Slave Clock
t1 t1
Estimated value of Real value of

Switch/Router Layer
Switch/Router Layer
t1 received at Slave t1 received at Slave
Real value of
t1 received at Slave
t3 t3
t4 t4
The follow_up message is helpful when hardware time

stamping cannot insert the time into the sync message
without causing a delay.
Packet encryption may also prevent the real-time stamp from
Time
Time
Time
Time
being inserted into the Sync message.

IEEE 1588-2008 Traffic Impact
Message Packet Sizes In-band Traffic Rate
Signaling (request) 96 bytes (54) Using the following typical values:
Signaling (ACK/NACK) 98 bytes (56)
Announce message 106 bytes (64) Announce interval 1 per second
Sync message 86 bytes (44) Sync interval 64 per second
Follow_Up message 86 bytes (44) Lease duration 300 seconds
Delay_Resp(onse) 96 bytes (54) Delay_Req(uest) 64 per second
Delay_Req(uest) 86 bytes (44) Delay_Resp(onse) 64 per second
Peak traffic transmitted in one second:

(96x3)+(98*3)+106+64x(86+96+86)
= 17840 bytes
= 0.017% of Fast Ethernet (100mbps)
= 0.00166% of GigE
() 1588 only message size in bytes.

Overview

On-Path Support
Management Messages
1588 Modes

► In lieu of signaling, the
Grandmaster is self-declared,
based on user priority, clockClass…
and the lowest clockid.
► Interval & lease are set by the user
in the Grandmaster. Ordinary Clock 1
► Ordinary clocks have 3 modes:

► Grandmaster only (never syncs
Network Ordinary Clock 2
to 1588 flows)
► Slave only (can never function as
a Grandmaster)
► Grandmaster or slave (roles are
Ordinary Clock 3
changeable)

Best Master Clock Selection
When an Ordinary Clock (1) comes
on-line it looks for a Grandmaster

(announce messages). Priority 1
GPS Reference
► If after 3x announce_timeout there Grandmaster
Passive Mode
is no announce, the clock 1
becomes the Grandmaster. Ordinary Clock 1
Delay_resp
Announce
► If there is a lower priority/class
Sync
Priority 1
Grandmaster, the Clock 1 takes GPS Reference
Grandmaster
over the role of Master. Delay_resp
Sync
Network
► Otherwise the Clock monitors the Ordinary Clock 2
Announce
announce messages for a change
of state.
Consider the example where
Ordinary Clock 1 loses the GPS Ordinary Clock 3
reference (change of state):
► clockClass is reduced from 6 to 7
► Clock 2 assumes Grandmaster
mode. Clock 1 enters passive

state.
Multicast Time Transfer Technique
Master Clock Slave Clock Data At Round Trip Delay
Slave Clock RTD = (t2 - t1) + (t4 - t3)
Offset:
(slave clock error and one-way path delay)
OffsetSYNC = t2 – t1
t1 Leap second offset
OffsetDELAY_REQ = t4 – t3
Switch/Router Layer
t2 t2 (& t1 for 1-step)

We assume path symmetry, therefore
t1,t2 One-Way Path Delay = RTD ÷ 2
t3 t1, t2, t3 Slave Clock Error = (t2 - t1) - (RTD ÷ 2)
t4 Key difference from Unicast

Notes:
1. No signaling occurs. Sync interval is pre-
determined, & lease is infinite.
t1, t2, t3, t4
2. One-way delay cannot be calculated
exactly, but there is a bounded error.
Time
Time
3. The protocol transfers TAI (Atomic Time).

UTC time is TAI + leap second offset from
the announce message.
The process is repeated up to 128 times per second.
Overview

On-Path Support
Management Messages
1588 Modes

On-Path Support
On-Path Support In Context On-Path Support Elements
 Packet Delay Variation (~jitter) has Transparent Clock (switch not a clock)
largest impact on PTP accuracy.  Measures Sync packet delay
inside the switch (residence time)
 PDV is determined by bandwidth
 Modifies (adds) residence time to the
utilization & store & forward buffers
correction field in the PTP message
 Transparent & boundary clocks reduce
jitter introduced by switches & routers. Boundary Clock (switch & clock)
 Improve accuracy (over fixed path),  Internal clock synchronized via PTP to
the upstream master (slave)
 Increase path for fixed performance
 Regenerates PTP messages (master)
 Slave on 1 port, master on other ports
 On-path support is not necessary for

typical frequency applications
 ITU-T Telecom profile does not call for
on-path support.

Overview

On-Path Support
Management Messages
1588 Modes

IEEE 1588 Management Messages

IEEE 1588 Management Support
Our Grandmaster /Slaves respond to the following management messages:
► null management (primarily for testing/results in no change in operation)
► CLOCK DESCRIPTION (provides serial number, type, manufacturer, etc.
of the clock element)

► ACCEPTABLE_MASTER_TABLE (who the Grandmaster candidates are).
Symmetricom supports two entries per slave.

Private Symmetricom messages supported include:
► Reboot. 1588 specifies initialize, but resetting clocks has a large impact on
the network, and the private reboot command is more secure.

► Upgrade (updates the clock firmware)
► Status (provides information on locked condition, whether in alarm state,
holdover status, and other performance data collected).

► Alarm (alarm status)
Bulk upgrade & reboot significantly reduces the time, effort, and
configuration management complexity for high density slave deployment.
IEEE 1588 Management Support
► IEEE 1588 includes management
capability.
► Network security is complex & varied.
► Management through the Network 1
Grandmaster reduces
Slave
security & deployment complexity.
Network 2
Timing & Management (1588)

Slave
VLAN 1
Switch Slave
VLAN 4
Slave
Master Clock
TimePictra Management
Overview

On-Path Support
Management Messages
1588 Modes

IEEE 1588 Routing Options
Multicast Unicast
► Grandmaster broadcasts PTP packets ► Grandmaster sends PTP packets
to a Multicast IP address. directly to PTP slaves.
► Switches/Routers… ► Switches/Router forward PTP packets
► With IGMP snooping, forwards directly to slaves.
multicast packets to subscribers. ► Unicast Sync Interval; Telecom Profile:
► Without IGMP snooping all multicast ► User defined Sync interval up to
traffic broadcast to all ports. 128Hz.
► Multicast Sync Interval; Default Profile: ► Many subscribers supported.
► 0.5 Hz, 1Hz & 2 Hz (1 packet/ 2
seconds up to 2 packets/second).
Multicast (1:group) Unicast (1:1)

The IEEE 1588 Modes
Dynamic Allocation Static Allocation
The slave initiates the session with the The master is manually programmed to
Master, and the lease is assigned by the provide sync (and announce) messages
master. The master provides sync (and to a pre-determined slave continuously.
announce) messages for the lease The interval rate is programmed in the
duration at the interval rate. master.
MASTER MASTER
No signaling. No lease.
Slave signaling negotiates lease
& interval. Session is created Session programmed into the
and terminated dynamically by Grandmaster for a specific slave
the Grandmaster. (static) at a fixed interval, with
non-terminating lease.
SLAVE SLAVE
Most common allocation type. Limited application because of

configuration management complexity.
Useful for Lab applications.
The IEEE 1588 Modes
End-to-End Peer-to-Peer
Concerned about the end-end delay, and The link delay is determined, and
corrects the full path delay at the slave. corrected in each stage.
MASTER MASTER
Link delay determined &
corrected in each stage
Link delay determined &

corrected in each stage
Total link delay determined & Link delay determined &

corrected by the Slave corrected in each stage
SLAVE SLAVE
Typical for Telecom application. The peer-to-peer mode is typically used

when deploying transparent clocks in the
network.

1588 clockClass (Stratum)
A New Definition for Clock Accuracy
Telecom Definition Timing Definition IEEE 1588 Definitions
A measure of the frequency A measure of the distance clockClass (called stratum

accuracy of the oscillator or from the UTC traceable model in v1) represents the
clock being described. source (number of steps) quality of the clock.
Stratum 1 G.811 Stratum 0 UTC source

Stratum 2 G.812 Stratum 1 Gets Time from Version 1 Version 2
Stratum 3E G.812 Stratum 0 source 0 6
Stratum 3 G.813 Stratum 3 Timed from 1 9
Stratum 4 G.813 Stratum 2 source 2 10
Stratum 4 Timed from 3 248
Stratum 3 source
4 251
255 255

1588 clockClass (Stratum)
clockClass Definition
0 Reserved to enable compatibility with future versions
1-5 Reserved
6 Clock synchronized to a Primary Reference time source
7 Clock previously in clockClass 6 but is in holdover within holdover specs.
8-12 Reserved
13 Clock synchronized to the application time of source. Time scale is arbitrary.
14 Clock previously in clockClass 13 but is in holdover within holdover specs
15-186 Reserved or use by alternate PTP profiles
187 Clock previously in clockClass 7 but not within holdover specs. May be slave to
another clock
188-192 Reserved
193 Clock previously in clockClass 14 but not within holdover specs. May be slave to
another clock
194-254 Reserved for alternate PTP Profiles
255 Slave only clock
IEEE Std 1588-2008, Table 5

Overview

On-Path Support
Management Messages
1588 Modes

Influences on IEEE 1588 Accuracy
► Packet Delay Variation (PDV) appears
as a change in frequency or phase of
the recovered clock. 1588
► Increases with number of network
OSI Stack
UDP
elements and traffic load. 1588
IP
► Multiple causes, including queuing
OSI Stack
UDP
delays, routing changes, Ethernet
IP
congestion, use of switches versus
routers, etc. Ethernet
Receive
► Network asymmetry queue
► Prolonged Packet Loss (Outage).

Receive
► Causes clock recovery process to queue Transmit
queue
Receive
enter holdover. queue
► Local oscillator quality (part of the Transmit

queue
filtering process) Transmit
queue
► Packet Delay, Packet Loss, and
Packet Errors are not an issue for
packet timing protocols.
Overview

On-Path Support
Management Messages
1588 Modes

Conclusions
IEEE1588-2008 is a viable means for repairing the broken synchronization
chains through packet networks.
The Road Ahead is about implementing Packet Time.

► The protocol has reached specification maturity.
► Characterize the behavior of different physical layer(s) on the end-end

performance of the system through field trials and laboratory studies.
► G.8261 standard test configurations & result database.
► Build a knowledgebase and empirical deployment guidelines.
► Develop high performance client algorithms and default profiles for
different transport technologies (xDSL, Ethernet on SDH, …).

► Network planning deployment guidelines.

Thank You For Your Time …
Symmetricom
2300 Orchard Parkway
San Jose, California, 95131
United States of America
www.symmetricom.com

Commonly Used Terms
Meanings of common terms used in IEEE 1588

Boundary clock A boundary clock is a clock with more than a single PTP port, with each PTP port
providing access to a separate PTP communication path. Boundary clocks are used to
eliminate fluctuations produced by routers and similar network elements.
Clock A device providing a measurement of the passage of time since a defined epoch. There
are two types of clocks in 1588: boundary clocks and ordinary clocks.
Clock timestamp 1588 requires the generation of a timestamp on transmission or receipt of all 1588 Sync
point and Delay_Req messages. The point in the outbound and inbound protocol stacks
where this timestamp is generated is called the clock timestamp point.
Direct The communication of PTP information between two PTP clocks with no intervening
communication boundary clock is termed a direct communication.
External It is often desirable to synchronize a single clock to an external source of time, for
synchronization example to a GPS system to establish a UTC time base. This synchronization is
accomplished by means other than those specified by 1588 and is referred to as
external synchronization
Epoch The reference time defining the origin of a time scale is termed the epoch.
Grandmaster Within a collection of 1588 clocks one clock, the grandmaster clock, will serve as the
clock primary source of time to which all others are ultimately synchronized.
http://ieee1588.nist.gov/terms.htm

Commonly Used Terms

Master clock A system of 1588 clocks may be segmented into regions separated by boundary clocks.
Within each region there will be a single clock, the master clock, serving as the primary
source of time. These master clocks will in turn synchronize to other master clocks and
ultimately to the grandmaster clock.
Message 1588 Sync and Delay_Req messages contain a distinguished feature, the message
timestamp point timestamp point, serving as a reference point in these messages. When the message
timestamp point passes the clock timestamp point, a timestamp is generated that is
used by 1588 to compute the necessary corrections to the local clock
Ordinary clock A clock that has a single Precision Time Protocol (PTP) port in a domain and maintains
the timescale used in the domain. It may serve as a source of time, i.e., be a master
clock, or may synchronize to another clock, i.e., be a slave clock.
Preferred master 1588 allows the definition a set of clocks that will be favored over those not so
clock set designated in the selection of the grandmaster clock.
PTP PTP is an acronym for Precision Time Protocol, the name used in the standard for the
protocol.
PTP domain A PTP domain is a collection of one or more PTP sub domains. A sub domain is a logical
grouping of 1588 clocks that synchronize to each other using the PTP protocol, but that
are not necessarily synchronized to PTP clocks in another PTP sub domain. Sub
domains provide a way of implementing disjoint sets of clocks, sharing a common
network, but maintaining independent synchronization within each set.
Commonly Used Terms

PTP message There are five designated messages types defined by 1588: Sync, Delay_Req, Follow-
up, Delay_Resp, and Management
Multicast 1588 requires that PTP messages be communicated via a multicast. In this style of
communication communication any node may post a message and all nodes in the same segment of a
sub domain will receive this message. Boundary clocks define the segments within a
sub domain.
PTP port A PTP port is the logical access point for 1588 communications to the clock containing
the port.
Synchronized Two clocks are synchronized to a specified uncertainty if they have the same epoch and
clocks measurements of any time interval by both clocks differ by no more than the specified
uncertainty. The timestamps generated by two synchronized clocks for the same event
will differ by no more than the specified uncertainty.

Ieee 1588 Anew Vocabulary

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ieee 1588 Anew Vocabulary

Hochgeladen von

Copyright:

Verfügbare Formate

IEEE 1588-2008

UNDERSTANDING THE IEEE 1588 PRECISION TIME PROTOCOL

Introduction to IEEE 1588

© COPYRIGHT SYMMETRICOM (2009) PAGE 2

► over the industrial Ethernet

© COPYRIGHT SYMMETRICOM (2009) PAGE 3

Image courtesy of National Instruments

Protocol ref. Oxford English Dictionary

© COPYRIGHT SYMMETRICOM (2009) PAGE 6

► Separate announce message (lower frequency);

► Provision for Grandmaster and network failures

► Transparent clocking through 1588-aware network equipment.

© COPYRIGHT SYMMETRICOM (2009) PAGE 7

50nS) time-of-day precision over 3µs inter-cell

© COPYRIGHT SYMMETRICOM (2009) PAGE 8

master & slaves, and

Hardware-Assisted Time Stamping

as it passes between the PHY and the MAC.

Best Master Clock (BMC) Algorithm.

© COPYRIGHT SYMMETRICOM (2009) PAGE 9

WIDE AREA NETWORK

LOCAL AREA NETWORK

Synchronous Ethernet Microwave Transport

© COPYRIGHT SYMMETRICOM (2009) PAGE 12

© COPYRIGHT SYMMETRICOM (2009) PAGE 13

► Acknowledge TLV (ACK) ► Request announce

► Negative Acknowledge TLV (NACK) ► Request sync

► Announce message ► Request delay_resp(onse)

► Sync message ► Delay_Req(uest)

Message Headers entering the PHY are the “on-time” marker

© COPYRIGHT SYMMETRICOM (2009) PAGE 14

Introduction to IEEE 1588

© COPYRIGHT SYMMETRICOM (2009) PAGE 15

Master/Server Master Clock Slave Clock Slave/Client

IEEE 1588 Processor IEEE 1588 Processor

PROCESS SET’S UP THE

The process is repeated before the lease expires

Lease Duration in Bytes (10-1000s for Telecom Profile)

t2 t2 (& t1 for 1-step)

t3 t1, t2, t3 Slave Clock Error = (t2 - t1) - (RTD ÷ 2)

The process is repeated up to 128 times per second.

t1 Sync message is sent at t = 100 seconds

t2 t1 = 100 seconds after the Sync message is received:

Slave Clock Error = (t2 - t1) - (RTD ÷ 2)

Round trip error eliminated

If the slave clock is adjusted by -50 seconds,

Leap Second Information

Grandmaster Clock Type

© COPYRIGHT SYMMETRICOM (2009) PAGE 21

© COPYRIGHT SYMMETRICOM (2009) PAGE 22

► The unique clockID is the tie-breaker.

© COPYRIGHT SYMMETRICOM (2009) PAGE 23

© COPYRIGHT SYMMETRICOM (2009) PAGE 24

© COPYRIGHT SYMMETRICOM (2009) PAGE 25

© COPYRIGHT SYMMETRICOM (2009) PAGE 26

Estimated value of Real value of

The follow_up message is helpful when hardware time

© COPYRIGHT SYMMETRICOM (2009) PAGE 27

Peak traffic transmitted in one second:

() 1588 only message size in bytes.

© COPYRIGHT SYMMETRICOM (2009) PAGE 28

Introduction to IEEE 1588

© COPYRIGHT SYMMETRICOM (2009) PAGE 29

► Ordinary clocks have 3 modes: