Typesets in DaaS-IoT¶
A typeset is a 16-bit identifier that labels the semantic category of a DDO. It tells both sender and receiver what kind of information is being exchanged.
Typesets allow DaaS-IoT to handle structured, heterogeneous messages across the overlay.
1. Purpose of Typesets¶
Every message carries a typeset which defines:
- how the payload should be interpreted
- which handler or subsystem should process it
- whether it represents telemetry, configuration, events or system data
- the expected message schema
Typesets prevent ambiguity across distributed components.
2. How Typesets Are Used¶
On Sending¶
- A DDO is created
- A typeset is assigned
- Payload is written according to the schema
- The DDO is pushed toward a destination DIN
On Receiving¶
- The DDO is reconstructed
- The typeset is read
- The runtime dispatches the message to the correct handler
3. User-Defined Typesets¶
Developers may define their own typesets to represent custom payloads.
Typical examples:
- telemetry sensors
- configuration packets
- alert/notification messages
- command messages
- domain‑specific structures
User typesets can be registered at startup.
4. System Typesets¶
Some typesets are reserved for internal DaaS-IoT functions:
- discovery
- synchronization
- Frisbees
- topology updates
- diagnostic messages
These ensure consistent behavior across the overlay.
5. Typesets and Transport Independence¶
Typesets operate above the transport layer:
- the same typeset works over INET4, Bluetooth, Serial, etc.
- routing and semantics remain stable across media
- payload decoding is deterministic
Summary¶
Typesets give DaaS-IoT a structured, semantic communication model:
- 16-bit identifier
- defines message purpose
- enables dispatch, routing and decoding
- supports both system and user-defined messages
They are the backbone of semantic interoperability in the overlay.