onem2m common architecture for iot interoperability … · onem2m common architecture for iot...

oneM2M Common Architecture for IoT interoperability

Dr. Mahdi Ben AlayaFounder & CEO, Sensinov

[email protected]

October 23, 2017

• R&D engineer at LAAS-CNRS laboratory in Toulouse, France.

• Ph.D in IoT system interoperability

• Founder and CEO of Sensinov startup.

• Vice Chairman of oneM2M Testing Group.

• Co-founder and technical manager of the open source project Eclipse OM2M.

Open Source

IoTSolutions

Research Standards

Biography• IoT tutorials in summer schools and

universities worldwide including France, Taiwan, and Korea.

• R&D projects at LAAS-CNRS and Sensinovincluding ITEA2-USENET, ITEA2-A2NETS, H2020-LSP5-AUTOPILOT, ETSI-OSM, and ETSI-SAREF.

• Authored more than 20 refereed publications in international journals and conferences.

• More than 50 contributions to IoT standards.

2

3

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

The evolution of IoT

CommunicationInteroperability

DataInteroperability

SemanticReasoning

IoT vs M2M

M2M as a subset of IoT

• M2M: connects devices, electronic sensors, RFID tags.

• IoT: connects general things, animals, peoples.

M2M as an industrial environment

• M2M: based on industrial protocols, closed solutions.

• IoT: common usage applications, open solutions for mass.

M2M as the kernel of IoT

• M2M: plumbing of IoT, required connectivity for things.

• IoT: depends on M2M, not possible without it.

M2M IoT

IoT

M2M

M2M

IoTAdopted

definition

M2M paradigm

The ability of machines to communicate with other devices without human interventions.

4

Global Internet device installed Base Forecast

5

• 33 Billion Internet Devices By 2020: Four Connected Devices For Every Person In World.

Source: The M2M adoption Barometer 2014, Vodafone

• Energy and utilities leading closely followed by automotive and retails.

6

Adoption of IoT by industry

7Source: Machina Research, 2015

Global IoT Market opportunities

• IoT market opportunity will be reach 4.3 trillion USD by 2024.

*M2M Communications A Systems Approach - 2012 (book)

IoT

VerticalFragmentation

IoT main challenges

vendor-specific solutions, no

interoperability, semantic gap.

IncreasingComplexity

Large number of devices,

Unmanageable, high costs

PowerManagement

Inefficient battery life-

cycles, lack of clean energy.

NetworkMisalignment

Devices behavior differs from

humans: collapse of internet infra.

Security

Weakness in M2M devices, privacy, fraud, cyber attacks.

8

M2M world of connected services

9

• The current marketplace is extremely fragmented, which has increased the R&D cost in each specific domain.

• Current IoT silo model is not an efficient way to communicate, it is a barrier to further development.

• Many vertical IoT solutions have been designed independently and separately for different applications, which impedes large-scale M2M deployment.

IoT market fragmentation

Source: CRYSTAL project/Philips

10

IoT cross-domain interoperability

• Highly fragmented market with small vendor-specific applications.

• Reinventing the wheel: Same services developed again and again.

• Each silo contains its own technologies without interop.

Invert the pipe

• End-to-end platform: common service capabilities layer.

• Interoperability at the level of communications and data.

• Seamless interaction between heterogeneous applications and devices. 11

• 143 organizations around the world are involved in M2Mstandardization according to the Global StandardsCollaboration M2MTask Force.

M2M

Buildings

EnergyConsumer

Health careIndustrial

TransportationRetail Security

Standards landscape for IoT

12

IoT Interoperability potential impact

Source: McKinsey Global Institute

http://www.etsi.org/technologies-clusters/technologies/m2m

IoT high level architecture

14

Standards for Wide Area Networks(3GPP, fixed NW, WiMax…):Target: protect networks against negative effects of M2M traffic (many devices, non-human traffic …)

Standards for Wide Area Networks

http://www.etsi.org/technologies-clusters/technologies/m2m15

Standards for Local Area Networks (ZigBee, Bluetooth, PLC, etc.)Target: foster use of LAN technology by supporting diverse ecosystem of service providers and device manufacturers.

Standards for M2M Area Networks


Standards for vertical Industries applicationsTarget: enable interoperable, cost-efficient Solutions.

Standards for vertical industries


Standards for M2M service capabilities

http://www.etsi.org/technologies-clusters/technologies/m2m

Standards for M2M Service capabilities:Target: end-to end enablement across servers, gateways, and devices.Standardized service interfaces.

18

oneM2M: The Partnership Project

19

Over 200 member organizations in oneM2M

20

oneM2M organization and Structure

oneM2M certification

oneM2M liaisons

23

PurposeTo specify and promote an

M2M Common Service Layer

WorkSix physical 1-week meetings per year

About 5 conference calls per week between the meetings200+ documents produced and discussed at each meeting

3800 docs in 2013 4200 docs in 2014

DeliverablesTechnical Reports and Technical Specifications

Purpose, Work & Deliverables

24

25

Use Cases & Requirements

Industry

Public ServicesEnterprise HealthcareEnergy

TransportationOtherResidential

REQUIREMENTSTS-0002

TECHNICAL SPECSTECHNICAL REPORTS

ServiceComponents

TS-0007

MQTT ProtocolBinding

TS-0010

Service LayerCore Protocols

TS-0004

FunctionalArchitecture

TS-0001

Definitions& Acronyms

TS-0011

Requirements

TS-0002

26

Technical Specifications

ManagementEnablnt - BBF

TS-0006

ManagementEnablnt - OMA

TS-0005

CoAP ProtocolBinding

TS-0008

HTTP ProtocolBinding

TS-0009

SecuritySolutions

TS-0003

…

oneM2M high level architecture

UnderlyingNetwork

UnderlyingNetwork

CSE

AE

NSE

CSE

AE

NSE

CSE

AE

NSENSE

Device Gateway Server

ApplicationLayer

ServiceLayer

NetworkLayer

Mca

Mcn

Mca Mca

McnMcnMcnMcc Mcc

Entities: AE (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity)

Reference Point: One or more interfaces - Mca, Mcn, Mcc and Mcc’

CSE

Mcc’

OtherServer

27

MN Node

MN-AE

REG

SEC RF

ASM

CMDHGMG

LOC

SUB

MN-CSE

ASN-AE

ASN-CSE

IN Node

IN-AE

Security(SEC)

Data Mgmt and Repository (DMR)

RoutingFunction

(RF)

Application and Service Layer Mgmt (ASM)

Communication Mgmt & Delivery Handling (CMDH)

Location(LOC)

Subscription and Notification

(SUB)

Registration(REG)

IN-CSE

ADN Node

ASNNode

Non oneM2M

Nodes

ADN-AE

ADN Node

ADN-AE

OtherMN Node

oneM2M functional architecture

Group Management

(GMG)

OtherIN Node

DMR

REG

SEC RF

ASM

CMDHGMG

LOC

SUB

DMR

IN-NSE

MN-NSE

ASN-NSE

28

29

OneM2M resource structure

OneM2M Resource structure

Resource type representation

Mgmt ObjectPolling Channel

Application Entity

Access Control Policy

Node

30

oneM2M resource types

SubscriptionGroupContent Instance

Container

Remote CSECse BASE

…

MN-CSE-HOME

AE-SMART-METER

CIN-MEASUREMENT_3

CNT-DATA

CIN-MEASUREMENT_2

CIN-DESCRIPTION_1

CNT-DESCRIPTOR

Server/Cloud(IN-CSE)

Smart Meter(ADN)

End user(DA)

Gateway (MN-CSE)

CIN-MEASUREMENT_1

oneM2M resource tree example

CseBase

Application Entity

Container

Content Instance

Resource Type

31

Interworking with non oneM2M devices

• The Interworking Proxy Entity (IPE) abstracts and maps the non-oneM2M data model to the oneM2M resources.

• Bidrectional communication between the oneM2M system and a specific technology (Monitor and Control).

• Seamless interaction between applications and devices using the oneM2M Restful API.

Zigbee Zwave

Modbus

Canbus

Enocean

LWM2M

OIC

AllJoin

Others

KNX

LORA

InterworkingProxy Entity

CSE

Non oneM2M entities oneM2M entities

oneM2M resources

32

oneM2M addressing mode

Unstructured address (flat, short)• CSE-Relativehttp://127.0.0.1:8080/container-id

• SP-Relativehttp://127.0.0.1:8080/~/cse-id/container-id

• Absolute http://127.0.0.1:8080/_/sp-id/cse-id/container-id

Structured address (hierarchical, long)• CSE-Relativehttp://127.0.0.1:8080/cse-name/ae-name/container-name

• SP-Relativehttp://127.0.0.1:8080/~/cse-id/cse-name/ae-name/container-name

• Absolute http://127.0.0.1:8080/_/sp-id/cse-id/cse-name/ae-name/container-name

CSE

AE

Container

33

34

Blocking requests

Accessing resources in oneM2M(Blocking)

35Non blocking synchronous requests

Accessing resources in oneM2M(Non blocking Synchronous)

36

Non blocking asynchronous requests

Accessing resources in oneM2M(Non blocking asynchronous)

• App-ID uniquely defines the application running in the oneM2M environment

• AE-ID uniquely defines the INSTANCE of the application running in the oneM2M environment

App-ID vs AE-ID

37

• App-ID registry: uniquely identifying applications is necessary in an interconnected world

App-ID Registry to avoid App-ID collision

38

https://appid.iconectiv.com

Access to App-ID Registry

39

Summary of release 2 & 3 features

40

oneM2M implementations

Open source

Commercial & Demo (Non exhaustive)

41

oneM2M scenarios

• Scenario 1 - Nodes mutual authentication and applications registration

• Scenario 2 - Retrieve data from smart meter

• Scenario 3 - Get notified when new metering data is created

• Scenario 4 - Get notified when new smart a meter is registered

• Scenario 5 - Store smart meter data remotely using announcement

42

Scenario 1Nodes mutual authentication and applications

registration

43

ASN-CSECseBase-SmartMeter

ASN-AE

mca

mcc

SmartMeterDevice

Initial state

Scenario 1

IN-CSECseBase-MeteringServer

IN-AE

mca

Smart Metering

Server

44

Scenario 1


ASN-AE

mca

mcc

SmartMeterDevice

IN-CSE

IN-AEAE-PowerProcessing

AE-PowerProcessing

Smart Metering

Server

POST

mca

CseBase-MeteringServer

Step 1- AE-PowerProcessing Registers to the Metering Server IN-CSE 45

ASN-CSE IN-CSE

ASN-AE

mca

mcc

mca

SmartMeterDevice

Smart Metering

Server

RemoteCSE-SmartMeter

POST

Scenario 1

AE-PowerProcessing


CseBase-MeteringServerCseBase-SmartMeter

Step 2- The Smart Meter ASN-CSE registers to the Metering Server IN-CSE 46

ASN-CSE IN-CSECseBase-SmartMeter

ASN-AE

mca

mcc

mca

RemoteCSE-MeteringServer

SmartMeterDevice

Smart Metering

Server


Scenario 1

AE-PowerProcessing



Step 3- The Smart Meter ASN-CSE Creates locally RemoteCSE-MeteringServer resource 47

ASN-CSE IN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

Smart Metering

Server

POST

Scenario 1

CseBase-SmartMeter




AE-SmartMeter

mca

mcc

mca


AE-PowerProcessing

Step 4- AE-SmartMeter registers to the Smart Meter ASN-CSE 48

Scenario 2Retrieve data from smart meter

49

ASN-CSE IN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

Smart Metering

Server

Scenario 2

CseBase-SmartMeter




AE-SmartMeter

mca

mcc

mca


AE-PowerProcessing

Initial state 50

ASN-CSE

ASN-AE

mca

SmartMeterDevice

POST

Scenario 2

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power

Step 1- AE-SmartMeter Creates Container-Power sub-resource 51

ASN-CSE

ASN-AE

mca

SmartMeterDevice

POST

Scenario 2

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power

ContentInstance-Power

Step 2- AE-SmartMeter creates ContentInstance-Power sub-resource 52

ASN-CSE

ASN-AE

mca

SmartMeterDevice

Scenario 2

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power


GET

GET

Step 3- AE-PowerProcessing retrieves the ContentInstance-Power resource 53

Scenario 3Get notified when new metering

data is created

54

ASN-CSE

ASN-AE

mca

SmartMeterDevice

Scenario 3

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power

Initial state 55

ASN-CSE

ASN-AE

mca

SmartMeterDevice

Scenario 3

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power

POST

POST

Subscription-Power

Step 1- AE-PowerProcessing subscribes to Container-Power of AE-SmartMeter 56

ASN-CSE

ASN-AE

mca

SmartMeterDevice

Step 2- AE-SmartMeter creates ContentInstance-Power. AE-PowerProcessing is notified.

Scenario 3

IN-CSE

Smart Metering

Server



mca

mcc

CseBase-SmartMeter

AE-SmartMeter


AE-PowerProcessing

AE-SmartMeter


Container-Power

Subscription-Power

POST

POST

PO

ST


57

Scenario 4Get notified when new smart a meter is

registered

58

Scenario 4


ASN-AE

mca

mcc

SmartMeterDevice

IN-CSE


Smart Metering

Server

mca


Initial state

AE-PowerProcessing

59

Scenario 4


ASN-AE

mca

mcc

SmartMeterDevice

IN-CSE


Smart Metering

Server

POST

mca


Step 1- AE-PowerProcessing creates Subscription-devices resource to get notified of new meters

Subscription-remoteCSE

AE-PowerProcessing

60

ASN-CSE IN-CSE

ASN-AE

mca

mcc

mca

SmartMeterDevice

Smart Metering

Server

POST

Scenario 4


CseBase-SmartMeter

Step 2- The Smart Meter registers to the Metering Server. AE-PowerProcessing is notified



AE-PowerProcessing


PO

ST

61


ASN-AE

mca

mcc


SmartMeterDevice

Scenario 4

Step 3- The Smart Meter ASN-CSE Creates locally RemoteCSE-SmartMeter resource

IN-CSE

mca

Smart Metering

Server




AE-PowerProcessing


62

Scenario 5Store smart meter data remotely using

announcement

63

IN-CSE

mcc

mca

Smart Metering

Server

Scenario 5


Initial state



AE-PowerProcessing


ASN-CSE

ASN-AE

SmartMeterDevice

CseBase-SmartMeter


mca

64

IN-CSE

mcc

mca

Smart Metering

Server


Step 1- AE-SmartMeter registers to the Smart Meter ASN-CSE with announcement.



AE-PowerProcessing


ASN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

POST

CseBase-SmartMeter


AE-SmartMeter

mca

POST

AE-SmartMeter-Announced

Scenario 5

65

IN-CSE

mcc

mca

Smart Metering

Server

Scenario 5


Step 2- AE-SmartMeter remotely creates Container-Power on AE-SmartMeter-Announced



AE-PowerProcessing


ASN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

POST

CseBase-SmartMeter


AE-SmartMeter

mca

POST


Container-Power

66

IN-CSE

mcc

mca

Smart Metering

Server

Scenario 5


Step 3- AE-SmartMeter creates remotely ContentInstance-Power



AE-PowerProcessing


ASN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

POST

CseBase-SmartMeter


AE-SmartMeter

mca

POST


Container-Power


67

IN-CSE

mcc

mca

Smart Metering

Server

Scenario 5


Step 4- AE-PowerProcessing retrieves the ContentInstance-Power resource direcly from IN-CSE



AE-PowerProcessing


ASN-CSE

ASN-AEAE-SmartMeter

SmartMeterDevice

CseBase-SmartMeter


AE-SmartMeter

mca


Container-Power


GET

68

Thank you for your Attention

[email protected]

69

onem2m common architecture for iot interoperability … · onem2m common architecture for iot...

Documents