Mark SkarpnessDirector of Embedded Software

Intel Software and Services Group

Mobile

50BDEVICES**

The Internet of Things is…Intelligence Everywhere

Home/ Industrial

Sensors

Network DC/Cloud

Gateway

*** Goldman Sachs** IMC/EDC: The Digital Universe of Opportunities* IDC

***COST OF

SENSORS2X

PAST 10 YEARS

COST OF BANDWIDTH

40XPAST 10 YEARS

COST OF PROCESSING

60XPAST 10 YEARS

44ZETABYTES**

Key Features for IoT Development

Customization Connectivity SecurityDevice

Management

IoT Comms Infrastructure

Bluetooth 4.2BlueZ (Classic + LE)

NFCneard

TelephonyoFono

IP

IEEE 802.15.4

Interconnect

Device Discovery & MessagingREST/CoAP

Protocol BridgeServices(Rich Device)

Kernel

DLNA Plugindleyna

Comprehensive comms framework for any type of implementation.

* Other names and brands may be claimed as the property of others.

The Challenge of IoT Communications

IoT is currently evolving as unconnected islands of devices

Addressing the Challenge of Communications

OIC goal is to make it easy for devices to connect and interoperate - regardless of vendor, OS, hardware, etc.

* Other names and brands may be claimed as the property of others.

100+

Industry Standards

Open Source

Interoperability+ =

Open source and standards to foster innovation.

Building Connectivity Standards

8

IoT can’t deliver potential without the cloud

source: http://m.eet.com/media/1174500/internet-of-things-lg.jpg

Cloud-Native Architecture for IoT

•Devices can reach the cloud directly.

•Devices can self-organize if the cloud is not accessible.

•Architecture and protocols don’t have to be replaced when device deployment changes from local-only to cloud-connected.

•Encourages end-to-end micro-services.

What Makes OIC and IoTivity “Cloud-Native”

• IPV6 and 6LoWPAN designed into the protocol from the beginning; provided there is a link to the internet, supporting devices can readily talk to the cloud.

• RESTful API techniques that tolerate intermittent connections between devices and services

• CoAP (constrained application protocol) over TCP/IP that allows local devices to reach the cloud by sending information via TCP/IP to the cloud, while using the simpler UDP protocol locally.

•XMPP (extensible message passing protocol) originally developed for chat applications.

• JavaScript APIs implemented via node.js in IoTivity to ease both local and cloud development.

Where OIC is today

1.0 Spec ready today

1.0 IoTivity code ready

First round of certification in progress

OIC-certified products shipping in volume soon

Participate!Become A Member! Join Open Source Project Get Educated on the Standard

Membership includes:Gold Membership and above:• Certify spec compliant apps and

devices• Use OIC branding• Benefit from patent cross-licensing

protection• Provide input in the standard

development• Participate in working groupsPlatinum and above:• Vote in working groups• Have leadership positions Diamond and above:• One director appointed the board

http://openinterconnect.org/join/

• Download the code and get started

• Code is available at under the Apache v2.0 license

• Contribute code!

http://www.IoTivity.org

• Go to the website to find out more and sign up to get updates http://openinterconnect.org/newsletter/

http://www.openinterconnect.org

Device interoperability will change IoT as we know it today!

Back Up