Protocol Stack Overview
From the meter upward: meter firmware → Bluetooth Mesh → IoT base station → MQTT over TLS → cloud platform. Each layer has a specific role and security boundary.
Meter Firmware
Reads electrical parameters at 1 kHz, calculates RMS values every second, packages them into Mesh publish messages. Battery-backed RTC keeps accurate timestamps during power outages.
Bluetooth Mesh Layer
Each meter publishes to a group address (e.g. "floor-3-three-phase"). Relay nodes forward the message up to 3–7 hops. Duplicate detection and TTL prevent loops.
IoT Base Station
Subscribes to relevant group addresses, de-duplicates and time-stamps incoming messages, batches them into MQTT payloads, and forwards upstream over TLS. Local buffering covers 30 days of network outages.
Cloud Platform
Ingests MQTT streams, stores time-series data, runs analytics (peak demand, power quality, anomaly detection), and exposes APIs for third-party integration.
End-to-End Latency
Typical end-to-end latency from meter to dashboard: 1.5–2.5 seconds, dominated by the Mesh relay hops and MQTT batching.
Security Architecture
AES-128 link-layer encryption in Mesh, AES-CCM-256 in MQTT/TLS, role-based access control in the cloud platform. Device identity is rooted in the factory-provisioned key.
Reliability and Resilience
Mesh self-healing reroutes around failed nodes. Base station local buffering covers internet outages. Cloud platform replicates across three availability zones for disaster recovery.
Conclusion
Industrial Bluetooth delivers a robust, secure, end-to-end wireless data transmission architecture for smart power distribution. Each layer is well-understood and field-proven across hundreds of Rynon deployments.