Welcome to IoTivityThiago Macieira Keywords Qt, intrinsics, compiler, optimisations, x86, assembly...

Welcome to IoTivityWelcome to IoTivity

Thiago MacieiraThiago MacieiraLinuxCon / Embedded Linux Conference Europe – October, 2015LinuxCon / Embedded Linux Conference Europe – October, 2015

2

Who am I?

3

Abstract

• What’s OIC?

• What’s IoTivity?

• How they relate to each other?

• Why should I care?

4

The challenge of IoT communications

• The Internet of Things is currently evolving as “Isolated Islands of Things.”

• Severely limits the value of IoT.

5

Addressing the Challenge of Communications

= Interoperability☑Standards Open Source

ProjectCertification

OIC (the standard) and IoTivity (open source project) are making it easy for devices to connect and interoperate – regardless of vendor, OS, hardware, etc.

6

The Strategy for Building Device Interoperability

IoT Device InteroperabilitySpecification Open Source Project Certification

☑• Industry leaders providing

guidance• Common protocols, security,

identity, and service-level protocols, object models and developer APIs

• Open specification that anyone can implement

• Reference implementation: fast-path to market

• Open source development

• Connectivity framework that abstracts complexity

• IP protection & branding for certified devices

• Certification = a device implementation as defined in the specification and released into the open source

7

IP Coverage best in industryOIC Others

Reference code is open source, permissive licence. ✓ ✓Reference code comes with a licence to use patents as long as certification is passed. ✓ ✓

Reference code comes with a licence to use patents even without certification (forking). ✓ ☒

Reimplementation of the specification can get certified and obtain patent licensing. ✓ ☒

Patents from member companies who do not contribute code are still licensed if needed to implement the specification. ✓ ☒

Patents from affiliate or parent companies of member companies are licensed. ✓ ☒

8

Building on other standards

RadioR

Others

NetworkIPv6

Dual-StackIPv4+IPv6

(Happy Eyeballs)

Bluetooth profileor 6lo over mesh

Transport UDP and TCP

Session CoAP (RFC 7252) CoAP-like

Encryption DTLS

9

IoT can’t deliver potential without the cloud

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

10

What is Cloud Native 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.

11

OIC and IoTivity are Cloud Native

• Designed with IPv6 and 6LoWPAN in mind, from the beginning– If there’s 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) as session layer– Very similar to HTTP/2.0

– UDP locally, we’ll use TCP to reach the cloud

• XMPP (eXtensible Message Passing Protocol) originally developed for chat applications

• JavaScript APIs implemented via node.js in IoTivity

12

Participate!

Become a member

• Membership levels:– Gold

– Platinum

– Diamond

• http://openinterconnect.org/join

Join the Open Source Project

– Download the code and get started

– Licensed under Apache 2.0 licence

– Contribute!

http://iotivity.org

Get educated on the standard– Draft 1.0 available on the site

– http://openinterconnect.org/newsletter☑

13

Sample of Current MembersDiamond:

Platinum:

Gold:

Non-profit:

14

Thiago Macieirathiago.macieira@intel.com

http://google.com/+ThiagoMacieira