Need of Synchronization:

Telecommunication networks are evolving from TDM networks based on circuitswitched technology to so-called Next Generation Networks (NGN) based on
packet-switching. The driver of this evolution is cost reduction; the technical goal
is the transport of all telecommunication services over a unified and packetswitched platform. Ethernet is already playing an important role in the network
convergence scenario. Ethernet started as a LAN technology for enterprise
networks, and is now being used in base station backhaul and aggregation
networks, and even in metro networks. It turns out that many access network
technologies require some form of synchronization. This is the case for all cellular
mobile networks which require their base stations to be synchronized. Some of
these technologies require synchronization of their equipment clocks in
frequency, some in phase.

IEEE 1588v2 PTP (Precision Time Protocol):

The Precision Time Protocol (PTP), also known as IEEE1588, is a standardized
protocol defined by the IEEE, coming initially from the automation world.
Two versions of PTP have been released:
IEEE-1588V1 exists since quite a long time, and is really targeting applications
others than telecom.
IEEE1588V2, approved by IEEE in 2008 (IEEE1588-2008), provides new features
that can be useful to telecom applications. However, there is a need to define in
details the options and parameters of PTPv2 in order to enable this protocol to be
used in a telecom environment. This is part of the so-called "telecom profiles"
definition.
ITU-T has defined a PTP telecom profile for end-to-end frequency distribution in
the Recommendations G.8265 and G.8265.1, released in 2010. End-to-end
means that the nodes in the synchronization path (the path the PTP packets
follow from the grandmaster to the slave) do not embed PTPv2 functions.
Other PTP telecom profiles are currently under definition at the ITU-T to address
the phase and time distribution by the network in the Recommendations G.827x.
These profiles will rely on the fact that all the nodes (full on path support) or only
some nodes (partial support) in the synchronization path embed PTPv2 functions.
ITU-T is currently defining two telecom profiles for phase and time delivery:

G.8275.1 is the phase/time profile assuming full on-path support i.e.

assuming that all equipments between the master clock and the slave clock
support PTPv2 functions (T-BC or T-TC), most likely the selection could be for
T-BC. This profile is expected to be finalized very soon (Probably in April
2014). A combination with Synchronous Ethernet is possible in order to
improve the performance and the time holdover in case of PRTC failure.

G.8275.2 is the phase/time profile assuming partial on-path support i.e.

assuming that not all equipments between the master clock and the slave
clock support PTPv2 functions. The discussion has only started on this
profile and its feasibility has first to be demonstrated before any work starts
on this recommendation. Therefore, at this point of time, this solution
should not be considered as an applicable solution to deliver phase and
time with the proper quality.