+ All Categories
Home > Documents > Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM...

Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM...

Date post: 19-Jan-2021
Category:
Upload: others
View: 1 times
Download: 0 times
Share this document with a friend
20
OVERVIEW OF ETSI M2M ARCHITECTURE Presented by: Barbara Pareglio, Ericsson © ETSI 2011. All rights reserved October 2011
Transcript
Page 1: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

OVERVIEW OF ETSI M2M ARCHITECTURE Presented by:

Barbara Pareglio, Ericsson

© ETSI 2011. All rights reservedOctober 2011

Page 2: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Why ETSI M2M ?

Provide an M2M architecture with a generic

set of capabilities for M2M services

Provide a framework for developing services

independently of the underlying networkindependently of the underlying network

Facilitate deployment of vertical applications

Facilitate innovation across industries by

exposing data and information and providing

services.

2

Page 3: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

M2M M2M –– High Level ArchitectureHigh Level Architecture

M2M Service Capabilities Layer (M2M

NSCL)

M2M GatewayM2M Device

WIRELESSM2M

AREA

NETWORK

M2M Gateway

WIDE AREA NETWORK

mIddIa dIa mIa

M2M App. M2M App.

M2M

Application

M2M Network DomainM2M Device & Gateway Domain

NSCL)

M2M Device Service

Capability (DSCL)

M2M Device

MOBILE

FIXED

.. OTHER

M2M Gateway Service

Capability (GSCL) M2M

Application

M2M

Application

Proprietary

M2M Device

mId

mId

3

mIa

dIa

mIaM2M App.

REFERENCEREFERENCE POINTSPOINTS

Network Network

ApplicationApplication

(NA)(NA)

Device Device

ApplicationApplication

(DA)(DA)

Page 4: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

M2M architecture

ETSI M2M adopted a RESTful architecture style

• Information is represented by resources which are structured as a tree

ETSI M2M standardizes the resource structure that resides on

an M2M Service Capability Layer (SCL)

• Each SCL contains a resource structure where the information is kept• Each SCL contains a resource structure where the information is kept

M2M Application and/or M2M Service Capability Layer

exchange information by means of these resources over the

defined reference points

ETSI M2M standardizes the procedure for handling the

resources

4

Page 5: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Features offered by ETSI M2M

Identification of the M2M Application and the M2M Devices

Asynchronous and synchronous communication

Store and forward mechanism based on policies for optimising the communication

Location information

Device management based both on OMA DM (wireless) and Device management based both on OMA DM (wireless) and BBF TR-69 (wireline)

Mutual authentication between Network Service Capability Layer and Device/Gateway Service Capability Layer that are connected

Secure channel for transporting data over mId reference point

And much more ….

5

Page 6: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Security

ETSI M2M Release 1 provides standardized security mechanism for the reference point mId

The device/gateway needs to have keys for securing the connection.

The device/gateway is provisioned with the key M2M The device/gateway is provisioned with the key M2M Root Key.

The high level procedure are to • Perform mutual mId end point authentication

• Perform M2M Connection Key agreement

• Optionally establish a secure session over mId.

• Perform RESTful procedures over the mId

6

Page 7: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Example:

Connected home

Network Application

(NA)

Wireless or Wired Networks

M2M Network (NSCL)

M2M Gateway (GSCL)

M2M Devices with

Device Application

(DA)

Page 8: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

High level deployment

Example NSCL

M2M Gateway

WIRELESSwifi

WIDE AREA NETWORKHeating

Heating App

M2M Network DomainM2M Device & Gateway Domain

dIaMOBILE

FIXED

.. OTHER

myHome GSCL

mIdmIa

8

SmartHome

AppWashing-

machine

Washing App

Page 9: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Flow of events

Example NSCLM2M Gateway

WIRELESSwifi

WIDE AREA NETWORK

Configure& provision

Heating

Heating App

M2M Network DomainM2M Device & Gateway Domain

MOBILE

FIXED

.. OTHER

myHome GSCL

9

register

register

register

Washing-

machine

Washing App

SmartHome

App

Configure&

provision

Page 10: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Network Application registration

The Network

Application registers

to the NSCL

• Name of the NSCL =

exampleNSCL

exampleNSCL

applications

scls

SmartHome-ID

• Network application

register with the ID =

SmartHome-ID containers

groups

accessRights

subscriptions

discovery

subscriptions

mgmtObjs

10

containers

groups

accessRights

subscriptions

notificationChanel

Page 11: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Gateway registration

The gateway (GSCL)

registers to the NSCL

• Name of the NSCL =

exampleNSCL

• Name of the GSCL =

myHomeGSCL

exampleNSCL

scls

subscriptions

myHomeGSCL

containers

groups

applications

accessRightsmyHomeGSCL

Before registration

the GSCL and NSCL

are authenticated by

means of the M2M

Communication

procedures

applications

containers

groups

accessRights

subscriptions

discovery

mgmtObjs

11

accessRights

subscriptions

mgmtObjs

notificationsChannel

m2mPocs

attachedDevices

Page 12: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Result of Gateway registration

As a result of the

gateway registration

a resource

representing the

NSCL is created in the

myHomeGSCL

scls containers

exampleNSCLgroups

applicationssubscriptions

NSCL is created in the

GSCL. accessRights

subscriptions

mgmtObjs

notificationsChannel

subscriptions

12

applications

containers

groups

accessRights

subscriptions

discovery

Page 13: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Device applications registration

The device

Applications

register to the GSCL

• Name of GSCL =

myHomeGSCL

myHomeGSCL

applications

scls

Heating-App-ID

• Device application

heating register

with the ID =

Heating-App-ID

• Device application

washing-mashing

register with the ID

= Washing-App-ID

containers

groups

accessRights

subscriptions

discovery

Washing-App-ID

subscriptions

13

containers

groups

accessRights

subscriptions

notificationChanel

Page 14: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Appropriate access rights needs to be set up.

• For example the network application that knows the

GSCL and the applications is setting up the

accessRights

What’s next ?

accessRights

information can now be transferred over the

mId.

14

Page 15: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Store information

The information

from the 2 device

applications are

stored in the

containers in the

exampleNSCL

scls

myHomeGSCL

15

containers in the

NSCLcontainers

heaterInfo

washingInfo contentInstances

subscriptions

Page 16: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Heating

Heating App

Flow of events: add & read data

Example NSCL

M2M Gateway

M2M Network DomainM2M Device & Gateway Domain

SmartHome

AppWashing-

machine

Washing App

myHome GSCL

16

read

add

add

add

Page 17: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Flow of events: subscribe & notify

Example NSCL

M2M Gateway

Heating

Heating App

M2M Network DomainM2M Device & Gateway Domain

SmartHome

AppmyHome GSCL

17

subscribe

notify

Washing-

machine

Washing App

Page 18: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

What if …

A new Network Application would like to reuse some of the

data produced?

• For example the device manufacturer that controls the performance

and status of the device

• The utility company that monitors the levels of utilization for each

appliancesappliances

• ….

All you need to do is to develop the Network Application and

• Ask the “owner” of the information to give you read permission by

updating the access right

• Retrieve the information and consume it

18

Page 19: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

High level deployment

Example NSCL

M2M Gateway

Heating

WIRELESSwifi

WIDE AREA NETWORK

Utility

App

Heating App

M2M Network DomainM2M Device & Gateway Domain

dIaMOBILE

FIXED

.. OTHER

myHome GSCL

SmartHome

App

Washing App

Washing-

machinemId

mIa

19

Manufacturer

App

Legacy area

network

Interworking

Page 20: Presented by: Barbara Pareglio, Ericsson October 2011...Device management based both on OMA DM (wireless) and BBF TR-69 (wireline) Mutual authentication between Network Service Capability

Questions

20

Contact details:

Barbara Pareglio,

[email protected]


Recommended