IEEE 1588 PTP
Solutions with IEEE 1588 PTP for Network Switches, Routers, and Infrastructures
We enable the IEEE 1588 PTP support in software and hardware for diverse telecommunication devices. With advanced timestamping capabilities, our custom solutions align the clocks of various network elements with extremely low latency.
How Does It Work?
IEEE 1588 functions by exchanging two-way timing messages between the master and slave clocks. In these messages, the slave receives information about the time the master is on. The delay is easily determined in this process. Subsequently, the protocol estimates the one-way message delay by halving the round-trip delay.
Benefits of IEEE 1588 Synchronisation Protocol
IEEE 1588 synchronisation protocol is essential for coordinating and aligning various components or processes within a system. It provides real-time applications with the following information:
- Precise time-of-day (ToD) information
- Time-stamped inputs
- Scheduled and synchronised outputs
This protocol is the sole standardised terrestrial mechanism for delivering phase/time with the highest accuracy via a packet-based network. Its application areas include mobile networks, industrial process control, audio/video networks, smart energy distribution, transportation, automotive, and IIoT.
How Promwad Adopts This Technology
Promwad is silicon-agnostic: we architect timing subsystems around your chosen platform — Microchip, Realtek, NVIDIA, Qualcomm, and others. The reference implementation below uses Microchip SparX-5i Ethernet switches with Microchip 1588v2 and 10G PHYs; we apply the same approach to whatever silicon your product is built on.
The model range we employ:
- Ethernet switches: VSC7546TSN, VSC7549TSN, VSC7552TSN, VSC7556TSN, VSC7558TSN
- PHYs/10G PHYs: VSC8572, VSC8574
Software Development
IEEE 1588v2 PTP is integrated as an application-level module within the IStaX SDKs. It operates on Microchip Ethernet switch hardware and is supported by a rewriter, egress port modules, and timing-aware PHYs.
The PTP implementation encompasses the following features:
-
Ordinary and boundary clocks employing basic delay and peer-to-peer mechanisms
-
Peer-to-peer/end-to-end transparent clock
-
Local clock and servo
-
Best Master Clock (BMC) algorithm
By default, the protocol operates over Ethernet PTP using Ethernet multicast. It is possible to configure PTP over IPv4 multicast or unicast.
Supported Applications
PTP synchronisation profiles, introduced in IEEE 1588-2008, facilitate the adoption of PTP by various standards bodies (e.g. ITU-T, IETF, SMPTE, AES, IEC, Avnu, AUTOSAR, LXI, AIA) for specific applications such as financial/enterprise, professional broadcast, power industry, and test and measurement.
Our engineers enable support of the following profiles:
IEEE Std 1588-2019 for generic applications
G8275.1, G.8265.1 for telecom industry
IEEE Std 802.1AS for audio/video, industrial automation, and automotive applications
Our Tech Stack
IEEE 1588-2008 | IEEE 802.1AS-2020 | ITU-T G.8265.1 | ITU-T G.8275.1 | ITU-T G.8275.2 | SMPTE ST-2059-2
PHC | Timestamp unit | Servo | PPS in/out | GNSS | Ordinary clock | Transparent clock | Boundary clock
5G/6G telecom systems | Multimedia broadcasting | Financial trading | Industrial automation
Servo algorithm | two/one-step sync mode | e2e/p2p delay mechanism | l2/l4 transport | SyncE usage | Domain number | PHC time format | Messages timings | BMCA method | Unicast/Multicast
Microchip | Realtek | SiTime | NVIDIA | Qualcomm | Marvell
Bridging Eras of Timing: PTP, SyncE & Legacy Synchronization
PTP rarely arrives alone. The moment a network moves off SONET/SDH, or a switch has to serve a utility, railway, or 5G customer, timing turns into a multi-standard problem and most network equipment vendors aren't staffed to solve it.
Promwad is a timing integration partner: we don't sell you a finished grandmaster, we engineer complete synchronization into the hardware you already build.
The full timing stack, one design partner
All PTP profiles that clear an RFQ
G.8265.1 (frequency, telecom), G.8275.1 (phase/time with SyncE assist, utility & mobile backhaul), G.8275.2 (PTP-only, factory & enterprise), IEC 62439-3 (HSR/PRP for substations), and IEEE 802.1AS/gPTP for TSN. One firmware base that passes utility, factory, and telecom qualification without a redesign per customer.
Synchronous Ethernet (SyncE), including Enhanced eEEC
We add SyncE (ITU-T G.8262) and Enhanced eEEC (G.8262.1) — the physical-layer frequency reference that G.8275.1 depends on, mandatory for critical infrastructure. Industrial SyncE penetration still lags far behind telecom: without it, vendors cannot sell into utility or rail markets, and closing that gap is exactly where we work.
Telecom Boundary Clock, Class A through D (ITU-T G.8273.2)
Utility deployments typically need Class A–C (100–40 ns); private 5G and O-RAN fronthaul demand Class D (<5 ns). Class D is your entry ticket to the 5G timing market.
Custom synchronization where nothing off-the-shelf fits
Hybrid TSN-plus-utility platforms, industrial private 5G, non-standard holdover and failover requirements — we architect the servo, holdover (OCXO/TCXO), and failover behaviour to your target.
Legacy continuity, designed in from day one
SONET/SDH (ITU-T G.813) and PDH (G.812) interworking, plus circuit-emulation transport (CES/TDMoIP), so your customers migrate to IP/MPLS on their own timeline instead of in one disruptive step. As SDH reaches end-of-life, backward compatibility lets the deal close.
GNSS-resilient timing (forward-looking)
As anti-jamming and spoofing resistance move from premium feature to RFQ requirement in utility and critical infrastructure, we design GNSS security and holdover into the timing subsystem.
Why a Design Partner Beats a Product
Grandmaster vendors sell a finished box. We put timing inside the box you already build — matched to your silicon, your servo and holdover requirements, and your target certifications (IEEE C37.238 for utility, ITU-T Class D for 5G). One switch platform, ready for both PTP-only factory networks and SyncE+PTP critical infrastructure instead of two product lines and two engineering teams you don't have.
When to bring us in:
If any of these sound like your roadmap, that's the conversation to have with us.
Our Case Studies in Telecom
Do you want to implement IEEE 1588 functionality for your project?
Please, drop us a line. We will contact you today or next business day. All submitted information will be kept confidential.
FAQ
What are the key areas of implementation for PTP?
How does IEEE 1588 PTP work?
The protocol determines the server and client operating modes, as well as the master and slave parts synchronisation messages. The slave synchronises with the master, which is the source of time. A master synchronised to a time reference, such as GPS or CDMA, is called a grandmaster.
- Master sync messages
- Master delay response messages
- Slave delay request messages
The BMC technique enables several masters to agree upon the best clock for the network in addition to the messages.
At least one master and one slave are needed for synchronisation via LAN. A single master can synchronise with several slaves. The slaves use synchronisation messages from the masters to adjust their local ones. All of them record exact timestamps.