ETSI M2M Release 2. Enrico Scarrone, ETSI TC Smart M2M Vice-Chairman, Telecom Italia 4 ETSI M2M workshop, Mandelieu, France, EU

Transcription

1 Enrico Scarrone, ETSI TC Smart M2M Vice-Chairman, Telecom Italia 4 ETSI M2M workshop, Mandelieu, France, EU

2 TC M2M (now SmartM2M) Hasbeenfoundedin2008 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 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 alreadytransferredthetechnicalworkofetsim2mofrelease1and2to onem2m. 2

3 From thrm2m stovepipes to integrated offering Pipe#1 1 Application, 1 Network 1 (or few) types of Pipe#2 1 Application, 1 Network 1 (or few) types of Pipe#N 1 Application, 1 Network 1 (or few) types of Horizontal (based on common Layer) Applications share common infrastructure, environments and network elements Application Application Application Application #1 Application # i Application #N Common Application Infrastructure Transport Network (mobile, fixed, Powerline..) Transport Network (mobile, fixed, Powerline..) Transport Network (mobile, fixed, Powerline..) Transport Network 1 Transport Network 2 Gateway Gateway Gateway Gateway IP Local NW Local NW Local NW Local NW 3

4 reusing existing communication Technologies M2M Application Smart Energy Smart User Core Networks 3GPP (GPRS, EPC) ETSI TISPAN ATTM NGN Service Capabilities M2M Core M2M Area Networks M2M Area Network PLC SRD UWB DIRECT ZigBee CONNECT M-BUS Wireless M-BUS IEEE Smart Health Client Application Smart Transport Access Networks xdsl Hybrid FiberCoax PLC Satellite GERAN, UTRAN, eutran WLAN SRDs UWB WiMAX DIRECT CONNECT M2M Gateway 4

5 TC M2M Release 1 Release 1 Core Release1 Finalized in November ( and Including: Stage 1: Service and operational requirements for a multiservice M2M system 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 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 TS M2M service requirements DTS/M2M TS M2M Architecture DTS/M2M TS M2M Stage 3 Interfaces

6 ETSI M2M Connectivity s Management Services Connectivity s Service Enablement Data Management Services Connectivity s Connectivity Deployme nt Integratio n 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, 6

7 ETSI M2M Main functionality summary Function 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 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 management X 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

8 ETSI M2M full Release 2 Architecture Legacy case 1 Case 1 Legacy case 2 Case 2 d (out of scope) D DA dia DSCL d D DA mid (out of scope) dia G GIP (*dia) GSCL GA dia mid NIP Network Domain NA mia NSCL 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. (D): provides M2M Service Capability (DSCL) that communicates to an NSCL using the mid reference point and to Case 3 Legacy case 3 D DA d dia (out of scope) D (*optionally dia) DIP (*dia) DSCL DA dia mid NIP Network Domain NA mia NSCL mim DA using the dia reference point. ' (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

9 TC M2M Release 2 major additions 9 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 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 technologies

10 QUESTIONS? 10