If you work with industrial networking, automation, TSN, robotics, or smart manufacturing, you've probably come across terms such as:

• SyncE
• NTP
• PTP
• IEEE 1588
• gPTP
• IEEE 802.1AS
• TSN

Many industrial switches and network devices now advertise features like:

• IEEE 1588v2 Support
• gPTP Support
• TSN Ready
• SyncE Support

But if someone asks:

What exactly is the relationship between all these technologies?

Many engineers find themselves in a familiar situation:

• I've heard of them.
• I've configured them.
• I've seen them in datasheets.
• But explaining how they fit together isn't always easy.

This article aims to simplify the picture.

No protocol deep dives.

No packet-level analysis.

Just one simple question:

What exactly are we synchronizing when we talk about "time synchronization" in industrial networks?

A Simple Question

Imagine three devices on the same network:

• A PLC
• An Industrial Camera
• A Server

All of them display:

2026-06-11 10:00:00

Are they synchronized?

Most people would immediately answer:

Yes.

The reality is:

Not necessarily.

Because time synchronization actually consists of three different layers.

Layer 1: Running at the Same Speed

Suppose:

Clock A:

1 second = 1 second

Clock B:

1 second = 0.999999 seconds

Initially, the difference is almost invisible.

After a day, it becomes noticeable.

After weeks or months, the clocks drift significantly apart.

Even if they appear synchronized now, they are not running at the same frequency.

This is the first challenge.

Layer 2: Knowing the Correct Time

Even if all clocks run at exactly the same speed, devices may still disagree about the current time.

For example:

Device A:

10:00:00

Device B:

09:59:50

They run at the same speed.

But they started from different references.

They are still not synchronized.

Layer 3: Acting According to the Same Timeline

This is where industrial real-time networking becomes truly challenging.

Imagine:

A robot controller must transmit commands every:

1 ms

An industrial camera must capture an image at:

10:00:00.001

A motion controller must execute an action at:

10:00:00.002

Now synchronization is no longer just about knowing the time.

It is about ensuring that every device operates according to the same timeline.

This Is Why Different Technologies Exist

Each technology solves a different synchronization problem.

SyncE: Synchronizing Frequency

OSI Layer

Layer 1 (Physical Layer)

Full Name

Synchronous Ethernet

What Does It Do?

SyncE solves one problem:

Frequency synchronization.

Simply put:

It ensures all clocks run at the same rate.

It does not care about:

What time is it?

It only cares about:

Are all clocks ticking at the same speed?

A Simple Analogy

Imagine a group of runners.

SyncE ensures:

Everyone runs at the same pace.

But nobody knows where the finish line is.

Typical Applications

• 5G Networks
• Carrier Ethernet
• Utility Communications
• Power Grid Networks

NTP: Synchronizing Time

OSI Layer

Layer 7 (Application Layer)

Full Name

Network Time Protocol

What Does It Do?

NTP helps devices answer:

What time is it?

Examples include:

• Windows Time Synchronization
• Linux NTP Services
• SCADA Systems
• OpenNMS
• Enterprise Servers

Typical Accuracy

Usually:

• 1 ms to 10 ms

Sometimes better.

Advantages

• Simple
• Universally Supported
• Easy to Deploy

Limitations

Accuracy is often insufficient for real-time industrial applications.

PTP: Precision Time Synchronization

OSI Layer

Layer 2 or Layer 3

Full Name

Precision Time Protocol

IEEE 1588

Why Was PTP Developed?

Many industrial applications eventually reached the limits of NTP.

Examples include:

• Power Protection Systems
• Industrial Robotics
• Multi-Camera Vision Systems
• High-Speed Manufacturing

These applications require:

• Microsecond-level accuracy
• Sometimes nanosecond-level accuracy

The Biggest Difference

The key innovation is:

Hardware Timestamping

Instead of relying on software timestamps, timing information is generated directly by:

• PHY Devices
• Network Interfaces
• Switch ASICs

This dramatically improves synchronization accuracy.

Think of It This Way

NTP:

People comparing watches.

PTP:

People comparing atomic clocks.

gPTP: The Timing Foundation of TSN

OSI Layer

Layer 2

Standard

IEEE 802.1AS

Why Do We Need gPTP If We Already Have PTP?

PTP is highly flexible.

Different vendors can implement different profiles and behaviors.

As a result:

Two devices may both support PTP but still struggle to interoperate.

IEEE 802.1AS (gPTP) was introduced to solve this problem.

You can think of it as:

A TSN-optimized version of PTP.

It standardizes:

• Synchronization methods
• Delay measurements
• Master clock selection

allowing devices from different vendors to work together more effectively.

TSN: Scheduling Traffic by Time

One of the biggest misconceptions is:

TSN is a time synchronization protocol.

It is not.

TSN stands for:

Time-Sensitive Networking

TSN is a family of standards.

Examples include:

TSN
├── 802.1AS (gPTP)
├── 802.1Qbv
├── 802.1Qbu
├── 802.1CB
└── ...

Within TSN:

gPTP provides:

A common notion of time.

802.1Qbv provides:

Time-aware scheduling.

802.1Qbu provides:

Frame preemption.

802.1CB provides:

Redundancy and reliability.

Therefore:

TSN is not gPTP.

Instead:

gPTP is one component of TSN.

Visualizing the Relationship

Traffic Scheduling
        ↑
       TSN
        ↑
      gPTP
        ↑
       PTP
        ↑
       NTP

Frequency Synchronization
        ↑
      SyncE

One Simple Analogy

Imagine an orchestra.

SyncE

Ensures every musician plays at the same tempo.

NTP

Tells everyone when the concert starts.

PTP

Provides highly accurate clocks for every musician.

gPTP

Ensures everyone follows the same timing standard.

TSN

Ensures every instrument plays the correct note at the exact right moment.

Final Thoughts

For years, industrial networking focused on one challenge:

Can devices communicate?

Today, the challenge is evolving into:

Can devices operate within the same timeline?

From SyncE to NTP, from PTP to gPTP, and ultimately TSN, each technology addresses a different aspect of synchronization.

Together, they form the foundation of next-generation deterministic industrial networking.

In future articles, we will explore:

• How IEEE 1588 was developed
• What makes gPTP different from standard PTP
• Why TSN is considered the future of Industrial Ethernet
• The role industrial switches play in building time-aware networks

Stay tuned. The future of industrial networking is not only connected.

It is synchronized.