Thread Group: certifying the 802.15.4 IPv6 mesh

Author Hugues Orgitello Last updated 27 May 2026 ~15 min read

Guide · Thread Group

Thread Group certification is, like Bluetooth SIG qualification or Wi-Fi Alliance certification, a private interoperability regime. The Thread Group, formed in 2014 by Nest, ARM, Silicon Labs and several other industrial members, publishes the Thread protocol specification and operates the certification programme that conditions its commercial use. Thread is a low-power IPv6 mesh networking stack built on top of the IEEE 802.15.4 physical and MAC layers, designed for smart-home and industrial IoT meshes. This page describes the scope of the programme, the membership tiers (Adopter, Affiliate, Sponsor), the device roles (Border Router, Router, REED, FED, MED, Sleepy End Device), the spec evolution from Thread 1.0 to 1.4, the certification workflow at an Authorized Test Lab and its articulation with the underlying radio regimes and with Matter.

What Thread is

Thread is a low-power IPv6 mesh network protocol specified by the Thread Group. Its scope is strictly that of the network and transport layers of the OSI stack: IPv6 routing over 6LoWPAN, mesh formation and maintenance, network security (MLE, commissioning), local service discovery (mDNS / DNS-SD). The physical and MAC layers are entirely delegated to IEEE 802.15.4, from which Thread inherits the O-QPSK modulation and CSMA-CA medium access.

OSI layer	Thread	Zigbee comparison	Wi-Fi comparison
Application	Out of scope (Matter, proprietary...)	Zigbee Cluster Library	Out of scope
Transport	UDP, TCP (rare) over IPv6	Zigbee APS, proprietary	UDP, TCP
Network	IPv6, 6LoWPAN, slim RPL	Zigbee NWK (proprietary)	IPv4 / IPv6
Link	IEEE 802.15.4 MAC	IEEE 802.15.4 MAC	IEEE 802.11 MAC
Physical	IEEE 802.15.4 O-QPSK 2.4 GHz	IEEE 802.15.4 O-QPSK 2.4 GHz	IEEE 802.11 OFDM

Three practical consequences follow from this architecture:

• Thread does not define an application. A Thread product knows only how to route IPv6 packets through its mesh. Business logic (turn on a light, read a sensor) requires an additional application layer, today most often Matter, sometimes a proprietary protocol.
• Thread does not define the radio. The underlying 802.15.4 circuit remains subject to national regimes (RED in the EU, FCC in the US, SRRC in China, TELEC in Japan, and so on).
• Thread does not enforce an application brand. The Thread logo attests network conformance, not application interoperability between two different products. For that, a second certification is required, typically Matter.

The Thread Group and its programme

The Thread Group is a paid-membership organisation incorporated in the United States. It owns the Thread trademarks, operates the certification portal, publishes the member-only specification and accredits the test laboratories (Authorized Test Lab, ATL). The word Thread, the logo and its variants (Thread 1.x, Thread Certified Component) are protected by international trademark filings, and unauthorised commercial use opens the door to an infringement action.

Three membership tiers structure programme access:

• Adopter: entry level, sufficient to certify products, access the published specification, use the Thread brand on certified products. No access to the technical working groups or to draft future versions.
• Affiliate: intermediate level, with an annual subscription. Grants access to the Working Groups, to draft future specifications, to voting rights on some technical decisions, and to reduced certification fees.
• Sponsor: higher tier, reserved to major contributors (silicon vendors, large integrators, ecosystem providers). Sits on the Board of Directors, drives roadmap and version schedule.

Tier	Subscription	Working Group access	Vote	Product certification
Adopter	Modest, confirm with Thread Group	No	No	Yes, standard fees
Affiliate	Annual, higher	Yes	On some committees	Yes, reduced fees
Sponsor	Sponsor commitment	Yes, priority contribution	Board	Yes, reduced fees

Exact amounts evolve and must be confirmed directly with the Thread Group. A manufacturer integrating an already certified Thread module usually picks Adopter. Moving to Affiliate is justified for stack designers, silicon vendors and players who want to weigh in on the evolution of the standard.

Thread device roles

Thread architecture defines several functional roles a device can take in the mesh. The same product can, depending on its configuration and resources, play one role or another, and switch between them dynamically. Certification applies to the role declared in the dossier.

Border Router

The Thread Border Router (TBR) is the junction point between the 802.15.4 mesh and an external IPv6 network, typically Ethernet or Wi-Fi. Its functions are multiple:

• Relay IPv6 traffic between the two networks, with neighbour discovery proxying as needed.
• Act as a service discovery agent via mDNS / DNS-SD to expose Thread end devices to the rest of the LAN.
• Host the Commissioner or relay a commissioning session to an external Commissioner (a phone).
• Maintain mesh security by responding to MLE requests and distributing the network key to new joiners.

A Border Router is a full product in its own right, with its own test plan, its own certification requirements and its own operational responsibilities. Apple HomePod, Google Nest Hub, Amazon Echo, Samsung SmartThings Hub, Eve Hub and several carrier gateways embed a certified Border Router.

Router and REED

A Router is a Thread end device that actively participates in mesh routing. It maintains routing tables, propagates MLE advertisements, parents End Devices and forwards packets across the network. A Thread mesh can run up to 32 active Routers simultaneously.

A REED (Router Eligible End Device) is an end device that behaves as an End Device in normal operation but can be promoted to Router dynamically by the network Leader if the mesh runs short on routers. This is an optimisation: avoid committing Router resources unless the network really needs them.

FED and MED

A FED (Full End Device) is an end device that maintains a permanent radio link with its parent Router. It stays fully addressable and receives downstream traffic without delay. Suits mains-powered or high-autonomy equipment (wall switches, mains sensors, outlets).

A MED (Minimal End Device) is a lighter variant of the FED, with a simplified Thread stack but still permanently active on the radio.

Sleepy End Device

A Sleepy End Device (SED) puts its radio to sleep between short polling windows, saving power. The parent Router buffers waiting packets, and the SED retrieves them on wake by an explicit poll. Ideal for sensors on long-life batteries (door contact, motion sensor, temperature probe).

Role	Routing	Radio	Typical use case
Border Router	Bridge to external IPv6	Always on	Smart-home hub, carrier gateway
Router	Active in mesh	Always on	Mains outlet, smart bulb
REED	Idle, promotable	Always on	Mains-powered end device
FED	None	Always on	Wall switch, mains sensor
MED	None	Always on, slim stack	Constrained end device
Sleepy End Device	None	Sleep + polls	Battery sensor

The chosen role structures the entire hardware project: power supply, antenna, flash footprint, target certification. A SED that needs to switch to Router for a major upgrade cannot do so without revisiting its power design.

Specification version evolution

The Thread Group publishes its specification in successive versions, adding features while preserving network backward compatibility wherever possible. Each version has a dedicated test plan, and certification is tied to a given version.

Version	Year (per Thread Group reference)	Main contributions	Typical status
Thread 1.0	First stable spec	IPv6 mesh on 6LoWPAN, MLE, basic commissioning	Obsolete
Thread 1.1	Minor evolution	Stabilisation, errata, security hardening	Still present on older hardware
Thread 1.2	Broadened scope	Improved multicast, CSL (Coordinated Sampled Listening) for low-power SEDs, Thread Domains	Deployed
Thread 1.3	Major milestone	TCAT (Thread Commissioning over Authenticated TLS), refreshed commissioning, Matter alignment, EPSKc	Common adoption
Thread 1.4	Recent milestone	Broader range of credential types, multi-PAN, TBR refinements for carrier-scale use	Early adoption

A few practical points:

• Thread 1.3 marks the Matter pivot. Historical Thread commissioning ran through an external Commissioner over BLE; Thread 1.3 introduces TCAT, which lets a device establish an authenticated TLS session directly over the Thread channel, without necessarily relying on BLE for the authorisation phase. Matter 1.0 and above rely on Thread 1.3 mechanisms.
• Thread 1.4 broadens the palette of credentials accepted by commissioning and adds refinements for Border Routers operated at scale, for instance by a telecom carrier or an ecosystem aggregator.
• Network backward compatibility holds in the vast majority of cases (a 1.2 device can join a 1.3 mesh), but product certification stays tied to the declared version. Moving an in-service product from 1.3 to 1.4 over the air requires a formal update of the product dossier.

Position in the certification stack

For a Thread product targeting EU and US markets, the minimum regime stack looks like this:

Regime	Scope	Required when...
CE marking + RED art. 3.2	802.15.4 spectrum in 2.4 GHz	Placed on the EU market
CE marking + RED art. 3.3	Cybersecurity, EN 18031	Placed on the EU market, from August 2025
FCC Part 15.247	2.4 GHz emitter in the US	Placed on the US market
Thread Group	Protocol conformance and Thread logo	Thread logo displayed and Thread feature
Bluetooth SIG	Commissioning BLE, Bluetooth logo	BLE used for commissioning
CSA Matter	Matter application layer	Matter logo and Apple, Google, Amazon, Samsung ecosystems

None of these regimes substitute for one another. See the RED pillar for the European radio directive, the FCC pillar for the US route, the Matter guide for the application layer, and the Bluetooth SIG guide for the commissioning BLE. Wi-Fi Alliance certification, sibling of Thread Group certification on the Wi-Fi side, is covered in the Wi-Fi Alliance guide.

Articulation with the 802.15.4 radio regime

The Thread radio operates in the 2.4 GHz band (channels 11 to 26 of the IEEE 802.15.4 plan). It is therefore subject to the same radio regimes as Wi-Fi, Bluetooth and Zigbee in this band, in addition to Thread Group certification on the protocol side.

EU side, RED article 3.2

The conformance report rests on EN 300 328, the harmonised standard covering all transmitters in the 2.4 GHz band, including low-power DSSS radios of the 802.15.4 family. Tests address maximum radiated power, spectral occupancy, modulation and collision avoidance. The EN 300 328 report says absolutely nothing about the Thread protocol, and conversely the Thread Group test plan does not measure radio power.

Other RED articles remain applicable: 3.1(a) safety via EN 62479 or EN 62311 depending on power level, 3.1(b) radio EMC via EN 301 489-17, and from August 2025 article 3.3 cybersecurity via EN 18031. Detail on the RED tests page.

US side, FCC Part 15.247

In the United States the 802.15.4 radio falls under 47 CFR Part 15.247, which governs unlicensed transmissions in the 2.4 GHz and 5 GHz bands. Requirements address conducted power, out-of-band emissions, modulation and coexistence. The FCC report yields an FCC ID via a TCB. See the FCC pillar for the full scope.

Here too, the FCC ID does not cover Thread Group certification, and conversely. A Thread product distributed in both regions therefore accumulates: RED + FCC for the radio, Thread Group for the protocol, plus Matter and Bluetooth SIG depending on the features, plus Wi-Fi Alliance certification if the Border Router includes a Wi-Fi radio. See EU + US dual certification for the framing of a dual programme.

Coexistence with Zigbee on the same chipset

Most recent 802.15.4 chipsets share their radio between Thread and Zigbee, in concurrent or alternating multiprotocol. On the silicon vendor side, this has become a standard pitch: Silicon Labs EFR32MG, Nordic nRF52840 and nRF54, Espressif ESP32-H2 and C6, NXP K32W and RW61x, Texas Instruments CC2652 and CC1352 all ship SDKs that stack a Thread stack and a Zigbee stack simultaneously on the same physical radio.

This duality has two consequences for certification:

• On the radio side, a single EN 300 328 or FCC Part 15.247 report is enough, since the RF circuit is identical. The report covers 802.15.4 use without distinguishing the upper protocol.
• On the protocol side, two separate certifications are required: Thread Group for Thread, CSA for Zigbee (the CSA, formerly the Zigbee Alliance, merged Zigbee and Matter governance). Each dossier covers its own stack, its own test plan and its own profiles.

A dual-stack product is therefore not a product whose certification is doubled overall; it is a product whose radio is tested once but whose protocol layers are tested twice.

Commissioning: the role of BLE

A Thread End Device leaving the factory knows nothing about the surrounding Thread network: it does not know the network key, the radio channel (among the sixteen available in 2.4 GHz), the PAN ID or the topology of Border Routers. Commissioning is the procedure by which a Commissioner conveys this information to the joiner and authorises it to enter the mesh.

Several paths coexist:

• BLE commissioning. Historical and still dominant path. The device exposes an ephemeral BLE session, intercepted by a phone (typically the ecosystem app, for instance Apple Home or Google Home). The BLE phase transfers Thread credentials (key, channel, PAN ID), then the device switches to the Thread radio and joins the mesh. This BLE is not optional: it requires Bluetooth SIG qualification of the device for the right to use the Bluetooth brand, and applicable BLE radio compliance.
• Border Router commissioning via TCAT (Thread 1.3+). The device can establish an authenticated TLS session directly over Thread, with an EPSKc (Ephemeral PSK for Commissioning). This path reduces BLE dependence in some architectures, but does not remove it for consumer ecosystems where the phone remains the Commissioner.
• Out-of-band commissioning. Manual key entry on an integrated screen, QR code scan by a Border Router camera, NFC. Rare in consumer products, present in industrial.

Practical conclusion for the project: plan BLE and its Bluetooth SIG qualification as a mandatory function, not as an option. Bluetooth SIG qualification is covered in the Bluetooth SIG qualification guide.

The certification process at an ATL

Standard sequence of a Thread Group certification, from route selection to public registry listing:

1. Thread Group membership. Create an account on the Thread Group portal, administrative validation, payment of the Adopter subscription at minimum. Short administrative delay, depends on the Thread Group.
2. Choose the route and the parent component. Identify whether the product relies on an existing Thread Certified Component (chipset, module, stack), in which case a streamlined compliance review is possible. Otherwise, plan a full certification.
3. Define the role. Border Router, Router, REED, FED, MED or Sleepy End Device. The declared role conditions the applicable test plan. A device combining multiple roles (typically a Router that can fall back to REED) must declare so.
4. Prepare the technical artefacts. Documentation of the stack in use (OpenThread from Apple/Google/Nordic, vendor stack, proprietary stack), target version (1.3, 1.4), configuration parameters, antenna, power supply.
5. Internal pre-tests. Validation on a test bench with the official Thread Test Harness, ensuring that the test cases for the targeted role pass internally. Identify gaps before paying for external testing.
6. Select an Authorized Test Lab. Public list on the Thread Group portal, up to date. Engage the lab, ship the product, transmit the technical dossier and the submission form.
7. ATL test plan execution. The lab runs the tests on the device, across all cases of the declared role. Protocol conformance, network robustness (parent loss, fragmentation, Router rotation), commissioning, security (key verification, MLE, KEK).
8. Report and submission to the Thread Group. The lab issues the report, the manufacturer assembles its dossier (declaration, certification fees), and the whole is submitted to the Thread Group for review.
9. Compliance Review. The Thread Group examines the report, requests any complements, and rules on certificate issuance. For a product based on an already certified component, this stage can short-circuit part of the testing.
10. Listing in the public registry. The certified product appears in the Thread Certified Products database with its commercial name, manufacturer, Thread version and the list of its certified roles.
11. Brand and logo application. Once certified, the manufacturer can display the word Thread and the official logo, in compliance with the Thread Group brand book (size, contrast, clear space).
12. Maintenance. Update the dossier on any hardware or firmware change affecting Thread. An undocumented modification invalidates the certification.

Total timeline depends on the role, on the team's maturity and on ATL availability. Exact durations vary by lab and spec version, and must be confirmed at the start of the programme.

Reuse via compliance review

A distinctive feature of the Thread Group programme is compliance review: a product inheriting a Thread Certified Component (chipset, module, or stack), without modification of the Thread layer, can follow a streamlined procedure. The candidate submits the dossier indicating the parent component, the Thread Group verifies that the assumptions hold (no stack modification, compatible antenna, consistent configuration), and a reduced test suffices.

This mechanic is the functional counterpart of Bluetooth SIG EPL or Wi-Fi Alliance Member Product reuse: it avoids redoing full protocol testing for every product variation. Practical conditions:

• The parent component must be listed in the Thread Group registry at Certified status and cover the Thread version targeted by the product.
• The Thread layer of the component must not be modified, neither in firmware nor in stack configuration.
• The role declared by the finished product must be included in the certified scope of the parent component.
• Any hardware change (antenna, RF supply, layout) or software change (stack parameters, added functions) takes the product out of scope and triggers a new certification.

For a team integrating a Silicon Labs MGM240, Nordic nRF52840, Espressif ESP32-H2 or NXP K32W module that is already certified, compliance review significantly reduces delays and costs. For a team developing its own Thread stack, the only path is full certification.

Frequent pitfalls

Assuming Matter covers Thread

The most common mistake on first Matter-over-Thread products. A CSA Matter certification says nothing about the Thread conformance of the device. The two regimes are run by two distinct organisations, with two dossiers, two test plans, two ATL lists and two public registries. A product displaying the Matter logo and using Thread as its network layer must hold both certifications, under penalty of misuse of one of the marks.

Forgetting Border Router certification

The Border Router is a full Thread product. When a manufacturer launches a smart-home hub combining Wi-Fi and Thread, it must certify the hub as a Border Router, on top of the Matter certification of the hub and the Wi-Fi Alliance certification of the Wi-Fi segment. Many teams treat the Border Router as a mere accessory to the main device and discover late that it is in fact the most demanding piece on the Thread Group side.

Modifying the Thread stack without recertifying

A product inheriting a certified module under compliance review rests on the strong assumption that the stack is not modified. Any local patch (proprietary bug fix, adjusted timings, added Thread feature) takes the product out of scope. The rule is the same as in Bluetooth SIG or Wi-Fi Alliance: the qualified stack must be shipped as-is.

Confusing Thread Group certification with radio compliance

A manufacturer who thinks that its EN 300 328 report or its FCC ID covers Thread Group certification stalls its project at the last gate. The two regimes are disjoint and their deliverables do not overlap: one measures power and spectral occupancy, the other measures protocol conformance. Both must exist, in parallel, before placing on the market.

Underestimating commissioning BLE

BLE is not optional in the vast majority of consumer Thread architectures. It must be treated from design as a certified subsystem: Bluetooth SIG qualification on the logo side, EN 300 328 or Part 15.247 report on the radio side (the same report can cover BLE and 802.15.4 if the radio is shared), EN 301 489-17 conformity on the EMC side. Discovering BLE mid-programme adds several weeks.

Bumping the Thread version without updating the dossier

Thread network backward compatibility is strong, which can suggest that a 1.2-certified device stays certified when bumped to 1.3 or 1.4 over the air. False from the programme side: certification is tied to a version. A major bump requires a formal dossier update, possibly a new submission.

Misdeclaring the device role

A device that can switch between REED and Router on the Leader's request must declare both roles. An incomplete declaration leads to a partial test plan and to a production failure risk when the untested role triggers. Conversely, declaring unimplemented roles needlessly inflates the test plan.

Stacking Zigbee on the same radio without stacking certifications

An 802.15.4 chipset running dual-stack Thread + Zigbee needs two distinct protocol certifications: Thread Group for Thread, CSA (formerly Zigbee Alliance) for Zigbee. The 802.15.4 radio certification is shared, but the protocol certifications are not. A product displaying both logos without having cleared both regimes is in breach on both marks.

Going further

Working on framing a Thread project and its articulation with Matter for a real product? AESTECHNO can audit your design and certification plan. Get in touch →

See also the glossary for the definitions Border Router, REED, FED, MED, TCAT, as well as the guides Matter certification, Bluetooth SIG qualification, Wi-Fi Alliance certification, and EU + US dual certification.

Sources & references

1. Thread Group , Thread Group www.threadgroup.org/
2. Thread Group, What is Thread / Benefits , Thread Group www.threadgroup.org/What-is-Thread/Thread-Benefits
3. IEEE 802.15.4 Working Group , IEEE www.ieee802.org/15/pub/TG4.html
4. ETSI EN 300 328, transmission systems in the 2.4 GHz band , ETSI www.etsi.org/deliver/etsi_en/300300_300399/300328/
5. 47 CFR Part 15.247, unlicensed operation in 2.4 GHz and 5 GHz bands , FCC www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-C/section-15.247
6. CSA Matter, overview , Connectivity Standards Alliance csa-iot.org/all-solutions/matter/