Supporting a Unified IoT Architecture through Inforamtion-Centric - - PowerPoint PPT Presentation

Supporting a Unified IoT Architecture through Inforamtion-Centric Networking

张燕咏 Yanyong Zhang WINLAB, Rutgers University yyzhang@winlab.rutgers.edu

Introduction

WINLAB

A Vision of the Internet of Things (IoT)

Goal: many-to-many networking between things and devices

WINLAB

Legacy IoT systems

 Silo IoT Architecture (Fragmented, Proprietary):

 e.g. DF-1, MelsecNet (Mitsubishi Electric), SDS (Honeywell),

BACnet, Bluetooth Low Energy, etc

Vertically Integrated

WINLAB

State of the Art

 Overlay Based Unified IoT Solutions (i.e., OpenIoT, AllJoyn)  Disadvantages

 The lack of naming transparency between systems which hinders efficient

data/service discovery

 The lack of networking-layer support such as multi-cast, mobility support

Internet

Smart Homes

Publishing Subscribing

Sensors Routers IoT Server IoT Applications IoT Gateway

Publishing

Smart Grid Sensors IoT Gateway Smart Healthcare Sensors IoT Gateway

API API API

Publishing

WINLAB

ICN-Centric Unified IoT Platform

ICN

Smart Home

Home -1

Home -2 D2D Smart Transport Smart Healthcare

App

ICN

IoT Smart Home Management IoT Smart Transport Management IoT Smart Healthcare Management

App

ICN

App

ICN

ICN has a potential to enable interaction between Consumers, IoT ASPs, Network Operators ICN potential as Network layer at the edge?

ICN-IoT Middleware

WINLAB

A Typical ICN-IoT System

…

…...

IoT Aggregator (e.g. Raspberry Pi, Smart Phone, nest thermostat)

 Basic hardware information for attached sensors  Service types of the attached sensors  Sensor names for ICN-enabled sensors  Information about sensors attached to peer aggregators

Local Service Gateway (e.g., AP, local gateway)

 Full information of IoT resources in the local networks (including sensor service types)

ICN Network

APP—Website, Mobile APP: ICN Data Consumer

Radio-specific Interface Adaptation

ICN Adaptor ZigBee, TO, 6LoWPAN, BLE,etc

ICN Non- ICN ICN

Edge Service Router Service Controller Edge Service Router Service Provider

ICN-NNI ICN/Non - ICN Data Center

Sensors (e.g., RFID, temperature sensors)

 Sensor hardware information  Sensor names for ICN-enabled sensors IoT Server

 Names and the service types that are exposed to the server  Subscription memberships

WINLAB

Local Interactions in ICN-IoT

• 1. S1 and S2

periodically sends sensor data to AG2

• 2. AG1 requests data from S1

and S2 through AG2

• 3. AG2 returns data to AG1

ID Service type S1 temperature S2 temperature AG1 thermostat

AG 1 AG 2 S1 S2

Objective: Nest thermostat needs temperature readings from multiple temperature sensors

ID Service type AG2/S1 temperature AG2/S2 temperature AG1 thermostat

WINLAB

Remote Interactions in ICN-IoT

• 1. Sensors send updates

to aggregator

ICN Network

Smartphone sends request to retrieve the resource: /bob/home/temperature_sensing/1 (resource acquired through the IoT server) Local Service Gateway has the full information for the local resource

A: Request B: Data

A A A B B B Objective: Smartphone (away from home) needs temperature readings from home temperature sensors

WINLAB

ICN- IoT Functionalities

FIA Optional: In-network Computing (Data Aggregation/Fusion) Network Service ( Unicast, Multicast, Anycast, etc) Pub/Sub Management Device/Network Service Discovery Service Device/App Naming Service Name-based Routing

Sensor Actuator Gateway

Data Aggregation Producer Consumer

Service App

Context processing & storage

Smart Things

Mobility & Security Security

IoT Middleware

App Service Discovery Self Clustering/Organization

WINLAB

ICN-IoT System Architecture

…

…...

Sensors/Actuator/Smart devices  Data signal generation

 Key pre-distribution  Energy mgmt

IoT Aggregator (e.g. Raspberry Pi, Smart Phone)

 Data collection  Data filtering, grouping and formatting  Device/Service Discovery Service  Device local naming service

Local Service Gateway

 Subscribe to the formatted sensor data  Context data processing& storage  Name Assignment Service  Local/Global ID translation  Sensor data access policy enforcement

ICN Network

IoT Server: Pub/Sub Management, System Monitoring APP—Website, Mobile APP: ICN Data Consumer

Radio-specific Interface Adaptation

ICN Adaptor ZigBee, TO, 6LoWPAN, BLE,etc

ICN Non- ICN ICN ICN- UNI

Edge Service Router Service Controller Edge Service Router Service Provider

ICN-NNI ICN/Non - ICN

Heterogeneous Collector Cluster (e.g., Mote/Receiver/Sensor Router, Nest)

 Context-supervised sensor discovery & clustering

 Data relay with security

Data Center

V2V-ICN ICN IoT Aggregators (e.g. RSU)

A Simulation-Based Comparison of MF-IoT and NDF-IoT

WINLAB

NDN Overview

 Two types of packets



Interest & data

 Three data structure



Forwarding Information Base (FIB)



Pending Interest Table (PIT)



Content Store (CS)

WINLAB

MobilityFirst Overview

IP Hop-by-Hop Block Transfer

Link Layer 1 (802.11) Link Layer 2 (LTE) Link Layer 3 (Ethernet) Link Layer 4 (SONET) Link Layer 5 (etc.)

GSTAR Routing MF Inter-Domain E2E TP1 E2E TP2 E2E TP3 E2E TP4 App 1 App 2 App 3 App 4 GUID Service Layer

Narrow Waist

GNRS MF Routing Control Protocol NCS

Name Certification & Assignment Service Global Name Resolution Service

Data Plane Control Plane

Socket API

Switching Option

Optional Compute Layer Plug-In A

WINLAB

ICN-IoT Use Cases

 Smart Campus  Stationary IoT : Building management system (BMS)

 Control complex ecosystems such as climate control, security

monitoring, smoke detection, etc

 Heterogeneous communication protocols  Complex middleware required

 Dynamic IoT : School Bus System

WINLAB

Building Management System

a

Network MF/NDN Control Service Environment Monitoring Occupancy Monitoring

Fixture /Interface Thermostat /Interface

…........

Sensor

Sink a

Sensor

Sink ……………………

Web Portal

WINLAB

BMS-Evaluation

Sink Router Actuator

1 3 1 4 1 5 1 6 1 7

BMS server

• 1. Based on MF-sim and NDN-sim
• 2. Based on campus building floor plan

WINLAB

BMS-Evaluation

1.Average Data Report Delay On Server

• 2. Average delay from sink to

actuator 4 . Goodput at the server

• 3. Total PIT size in the network

WINLAB

School Bus

• Vehicle to infrastructure (V2I)
• Update sensor data on bus to the server
• Receive notification from the administrator
• Handling Mobility

GPS

Peer Bus(e.g . Route A) Mobile Data Terminal(MDT )

web School Bus Server AP

Location/Se at Sensor data

WINLAB

School Bus Evaluation

Several IoT Systems at Winlab

WINLAB

OWL

WINLAB

Owl Application: Status and notification

WINLAB

Application: Laboratory Animal Monitoring

2015/5/14 Huawei project

MF-IoT Prototype

33

Click-based MF Router

• Storage-aware routing (GSTAR)
• Name resolution server (GNRS)
• Reliable hop-by-hop link transport (Hop)

Android/Linux MF Protocol Stack

• Network API
• Hop
• Dual homing (WiFi/WiMAX)

WiMAX BTS WiFi AP

Native, user-level implementati

• n on Android

runtime

MF Router

MF Router MF Router

WINLAB

37

Questions & Answers