Enabling the Management of Constrained Devices Using the OIC Framework
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Thursday, 2017-02-23· at 12:10· Broadway I/II·
summary
Apache Mynewt runs an OIC 1.1 (IoTivity-based) application layer over Bluetooth Low Energy 4.2 and IPv6, ported to Nordic nRF51/nRF52 and other MCUs to manage constrained sensors and actuators. Work replaces IoTivity‑constrained memory pools with mynewt em_buf chains, adds zero‑copy buffering and stack CBOR decoding, cuts RAM/text enough to run on 16 KB RAM devices, supports CoAP and CBOR over BLE and yields 32 concurrent connections while enabling OTA updates and OIC-based logging.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:35Background
- 8:17Why OIC
- 16:02Logical Operations
- 18:12Resource Discovery
- 20:32Operations on Resources
- 21:22Reference Implementations
- 23:05Implementation Overview
- 23:48Implementation Challenges
- 31:20Optimizations
- 32:42What next
- 40:01Bluetooth
- 41:02Interoperability
related talks
42mApache Mynewt Overview
32mApache Mynewt - connected RTOS - project overview
54mOCF for Resource-Constrained Environments
52mIoTivity: The Open Connectivity Foundation and the IoT Challenge
01h 02m.NET on tiny IOT Meadow Boards.
46mFunctional IoT with Elixir and Nerves
15mLighweightM2M and its ecosystem
15mDecentralising the IOT for Smarter Cities and Businesses