Status of Machine to Machine Standards work in TC M2M and onem2m Source : David Boswarthick (Technical Officer TC M2M). Many thanks to the various contributors from TC M2M
Setting the Scene 2
Where do we stand in the maturity cycle of M2M? Government stimulus programs boost M2M standards: EC mandate to ETSI/CEN/CENELEC to develop EU standards for Smart Metering (M/441), and later on for Smart Grid (M/490) NIST mandated to pilot delivery of standards for Smart Grids 3 Principal focus of ETSI M2M: prepare the deployment transition phase to horizontal platforms Source: of graphic: The Yankee Group
Rationale The M2M market is taking off: Government and industry initiatives Telecom actors business opportunity Ubiquitous networks and affordable hardware Fragmented industry Industry verticals are solving li their M2M needs on their own Customised solutions abound but there is much commonality (authentication, security, access rights) Economies of scale necessary for M2M are difficult to achieve There h is a need for a common efficient, i easily and widely available M2M Service Layer, which can be readily embedded within various hardware and Fast and global standardization is a key enabler to remove the technical barriers and ensure interoperable software. M2M services and networks 4 OneM2M overview
Value chain evolution for Telcos Application Layer Management Services (SIM, Module, Connectivity) Connectivity Application Layer Service Enablement Data Management Services Connectivity Revenue distribution shift to: Support business decisions with M2M data intelligence. Secure and manage M2M data. Identify and create new applications for M2M. Devices Devices Revenues are moving towards the service enablement layer and the support of data access, storage, management and security 5
Enabling information sharing Yesterday Connectivity Devices Today Management Services Connectivity Devices Tomorrow Service Enablement Data Management Services Connectivity Devices Connectivity Deployment Integration ETSI M2M is based on a Store and Share 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 6
ETSI M2M 7
ETSI M2M Vision Rd Reduced dcomplexity, Simplified applications i development, Standard Multi APIs and protocols, Enabling vendor M2M ecosystem, Service Reduced initial investment costs. Reduces solution Application Capabilities, cost and improves Same service layer for many verticals interoperability. Horizontal Multi Service Platform Business Application #1 Scalable horizontal solution, Re use of platform to test and roll out new services, Better network efficiency Network independent, use Technology best networks for deployment needs, Leverageonunderlying Independent networks functionality Gateway Business Application #2 Common Application Infrastructure Transport Network 1 Local NW IP Transport Network 2 Business Application #N Device Device Device Device Resource Based Shorter time to market Allows Data to trail new services, Less expensive to roll out than dedicated solution. Existing Standards Re use and Integration Full package toolbox End to End Reducesd integrationtimeand cost 8
Simplified M2M Architecture M2M Area Network M2M A Application li ti DIRECT CONNECT Service Capabilities M2M Core M2M Gateway Client Application DIRECT CONNECT 9
based on existing Technologies M2M Application A li ti Smart Energy gy Core Networks 3GPP (GPRS, EPC) ETSI TISPAN ATTM NGN Service Capabilities M2M Core M2M Area Networks M2M Area Network PLC SRD UWB ZigBee DIRECT M-BUS M BUS CONNECT Wireless M-BUS IEEE 802.15 Smart User Smart Health Client Application Smart Transport p 10 M2M Access Networks Gateway xdsl Hybrid FiberCoax y PLC Satellite GERAN, UTRAN, eutran WLAN DIRECT SRDs CONNECT UWB WiMAX
Overview of ETSI M2M Defines a Service Service Capability Layer (SCL) on top of connectivity layers SCL in network server server, gateways and devices. SCL does registration, access rights, security&authentication, data transfer (containers), subscribe / notify, groups API for applications is based on REST principles allowing Scalability (stateless, idempotent) Unreliable connections Binding to e.g. HTTP, CoAP Re uses TR 069 (from BBF) and OMA DM (from OMA) for device management 11
M2M high level system overview M2M Application Domain Application (e.g. Smart Metering application) mia ETSI M2M Service Capabilities mid User interface to application e.g. Web portal interface (usage monitoring, user preferences, ) M2M Server M2M Network Domain Based on existing standards and technologies, e.g.: 3GPP, TISPAN, IETF, Network 3GPP, Fixed, IP.. M2M Core Scope of ETSI M2M M2M Gateway M2M Service Capabilities M2M Devices / Gateways M2M Gateway dia M2M Device Domain Based on existing standards and technologies, e.g.: DLMS, CEN, CENELEC, PLT, Zigbee, M-BUS, KNX, etc. M2M Area Network M2M D Device Application M2M Service Capabilities dia Application M2M Device M2M Device(s) 12
ETSI M2M defines 3 interfaces mia... application Service Capabilities in the M2M Core Service capabilities are exposed (e.g. via an API) to applications in the form of service capability features. dia... application Service Capabilities in the M2M Device / GW The service capability features at the dia and at the mia are assumed to be identical if no difference is explicitly defined. mid SC in the M2M Core SC in the M2M Device / GW Reference point using IP connectivity, it includes interface between theservice Capability Client andtheservice Capability server, andit makes parallel use of existing management protocols (including TR 069) ETSI M2M is modelling these interfaces following a RESTful approach. 13 13
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 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: WI Ref ETSI Ref Specification Name DTS/M2M 00001 TS 102 689 M2M servicerequirements requirements DTS/M2M 00002 TS 102 690 M2M Architecture 14 DTS/M2M 00010 TS 102 921 M2M Stage 3 Interfaces
ETSI TC M2M deliverables status Use Cases [Stage 0] TR 102 691 Smart Metering P TR 102 732 ehealth TR 102 857 Connected Consumer TR 102 898 Automotive TR 102 897 City automation TR 102 935 Smart Grid impacts on M2M Stage 1 P (R1) TS 102 689 M2M Service Requirements TR 101 584 Semantic support for M2M data TR 102 725 M2M Definitions i i TS 103 092 OMA DM compatible Management Objects P Stage 2 P (R1) TS 102 690 M2M Functional Architecture TR 101 531 Re-use of 3GPP nodes by M2M SC layer TR 102 167 Threat analysis & counter measures to M2M service layer P TS 103 093 BBF TR-069 compatible Management Objects P Stage 3 P(R1) TS 102 921 M2M Comms; mia, dia, mid interfaces TR 102 966 Interworking with M2M Area Networks P = Published TS 101 603 Service Layer interworking with 3GPP networks 15
TC M2M future activities TCM2M workson M2M Release 2, and already set priorities; charging, data models and semantics, security extensions, the standardised use of operators network interfaces, multi operator service platforms, ltf service discovery, Area Nt NetworkManagement and service interworking profiles. The Two major area of work are; Standardization of the Interworking with the 3GPP and 3GPP 2 networks The study of solutions for the definition of common semantic rules between applications belonging to different industrial segment, to assure the understanding of the shared data TC M2M is also looking at testing; DTS/M2M 00019/DTS 103 104 Interoperability Test Specification for CoAP Binding of ETSI M2M Primitives, Rapporteur: Zach Shelby. 16
onem2m 17
From Technical Bodies to Partnerships ETSI TC M2M established 2008. First set of M2M platform standards to market in 2011. onem2m Partnership project established July 2012. 18 ETSI 2012. All rights reserved
Evolution of ETSI TC M2M into a global partnership project 19 Leading regional SDOs have agreed to create a global harmonisation partnership To prepare, approve and maintaingloballyapplicable applicable, access independent technical specifications and reports related to M2M solutions, with initial focus on the Service Layer same as ETSI M2M, some of whose work will be transferred to onem2m and form the basis for further OneM2M work. ETSI M2M will refocus on EU issues. With the opportunity for broad and equitable participation by all stakeholders in the M2M marketplace, including manufacturers, service providers and end users from all industries OneM2M overview avoiding any duplication of work between SDOs involved in the same domain of M2M Service Layer
Scope of onem2m Common set of Service Layer capabilities Access independent view of end to end services Open /standard interfaces, APIs and protocols Security, privacy, and charging aspects Reachability and discovery of applications Interoperability, including test and conformance specifications Identification and naming of devices and applications Management aspects (including remote management of entities 20 OneM2M overview
Founding SDOs (Partner Type 1) 21 OneM2M overview
Supporters (Partner Type 2) Industry organisations/associations that have applied to join as Partner Type 2, or have shown interest in applying: OMA Open Mobile Alliance (accepted 13 Sep 2012) BBF Broadband Forum CDF Connected Device Forum (applied 13 Sep 2012) CDG CDMA Development eeop etgoup Group Continua Continua Health Alliance IEEE SA IEEE Standards Association GSMA GSM Association HGI Home Gateway Initiative (applied 17 Sep 2012) IPSO Alliance IP for Smart Objects IPv6 Forum IPv6 Forum (applied 6 Aug 2012) ITU International Telecommunication Union KSGA Korea Smart Grid Association Mandat Intl represents FP7 IoT6 (applied Sep 2012) Zigbee Zigbee Alliance 22 OneM2M overview
THANK YOU FOR YOUR ATTENTION & ANY QUESTIONS?