NEON Starting Guide
Step 2: Identify the keys
Table of contents
Each device has a unique combination of security keys that are used by the LNS to identify the device and provide access to the data being sent via LoRa. TWTG will send these keys in an encrypted file alongside the shipment confirmation after purchase.
The file will contain the following information:
Serial Number
devEUI
appEUI/joinEUI
appKey
From LoRaWAN 1.0.4 appEUI is known as joinEUI
The devEUI and the appKey will be requested by the LNS when adding a device. The appEUI/joinEUI is only needed for end-to-end encryption between the device and the application server, and therefore should not be entered in the LNS but in the application server. This is not mandatory, therefore in many situations, the appEUI/joinEUI is not needed at all. It is only needed when LNS and join server are separated and the application server does not trust the LNS.
Please note that for security reasons TWTG will avoid sending the keys more than once. It is recommended that the user store these keys in a safe and documented location.
Examples of the key file
Transmitter ser. no. | type | devEUI | appEUI/joinEUI | appKey |
|---|---|---|---|---|
TT0123AA00001 | DS-TT-01-01 | 848BCD612345678 | 848BCDFFFEEEFFAB | 7A4DFAA5F47A5C3A53FB349670D5B2AF |
TT0123AA00002 | DS-TT-01-01 | 848BCD600000000 | 848BCDFFFEEEFFAC | 7A4DFAA5F47A5C3A53FB349670D5B2AE |