KNoT Manifesto
0 likes•122 views
The document discusses the Internet of Things (IoT), focusing on the challenges of connectivity, diverse protocols, and the absence of a unified standard. It proposes a meta-platform for IoT that bridges existing platforms and enables interoperability among devices using multi-protocol solutions. The goal is to simplify IoT development, allowing efficient integration of various hardware and software components while maintaining low costs and ease of use.
KNoT Manifesto
- 2. What is the Internet of Things? Embed connectivity and share data across mutiple devices, to add more value. connectivity to the things
- 3. Why every one is looking at IoT? Values
- 4. 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
- 5. 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
- 6. 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.”
- 7. It generates a problem Complexity
- 9. How to mitigate this complexity? Software platforms Cloud services to exchange data across devices
- 10. How to mitigate this complexity? Hardware platforms Wireless microcontrollers + sensors to develop your application
- 11. Applications have its own protocols… …and they didn't talk to each other.
- 12. What are we doing?
- 14. We are not creating one more IoT platform!
- 15. meta plataform for IoT bridging the gap between existing platforms made on top of them
- 20. open source, hardware and software.
- 21. multi protocol for the physical (multi radios), data link, network and transport layers To address all communication needs.
- 22. end to end from the device to the app, crossing radios, gateways and cloud services.
- 23. data sharing by space and time “to share the data only on monday, from 2pm to 3pm.”
- 24. semantic data model applications will know the data type of each other.
- 25. distributed cloud a distributed system can handle billions of devices.
- 26. low cost the maximum cost of cheapest device will be $5.
- 27. easy to use the developer only needs to implement 3 functions to have his device connected.
- 28. architecture 1.0
- 29. Components - KNoT Thing protocol state machine protocol messages hardware interface and abstraction manages sensors and actuators multiple hardware configurations for µC, power and radio
- 30. 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
- 31. Components - KNoT Cloud planning to integrate with ConASys non-relational database currently supporting meshblu and FIWARE. planning to integrate with AWS IoT and Google Cloud.
- 32. Components - KNoT Lib library that abstracts the cloud services and is used to develop applications. currently implemented for Android, iOS and Javascript libraries.
- 33. Hardware - Maker Board
- 34. Hardware - Dev Board
- 35. Why are we doing it?
- 36. Construction of applied knowledge The group's researches turns into experiments in observatories, enabling CESAR to apply the knowledge acquired in IoT projects.
- 37. Integrate many platforms into a unique one It allows interoperability across platforms and across data from many devices.
- 38. 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.