Thread network technology - 01 introduction (IEEE802.15.4, 6LowPAN, IPv6, UDP, CoAP)

Thread is a network technology for wireless networks based on IPv6. It is ideally suited for home automation, Industry 4.0 and wireless sensor-actuator networks. The Thread Group was founded in 2014 and its founding members include Google Nest, Osram and Samsung. Apple joined the group in 2018. Thread is based on the reliable IEEE 802.15.4 standard, which enables secure wireless communication from radio modules that are directly within range. Thread extends this standard to include the ability to create IPv6-based mesh networks, so that routing makes it possible to build larger networks and to reach radio modules that are not in direct range.
You can support me at Patreon:
/ wsnandiot
00:00 Overview
01:41 Thread layers
04:32 Forwarding roles
05:26 Device types
06:45 REED upgrading
08:46 Thread Leader and Border Router
10:30 Partitions
12:02 Device limits
14:41 IPv6 address types
16:51 IPv6 address scopes
19:19 Mesh Local Endpoint Identifier (ML-EID)
20:22 Routing Locator
23:52 Summary

[@rosskappa5410]

Loved it. Very systematic and clear. Sometimes your English is unclear to me but I can understand it better as I adjust to it. Thank you.

[@dheemz]

Good job !!

[@nicoladellino8124]

Very nice video, TNX.

[@theebz1]

Awesome. Thank you. 😀

[@b.saravanakumarsaravanan7797]

great video sir

[@leoxie1971]

nice video!

[@jeevakumar6376]

Good

[@wsniot]

Thank you.🙂

[@dreamEater99]

Thank you for the excellent video series about Threads. I was able to set up my Nordic boards and play around with them. I have a question, how does one differentiate between ZigBee and Thread traffic in the 802.15.4 MAC layer? Both of them use the same 802.15.4 standard. The scope of the Source, Destination, PAN ID is the same for both and the MAC addresses is not sent every packet. Also, could you please do a video series on ZigBee? Thank you again and subbed!

[@wsniot]

At the MAC level, it is not possible to distinguish whether it is a Thread or a ZigBee packet. There is no flag in the MAC header or anything. The difference only becomes visible in the payload. It might be better to avoid using the same PAN ID on the same channel. However, thread networks are always encrypted, i.e. only devices that have the same key can unpack the packet. While ZigBee networks can be unencrypted, they should also be encrypted in general. But even in the worst case, using the same PAN ID and key shouldn't cause any major problems. At the latest when interpreted as an IPHC header (Thread) or NWK header (ZigBee), a packet that does not follow the corresponding header structure would be discarded. Packets from another network protocol are not forwarded anyway.

[@dreamEater99]

@@wsniot Thank you so much for the detailed explanation. I have searched the spec and the internet for an answer and none of them went into this detail. Like you said, looking into the payload might give a clue. Thanks anyway, your answer validated my understanding as well!