IBM ADEPT

DEVICE DEMOCRACYSolid 2015

!

!

!

IBM Institute for Business Value

© 2015 IBM Corporation

CREDITSIBM IBV !Paul Brody Veena Pureswaran Sumbala NairSanjay Pannikar ADEPT team !SpeakerHenning Diedrich

2

ADEPTIoT research project by IBM

3


ADEPT: CES DEMO RECAP

• washer buying detergent

• washer bartering energy use

• washer ordering service

4

RetailerOrder, Payment

Confirmation

Payment

Negotiation

Detergent!Check

TV Price Alert

Confirmation

Service Request

Service"Vendor Service Checklist!

Warranty Check

Owner

ADEPT"WASHER

Notification

1 2

3


BIG PICTURE IOT• coming massive computing power of ‘things’ • failed expectations • market size trailing predictions • IBM IoT Platform on Bluemix • autonomous devices • inter-device commerce

5


ADEPT: IOT CHALLENGE FOCUS

√ cost □ trust √ monetisation √ interoperability √ discoverability √ authentication √ long term service expectation □ scale

6

Lack of Not future-proof

Lac

k of

pri

vacyInternet

of Things

Broke

n business High cost

m

odels

fun

ctional value


DEVICE OWNERSHIP OPTIONS

• manufacturer • provider • owner • device

7


DECENTRALIZATION

8

!

device agency device democracy

open platform common market

ADEPT VISION


ADEPT DESIGN

√ trust-less peer-to-peer messaging √ distributed file sharing √ autonomous device coordination □ identity

10


ADEPT VISION

□ highly efficient digital marketplaces √ real-time resource competition √ inter-device agreements √ direct payments between devices √ service and resource barter between devices □ inter-device reputation !

√ = demo’ed11


ADEPT DEVICE CATEGORIES

12

ADEPT Device Categories

Light&Wallet&

Messaging& File&Transfer&

Related&Peer&List&

Op7mized&Wallet&


Related&Peer&List&

Autonomous&Device&Coordina7on&Framework&

Data&Management&&&Analy7cs&

Transac7on&Verifica7on&(capabilityIbased)&

Full&Wallet&


Related&Peer&List&

Autonomous&Device&Coordina7on&Framework&

Data&Management&&&Analy7cs&

Transac7on&Verifica7on&&(Full)&

Marketplace&Enablers&

P.&Ex.&Marketplaces&

Implemented&as&PoC&

Proposed&

Light&Peer&

Standard&Peer&

Peer&Exchange&

37


ADEPT ARCHITECTURE

(√) protocols, services, applications √ TeleHash, BitTorrent, Ethereum □ light peers, standard peers, hub

13

ADEPT ArchitectureLogical View

Devices enabled as decentralized autonomous peers Device communication private by

UI

Business

Messaging

LifeCycle

Message

Blockchain

LifeCycle

Transaction

File Sharing

LifeCycle

File sharing

Data

LifeCyclePeer

Analytics

Asset

Appliance Examples Resource

Virtual Diagnosti

Data Management (e.g. MySQL & Distributed DB)

E.g. Android, Linux compatibility

Messaging

Store &

OptimizedBlockchain

Mining

File Sharing(e.g.

Own and Light Peer protocol

Auto

nom

ous

Dev

ice

ADEPT Installer

Application

Open source

Open source

Data

OS

ADEPT ArchitectureLogical View

Devices enabled as decentralized autonomous peers Device communication private by design Capability to achieve distributed consensus

UI

Business Logic

Messaging Service

LifeCycle

Message Handler

Blockchain Service

LifeCycle

Transaction Handler

File Sharing Service

LifeCycle

File sharing Handler

Data Management Service

LifeCycle

Peer Management

Analytics

Assetsharing

Appliance Self-service Examples

Resource Bartering

Virtual CreditManagement

Diagnostics

Data Management (e.g. MySQL & Distributed DB)

E.g. Android, Linux compatibility

Messaging (e.g. Telehash)

Store & Forward

OptimizedBlockchain

(e.g. Ethereum)

Mining

File Sharing(e.g. BitTorrent & OBEX)

Own and Light Peer protocol handler

Auto

nom

ous

Dev

ice

Cord

inat

ion

Fram

ewor

k

ADEPT Installer

Application Layer

Open source Services

Open source Protocols

Data Layer

OS Interface


ADEPT DEVICE SECURITY AND MAINTENANCE

• automatic and secure software updates • verification of trustworthiness of peers • self-maintaining, self-servicing units

15

© 2015 IBM Corporation|

/Use Case 1: The Autonomous WasherAutonomous transactions between Washer, Retailer, After Sales Service and other appliances.

16

RetailerOrder, Payment

Confirmation

PaymentNegotiation

Detergent!Check

TV Price Alert

ConfirmationService Request

Service"Vendor Service Checklist!

Warranty Check

Owner

ADEPT"WASHER

Notification

1 2

3

Consumables Marketplace 1

2

3

Service Marketplace

Energy Marketplace

Use Case Scenarios:

© 2015 IBM Corporation|

Interactions – Detergent reorder

Trigger:Detergent falls below re-order levelMake payment against existing contract.!Features demonstratedConsumables analyticsPolicy to invoke payment contractSecure point to point messaging

Ethereum Payment()

TelehashCreate order()

TelehashDispatch confirmation ()

Notify owner()

Notify owner()

1

2

2

34

4

17

Authorized Retailer

Authorized Retailer

© 2015 IBM Corporation|18

Interactions – component in-warranty replacement

If In warranty, raise telehash Replacement Order()

If in warranty, Telehash Service order confirm ()Notify owner()

Notify owner()Verify warranty status()

1

5 4

2

3 35

Trigger:Washer detects potential air filter failure.Find authorized service center.

!Internet discoveryIn device analyticsBlock chain verificationSecure point to point messaging

Check warranty status()

BLOCKCHAINWhy Blockchain?


WHAT IS A BLOCKCHAIN?

!

• trust-less network

• signed transactions

• public consensus

• transaction code

20


SMART CONTRACTS

• transaction scripts • on- or off-chain • transacting value-holding token • micro-fee capability

21


BLOCKCHAIN CHALLENGES

privacy scaling mining finality volatility legality stability

22


• Bitcoin limited smart contracts • Ethereum not ready • Ripple not decentralized

23

THE CLOUDas peer


CLOUD AND ADEPT

• hash key in the chain

• content in key-value* store like Cloudant

• scaling platform like Softlayer

25


CLOUD AS PEER

Cloud as State-Holder

• cost efficient

• unlimited capacity

• elastic scale

26

Cloud as Code-Repository

• light protocol

• fast execution

• out-of-band validation

ONGOING DEVELOPMENTS


CURRENT RESEARCH

• Consensus implementations • Performance scaling vs centralized solutions • Energy cost of proof of stake vs. proof of work

28


CONSENSUS IMPLEMENTATIONS

• Proof of Work • Proof of Stake • Traditional Consensus Protocols

29


PERFORMANCE SCALING VS CENTRALIZED SOLUTIONS

Performance for decentralized and centralized models with increasing network size for downloading a 100 MB file, with Kademlia messages generated between any random pair of nodes at an interval of 30 ms.

30


ENERGY COST

31

Power&Consump-on:&PoS&v/s&PoW •  2"device"types""

•  GPU_dev:""•  Radeon"R9"290X"

•  Idle"power:"20W"•  Stressed"power:"308W"

•  Intel"BaseAT"NIC"•  Idle"power:"21.2W"•  AcHve"power:"21.4W"

•  CPU_dev:""•  Intel"PenHum"4"540"processor""

•  Idle"power:"150W"•  Stressed"power:"223W"

•  Intel"BaseAT"NIC"•  Idle"power:"21.2W"•  AcHve"power:"21.4W"

"

•  1000"devices"•  100"miners,"900"nonAminers"•  1"blockchain,"12s"blockAHme"•  Nature"of"traffic"

•  SimulaHon"run"for"12,000"seconds"(1000"block"Hmes)"•  On"average,"an"event"happens"every"0.25s"•  Event"is"either"publish_contract,"call_contract,"or"

send_money."Each"happens"with"equal"probability."

•  Up"to"41%"less"power"consumed"by"PoS"than"PoW."This"is"in"the"all"GPU"case."

0"20"40"60"80"100"120"140"160"180"200"

0" 0.25" 0.5" 0.75" 1"

Avg."Pow

er"Con

sumed

"

FracHon"of"GPU"devices"

Total"PoS" Total"PoW"


ENERGY COST

32

•  1000#Raspberry#Pi�s##•  100#miners,#900#non3miners#•  12s#block38me#•  Simula8on#run#for#12,000s#•  Choice#of#consensus#mechanism#ma>ers#–#

but#not#so#much#for#low#power#devices#•  PoW#consumes#less#than#6%#more#energy#

than#PoS#•  Energy#consumed#by#PoS#consensus#

mechanism#is#close#to#devices#opera8ng#in#idle#mode#


BLOCKCHAIN SIZE

33

Size%of%the%Add,only%Block,chain

0"

200"

400"

600"

800"

1000"

1200"

1" 7" 13" 19" 25" 31" 37" 43" 49" 55" 61" 67" 73" 79" 85" 91" 97"103"109"115"121"127"133"139"145"151"157"163"169"175"181"187"193"199"205"211"217"223"229"235"241"247"253"259"265"271"277"283"289"

Size"of"B

lockchain"(M

B)"

Time"(Hours)"

100"tps" 50"tps" 25"tps" 10"tps"

•  This"chart"emphasizes"the"need"for"block"chain"pruning."•  A"device"with"1GB"memory"would"run"out"of"memory"fairly"quickly."""

Time"of"crash"

Time"of"crash"

Time"of"crash"

Time"of"crash"


OTHERS’ EFFORTS

• Samsung • Filament • 21

34


FILAMENT

35


FILAMENT

TeleHash Bitcoin mainnet Blockname DNS JOSE off-chain code Pennybank microtransactions

36

SUMMARY & OUTLOOK


WHAT WE'VE LEARNED

• concept works • much left to do • blockchain works as advertised • smart contracts are a powerful new paradigm • machine-to-machine commerce works

38


WHAT WE DON'T KNOW YET

• scaling • privacy • consensus algorithm

39


PRODUCTS AS SUBSCRIBED EXPERIENCE

• empowering the sharing economy

• subscription, not purchase

• full life time full service

40

Instrumented

Intelligent

Invisible

Interactive

Interconnected


BUILDING AN OPEN DEVICE ECOSYSTEM

!

Charge to the industry

41

p

Registration of new device

Authentication of remote

users

Contract to barter power with other

appliances

Checklist for automobile

safety

IBM ADEPT

Technology

Transcript of IBM ADEPT