Open IoT Cloud Architecture, Web of Things, Shenzhen, China.

1. Open IoT Cloud

2. Mokoversity Jollen Chen, 2015.04.11, Shenzhen <jollen@jollen.org> ! www.mokoversity.com Mokoversity Open IoT Cloud 设计思想

3. IoT 三件⼤大事 IoT 进⼊入与Web 融合的新阶段－Web of Things。 Google 为WoT 时代推出Physical Web 计画，ARM 也推出ARM mbed ⽣生态体系。 Big players 都在推展⾃自已的WoT ⽣生态与IoT Cloud 架构。

4. 1 Going Web

5. 2 Open IoT Cloud Architecture IoT CloudIoT Device Mobile

6. 3 Physical Object http://wot.city/1/00886956590989/kitchen/sensor/dust/a ws://wot.city/object/00886956590989/kitchen/sensor/dust/a coap://wot.city/00886956590989/kitchen/sensor/dust/a

7. REST Object Physical Web GET /1/00886956590989/kitchen/sensor/dust/a

8. REST Object Physical Web GET /1/00886956590989/kitchen/sensor/dust/a

9. Web Web of Things 使用情境

10. IoT Device Mobile HTTP 1.1/2.0HTTP 1.1/2.0 Light-weight Web server Web Frontend Physical Object HTTP 使用情境 http://wot.city/1/jollenchen/sensor/dust/a

11. IoT Device Mobile HTTP 1.1/2.0 Streaming Data Physical Object Web Frontend Physical Object Websocket 使用情境 Real-Time Data Broker ws://wot.city/object/jollenchen/sensor/dust/a

12. IoT App In the form of URLs.

13. Smart Object IoT Node GET /1/00886956590989/kitchen/sensor/dust/a

14. HTTP Websocket CoAP http:// ws:// coap://

15. Websocket HTTP 1.1/2.0 CoAP IoT Cloud IoT Device IoT Device IoT Device IoT Device Mobile & Client IoT Proxy Open IoT Cloud Architecture www.mokoversity.com

16. Privacy Security Personal 隐私性安全性个⼈人性⾃自有云 TLS / SSL ⾃自有云

17. Privacy 制造商收集你的个⼈人资讯，加⼯工后⽤用于商业⾏行为

18. 集中化现有的IoT ⽣生态，所收集的资料健康照护或个⼈人⽣生理监测数据，都朝向「集中化储存」的发展趋势。然⽽而，以个⼈人⽣生理资料来说，我们都是⽆无偿对这些「云服务」公司提供宝贵资料，这些公司对资料进⾏行分析与价值挖掘后，所取得的商业利益，是否能有⼀一个机制，能分享与回馈给提供「素材」的我们

19. Free 将数据储存到⾮非开放的IoT 云服务，是否能「取回」⾃自已的资料，会是⼀一个问题。储存在真正开放的IoT 云，才能解决这样的问题。开放式IoT 架构的意义，必须是⾃自由的：Personal Things

20. Libre Software Gives users the freedom to run the software for any purpose as well as to study, modify, and distribute the original software and the adapted versions. (—wikipedia)

21. Libre IoT Cloud Gives users the freedom to ___ the personal data for any purpose as well as to ___, ___, and ___ the original data and the ______ versions. (—WoT.City)

22. Websocket HTTP 1.1/2.0 CoAP Personal Things OSHW IoT OSHW IoT OSHW IoT OSHW IoT Mobile & Client IoT Proxy Open & Libre IoT Cloud Architecture www.mokoversity.com Open Standards

23. WoT.City IoT Cloud Architecture Open IoT Cloud Open Standards Personal Things Free & Libre Things Open Hardware Web IoT Cloud Framework Hacker x Maker

24. OSHW 「物联⺴⽹网装置终将免费」。在IoT Open Architecture 的理想中，消费者可以免费取得硬件。这个理想并⾮非不可⾏行，第⼀一个步骤，就是设法降低取得硬件的成本。⾃自造硬体（成为IoT 的创客），就是重要的起步

25. IoT Smart Phone Open Source CultureOpen Hardware Maker Culture Free & App Economic Free and Libre Education&Training

27. Web of Things

28. Web-technolog Matrix HTML5/ CSS/JS REST SPA WebSocket CORS Frontend Patterns Web Pages V Web App V V SPA V V V (Backbone) Web Service V V (Server) V IoT / WoT V V V (Client) V (jQuery、Module、 Closure)

29. IoT vs WoT IoT WoT 連結⽅方式 Bluetooth HTTP 數據管理 Centerlized Decenterlized Things Objects RESTful Objects 應⽤用開發模式 Native Web (SPA) 硬件概念 Sensor Device Physical Web (Sensor Fusion) Figure: Thinking in WoT. Copyright (C) 2014 Mokoversity Inc.

30. Connectivity IoT WoT Connectivity Machine to Machine LWM2M Machine to Web Networking TCP / UDP HTTP / REST / CoAP Things Sensor Device RESTful Objects Data Streaming Data Time-Series Data Discover MQTT Publish / Subscribe Figure: Thinking in WoT. Copyright (C) 2015 Mokoversity Inc.

31. Source: http://coap.technology REST model for small devices ! Like HTTP, CoAP is based on the wildly successful REST model: Servers make resources available under a URL, and clients access these resources using methods such as GET, PUT, POST, and DELETE.

32. Source: http://coap.technology Made for billions of nodes ! The Internet of Things will need billions of nodes, many of which will need to be inexpensive. CoAP has been designed to work on microcontrollers with as low as 10 KiB of RAM and 100 KiB of code space (RFC 7228).

33. Source: http://coap.technology Existing skills transfer ! From a developer point of view, CoAP feels very much like HTTP. Obtaining a value from a sensor is not much different from obtaining a value from a Web API.

34. Source: http://coap.technology Ready for integration ! Since HTTP and CoAP share the REST model, they can easily be connected using application- agnostic cross-protocol proxies. A Web client may not even notice that it just accessed a sensor resource! ARM IoT Tutorial https://www.youtube.com/watch?v=4bSr5x5gKvA

35. Websocket HTTP 1.1/2.0 CoAP CoAP www.mokoversity.com IoT Cloud IoT Device IoT Device IoT Proxy 1 2 IoT Device 2 3 Mobile & Client The Web of Things Protocol 3

36. From HTTP to CoAP HTTP The Web protocol. ! CoAP The Web of Things Protocol. ! MQTT The TCP Protocol. IoT Device IoT Device IoT Proxy 1 2 IoT Device 2 3 Constrained Environment 3

37. RESTful UDP M2M Wireless Sensor Network HTTP in Uniform way Simple Cache IoT Device IoT Device IoT Proxy 1 2 IoT Device 2 3 Constrained Environment 3 Features of CoAP

38. W o T. C i t y

39. 打造放的 WoT 源方案 WoT.City Mokoversity 提倡放的 WoT 创业思想

40. MakerWoT Open  Hardware Mokoversity x Seeed x Openmbed

41. mbed REST Object OS

42. ARM mbed

43. Source: http://mbed.org/technology/os/ mbed OS mbed™ OS is an operating system for IoT devices and is especially well-suited to run in energy constrained environments.

44. mbed Tools Digital Interface Networking HTTPD & REST API Websocket HTTP Websocket CoAP Collect and Assemble Manage and Analysis

45. Frontend Composition Layer

46. API Driven Development API Business Logic Data Access Layer ! and Databases Security Logging “server-side implementations are becoming a thin layer with an API for data and security” (-Shiju Varghese) “modern Web developers are writing their server- side code for both Mobile apps and Web apps” (- Shiju Varghese)

47. AutomationJS Web Frontend Boundary Compositor -! update DOM subtree Data Compositor -! integrate the services and data AutomationJS Composition Layer - programmable widgets ! Physical Mashup ! Building Blocks Pattern ! (…)

48. IoT Device Mobile HTTP 1.1/2.0 Streaming Data Physical Object Web Frontend Physical Object Websocket 使用情境 Real-Time Data Broker ws://wot.city/object/jollenchen/sensor/dust/a

49. WoT.City IoT Cloud Device Registration ! Device Container ! Websocket Broker (Channel) ! CoAP Broker (Channel) ! Data Compositor

50. ARM mbed IoT Devices ! Maker Kit ! In-place small data analytics WoT.City IoT Device

51. IoT Application Layer Framework ! AutomationJS WoT.City Mobile and Client

52. Jollen WeChat ID: jollentw <jollen@jollen.org> Thanks Mokoversity Openmbed

Open IoT Cloud Architecture, Web of Things, Shenzhen, China.

You are reading a preview.

Check these out next

Open IoT Cloud Architecture, Web of Things, Shenzhen, China.

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Similar to Open IoT Cloud Architecture, Web of Things, Shenzhen, China. (20)

More from Jollen Chen (18)

Recently uploaded (20)

Open IoT Cloud Architecture, Web of Things, Shenzhen, China.