Summary

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

Details

Page properties

Content

...	...	@@ -28,7 +28,7 @@
28	28
29	29
30	30	(((
31		-From above screen shot, we can see most of the meaning except this** (% style="color:#4F81BD" %)"data":"QHxqASaAygwCXrumS1oFsgRq"**.(%%) This is the AES128 encryption data we mention above, it is base64 format. To decode this data, we need to have the APP Session Key and Network Session Key of this end node. If we have these two keys, we are able to decode this packet by some LoRaWAN decode website like: [[LoRaWAN Decode Website>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]].
	31	+From above screen shot, we can see most of the meaning except this** (% style="color:#4f81bd" %)"data":"QHxqASaAygwCXrumS1oFsgRq"(%%)**(% style="color:#4f81bd" %).(%%) This is the AES128 encryption data we mention above, it is base64 format. To decode this data, we need to have the APP Session Key and Network Session Key of this end node. If we have these two keys, we are able to decode this packet by some LoRaWAN decode website like: [[LoRaWAN Decode Website>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]].
32	32	)))
33	33
34	34
...	...	@@ -40,6 +40,7 @@
40	40
41	41	Decode the packet
42	42
	43	+
43	43	= 3. Difference between OTAA and ABP mode =
44	44
45	45	There are two mode for End Node:
...	...	@@ -47,6 +47,7 @@
47	47	* 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.
48	48	* 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.
49	49
	51	+
50	50	= 4. Get and decode the packet =
51	51
52	52	According to above, it is possible to get the payload from sensor without LoRaWAN server:
...	...	@@ -54,6 +54,7 @@
54	54	1. Setting the end node to ABP mode
55	55	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>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]]
56	56
	59	+
57	57	= 5. Use an unencrypt firmware =
58	58
59	59	If user doesn't care about the security of the data and use Dragino end node, it is possible that we provide a firmware without AES128 encrytion, so the server no need to decode packet. Please note this software is no LoRaWAN compatible and no security.
...	...	@@ -62,7 +62,7 @@
62	62	The software will disable encryption, so the LoRaWAN payload raw "data":"QHxqASaAygwCXrumS1oFsgRq" will looks like "data":"4068370126000000000c9e11223361898841", and the meaning is as below:
63	63	)))
64	64
65		-[[image:https://wiki.dragino.com/images/thumb/d/d6/None_Encryption_4.png/600px-None_Encryption_4.png||height="70" width="600"]]
	68	+[[image:image-20220527090341-5.png]]
66	66
67	67	Unencrypt packet
68	68