Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -50,7 +50,6 @@
50	50	Decode the packet
51	51
52	52
53		-
54	54	= 3. Difference between OTAA and ABP mode =
55	55
56	56
...	...	@@ -59,6 +59,8 @@
59	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	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
61	61
	61	+
	62	+
62	62	= 4. Get and decode the packet =
63	63
64	64
...	...	@@ -65,8 +65,10 @@
65	65	According to above, it is possible to get the payload from sensor without LoRaWAN server:
66	66
67	67	1. Setting the end node to ABP mode
68		-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	+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
	71	+
	72	+
70	70	= 5. Use an unencrypt firmware =
71	71
72	72
...	...	@@ -87,6 +87,7 @@
87	87	* AT+DECRYPT=0 Encrypt when uploading payload (default)
88	88
89	89
	93	+
90	90	= 6. limitation =
91	91
92	92