Payload encoding/decoding data transformation service is supported when required. The service can be used to perform the necessary payload encoding/decoding and or re-encoding to support use-cases whereby it is critical to encode payload with particular encoding scheme to preserve the payload and avoid malformed or unintelligible content data.

Payload encoding can be performed from/to any of the following encoding schemes: utf8, base64, ascii, hex in any direction.

This service provide the capability to transform payload to/from deivce between base64, UTF8, ASCII, Hex independently for the uplink and downlink flows between the Device and the IoTGtw Cloud Service (leg 1) and the uplink and downlink flows between IoTGtw and the Customer upstream application (leg 2) The charr set encoding to use for each leg of the flow can be set independently to match your upstream application and device requirements.

The default encoding is UTF8 for both legs.