LoRaWAN devices typically require users to enter parameters such as the DevEUI, JoinEUI (formerly AppEUI), AppKey, and potentially the DevAddr plus the session keys, depending on the activation mode (ABP vs OTAA). This is manageable for a handful of devices, but becomes time-consuming, error-prone, and costly at scale.
To make the onboarding process easier and scale LoRaWAN networks more effectively, the LoRa Alliance has now introduced three new documents: the TS014 and TS018 specifications and the TR016 technical recommendations. They should all help users get a device onto a network quickly, securely, and with minimal manual work, such as scanning a QR code.
Here are the links and summaries for all three documents:
- TS014-1.0.0 – LoRaWAN End-Device Capabilities API Specification – TS014 eliminates manual data entry and proprietary workarounds by enabling LoRaWAN networks to automatically pull device profiles. It specifically describes a standard interface which enables the hNS (Home Network Server) to download a Device Profile from a server called the Device Profile Server (DPS).
- TS018-1.0.0 – LoRaWAN Device Identification QR Codes for Automated Onboarding – TS018 helps make setup errors less likely by encoding the device profile server on the device identification QR code.
- TR016-1.0.0 LoRaWAN Relay Technical Recommendations – TR016 gives device makers practical guidance to build relay-based products that work reliably and interoperate well. LoRaWAN Relay can now be adopted more easily in places a gateway can’t reach economically: behind thick walls, underground, inside metal enclosures, or in remote spots with no power or backhaul.
In summary, TS014 defines the protocol between the home network server and the device profile server, while TS018 defines the data stored in the QR code. The LoRaWAN module in the photo at the top of this article doesn’t exist, but the QR code in the image was taken from the appendix in the specifications, and if you try to scan it, it should decode as follows:
|
1 |
LW:D0:1122334455667788:AABBCCDDEEFF0011:AABB1122:OAABBCCDDEEFF:SYYWWNNNNNN:DEXAMPLE.ORG%3A444:PFOOBAR:CF756 |
The string above can be decoded as follows:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
{ "schema_id": "D0", "join_eui": "1122334455667788", "dev_eui": "AABBCCDDEEFF0011", "vendor_id": "AABB", "vendor_profile_id": "1122", "owner_token": "AABBCCDDEEFF", "ser_num": "YYWWNNNNNN", "dps_hostname": "EXAMPLE.ORG", "dps_port": "444", "proprietary": "FOOBAR", "include_checksum": true } |
While the two technical specifications target LoRa devices onboarding, the TR016 technical guidance document introduces best practices to end-device and LoRaWAN protocol stack developers to help ensure they produce well-behaved and interoperable products when using a LoRaWAN relay.
LoRaWAN relays always work in conjunction with a gateway, and are especially useful in locations with limited or non-existent power infrastructure, where IP backhaul connectivity is not feasible, sparse LoRaWAN deployments, and wherever the signal may be obstructed. Released in 2022, the TS011 specification defined what a LoRaWAN relay was, and TRS016 provides additional guidance.
The press release provides an example explaining how TS014, TS018, and TR016 can help with a Smart City deployment:
Consider a city-wide smart water metering rollout: tens of thousands of meters, some buried underground or tucked inside utility vaults where a gateway signal can’t reach. Historically, onboarding even one new meter type meant manually configuring its device profile for the network. Now, scanning or bulk-importing each meter’s QR code points the network straight to the right Device Profile Server. Automated, secure access to that meter type’s profile streamlines onboarding for the entire fleet in one step. With TR016, meters in the hardest-to-reach locations can stay connected via LoRaWAN Relay, without a dedicated gateway for every isolated cluster. The same pattern applies across smart agriculture, smart buildings, and logistics: fewer manual steps, fewer coverage gaps, faster time to value.
Thanks to TLS for the tip.
Jean-Luc started CNX Software in 2010 as a part-time endeavor, before quitting his job as a software engineering manager, and starting to write daily news, and reviews full time later in 2011.
Support CNX Software! Donate via cryptocurrencies, become a Patron on Patreon, or purchase goods on Amazon or Aliexpress. We also use affiliate links in articles to earn commissions if you make a purchase after clicking on those links.
