5177 Brandi n Court, Frem ont, CA94538 | Tel : +1 51 0 -4 9 2 -4044 | Fax : +1 510 -4 9 2 -4001 | www.l o ra -al l i anc e.org
Payload Codec API FAQ
5. What kind of metadata are provided in the standard codec?
A simple file that declares some properties to simplify the open distribution and integration
with LoRaWAN platforms: codec identifier, ID of vendor, codec version, description, etc.
6. Are there any constraints when developing a codec following the specification?
LoRa Alliance defined inside the specification some recommendations and requirements.
Main requirements/constraints are related to security and size of delivered codec, as no
external codes allowed to be used during runtime, and its size should not exceed 64 KB.
7. Is there a standard functionality for binary encoding/decoding defined in the
specification?
Yes, the specification defines the Node's Buffer as a standard way to decode/encode binary
data to/from application readable formats following the datasheet of the device.
8. Why is there no encodeUplink() function?
The uplink payload is already encoded by the device and sent using LoRaWAN. The
encoding process is only needed to send downlink payload from Application Server to
device.
9. As a device maker, if I have several devices that use different payload formats, can I
define multiple codecs and use multiple codecId?
Yes. Codec ID is not dedicated to a device maker, but rather to a device / group of devices.