Thread Network Roles Workbench

Build a correct mental model for Thread roles, partitions, Router IDs, Border Routers, and sleepy end devices

animation
thread
mesh
leader
router
reed
border-router
ipv6
Learner-ready Thread network roles workbench with a visual Thread partition, role transitions, router-count guardrails, RLOC16 addressing, partition split/merge behavior, Border Router routing, quick reference, guided practice, and primary OpenThread source links.
Thread mesh Roles Partitions IPv6

Thread network roles, formation, and repair

A Thread network is not just one coordinator with many leaves. Routers form the forwarding backbone, End Devices attach to parents, the Leader manages router state inside a partition, and Border Routers connect that Thread mesh to other IP networks. Use the presets first, then change the router count, link fade, child pressure, and Border Router availability.

Leader One per partition
Routers Target 16-23, max 32
End devices Attach to one parent
Border Routers Zero, one, or many
Beginner ramp

What to notice before pressing Play

Thread uses IEEE 802.15.4 radios and IPv6 networking. The key idea is that device role and network position can change as links, router count, and child load change.

Forwarding role

A Router forwards packets for other devices. An End Device does not forward; it sends traffic through its parent Router.

Device type

FTDs can be Routers or children. MTDs, including MED and SED, can only be End Devices.

Network vs partition

Security credentials define the Thread network. Radio connectivity decides whether that network is currently one partition or split into multiple partitions.

Interactive workbench

Trace the role changes

Dataset and radio settings identify the Thread network before a device attaches. The Leader is not yet the same thing as off-mesh connectivity.

Controls

Step through the stages or choose a scenario. The visual, table, metrics, and diagnosis update together.

18
Thread tries to keep enough Routers for coverage and redundancy while staying below the 32-router limit.
4 dB
Higher fade weakens router-router links and can create a second partition if groups cannot hear each other.
24 children
Heavy child load can make another Router or REED promotion useful for parent capacity and coverage.
2
A Thread mesh can keep local connectivity even when off-mesh IPv6 routing is unavailable.
The highlighted role changes the table row and the addressing example.
Router count in target band Single partition Off-mesh route available

Thread partition view

Leader, Border Routers, Routers, REED, MED, and SED are in one partition with usable router-router links.

Stage 1: Dataset known
Thread network roles and partition behavior Thread mesh with Leader, Border Router, Routers, REED, MED, Sleepy End Device, MLE messages, partition boundary, and external IP network. Thread partition A same partition Wi-Fi / Ethernet / Internet L Leader Router ID manager BR Border Router off-mesh IPv6 route R Hall Router router-router link R Kitchen Router same partition RE Garage REED eligible child S Weather SED polls parent M Display MED radio on child DS Active Dataset: channel, PAN ID, network name, key
L

Leader manages router state

One Leader exists in this partition and distributes network-wide data.

R

Routers form the backbone

Routers keep radios on, forward traffic, and maintain router-router links.

S

End Devices attach to parents

The Sleepy End Device conserves power by polling its parent Router.

BR

Border Router provides off-mesh reach

External IPv6 routing is available through at least one Border Router.

Task flow

Six stages of the mental model

1

Dataset known

Channel, PAN ID, network name, and credentials identify the target Thread network.

2

Leader exists

A Router becomes Leader for this partition and manages Router IDs and network data.

3

Child attaches

End Devices choose a parent with MLE Parent Request and Parent Response.

4

Routers link

Routers maintain router-router links and keep the connected backbone usable.

5

Border routes

Border Routers advertise off-mesh connectivity and services for external IP reach.

6

Repair

Role changes, REED promotion, or partition merge/split behavior respond to topology changes.

Diagnosis

Current network reading

Network state

One healthy partition

Routers can hear each other, so the partition has one Leader and one set of Router ID assignments.

Role pressure

Router count in target band

Router count is inside the preferred operating range, so REED promotion is not urgent.

Addressing

RLOC16 example: 0x3003

The RLOC16 is a topology locator derived from Router ID and Child ID. Applications should normally prefer stable Endpoint Identifiers.

Evidence table

Role evidence and learner checks

Use this table to decide whether a device forwards, sleeps, manages router state, or provides external connectivity.

Device Current role Forwards for others? Can sleep? Evidence to notice
Quick reference

Keep these distinctions straight

Leader

A Router role inside a partition. It manages Router IDs and network-wide data. It is dynamically self-elected for fault tolerance.

Border Router

Forwards information between Thread and a non-Thread network such as Wi-Fi or Ethernet. It is not automatically the Leader.

REED

A Router Eligible End Device can be promoted to Router after the Leader grants a Router ID.

SED and MED

Minimal Thread Devices are children only. A MED keeps its radio on; a SED sleeps and polls its parent.

Router range

Thread supports up to 32 Routers and tries to keep enough Routers for coverage and redundancy, commonly 16 to 23.

Partition

If groups cannot communicate by radio, each partition has its own Leader and Router IDs while retaining the same network credentials.

RLOC16

RLOC16 is based on Router ID and Child ID. It can change when a device moves to a different parent or becomes a Router.

ML-EID

The Mesh-Local EID is topology independent inside the partition and is a better mental model for application identity.

Guided practice

Three checks to perform

Find the Leader/BR distinction

  • Select Border route loss.
  • Notice that the mesh still has a Leader.
  • Explain why local Thread traffic can still work.

Trigger a REED promotion

  • Select REED coverage.
  • Lower router count below 16.
  • Watch the REED become a Router when coverage needs it.

Diagnose a partition

  • Select Partition split.
  • Increase link fade above 18 dB.
  • Explain why each partition gets its own Leader.
Deeper notes

Technical guardrails

Leader repair is not taught as a Raft implementation

This workbench avoids calling Thread Leader behavior a Raft algorithm. For learners, the reliable model is: one Leader manages a partition; if radio connectivity changes or the Leader disappears, Thread maintains operation by selecting a Leader for the reachable partition and distributing network data.

RLOC16 is useful, but not a stable application identity

The teaching formula is RLOC16 = (Router ID << 10) | Child ID. A Router has child ID 0. A child has a child ID assigned by its parent. Because this locator depends on topology, a device can receive a different RLOC16 after changing parent or becoming a Router.

Primary source links
OpenThread primer Node roles and types

Router, End Device, FTD, MTD, REED, Leader, Border Router, partitions, and device limits.

 OpenThread primer Router selection

Connected Dominating Set, Router ID solicit, REED upgrade, and router-router links.

 OpenThread primer Network discovery

MLE discovery, Parent Request, Parent Response, Child ID Request, and attach flow.

 OpenThread primer IPv6 addressing

Link-Local, Mesh-Local, RLOC, ML-EID, ALOC, and RLOC16 behavior.