Supporting a Unified IoT Architecture through Inforamtion-Centric Networking 张燕咏 Yanyong Zhang WINLAB, Rutgers University yyzhang@winlab.rutgers.edu
Introduction
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 Subscribing Publishing IoT Server Publishing IoT IoT Applications Publishing Gateway Internet API IoT Smart Homes Routers Gateway API IoT Smart Healthcare Sensors Gateway API Smart Grid Sensors Sensors WINLAB
ICN-Centric Unified IoT Platform IoT Smart IoT Smart IoT Smart Home Transport Healthcare Management Management Management ICN App Smart Smart Healthcare Home ICN Smart Transport Home -2 App Home -1 App ICN D2D ICN ICN has a potential to enable interaction between Consumers, IoT ASPs, Network Operators ICN potential as Network layer at the edge? WINLAB
ICN-IoT Middleware
A Typical ICN-IoT System Data Center ICN Network Edge Service Edge Service Router Router Service Controller IoT Server ICN-NNI Names and the service types that are exposed to the server Service Subscription memberships Provider Local Service Gateway (e.g., AP, local gateway) Full information of IoT resources in the local networks (including sensor service types) APP — Website, Mobile APP: ICN ICN Data Consumer … IoT Aggregator (e.g. Raspberry Pi, Smart Phone, nest thermostat) Radio-specific Interface Adaptation Basic hardware information for attached sensors ICN ZigBee, TO, Service types of the attached sensors Adaptor 6LoWPAN, BLE,etc Sensor names for ICN-enabled sensors ICN/Non - Information about sensors attached to peer ICN aggregators Non- ICN ICN Sensors (e.g., RFID, temperature sensors) Sensor hardware information Sensor names for ICN-enabled sensors …... WINLAB
Local Interactions in ICN-IoT Objective: Nest thermostat needs temperature readings from multiple temperature sensors ID Service type 2. AG1 requests data from S1 S1 temperature and S2 through AG2 ID Service type S2 temperature AG 1 AG 2 AG2/S1 temperature AG1 thermostat AG2/S2 temperature 3. AG2 returns data to AG1 AG1 thermostat S1 S2 1. S1 and S2 periodically sends sensor data to AG2 WINLAB
Remote Interactions in ICN-IoT Objective: Smartphone (away from home) needs temperature readings from home temperature sensors A: Request B: Data ICN Network A A B Local Service Gateway B has the full information for the local resource A B Smartphone sends request to retrieve the resource: /bob/home/temperature_sensing/1 (resource acquired through the IoT server) 1. Sensors send updates to aggregator WINLAB
ICN- IoT Functionalities IoT Middleware Pub/Sub Management App Service Discovery Context processing & storage Security Data Aggregation Device/App Naming Service Producer Consumer Device/Network Service Sensor Discovery Service App Gateway Self Clustering/Organization Service Actuator Smart Things Optional: In-network FIA Computing (Data Aggregation/Fusion) Network Service ( Unicast, Multicast, Anycast, etc) Name-based Routing Mobility & Security WINLAB
ICN-IoT System Architecture Data IoT Server: Center Pub/Sub Management, System Monitoring ICN Network Edge Service Edge Service Router Router Service Controller ICN ICN-NNI Service ICN- Provider UNI IoT Aggregators V2V-ICN Local Service Gateway (e.g. RSU) Subscribe to the formatted sensor data Context data processing& storage Name Assignment Service Local/Global ID translation Sensor data access policy enforcement APP — Website, Mobile APP: ICN ICN Data Consumer … IoT Aggregator (e.g. Raspberry Pi, Smart Phone) Data collection Radio-specific Interface Adaptation Data filtering, grouping and formatting Device/Service Discovery Service ICN ZigBee, TO, Device local naming service Adaptor 6LoWPAN, BLE,etc ICN/Non - ICN Heterogeneous Collector Cluster (e.g., Mote/Receiver/Sensor Router, Nest) Context-supervised sensor discovery & clustering Non- ICN Data relay with security ICN Sensors/Actuator/Smart devices Data signal generation Key pre-distribution …... Energy mgmt WINLAB
A Simulation-Based Comparison of MF-IoT and NDF-IoT
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 App 1 App 2 App 3 App 4 Socket API Name NCS Certification & Assignment E2E TP1 E2E TP2 E2E TP3 E2E TP4 Service Optional Compute Layer Plug-In A Global Name GNRS Resolution GUID Service Layer Narrow Waist Service MF Routing GSTAR Routing MF Inter-Domain IP Control Protocol Switching Hop-by-Hop Block Transfer Option Link Layer 1 Link Layer 2 Link Layer 3 Link Layer 4 Link Layer 5 (802.11) (LTE) (Ethernet) (SONET) (etc.) Control Plane Data Plane 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 Sensor Sensor a a …………………… Sink Sink Control Service Fixture /Interface Environment …........ Network Monitoring MF/NDN Thermostat Occupancy /Interface Monitoring Web Portal WINLAB
BMS-Evaluation 1. Based on MF-sim and NDN-sim 2. Based on campus building floor plan Sink Router Actuator 1 1 3 4 1 1 5 6 1 7 BMS server WINLAB
BMS-Evaluation 1.Average Data Report Delay On 2. Average delay from sink to Server actuator 3. Total PIT size in the network 4 . Goodput at the server WINLAB
School Bus • Vehicle to infrastructure (V2I) • Update sensor data on bus to the server • Receive notification from the administrator • Handling Mobility GPS Mobile Data Terminal(MDT ) AP Location/Se at Sensor data School Peer Bus Bus(e.g Server . Route A) web WINLAB
School Bus Evaluation WINLAB
Several IoT Systems at Winlab
OWL WINLAB
Owl Application: Status and notification WINLAB
Application: Laboratory Animal Monitoring WINLAB
MF-IoT Prototype Click-based MF Router Android/Linux MF Protocol Stack - Storage-aware routing (GSTAR) - Network API - Hop - Name resolution server (GNRS) - Dual homing (WiFi/WiMAX) - Reliable hop-by-hop link transport (Hop) Native, user-level implementati on on Android runtime WiFi AP MF Router MF Router MF Router Huawei project 2015/5/14 33 WiMAX BTS
Questions & Answers 37 WINLAB
Recommend
More recommend
