220 likes | 347 Vues
The third meeting of the IoT Connection Model (IoTCM) was held on March 20, 2014, focusing on key aspects like current progress and implementation, division of tasks, and the evolution of Version 1.0. IoTCM aims to establish standard terms and interfaces for seamless communication in heterogeneous systems. Attendees discussed the status of various projects, including the development of a web platform and the need for translators to interface with existing protocols. Future milestones were outlined, setting the stage for the release of Version 1.0 and community involvement.
E N D
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 about • Things IoTCM Host Thing Things Data Data Methods Methods
What is IoTCM? A “Host” implements the spec. A “Client” consumes it. IoTCM Host IoTCM Client IoTCM Client Things Thing Interfaces Thing Interfaces Network (WiFi, Cellular, etc.) Thing Data
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
Server Sessions POST to create Client-driven response format
What IoTCM Looks Like: JSON User/Role-based Access Session-based Security Client-driven Format
What IoTCM Looks Like: JSON Standard Semantics Standard Units Standard “Thing” Accessibility Standard Data Types
What IoTCM Looks Like: JSON Temporal consistency 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 “Things” Standard Data Types Standard Semantics Accessibility Standard Units
What IoTCM Looks Like: XML Temporal consistency Standard “DataValues” Minimized traffic
Data Input: IoTCM Translators 5.736 mA Temp Sensor Temp Sensor Temp Sensor IoTCM Client IoTCM Client Thing Interfaces Thing Interfaces OPC Tag Point “420” BACnetpresent-value Tag “42.0” IoTCM Host Network (WiFi, Cellular, etc.) Proprietary BACnet OPC Things Motor 42.0 C Standard Outputs
Reference Translator needs • MTConnect • OPC (DA and UA) • BACnet • MQTT • J1939 (CAN) • Modbus • SNMP • Others?
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
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
Questions, Feedback, Volunteers ctacke@opennetcf.com (240) 293-4633 Coming Soon: http://www.iotcm.org