ETSI M2M HORIZONTAL PLATFORM STRATEGY
Presented by Marylin Arndt, Joachim Koss for DG CONNECT & ETSI Workshop on Smart Appliances,27 May 2014
© ETSI 2014. All rights reserved
Content of the presentation
Horizontal Platform Vision• Current state of affairs• M2M use cases• Horizontal M2M Service Layer• Horizontal M2M Service Layer
oneM2M Partnership ProjectETSI SmartM2M• Brief biography• Proposals• N W k It• New Work Items• Deliverables, key M2M standard assets
Conclusion
© ETSI 2014. All rights reserved2
Introduction of ETSI
― ICT standards organization based in France
Other Governmental
Body2%ICT standards organization based in France
― Formed in 1988― Formaly recognized as SDO by the EU
T l IT d ICT i id
Administration8%Research
Body/University15%
Others4%
2%
― Telecoms, IT and « ICT inside » e.g. transports, mobile payments, smart grids, etcGl b l b hi (770+ M b /63
Manufacturer40%
Network Service Provider
Users4%
Consultancy9%
― Global membership (770+ Members/63 countries)
― Direct participation
Operator10%
Service Provider8%
4>3%3>3% 120 Associate Members ( )― “Made in EU for global use” enabler of
a series of worldwide industrial hits― Partnership is the preferred way (3GPP,
)
4>3%
54>45%
(Nber > %)
Australia
America
Asia
3
oneM2M…)― Interoperability (CTI)
59>49%54>45% Asia
Africa
HORIZONTAL PLATFORM VISIONJoachim Koss
© ETSI 2014. All rights reserved4
Current state of affairs
M2M has been around for several decades now – some deployments date back more than 20 years. However M2M markets are struggling to realise the full M2M market potentialpotentialFragmentation, provisioning, efficiency, integration complexity, scalability – and – lack of standards, seem to be major obstaclesKey challenges:• M2M C i ti t ICT I d t t• M2M Communications meets non‐ICT Industry sectors• Make intelligent use of information, enabled by connected IT
© ETSI 2014. All rights reserved5
Current state of affairs
Inhibitors for large scale M2M deployments – extracts from g p yindustry reports:
… a key challenge for the industry remains the complexity of developing, deploying, and managing M2M applications ... This is a challenge both for mobile network operators that are trying to offer profitable services tailored to the M2M market, as well as for application developers and service providers that are trying to reduce costs, speed time to market, and simplify robust application deployments ABI Research, M2M software platformsrobust application deployments, ABI Research, M2M software platforms
For many years M2M was held back by the lack of a low cost, global access medium, the fragmented nature of the ecosystem, the lack of any single killer application driving demand and h l f 2 l i l di hi h d l dthe complex nature of M2M solutions leading to high-cost development and systems
integration.Strategy analytics, M2M strategies
© ETSI 2014. All rights reserved6
Examples of M2M Use Cases
Fleet Management Fleet Management Home Energy
Management Smart Parking Smart Parking
© ETSI 2014. All rights reserved
7
Horizontal Platform Vision
Pipes (verticals):1 Application, 1 NW,
1 (or few) type of Device
Horizontal (based on common Layer)Applications share common infrastructure, environments
d t k l t1 (or few) type of Device
BusinessApplication
and network elements
Business Application #1
Business Application #i
Business Application #N
BusinessApplicationBusiness
A li ti
CommunicationNetwork (mobile
Common Application Infrastructure
C i ti
ApplicationBusinessApplicationBusiness
Application
Network (mobile, fixed, Powerline ..)
Gateway
CommunicationNetwork 1
CommunicationNetwork 2
IP
CommunicationNetwork (mobile,
fixed, Powerline ..)CommunicationNetwork (mobile,
fixed, Powerline ..)CommunicationNetwork (mobile,
fixed, Powerline ..)CommunicationNetwork (mobile,
fixed, Powerline ..)
Local NW
Device
y
Local NW
Device Device Device Device
GatewayIP
Local NW
Device
Gateway
Local NW
Gateway
Local NW
Gateway
, )
Gateway
© ETSI 2014. All rights reserved
DeviceDevice
Local NW
Device
8Source: ETSI SmartM2M, February 2014
Horizontal Platform vision: ETSI M2M / oneM2M Standard
The M2M Standard was designed specially g p yto give a simplified & unified layer as a service to various partners aiming at sharing their respective information =their respective information =a common Platform to share data among various Application domains initially having different data models
© ETSI 2014. All rights reserved9
M2M standard… the Service Platform ‐for multi‐domains interworking
hosting databases applicationspartners SI
M2M Service Platform
All devicesOur managed devices your
devices
simple, open, scalable & secure
© ETSI 2014. All rights reserved10
Facilitate, rationalize and secure the exchange of M2M data within the networkIntegrate new devices, create new or evolve your applications easily
Based on ETSI Smart City WS June 2013 presentation M. Arndt, ORANGE.
M2M Service Layer
Middleware ‐ supporting secure end‐to‐end data/control pp g /exchange between M2M devices and customer applications by providing functions for remote provisioning & activation, authentication encryption connectivity setup bufferingauthentication, encryption, connectivity setup, buffering, synchronization, aggregation and device management
a software layersits between M2M applications and communication HW/SW that provides data transport
ll id f IPnormally rides on top of IPprovides functions that M2M applications across different industry segmentsindustry segments
© ETSI 2014. All rights reserved11
ONEM2M PARTNERSHIP PROJECTJoachim Koss
© ETSI 2014. All rights reserved12
oneM2M Partnership Project
On July 24, 2012 seven of the world’s leading ICT Standards y , gDevelopment Organizations (SDOs) launched a new global organisation: the oneM2M Partnership Project: http://www oneM2M orghttp://www.oneM2M.org
Mission:oneM2M is working to unify the g yGlobal M2M Community, by enabling the federation and interoperability of M2M systemsinteroperability of M2M systems, across multiple networks and topologies
In addition Broad Band Forum, Continua Health Alliance, Home Gateway Initiative and Open Mobile Alliance (OMA) have been accepted as a oneM2M Partners Type 2
© ETSI 2014. All rights reserved13
accepted as a oneM2M Partners Type 2.
oneM2M Partnership Project ‐ Organization
Legal FinanceSteering Committee
(Partners)
Legal
Methods &Processes
Finance
MARCOM
Technical PlenaryMethod of Work
WorkProgrammeTechnical Plenary
(Members / Partners)
RequirementsWG1
Management,Abstraction,
Programme
ProtocolsWG3
WG1
ArchitectureWG2
SecurityWG4
Semantics WG5
© ETSI 2014. All rights reserved14
WG3WG2 WG4
oneM2M Partnership Project – Work Areas
WG1 – Requirementsq• Input accepted on more than 100 service requirements
WG2 – Architecture• Distilling service‐layer architectural options
WG3 – Protocols• Assessing protocols for service layer, and interoperabilityAssessing protocols for service layer, and interoperability
WG4 – Security• Ensuring Security and Privacy aspects are considered
WG5 – Management & Semantics• Providing device management; Working on semantic library
List of deliverables attached
© ETSI 2014. All rights reserved15
ETSI SMARTM2MMarylin Arndt
© ETSI 2014. All rights reserved16
M2M ‐> SmartM2M
ETSI M2M Technical Committee has developed since 2009 a set of specifications for M2M services and applicationsset of specifications for M2M services and applications.
http://docbox.etsi.org/M2M/Open/
ETSI C i f h l b li iETSI Commitment to further globalization :• ETSI being a founding member of the Partnership Project, the
specifications published by TC M2M have been pushed in oneM2MoneM2M.
M2M has been modified to SmartM2M. • SmartM2M will maintain ETSI M2M published specifications, and
produce complementary specifications as needed for regulatory purposes
• SmartM2M will Identify through EU policy and regulatory requirements on M2M services and applications to be developed
© ETSI 2014. All rights reserved17
equ e e ts o se ces a d app cat o s to be de e opedby oneM2M, and convert the oneM2M specifications into European Standards
So What ?
I it 2014 W k S t M2M illIn its 2014 Workprogram, Smart M2M will work, using the M2M platform as an asset that can federate all the local actors involved in Energy Efficiency, for example.
J t lik h t i d ith th M2M/I TJust like what is done with other M2M/IoT‐related stakeholders, a similar approach will be investigated for Smart Appliances, in collaboration with the European Commission.
© ETSI 2014. All rights reserved18
And Then ?
Expected BeneficesExpected Benefices• semantics assets for the interoperability of smart appliances, • mapping into a common ontology as an M2M application layer
semantics.• allowing unified access to the data with adequate access rights• for seamless exchanges among all the applicative domains involved in
the Smart Appliances
ETSI SmartM2Mwill be able to explain how to map theseETSI SmartM2M will be able to explain how to map these ontologies to the platform,
as to « plug & play » easily the applications to the generic « shared‐by‐all » solution
© ETSI 2014. All rights reserved19
New Work Items
DMI/SmartM2M‐0024SmartApp/ pp(deliverable: action‐plan incl. initial description of a set of ETSI deliverables)Th W kit h b d d iThree new Workitems have been approved during SmartM2M#30 at Venice, 5th to 7th May, 2014• SmartM2M(14)000001r4 NWI‐"Common Ontology for Smart
Appliances" as DTS/SmartM2M‐103 265 SAP_Onth• SmartM2M(14)000002r5 NWI‐"M2M communications for Smart
Appliances“ as DTS/SmartM2M‐103 267 SAP_Com• SmartM2M(14)000005r3 NWI‐"Smart Appliances ontology and
communications testing“ as DTS/SmartM2M‐103 268‐1 SAP_tst
© ETSI 2014. All rights reserved20
Conclusion
A t d di dM2M S i LA standardised M2M Service Layer, being Access Technology Independent is expected to become the vehicleis expected to become the vehicle
to transport and manage data traffic of M2M applications, pp ,
globally,across many M2M sectors and across all regions ….
it i t th d j t th b i i f th t !it is not the end … just the beginning of the story !
© ETSI 2014. All rights reserved21
Contact details
Joachim KossDirector Standardization M2M
Marylin ArndtM2M Senior Standardisation Manager Director Standardization M2M
ETSI Board MemberoneM2M TP Vice Chairman
Gemalto M2M GmbHSiemensdamm 50
M2M Senior Standardisation Manager Chairman ETSI TC SmartM2M
Orange LabsBP9838243 MEYLAN CEDEX Siemensdamm 50
13629 Berlin
Phone: +49 30 31102-8255Mobile: +49 172 3911249mailto:[email protected]
38243 MEYLAN CEDEXFrance
Phone: +33 476764250 Mobile: +33 673692834 mailto:[email protected]
www.gemalto/m2m.commailto:[email protected]
Thank you!
© ETSI 2014. All rights reserved22
Annex – ETSI M2M deliverables
23 © ETSI 2014. All rights reserved
ETSI M2M deliverablesRelease2 published end-2013
Use Cases
TR 102 691Smart Metering
TR 102 732eHealth
TR 102 897City automation
TR 102 898Automotive
Use Cases
TR 102 857Connected
TS 102 689TR 102 935
Smart Metering eHealth City automationAutomotive Connected consumer
TR 102 725Stage 1TS 102 689M2M Service Requirements
TS 102 690
TR 102 935Smart Grid
impacts on M2M
TR 102 167 TR 102 966
TR 102 725M2M Definitions
TR 101 584Stage 2
TS 102 690M2M Functional
Architecture
TR 102 167Threat analysis &
counter measures to M2M service layer
TR 102 966Interworking with
M2M Area Networks
TR 101 584Study on
Semantic support for M2M Data
Stage 3TS 102 921
M2M Communications; mIa, dIa and mId interfaces
TR 101 531Re-use of 3GPP
nodes by M2MSC layer
TS 103 104Interoperability Test
Specification forCoAP Binding of
ETSI M2M Primitivesongoing:
© ETSI 2014. All rights reserved
TS 103 092OMA DM compatible Management Objects
TS103 093BBF TR-069 compatible
Management Objects
TR 103 118Smart Energy Infrastructures
security; review…
TR Report on Smart City activity;
impact on IoT Environment
g g
24
oneM2M deliverables
WI TS / TR Name
0001 TR 0001 oneM2M Use Case collection
published
0001 TS 0002 M2M Requirements
0002 TR 0002 Part 1: Analysis of the architectures proposed for consideration by oneM2M
0002 TR 0003 Part 2 Study for the merging of architectures proposed for consideration by oneM2M
0002 TS 0001 M2M Architecture
0003 TR 0004 Definitions and Acronyms0003 TR 0004 Definitions and Acronyms
0003 TR 0005 Roles and Focus Areas
0004 TR 0006 Study of Management Capability Enablement Technologies for Consideration by oneM2M
0005 TR 0007 oneM2M Abstraction and Semantics Capability Enablement
0006 TR 0010 oneM2M Device / Gateway Classification
0007 TR 0008 Analysis of Security Solutions for the oneM2M System
0007 TS 0003 oneM2M Security Solutions
0008 TR 0009 oneM2M Protocol Analysis
0009 TS 0004 oneM2M Protocol Technical Specification
bl ( )0010 TS 0005 oneM2M Management Enablement (OMA)
0010 TS 0006 oneM2M Management Enablement (BBF)
0011 TS 0007 oneM2M Service Components
0012 TS 0008 CoAP Protocol Binding Technical Specification
0013 TS 0009 HTTP Protocol Binding Technical Specification0013 TS 0009 HTTP Protocol Binding Technical Specification
0014 TS 0010 MQTT Protocol Binding Technical Specification
0014 TR 0011 MQTT Protocol Interworking Study
0014 TS 0001 ‐ CR Architecture changes for interworking
25