Without App Standards, There's No Internet of Anything
•Download as PPTX, PDF•
1 like•1,085 views
Guy Martin, OIC Head of Digital Marketing, discusses the need for app standards within IoT, and how OIC is structured to begin delivering on a cross-platform common communications layer.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Without App Standards, There's No Internet of Anything
Similar to Without App Standards, There's No Internet of Anything (20)
Recently uploaded
Recently uploaded (20)
Without App Standards, There's No Internet of Anything
- 1. Without App Standards… …There Is No Internet of Anything Guy Martin Senior Strategist/Head of Digital Marketing guym@osg.samsung.com @guyma, @OpenInterConn
- 2. Agenda • IoT Market • IoT Challenges • IoT Standards & Their Importance • IoT Needs by Stakeholder Group • Moving IoT Forward
- 3. Internet of Things – The Market
- 4. Internet of Things… …is at the “Peak of Inflated Expectations” - Gartner “Hype Cycle Report” 2014
- 5. Internet of Things… …will take“5 to 10 years to reach maturity.” - Gartner “Hype Cycle Report” 2014
- 6. Internet of Things… …is not a new concept. (Earliest modern references were in 1990s)
- 7. Internet of Things… …devices getting smart & connected.
- 8. Internet of Things… …an explosion of data and control points.
- 9. Internet of Things… …will affect everything.
- 10. Internet of Things… …is going to be HUGE!
- 11. Internet of Things… …“50B devices by 2020” - Cisco
- 12. Internet of Things… …“$1.7T in products & services by 2020” - IDC
- 13. Internet of Things… …“$300B in products & services by 2020” - Gartner
- 14. How will the services & apps talk to the devices?
- 15. How will developers build the services & apps that talk to the devices?
- 16. Internet of Things Market
- 17. Internet of Things Market • Significant Market Opportunities – Device/Sensor Makers – Consumer Electronics – Software Developers – Infrastructure (Cloud) Providers – Service Providers
- 18. Internet of Things Market • Driving Connected Decisions – Connecting Things is only the first step – Intelligent Decisions/Actions is the key
- 19. Internet of Things – Challenges
- 20. Internet of Things Challenges - INTEROPERABILITY • Different devices/capabilities – Micro (no screen, embedded, etc.) – Mini (wearables) – Standard (mobile devices, tablets, etc.) – Macro (SmartHome collections, Cloud, etc.)
- 21. Internet of Things Challenges - INTEROPERABILITY • Different operating systems • Different network protocols • Different vendors – How do you differentiate products? • Different silos/vertical markets
- 22. Internet of Things Challenges – USER ACCEPTANCE • Security • Data privacy • Different user expectations – Techie/Expert – Average User – Corporate/Enterprise User – Industrial User
- 23. Internet of Things – Standards
- 24. “The nice things about standards… …is you have so many to choose from.” - Dr. Andrew S. Tanenbaum
- 25. Where Standards Fit in IoT Applications Supporting Organizations
- 26. Standards Are Nothing Without Code
- 27. Open Source Code for IoT App Standards • Collaborative Development – Speeds Innovation & Interoperability • Bootstraps Device Makers • Bootstraps App Developers • Provides ‘reality check’ for Standards Organization Source: https://ccistudentcenterblog.files.wordpress.com
- 28. How OIC Works in Standards & Open Source • Specification Development • RAND-Z IP policy • Reference Implementation • Apache 2.0 License OIC Certified Products Hardware & Applications
- 29. IoT Needs by Stakeholder Group
- 30. IoT Standards & Consumers
- 31. Where Standards Fit - CONSUMERS in IoT Applications Supporting Organizations
- 32. What CONSUMERS (Currently) Want in IoT
- 33. What CONSUMERS (Eventually) Want in IoT
- 34. What CONSUMERS Currently Get in IoT
- 35. What CONSUMERS Currently Get in IoT
- 36. IoT Standards & Device Makers
- 37. Where Standards Fit - DEVICE MAKERS in IoT Applications Supporting Organizations
- 38. IoT Cloud Services Reporting & Control Internet Things & Wearables Bridging & Forwarding LE New Modes of Communication = Local Network / Same Subnet (Wi-Fi, Ethernet, etc…) Smart Devices Peer-to-Peer STUN/TURN Scope of IoT Comms App Standards We need a way to make IoT comms as easy for developers and manufacturers as connecting a client to a server in the Cloud. App Standards will address the challenge of IoT comms CloudSmartIoT Client to Cloud Internet
- 39. Compliance Testing & Certification • Mandatory feature: – Defined in the specification, – Released in open source, and – Mandatory in the Interoperability certification program • All other features are optional – Note: some features that are in both the specification and open source may be still be optional Open Source Specification Mandatory (in spec, cert & committed in Open Source Project) Interoperability Certification Optional Open Source Features Tested Optional Open Source Features Tested Optional Spec Features Optional Spec Features
- 40. IoT Standards & Developers
- 41. Where Standards Fit - DEVELOPERS in IoT Applications Supporting Organizations
- 42. Conceptual Framework Framework Profiles Consumer Enterprise Industrial Automotive Education Health Security, Identity & Permissions Discovery Data Transmission Data Management Device Management Transports LE Remote Access Cloud Resource Model
- 43. Resource Model Security, Identity & Permissions Discovery Comms Device Management Transport Abstraction API - Language Mapping Accessing Resources Resource Model Security, Identity & Permissions Discovery Comms Device Management Transport Abstraction LE Entity HandlerAPI - Language Mapping Application Local IP Local IP Resource Shared Transport
- 44. Security, Identity & Permissions Discovery Comms Device Management Transport Abstraction API - Language Mapping Accessing Non-Standard Resources Resource Model Security, Identity & Permissions Discovery Comms Device Management Transport Abstraction LE Protocol Plug-In API - Language Mapping Application Local IP Local IP Shared Transport Resource Model Protocol Plug-In Manager Resource Comms
- 45. Resources and Structures Collection Property Collection Property Resource Property Attribute Attribute Resource Property Attribute Attribute Resource Property Attribute Attribute • On-off state • Brightness • Temperature • Location • Friendly name • Sensor version • Etc… Property • Resource Type • Resource Interface • Discoverability • Resource version • Access Control List • Observable • Etc… Property Property Property Property
- 46. Light Resource Examples Resource Light Status: On/Off Resource Light Status: On/Off Dimming: 0-100 Resource Light Status: On/Off Dimming: 0-100 Hue: RGB Hue: HSL Colour Temp: K
- 47. Grouping Devices Collection Garage Door Opener Resource Door Mechanism Action: Open/Close/Stop Status: Closed/Not-Closed Resource Light Status: On/Off Detailed Status: Open/Opening/ Closing/Closed/Etc… Collection Things in the Garage Resource Light Status: On/Off
- 49. Moving IoT Forward Continue Innovation at Transport Layer • Develop new/better RF/network protocols/standards • Strengthen existing standards • Foster relationships with app standards
- 50. Moving IoT Forward Let Developers Add Value, Not Deal with Plumbing • Standard APIs that allow developers to deliver value • Cross-platform & IoT vertical agnostic layers • Open up a market for ‘Connected Decisions’ apps Automated/Intelligent Decision Device /Data Sensor Sensor
Editor's Notes
- Happening now because of Moore’s Law; cost effective to connect a light blub.
- Not the only question for the Internet of Things…but a big one.
- Not the only question for the Internet of Things…but a big one.
- OIC will align with other groups, including the Industrial Internet Consortium (IIC) that are already working on IoT Cloud Services. Client to Cloud communications is a solved problem. Developers find it easy to set up this sort of communication. They can get a connection to a particular IP address and port without understanding anything about the underlying technologies. More people got PCs, phones and then tablets. Many people have more than one device. There are lots of ways these devices can communicate directly with each other: Bluetooth, Wi-Fi Direct, via a local IP network they are both connected to – often because they are using the same Wi-Fi AP – or via the Internet (using servers to find each other, but with the data flowing directly from one device to another). Any one of these technologies is more complex than the classic client to cloud communication. Add in additional requirements such as security and identity, or actively managing a connection and moving it between available transports to always deliver the best connection, and it becomes a very hard problem. Better for the industry to solve it once, and well. As the cost of compute power and connectivity decreases both are finding their way onto fixed and limited function devices, enabling the Internet of Things (IoT). Similar issues of communications complexity exist in this area, along with a need for service-level normalisation to deliver the envisioned interoperability. Things and wearables need to communicate with each other, and also with smarter devices. Data needs to be shared widely across a mesh of communications. Once on a smart device the data can be shared with other smart devices, bridging across different transports via the peer-to-peer connectivity already discussed, or to Cloud servers via traditional client to Cloud comms. This is a “bottoms-up” type communication that is a high priority for consumer IoT applications, but will also have value in other verticals. Another related mode of communication is a big focus for the Industrial vertical: IoT Cloud Services. This mode of communication is more concerned with “tops-down” control of devices by, and reporting of data back to, a central node – usually a server in the cloud. It implies a degree of ownership and ability to configure both the network and all the devices that are members of the network.
- For a feature to become Mandatory, it shall be specified in the standard, committed in the open source and mandatory in the certification & interop program. Otherwise, it will be Optional. The latest approved open source code shall implement all the mandatory features of the latest approved standard The open source code can include optional components that are or not present in the standard, and vice-versa
- Collection is a resource that has references to other resources – can be used to build trees, graphs and other structures. Can also be used for simple groups. Attribute describes the state of a resource while the property describes the resource (example of properties are type, interface, discoverability, observability etc) Resource types have some similarity to but not the same as profiles in BLE.