global scale event notification

26
global scale event notification Bob Briscoe, BT Research Sep 2004 Acknowledgements : Jon Crowcroft (Uni Cam) Jane Tateson, Andrea Soppera, Trevor Burbridge (BT)

Upload: talib

Post on 13-Jan-2016

35 views

Category:

Documents


0 download

DESCRIPTION

global scale event notification. Bob Briscoe, BT Research Sep 2004 Acknowledgements : Jon Crowcroft (Uni Cam) Jane Tateson, Andrea Soppera, Trevor Burbridge (BT). event notification?. event: (the representation of) some asynchronous occurrence - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: global scale event notification

global scale event notification

Bob Briscoe, BT ResearchSep 2004Acknowledgements: Jon Crowcroft (Uni Cam)Jane Tateson, Andrea Soppera, Trevor Burbridge (BT)

Page 2: global scale event notification

event notification?

• event:(the representation of)some asynchronous occurrence

• asynchronous:at a time unpredictable to the observer

• occurrence:change in the state of an object

Page 3: global scale event notification

my point

• the Internet of thingsdepends on widespread event notification handlers

• far from consensus on outstanding hard problems• hard to make endpoints reliant only on themselves

• too onerous for challenged hardware

• but alternatives require unscalable state in comms infrastructure

IPUDPTCP…

?

IPUDP TCP …?

messaging services?

comms state

comms state

event notification handlerevent notification handler

Page 4: global scale event notification

phenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

conceptual model

assetregister

€7

property ofLegoland

3D assetmodel

• transducers• synchronising comms• distributed processing• cumulative layering

• transducers• synchronising comms• distributed processing• cumulative layering

care in the community, home, automotive, supply chain, Internet zero, sensor nets

care in the community, home, automotive, supply chain, Internet zero, sensor nets• the hard comms problem

• synch info models with real world• the hard comms problem• synch info models with real world

Page 5: global scale event notification

comms modes

asynchronous communications• iPic Web server [Shrikumar02]

– RFC1122 compliant, (Host Requirements)• HTTPd + FS 90 instr• UDP+TCP 98 instr• ICMP (ping) 14 instr• IP 68 instr• SLIP 76 instr• UART 56 instr• TOTAL 256B

• impressive but...

• do we continually ask everything physical to report its state?

• asynch event notification more applicable for sensors [Shrikumar01]

• polling never better: not timely, not efficient

• cascade of event notification over polling loses timeliness

• storing & reporting state can be decomposed“The iPic demo server is connected by a serial link, which is currently experiencing a load up to its full design capacity...Please visit the mirror site below.”

phenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

assetregister

€7

property ofLegoland

3D assetmodel

Page 6: global scale event notification

call-backone shot

request-reply

publish-subscribe

clientserver

listenerssource channel

request

reply

subscribe

publishnotify

newsubscribe

time

updates

updates

communication modesphenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

assetregister

€7

property ofLegoland

3D assetmodel

Page 7: global scale event notification

• inherently point to multipoint (group communications)• feeds from real world maintain plethora of views of the world

• no need for radio listener: power hungry

• but no control over subscription memory demand

storesubscriptions

storelast event

sensephenomenon

comms modes

publish-subscribe

storesubscriptions

storelast event

senseevent

listenerlistener

client

client

request reply

decomposition

pub-sub

req-rep

phenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

assetregister

€7

property ofLegoland

3D assetmodel

Page 8: global scale event notification

open but closable

• pub-sub has a nice ‘business model’

• basic model: open publication of data on a channel

• limit visibility with crypto or scoping of msg routing• rights can be changed out of band at run-time

• can maintain relationship with listeners, which pub-sub hides

• doesn’t lock in zero config devices to one company• zero config device’s packet destination is a neutral ‘channel’

• listeners join channel at run-time to complete msg routing config

Page 9: global scale event notification

mains Internetbattery net

energy constraint reverses rules

• don’t multicast until mains• minimise message.links

• can do better• aggregation of multiple messages

(directed diffusion) [Estrin00,01]

• concast

• cf generic router assist (GRA)(cisco - generalisation of nack aggregation (PGM))

• receiver initiated multicast– normal rules apply

• but gateway is proxy source (e.g. for re-transmit)

– relay doesn’t need meaning

• encrypt end to end

Page 10: global scale event notification

source

host 1

host 2 host 3

members

relay 1

relay 2

host 4

joinrouting group

host 1

host 2 host 3

source

listeners

duplicate

duplicate

host 4

multicastforwarding

host 1

host 2 host 3

listener

sources

aggregate

aggregate

host 4

concastforwarding

group formation and forwarding

host 1

host 2 host 3

initiator

potentialsources

install

install

host 4

deployaggregationbehaviour

e.g. COUNT, MIN, MAX, SUM, AVE(TinyDB)

e.g. COUNT, MIN, MAX, SUM, AVE(TinyDB)

see also stocast [Nekovee]see also stocast [Nekovee]

Page 11: global scale event notification

channelisation problem [Adler01]• each group’s channel requires stored resource

– either distributed group routing tables

• group routing tree created by receiver interest (app or net layer)

• each relay stores list of neighbour interest per routing group

• near-linear complexity: little inherent topological correlation?

– or channel allocations

• each group in each ‘cell’ allocated spectrum/timeslot/code/ etc

• if aggregate channel resource• must then filter at receiver wasting b/w, interrupts and processing

• or filter in network (equivalent to channelisation problem)

• or index-based dynamic creation of groups [Soppera:watchcast]

• creates an economic limit to pervasive computing

everywhere in network between event sources and group interesteverywhere in network between event sources and group interest

Page 12: global scale event notification

the unexpected didn’t happen – I think

• if pub-sub, avoid ack implosion & sender doesn’t know receiver list anyway

• nack preferred (SRM/concast etc avoids implosion)

• rcvr cannot nack asynch msg– until receives next in sequence (msec or years later)

• solutions:– hop by hop ack [Rowstron01:SCRIBE]

– e2e index beacon [Soppera:watchcast]

• note: hop by hop ack doesn’t imply e2e delivery (cf TCP)

• for sensor nets, e2e = across concast & multicast parts

Page 13: global scale event notification

attempts at solutions

global scale event notification

Page 14: global scale event notification

Generic Announcement Protocol

Announcement Thread ID

version

Payload

IP

multicast

Generic Announcement Protocol (GAP)

Managed GAP

Watchcast Application

Business Solution

<ath:URL=http://www.hosting.org/AThID?set=farm$31425>

Page 15: global scale event notification

index-based event messaging

indexerevent1

sender

event2

sender

event3

sender

potential receivers

joins (routing) data (forwarding)

multipoint request-reply

IP

multicast

Generic Announcement Protocol (GAP)

Managed GAP

Watchcast Application

Business Solution

zero cost forextra watches

Page 16: global scale event notification

SPINS [Perrig01]• implemented on Berkeley motes

• group security, not just 1-1

• based on two primitives:• SNEP for message encryption

• TESLA for message authentication

• TESLA derives asymmetry from passage of time, not modular exponentiation [Perrig00:TESLA, Briscoe00:FLAMeS]

• strong cryptobut light processing & msg overhead time

K0,j

CS,i

MiA0,i Mi+1A0,i+1 K0,j+1 ...

PiCS,i

CS,i +T0,K+T0,GCS,i+T0,K

MmA0,m K0,n

Page 17: global scale event notification

straw man proposal

phenomenontamper-resistant

hard-codedmulticast

groupaddress

stored symmetric seed

wipe then update by touch

key server copy of seed

EK1(1,event1)

• design goals• zero rcv• zero config

• design goals• zero rcv• zero config

EKi(i,eventi)

EK1(1,event1)

EKi(i,eventi)

EK1(1,event1)

EKi(i,eventi)

threshold transitionthreshold transition

threshold transitionthreshold transition

beacon repetitionbeacon repetitionK1...Ki

pseudo-random key sequence from symmetric seed

K1...Kipseudo-random key sequence from symmetric seed

one hop to mains power

Page 18: global scale event notification

prerequisites for Internet of things

• ubiquitous pub-sub

• but also…• group creation facilities capable of 106 group /sec worldwide

• infrastructure investment incentives

• if p2p infrastructure, solve free-riding

• solve privacy without limiting commercial potential

all our efforts here now privacy is the gating factor

(what you’ve seen is 2-4yrs old)

all our efforts here now privacy is the gating factor

(what you’ve seen is 2-4yrs old)

Page 19: global scale event notification

more info

• strange links, ad hoc connectivity creation, routing across sensor databases, addressing events, message traffic profiles, unusual congestion control, security in the wild, key establishment without RSA and more…

Bob Briscoe, "The Implications of Pervasive Computing on Network Design" BT Technology Journal 22 (3) pp. 170--190 URL: <http://www.btexact.com/publications/bttj/bttjissues/> (July, 2004)(but deliberate journal on-line publication delay)

[email protected]

• questions?

Page 20: global scale event notification
Page 21: global scale event notification

global scale event notification

spare slides

Page 22: global scale event notification

IP Multicast - recap

receiver initiated

receivers join group

Data replicated by routersData sent to group

IP

multicast

Generic Announcement Protocol (GAP)

Managed GAP

Watchcast Application

Business Solution

IP address within an allocated rangerepresents a ‘group’ not a host

IP address within an allocated rangerepresents a ‘group’ not a host

Page 23: global scale event notification

connectivity of everything

• as a statement of scope– otherwise implications on networking uninteresting

• as a statement of recommendation– universally present software:

• TCP/IP, event notification?, higher... HTTP, XML parser?

– why? if relative cost small, potential benefit is large

• TCP/IP cost:– 200B code (cf. TinyOS 3.5kB, mote 8kB)– memory smaller, cheaper, energy efficient O(2t/D)– processing costs energy– headers cost bandwidth esp. IPv6 (header compression helps)

• potential benefit: O(n2) [Metcalfe]

– avoid constraining new uses by locality

n = no. of connectable

nodes

n = no. of connectable

nodes

D = doubling timeD = doubling time

Page 24: global scale event notification

connectivity creation

motivating force• no grand plan for the model of everything

– mini-models required in their own right

• re-sell for others to build bigger models– retail then wholesale

• or open publication?

phenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

assetregister

€7

property ofLegoland

3D assetmodel

Page 25: global scale event notification

connectivity creation

connectivity by arrangement?• how did the model’s connectivity arise?

– by arrangement: frequencies, formats, codings, protocols, languages

– created within another application: discovery and configuration

• classic example:– personal digital assistant seeks attractive monitor

– love at first byte? straight to layer 7 on the first date?

• an alternative– cyberspace as chaperone and matchmaker (pre-connected)

– new requirements on cyberspace

• proximity model(s)

• are you a flatscreened Sony or a 53yr-old divorcee from Hounslow in a rain-coat?

phenomenon

colourphotography

visualmodel

edge detection

edgemodel

thermalimaging

co-s

enso

rs

thermalmodel

assetregister

€7

property ofLegoland

3D assetmodel

Page 26: global scale event notification

802.11 RS432IPv6 no-net

ASCII XDRJINI SLP

TCP eh?

*%+4/s9d

???

locationmodels

incyberspace

• more advantages• coverage• augmented reality

• more advantages• coverage• augmented reality

proximity awareness

?XML

capability description