Changes for page How to send none encryption LoRaWAN Packet
Last modified by Xiaoling on 2023/04/19 17:49
<
edited by Edwin Chen
on 2022/08/23 11:59
on 2022/08/23 11:59
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -15,6 +15,7 @@ 15 15 Unencrypt Network modified from LoRaWAN 16 16 17 17 18 + 18 18 = 2. Analyze the LoRaWAN packet = 19 19 20 20 ... ... @@ -49,28 +49,25 @@ 49 49 Decode the packet 50 50 51 51 53 + 52 52 = 3. Difference between OTAA and ABP mode = 53 53 54 54 55 55 There are two mode for End Node: 56 56 57 -* (% style="color:blue" %)**OTAA:**(%%) Over the air activation. In this mode, the end node will send a Join Request to server, server will reply with a Join Accept and the end node will parse this Join Accept message to get the Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey). Because the AppSkey and NwkSkey is dynamic, OTAA mode provide more security. 59 +* OTAA: Over the air activation. In this mode, the end node will send a Join Request to server, server will reply with a Join Accept and the end node will parse this Join Accept message to get the Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey). Because the AppSkey and NwkSkey is dynamic, OTAA mode provide more security. 60 +* ABP: Activation by personalization. There is no hand-shake with LoRaWAN server for activition. The end node will use fix Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey) to upload the packet. So the packet can be decode if someone know these fix keys 58 58 59 -* (% style="color:blue" %)**ABP:**(%%) Activation by personalization. There is no hand-shake with LoRaWAN server for activition. The end node will use fix Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey) to upload the packet. So the packet can be decode if someone know these fix keys 60 60 61 - 62 - 63 63 = 4. Get and decode the packet = 64 64 65 65 66 66 According to above, it is possible to get the payload from sensor without LoRaWAN server: 67 67 68 -* Setting the end node to ABP mode 68 +1. Setting the end node to ABP mode 69 +1. Add decode program and add the keys of the sensor. So to get the payload. There is an example for such application, see [[Communication with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]] 69 69 70 -* Add decode program and add the keys of the sensor. So to get the payload. There is an example for such application, see [[Communication with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]]. 71 71 72 - 73 - 74 74 = 5. Use an unencrypt firmware = 75 75 76 76 ... ... @@ -85,25 +85,19 @@ 85 85 Unencrypt packet 86 86 87 87 88 - (% style="color:red" %)**Note: Insomedevice'sfirmware . There is a AT Command to Disable Encryption. See below:**86 +Note: In the new firmware with 007 stack . There is a AT Command to Disable Encryption. See below: 89 89 90 -* (% style="color:blue" %)**AT+DECRYPT=1**(%%) The payload is uploaded without encryption 88 +* AT+DECRYPT=1 The payload is uploaded without encryption 89 +* AT+DECRYPT=0 Encrypt when uploading payload (default) 91 91 92 -* (% style="color:blue" %)**AT+DECRYPT=0 **(%%) Encrypt when uploading payload (default) 93 93 94 - 95 - 96 96 = 6. limitation = 97 97 98 98 99 99 * None standard LoRaWAN protocol, it is not compatible with LoRaWAN server. 100 - 101 101 * No device management / ADR management defined in LoRaWAN protocol 102 - 103 103 * No security. 104 - 105 105 * No Downlink 106 - 107 107 * Only use for ABP 108 108 109 109