ETSI M2M Architecture Introduction
A brief overview for Release 1 and Release 2Presented by Barbara Pareglio , on behalf of Paul Russell, ETSI TC M2M WG2 Chair
ETSI M2M Workshop, 24-25 October 2012© ETSI 2012. All rights reserved
Agenda
Overview of ETSI M2M Architecture, Release 1
Resource Tree Structure
Resource Operation Procedures
• Service & Application Registration
• Container, Announce & Discovery• Container, Announce & Discovery
• Subscription and Notification
M2M Device Management
Added features for Release 2
2
ETSI M2M Service Architecture, Release 1
M2M SP-1
M2M Network DomainM2M Device Domain
D’ device
D’ device
Gateway 1dIa
dIa
mId
mIa
M2M SP-2
M2M SP-1
M2M SP-3
D’ device
D’ device
D device
D device
D device
Gateway 2
dIa
dIamId
mId
mId
mId
mIa
mIa
d
dIa
dIa
Basic entities, deployment view
dIa
mIadIa
Application only Service Capability Layer only
Service Capability Layer and Application
mId
dIa
D’ Device, Network Application
Network, Gateway, D Device
Gateway, D Device
Basic principles
IP-basedRESTful – resource structure treeSome of the supported features are:• Authentication• Secure communication• Service and Application Registration• Announce and Discovery• Service and Application Registration• Announce and Discovery• Exchange of Information through containers• Subscription and Notification• Group handling• Access Control• Store and Forward• Notification channels• Device Management
“attribute”
<sclBase>
sclsCollection of Remote SCLs that have registered & of SCLs that the
<sclbase> is registered to
1
n
1
1
The main resource tree
applications
containers
groups
accessRights
subscriptions
discovery
Local applications that have registered with the <sclbase>
Collection of containers created by local or remote entities.
Collection of groups that are created and which do not have a containment relation with a specific entity
Collection of accessRights that are created and which do not have a containment relation with a specific entity.
Collection of 0 to n <subscription> resources that represent an individual subscription
Used to perform a discover on <sclbase>
1
1
1
1
1
RESTful Resource Tree
M2M Gateway M2M Server
M2M
Application
M2M
Application
M2M
eHealth / mHealth(Bluetooth / ZigBee…)
Smart Energy(WiFi / ZigBee / …)
M2M Area Network 1
M2M Area Network 2
M2M Applications
M2M Applications M2M Applications
M2M
Application
M2M
Application
Home Automation(ZigBee / Bluetooth / …)
M2M Area Network N M2M Device
M2M Applications
M2M Applications
Resource Tree Overview
Remote SCL registered to this <sclBase>
Active subscriptions
for different
Well-known resource
© ETSI 2011. All rights reserved8
Locally registered
applications
Announced applications
Containers are used to store data; they are at
different locations of the tree for different owners
Groups of resources for
bulk operations
for different resources
Defines access permissions for
different resources
Manage M2M
area networks
Example simplified Resource Tree on NSCL
© ETSI 2011. All rights reserved9
M2M Service & Application Registration
M2M Gateway (GSCL)
M2M Network (NSCL)
M2M Device (DA)
Network Application
(NA)
mIamIddIa
NSCL initiated; created NSCL resource tree root and its child resources
<exampleNSCL>/…
GSCL initiated; created GSCL resource tree root and its child resources<myHomeGSCL>/…
GSCL Registers to NSCL
Secure M2M service bootstrap and connection
Responses Responses not shown
for simplicity
NA Registers to NSCL
(CREATE)DA Registers to GSCL
(CREATE)
Created resource for NA registration
<exampleNSCL>/applications/SmartHome-ID
GSCL Registers to NSCL
(CREATE)
Created resource for GSCL< exampleNSCL>
/scls/<myHomeGSCL>
Created counterpart resource for NSCL
<myHomeGSCL>/scls/<exampleNSCL>
Created resource for DA registration
<myHomeGSCL>/applications/Heating-
App-ID
10
Write Data to Containers, Announce and Data
Retrieval
M2M Gateway (GSCL)
M2M Network (NSCL)
M2M Device (DA)
Network Application
(NA)
mIamIddIa
DA writes data to GSCL container (CREATE)
Created resource for DA data
DA CREATE its container in GSCL
Created container resource for DA <myHomeGSCL>/applications/Heatin
g-App-ID/containers/temperature
© ETSI 2011. All rights reserved11 © ETSI 2011. All rights reserved
Created resource for DA data<myHomeGSCL/applications/Heating-App-
ID/containers/temperature/contentInstances/myHomeTemp1
GSCL AnnouncesDA to NSCL (CREATE)
Created Annc resource for DA in NSCL <exampleNSCL>/scls/<myHomeGSCL>/app
lications/Heating-App-ID-Annc
NA discovers DAUnder <nscl>/discovery
(RETRIEVE)
Obtained a URI list
NA retrieves DA data (RETRIEVE)
<myHomeGSCL>/applications/Heating-App-
ID/containers/temperature/contentInstances/myHomeTemp
… …
Resource Subscription and Notification
M2M Gateway (GSCL)
M2M Network (NSCL)
M2M Device (DA)
Network Application
(NA)
mIamIddIa
NA subscribes to DA data
stored on GSCL (CREATE)
Created subscription resource <myHomeGSCL>/applications/He
ating-App-
ID/containers/temperature/contenID/containers/temperature/contentInstances/subscriptions/tempSub
DA writes new data to GSCL
container (UPDATE)
Updated resource for DA <myHomeGSCL>/applications
/Heating-App-ID/containers/temperature/contentInstances/myHomeTemp2
Notification to NA
(NOTIFY)
Obtained new
temp
12
ETSI M2M – HTTP and CoAP Binding
13
M2M Device Management
Device Management
DM Server
M2M Server M
2M
Applic a
ti on
M2M Service Capabilities (SC)
Mgmt Request
Converted Mgmt
Commands
Mgmt Commands
Response
Response
Response
M2M Devices w/ SC
Mgmt Proxy and
Translation
Mgmt Command Conversion
and mgmtObj Mapping
ETSI M2M reuses OMA DM and BBF TR069 for managing M2M Devices
14
M2M AreaNetwork
Access
Networks
Core Networks
M2M Devicesw/o SC
M2M
Gateway
Mgmt Commands
Response
Converted Mgmt Commands
Response
Remote Entity Management Architecture (1)
M2M Device/Gateway
M2M Service Capabilities
M2M Applications
mIa
NREM
M2M Applications
dIa
M2M Service
Capabilities
D/GREM
REM REM REM
Page 15
� Integrated Architecture for Managing M2M Devices/Gateways directly:
*NOTE: Alternatively to REM Server
being integrated as a part of the NREM,
the REM Server may be external to the
NREM but interface with the NREM via
an implementation-specific interface
exposed by the REM Server.
ETSI M2M OMA DM BBF TR069
REM Server (*) DM Server ACS
REM Client DM Client CPE
REM Interface (mId) DM-1, DM-2 TR069-CWMP
Communication modules
Core Network BCore Network A
Core Network Connection
mId
REM
Client
REM Server
REMinterface
Remote Entity Management Architecture (2)
M2M Gateway M2M Applications
mIa M2M Applications
dIa
M2M Service Capabilities Layer
GREM
REM Interface 1
M2M Device (D’) REM
M2M Service
Capabilities Layer
Legacy Device (d)
Communication modules
Management
Client
REM
Server
REM
Interface 2
NREM
Page 16
Communication modules
mId
REM
Client
REM
Proxy
REM
Server
dIa
REM
Interface 2 Management
Client
M2M Applications
Communication modules
REM Server
� Integrated Architecture for Managing M2M Devices behind a M2M
Gateway:ETSI M2M OMA DM BBF TR069
REM Server (N) DM Server ACS
REM Server (G) Legacy Server Control Point
REM Proxy GwMO Proxy Module
REM Client DM Client CPE
Management Client Legacy Client Legacy Client
REM IF 1 (mId) DM-1, DM-2 TR069-CWMP
REM IF 2 (dIa) Legacy IF Legacy IF
Additional features in Release 2
17 © ETSI 2012. All rights reserved
Main Release 2 features
Interworking with 3GPP
M2M Information Recording
Charging architecture
Few enhancements: like the communication channel used for
arbitrary requests to a Gateway behind a NATarbitrary requests to a Gateway behind a NAT
Interworking with 3GPP MTC
3GPP/LTE RAN
Cellular
M2M
Device
Cellular
M2M
M2M Network
Applications
The image cannot be displayed. Your computer …
M2M Server
mIa
(ETSI )
Tsp
(3GPP)
MTC -IWF
3GPP Core Network
NodeB
HSS
SMS-SC
19
3GPP/LTE RANM2M
GW
Cellular
M2M
Device
The image cannot be displayed. Your computer …
(ETSI )(3GPP)
SGSNGGSN
MMEmId
(ETSI )
MSC
ETSI M 2M
Reference Points
3GPP MTC
Interface
M2M Information Recording (1)
ETSI TC M2M Release 2 provide the recording feature on the M2M NSCL (only network side).
The M2M NSCL shall be able to initiate recording based on any of the following triggers:• A request received by the M2M NSCL over the mId reference point.
• A request received by the M2M NSCL over the mIa reference point
• A request initiated by the M2M NSCL• A request initiated by the M2M NSCL
• Timer- based trigger for non- request based information recording. This trigger is used only when the memory size of a container over a period of time is required.
More than one trigger can be simultaneously configured
The recording triggers may also be configurable, for example, as follows:• On a per SCL basis, for requests originating/arriving from/at the M2M NSCL.
• On a per application basis
• A default behaviour for non-configured SCLs/applications.
M2M Information Recording (2)
A recorded unit shall be tagged to depict its content according
to the following classification:
• Data related procedures represent procedures associated with data
storage or retrieval from the M2M NSCL (eg. Container related
procedures)
• Control related procedures: represent all procedures that are not • Control related procedures: represent all procedures that are not
associated with data storage/retrieval from the M2M NSCL with the
exclusion of group and device management related procedures (e.g.
subscription procedures)
• Group related procedures: represent procedures that handle groups.
• Device Management Procedures
Offline Charging architecture
Network Domain Network Applications
mIa
M2M Device Domain
Communication modules
Device Applications
dIa/Internal
M2MService
Capabilities
M2M Device Domain
Communication modules
Device Applications
dIa/Internal
M2MService
Capabilities
mId NSCL
Network Domain Network Applications
mIa
M2M Device Domain
Communication modules
Device Applications
dIa/Internal
M2MService
Capabilities
M2M Device Domain
Communication modules
Device Applications
dIa/Internal
M2MService
Capabilities
mId NSCL M2M Charging Function
Communication modulesCommunication modules
Core Network Connection
M2M Gateway
Communication modules
Gateway Applications
dIa/Internal
M2MService
Capabilities
M2M Devices
Core Network Connection
Core Network
Communication modulesCommunication modules
Core Network Connection
M2M Gateway
Communication modules
Gateway Applications
dIa/Internal
M2MService
Capabilities
M2M Devices
Core Network Connection
Core Network
Cm
Charging server
Contact Details:
Barbara Pareglio, Ericsson
Paul Russell, InterDigital
[email protected]@InterDigital.com
23
Thank you!
© ETSI 2012. All rights reserved