ONEM2M FOR SMART CITIES - GreenDigitalCharter · Application Entity Provides application logic for...

© 2016 oneM2M

Presenter: Omar Elloumi, oneM2M TP Chair, Nokia Bell-Labs and CTO [email protected]

oneM2M www.oneM2M.org

ONEM2M FOR SMART CITIES

© 2016 oneM2M 2

Outline

• Introduction to oneM2M• IoT technology trends• Role of oneM2M in smart cities• A possible Smart city blue-print• Take-away

© 2016 oneM2M

Over 200 member organizations in oneM2M

oneM2M Partnership Project

www.oneM2M.orgAll document are publically available

© 2016 oneM2M 4

PurposeTo specify and promote an

M2M Common Service Layer

DeliverablesTechnical Reports and Technical Specifications

Purpose & Deliverables

© 2016 oneM2M 5

M2M Common Service Layer in a nutshell

• It is a software layer• It sits between M2M applications and

communication HW/SW that provides data transport

• It normally rides on top of IP• It provides functions that M2M applications

across different industry segments commonly need. Those functions are exposed to Applications via developer friendly APIs.

• It allows for distributed intelligence (device, gateway, cloud apps)

© 2016 oneM2M 6

Industry

Work Process

Public ServicesEnterprise HealthcareEnergy

TransportationOtherResidential

REQUIREMENTSTS-0002

TECHNICAL SPECSTECHNICAL REPORTS

© 2016 oneM2M 7

oneM2M Architecture approach

Pipe (vertical):1 Application, 1 NW,

1 (or few) type of DevicePoint to point communications

Horizontal (based on common Layer)Applications share common service and network infrastructure

Multipoint communications

Local NW

BusinessApplication

Device

CommunicationNetwork (wireline, wireless,

Powerline ..)

Gateway

CommunicationNetwork 1

CommunicationNetwork 2

Local NW

GatewayIP

Application

A

Application Application Application

Common Service Layer

Device Device

Device

AS

AA Device

AS

S Common Service Layer

S

A


A Application

Things

Thingsrepresentations(includingsemantics)

© 2016 oneM2M 8

UnderlyingNetwork

UnderlyingNetwork

AE

NSE

AE

NSE NSENSE

Application Service Node Middle Node Infrastructure Node

ApplicationLayer

NetworkLayer

Architecture

AE

Application Entity Provides application logic for the end-to-end M2M solutions

Network Services Entity Provides services to the CSEs besides the pure data transport

Node Logical equivalent of a physical (or possibly virtualized, especially on the server side) device

© 2016 oneM2M 9

UnderlyingNetwork

UnderlyingNetwork

CSE

AE

NSE

CSE

AE

NSE

CSE

AE

NSENSE

Application Service Node Middle Node Infrastructure Node

ApplicationLayer

ServiceLayer

NetworkLayer

McaMca

McnMcn

McaMca McaMca

McnMcnMcnMcnMcnMcnMccMcc MccMcc

Reference Point One or more interfaces - Mca, Mcn, Mcc and Mcc’ (between 2 service providers)

Common Services Entity Provides the set of "service functions" that are common to the M2M environments

Application Entity Provides application logic for the end-to-end M2M solutions

Network Services Entity Provides services to the CSEs besides the pure data transport

Node Logical equivalent of a physical (or possibly virtualized, especially on the server side) device

Architecture

CSE

Mcc’Mcc’

Inf. Node

© 2016 oneM2M 10

Communication ProtocolsReuse IP-based existing protocols

NB: Interworking with field area protocols and data models (OCF, AllSeen, OMA LWM2M, Zwave, etc)

Service LayerCore Protocols

TS-0004

CoAP MQTT BindingHTTP

XML or JSON Content serialization - HTTP Example

REQUESTGET /~/CSE-178/CSEBase/home/temperature HTTP/1.1Host: provider.netX-M2M-Origin: /CSE-123/WeatherApp42X-M2M-RI: 56398096Accept: application/json

RESPONSEHTTP/1.1 200 OKX-M2M-RI: 56398096X-M2M-RSC: 2000Content-Type: application/vnd.onem2m-res+jsonContent-Length: 101{“m2m:cin”:[

"cnf":"application/json:0","con":"{'timestamp':1413405177000,'value':25.32}"]

}

WebSockets

© 2016 oneM2M 11

Registration Group ManagementSecurityDiscovery

Data Management &

Repository

Application & Service

Management

Device Management

Subscription & Notification

Communication Management

Service Charging & Accounting

LocationNetwork Service

Exposure

Common Service Functions

© 2016 oneM2M 12

Strong implementation baseIndustry-driven Open source implementations

Examples of Commercial implementations /demos

2 interop. events in 2015/2016

With 30 participating organizations and 75 engineers

IotDM

© 2016 oneM2M 13

Ongoing collaborations

Guidelines& Ref. Arch.

Protocols Platforms

MQTT

OMADM LWM2M

HTTP CoAP TLS DTLS

Uses/interworks

uses

usesinterworks with

interworks with

collaborations

Now OCF

© 2016 oneM2M 14

oneM2M release 2 features

Industrial domainenablement

• “Real-time” data collection• redundancy and fault tolerance• enablers for analytics oneM2M

Beyondinitial release

Semantic interoperability• base ontology, link to domain specific ontologies• semantic descriptions• semantic discovery

Dynamic authorizations and end to end security

• device onboardingand provisioning

oneM2M as generic interworking framework

• AllJoyn/AllSeen• OIC• LightWeight M2M (LWM2M)

Home domainenablement

• Home applianceinformation models• ontologies and mapping to existingstandards

Application developer APIs and guidelines

© 2016 oneM2M

IOT TECHNOLOGY TRENDS

© 2016 oneM2M 16

Trend1: horizontalization

BROAD ADOPTION High volume, low ARPC, low TCO

NICHE VERTICALSLow volumes, high ARPC, high TCO

• Devices and Applications are designed as “stove-pipes”• Devices dedicated for single application use• Solutions are closed and not scalable: duplication of

dedicated infrastructure• High development & delivery cost

• Devices and Applications are designed to collaborate across “clouds”

• Devices are used for multiple application purposes• Devices and Applications offering continuously evolve• Easy app development and device integra-tion through

APIs and standard interfaces

Horizontal platform with common functions and interfaces

Source: Alcatel-Lucent

© 2016 oneM2M 17

Trend 2: softwarization

Source: ITU-T Focus Group IMT2020

© 2016 oneM2M 18

Trend 3: connectivity, plenty to chose from

Range (extended)

Range (low)

Device cost (high)Bitrate (high)

WLAN(e.g. 802.11)

Native Low Power Wide-area Access

Device cost (low)Bitrate (low)

3GPP Cellular(GSM/LTE)

NB-IoT, CIoT, etc.

WPAN(e.g. 802.15.4, DECT

ULE)

Source AIOTI, modified from an ALU contribution

© 2016 oneM2M 19

Trend 4: Semantic interoperability

Source: sensinov

19

All monuments are described on

the web.

Brochure web site

Sent packagesare tracked on

the web

Take the world online

Plants action a tap to water themselves.

Let the things talk to each others

Monitor and control home appliances.

Take the control of the world

Alarm ring earlier in case of traffic or bad

weather.

Let Things becomeintelligent

CommunicationInteroperability

DataInteroperability

SemanticReasoning

© 2016 oneM2M

ROLE OF ONEM2M IN SMART CITIES

© 2016 oneM2M 21

Vision for building smart cities

2. Digitalize and «sensorise»

4. Expand the vision, Integrate

and Innovate

3. Build Dashboards

1. Build a vision

Source: Based on discussions with Dr. Martin Serrano, OASC and Insight centre

© 2016 oneM2M 22

NG-NBN National Fiber

Network

WirelessNational WiFi

Network

Deploy an “operating system” accessible by all

stakeholders

Generalized Heterogeneous Network to boost Citizen

Quality of Services

Deploy sensors using Above Ground Boxes for electricity

& connectivity

CONNECT

COLLECT & COMPREHEND Sustain livability and position Singapore as a

(regional) Digital Harbor to drive economic growth.

0,0

1,0

2,0 1,73

1,1 1,1 1,2 1,2 1,2 1,3

1,8

Singapore Government ICT Investmentin BSGD (1SGD = 0.65Euro)

Source:IDA 2014

Past In Progress Future

Example - Singapore “Smart Nation” initiative: Anticipation, Vision and Execution

© 2016 oneM2M 23

Integration challenge

Source: CRYSTAL project/Philips

Platform based integrationBased on open standards

Home Energy HealthAutomotive

Communication Devices & Hardware

Communication Technologies & Protocols


Communication Networks

AutomotiveApplications

HomeApplications

EnergyApplications

e-HealthApplications

© 2016 oneM2M 24

Semantic interop challenge

Common Service layer

things Things representation

Data (e.g. temperature)

Metadata

Semantic description

Other metada (e.g. digital right

management and privacy related)

instantiates

ontology

represents

Discovery – Consistency – Scalability - Efficiency

Source: AIOTI

© 2016 oneM2M 25

It’s not about the technology!• Ontology-driven approaches provides a lower costs when

dealing with high number of data sources.• It ensure interoperability for open and big environments.

Source: Price Waterhouse Cooper

© 2016 oneM2M 26

Innovation challenge

How do I address the needs of app developers

• App developers focus on app logic: use of Restful APIs

• Hide WAN and Area Network technologies specificities (interworking exposed as a service by the platform)

• Free access to city open data– Controlled access to other data

© 2016 oneM2M 30

Key requirements for smart city IoT platform

Horizontal platform for new deployments

• Smart city is an incremental and participatory journey• New deployments should, where possible, leverage a converged networks and an horizontal service platform• Open standards are key to avoid lock-in and master the total cost of ownership

Existing deployments

• Do not disrupt existing “vertical deployment” but seek opportunities for an integration path with an horizontal approach• Build value through smash-ups and open data

Participatory and innovativeapproach

• Surveys• Address needs for innovation through app development:

• APIs• Access to, eventually semantically enriched, Open data (where feasible and subject to privacy legislation/citizen consent)

Security and (device) management are key

• Despite initial focus on IoT data, there is an increased interest in security and device management (which go hand in hand).• Need arises from security threat analysis conducted recently: e.g. ”Two researchers analyzed Smart meters widely used in Spain and discovered that can be hacked by attackers to harm the overall National power network.”, source: http://securityaffairs.co/wordpress/29353/security/smart-meters-hacking.html

© 2016 oneM2M 31

App

D

App

D

App

DD

DD

DD

D

ExistingdeploymentsAdapter

Open data (Semantics)

BrokerBroker

Adapter

Smart city backendBig Data Storage

CloudVM Mgmtg

DataMgmt

Big Data enablers

Smart city frontend

DeviceGatewayGatewayField domain

Data center

I/F to otherIoT platforms

Device mgmt

DeviceInterwor

king

Discovery

Location

Group mgmt

Security

Other datasources

LWM2M

City AppsCity

Apps3rd party

apps3rd party

appsAnalytics

appsAnalytics

apps

REST APIs

SPARQL orREST APIs

REST APIs

3rd party apps

3rd party apps

City AppsCity

AppsAnalytics

appsAnalytics

appsDashboards

Dashboards

Cloud appsA possible smart city blue-print

© 2016 oneM2M 32

Design Principles• Frontend/backend scale

differently.• Frontend designed for massive

secure connections to devices/apps, dev mgmt, interworking, protocol adaption

• Backend about data functions: replication, anonymization, VM management, availability etc.

• Semantic engine is about metadata to enrich data sets, reasoning: fast track for integration and analytics

• Build value for existingapplication through adapters

• Open APIs and open data are keyfor innovation

• I/F to other platforms: utility, automotive (autonomousdriving), etc.

© 2016 oneM2M 34

Take-away• City

– Every city is unique– Build a vision: initial set of use cases– Build an architecture that leverages cross sector

applications using open standards– Integrate existing deployments– Stimulate and cultivate a collaborative culture for

innovation

• oneM2M provides a fast-track and future proof IoTbased smart city – complementary standards and open source are needed

ONEM2M FOR SMART CITIES - GreenDigitalCharter · Application Entity Provides application logic for...

Documents

Transcript of ONEM2M FOR SMART CITIES - GreenDigitalCharter · Application Entity Provides application logic for...