developing interoperable iot controls

17
DD MM YYYY AllSeen Alliance ‹#› Developing Interoperable IoT Controls Founder, Two Bulls March 4th, 2015 NOAH HARLAN

Upload: allseen-alliance

Post on 16-Jul-2015

380 views

Category:

Technology


3 download

TRANSCRIPT

Page 1: Developing Interoperable IoT Controls

DD MM YYYY AllSeen Alliance ‹#›

Developing Interoperable IoT Controls

Founder, Two Bulls March 4th, 2015

NOAH HARLAN

Page 2: Developing Interoperable IoT Controls

D E V E L O P I N G I N T E R O P E R A B L E I o T C O N T R O L S

@noahharlan @two_bulls @AllSeenAlliance

Page 3: Developing Interoperable IoT Controls

@noahharlanB A C K G R O U N D : I O T

The Internet of Things = IoT

IoT is the world of objects when they are connected to networks.

Network access means objects can both communicate and be controlled.

Connected objects can be simple (light bulbs), complex (cars), personal (wristwatches), public (traffic lights) or industrial (forklift).

Page 4: Developing Interoperable IoT Controls

@noahharlanT H E E C O S Y S T E M

Pain: Cross-Platform/OEM Interoperability Solution: Standards Protocols!

Pain: managing large volumes of deployed devices. Solution: Platform as a Service Deployment Management

Page 5: Developing Interoperable IoT Controls

@noahharlanA L L J O Y N A N D T H E A L L S E E N A L L I A N C E

Qualcomm created AllJoyn as a standard communication protocol for IoT devices.

In December 2013, Qualcomm open sourced AllJoyn through the AllSeen Alliance so OEMs could coordinate on technical standards.

AllJoyn has since become the first widely adopted IoT industry standard with 122 members led by Electrolux, Haier, LG, Microsoft, Panasonic, Qualcomm, Sharp, Silicon Image, Sony, Technicolor, TP-Link, and - of course - Two Bulls!

Katie Schultz
Katie Schultz
AllJoyn
Page 6: Developing Interoperable IoT Controls

@noahharlanT H E P R O B L E M : I O T S T A N D A R D P R O T O C O L S B A T T L E

Each may have a place, but openness is the future.

A S A M P L E O F C U R R E N T I O T P R O T O C O L S:

STANDARDS OEM - SPECIFIC NICHE-SPECIFIC

AllJoyn Belkin WeMo Carvoyant

IoTivity Google Nest Fitbit

Home Kit Philips Hue EnOcean

Page 7: Developing Interoperable IoT Controls

@noahharlanT H E E C O S Y S T E M

Devices are talking to each other, but no one is coordinating the conversation.

Users are acquiring devices but onboarding and interacting is painful, utility is low.

Pain: Cross-Platform/OEM Interoperability Solution: AllJoyn!

Pain: User Interface overload & confusion

Page 8: Developing Interoperable IoT Controls

@noahharlanT H E P R O B L E M

Currently each brand requires a dedicated app to control its devices or even a dedicated app for each device.

You shouldn’t have a Philips app for your Philips light bulbs and an LG app

for your LG light bulbs.

You shouldn’t have to pull out your phone and open an app every time you want to

open your garage door.

You shouldn’t be forced to buy an Apple approved refrigerator simply because you

have an iPhone.

Page 9: Developing Interoperable IoT Controls

B L A S T F R O M T H E P A S T

Page 10: Developing Interoperable IoT Controls

How it all connects

Page 11: Developing Interoperable IoT Controls

@noahharlanM E E T H I G G N S

Higgns is your interface with the Internet of Things.

Higgns seamlessly translates your needs into orchestrated technical commands.

Higgns works across manufacturers and standards creating interoperability where none existed.

Higgns can control all your lights at once and have them respond to the rest of your environment. Watching a movie? Dim all the lights in the living room and switch the stereo to movie mode. Without opening an app.

Higgns can have your garage door open when you start your car. Without opening an app.

Page 12: Developing Interoperable IoT Controls

@noahharlan

IoT is a massively distributed computing environment.

Higgns is not an app

Latency, security, and scalability are critical issues.

Persistence in environments is as important as passing between them.

W H E R E I T I S

Higgns is control, distributed.

Apps, The Cloud, and the Proximal Network Topology

Page 13: Developing Interoperable IoT Controls

%XLOGLQJ�6FHQHV��0DNLQJ�6WRULHV

5EGPGU�CTG�EQNNGEVKQPU�QH�FGXKEGU�KP�C�URGEKHKE�UVCVG�

5VQTKGU�EQPPGEV�GXGPVU�VQ�CEVKQPU�VJG�WUGT�YCPVU�VCMGP�

*KIIPU�OQPKVQTU�+Q6�CEVKXKV[�CPF�KORNGOGPVU�VJG�WUGTũU�UVQTKGU�

+�2�:��,�7��:�2�5�.�6

Page 14: Developing Interoperable IoT Controls

DEMO

Page 15: Developing Interoperable IoT Controls

Q & A

Page 16: Developing Interoperable IoT Controls

@noahharlanT H A N K Y O U

C O N T A C T

w w w . h i g g n s . c o m

N O A H H A R L A N n o a h @ h i g g n s . c o m

+1 3 4 7 / 8 3 7 - 6 1 4 1

J A M E S K A N E j a m e s @ h i g g n s . c o m

+4 9 1 7 5 5 7 4 3 0 5 5

Page 17: Developing Interoperable IoT Controls

DD MM YYYY AllSeen Alliance ‹#›

Thank youFollow us on

For more information on Allseen Alliance, visit us at: allseenalliance.org & allseenalliance.org/news/blogs

© 2015 Two Bulls