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

Summary

Details

Page properties
Content
... ... @@ -20,6 +20,7 @@
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 +
23 23  [[image:image-20220527090005-2.png]]
24 24  
25 25  UDP Server
... ... @@ -39,6 +39,8 @@
39 39  
40 40  (((
41 41  Below is an example, from
43 +
44 +
42 42  )))
43 43  
44 44  [[image:image-20220527090122-4.png]]
... ... @@ -51,9 +51,9 @@
51 51  
52 52  There are two mode for End Node:
53 53  
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
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.
56 56  
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
57 57  
58 58  
59 59  
... ... @@ -62,9 +62,9 @@
62 62  
63 63  According to above, it is possible to get the payload from sensor without LoRaWAN server:
64 64  
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]]
68 +* Setting the end node to ABP mode
67 67  
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]].
68 68  
69 69  
70 70  
... ... @@ -80,13 +80,27 @@
80 80  [[image:image-20220527090341-5.png]]
81 81  
82 82  Unencrypt packet
83 -
84 84  
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 +
85 85  = 6. limitation =
86 86  
87 87  
88 88  * None standard LoRaWAN protocol, it is not compatible with LoRaWAN server.
100 +
89 89  * No device management / ADR management defined in LoRaWAN protocol
102 +
90 90  * No security.
104 +
91 91  * No Downlink
106 +
92 92  * Only use for ABP
108 +
109 +
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0