Thread Parent Selection

Thread Parent Selection

animation
thread
networking

End devices depend on parents. That relationship is architectural, not just operational. A parent must be available for the child communication pattern, and the child must be configured for the latency and power behavior the application expects.

Child role claim: battery contact sensor reports local state without routing traffic.
Parent evidence: attached to a nearby router with an observed parent-child relationship.
Application boundary: local event delivery is accepted; immediate inbound commands are not part of the claim.
Retest trigger: parent moved, wall power changed, firmware changed, or alert latency requirement changed.

For a low-power child, the architecture record should not say “the mesh heals itself” and stop. It should say which parent-child assumption was observed, what happens if the parent is unavailable, and what application behavior is still acceptable.

Thread parent selection narrated tour

Narrated audio tour. The full transcript is below.

Play the tour to open the simulator. Pause, replay a beat, or read the full transcript below.

Some beats explain situations this teaching model cannot show; those beats keep the existing frame and provide captions only.

Full transcript — Thread parent selection (8 beats)

B1 — Battery sensor
You are setting up a battery contact sensor in a building. Your job is to get its local state reports delivered. The sensor depends on a parent router, so choosing the parent matters to the communication you are trying to support.

Model caption: You are installing a battery contact sensor. Local state delivery depends on a parent router.

B2 — Parent Request
In Thread, the parent carries the child's ordinary network traffic. Parent selection means finding an acceptable router for the job. Our sensor already has the network credentials it needs. It begins by sending a Parent Request to neighboring routers.

Model caption: The child has network credentials and sends a Parent Request to neighboring routers. Its selected parent will carry ordinary network traffic.

B3 — Parent Responses
The routers send Parent Responses with link margin and connectivity information. Link margin measures how far the received signal is above the minimum level needed to receive it. It is expressed in decibels; a larger margin gives more room for the signal to weaken. Connectivity describes how routers connect to the network. The child compares acceptable candidates. The workbench uses an explanatory teaching score for the comparison, with lower scores ranked first.

Model caption: Parent Responses supply link margin in decibels and connectivity evidence. The teaching model ranks acceptable candidates by ascending score.

B4 — Balanced comparison
Take the balanced example. Hall Router has a link margin of twenty-four decibels and five children out of a maximum of twelve. Kitchen Router has eighteen decibels and nine children out of twelve. For Hall, the model adds a connectivity penalty of seven to a load penalty of six to get thirteen. For Kitchen, it adds a radio penalty of thirty-two, a connectivity penalty of three, and a load penalty of eleven, then subtracts a priority bonus of ten to get thirty-six. Lower scores rank first, so the model selects Hall.

Model caption: Balanced: Hall 24 dB, 5/12 children, score 13; Kitchen 18 dB, 9/12, score 36. Hall is selected.

B5 — Capacity limit
Now add seven children to Hall while keeping the radio conditions unchanged. Five plus seven makes twelve. Hall has reached its limit of twelve children, so the model excludes it from the acceptable candidates. Its twenty-four decibels of link margin have stayed exactly the same.

Model caption: Hall: 5 + 7 = 12 children, at its 12-child limit. Its 24 dB margin is unchanged, but capacity excludes it.

B6 — Child ID handshake
Kitchen still has nine children out of twelve, with a link margin of eighteen decibels. Its score remains thirty-six, and it becomes the selected parent. The child then completes the final request and response with the chosen parent to establish their link. For your sensor, the choice is Kitchen.

Model caption: Kitchen: 18 dB, 9/12 children, score 36. Kitchen wins among acceptable candidates; the final request and response establish the child-parent link.

B7 — Radio and capacity
A common mistake is to assume Hall can accept another child because its signal is unchanged, but Hall has the higher link margin and no free child slot. Kitchen wins the model's comparison among candidates able to accept the child. Link margin and available capacity both matter when choosing the sensor's parent.

Model caption: Stronger radio evidence alone does not win: Hall has 24 dB but no room; Kitchen has 18 dB and available capacity.

B8 — Usable link and room
Choose a parent with a usable link and room for the child.

Model caption: Choose a parent with a usable link and room for the child.

Back to the chapter