IoT for Smart Cities:A Data Centric Perspective

Bharadwaj Amrutur

Professor

Robert Bosch Centre for Cyber-Physical Systems,

Indian Institute of Science, Bangalore

amrutur@iisc.ac.in

Outline

● Motivation & Context● Data Centric Perspective● IISc Testbed● Closing remarks

Smart City Features - India● Promoting Mixed Land use● Housing and Inclusiveness● Creating Walkable Localities● Preserving and Developing Open Spaces● Promoting Transport Options● Make Governance Citizen-Friendly and Cost-Effective● Give unique identity to a city● Apply Smart Solutions to Infrastructure & Services

from : http://smartcities.gov.in/content/innerpage/smart-city-features.php

Smart City Components

from: http://smartcities.gov.in/content/smart_solution.php

Perspectives from city administrators• Citizens must be the key beneficiaries of any smart city solution. It

should benefit all strata of society.

• Unified Command and Control centre is needed to be able to oversee all the city operations by the administrators.

• Need low cost, sustainable, interoperable solutions with smartness built in to help with maintenance and operations.

• Solutions should be vendor technology (s/w or hardware) agnostic

• It should enable development of future smarter/intelligent solutions.

Additional Observations

• Point solutions leading to Silos• Inability to reuse deployed resources

• Need reference implementations of reference architectures

• Lack of “India Appropriate Standards”• No interoperability test bed• What about new applications?

Cameras

Middle Ware

Storage, Dashboard, Analytics

Surveillance

Sensors

Middle Ware

Storage, Dashboard, Analytics

Parking

Example New Applications

@Citizen: Give me a route which is safe to walk and not worsen my allergies.

@Police: Can we get a better picture of a vehicle using the Streelight LED as a flash?

@StuckInTraffic: What is causing the traffic jam?

@Shopper: What are the deals available in this street now?

Outline

● Motivation & Context● Data Centric Perspective● IISc Testbed● Closing remarks

Our vision of a Smart City IoT Framework

• Focus on Data & APIs

• Extensible & Scalable

• Secure & Privacy preserving

• Sustainable & Maintainable

• Enable new cross-domain (real-time) applications

• Application & Device portability

Separation of Concerns: Data vs Devices

Data Middleware Architecture

11

Catalogue

● Directory - similar to hypercat● List of resources and their

associated meta information● REST API

Catalog Item Schema - 1

Catalog Schema - 2

Catalog Item: Streetlight - 1

Catalog Item: Streetlight - 2

Catalog Item: Streetlight - 3

Schema Validation Review

Streetlight Observation & Control Data

{ "dataSamplingInstant":77475, "caseTemperature":21, "powerConsumption":0, "luxOutput":781, "ambientLux":546}

{ "dataSamplingInstant":138321, "caseTemperature":21, "powerConsumption":21, "luxOutput":36, "ambientLux":24}

{ "targetBrightnessLevel": 70,}

{ "targetControlPolicy": "AUTO_TIMER", "targetAutoTimerParams": { "targetOnTime": 343434, "targetOffTime": 606400},}

Power Meter Observation Data

{"YPhaseReactivePower": 6.8999999202787876, "BPhaseVoltage": 230.93382263183594, "YPhaseApparentPower": 195.6000030040741, "YPhaseActivePower": 195.50000131130219, "RPhasePowerFactor": 0.91299998760223389, "BPhaseActivePower": 142.80000329017639, "EnergyReactive": 4934.6000003814697, "BPhaseCurrent": 0.62379997968673706, "RPhaseApparentPower": 5969.2997932434082, "RPhaseReactivePower": 2434.0999126434326, "YPhasePowerFactor": 0.99900001287460327, "RPhaseVoltage": 235.37983703613281, "BPhaseReactivePower": -18.999999389052391, "BPhasePowerFactor": -0.99099999666213989, "RPhaseActivePower": 5462.399959564209, "YPhaseCurrent": 0.83859997987747192, "YPhaseVoltage": 233.32395935058594, "RPhaseCurrent": 25.36039924621582, "BPhaseApparentPower": 143.99999380111694, "dataSamplingInstant": 1503896327.0, "EnergyActive": 8153.60009765625}

LPWAN Issues

● LPWAN such as LORA is non-IP● Would like to enable interoperability of City Scale IOT devices from multiple vendors

○ Parking Sensors○ Streetlights○ Garbage bins○ etc.

● Would be great if they agree on a common wire (air) format● Bandwidth is precious (only 2MHz) spectrum in India (currently)

○ Need to be efficient (better than JSON)○ Multiple possibilities

■ BSON, CBOR, Protobuf …..

Protocol Buffers for IoT Device Wire (Air) format

● Bandwidth efficient● Strong type checking● Open source toolkit for creating client libraries for handling, conversion etc.● Path to a richer exposure of services and RPC (gRPC) for more complex devices

Outline

● Motivation & Context● Data Centric Perspective● IISc Testbed● Closing remarks

Hardware Test Bed

B:PoleHub

C: OnPoleSensor (camera etc)

D: Intra-Pole Wired Interface

E: Pole Wireless CapillaryLink

H: Low BW/ Wireless Net

F: External fixed or mobile sensors

G: Inter-Pole Hi BW Wireless Mesh

A: Street Pole

H: Optic Fibre

Ubiquitous

Access to Power

Physical Mount Points

Network Architecture

iSCM Middleware Realization

LoRa Setup

API Key based Authentication and Authorization

Security Components

Authentication done here

Authorization checked by each service

Catalogue

Outline

● Motivation & Context● Data Centric Perspective● IISc Testbed● Closing remarks

Needs for Standards

● Schemas for IoT Devices (both real and virtual)○ E.g. JSON based schemas

● Interfaces to devices on LPWAN (non-IP)○ E.g. Protobuf

● APIs to Middleware○ Enable Application and Device portability across cities

● City Information Models - for Indian Cities○ Capture their structure, processes etc.

Acknowledgements

RBCCPS-IISc Team: Dr. Abhay Sharma, Vasanth Rajaraman, Rakshit Ramesh, Dr. Arun Babu, Dr. Ashish Joglekar, Srikrishna Acharya, Sahil, Dr. Yogesh Simmhan

Collaborators (from): Mapunity, Tejas Networks, Wipro, Bosch, IoT4SCTF, ELCITA

Thank You!

33