Embed Size (px)
Citation preview
ETSI M2M Release 2
Enrico Scarrone, ETSI TC Smart M2M Vice-Chairman,
Telecom Italia
4° ETSI M2M workshop, Mandelieu, France, EU
ETSI M2M Release 2
TC M2M (now SmartM2M)
Has been founded in 2008
to develop and maintain an end-to-end overall telecommunication high
level architecture for M2M
to identify gaps where existing standards and provide specifications to
fill these gaps
TC M2M has faced the challenge of developing a common M2MTC M2M has faced the challenge of developing a common M2M
framework as an answer to the fragmentation of the solution that is
penalizing the M2M market developments the understanding of the
shared data
Release 1 finalized end 2011
Release 2 finalized in beginning 2013
TC M2M is fully committed to the global initiative of oneM2M has
already transferred the technical work of ETSI M2M of Release 1 and 2 to
oneM2M.
2
ETSI M2M Release 2
From thrM2M stovepipes to integrated
offering
Pipe#1 1 Application,
1 Network 1 (or few) types of
Device
Business
Application
Horizontal (based on common Layer)Applications share common infrastructure,
environments and network elements
Business Application #1
Business Application # i
Business Application #N
Business
Application
Business
Application
Pipe#2 1 Application,
1 Network 1 (or few) types of
Device
Pipe#N 1 Application,
1 Network 1 (or few) types of
Device
3
Local NW
Device
Transport Network (mobile, fixed, Powerline ..)
Gateway
Transport Network 1
Transport Network 2
Local NW
Device Device Device Device
Common Application Infrastructure
Gateway
IP
Local NW
Device
Transport Network (mobile, fixed, Powerline ..)
Gateway
Local NW
Device
Gateway
Transport Network (mobile, fixed, Powerline ..)
ETSI M2M Release 2
M2M Application M2M Area Network
Service
Capabilities
M2M
Core
DIRECT
CONNECT
… reusing existing communication
Technologies
M2M Area Networks• PLC• SRD• UWB
• ZigBee• M-BUS• Wireless M-BUS• IEEE 802.15•
Core Networks• 3GPP (GPRS, EPC)• ETSI TISPAN• ATTM• NGNSmart Energy
Smart User
M2M
Gateway
Client
Application
DIRECT
CONNECT
4
Smart User
Smart Transport
Smart Health
Access Networks• xDSL• Hybrid FiberCoax• PLC• Satellite• GERAN, UTRAN, eUTRAN• WLAN• SRDs• UWB• WiMAX
ETSI M2M Release 2
TC M2M– Release 1
Release 1
Core Release1 Finalized in November 2011. (http://docbox.etsi.org/M2M/Open/Latest_Drafts/ and www.etsi.org)
Including:• Stage 1: Service and operational requirements for a multiservice M2M system
• Stage 2: Architecture: SCL, device, gateways and network platforms, RESTful • Stage 2: Architecture: SCL, device, gateways and network platforms, RESTful
resources information model and relates procedures, service bootstrap, reference
points (dIa, mId, & mIa definition), legacy devices, etc
• Device Management (with BBF and OMA DM)
• Security (Key management and Automated Bootstrapping)
• Stage 3 (API primitives and parameter definitions, HTTP / CoAP Binding)
Release 1 core specs (full list available on the ETSI portal)
WI Ref ETSI Ref Specification Name
DTS/M2M-00001 TS 102 689 M2M service requirements
DTS/M2M-00002 TS 102 690 M2M Architecture
DTS/M2M-00010 TS 102 921 M2M Stage 3 Interfaces
ETSI M2M Release 2
ETSI M2M
Devices
Connectivity
Service Enablement
DataDataDataDataManagement
Services
Devices
Connectivity
Management
Services
Devices
Connectivity
6
Connectivity Deployment
Integration
� ETSI M2M standard is based on a “Store and Share” resource based paradigm.
� The data may be made available in the platform to the other applications, interested
application are notified by means of subscription
� Privacy is ensured by a strict Access Rights Management, which relies on underlying
network security, providing a secure light solution
� ETSI M2M is heavily reusing underlying network functionalities, including TR069 and OMA
DM management, LCS, subscription management, QoS, Charging, etc.
� ETSI M2M release 1 has been released end 2012,
ETSI M2M Release 2
ETSI M2M Main functionality summaryFunction NSCL GSCL DSCL
Ensure that only trusted applications can communicate to the SCL X X X
Registration of applications to the local SCL X X X
Authetication and authorisation of SCL communication X X X
Generation of charging records pertaining to the use of the system for purposes of e.g. billing, accounting X
Provides means to store application data with history X X X
Provides means to share data among applications X X X
Provides M2M service connection establishment and teardown along with security key negotiation. X X X
Selection of communication means for delivery of information based on policies X X X
Analysis and forwarding of methods according to provisioned policies and method metadata X X X
Manages subscriptions and notifications pertaining to changes in data. X X X
Support access control for stored data (authorisation) X X X
Keeping track of reachability of the M2M Device or M2M Gateway X X X
Support grouping of information pertaining to gateways, devices and applications X X X
Supports remote management of gateways, devices and area network, including performance management,
configuration management, fault management and software and firmware upgrading managementX X X
Supports multiple management protocols X X
Provides interworking between non ETSI compliant devices or gateways and the SCL X X X
Interworking and using of Core Network services exposed by the Network Operator. X
Geographic location support X X X
NAT traversal support X X X
ETSI M2M Release 2
Network
Domain
NA
DDA
DSCL
dIa
mIa
d(out of scope)
D‘
DA
dG GA
dIa
GSCLdIa
mId
mId
Legacy case 1
Case 1
Case 2
Legacy case 2
NSCL
NIPGIP(*dIa)(out of scope)
ETSI M2M full Release 2 Architecture� Gateway (G):Gateway (G):Gateway (G):Gateway (G): provides M2M
Service Capabilities (GSCL) that
communicates to the NSCL using
the mId reference point and to
DA or GA using the dIa reference
point.
� Device (D):Device (D):Device (D):Device (D): provides M2M
Service Capability (DSCL) that
communicates to an NSCL using
the mId reference point and to
DA using the dIa reference point.
d
D DA
dIa
DSCL
Legacy case 3(out of scope)
DIP
(*optionally dIa)
(*dIa)Network
Domain
NA
mIa
NSCL
NIP
mIm
D‘
DAdIaCase 3
mId
DA using the dIa reference point.
� Device' (D'):Device' (D'):Device' (D'):Device' (D'): hosts DA that
communicates to a GSCL or to
NSCL using the dIa reference
point. D' does not implement
ETSI M2M Service Capabilities.
� Additionally there is a non-ETSI
M2M compliant device ('d') that
connects to SCL using the xIP
Capability (NIP, GIP, DIP). d
devices do not use ETSI M2M
defined reference protocols/API
ETSI M2M Release 2
TC M2M Release 2 major additions
Charging: definition of the architectural framework for recording,
tracking and exchange of events relevant for the collection of statistical
information and for the exchange of charging information, including
correlation with charging information from the underlying network
Inter-domain communications between service platforms, i.e. inter-NSCL
communication, on mIm reference point (a variant of mId). This allow
application in a domain to exchange information with application in aapplication in a domain to exchange information with application in a
different domain, in a transparent way respect to the domain they
belong to.
M2M Light: ETSI M2M Release1 was already supporting very constrained
devices via gateways, in Release 2 very constrained device can connect
directly to the network platform. Implementation has been made on
made on USB dongles.
Semantic interworking guidelines common semantic rules has been
defined for applications belonging to different industrial segment, to
assure the understanding of the shared data, for a very wide set of
commonly used technologies9
