IoT and connectivity engineering

We build BLE peripherals and centrals on Nordic nRF52 and nRF53, Silicon Labs EFR32, ESP32 and STM32: GATT services and characteristics, advertising and connection parameters tuned for battery life, and firmware updates over BLE (DFU). We work with the team building the mobile app, so both sides share one protocol specification.

For Bluetooth Mesh and Thread/Matter products we plan provisioning, network size and power roles up front, and test interoperability with the phones and hubs your customers actually use.

• LE Secure Connections pairing, bonding and protection against eavesdropping
• BLE DFU with signed images and rollback
• Support for Bluetooth SIG qualification and listing
• Range and throughput measurements in the target enclosure

Radio products sold in the EU must already meet the cybersecurity requirements of the Radio Equipment Directive (EN 18031 standards, applicable since 1 August 2025). The Cyber Resilience Act builds on them and extends the obligations to the whole product lifecycle, including security updates for the support period.

For battery-powered devices that send small amounts of data over long distances we use LoRaWAN, NB-IoT or LTE-M. The choice depends on coverage, roaming, message size, latency and the cost of connectivity over the product's lifetime. We implement the LoRaWAN stack with ADR and duty-cycle limits, and integrate cellular modems with power-saving modes (PSM and eDRX).

Typical work includes modem driver integration, network registration and fallback logic, SIM and eSIM handling, buffering data when coverage drops, and field tests in the real installation environment.

• LoRaWAN class A/B/C end devices and over-the-air activation (OTAA)
• LTE-M / NB-IoT modem integration, PSM and eDRX tuning
• Compact message formats such as CBOR or Protocol Buffers to save airtime
• Battery life estimates confirmed by current measurements

Long-life devices need a secure update path for many years. With LoRaWAN, where bandwidth is small, we plan delta or multicast firmware updates (FUOTA) early, because the Cyber Resilience Act expects security updates for the whole support period.

Every connected device needs a unique identity, credentials that are not shared across the fleet, and a way to renew them. We provision keys and certificates in production, store them in a secure element or the MCU's protected storage, and use mutually authenticated TLS or DTLS towards the cloud.

Over-the-air updates use signed images, verification before installation and A/B partitions or a recovery image, so a failed update never bricks the device. Update campaigns are staged, with telemetry that shows which versions are in the field.

• Device provisioning, certificates and key rotation
• Secure OTA with A/B partitions and rollback protection
• Remote logging and diagnostics designed with privacy in mind
• Fleet version tracking for vulnerability handling

These measures cover a large part of the Cyber Resilience Act requirements for connected products: integrity, confidentiality, secure updates and logging.