The Device Messaging acknowledgement service is available on:
- SimplyTiny over raw socket
- SimplyTiny over CoAP
- SimplyTiny over MQTT-SN
- Blob over CoAP
- Blob over MQTT-SN
- Blob over Raw Socket
- All the above Transported over TCP or UDP
The “SimplyTiny for IoT” transfer method provides a simple and efficient message acknowledgement capability for IoT devices that need message acknowledgement for both uplink and downlink message deliveries. SimplyTiny is easy to use on high and low end IoT devices without need for any libraries, plugins or firmware updates.Using “SimplyTiny for IoT” is also a great way of providing simplification of message acknowledgment to IoT devices that use TCP or any other complex protocol/framework. Further message acknowledgements help to keep track of uplink and downlink message delivery for event notifications and allows the customer to monitor the message status on the portal or through messaging API queries.
Customers can setup notification event (for example the “notify_on_delivery” event in the service template) to get a notification sent to the upstream application defined in the messaging endpoint associated to the device service template.
Messaging Ack for SimplyTiny over (raw socket, CoAP or MQTT-SN) can be configured by following the instructions for SimplyTiny.
Messaging Ack for Blob over CoAP can be used by following the instructions in the CoAP service description.
Messaging Ack for Blob over MQTT-SN can be used by following the instructions in the MQTT-SN service description.
Device Assisted Acknowledgement Service (For Raw Sockets)
Message Acknowledgement can also be provided for raw TCP or UDP sockets.
To setup and message acknowledgement for raw sockets follow the simple steps below.
Steps:
- Go to the device service template and enable “Device Assisted Ack” service (This service can only be used with a private SAP)
- Add one or more rules to specify which protocol messages require message acknowledgements select from UDP or TCP.
- Select the preferred method for performing the ack, in the ACK-Type field select either String-Value or Uplink-Length
- If set to String-Value selected then specify the static string to return to the device everytime a matching packet from device is received
- If set to Uplink-Length then everytime a matching packet from the device is received, the TCP/UDP payload length of the uplink message is echo’d back
- In both cases the ack message (static string or uplink-length) is transmitted back as plain string using the socket the uplink was received on.
- Refer to the Service Template parameter description page for more details about Device Assisted Ack