© 2017 oneM2M

Presenter: Omar Elloumi, oneM2M TP Chair, Nokia Bell-Labs and CTO groupomar.elloumi@nokia.com

oneM2M www.oneM2M.org

WORKSHOP ON FUTURE PROOF SMART CITIES WITH COMMON SERVICE LAYER

© 2017 oneM2M 2

Outline

• Introduction to oneM2M

• Role of oneM2M in smart cities

• A possible Smart city blue-print

• Take-away

© 2017 oneM2M

Over 200 member organizations in oneM2M

oneM2M Partnership Project

www.oneM2M.orgAll document are publically available

© 2017 oneM2M 4

Industry

Work Process

Public ServicesEnterprise HealthcareEnergy

TransportationOtherResidential

REQUIREMENTSTS-0002

TECHNICAL SPECSTECHNICAL REPORTS

© 2017 oneM2M 5

Ongoing collaborations

Interoperability standards

Protocols Platforms

MQTT

OMADM LWM2M

HTTP CoAP TLS DTLS

Uses/interworks

uses

usesinterworks with

interworks with

collaborations

Now OCF

P2413

Guidelines& Ref. Arch.

© 2017 oneM2M 6

Strong implementation base

Industry-driven Open source implementations

Examples of Commercial implementations /demos

2 interop. events in 2015/2016

With 30 participating organizations and 75 engineers

IotDM

© 2017 oneM2M 7

oneM2M Architecture approach

Pipe (vertical):1 Application, 1 NW,

1 (or few) type of Device

Point 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

Common Service Layer

A Application

Things

Thingsrepresentations(includingsemantics)

© 2017 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

© 2017 oneM2M 9

UnderlyingNetwork

UnderlyingNetwork

CSE

AE

NSE

CSE

AE

NSE

CSE

AE

NSENSE

Application Service Node Middle Node Infrastructure Node

ApplicationLayer

ServiceLayer

NetworkLayer

Mca

Mcn

Mca Mca

McnMcnMcnMcc Mcc

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’

Inf. Node

© 2017 oneM2M 11

RegistrationGroup

ManagementSecurityDiscovery

Data Management &

Repository

Application & Service

Management

Device Management

Subscription & Notification

Communication Management

Service Charging & Accounting

LocationNetwork Service

Exposure

Common Service Functions

© 2017 oneM2M 12

oneM2M release 2 features

Industrial domainenablement

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

oneM2MBeyond

initial 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

© 2017 oneM2M

ROLE OF ONEM2M IN SMART CITIES

© 2017 oneM2M 14

Standards for Smart CityShould cities worry?

Source: STF505 based on ETSI TR 103 375 • Do we lack standards for smart cities? What are the gaps?

• IoT common and platform standards are generally applicable to Smart Cities

• Smart cities enabled IoT platforms are generally about cross domain and big (incl. open) data

• Several standards exists for, e.g.:– Street light:

– Water mgmt:

© 2017 oneM2M 15

Where do we stand?Three routes to smart cities:

(source The Smart City Playbook, Machina research 2016)

• The ‘Anchor’ route: vertical stand-alone applications

• The ‘beta city’ route: build hands-on experience through pilot programs which may lead to operational deployments

• The platform route: network infrastructure and IoT platform as a step preceding onboarding new applications

© 2017 oneM2M 16

Key findings/trends«City 2.0»

• Smart city platforms bring significant efficiencies when the number of applications grows– Shared data

– Single API set and data formats are beneficial for developers

• Initial cost of platform investment tends to be marginal compared to economies of scale, OPEX options can alleviate initial costs

• Connectivity, plenty to chose from

• Machine learning and analytics create great benefits (e.g. traffic management, parking management)

• Living labs for research and innovation

• Open standards are crucial for sustainable success

© 2017 oneM2M 17

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

© 2017 oneM2M 18

Integration challenge

Source: CRYSTAL project/Philips

Platform based integration

Based on open standards

Home Energy HealthAutomotive

Communication Devices & Hardware

Communication Technologies & Protocols

Common Service Layer

Communication Networks

AutomotiveApplications

HomeApplications

EnergyApplications

e-HealthApplications

© 2017 oneM2M 19

Semantic interop challenge

Common Service layer

thingsThings 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

© 2017 oneM2M 20

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

© 2017 oneM2M 21

oneM2M based smart city deployment example - Busan

Source: SKT

© 2017 oneM2M 22

oneTransport

Source: Interdigital

© 2017 oneM2M

A POSSIBLE SMART CITY BLUE-PRINT

© 2017 oneM2M 24

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

© 2017 oneM2M 25

App

D

App

D

App

DD

DD

DD

D

ExistingdeploymentsAdapter

Open data (Semantics)

Broker

Adapter

Smart city backendBig Data Storage

CloudVM Mgmt

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 Apps

3rd party apps

Analyticsapps

REST APIs

SPARQL orREST APIs

REST APIs

3rd party apps

City Apps

Analyticsapps

DashboardsDashboards

Cloud appsA possible smart city blue-print

© 2017 oneM2M

TAKE AWAY

© 2017 oneM2M 27

Take-away

• City

– Every city is unique

– Build a vision: initial set of use cases

– Build an architecture that leverages cross sectorapplications 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

© 2017 oneM2M 28

Take-away

• Cities need open standards to avoid lock-in to a platform or a cloud provider

– It is also a matter of national sovereignty

– However oftentimes they do not have enough resources for ensuring this objective, therefore guidance will be beneficial

• Multiple standards exist for connectivity/proximity networks and specific vertical

– Therefore one need to be careful when comparing standards

– From this perspective oneM2M is the only standard that addresses cross domain and cloud wide IoT data communications, it is also applicable for device and gateway nodes

• Another challenge is making the platform cloud native– This is one area of differentiation

– Cloud native means: High throughput, low latency, no single point of failure, horizontal scalability, micro services, DevOps, multitenancy, no dependency on a specific cloud provider, etc.

• The debate about which platform standards is largely distracting the stakeholdersfrom the real value of IoT: data – Cloud native IoT along with REST APIs help in building a data economy