2007 International IEEE Symposium on Precision Clock Synchronization (ISPCS)

for Measurement, Control and Communication

Vienna, Austria, October 1-3, 2007.

IEEE-1588 and Synchronous Ethernet in Telecom

Silvana Rodrigues
Zarlink Semiconductor
400 March Road
Ottawa, ON, Canada
silvana.rodrigues @zarlink.com

Abstract

The packet-based methods rely on timing

information carried by the packets. In this case the
timing can be carried by dedicated time stamp
messages using the IEEE-1588 [6], the Precision Time
Protocol (PTP). PTP uses time stamps for
synchronizing clocks in the network in a master-slave
hierarchy. IEEE1588 [6] can be used to distribute
frequency and/or Time-of-Day (ToD) information.
The Synchronous Ethernet method uses the physical
layer to transport synchronization. Synchronous
Ethernet is based on a well-established SONET/SDH
synchronization distribution model. These methods are
widely implemented to synchronize the TDM
networks.
If PTP is deployed only at the end nodes (i.e.; at the
master and slave nodes), then the synchronization
performance can be affected by impairments of the
telecom network, such as packet delay variation

Service Providers are moving from voice services to

bundled services, delivering voice, data, video and
wireless (Quad-play). TDM services continue to
represent significant revenue for carriers, and must be
supported in this new model. As the network moves to a
Packet Switched infrastructure, there are still
applications that require synchronization, e.g.;
traditional TDM services, cellular basestations. Timing
synchronization is key to distributed networks and it is
critical for today's network environments. As the
network services continue to increase, the challenges
involved with providing accurate time to systems and
applications also increase. This paper addresses the
use of IEEE1588CM in conjunction with Synchronous
Ethernet to deliver accurate synchronization for the
Telecom Network.

(PDV).

In cases where the network is very noisy (high

PDV), and there is a need to have carrier-class
synchronization, phase alignment and/or ToD,
Synchronous Ethernet can be used to deliver frequency
and IEEE-1588 [6] can be used to deliver phase
alignment and/or ToD.

1. Introduction
In current networks, synchronization is transported
and distributed by TDM networks. As the network
evolves, legacy equipment with TDM interfaces (i.e.,
STM-N) will be mixed with Gigabit Ethernet
interfaces.
There are emerging technologies, including CES
(Circuit Emulation Services), which are designed to
transport synchronous circuits, such as TI/El, over
asynchronous networks. This type of technology will
benefit from the transport of accurate clocks over the
packet network.
There are several methods to transport a clock from
one node to another in packet networks.
The ITU-T G.8261 Recommendation - Timing and
Synchronization Aspects in Packet Networks [2],
defines several modes for clock distribution and clock
recovery. G.8261 [2] describes packet-based methods
and the Synchronous Ethernet method.

2. Synchronous Ethernet
2.1. Synchronous Ethernet concept
In the case of Synchronous Ethernet based methods,
the the physical layer of the Ethernet is used to
transport synchronization. The clock signal can be
generated from "bit stream" in a similar manner as it is
generated in traditional SONET/SDH/PDH networks.
Each node in the Packet Network that is part of the
Synchronous Ethernet (SyncE) chain recovers the
clock from the upstream node and distributes the clock
to the downstream node by relying on the transport of
the clock through the physical layer. Because
Synchronous Ethernet uses the physical layer of
Ethernet to recover the timing, it can only distribute
frequency; it can't distribute ToD or phase alignment.
The performance of the recovered clock is independent

IEEE-1588TM is trademark of its respective owner

1-4244-1 064-9/07/$25.00

2007 IEEE

138

ITU-T G.8262 [1] recommendation describes all the

clock characteristics that must be met; it specifies
requirements such as clock accuracy, noise transfer,
holdover performance, noise tolerance, and noise
generation. Synchronous Ethernet clock distribution
can be considered an extension of the current
synchronization distribution network. One important
aspect of Synchronous Ethernet is that it does not
impact any existing IEEE 802.3 specifications such as
frequency tolerance, but adds new network element
clock functionality.
ITU-T G.8262 [1] EEC-Option 1 is based on the
Option 1 clock from ITU-T G.813 Recommendation
[7], and EEC-Option 2 is based on the Type IV clock
from ITU-T G.812 Recommendation [8]. Jitter
generation and jitter tolerance for Ethernet interfaces
for EEC-Option 1 and EEC-Option 2 are based on
IEEE 802.3.
An additional mechanism is also needed to provide
the clock quality to the end nodes in order to detect and
correct network synchronization failures. The
mechanism used in current SONET/SDH networks is
Synchronization Status Messaging (SSM). SSM is
defined in ITU-T G.707 - Network Node Interface for
the Synchronous Digital Hierarchy (SDH) [3] and ITUT G.781 - Synchronization Layer Functions [4]. SSM
can also be used for Synchronous Ethernet to convey
timing quality information for the downstream Ethernet
switches. If upstream network synchronization failure
occurs the synchronization function processes the SSM
and takes appropriate action to select a new timing
reference. The channel to transport the SSM in
Ethernet networks is still being studied at ITU-T. It is
expected that the SSM will be defined and be part of a
new ITU-T recommendation that will be consented in
February 2008.

of network loading and is not influenced by any

impairments associated with the packet network (e.g.,
queuing, routing, PDV, etc).
Figure 1 shows the concept of Synchonous
Ethernet.
Node 1
Data

---

F2----

Node2

Node3

taye-2-7-

-eFZ4-

Data

1.1- -i UP
PRC

tacebl
tracable

_-o

--

SycE

--L

DPLL

I!

SycE
DPLL

coveredl

* dock

Synchronization Path
Data Path

Figure 1. Synchronous Ethernet Concept

In figure 1, a Primary Reference Clock (PRC)
traceable reference is injected into the Synchronous
Ethernet (SyncE) Digital Phase Lock Loop (DPLL).
The DPLL provides jitter and wander filtering, and
also translates telecom clocks to Ethernet clocks. The
output of the DPLL is also used to drive the clock of
the Ethernet PHY. On the second node, the PRCtraceable clock can be extracted at the receive path of
the Ethernet PHY. The DPLL provides the wander and
jitter filtering and the output of the DPLL is used to
drive the Ethernet PHY. At the third node, in this
example the last node, the PRC-traceable clock can be
extracted at the receive path of the Ethernet PHY. The
DPLL provides jitter and wander filtering and also
translates Ethernet clocks to Telecom clocks. The
output of the DPLL is used to drive the system clock at
the end node. The example above includes 3 nodes, but
this can be repeated for several nodes as long as it
follows the synchronization specifications as described
in ITU-T G.8262 - Timing Characteristics of
Synchronous Ethernet Equipment Slave Clock (EEC)
[1]. The new ITU-T G.8262 [1] standards consented in
June 2007 specifies all related requirements for
Synchronous Ethernet.

3. Packet-Based Methods
3.1. Packet-Based Method Concept
In the case of packet-based methods, the timing
information is transported by the packets, or Timing
over Packet (ToP). The clock is encoded in the packets
and is transported either at Layer 2 or Layer 3,
independent of the Physical Layer. In this case the
Packet Network is 'transparent" regarding the
synchronization, and ToP methods can be deployed
only at the 'end' points - the master and the slave.
Examples of protocols used to transport Timing over
Packet are NTP, RTP and IEEE1588 [6]. IEEE1588 [6]
is emerging as one of the preferred choices to be used
for Telecom Networks.
Figure 2 depicts the concept of ToP.

2.2. ITU-T G.8262 [1] Standard

Two clock options for Synchronous Ethernet are
specified in the ITU-T G.8262 [1] recommendation.
One of the options is described as "EEC-Option 1".
EEC-Option 1 was specified for Synchronous Ethernet
equipment that is designed to interwork with networks
optimized for the 2048 kbit/s hierarchy. The other
option is described as "EEC-Option 2". EEC-Option 2
was specified for Synchronous Ethernet equipment that
is designed to interwork with networks optimized for
the 1544 kbit/s hierarchy.

139

FFR
taEie
dock

Eda-

TCP
E[}JL T1hT
F

----------------

Lae2- 7

&t

_____-i-

*kds

R-tff-e

LaW2- 7

-_

R-t(La,

Version 2 of the standard includes key features for

Telecom. It allows the message to be transmitted in
Unicast, defines a Unified Frame format, allows Fault
Tolerant Clocks, and allows different methods for
Master clock selection. However, a Telecom profile
still needs to be defined. The profile is a set of required
options, prohibited options, and the ranges and defaults
of configurable attributes. As defined in the draft
standard "An IEEE-1588 profile may be developed by
external organizations including:
a) A recognized standards organization with
jurisdiction over the industry, e.g. IEC, IEEE, IETF,
ANSI, ITU, or;
b) An industry trade association or other
similar organization recognized within the industry as
having standards authority for the industry;
c) Other organizations as appropriate."
ITU-T is currently working on the definition of an
IEEE-1588 Telecom profile.
IEEE-1588 [6] describes a protocol for
synchronization, but it does not address any
performance requirements. Also a proper algorithm has
to be implemented in the slave devices to handle PDV
if the packet-switched network has switches and
routers that do not support the PTP standard (the
switches and routers do not support Transparent Clocks
or Boundary clocks). In this case the IEEE-1588 [6]
timing packets will go through the packet-switched
network, but it will only be handled at the master and
slave nodes. These algorithms are usually based on
adaptive clock recovery.

-EAa

TOP'R_

dok

EdaP&h

Figure 2. ToP Concept

In figure 2, a PRC traceable reference is injected
into the ToP DPLL. The ToP DPLL generates timing
packets as defined in the IEEE1588 [6] standards;
those IEEE1588 [6] timing packets contain the timing
information and are transmitted in the packet-switched
network. At the slave node, the ToP DPLL runs an
algorithm to recover the clock from the IEEE1588 [6]
timing packets, the recovered clock is locked to the
PRC traceable clock at the Master node. The algorithm
to recover the clock at the slave node is out of scope of
the 1588 standard, so it is proprietary.

3.2. IEEE-1588 [6]

IEEE-1588 - Standard for a Precision Clock
Synchronization Protocol for Networked Measurement
and Control Systems was approved in September 2002
and published November 2002 [5]. It defines a
Precision Time Protocol (PTP) designed to synchronize
real-time clocks in a distributed system. The 2002
version of IEEE-1588 [5] was intended for Local Area
Networks using multicast communications (including
Ethernet). IEEE-1588 [5] was designed to work within
a building or factory to address typically Industrial
Automation and Test and Measurement Systems.
IEEE-1588 [5] was designed to target an accuracy of
microsecond to sub-microsecond. PTP uses time
stamps for synchronizing clocks in the network; the
clocks are arranged in a master-slave hierarchy. PTP
also defines a Boundary Clock that is typically a multiport device. The Boundary Clock is used to translate
the PTP protocol messages between regions by
implementing different transport and messaging
protocols.
A Project Authorization Request (PAR) was
approved in March 2005 to work on a second revision
of the IEEE1588 [5] standard. The PAR includes
of known
resolution
conformance
errors,
enhancements, and enhancements to address new
applications (including Telecom). A new type of
IEEE1588 clock was introduced in version 2 that is
called Transparent Clock. Two types of transparent
clocks are defined as End-to-End and Peer-to-Peer
Transparent Clock. The Peer-to-Peer Transparent
Clock differs from the End-to-End Transparent Clock
in the way it corrects and handles the PTP timing

3.2.1. Adaptive Clock Recovery [10]

One of the simplest form of adaptive clock recovery
is based on packet arrival times (or inter-arrival times).
In this case, the clock rate can be inferred by averaging
the arrival rate of the packets over a period of time.
The arrival rate is recorded and the mean rate is
calculated and compared to the rate of a local
oscillator. The frequency of the digital controlled
oscillator is then adjusted to match the master clock
frequency. The variation in the transit delay of packets
that transverse the network causes jitter effects. These
jitter effects will introduce noise into the recovered
clock, which needs to be removed. To remove the jitter
effects, the averaging period of the arrival rate has to
be sufficiently long.
For this type of adaptive clock recovery it may be
difficult to recover a clock that stays with the
specification of wander requirement because it depends
on the characteristics of the packet network, In this
type of scheme any variation in delay between packets
will feed through as a variation in the frequency of the
recovered clock. It is easy to filter high frequency
Jitter, but any low frequency variation or wander is
more difficult to remove without a filer with very long

messages.

140

time constant. This will make the locking time not

acceptable for some applications.
There are other methods for ACR that are based on
non-linear filtering. Several non-linear filtering
approaches have been reported. Several methods can
be used, for example, "pre-conditioning" the packet
delay estimates, packet selection techniques to select
"good" timing packets, use of time-invariant property
of the delay variation to estimate the frequency of
packet arrival. By applying these non-linear filtering
techniques performance can be greatly improved.
Further improvements can be achieved by using high
priorities settings for the timing packets, such that the
delay variation through the network is reduced. Very
good results have been reported throughout the
industry by using these types of methods.

3.3. IEEE-1588 [6] and Synchronous Ethernet in

Telecom

3.3.1. IEEE-1588 [6] used in combination of

Synchronous Ethernet Network
Several emerging Telecom applications need to
maintain phase alignment (and/or ToD) in many places
of the network with very stringent requirement. For
example, for 3GPP CDMA Base Stations the time
alignment error should be less than 3 vs and shall be
less than 10 his.
IEEE-1588 [6] can transport ToD and frequency,
but if IEEE-1588 [6] is only deployed at the end nodes
of the network (master and slave nodes) then it can be
affected by impairments of the telecom network, such
as PDV. Multiple causes can contribute to PDV,
including queuing delays, routing changes, congestion,
etc. Some Telecom networks have very high PDV; so
using Synchronous Ethernet that is based on a wellknown technology (similar to SONET/SDH
synchronization) will guarantee carrier-class frequency
synchronization. However, Synchronous Ethernet can
only distribute frequency, it cannot distribute ToD, but
it may significantly enhance the quality of the time

transferred by IEEE-1588 [6]. Concurrently using

Synchronous Ethernet to distribute frequency and
IEEE-1588 [6] to distribute ToD may allow very
stringent phase alignment requirements to be met.

3.3.2. IEEE-1588 [6] used to extend the

Synchronous Ethernet Network
Incumbent Telecom Carriers are very familiar and
comfortable with the current synchronization network
being distributed using the physical layer.
Synchronization is key for the proper function of the
network today and service providers want a reliable
way to extend and distribute synchronization in nextgeneration networks.
Synchronous Ethernet can be used to distribute
synchronization from the core of the network to the
edge. IEEE-1588 [6] can be used to extend the
synchronization chain from the edge to the access of
the network. Figure 3 depicts a diagram that shows the
concept of IEEE-1588 [6] being used to extend the
synchronization at the access.
In Figure 3 [9], the PRC is located in the core of the
network. Synchronous Ethernet is used to distribute a
traceable PRC reference clock to the edge of the
network. At the edge, an IEEE-1588 [6] device will be
used to lock to the Synchronous Ethernet clock and
generate timing packets according to version 2 of
IEEE-1588 [6] standards to distribute synchronization
to the access devices.

References
[1]

[2]
[3]
[4]

ITU-T Recommendation G.8262 (2007), Timing

Characteristics of Synchronous Ethernet Equipment
Slave Clock (EEC).
ITU-T Recommendation G.8261 (2006), Timing and
Synchronization aspects in Packet Networks.
ITU-T Recommendation G.707 (2001), Network node
interface for the synchronous digital hierarchy (SDH)
ITU-T
Recommendation
G.781
(1999),
Synchronization layer functions

T--

Kernet

Figure 3. IEEE-1588 and Synchronous Ethernet

[5]

IEEE-1588 - Standard for a Precision Clock

Synchronization Protocol for Networked Measurement
and Control Systems
[6] IEEE P1588TM D2.1 Draft Standard for a Precision
Clock Synchronization Protocol for Networked
Measurement and Control Systems
[7] ITU-T Recommendation G.813
(2003), Timing
characteristics of SDH equipment slave clocks (SEC)
[8] ITU-T Recommendation G.812 (1998), Timing
requirements at the outputs of slave clocks suitable for
plesiochronous operation of international digital links.
[9] Silvana Rodrigues, "Combining Synchronous Ethernet
and IEEE-1588TM for use in Telecom", 2006
Conference on IEEE-1588
[10] Silvana Rodrigues, OPTXS-SYNC-2006-068, ATIS/
OPTXS contribution

142