Solutions

IoT Platform Solution

An IoT platform you own, from device connectivity to remote control

01Overview

Many hardware companies get their devices online, then stall: telemetry piles up unread, alarms depend on someone watching a screen, firmware updates need a site visit, and customers who want app control require yet another vendor.

Our IoT platform solution starts with MQTT connectivity and ties together device management, OTA updates, a rules and alerting engine, data dashboards and mini-program or app control. The connectivity layer can run on Alibaba Cloud IoT, Tencent Cloud IoT or a self-hosted EMQX cluster, chosen by fleet size, data ownership requirements and long-term cost.

Delivery is project-based: we map device models, protocols and data points first, define the thing model and platform boundaries, then roll out in phases. Source code and deployment docs are handed over to you.

02The problems

Mixed protocols and models

Legacy units speak Modbus or serial passthrough, newer ones use MQTT, and firmware fields drift between batches.

Alerting by eyeball

Thresholds are hard-coded, alerts go out by SMS only, and nobody can tell who acknowledged what.

Risky firmware updates

Without staged OTA and rollback, one bad release can knock a batch offline and trigger site visits.

Cloud lock-in

A proprietary SDK chosen for speed becomes expensive and hard to migrate once the fleet grows.

03Architecture

L1Device layer

Sensors, controllers, gateways and terminals; edge gateways translate Modbus or serial for non-MQTT devices.

L2Connectivity layer

An MQTT broker on Alibaba Cloud IoT, Tencent Cloud IoT or self-hosted EMQX, with TLS and per-device credentials.

L3Platform layer

Thing models, device shadows, the rules engine, OTA scheduling and time-series storage.

L4Application layer

Admin console, dashboards, mini-program or app control, and open APIs for your other systems.

L5Operations and security

Device logs, connection monitoring, audit trails and role-based access.

04Capabilities

01

MQTT connectivity

Per-device or per-product credentials, QoS levels, last-will messages and gateway sub-devices.

02

Thing models and shadows

Properties, events and services describe each device; commands queue in the shadow while offline.

03

Device lifecycle

Bulk import, grouping, tagging, online status and ownership transfer.

04

OTA updates

Staged rollouts by model, version or group, with retries, rollback and progress tracking.

05

Rules and alerting

Configurable thresholds and compound conditions, pushed to SMS, WeCom, DingTalk or WeChat, with acknowledgement records.

06

Dashboards

Online rates, key metric trends and alarm distribution by site or project.

07

Mini-program and app control

End users bind devices, send commands, set schedules and share access.

08

Open APIs

Device data and control endpoints for ERP, MES or your own systems, plus historical export.

05Typical scenarios

Typical situations — not specific client cases.

After-sales remote service

For example, an equipment maker that wants to see field units, catch fault codes early and push fixes remotely.

Factory energy and status monitoring

For example, a workshop connecting older machines through edge gateways to one energy and downtime dashboard.

Consumer device control

For example, a smart-home brand needing a mini-program for pairing and control plus activation data on the back end.

Distributed environment monitoring

For example, warehouses or server rooms escalating out-of-range readings through an on-call rota.

06Technology

  • MQTT
  • EMQX
  • 阿里云物联网平台
  • 腾讯云 IoT
  • TDengine
  • PostgreSQL
  • Redis
  • 微信小程序

07FAQ

Cloud IoT platform or self-hosted EMQX?

Managed cloud platforms save ops effort for smaller fleets; self-hosted EMQX gives more control over data and long-term cost at scale. We compare both for your numbers.

Can legacy non-MQTT devices connect?

Usually yes, via an edge gateway that translates Modbus, serial or proprietary protocols, provided the protocol is documented.

Do we get the source code?

Yes. Source, deployment docs and thing-model definitions are part of the handover.

Talk to us

Tell us about your project

Leave your details and we’ll reply within one business day. We start with your needs, then a proposal; pricing is discussed directly.

  • Reply within one business day
  • Free initial conversation, no hard sell
  • Handover with admin and docs
Used only to reply to this enquiry.