Case Study

Connecting DDS Devices to Azure IoT Without Losing Identity

Previously isolated DDS devices became first-class, identifiable participants on Azure IoT, without a compliance compromise.

Industry

Embedded & Silicon

Services We offer

Embedded & Firmware

Industrial Protocols

Cloud Integration

Device Security

About the client

A global medical-technology company.

Problem Statement

Devices speaking the DDS protocol traditionally lacked internet connectivity. The client needed them on Azure IoT Hub, without losing per-device identity or breaking compliance.

The Challenges

Two protocol worlds

Bridging RTI and Cyclone DDS to Azure IoT meant handling the semantics of both sides faithfully.

Identity preserved

Each device kept its identity and rolling certificates across the bridge, so governance held.

Approach

We built a protocol-aware, security-first gateway:

A DDS-to-Azure bridge supporting RTI DDS and Cyclone DDS
Governance and permission management
Per-device identity preservation across the bridge
Certificate rolling and security compliance, with managed connection handling

The Solution

The gateway translates between DDS and Azure IoT while each device keeps its identity, certificates roll automatically, and permissions are enforced, running as a Dockerized service in C++ and Python.

Read more case studies

Secure Boot and Trusted Configuration for a Medical IoT Gateway

Learn More

Unified Device Management for Hospital Networks with Azure Arc

Learn More

Bringing 1,000+ Elevators Online: A CANBUS/MODBUS to SCADA Gateway

Learn More

Get Detailed Case Study

Connecting DDS Devices to Azure IoT Without Losing Identity

A gateway that brings devices on the DDS protocol, traditionally offline, onto Azure IoT Hub while preserving identity, rolling certificates, and staying compliant.

Tráiganos el caso extremo que su nube no puede alcanzar. Vamos a diseñarlo.