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

День тому

Thread is a secure, reliable, IPv6-based mesh networking protocol designed for connecting battery-powered devices. OpenThread released by Nest is an open-source implementation of Thread, making the same technology used in Nest products more broadly available to developers. OpenThread supports a variety of chipsets and product platforms such as Android Things, Linux, and RTOS. This talk will provide a brief overview of Thread and how developers can quickly build IoT solutions using OpenThread.
Rate this session by signing-in on the I/O website here → goo.gl/qS1xyt
Visit the website → openthread.io/
OpenThread Github → goo.gl/mXFBd8
Simulating a Thread network using OpenThread codelab → goo.gl/vrn8ay
OpenThread Hardware codelab → goo.gl/npEBc1
Watch more IoT sessions from I/O '18 here → goo.gl/xfowJ8
See all the sessions from Google I/O '18 here → goo.gl/q1Tr8x
Subscribe to the Google Developers channel → goo.gl/mQyv5L
#io18 event: Google I/O 2018; re_ty: Publish; fullname: Jonathan Hui, Vaas Krishnamurthy; event: Google I/O 2018;

КОМЕНТАРІ: 32

@movax20h 5 років тому

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

@kranthisai 5 років тому

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

@movax20h 5 років тому

Awesome demo Vaas!

@gabrielgraf2521 Рік тому

Amazing, will definitely try this out

@antonalm7689 5 років тому

Great talk!

@brandonlamontcooper8141 Рік тому

thanks for all your tips, tricks and wisdom

@seshansesha7645 4 роки тому

Nice...👍

@cheshire147 2 роки тому

im about as excited to see this a googleFI

@RaviPujar 4 роки тому

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 4 роки тому

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

@RaviPujar 4 роки тому

@@mrhusi I am talking about using Bluetooth 5

@yunushkin88 5 років тому

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 5 років тому

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.

@petkish 5 років тому

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

@jonathanhui3322 5 років тому

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 5 років тому

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

@jonathanhui3322 5 років тому

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 5 років тому

thanks for this answer, I had the same question.

@33jaha 6 років тому

Will this technology be suitable in outdoor?

@jonathanhui3322 6 років тому

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

@movax20h 5 років тому

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 5 років тому

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.