Distributed Time Synchronization in DaaS-IoT Nodes: the dATS Protocol

---

In modern distributed systems, time is a fundamental resource. When multiple nodes communicate with each other, collect measurements, send commands, or coordinate events, it is not sufficient to know what happened. It is equally important to know when it happened.

This problem becomes even more relevant in IoT, edge, and cyber-physical networks, where devices can be physically distributed, connected through different channels, and characterized by different hardware capabilities.

This is the context in which dATS emerges — the time synchronization algorithm implemented by Sebyone for DaaS-IoT nodes.

dATS is a consensus-based protocol, designed to allow nodes in a distributed network to achieve a shared temporal alignment.

Why synchronize nodes temporally

In a distributed network, each node has its own local clock. This clock can be subject to small errors, drift, communication delays, and hardware differences.

Even when two devices start at the same moment, over time their clocks can diverge. This phenomenon is known as clock drift.

In simple scenarios, a small temporal difference may not be a problem. In more complex systems, however, it can generate significant inconsistencies.

For example, if multiple nodes collect environmental, industrial, or medical data, the correct interpretation of measurements also depends on the temporal order of events. If timestamps are not aligned, it becomes difficult to determine whether an event occurred before, after, or simultaneously with another.

Temporal synchronization therefore serves to build a coherent view of the distributed system.

The limitation of a central temporal reference

A traditional approach to synchronization involves using a central reference: a server, a gateway, or an external time source.

This model can work in many scenarios, but introduces some critical issues.

The first is dependency on a single point of reference. If the central node is unreachable, the entire system may lose its ability to realign.

The second is architectural rigidity. In a distributed and dynamic network, it is not always possible to assume that all nodes can stably reach the same reference.

The third is scalability. As the number of nodes and network complexity increases, a fully centralized model may become less suitable.

For this reason, in advanced distributed systems, it is useful to adopt a model where temporal alignment emerges from cooperation between the nodes themselves.

What is a consensus-based protocol

A consensus-based protocol is one where nodes do not depend exclusively on a single central authority, but participate in a collaborative process to reach a shared value.

In the case of temporal synchronization, the shared value concerns the alignment of the logical clocks of the nodes.

Each node observes its own local time, communicates with other nodes, and participates in calculating a temporal correction. The goal is not to impose an absolute time from the outside, but to make the network converge toward a coherent time base.

This approach is particularly suited to distributed networks, because it reflects the very nature of the system: multiple nodes, multiple viewpoints, coordinated behavior.

dATS: Distributed Adaptive Time Synchronization

dATS can be interpreted as a mechanism of Distributed Adaptive Time Synchronization.

Its purpose is to allow DaaS-IoT nodes to synchronize temporally through a distributed process, based on information exchange and progressive convergence toward a common time reference.

Instead of treating time as information imposed by a single dominant node, dATS treats it as an emergent property of the network.

Each node contributes to the alignment process. The system, as a whole, calculates and updates the corrections necessary to reduce temporal differences between participants.

How the synchronization principle works

The general principle of dATS can be described in four logical phases.

The first phase is local observation. Each node maintains its own clock and records the time of events according to its own perspective.

The second phase is temporal information exchange. Nodes communicate with each other data useful for estimating the difference between their respective temporal references.

The third phase is offset evaluation. Each node can estimate how far its clock is from the other nodes it interacts with.

The fourth phase is progressive correction. The node updates its logical reference by applying an adjustment, with the goal of reducing the temporal distance from the network.

This process does not necessarily need to occur only once. In a real network, synchronization is a continuous activity, because clocks can continue to diverge and network conditions can change over time.

Physical time and logical time

An important point is the distinction between physical time and logical time.

Physical time is that measured by the device’s hardware clock. It is tied to the local clock of the machine and can be influenced by drift, hardware component precision, system load, and other factors.

Logical time, on the other hand, is the temporal reference used by the distributed system to correctly interpret events.

dATS works on the logical alignment of nodes. This means it is not necessary to physically modify the system clock of the device. It is possible to maintain an offset, a correction, or an internal reference that allows the node to reason according to the shared network time.

This approach is safer and more flexible, because it avoids depending directly on modification of the operating system clock.

Why consensus is useful in DaaS-IoT networks

DaaS-IoT is designed for distributed, heterogeneous networks potentially composed of different devices.

In this scenario, a consensus-based protocol like dATS is consistent with the overall system architecture.

DaaS-IoT nodes are not simple passive clients. They are active elements of the network, capable of communicating, exchanging data, and participating in the distributed behavior of the system.

Consensus-based synchronization therefore allows maintaining temporal coherence without introducing a rigid dependency on a single central reference.

This is particularly important when the network must operate in edge, embedded, industrial, or cyber-physical environments, where connectivity may not always be uniform and where devices must maintain a certain degree of autonomy.

Synchronization and telemetry

One of the areas where dATS becomes particularly useful is telemetry.

When multiple nodes collect data, each measurement must be associated with a reliable timestamp. If timestamps are not consistent with each other, subsequent analysis can be incorrect.

For example, in a distributed monitoring system, two measurements from different nodes might appear simultaneous when they are not, or might appear in reverse temporal order.

With a shared temporal reference, instead, the network can produce more consistent and more easily correlatable data.

This improves the quality of analysis, event reconstruction, and the reliability of supervision systems.

Synchronization and distributed control

Temporal synchronization is also important in control systems.

In a cyber-physical system, nodes can send commands, receive responses, monitor states, or coordinate actions. If times are not aligned, the system may incorrectly interpret the sequence of events.

dATS contributes to creating a common time base, useful for better coordinating the behavior of nodes.

This does not mean that all nodes must perform the same operations at the same instant, but that distributed events can be ordered and interpreted according to a shared reference.

Robustness against network variations

In a real network, communication conditions are never perfect.

Messages can experience delays, links can vary, some nodes can enter or exit the network, and device load can change over time.

A distributed approach to synchronization must therefore be capable of adapting.

dATS is designed to operate in this type of context: not as a static synchronization, but as a continuous process of adjustment and convergence.

The goal is to maintain temporal coherence sufficient for the correct operation of the system, even in the presence of operational variations.

dATS within the DaaS-IoT architecture

Within DaaS-IoT, dATS represents one of the fundamental mechanisms for enabling a truly coordinated distributed network.

The DaaS-IoT network does not simply connect different devices. The goal is to allow these devices to collaborate as part of a common logical infrastructure.

To do this, node identification, data exchange, channel management, telemetry, messaging, and synchronization are all needed.

dATS fits into this framework as the component dedicated to temporal coherence. It allows nodes to share not only data, but also a more orderly view of the time in which that data is produced.

Advantages of dATS

The use of dATS brings several advantages.

The first is distribution: synchronization does not depend exclusively on a single central node.

The second is adaptability: the system can progressively update its temporal alignment based on network conditions.

The third is data coherence: measurements, events, and commands can be interpreted with more reliable timestamps.

The fourth is architectural scalability: the mechanism is consistent with networks composed of multiple nodes, even in heterogeneous scenarios.

The fifth is compatibility with the DaaS-IoT approach: time becomes part of the distributed logic of the network, not an external detail entrusted to a separate infrastructure.

Conclusion

Temporal synchronization is a fundamental requirement for many distributed IoT networks. Without a coherent temporal reference, it becomes difficult to correctly interpret measurements, events, commands, and states coming from different nodes.

dATS is designed to address this need within the DaaS-IoT ecosystem.

Being a consensus-based protocol, dATS allows nodes to actively participate in the synchronization process, contributing to the construction of a shared time base.

This approach is consistent with the DaaS-IoT vision: a distributed, flexible, heterogeneous network oriented toward collaboration between devices.

In a network where nodes must not only communicate, but also coordinate, time becomes an essential component of the architecture. dATS provides the mechanism to make it distributed, adaptive, and integrated into the system.