Sensors to Servers Meeting #3: March 20, 2014 IoTCM: IoT Connection Model.
22
Sensors to Servers Meeting #3: March 20, 2014 IoTCM: IoT Connection Model
-
Upload
thomasine-rogers -
Category
Documents
-
view
214 -
download
0
Transcript of Sensors to Servers Meeting #3: March 20, 2014 IoTCM: IoT Connection Model.
Sensors to Servers
Meeting #3: March 20, 2014
IoTCM: IoT Connection Model
Meeting Goals
• Quick review of IoTCM• Current Progress• Current Implementation• Translators• Progress So Far• Division of Tasks• The Evolution of Version 1.0• “The Plan” (schedule and
milestones)
The Mission Has Not Changed• To provide a recommended set of
standard terms and interfaces to allow nodes in heterogeneous systems to communicate at a basic level while leaving implementers free to extend and add value in any way they choose.
What is IoTCM?
It’s all aboutThings
IoTCM Host
Thing
Data
Methods
Things
Data
Methods
What is IoTCM?
IoTCM Host
Things
IoTCM Client
ThingInterfaces
IoTCM Client
ThingInterfaces
Netw
ork (WiFi, C
ellular, etc.)
Thing Data
A “Host” implements the spec.
A “Client” consumes it.
Current Progress
• Web Site up at www.IoTCM.org• Wordpress-based• Blog• Forums
• Codeplex Project online at iotcm.codeplex.com• Source code• Issue tracker• Implementation Matrix
Host Implementation Details
Server Sessions
POST to create
Client-driven responseformat
What IoTCM Looks Like: JSON
User/Role-based Access
Session-based
Security
Client-driven Format
What IoTCM Looks Like: JSON
Standard Semantics
Standard Units
Accessibility
Standard Data Types
Standard “Thing”
What IoTCM Looks Like: JSON
Temporal consistenc
y
Minimized traffic
Standard “DataValues
”
What IoTCM Looks Like: XML
User/Role-based Access
Session-based
Security
Client-driven Format
What IoTCM Looks Like: XML
Standard Semantics
Standard Units
Accessibility
Standard Data Types
Standard “Things”
What IoTCM Looks Like: XML
Temporal consistenc
y
Minimized traffic
Standard “DataValues
”
Other protocols to IoTCM:
Translators
Data Input: IoTCM Translators
IoTCM Client
ThingInterfaces
IoTCM Client
ThingInterfaces
Netw
ork (WiFi, C
ellular, etc.)
Temp Senso
r
Temp Senso
r Temp Senso
r
BACnet present-value Tag “42.0”
5.736 mA
OPC Tag Point “420”
Motor42.0 C
IoTCM Host
Things
Sta
ndard
Outp
uts
BAC
net
OPC
Prop
riet
ary
Reference Translator needs
• MTConnect• OPC (DA and UA)• BACnet• MQTT• J1939 (CAN)• Modbus• SNMP• Others?
Summary
What will be in v 1.0?
Specification of Components• Things• Data• Functions
Data Access over IP• REST interface
definitions• XML and JSON• (Maybe proto-buf?)
Discovery • Details to be worked
out – need volunteers
History• Look to v 2.0
Thing Library• Definitions of common
Things
SDKs and Reference Implementations• C# Host and Client• Translators
What will be in v 1.0?
The Plan
Completed:• Begin Spec Document • Begin SDK and Reference Host Implementation• IoTCM.org domain and web site• Iotcm.codeplex.com project portal
Next 4 weeks• Start the Thing Library• Implement Reference Host and Client• Get others involved
April-May 2014• Find implementers and early adopters
June 2014• Publish 0.9 and solicit feedback
August 2014• Publish 1.0
![Eclipse IoT stack with Java and the End-to-end IoT solutions...End-to-end IoT? Actuators/Sensors + Gateway + [ Cloud ] + User front-end 1. Sensors/Actuators Sense the physical environment](https://static.fdocuments.us/doc/165x107/5f9f73d4a6911045bd00df1b/eclipse-iot-stack-with-java-and-the-end-to-end-iot-solutions-end-to-end-iot.jpg)
