This page (revision-10) was last changed on 29-Nov-2024 16:16 by Administrator

This page was created on 29-Nov-2024 16:16 by -jim

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
10 29-Nov-2024 16:16 2 KB Administrator to previous
9 29-Nov-2024 16:16 2 KB -jim to previous | to last
8 29-Nov-2024 16:16 2 KB -jim to previous | to last
7 29-Nov-2024 16:16 2 KB -jim to previous | to last
6 29-Nov-2024 16:16 2 KB -jim to previous | to last
5 29-Nov-2024 16:16 1 KB -jim to previous | to last
4 29-Nov-2024 16:16 1 KB -jim to previous | to last
3 29-Nov-2024 16:16 826 bytes -jim to previous | to last
2 29-Nov-2024 16:16 808 bytes -jim to previous | to last
1 29-Nov-2024 16:16 176 bytes -jim to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 2 changed one line
[{$pagename}] is an [IPv6]-based, [Low-Power Wide Area Network] [Mesh Network] technology for [Internet of Things] ([IoT]) products.[{$pagename}] uses [6LoWPAN], which, in turn, uses the [IEEE 802.15.4] [wireless] [protocol] with [Mesh Network] [communication], as does [Zigbee] and other systems. [{$pagename}] is different in that it is [IP]-addressable, with [cloud] access and [AES] [encryption].
[{$pagename}] is an [IPv6]-based, [Low-Power Wide Area Network] [Mesh Network] technology for [Internet of Things] ([IoT]) products.
At line 4 removed one line
A [BSD]-licensed [Open Source] [implementation] of [{$pagename}], called "[OpenThread]", has been released by [Google]
At line 6 changed one line
[{$pagename}] (or really [6LoWPAN]) is based on the use of a connecting [router], called an edge [router]. [{$pagename}] calls their edge routers Border [Routers]. Unlike other proprietary networks, [6LoWPAN], like any network with edge routers, does not maintain any [Application Layer] [state], because such networks forward [datagrams] at the [Network Layer]. This means that [6LoWPAN] remains unaware of [Application Layer] [protocols] and changes. This lowers the processing [power] burden on edge [routers]. It also means that Thread does not need to maintain an [Application Layer].
[{$pagename}] uses [6LoWPAN], which, in turn, uses the [IEEE 802.15.4] [wireless] [protocol] with [Mesh Network] [communication], as does [Zigbee] and other systems. [{$pagename}] is different in that it is IP-addressable, with [cloud] access and [AES] [encryption]. A [BSD]-licensed [Open Source] [implementation] of [{$pagename}], called "[OpenThread]", has been released by [Google]
At line 8 changed 12 lines
[{$pagename}] states that multiple [Application Layers] can be supported, as long as they are low-bandwidth and are able to operate over [IPv6]
[{$pagename}] is one of the [Network Layers] supported by [Matter Standard][{$pagename}] Radio layer it uses IEEE 802.15.4 [MAC] which is the same radio that [Zigbee] uses.
[{$pagename}] uses the IEEE 802.15.4 [PHY|Physical Layer] which is [6LoWPAN]
!! [{$pagename}] Scalability
[{$pagename}] supports a [Mesh Network] and supports up to:
* 32 [Routers] per network
* 511 [End nodes] per [Router]
* [Routers] perform a dynamic shortest path any to any routing [Protocol]. Similar to [Routing Information Protocol]
* Supports multiple [Border] [Routers][{$pagename}] [Devices] [MUST] use security [AES-128]. [{$pagename}] solves the secure device commissioning problem in a very user-friendly way. Via [Mobile Device] they can discover [{$pagename}] border [routers] on their network using [NDNS]. Then establish a [Secure connection] with that border [router], and then go over with their mobile device and scan the QR code of the device that they want to join, and obtain a short pairing code. The mobile device then establishes a secure [DTLS] session to [authenticate] the joining [device]!! More Information
!! More Information