NGMN Verticals Meeting IoT Requirements & Architecture Feb 2016. 3. 7.¢  NGN NGN NGN NGN . WINLAB A

  • View
    2

  • Download
    0

Embed Size (px)

Text of NGMN Verticals Meeting IoT Requirements & Architecture Feb 2016. 3. 7.¢  NGN NGN NGN...

  • 1

    NGMN Verticals Meeting

    IoT Requirements & Architecture

    Feb 29, 2016

    Rutgers, The State University of New Jersey

    www.winlab.rutgers.edu

    Contact: Professor D. Raychaudhuri, Director

    ray@winlab.rutgers.edu

    WINLAB

  • 2

    IoT Devices &

    Applications

  • WINLAB 3

    Ultra-Low Power Active RFID (WINLAB, 2010)

    Micro controller

    Radio

    Battery

    Antenna

    Transmit-Only TO-PIP(2013)

    Classic TelosB (2004)

    • Low-Power “Transmit-Only” Active RFID Technology for IoT applications

  • WINLAB

    Augmented Reality Tags (WINLAB, 2014) • RFID tag + optical detector for head-mounted AR/VR applications

  • WINLAB

    Wireless Smart Meters (Privacy Study, WINLAB 2012)

     Analyzed existing

    meters with USRP

    software radio

     Meters broadcast every 30s

     Significant privacy/security weaknesses as deployed

  • WINLAB

    Pedestrian Safety Services (WINLAB prototype 2015)

    • Warning for distracted pedestrians to look up as

    they walk off from a sidewalk to street

    • Profiles surface gradient using shoe mounted

    inertial sensors

    • Uses the ground profiles to detect transitions from

    sidewalk to street via ramps and curbs Researchers at Rutgers University made an

    Android app that senses when a texting

    pedestrian steps into a street,

    warning the person to look up. Photo:

    Geoffrey A. Fowler/The Wall Street Journal

  • WINLAB

    OWL Platform & Pipsqueak Sensor (WINLAB/InPoint prototype, 2012)

     10+ year ultra-low

    energy wireless sensor

     Reliable delivery in

    challenging radio

    environments

     Multiple sensing

    capabilities

    Owl Platform Software Stack

     Scalable, distributed

    software architecture

     IoT software stack

    targeting data streams

    from wireless sensors

  • WINLAB

    Lab Animal Monitoring Application (Rutgers deployment, 2014)

     9-month installation

     Improved staff

    workflow

     Reduced problem

    response times

     Supportive CMR

    management and

    faculty

     Product

    requirements

    developed

  • WINLAB

    OWL User Interface for Building

    Monitoring Application (WINLAB, 2014)

    2015 Huawei Strategy and Technology

    Workshop

  • 10

    IoT Requirements

  • WINLAB

    IoT Architectural Requirements

    Next-Generation Network

    Related Icons:

    Sensors & Actuators IoT End-Users

    IoT Application Providers

    Device Naming,

    Device to Service

    Binding

    Service

    Subscriptions

    Context Query (Pull)

    (e.g. device type,

    function, location,

    other attributes)

    Pub-Sub Data

    Dynamic Name

    Resolution Multicast Query

    to specified group

    Service

    Discovery

    Service Name

    Advertisements

     Future mobile networks should be designed to natively

    support anticipated IoT communication modes

    http://uxrepo.com/icon/home-by-dripicons https://www.iconexperience.com/o_collection/icons/?icon=industrial_robot&color_style=green_dark_grey https://www.iconexperience.com/o_collection/icons/?icon=industrial_robot&color_style=green_dark_grey https://www.iconexperience.com/o_collection/icons/?icon=industrial_robot&color_style=green_dark_grey https://www.iconexperience.com/o_collection/icons/?icon=industrial_robot&color_style=green_dark_grey https://www.fitbit.com/store http://uxrepo.com/icon/home-by-dripicons

  • WINLAB

    IoT Architectural Requirements

     Scalability  Scale to billions of devices; low control overhead

     Access Technology Neutral  Wireless access (WiFi, 6LoWPAN, LTE, 5G..) as “plug-in”

     Mobility  Device and cloud service mobility

     Device Limitations  Power/BW limited; sleep modes/disconnected operation

     Performance  Low or bounded latency

    Reference: IETF Draft, Feb 2016, Zhang et al, ICN Based Architecture for IoT

  • WINLAB

    IoT Architectural Requirements

    (cont.)

     Naming, Dynamic Name Resolution  Device/application centric, persistent during mobility

     Multicast/Gathercast Modes  Efficient multicast query and aggregated “gathercast” response

     Contextual Message Delivery  IoT devices addressable by context (location, state, etc.)

     Pub/Sub Modes  Support for both push and pull modes for IoT data/control

    Reference: IETF Draft, Feb 2016, Zhang et al, ICN Based Architecture for IoT

  • WINLAB

    IoT Architectural Requirements

    (cont.)

     Security and Privacy  Including support for low-end IoT devices

     Communication Reliability  Application specific (e.g. Health, Transportation)

     Storage and Caching  In-network storage for DTN and content cache services

     Self-Organization & Discovery  Ability to self-organize and discover resources (services/devices) and

    communicate

     Ad hoc and Infrastructure Modes  Seamless transitions between the two worlds

    Reference: IETF Draft, Feb 2016, Zhang et al, ICN Based Architecture for IoT

  • 15

    IoT Architecture

    Considerations

  • 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 in IoT Networks  Overlay Based Unified IoT Solutions (i.e., OpenIoT, AllJoyn)

     Disadvantages

     Lack of naming transparency between systems which hinders efficient data/service

    discovery

     No general purpose network-layer support for essential services such as pub/sub,

    multicast, mobility and context-aware delivery

    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

    Next-Gen Network as 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

    ICNApp

    ICN

    • Next-Gen (Mobile) Network has the potential to enable “flat” IoT solution which

    works across multiple applications, services & access technologies

    • Solutions such as information-centric networks (ICN) have been proposed and

    are currently under evaluation

    NGN

    NGN

    NGN

    NGN

  • WINLAB

    A Typical ICN-IoT System

    …...

    IoT Aggregator (e.g. Raspberry Pi, Smart Phone, nest thermostat)  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:

    MF 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

    Reference: IETF Draft, Feb 2016, Zhang et al, ICN Based Architecture for IoT

  • 20

    MobilityFirst “Named-Object”

    Architecture for 5G/IoT

  • WINLAB

    MobilityFirst Architecture: Key Features

    Routers with Integrated

    Storage & Computing Heterogeneous

    Wireless Access

    End-Point mobility

    with multi-homing In-network

    content cache

    Network Mobility &

    Disconnected Mode

    Hop-by-hop

    file transport Edge-aware

    Inter-domain

    routing

    Named devices, content,

    and context