Thread

What is Thread?

Thread is a low-power, IPv6-based mesh networking protocol designed for smart home and IoT devices. It was developed by the Thread Group, led by companies like Google, Apple, and Silicon Labs. It aims to provide secure, reliable, and scalable device-to-device communication.

Why is Thread useful?

  • Designed for reliable mesh networking, enabling self-healing communication paths.

  • Based on open standards (IPv6, 6LoWPAN, IEEE 802.15.4).

  • Supports low power consumption, making it ideal for battery-operated devices.

  • Built-in security with device authentication and encryption.

  • Works with Matter, making it a key technology in future-proof smart homes.

How it works?

  • Thread uses IEEE 802.15.4 at the physical and MAC layers for low-power wireless communication in the 2.4 GHz band.

  • Uses 6LoWPAN to compress IPv6 packets for efficient transmission.

  • Devices form a mesh network, with routers forwarding messages between endpoints.

  • A Thread Border Router connects the mesh network to other IP-based networks (like Wi-Fi or Ethernet).

  • Thread ensures secure joining and dynamic rerouting in case of node failures.

Where is Thread used?

  • Smart home devices: lights, thermostats, locks, sensors.

  • Consumer IoT: appliances, environmental sensors.

  • Building automation: access control, HVAC systems.

  • Matter-compatible devices, as Matter supports Thread for low-power networking.

Which OSI layer does this protocol belong to?

  • Thread spans multiple OSI layers: * Layer 1 (Physical): IEEE 802.15.4 radio. * Layer 2 (Data Link): MAC layer of 802.15.4. * Layer 3 (Network): IPv6 over 6LoWPAN. * Layer 7 (Application): Supports application protocols like Matter.

IS Thread Windows specific?

  • No, Thread is not Windows-specific.

  • It is designed for embedded systems and microcontrollers, not desktop or server operating systems.

  • Windows-based applications can communicate with Thread networks via Thread Border Routers.

IS Thread Linux Specific?

  • No, Thread is not Linux-specific.

  • However, Linux is commonly used on Thread Border Routers (e.g., OpenThread Border Router).

  • End devices typically run on bare-metal firmware or RTOS platforms.

Which Transport Protocol is used by Thread?

  • Thread supports IPv6 over 6LoWPAN.

  • At the transport layer, it supports: * UDP (mainly used for low-overhead communication). * ICMPv6 (for diagnostics and routing).

  • TCP is not supported due to overhead and power concerns.

Which Port is used by Thread?

  • Thread does not define a specific fixed port for all communication.

  • Application protocols (like CoAP over UDP) define their own ports.

  • Example: CoAP typically uses UDP port 5683.

Is Thread using Client server model?

  • Yes, application protocols over Thread (like CoAP or Matter) follow a client-server or request-response model.

  • The network layer itself (Thread) handles routing and addressing in a mesh topology, not application roles.

Topics in this section,

  • In this section, you are going to learn

  • Terminology

  • Version Info

  • rfc details

  • setup

  • setup

  • packet details

  • usecases

  • features

  • Reference links