Niche wireless: ANT+, KNX-RF, DECT ULE, 6LoWPAN
Guide, niche wireless protocols
Beyond Wi-Fi, Bluetooth Low Energy and the cellular family, an electronics engineer integrating a wireless link will sooner or later face a niche protocol with its own ecosystem, its own alliance and its own certification logic. Four recur in industrial and consumer projects: ANT and ANT+ for sport and fitness, KNX-RF for building automation, DECT ULE for residential gateways and home security, and 6LoWPAN as the IPv6 adaptation layer underlying Thread, Wi-SUN and various 802.15.4 deployments. None of these protocols replaces the underlying radio certification regime (FCC Part 15, RED 2014/53/EU, MIC). Each adds an alliance-level interop layer that determines logo rights and ecosystem compatibility. This guide maps the four protocols, their alliances, their underlying standards and the recurring industrialisation pitfalls.
Comparison at a glance
Section titled “Comparison at a glance”| Protocol | Band | Underlying radio standard | Alliance | Interop cert |
|---|---|---|---|---|
| ANT and ANT+ | 2.4 GHz ISM, FHSS | FCC Part 15.247, EN 300 328, MIC | ANT+ Alliance (Garmin) | ANT+ Manage, profile-based |
| KNX-RF | 868 MHz EU sub-GHz, 2.4 GHz multi-band | EN 300 220, EN 300 328 | KNX Association | KNX certification, mark licence |
| DECT ULE | 1.880, 1.900 GHz EU; 1.920, 1.930 GHz US (DECT 6.0) | EN 301 406, ETSI TS 102 939, FCC Part 15.323 | DECT Forum and ULE Alliance | ULE Alliance product certification |
| 6LoWPAN | Inherits from 802.15.4 (2.4 GHz or sub-GHz) | EN 300 328 or EN 300 220, FCC Part 15.247 | None as such | Via Thread, Wi-SUN or custom |
The table makes the structural point: each of these protocols sits on a different band, with a different radio standard, and a different governance body. There is no single certification that covers all four.
ANT and ANT+
Section titled “ANT and ANT+”Protocol origins and positioning
Section titled “Protocol origins and positioning”ANT is a 2.4 GHz wireless protocol designed in 2003 by Dynastream Innovations, a Canadian company acquired by Garmin in 2006 and re-named Garmin Canada. It targets ultra-low-power sensor networks with star, tree and mesh topologies and sub-millisecond latency. The radio uses frequency hopping spread spectrum (FHSS) on the ISM 2.4 GHz band, with very short transmission bursts and a low duty cycle, which gives multi-year coin-cell battery life for typical sensor payloads.
ANT+ is the interoperability layer built on top of ANT. It defines public device profiles describing how a category of devices exchanges data: heart rate, bike power, bike speed and cadence, foot pod, weight scale, glucose monitor, blood pressure, environment sensor, and several dozen others. A chest strap built to the ANT+ heart rate profile pairs with any ANT+ watch supporting that same profile, regardless of manufacturer.
Underlying radio certification
Section titled “Underlying radio certification”The ANT and ANT+ link is a 2.4 GHz radio that falls under the same regulatory regimes as Bluetooth or Zigbee on that band.
- United States: FCC Part 15.247 for digital transmission systems and frequency hopping spread spectrum, with the corresponding dwell time, channel occupancy and spurious emissions requirements. A grant of equipment authorisation is issued by an FCC-accepted Telecommunication Certification Body (TCB) and the FCC ID is affixed to the product.
- European Union: EN 300 328 for wideband transmission systems in 2.4 GHz, under the Radio Equipment Directive RED, with CE marking and the EU declaration of conformity.
- Japan: MIC certification under the Radio Law, with the Giteki mark for low-power data communication systems in 2.4 GHz.
- Other regional regimes (ANATEL Brazil, IFETEL Mexico, KC South Korea) apply as for any 2.4 GHz radio.
ANT+ Alliance certification
Section titled “ANT+ Alliance certification”ANT+ logo use and ecosystem listing go through the ANT+ Manage system, run by Garmin Canada as the steward of the ANT+ Alliance.
- The manufacturer registers as a participant through the ANT+ Manage portal.
- For each product, the manufacturer declares the implemented device profiles and runs the published profile test tools against the firmware.
- On successful self-declaration, the product is listed on the ANT+ product directory and the manufacturer is granted use of the ANT+ logo for that product.
- The model is not subject to a per-device royalty for ANT+ profile compliance.
The two paths are independent: the ANT+ profile self-declaration does not substitute for FCC, RED or MIC certification, and conversely an FCC-certified ANT radio without ANT+ profile compliance cannot use the ANT+ logo. Both paths must be planned together in the project schedule.
Common pitfalls on ANT
Section titled “Common pitfalls on ANT”- Missing FHSS dwell time declaration in the FCC filing. ANT uses a frequency-hopping scheme, and the FCC grant requires explicit declaration of the channel hopping pattern, dwell time per channel and total occupancy. A radio firmware that re-configures hopping behaviour after FCC test invalidates the grant.
- Conflating ANT and ANT+. A product can implement ANT without ANT+, but it cannot then claim ANT+ interop or use the ANT+ logo. The marketing claim must match the actual profile implementation.
- Antenna change after test. The FCC grant and the CE file are tied to the tested antenna. Swapping antennas in production for a similar but non-identical part invalidates the radio file and triggers a re-test.
KNX-RF
Section titled “KNX-RF”KNX-RF is the radio variant of the KNX building automation protocol, operating principally in the European 868 MHz sub-GHz band, with multi-band variants. It is certified through the KNX Association as part of the broader KNX programme that also covers KNX-TP (twisted pair) and KNX-IP. Underlying radio certification follows EN 300 220 for the sub-GHz EU side. A frequent error is to test a KNX-RF radio against the requirements applicable to KNX-IP or KNX-TP, which are not radio standards at all.
KNX-RF is treated in detail alongside DALI-2 and EnOcean in the KNX, DALI-2 and EnOcean certification guide, which covers the KNX Association certification programme, the KNX mark licensing model and the RED overlap. This page does not duplicate that material.
DECT ULE
Section titled “DECT ULE”What DECT ULE adds to classic DECT
Section titled “What DECT ULE adds to classic DECT”DECT (Digital Enhanced Cordless Telecommunications) was originally specified in 1992 for cordless telephony and is defined by the ETSI EN 300 175 series, with associated profiles such as ETSI EN 300 444 for Cordless Terminal Mobility (CTM). The DECT family operates in a licence-exempt but reserved band (no Wi-Fi or Bluetooth co-existence), which is the principal reason it has survived in industrial and home applications: the medium is far less congested than the 2.4 GHz ISM band.
DECT ULE (Ultra Low Energy) is a profile defined by ETSI TS 102 939, in cooperation with the DECT Forum and the ULE Alliance, that re-uses the DECT physical and MAC layers but adds:
- aggressive power-saving mechanisms (paging optimisation, short bursts, slot reservation) suitable for battery-powered sensors,
- a low-bitrate audio option (ETSI TS 102 527), useful for home security panel voice or HD voice notifications,
- a data plane for IP traffic between sensors and a residential gateway.
Band gap between EU and US
Section titled “Band gap between EU and US”The DECT family does not share a global band.
- European Union and large parts of EMEA: 1.880, 1.900 GHz, the original DECT band, under EN 301 406 and RED.
- United States: a US-specific variant known as DECT 6.0 sits at 1.920, 1.930 GHz, under FCC Part 15.323.
- Japan: a dedicated sJ-DECT allocation at 1.893, 1.906 GHz, under MIC.
A single-band radio engineered for the European DECT band cannot operate in the United States and vice versa. To cover both markets with one SKU, the design must support both sub-bands and both regulatory regimes, with a regulatory domain table selecting the correct band at startup. This band gap is a recurring source of design rework when a product designed for one market is later extended to the other.
DECT ULE certification
Section titled “DECT ULE certification”| Element | Body | Reference |
|---|---|---|
| Radio conformity EU | EU notified body or self-declaration under RED | EN 301 406, EN 301 489 |
| Radio conformity US | FCC-accepted TCB | FCC Part 15.323 (DECT 6.0) |
| DECT base profile | DECT Forum recognition | EN 300 444 (CTM) |
| ULE profile | ULE Alliance product certification | ETSI TS 102 939 |
| Audio profile | ULE Alliance (optional) | ETSI TS 102 527 |
The ULE Alliance maintains a product certification programme that delivers a ULE Certified mark on completion of interoperability testing against the ULE profile. The mark is granted per product reference, not per company, and is renewed when the underlying ETSI standards are revised. Underlying radio certification (RED, FCC, MIC) remains independent and must be completed in parallel.
Why a residential gateway designer picks DECT ULE over BLE
Section titled “Why a residential gateway designer picks DECT ULE over BLE”- Indoor range typically 50, 100 m through one or two interior walls, against 10, 30 m for BLE in similar conditions.
- Reserved band, so no Wi-Fi or Bluetooth contention, which is decisive in dense residential RF environments.
- Native HD voice support for security panels and intercom.
- Star topology with a central gateway, well suited to home security applications where every sensor reports to one hub.
The trade-off is a smaller silicon ecosystem than BLE and a per-band design constraint that limits SKU consolidation across regions.
6LoWPAN
Section titled “6LoWPAN”A layer, not a protocol stack
Section titled “A layer, not a protocol stack”6LoWPAN stands for IPv6 over Low-power Wireless Personal Area Networks. It is specified by the IETF:
- RFC 4944 (2007): transmission of IPv6 packets over IEEE 802.15.4, with the basic adaptation layer.
- RFC 6282 (2011): header compression format for IPv6 datagrams over 802.15.4, which reduces a 40-byte IPv6 header to a handful of bytes for the typical sensor packet.
- RFC 6775 (2012): neighbour discovery optimisations for low-power and lossy networks, reducing the chatter of standard IPv6 ND.
The role of 6LoWPAN is to carry IPv6 traffic over the constrained 127-byte 802.15.4 frames, with fragmentation, header compression and stateless address autoconfiguration adapted to a sensor network. It is an adaptation layer, not a complete stack. It defines neither the application layer, nor the routing protocol, nor the security model.
Certification path
Section titled “Certification path”There is no 6LoWPAN logo. The certification path comes from the upper-layer ecosystem that adopts 6LoWPAN.
| Ecosystem | What it adds | Certification body |
|---|---|---|
| Thread | 6LoWPAN over 802.15.4 at 2.4 GHz, mesh routing, DTLS security, commissioning model | Thread Group (Thread cert guide) |
| Wi-SUN FAN | 6LoWPAN over 802.15.4g in sub-GHz bands, FHSS, designed for utility metering and field area networks | Wi-SUN Alliance |
| Zigbee IP | 6LoWPAN-based Zigbee variant, deprecated in favour of Zigbee 3.0 over the original Zigbee stack | Connectivity Standards Alliance, no longer pushed |
| Custom 802.15.4 | Proprietary stack on top of 6LoWPAN, no interop logo | None, radio cert only |
For a product implementing raw 6LoWPAN with no upper-layer ecosystem, the certification path reduces to the underlying radio dossier: FCC Part 15.247 or Part 15.249 for the US, EN 300 328 or EN 300 220 for the EU depending on the chosen band, MIC for Japan. The product cannot claim any interop logo.
Wi-SUN FAN as the main 6LoWPAN production use case in sub-GHz
Section titled “Wi-SUN FAN as the main 6LoWPAN production use case in sub-GHz”The Wi-SUN Alliance maintains the Field Area Network (FAN) specification, published as FAN 1.0 in 2017 and revised in FAN 1.1. Wi-SUN FAN combines:
- IEEE 802.15.4g in sub-GHz bands (typically 863, 870 MHz in the EU, 902, 928 MHz in the US, 920, 928 MHz in Japan),
- a frequency-hopping channel access on the sub-GHz band,
- 6LoWPAN with RFC 6282 compression as the IPv6 adaptation layer,
- RPL or related routing for multi-hop mesh,
- IEEE 802.1X with EAP-TLS for device authentication.
The Wi-SUN Alliance runs the Wi-SUN Certified interop programme, with profile-specific test plans for FAN, JUTA and Home Area Network. Underlying radio cert remains independent (EN 300 220 EU, FCC Part 15.247 US, ARIB STD-T108 JP).
Pitfall: treating 6LoWPAN as a protocol
Section titled “Pitfall: treating 6LoWPAN as a protocol”The most frequent error on 6LoWPAN is to treat it as a self-contained certifiable protocol. There is no test plan one can run against a generic 6LoWPAN implementation that grants a certification mark. The certification path always passes through the upper-layer ecosystem (Thread, Wi-SUN) or through a pure 802.15.4 radio dossier with no interop claim. Documentation that lists 6LoWPAN among the product certifications, without a Thread or Wi-SUN label, is technically incorrect and misleads procurement.
Cross-cutting points
Section titled “Cross-cutting points”Underlying radio cert always applies
Section titled “Underlying radio cert always applies”All four protocols operate in licence-exempt or shared bands, and the underlying radio certification regime remains mandatory regardless of the alliance layer.
| Region | Sub-GHz (KNX-RF, Wi-SUN sub-GHz) | 2.4 GHz (ANT, Thread, 802.15.4) | 1.9 GHz (DECT, DECT 6.0) |
|---|---|---|---|
| EU | EN 300 220 + RED | EN 300 328 + RED | EN 301 406 + RED |
| US | FCC Part 15.247 or 15.249 | FCC Part 15.247 | FCC Part 15.323 |
| JP | ARIB STD-T108 + MIC Giteki | ARIB STD-T66 + MIC Giteki | sJ-DECT + MIC |
The alliance interop label sits on top of the radio cert and never replaces it. A product without the underlying radio cert cannot legally be placed on the market, regardless of how many alliance logos it displays.
What this guide does not cover
Section titled “What this guide does not cover”The following protocols are not in scope here and have dedicated guides on the site.
- Bluetooth LE: see Bluetooth SIG qualification.
- Thread: see Thread Group certification.
- Matter: see Matter certification.
- LoRaWAN, Sigfox, NB-IoT, Cat M1: these are LPWA technologies with their own ecosystem and are covered separately under the LPWAN family.
- UWB: see the UWB FiRa Consortium guide.
Choosing between ANT+, DECT ULE and a Thread or BLE alternative
Section titled “Choosing between ANT+, DECT ULE and a Thread or BLE alternative”When the choice is open at the project start, the principal trade-offs are these.
| Criterion | ANT+ | DECT ULE | Thread (6LoWPAN, 2.4 GHz) | BLE |
|---|---|---|---|---|
| Band congestion | 2.4 GHz, FHSS mitigates | Reserved 1.9 GHz, very low | 2.4 GHz, mesh mitigates | 2.4 GHz, can be congested |
| Indoor range | 5, 30 m typical | 50, 100 m+ | 30, 60 m, extended by mesh | 5, 30 m |
| Battery life | Multi-year coin cell | Multi-year on small alkaline | Multi-year coin cell | Multi-year coin cell |
| Audio support | None | HD voice native | None | LE Audio since BLE 5.2 |
| Smartphone integration | Limited (iOS support partial) | None native, gateway required | Via Matter | Native on all platforms |
| Cert complexity | ANT+ Manage + radio cert | ULE Alliance + DECT cert + radio cert | Thread Group + radio cert | Bluetooth SIG + radio cert |
| Silicon ecosystem | Narrow, Nordic-dominant | Narrow, DSP Group-dominant | Broad and growing | Very broad |
The choice is driven by use case more than by technology preference. Sport sensor reporting to a watch falls naturally to ANT+. Battery security sensor reporting to a residential gateway with HD voice falls naturally to DECT ULE. Mesh of low-power IP-addressable devices in a home falls to Thread. Direct user interaction with a smartphone falls to BLE.
Frequent pitfalls
Section titled “Frequent pitfalls”| Pitfall | Consequence |
|---|---|
| Treating ANT+ Alliance interop as a substitute for FCC, RED or MIC radio cert | Product not legally placeable, ANT+ logo without legal market access |
| Assuming EU DECT ULE hardware will ship in the US | Band gap (1.88, 1.90 vs 1.92, 1.93 GHz), full hardware redesign required |
| Treating 6LoWPAN as a certifiable protocol on its own | No certification path, must pass through Thread, Wi-SUN or pure 802.15.4 radio cert |
| Missing FHSS dwell time declaration on ANT radios in the FCC filing | Grant refusal or post-grant invalidation, project delay |
| Testing KNX-RF against KNX-IP or KNX-TP requirements | Wrong test plan, EN 300 220 sub-GHz coverage missing |
| Antenna swap after radio test on any of the four | Grant or DoC invalidated, re-test required |
| Listing 6LoWPAN among product certifications | Misleading to procurement, no body certifies 6LoWPAN as such |
| Mixing up ULE Alliance certification and DECT Forum certification | One covers the ULE profile, the other the base DECT profile, both may be needed |
| Skipping operator or gateway acceptance for a DECT ULE sensor sold for a residential gateway brand | Sensor not paired by the gateway despite valid radio and ULE cert |
| Reusing an ETSI EN 300 328 test campaign for an FCC Part 15.247 filing without dwell time re-verification | Filing rejected at the TCB review stage |
Going further
Section titled “Going further”- Building automation: KNX, DALI-2 and EnOcean certification: full coverage of KNX-RF and adjacent building protocols
- Bluetooth SIG qualification: the comparison point for BLE-based alternatives to ANT+
- Thread Group certification: the principal upper-layer ecosystem for 6LoWPAN at 2.4 GHz
- Matter certification: the application-layer standard above Thread and Wi-Fi
- RED 2014/53/EU: EU radio framework applicable to all four protocols on the EU market
- FCC: US framework, Part 15.247 for ANT and 802.15.4, Part 15.323 for DECT 6.0
- Glossary: definitions of ANT, ANT+, DECT, DECT ULE, 6LoWPAN, Wi-SUN, FHSS, ULE Alliance
See also
Section titled “See also”- Wi-SUN Alliance: IPv6 mesh sub-GHz certification
- Zigbee + CSA: certification of the 802.15.4 mesh protocol
- Bluetooth SIG qualification, process and product listing
- Wi-Fi Alliance: interoperability + Wi-Fi brand
- Matter certification (CSA): process, DAC and DCL
- Qi, Qi2 wireless charging certification (WPC)
Sources & references
- ETSI EN 300 175, Digital Enhanced Cordless Telecommunications (DECT) base standard , ETSI www.etsi.org/deliver/etsi_en/300100_300199/30017501/
- ETSI TS 102 939, DECT Ultra Low Energy (ULE) , ETSI www.etsi.org/deliver/etsi_ts/102900_102999/10293901/
- ETSI EN 300 444, DECT Cordless Terminal Mobility (CTM) , ETSI www.etsi.org/deliver/etsi_en/300400_300499/300444/
- RFC 4944, Transmission of IPv6 Packets over IEEE 802.15.4 Networks , IETF www.rfc-editor.org/rfc/rfc4944
- RFC 6282, Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks , IETF www.rfc-editor.org/rfc/rfc6282
- RFC 6775, Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks , IETF www.rfc-editor.org/rfc/rfc6775
- Wi-SUN Alliance, Field Area Network (FAN) specification , Wi-SUN Alliance wi-sun.org/specifications/