OVERVIEW OF ETSI M2M ARCHITECTURE Presented by: Barbara Pareglio, Ericsson. ETSI All rights reserved

Size: px

Start display at page:

Monica Wood
10 years ago
Views:

2 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 network Facilitate deployment of vertical applications Facilitate innovation across industries by exposing data and information and providing services. 2

underlying network Facilitate deployment of vertical applications Facilitate

3 M2M High Level Architecture M2M Device & Gateway Domain M2M Network Domain M2M Device M2M Gateway WIDE AREA NETWORK M2M App. Device Application (DA) Proprietary M2M Device dia M2M AREA NETWORK Proprietary Interface M2M App. dia M2M Gateway Service Capability (GSCL) M2M Device M2M App. dia WIRELESS MOBILE FIXED mid M2M Service Capabilities Layer (M2M NSCL) mia mia mia M2M Application M2M Application M2M Application REFERENCE POINTS M2M Device Service Capability (DSCL).. OTHER mid Network Application (NA) 3

dia M2M Gateway Service Capability (GSCL) M2M Device M2M App.

4 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 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

contains a resource structure where the information is kept M2M Application and/or M2M Service Capability Layer exchange

5 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 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

management based both on OMA DM (wireless) and BBF TR 69 (wireline) Mutual authentication between Network Service Capability

6 Security R1 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 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

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

7 Example: Connected home Network Application (NA) Wireless or Wired Networks M2M Devices with Device Application (DA) M2M Gateway (GSCL) M2M Network (NSCL)

8 High level deployment M2M Device & Gateway Domain Heating WIDE AREA NETWORK M2M Network Domain Heating App wifi WIRELESS Example NSCL M2M Gateway Washingmachine Washing App dia myhome GSCL MOBILE mid mia SmartHome App FIXED.. OTHER 8

WIRELESS Example NSCL M2M Gateway Washingmachine Washing

9 Flow of events M2M Device & Gateway Domain M2M Network Domain Heating WIDE AREA NETWORK Heating App wifi M2M Gateway WIRELESS Example NSCL Configure & provision Washingmachine Washing App register myhome GSCL MOBILE register register SmartHome App FIXED Configure & provision.. OTHER 9

Configure & provision Washingmachine Washing App register myhome GSCL

10 Network Application registration The Network Application registers to the NSCL Name of the NSCL = examplenscl Network application register with the ID = SmartHome ID examplenscl scls applications SmartHome-ID mgmtobjs containers groups accessrights containers groups accessrights notificationch anel discovery 10

= SmartHome ID examplenscl scls applications SmartHome-ID mgmtobjs containers

11 Gateway registration The gateway (GSCL) registers to the NSCL Name of the NSCL = examplenscl Name of the GSCL = myhomegscl Before registration the GSCL and NSCL are authenticated by means of the M2M Communication procedures examplenscl scls myhomegscl mgmtobjs applications containers groups accessrights containers groups applications accessrights mgmtobjs notificationscha nnel m2mpocs attacheddevices discovery 11

Communication procedures examplenscl scls myhomegscl mgmtobjs applications containers groups

12 Result of Gateway registration As a result of the gateway registration a resource representing the NSCL is created in the GSCL. myhomegscl scls examplenscl containers groups applications accessrights applications containers groups accessrights mgmtobjs notificationscha nnel discovery 12

myhomegscl scls examplenscl containers groups applications accessrights

13 Device applications registration The device Applications register to the GSCL Name of GSCL = myhomegscl Device application heating register with the ID = Heating App ID Device application washing mashing register with the ID = Washing App ID myhomegscl scls applications Heating-App-ID Washing-App-ID containers groups accessrights containers groups accessrights notificationch anel discovery 13

washing mashing register with the ID = Washing App ID myhomegscl scls applications Heating-App-ID

14 What s next 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 information can now be transferred over the mid. 14

GSCL and the applications is setting up the

15 Store information The information from the 2 device applications are stored in the containers in the NSCL examplenscl scls myhomegscl containers heaterinfo washinginfo contentinstances 15

16 Flow of events: add & read data M2M Device & Gateway Domain M2M Network Domain Heating Heating App M2M Gateway Example NSCL add Washingmachine Washing App add myhome GSCL add read SmartHome App 16

17 Flow of events: subscribe & notify M2M Device & Gateway Domain M2M Network Domain Heating Heating App M2M Gateway Example NSCL subscribe Washingmachine Washing App myhome GSCL notify SmartHome App 17

18 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 appliances. 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

that monitors the levels of utilization for each appliances.

19 High level deployment M2M Device & Gateway Domain M2M Network Domain Heating WIDE AREA NETWORK Heating App wifi M2M Gateway WIRELESS Example NSCL Utility App Washingmachine Washing App dia myhome GSCL MOBILE FIXED mid mia SmartHome App Manufacturer App.. OTHER 19

WIRELESS Example NSCL Utility App Washingmachine Washing App dia

20 Questions Contact details: Barbara Pareglio, 20

ETSI M2M application developers guideline

Cod. Doc. TTGSTSPI1300029 ETSI M2M application developers guideline Version: 1.0 Date: 27.05.2013 Privacy: Public Pages: 43 AUTHORS: FIRST APPROVAL: FINAL APPROVAL: Michele LUPANO (T.TG.ST.SPI) Roberto