Skip to content

Commit b21f95d

Browse files
Merge pull request #19 from OS2iot/feature/IOT_1228_MulticastDocs
Feature/iot_1228_multicast_docs
2 parents fb9e10d + d202bba commit b21f95d

File tree

3 files changed

+50
-0
lines changed

3 files changed

+50
-0
lines changed

source/contents.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
external-interface-design/external-interface-design.rst
1414
software-architecture/software-architecture.rst
1515
payload-decoders/payload-decoders.rst
16+
multicast/multicast.rst
1617
iot-data-handling/iot-data-handling.rst
1718
downlink-helpers/downlink-helpers.rst
1819
kombit-adgangsstyring/kombit-adgangsstyring.rst

source/multicast/media/image1.png

48.3 KB
Loading

source/multicast/multicast.rst

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
Multicast
2+
======================
3+
4+
This chapter describes the multicast-groups.
5+
6+
What can multicast-groups do?
7+
---------------------------------------------
8+
Multicast-groups make it possible to send a single downlink payload to a group of devices.
9+
10+
A multicast-group consist of some different properties like multicast-address, session-keys and frame counter. All these properties makes it possible to send only one downlink payload to a group
11+
of devices instead of sending many downlink payloads to devices one by one.
12+
13+
Multicast-groups does not support Class-A devices, and at this moment, multicast-groups only supports LoRaWAN devices.
14+
15+
Creation in OS2IoT
16+
-------------------
17+
If you want to make a multicast-group in OS2IoT you have to go into a specific application and then create the multicast-group from there.
18+
19+
You have to fill out all the required forms, and in the end you can add some devices. It's required that the devices share the same service profile, which is set when you create a LoRaWAN device.
20+
The multicast-address has to be an 8-character hexadecimal (hex) value, and the network and application session key has to be a 32-character hex value.
21+
22+
If these requirements are not met, then the multicast-group will not be created.
23+
24+
When you have added the devices that have the same service profile, and have filled out the other forms, then a multicast-group will be created in the database and in Chirpstack.
25+
26+
This sequence diagram describes the flow from the user to the Chirpstack Application Server:
27+
|image1|
28+
29+
Sending downlink payload
30+
-------------------------
31+
32+
When the multicast-group is created it's possible to send a downlink payload to the group of devices. This is done by navigating to the details page of the multicast-group, and from here you have to choose a specific port and a payload that you wish to send to the devices in the Multicast-group.
33+
34+
The downlink payload is sent using Chirpstack which also has the multicast-group with the devices from OS2IoT.
35+
36+
Explanation of properties
37+
--------------------------
38+
39+
A very short explanation of some of the properties that needs to be fulfilled when creating a multicast-group:
40+
41+
**Multicast address:** An address that defines the multicast-group. Has to be an 8-character hex value.
42+
43+
**Application Session Key:** An application session key used to encrypt the payloads that are send to the multicast-group. Has to be a 32-character hex value.
44+
45+
**Network Session Key:** A network session key is used to compute the message integrity check field of the packets sent to the group. Has to be a 32-character hex value.
46+
47+
----------
48+
49+
.. |image1| image:: ./media/image1.png

0 commit comments

Comments
 (0)