Bi-Directional Device to Cloud Data Flows
The platform supports any Low Power Wide Area (LPWA), cellular or non cellular IoT devices. A wide variety of protocols, encryption, application types and data frameworks are supported and can be setup in many different combinations.
Supported Device Transport Protocols
Supported Device Application Protocols:
- MQTTSN 1.2: QoS Supported: QoS -1 (additional QoS: 0 or 1 also supported).
- CoAP Service: Based on IETF core-coap-18 specification
- Raw Sockets
Supported Device Data Framewokrs
- Blob / Opaque data
- Custom JSON (bring your own JSON format)
- Microsoft Azure IoT Hub JSON
- SimplyTiny (JSON)
- SimpyTiny (flat string)
- SimpyTiny (URI embeded)
- LwM2M (coming soon)
In principle the platform supports device connections in any combination of Transport protocol, Application Protocol and Data framwork.
A Service Access Point (SAP) is used to define the exact combination required for your device / project.
A device may be setup to use one or multitude of connection combinations (Service Access Points) to meet the customer requirements. Devices may also be restricted to specific Service Access Points on top of that devices can be restricted to SAP in specific regions (for example to keep the device traffic in specific country/region only). All this and more can be configured in the device Service Profiles.
Notes:
- SimplyTiny service: Is a simple string format designed to convey IoT messages in a wide range of use cases even simply tiny sensors can use it out of the box (no special libraries required).
- SimplyTiny provides support for: Device Authentication, Device bootstrapping, Message Acknowledgement, Periodic Auth token update/refresh, Keep-alive, SAP list retrieval by device (list configurable by the device service template), Device shadow copy update which can be directly viewed on the portal and portal map as well as retrieved via APIs. Device shadow copy includes gps coordinates, signal strength information, power usage information, device timestamp, etc. Learn more:
- The service can provide acknowledgement using the device assisted acknowledgement feature for raw sockets in case acknowledgement service is required for raw UDP.
- Devices using raw sockets can use any data framework. However it is worth noting that some data frameworks require a private SAP which can be setup instantly on the portal or using the provisioning APIs. .