Why is time synchronization important in the EPD Pilot and what approaches can be used?

• A. It only affects display timestamps locally.
• B. It replaces the need for sequence numbers.
• C. It ensures consistent timestamps and correct sequencing; methods include NTP/PTP or synchronized clocks from a common time source.
• D. It is optional and rarely used in practice.

Answer: (C)

Time synchronization keeps all parts of the EPD Pilot on the same clock so timestamps are consistent and events can be ordered correctly. In a distributed system, clocks drift because of hardware differences, load, and network delays. If components don’t share time, a event that happened before another can appear after it in logs or streams, making auditing, debugging, and replay unreliable. With synchronized time, you can reliably determine when things happened and how they relate, which is essential for correct sequencing and data integrity.

A practical way to achieve this is by using time protocols and common time sources. NTP (Network Time Protocol) provides network-based clock synchronization with millisecond precision, which is usually enough for many applications. PTP (Precision Time Protocol) offers higher accuracy, often necessary in tightly coupled, local networks or performance-critical setups. Another approach is to synchronize all clocks to a shared time source—such as a GPS-based clock or a centralized time server using NTP or PTP—so every component refers to the same reference time.

In short, time synchronization is not just about pretty timestamps—it’s about ensuring events are timestamped consistently and ordered correctly across the system, using reliable time sources and protocols.