Issue link: https://read.uberflip.com/i/1493503

Contents of this Issue


Page 0 of 3

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 Payload Codec API FAQ 1. What is a codec? When using LoRaWAN to transport application payloads, messages are very compactly encoded to minimize bandwidth usage. As messages reach the Application Server, they must be decoded to be read and processed. The decoder is the device specified piece of code, on the Application Server, responsible for translating the data from binary to application/ human readable, and vice versa. 2. Why do we need a standard codec API? To decrease the huge friction for on-boarding new devices / apps and Application Server platforms, device makers can write their codecs once and have them used on any Application Server. 3. How does the standard codec API make it faster to deploy? Standard codec API can be adopted by both the device makers and Application Server vendors, such that: Device maker develops the codec implementation once, then it can be used with any Application Server platform. This allows the new LoRaWAN devices to be faster to deploy and easily integrated into any compatible platform. 4. How is the standard codec composed? A LoRaWAN Payload codec API standardizes the JavaScript codec and the metadata to be provided by the Device maker / Application server vendor. Metadata: Identifies the codec itself, vendor of device, version, etc. JavaScript codec: A JavaScript code that respects the three functions signatures: decodeUplink (mandatory), encodeDownlink (optional), decodeDownlink (optional).

Articles in this issue

Links on this page

view archives of FAQ - LoRaWAN_Payload_Codec_API_FAQ