42

KNoT Manifesto

Embed Size (px)

Citation preview

Page 1: KNoT Manifesto
Page 2: KNoT Manifesto

What is the Internet of Things?

Embed connectivity and share data across mutiple

devices, to add more value.

connectivity to the things

Page 3: KNoT Manifesto

Why every one is looking at IoT?

Values

Page 4: KNoT Manifesto

Why our home devices are still not connected to the internet?

Every "thing" has its specific connectivity needs:

● communication range● baud rate● power consumption● cost

Page 5: KNoT Manifesto

Why our home devices are still not connected to the internet?

…and this leads to many protocols:

● physical layer● data link and network layer● transport layer

Page 6: KNoT Manifesto

There is no standard yet

“It is very difficult to have a unique standard for IoT as we have for the WWW, with HTML and browsers. The THINGS in IoT are so different and the applications as diverse that many standards and protocols will coexist.”

Page 7: KNoT Manifesto

It generates a problem

Complexity

Page 8: KNoT Manifesto
Page 9: KNoT Manifesto

How to mitigate this complexity?

Software platforms

Cloud services to exchange data across devices

Page 10: KNoT Manifesto

How to mitigate this complexity?

Hardware platforms

Wireless microcontrollers + sensors to develop your

application

Page 11: KNoT Manifesto

Applications have its own protocols…

…and they didn't talk to each other.

Page 12: KNoT Manifesto

What are we doing?

Page 13: KNoT Manifesto
Page 14: KNoT Manifesto

We are not creating one more IoT platform!

Page 15: KNoT Manifesto

meta plataform for IoT bridging the gap between existing platforms

made on top of them

Page 16: KNoT Manifesto

IoT platforms

software

hardware

Page 17: KNoT Manifesto

IoT platforms

software

hardware

Page 18: KNoT Manifesto

IoT platforms

software

hardware

Page 19: KNoT Manifesto

IoT platforms

software

hardware

Page 20: KNoT Manifesto

open source, hardware and software.

Page 21: KNoT Manifesto

multi protocol for the physical (multi radios), data link, network and

transport layers To address all communication needs.

Page 22: KNoT Manifesto

end to end from the device to the app, crossing radios, gateways

and cloud services.

Page 23: KNoT Manifesto

data sharing by space and time “to share the data only on monday, from 2pm to 3pm.”

Page 24: KNoT Manifesto

semantic data model applications will know the data type of each other.

Page 25: KNoT Manifesto

distributed cloud a distributed system can handle billions of devices.

Page 26: KNoT Manifesto

low cost the maximum cost of sheapest device will be $5.

Page 27: KNoT Manifesto

easy to use the developer only needs to implement 3 functions to

have his device connected.

Page 28: KNoT Manifesto

architecture 1.0

Page 29: KNoT Manifesto

Components - KNoT Thing

protocol state machine protocol messages

hardware interface and abstraction

manages sensors and actuators

multiple hardware configurations for µC, power and radio

Page 30: KNoT Manifesto

Components - HAL details

PHY Layer

Link/NET Layer

Transport Layer

NRF24L01

PHY Layer

Link/NET Layer

Transport Layer

LoRa

PHY Layer

Link/NET Layer

Transport Layer

WiFi

Comm Interface

Page 31: KNoT Manifesto

SW

Components - KNoT Gateway

buildroot based linux distribution

hardware interface and abstraction.

manages devices from one radio.one daemon for each radio interface.

connects to all radio daemons and creates a bridge to the fog

cloud instance deployed on gateway

web app for gateway setup and config

Page 32: KNoT Manifesto

Components - KNoT Cloud

planning to integrate with ConASys

non-relational database

currently supporting meshblu. planning to integrate with fiware, AWS IoT and raptorbox.

Page 33: KNoT Manifesto

Components - KNoT Lib

library that abstracts the cloud services and is used to develop applications. currently implemented for Android. iOS and Javascript libraries are in the roadmap.

Page 34: KNoT Manifesto

Hardware - starter kit

Page 35: KNoT Manifesto

Hardware - dev board

Page 36: KNoT Manifesto

Why are we doing it?

Page 37: KNoT Manifesto

Construction of applied knowledge

The group's researches turns into experiments in observatories, enabling CESAR to apply the knowledge acquired in IoT projects.

Page 38: KNoT Manifesto

Integrate many platforms into a unique one

It allows interoperability across platforms and across data from many devices.

Page 39: KNoT Manifesto

More agility in developing IoT projects

A KNoT Lamp can be simple like this:

1. Get a KNoT device core schematic and customize it by adding a lamp actuator.

2. Write 3 functions on KNoT μOS that define your lamp behavior.

3. Write a mobile app using KNoT lib to interact with the lamp.

Page 40: KNoT Manifesto

Road Map

Page 41: KNoT Manifesto

Road Map

KNoT V 1.0 ● PAN device ● RPi PAN Gateway ● Meshblu

KNoT V 1.1 ● LPWAN device ● LPWAN Gateway Upgrade

KNoT V 1.4 ● SubGHz device ● SubGHz Gateway Upgrade ● Google Home support

KNoT V 2.0 ● WiFi device ● BLE device ● $5 ARM Gateway ● FiWare

KNoT V 1.2 ● 3G device

KNoT V 1.3 ● Mesh (802.15.4) device ● Mesh Gateway Upgrade ● HomeKit support

Page 42: KNoT Manifesto