Connecting a SAM R34 SiP/SAM R34 Module LoRaWAN® End Device to a LoRaWAN Network Server

LoRaWAN Join Types

Last modified by Microchip on 2024/07/18 10:22
   LoRaWAN® Message and End-Device Types  Provisioning LoRa® End Devices to Network Servers   

Two Methods for End-devices to Join a LoRaWAN® Network

Over-The-Air Activation (OTAA)

  • End-device transmits a Join Request to the application server containing:

    • Globally unique end-device identifier (DevEUI)
    • Join server Extended Unique Identifier (JoinEUI)/Application identifier (AppEUI), and
    • Authentication with Application key (AppKey)
  • End-device receives Join Accept from the application server
  • End-device authenticates Join Accept
  • End-device decrypts Join Accept
  • End-device extracts and stores Device Address (DevAddr)
  • End-device derives security keys:
    • Network Session Key (NwkSKey)
    • Application Session Key (AppSKey)

Over-The-Air Activation

Activation by Personalization (ABP)

  • The following information is configured at production time:

    • Device Address (DevAddr)
    • Network Session Key (NwkSKey)
    • Application Session Key (AppSKey)
  • No over-the-air handshaking
  • Device is ready to communicate on the network without any additional procedure

Activation by Personalization

​

In production, we recommend you use OTAA. OTAA is more reliable since the activation will be confirmed and more secure. Session keys are agreed upon with every activation. ABP can be used when doing demos or workshops.