<
From version < 17.3
edited by Xiaoling
on 2023/04/19 17:49
To version < 13.1 >
edited by Xiaoling
on 2022/07/13 18:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,7 +20,6 @@
20 20  
21 21  If the gateway is connected to LoRaWAN server via UDP packet fordward. We can set the server address to a UDP server to get the LoRaWAN packets.
22 22  
23 -
24 24  [[image:image-20220527090005-2.png]]
25 25  
26 26  UDP Server
... ... @@ -40,8 +40,6 @@
40 40  
41 41  (((
42 42  Below is an example, from
43 -
44 -
45 45  )))
46 46  
47 47  [[image:image-20220527090122-4.png]]
... ... @@ -54,9 +54,9 @@
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.
54 +* 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.
55 +* 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 61  
62 62  
... ... @@ -65,9 +65,9 @@
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
65 +1. Setting the end node to ABP mode
66 +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 72  
73 73  
... ... @@ -83,27 +83,13 @@
83 83  [[image:image-20220527090341-5.png]]
84 84  
85 85  Unencrypt packet
83 +
86 86  
87 -
88 -(% style="color:red" %)**Note: In some device's firmware . There is a AT Command to Disable Encryption. See below:**
89 -
90 -* (% style="color:blue" %)**AT+DECRYPT=1**(%%)  The payload is uploaded without encryption
91 -
92 -* (% style="color:blue" %)**AT+DECRYPT=0  **(%%) Encrypt when uploading payload (default)
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 -
109 -
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0