OpenThread: Bringing the Internet to low-power IoT devices (Google I/O '18)

[@movax20h]

Finally. IoT architecture that make sense. Good to see some good in engineering and industry wide support.

[@kranthisai]

awesome demo.. Looking forward to work on it ASAP..

[@brandonlamontcooper8141]

thanks for all your tips, tricks and wisdom

[@BooBar2521]

Amazing, will definitely try this out

[@cheshire147]

im about as excited to see this a googleFI

[@RaviPujar]

What's the longest distance we can achieve using Thread, considering streetlight type devices placed along a long street of few kilometers. Long distance support?

[@mrhusi]

This depends on the physical layer, Thread is on a higher-level. I guess you could use any kind of physical layer.

[@RaviPujar]

@@mrhusi I am talking about using Bluetooth 5

[@yunushkin88]

and what's the disadvantage of zigbee or z-wave? why another protocol if and so all smart houses are built on mesh networks. I certainly like to openthread and even try to make a network, but what is his future?

[@jonathanhui3322]

Zigbee and Z-Wave do not support IPv6 and, as a result, do not support direct end-to-end connectivity with devices outside their local network. WIth IPv6, you can build a single application that communicates securely, end-to-end across multiple link technologies (Wi-Fi, Cellular, and Thread) without stateful application gateways in between. The video has a couple slides on this aspect.

[@movax20h]

Awesome demo Vaas!

[@antonalm7689]

Great talk!

[@akashmishra2940]

great

[@petkish]

How routing is done for devices which move around in the house? Like a smart dog collar?

[@jonathanhui3322]

Something like a smart dog collar would most likely operate as a battery-powered end device in the Thread network. Thread end devices are responsible for connecting to a neighboring Thread router. The Thread routers are responsible for discovering which router a given end device is attached to. The Thread routing protocol maintains the shortest path between all routers.

[@shivamgupta549]

@@jonathanhui3322 For routing do you guys use RPL IPv6 Routing Protocol for Low power and Lossy Networks?

[@jonathanhui3322]

@@shivamgupta549 Thread does not implement RPL for IPv6 routing.

[@shivamgupta549]

@@jonathanhui3322 Thanks for your reply! It means alot. I was going through the thread specification, what I understood you are using MPL( RFC 7731) & Trickle Algorithm (RFC 6206) for multicast packets. for unicast you are using simple distance vector routing protocol, which seems like a simplified version/implementation of RPL (RFC6550). can you tell me brief what are the difference/benefits between Thread routing protocol and RPL? it helps me to understand more about OpenThread. Thanks for your valuable time.

[@jonathanhui3322]

@@shivamgupta549 Thread uses an any-to-any distance-vector routing protocol that is closer to RIP(ng) but takes advantage of the way Thread addresses nodes to compress the routing table information to reduce both memory and communication overhead.

[@mohmedaminpatel4427]

How is Thread different than 6lowPan other than its integration capabilities ?

[@jonathanhui3322]

6LoWPAN defines how to transport IPv6 datagrams in IEEE 802.15.4 frames. Thread builds upon 6LoWPAN to define a complete IPv6-based mesh network and includes link security, device commissioning, mesh routing, network configuration, sleepy end device operation, and more.

[@yaghiyahbrenner8902]

thanks for this answer, I had the same question.

[@seshansesha7645]

Nice...👍

[@33jaha]

Will this technology be suitable in outdoor?

[@jonathanhui3322]

Thread is a wireless communication technology. You can certainly use Thread to connect devices in outdoor applications.

[@movax20h]

Well, what about mobility? i.e. A sensor on a bike, that communicate with other bikes, or when it arrives at my home, or home of my friend, connects and communicate over Internet with some service recording my bike runs. Wireless static, is not the same as mobile wireless.

[@jonathanhui3322]

Thread typically assumes a relatively static infrastructure, much like Wi-Fi. At the same time, Thread can support device applications that involve intermittent connectivity due to the device entering/leaving the network, again much like Wi-Fi.

[@warrenhuang9692]

Does Google Home support Thread?

[@jonathanhui3322]

Google Home does not include an IEEE 802.15.4 radio that is necessary to support Thread.

[@AbduAhmed-hi6bw]

Good demo...can i get your email as i want test thread devices as part of my research

[@muhammadsiddiqui2244]

Periodic Better Parent Search......LOL.......this option is really powerful but not available to us humans

[@mkvhoqnuncdotfwqumbm845]

text