The Core Concepts of DaaS-IoT: DDO and Typeset

---

Every distributed architecture needs a common model to represent and exchange information.

In an IoT network, simply connecting devices is not enough. Nodes must be able to communicate consistently, recognize the meaning of received data, and distinguish between different types of messages: state, telemetry, commands, results, notifications, events, or application information.

In DaaS-IoT, two fundamental concepts for achieving this goal are DDOs and Typesets.

These two elements represent a central part of the DaaS communication model: DDOs define the data object exchanged between nodes, while Typesets allow classification of the meaning of the transported content.

Why common data concepts are needed

In many traditional IoT systems, information exchange happens through messages built directly by the application: strings, JSON, byte arrays, binary payloads, or proprietary protocols.

This approach is flexible, but can become fragile as the system grows.

If each node interprets data differently, the network becomes difficult to maintain. Every new integration requires specific agreements on format, message meaning, and handling methods.

DaaS-IoT addresses this problem by introducing a more structured model, where data is not simply packets transported from one point to another, but recognizable objects within the network.

What is a DDO

A DDO, or DaaS Data Object, is the informational unit exchanged between DaaS-IoT nodes.

It can be seen as a data container that travels through the network and carries a payload associated with a specific operational meaning.

The DDO does not represent just “a message.” It is a data object designed to be managed within the DaaS-IoT architecture.

Through DDOs, nodes can send and receive information in a more orderly manner, maintaining a separation between data transport and the applicative meaning of the content.

The DDO as a communication unit

In a DaaS-IoT network, nodes communicate by exchanging DDOs.

This allows for a common model for transmitting information. The sending node constructs a DDO, associates content, and sends it toward a destination node or a part of the network.

The receiving node, in turn, can interpret the received DDO, read its content, and handle it according to the intended applicative logic.

This model is useful because it allows communication to be treated uniformly, regardless of the type of data being transported.

A DDO can represent, for example:

• a state;
• a measurement;
• an event;
• a command;
• a result;
• a notification;
• an applicative message.

The key point is that the data is encapsulated in a structure consistent with the DaaS model.

Payload and meaning

The payload is the informational content transported by the DDO.

It can be a string, a structured message, a JSON representation, an applicative value, or a more specific encoding defined by the system.

However, the payload alone is not always sufficient.

Two payloads can have a similar format but completely different meanings. For example, a JSON string could represent a device state, a telemetry measurement, or the result of a command.

This is why DaaS-IoT introduces the concept of Typeset.

What is a Typeset

A Typeset is a logical identifier that allows classification of the type of content transported by a DDO.

In other words, the Typeset answers the question:

what kind of information does this DDO contain?

Thanks to the Typeset, a node can distinguish a state message from a command message, a measurement from a response, a telemetry from an applicative event.

The Typeset does not replace the payload, but contextualizes it.

The payload contains the data. The Typeset helps interpret its role within distributed communication.

DDO and Typeset work together

DDO and Typeset are complementary concepts.

The DDO represents the data object transported in the network. The Typeset represents the semantic classification of the content.

Without DDO, the system would have only raw messages to transport. Without Typeset, the system would have data objects lacking a clear classification.

Together, they allow DaaS-IoT nodes to exchange information in a more orderly, extensible, and interpretable manner.

A node can receive a DDO, verify its Typeset, and decide how to handle it.

For example:

• if the Typeset indicates a state, the node can update an internal representation;
• if it indicates telemetry, it can record a measurement;
• if it indicates a command, it can trigger a procedure;
• if it indicates a result, it can link it to a previous request;
• if it indicates an event, it can forward it or handle it locally.

This mechanism makes communication more modular.

Separating transport and semantics

One of the main advantages of DaaS-IoT is the separation between data transport and its meaning.

Transport concerns how the DDO is sent: which channel is used, which driver, which link, which path in the overlay network.

Semantics, on the other hand, concerns what that data represents.

DDO and Typeset belong to the semantic level of DaaS-IoT communication. They allow the application to reason about data without being excessively tied to the physical medium used to transmit it.

This is particularly important in an overlay architecture, where the logical network can rest on different channels such as Ethernet, Wi-Fi, Bluetooth, or other supported links.

Typeset as an application contract

The Typeset can be considered a form of applicative contract between nodes.

When two nodes use the same Typeset, they implicitly share a convention on the meaning of the DDO.

This convention can be simple or complex.

In a minimal scenario, a Typeset can simply distinguish a text message from telemetry. In a more advanced scenario, it can be used to separate different applicative streams, message families, commands, responses, events, or diagnostic data.

This classification allows for the design of more orderly networks.

Instead of having a single indistinct stream of messages, the network can organize communication based on the nature of the content.

Conceptual example

Imagine a DaaS-IoT network composed of multiple nodes.

A sensor node collects environmental information. A gateway node receives the data and forwards it to a supervision system. Another node can send commands or state requests.

In this scenario, DDOs can carry different contents.

A first DDO can contain a temperature measurement. A second DDO can contain the operational state of the node. A third DDO can contain a command. A fourth DDO can contain the result of that command’s execution.

Without Typeset, all these messages would simply be payloads to interpret manually.

With Typesets, each DDO is classified and can be handled consistently.

The receiving node does not need to guess the role of the message: it can read its classification and apply the correct logic.

DDO, Typeset and telemetry

Telemetry is one of the most natural examples of DDO usage.

In a distributed network, each node can produce measurements, operational statistics, internal states, or runtime data.

This information can be encapsulated in DDOs and classified through dedicated Typesets.

In this way, the system can clearly distinguish telemetry from other types of communication.

This is useful for collecting data in an orderly manner, feeding it to dashboards, monitoring systems, time-series databases, or analytics modules.

DDO, Typeset and commands

Beyond telemetry, DDO and Typeset can also be used for command management.

A node can send a DDO representing an operational request to another node. The Typeset allows identifying that DDO as a command.

The destination node can then recognize that this is not simply information, but an action to be interpreted and possibly executed.

Similarly, the result of execution can be sent via another DDO, classified with a different Typeset.

This allows for clear separation of:

• requests;
• responses;
• results;
• errors;
• operational notifications.

Communication becomes more readable and more easily extensible.

Extensibility of the model

One of the advantages of Typesets is the ability to extend the model without modifying the entire architecture.

New message types can be introduced by defining new classifications.

This allows DaaS-IoT to adapt to different applicative scenarios: industrial, medical, robotic, infrastructural, edge computing, or distributed monitoring.

The core of communication remains the same: nodes exchange DDOs. What changes is the meaning associated with the Typesets used.

This separation makes the system cleaner and more evolvable.

DDO and interoperability

In a heterogeneous system, interoperability is a fundamental requirement.

Different devices can be developed in different languages, run on different platforms, and connected through different channels.

DDO and Typeset help build a common language between these devices.

A node does not necessarily need to know all the internal details of another device. However, it must be able to recognize the type of data received and know how to handle it.

This makes it simpler to integrate new nodes into the network and build distributed applications where different components can collaborate.

Role in distributed DaaS-IoT systems

Within the DaaS-IoT architecture, DDO and Typeset are part of the logical layer that makes communication more structured.

The network does not only transport raw data, but classified informational objects.

This is consistent with the DaaS-IoT vision: devices as services, nodes as active participants, distributed communication and interpretable data.

In a network of this type, every piece of information must be produceable, transportable, receivable, and interpretable consistently.

DDO and Typeset provide the foundation for this.

Conclusion

DDO and Typeset are two fundamental core concepts of DaaS-IoT.

DDOs represent the data unit exchanged between nodes in the network. Typesets allow classification of the meaning of the transported content.

Together, these two concepts make DaaS-IoT communication more orderly, semantic, and extensible.

The result is a model in which nodes do not simply send payloads, but exchange recognizable, classified, and interpretable data objects.

This approach is essential for building distributed IoT networks where heterogeneous devices can collaborate consistently, scalably, and in a service-oriented manner.