the iot technical challenges for...

51
The IoT – technical challenges for interoperability Sandra Stinčić Clarke, Principal Researcher, BT TSO

Upload: others

Post on 28-May-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

The IoT – technical challenges for interoperability

Sandra Stinčić Clarke, Principal Researcher, BT TSO

Page 2: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Overview

• IOT ecosystems

• Actors & Interoperability

• Information brokerage & data hubs

• Connectivity

• Interoperability

• Examples:

– Logistics, Smart Cities, etc.

Page 3: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Internet of Things

* Gartner 26bn not including PC, Laptop, Smartphone by 2020

* ABI research 30bn any connected devices by 2020, 10bn in 2014

26bn+

sensors

devices

apps

industry

home

cities

lifestyles

achieving more with less

Page 4: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IoT opportunities for cities Reduce city congestion

Reduce energy use

Reduce traffic congestion

Streamline supply chains

Improve Air Quality

Save city councils £££

Plan journeys

Optimise waste disposal

Improve health

Enable assisted living at home

Reduce demand for water

Reduce accidents

Enable economic growth

….

Page 5: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Multiple players

Data privacy

T&Cs of Use

Monetisation of Data

Data ProvidersSensor Providers

Application Developers

SMEs Enterprises

Government

Education Sector

Utility Companies

Citizens

Page 6: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Car park sensors

Air quality sensors

Congestion sensors

Busyness sensors

Movement sensors

Cameras

Energy use

Water use

Temperature and heating

Satellite data

Smart phone / crowd sourcing

In vehicle sensors

Demographics

Water levels

Weather stations

….

Key issue: Merging it all

DA

TA

SO

UR

CE

S

?

Page 7: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

BT IoT Data Hub

* MK:Smart project, Milton Keynes

Page 8: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

LightSensor Bin

Usage

ParkingSensor

Vehicle Telemetry

RFIDTrace

Soil Moisture

Enabling the IoT ecosystem

TVWS

MESH

SENSORS CONNECTIVITY DATA HUB APPLICATIONS

UNB

Smart Parking

Driver Assist

Waste Management

TracingAssets:BT Trace

Smart Street Lighting

Analytics

Dev Environment

IT Services

Information Spine

IoT Ecosystem

Page 9: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IoT Ecosystem (II)

http://en.wikipedia.org/wiki/Internet_of_Things

Analytics

Dev Environment

IT Services

Information Spine

Page 10: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

ConnectivityIOT access networks

Key requirements

• Low Power (may need to run off batteries for several years)

• Long range – rural or in-building penetration (so sub 1Ghz best)

• Low cost – needs to be cheap

• Low Data rates –IoT use cases only need to transmit small amounts of data (Note: often, not always)

• Global Standards – economies of scale, works everywhere

Page 11: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IOT access networks

• Licensed

– Owned by Mobile Operators

– Can offer guaranteed QoS

– Standards evolving e.g. LTE-M

• Unlicensed

– Available to anyone –start-ups tend to use unlicensed

– 868MHz is available across EU, different spectra elsewhere

– Shared spectrum, so no guaranteed QoS

– Still regulated however – e.g. duty cycles (quota)

– Many players – e.g. LoRa Alliance are among most prominent

Page 12: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IOT access networks

• Different access networks appropriate in different scenarios

– Power

– Building penetration

– Local topology and geography

– Data rates and volumes

Page 13: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Other architectural considerations

DEVICE MANAGEMENT

EDGE PROCESSING

Page 14: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Interoperability

“Interoperability is essential to unlock 40% of the $11 trillion potential value of the IoT”

(McKinsey)

Page 15: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IoT Ecosystem

* Showing BT data hubs as example – 3rd party data hubs expected

Page 16: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Interoperability (II)

RISK:

without InteroperabilityData Hubs will become

Data Silos

Page 17: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

City Motion Map

Smart WaterUsage

Smart EnergyUsage

The Parks Trust

Smart StreetLighting

Smart Social Care

Smart Trap Air Quality

Driver AssistSmart ParkingSmart WasteManagement

Smart Home

Air Monitors

Car Park SensorsSmart Phones

Water Levels

Bin Sensors

Street Lights

Rat TrapsSatellite Images

Traffic Counting

Bus Bus Feeds

Weather Sensors

Train FeedsPedestrian Counters

Home Sensors

Aggregation pushes Innovation

Page 18: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

IoT hub to support the ecosystem

• Data aggregation

• Economies of scale

• Uniform access to data

• Breaking down silos

• Lowering the barriers to participation for data providers and app developers

• Fostering innovation

• Maximising the value of vast volumes of multiple types of data

Page 19: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Open Ecosystem

Page 20: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Interoperability Challenges

• Resource discovery and access (what data does this hub have and how do I get it?)

• Interoperation between hubs

Page 21: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Interoperability

• Nationally-funded

IOT Demonstrator programme

• 8 projects, each with an IOT data hub

• Requirement for hubs to interoperate

“Interoperability is essential to unlock 40% of the $11 trillion potential value of the IoT”

(McKinsey)

Page 22: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

HYPERCAT

• Hypercat standard

– a machine-readable data catalogue

– automated data discovery and access

• Breaking down silos

• Fostering innovation

• Maximising the value of data

www.hypercat.io

Page 23: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

HyperCat is:

• A data catalogue format for IOT data hubs

• More generally, a format for catalogues of data and services (or anything you care to point a URI at)

Page 24: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

HyperCat is:

• A JSON file format for cataloguing IoT resources - a HyperCat file

• A web API for fetching, serving, searching and editing HyperCat catalogues - The HyperCat Web API

HyperCat is:

Page 25: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

HyperCat provides:

• A standard endpoint to start probing– datahub.com/cat

• A standard response format with a catalogue of resources and metadata

• Mechanisms for interacting with the catalogue

Page 26: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

HyperCat is pragmatic

• Open source and royalty free

• Easy to implement

• Extensible

• Short, simple specification

– small mandatory core, community driven extensions

• Built on well-used web technologies

– JSON, RESTful

Low barrier to entry, “needs to ensure standards do not become barriers”

Page 27: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

‘s place in the world

• HyperCat is a common web API and file format

• It has a small set of mandatory core metadata

– horizontal

– can easily link to domain-specific vertical vocabularies

• It exists at application layer (OSI Layer 7)

• It is not transport, network, link or physical layer

Page 28: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

fragment

"items":[

{

"href":"http://api.bt-hypercat.com/sensors/feeds/3bdae7b8-c4c6-4701-81a7-e9ffcb47c6ac",

"item-metadata":[

{

"rel":"urn:X-hypercat:rels:hasDescription:en",

"val":"Air quality data from MK"

},

{

"rel":"urn:X-hypercat:rels:isContentType",

"val":"application/xml"

},

air quality data feed

in Milton Keynes

Page 29: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Empty Catalogue

Servers should serve a catalogue on http://hub.com/cat

The catalogue is a JSON document with MIME type application/vnd.hypercat

{

"catalogue-metadata":[

{

"rel":"urn:X-hypercat:rels:isContentType",

"val":"application/vnd.hypercat.catalogue+json"

},

{

"rel":"urn:X-hypercat:rels:hasDescription:en",

"val":"Minimal empty catalogue"

}

],

"items":[]

}

* (This is the minimum valid response, though it doesn't provide much interop potential...)

Page 30: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

is a Typed Catalogue

Annotate every item with a MIME type

(An app client can now tell which resources it is capable of consuming by format)

{

"catalogue-metadata":[

{

"rel":"urn:X-hypercat:rels:isContentType",

"val":"application/vnd.hypercat.catalogue+json"

},

{

"rel":"urn:X-hypercat:rels:hasDescription:en",

"val":"Typed catalogue example"

}

],

"items":[

{

"href":"http://hub.com/resource1",

"metadata":[

{

"rel":"urn:X-hypercat:rels:hasDescription:en",

"val":"Census data in CSV format"

},

{

"rel":"urn:X-hyprecat:rels:isContentType",

"val":"text/csv"

}

]

}

]

}

Page 31: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Catalogues and Resources

Servers provide catalogues of resources to clients

A catalogue is an array of URIs

Page 32: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Resource Metadata

Each resource in the catalogue is annotated with metadata (RDF-like triples)

Page 33: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

can advertise it’s API Discovery

A catalogue can advertise API mechanisms using its metadata

{

"metadata":[

{

"rel":"urn:X-hypercat:rels:supportsSearch",

"val":"urn:X-hypercat:search:simple"

},

...

],

"items":[...]

}

Page 34: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Is it Linked/Open Data?

• Yes (if you want)

• Linked resources are URIs

• Metadata is triples

• Interoperable with RDF

– RDF predicates (URIs) can link resources to RDF classeshttp://www.w3.org/1999/02/22rdfsyntaxns#type

• Hypercat can also be serialized in RDF or XML

Page 35: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

- Is it yet another industry body?

• No (not really)

• It is free, open, lightweight and can be used by anyone

• Addresses the issue of data discovery and exchange

• Agnostic with respect to architecture

Page 36: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

• British Standards Institute PAS

– Publically available specification

• Next step: BSI to identify most appropriate international standards body

• 15-20 data hubs

• 200+ organisations are part of the Hypercat consortium

- Current Status

Page 37: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Relationship to other initiatives

• IIC – Hypercat is a member

– IIC testbed partners will use Hypercat

• OIC – partnership agreement

– ‘use HyperCat to define relationships between resource types, catalogue them, and make them searchable’

• Let’s talk!

Page 38: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Interoperability Challenges

Google Doodle 21/06/2013 celebrates the 82nd birthday of Zlatko Grgić with his image of Profesor Baltazar and his magic machine

(Croatia and Slovenia Google Sites)

Page 39: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

APPLICATIONS

Page 40: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

MK:Smart use cases can be applied to cities across the world

Page 41: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Smart Parking and Smart Lighting

Page 42: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Increased speed in the prototype creation

* Flexeye’s tool Hyperspace utilising hypercat enabled Data Hubs,

Page 43: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Transport & Logisticse.g. Automation of pre-journey checks

Page 44: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Vehicle Registration

& Make

BT and Other

Information HUBs

Road TAX Due Date

MOT Due Date

“O” Licence Data

( HGV Fleets Only )

Vehicle Check

Template

Service Due Date

( HGV Fleets Only )

Check Licence and TAX Information

Page 45: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Summary

• IOT ecosystems

• Actors & Interoperability

• Information brokerage & data hubs

• Connectivity

• Interoperability

• Examples:

– Logistics, Smart Cities, etc.

Page 46: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

real time traffic

bus location

air quality

humidity (indoor)

pu

blic

tra

nsp

ort

tem

pe

ratu

re

driver behaviour

wa

ter

leve

l

IoT enabled cities

resource 1

resource 2 resource 3

resource 4

resource 5

resource 6

/cat1

/cat2

resource 1

resource 2

resource 3

reso

urc

e 4

Page 47: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Sup

po

rtin

g Sm

art

Cit

ies

* Future plans for Greater Cambridge

Page 49: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Page 50: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Questions?

Sandra Stinčić Clarke

Principal Researcher

Future Business Technology Research Practice

BT Technology, Service & Operations

Adastral Park, UK

email: [email protected]

Page 51: The IoT technical challenges for interoperabilityicteri.org/sites/default/files/Stincic-Clarke-2016-06-22...2016/06/22  · Interoperability Challenges Google Doodle 21/06/2013 celebrates

© British Telecommunications plc

Acknowledgements

• Icons Designed by Freepik and distributed by Flaticon(www.flaticon.com)