orolia.com EdgeSync Manual rev 1 | 59
rates, announce timeout, delay mechanism, datasets, etc. are customized per profile. This covers most
of it but for some of the profiles some additional parameters also need to be specified.
With EdgeSync, the user can select one of these PTP profiles for the timing engine to operate in. To
make it user friendly, once the profile is selected, internally EdgeSync software will set up the most of
the PTP profile specific parameters to default values for that profile and it is up to the customer if they
want to customize it further (like a power user).
Below is the list of PTP profiles that EdgeSync currently supports. More profiles will be added in future
releases and this documentation will be updated accordingly.
IEEE 1588 Default Profile
This is the profile that is specified by IEEE 1588 Standard itself. It uses domain 0, PTP over IPv4/UDP
and multicast mode of operation.
G.8275.1 Telecom Profile
This is one of the Telecom profiles specified by ITU-T and is recommended for new deployment or
green-field networks comprising switches. It is expected that every node or element in the network is
PTP-aware, or in other words, the network has full on-path support. This is used in conjunction with
Synchronous Ethernet (SyncE) which provides the physical layer frequency synchronization. G.8275.1
uses L2 (Ethernet) multicast as PTP transport layer. This is a better option as using the physical layer
assist for frequency and phase/time from PTP over packet network as it gives the best of both worlds.
With G.8275.1 profile and SyncE, a slave or the network is congruent if the PTP source and SyncE
source is traced back to the same Grandmaster. If they are not, then it is said to be non-congruent. In
either case, the SyncE frequency reference that is used by the slave should be traceable as specified in
the Quality Level (QL) value in the ESMC messages.
The figure below shows the details of G.8275.1 telecom profile.
Figure 31 G.8275.1 PTP profile
To Next Page
Loading...
General