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. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -15,7 +15,6 @@ 15 15 Unencrypt Network modified from LoRaWAN 16 16 17 17 18 - 19 19 = 2. Analyze the LoRaWAN packet = 20 20 21 21 ... ... @@ -50,25 +50,28 @@ 50 50 Decode the packet 51 51 52 52 53 - 54 54 = 3. Difference between OTAA and ABP mode = 55 55 56 56 57 57 There are two mode for End Node: 58 58 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 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. 61 61 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 62 62 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 -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]] 68 +* Setting the end node to ABP mode 70 70 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 + 72 72 = 5. Use an unencrypt firmware = 73 73 74 74 ... ... @@ -83,19 +83,25 @@ 83 83 Unencrypt packet 84 84 85 85 86 -Note: In thenewfirmwarewith 007 stack. There is a AT Command to Disable Encryption. See below:88 +(% style="color:red" %)**Note: In some device's firmware . There is a AT Command to Disable Encryption. See below:** 87 87 88 -* AT+DECRYPT=1 The payload is uploaded without encryption 89 -* AT+DECRYPT=0 Encrypt when uploading payload (default) 90 +* (% style="color:blue" %)**AT+DECRYPT=1**(%%) The payload is uploaded without encryption 90 90 92 +* (% style="color:blue" %)**AT+DECRYPT=0 **(%%) Encrypt when uploading payload (default) 91 91 94 + 95 + 92 92 = 6. limitation = 93 93 94 94 95 95 * None standard LoRaWAN protocol, it is not compatible with LoRaWAN server. 100 + 96 96 * No device management / ADR management defined in LoRaWAN protocol 102 + 97 97 * No security. 104 + 98 98 * No Downlink 106 + 99 99 * Only use for ABP 100 100 101 101