ecosystem specifications and framework
play

Ecosystem, Specifications and Framework March, 2016 OIC Presenters: - PowerPoint PPT Presentation

Open Internet Consortium (OIC) Ecosystem, Specifications and Framework March, 2016 OIC Presenters: Ravi Subramaniam Standard Working Group Open Interconnect Consortium Open Interconnect Consortium, Inc. Table of Contents Internet of


  1. Open Internet Consortium (OIC) – Ecosystem, Specifications and Framework March, 2016 OIC Presenters: Ravi Subramaniam Standard Working Group Open Interconnect Consortium Open Interconnect Consortium, Inc.

  2. Table of Contents • Internet of Things Standard Consideration • Introduction of Open Interconnect Consortium - Overview - Core Framework - Security - Remote Access - Smart Home Profile 2

  3. Technical Principles for an Internet of Things Ecosystem Open Interconnect Consortium, Inc.

  4. Scope of IoT Controller OIC Scope OIC Scope (anticipated) (current) Controller App Cloud Interface Cloud Servers Cloud Servers service #2 service #1 domain domain Things Controller Controller Local Control Remote Control Server to Server 4

  5. Approaches for defining and interacting with Things OIC Scope • Imperative : By defining functions • Declarative : By defining things as resources and its properties of and operations on things SetSwitch BinarySwitch - Power(in) - true(on), false(off) Resources Dimming SetDimmingLevel Functions - properties - dimmingSetting (int) - Input & Output Parameters - step(in), range(in) - step (int) - range [0-100] Brightness SetBrightness - brightness (int) - brightness (in) e.g., Light bulb - (no Verbs) + Objects - (Verbs + Objects) * Fixed set of verbs (CRUDN) from transport layer - RPC model will be used - Resource model in RESTful Architecture (e.g., W3C, CSEP, etc.) 5

  6. Additional Considerations* • Late Binding (Reliability, Resilience, Conformance) • Multi-Protocol • Peer – Peer (Gateway and Cloud are not first class citizens but peers) • Framework as middleware • what defines the ecosystem (is it only spec?) • Need consistent behavior • Adaptability • Optimization (e.g. sensors, connectivity) OIC Member Confidential Information 5/22/2016 6

  7. Support of Multiple Verticals • Legacy vertical services usually designed as silos Home Health Domain  No common way to communicate among them OIC Scope Insulin level low! … Need Help! Health Home Industrial … Health Home Industrial Discovery Common Platform Addressing Messaging Security Health Home Industrial … • A common platform provides a foundation for vertical services to collaborate and interwork Smart Home Domain by providing common services and data models 8

  8. Interoperability • Full interoperability from the connectivity layer up to the service layer is the only way to truly guarantee a satisfactory UX • Interoperability at the Connectivity and/or Platform layer only provides partial interoperability which can ultimately lead to fragmentation ② Platform Level ③ Service Level ① Connectivity Level Interoperability Interoperability Interoperability Vertical Vertical Vertical Vertical Vertical Vertical Services Services Services Services Services Services Platform Platform Platform Platform Platform Platform Connectivity Connectivity Connectivity Connectivity Connectivity Connectivity OIC Scope 9

  9. Interoperability & Certification • Conformance test - Each device proves conformance to specifications • Interoperability test - Each device proves interoperability with other devices OIC Scope Conformance Test Certificate Issue CERTIFIED & Logo Licensing Interoperability Device under Test Test Prerequisites: Dependency Certification (e.g. Connectivity) • Certification Scope Tested Optional Tested Mandatory Optional Optional Open Optional Open Spec (in spec, cert & committed Source Spec Source Features in Open Source Project) Features Features Features Open Source Specification 10

  10. Licensing OIC Scope For IPR Policy : e.g. RAND-Z, RAND, etc… • For Open Source : e.g. Apache2, Internet Software Consortium (ISC), etc… • Due to the common nature of IoT connecting everything over the Internet, it’s • most critical for manufacturers to avoid a licensing risk - Everything connected could be at potential risk Offering manufacturer-friendly Licensing and IPR Policy enables growth of • market by attracting both start-ups and large enterprises; such an IPR policy must be clear and readily understandable ensuring that the terms are offered by all IP holders. 11

  11. Introduction of Open Interconnect Consortium Open Interconnect Consortium, Inc.

  12. Growing Membership Diamond Platinum Gold 13

  13. OIC Organizational Structure Board of Directors IoTivity Standard Open Source Project Specification & Certification Steering Group Open Source Coordination Membership Sponsored (funded) by OIC Technology Develops reference implementation Planning of OIC standard Ecosystem Marketing Communications http://www.iotivity.org

  14. OIC Key Concepts • Dedicated and optimized protocols for IoT • Standards and Open Source to allow flexibility creating solutions • Full stack definition for maximum interoperability Connectivity, Platform and Vertical Services defined  License applies to members and affiliates of members  • Certification and Logo program • Free IPR License • Code: Apache 2.0 • Specification: RAND-Z 15

  15. OIC Specification overview Open Interconnect Consortium, Inc.

  16. Specification Structure Infrastructure • Core Framework • Security • Remote Access • Certification Test Plans and Test Cases Resource Model • Resource Specification (Domain agnostic) Per Application Vertical • Device Specification • Vertical Specific Resource Specification 17

  17. Core Framework Specification Overview Open Interconnect Consortium, Inc.

  18. Objectives • Core Framework Specification Scope • Specifies the technical specification(s) comprising of the core architectural framework, messaging, interfaces and protocols based on approved use-case scenarios • Enables the development of vertical profiles (e.g. Smart Home) on top of the core • Architect a core framework that is scalable from resource constrained devices to resource rich devices • Evaluate technical specification(s) for maximum testability and interoperability • Ensure alignment with OIC open source releases 19

  19. Separation of Concern Data Model “Logical” Information Model Mapping (Static & Dynamic) “Physical” Connectivity Model

  20. OIC Conceptual Architecture OIC Roles Information Model • Resource oriented • RESTful architecture • OIC OIC RESTful Semantics • Server Resource Client Physical abstraction • Model Layer Data Model • Entity OIC For vertical and device • (sensor / Resource actuator Data connectivity abstraction • interface) Protocol and layer agnostic OIC OIC • Device Device Dynamic and late binding • OIC Abstraction Implem- Interfaces entation Specific Connectivity Connectivity Protocol Layer 5/22/2016 21

  21. Organization of an OIC Device • OIC Device – abstraction on a platform to host resources and execute roles Resource URI: /oic/p rt: oic.wk.p if: oic.if.r /oic/p n: homePlatform policy: bm:11 /oic/res /oic/res pi: at1908 /oic/d /oic/d mnmn: Samsung /oic/ad /oic/mnt OIC Device 1 OIC Device 2 Physical Device e.g. light bulb Mandatory Optional 22

  22. Device example: light device (oic.d.light) • Example overview - Smart light device with i) binary switch & ii) brightness resource • Device type: Light device (oic.d.light) [Defined by the domain] • Associated resources - Core resources: ① oic/res, ② oic/d - Device specific resources: ③ Binary switch (oic.r.switch.binary), - Other optional resources can be exposed, in this example ④ Brightness resource (oic.r.light.brightness) Example: Smart light device with 4 resources Device Device oic/res Associated Resource Type M/O Title Type oic/d oic/res (oic.wk.core) M Binary switch oic/d ( oic.d.light ) M Light oic.d.light Binary switch (oic.r.switch.binary) M Brightness Brightness (oic.r.light.brightness) O 24

  23. Core Framework Specification Key Features Open Interconnect Consortium, Inc.

  24. OIC Spec Features – Core Framework Spec ① Discovery: Common method for device discovery (IETF CoRE) Vertical Industrial ② Messaging: Constrained device support as Smart Home … Profiles Internet default (IETF CoAP) as well as protocol translation via intermediaries OIC Core Framework ③ Common Resource Model: Real world entities defined as data models (resources)\ ⑥ Group Protocol ID & Addressing ④ CRUDN: Simple Request/Response mechanism management Bridge/GW with Create, Retrieve, Update, Delete and Notify commands ③ ④ ⑦ ⑤ Common Device Resource CRUDN Security ⑤ Device Management: Network connection management Model settings and remote monitoring/reset/reboot ① ② functions Discovery Messaging Streaming ⑥ ID & Addressing: OIC IDs and addressing for OIC entities (Devices, Clients, Servers, Resources) ⑦ Security: Basic security for network, access control L2 Connectivity Networking Transport based on resources, key management etc 26

  25. OIC Core Framework Basic Operation Discovery Operation Discovery - Discover access policies, device info and resources on the devices Operation - Get device information by retrieving resources - Control devices by changing resources - Observe change on the properties of resources Basic common capabilities - Device Monitoring - Maintenance (e.g., reboot, factory reset, statistics collection, etc.) Connectivity Networking Transport Security 27

Recommend


More recommend