IoTivity-Constrained: IoT for Tiny Devices
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Wednesday, 2017-02-22· at 14:00· Broadway I/II·
summary
IoTivity-Constrained implements OCF on severely limited hardware: a compact CoAP/CBOR stack with DTLS onboarding, tested on Zephyr, RIOT, Contiki and Linux and exercised on an Arduino 101. It uses an event loop, static memory allocation, small configurable pools, and supports block-wise transfers to handle MTU limits; ports implement minimal interfaces for clock, RNG, storage and networking. It targets class‑2 devices comfortably, can fit tuned class‑1 builds, struggles on class‑0, and is near OCF spec compliance with plugfest plans.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 3:12OCF resource modele
- 5:15OCF "well-known" resources
- 5:59OCF protocols
- 7:55GET and PUT requests
- 8:44OBSERVE and Notify
- 9:44Constrained device classes
- 11:51Hardware
- 14:14Software
- 15:51lo Tivity-Constrained features
- 19:34Architectural goals
- 21:04Architecture
- 22:21Core block
- 24:07Event loop execution
- 25:57Idle mode and signaling
- 27:58Platform Abstraction
- 28:23Zephyr adaptation
- 29:56Clock
- 31:11Connectivity events
- 32:43Persistent storage
- 33:33Application structure
- 35:13Background task in application
- 35:44Initialization
- 36:12Defining a resource
- 36:38Resource handler
- 37:42Resource discovery
- 38:58Issuing a request
- 39:35Response handler
- 40:03Framework configuration
- 40:49Project configuration
- 42:13IPv6 over BLE (IPSP) support
- 44:56Summary and plans
related talks
52mIoTivity: The Open Connectivity Foundation and the IoT Challenge
54mOCF for Resource-Constrained Environments
58mSoletta: Closing the IoT Development Gap
38mRTOS vs Bare metal Dawn of Constrained Device
31mRunning Linux on Constrained IOT Device
30mSoftware architecture for High-end IoT devices
30mOffline IoT - Building Resilient Connected Devices without the Internet
50mZephyr Project: An RTOS to Change the Face of IoT