演讲：Open IoT Cloud 设计思想。2015 年 4 月 11 日在深圳南山智园。

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

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

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

10. Web
Web of Things
使用情境

11. 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

12. 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

13. IoT App
In the form of URLs.

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

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

16. 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

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

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

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

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

21. 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)

22. 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)

23. 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

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

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

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

27. W o T. C i t y
(C) 2015 Mokoversity Inc. v0.1.0 CONFIDENTIAL.
jollen <jollen@jollen.org>
Mokoversity Inc.

28. Web of Things

29. 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)

30. 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.

31. 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.

33. 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.

34. 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).

35. 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.

36. 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

37. 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

38. 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

39. 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

40. W o T. C i t y

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

42. MakerWoT
Open
Hardware
Mokoversity x Seeed x Openmbed

43. mbed REST Object OS

44. ARM mbed

45. 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.

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

47. Frontend
Composition
Layer

48. 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)

49. 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
!
(…)

50. 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

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

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

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

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