(aspects of standardization) - · pdf fileetsi m2m - onem2m – iot (aspects of...

ETSI M2M - oneM2M – IoT(aspects of standardization)

Joerg Swetina (NEC)([email protected])

Many standards want / need to play in the M2M arena

M2M

e-health Automotive, ITS

BEMSHEMS, Smart House

The standards landscape related to M2M is very wide.

e.g. the Global Standards Collaboration Machine-Machine Task Force (GSC MSTF)

identifies 143 organisations with a direct or indirect interest in M2M standardisation !

M2MGateway

ClientApplication

M2M Application M2M Area Network

Service Capabilities

M2MCore

DIRECT CONNEC

T

A simple picture of M2M

3

DIRECT CONNEC

T

M2M Area Networks• PLC• SRD• UWB • ZigBee• M-BUS• Wireless M-BUS• IEEE 802.15

Core Networks• 3GPP (GPRS, EPC)• ETSI TISPAN• ATTM• NGN

Access Networks• xDSL• Hybrid FiberCoax• PLC• Satellite• GERAN, UTRAN, eUTRAN• WLAN• SRDs• UWB• WiMAX

Smart MeteringeHealthConnected

ConsumerCity AutomationAutomotiveSmart Grid

… and where the standards play their role

Standards on Services enablers for M2M

Standards for M2M Service enablers:Target:(a) end-to end enablement -across servers, gateways, devices(b) standardized service interfaces

ETSI TC M2M

… a bit more on

6

Introduction to ETSI TC M2M

▐ Scope of TC M2M• to develop and maintain an end-to-end overall teleco mmunication high level architecture

for M2M• to identify gaps where existing standards and provid e specifications to fill these gaps

▐ Some figures• Established in Jan 2009, after 8 months of preparat ion in the ETSI Board• 8 plenary meetings per year plus numerous ad-hoc me etings• 3-5 conference calls per week• Constantly Growing number of documents per meeting (200 +)• Constantly growing plenary participation (70 +)• Growing membership in M2M email list (400+)• Active delegates from Europe, North America, China, Korea, and Japan and

currently about 30% Operators, 60% Manufacturers an d 10% others

▐ Open approach• TC M2M has initiated active liaisons and cooperatio n with many other SDOs and consortia.• Published and draft TR/TS are available on the publ ic side of the ETSI server

http://docbox.etsi.org/M2M/Open/

6

TC M2M Organization

TC M2M PLENARY

WG1 WG2 WG3 WG4 WG5

Use Cases & Requirements

Architecture &Network

InterworkingProtocols & Interfaces

Security Aspects

Management Aspects

7

Patricia Maritigne

France Telecom

FrançoisEnnesserGemalto

Raymond Forbes

Ericsson

Yongjing ZhangHuawei

Paul Russel

Interdigital

Chairman: Enrico Scarrone – Telecom ItaliaVice Chairmen: Marylin Arndt – France Telecom

Omar Elloumi – Alcatel LucentJoachim Koss – Cinterion

Technical Officer: David Boswarthick – ETSI

The value of a standardized horizontal M2M service layer

8

Lower OPEX for M2M

ServicesLower CAPEX for

M2M Services

Reduces investment

barriers to new

markets

Simplifies M2M for

users and Apps

developers

Faster time for new

M2M services to

markets

Interoperable

solutions push cost

down

Standard APIs and protocols allow for horizontal solutions=> Reduced initial investment.

Single service layer abstracts from underlying networks=> Separate service- from

network business/management.

Standardized interfaces allow easy applications development.=> use of platform for fast testing and roll out of new services

Simplicity of developmentSimplicity of deployment

=> (inexpensively) test the market before investing.

Standard interfaces, protocols=> reduce costs for inter-operability on services level.(between service providers)

=> create new M2M ecosystems to foster innovation of services.

ETSI TC M2M - the ETSI M2M Vision

A bit more technical on ETSI M2M

▐ Defines a “Service Capability Layer” (SCL) on top of connec-tivity layers (not in scope)� SCL in network server,

gateways and devices.� SCL does registration, access

rights, security&authentication,data-transfer (containers), subscribe / notify, groups …

▐ API for applications is based onREST principles allowing� Scalability (stateless, idempotent)� Supports unreliable connections� Binding to e.g. HTTP, CoAP

▐ Re-uses TR-069 (from BBF) and OMA DM (from OMA) for device management

⇒ ETSI M2M Release 1 has been finalized this year!⇒ All specifications and reports openly available at: http://docbox.etsi.org/M2M/Open/Latest_Drafts/

The ETSI M2M Specifications Work

10

Stage 3

Stage 2

Stage 1

TR 102 691Smart

Metering

TS 102 689M2M Service Requirements

TR 102 732eHealth

TR 102 897City

automation

TR 102 898Automotive

Use Cases [Stage 0]

TS 102 690M2M Functional

Architecture

TS 102 921M2M Communications; mIa,

dIa and mId interfaces

TR 102 966Interworking

with M2M Area Networks

TR 102 725M2M

DefinitionsTR 102 167Threat analysis &

counter measures to M2M service layerTR 101 531

Re-use of 3GPP nodes by

M2MSC layer

TR 102 857Connected consumer

TR 102 935Smart Grid impacts on

M2M

P

TS 101 404OMA DM

compatible Management

Objects

TS 101 405BBF TR-069 compatible

Management Objects

TR 101 584Semantic

support for M2M Data

P

P

P

P

This study willcreate a direct

link to IoT

… AGREE ON A SINGLESTANDARD !!

… but ETSI M2M is not the only SDOworking on Service level interface standardsHow to avoid fragmentation of markets ???

Good news: the ”oneM2M” global Initiative

▐ To avoid creation of competing M2M standards the 7 SDOs, that publish telecom standards: TTC, ARIB (Japan), ATIS, TIA (USA), TTA (Korea) CCSA (China), ETSI (Europe) are now finalizing set-up of the oneM2M Global Initiative .

oneM2MGlobal Initiative

▐ Objective:� Develop one globally agreed M2M

specification, initial focus on Service Layer� Consolidate current M2M Service Layer

standards activities into the oneM2M initiative

� Partner/Collaborate with wireless and wireline SDOs and fora responsible for developing standards

• for Core and Access Networks.• the vertical markets (i.e., domain-specific) • auxiliary specifications (e.g., OMA DM, W3C

for Device APIs).

⇒ ETSI TC M2M (Europe), TIA TR-50 (USA) and CCSA TC 10 (China) will stop individual work and join their efforts to create a single M2M standard!

▐ Organizations� ICT/Telecom SDOs� Others standards and specifications setting organizations� Industry groups� Associations� Specific technology organizations

▐ Individual Companies� Service Providers (e.g., M2M SPs, Telecom SPs, Service Layer SPs)� M2M service users (e.g., Utilities)� Vendors (e.g., M2M Application Providers)

▐ Regional/Country Governmental Entities

Participation needs to:� Be open and well balanced� Provide opportunities for various levels of participation� Accommodate companies and organizations

13

Target Participation in oneM2M

Latest news on oneM2M

▐ Bi-weekly conference calls of 7 SDOs to prepare oneM2M▐ Update one “oneM2M” creation progress:

• ARIB Internal approval process is completed in ARIB.• ATIS Internal approval of the agreement will happen end of June.• CCSA Internal approval process is completed in CCSA• ETSI Internal approval process will complete on 22nd June.• TIA internal approval process should be complete by mid June.• TTA General Assembly had approved admission into oneM2M.• TTC Internal approval process is completed in TTC.

▐ Official signing ceremony of creation documents of “oneM2M Global Initiative” 24-26 July in Seattle, at the occasion of Steering Committee meeting #01

▐ inviting verticals to Steering Committee meeting #01▐ See website: www.oneM2M.org

Tentative timeline

▐ 16-20 July 2012 M2M#21 Sophia Antipolis, France, EU▐ 24-26 July 2012 One M2M Steering Committee#1 Seattle, USA

� Kick-off event and ceremony of signing� Potential SC agenda:

• Convenor of Technical Plenary nominated by Steering Committee• Number of Participants of Technical Plenary identified• Working Procedures approved by Steering Committee• Draft Agenda of the first TP meeting

� Partners Type 1 may provide first list of proposed candidate standards/specifications to be transferred into oneM2M

▐ 17-21 Sept. 2012 M2M#22 Sophia Antipolis, France, EU▐ 24-28 Sept. 2012 One M2M Technical Plenary#1+ SC#2 Sophia Antipolis Area, France

� Potential TP agenda:• Analysis of the potential candidate standards/specifications to be transferred into oneM2M and potential

agreement• Initial discussion on Work Plan• Initial Working Groups defined• Convenors of Working Groups nominated by Technical Plenary• Meeting schedule defined

▐ 03-07 Dec. 2012 M2M#23 China▐ 10-14 Dec. 2012 One M2M Technical Plenary#2 China (TBC)

Backup

1 - Standards for Wide Area Networks

Standards for Wide Area Networks(3GPP, fixed NW, WiMax…):Target :protect networks against negative effects of M2M traffic (many devices, non-human traffic …)

2 - Standards for Local Area Networks

Example ZigBee:� 802.15.4 phy/link layer

optimized for low bitrate� Support of vertical

industry segments:Application Profiles

Standards forLocal Area Networks(ZigBee, Bluetooth,.)Target :foster use of LANtechnology by supporting servicesof multiple verticals

Das Bild kann zurzeit nicht angezeigt werden.

3 - Standards and fora of ‘vertical’ industries

Standards / fora of ‘vertical’Industries(applications)Target :enable interoperable,cost-efficient Solutions

… eventually will create a part of …

M2M is inverting - ‘horizontalizing’ - the pipes

20

Local NW

Pipe (vertical):1 Application, 1 NW,

1 (or few) type of Device

Horizontal (based on common Layer)Applications share common infrastructure, environments

and network elements

Business Application #1

Business Application #i

Business Application #N

BusinessApplication

Device

Transport Network 1

Transport Network (mobile, fixed, Powerline ..)

Transport Network 2

Gateway

Local NW

Device Device Device Device

Common Application Infrastructure

Gateway

IP

M2M Applications providers run individual M2M services. Customer is Device owner

M2M Service provider hosts several M2M Applications on his Platform.

Wide Area Transport Network operator(s)Customer is the M2M service provider

End user owns / operates the Device or Gateway

Features offered by ETSI M2M

▐ Identification of the M2M Application and the M2M Devices▐ Asynchronous and synchronous communication▐ Store and forward mechanism based on policies for optimizing the

communication▐ Location information▐ Device management based both on OMA DM (wireless) and BBF TR-69

(wireline)▐ Mutual authentication between Network Service Capability Layer and

Device/Gateway Service Capability Layer that are connected▐ Secure channel for transporting data over mId reference point▐ And much more ….

21

21

M2M Security

▐ R1 provides standardized security mechanism for the reference point mId

▐ The device/gateway needs to have keys for securing the connection.

▐ The device/gateway is provisioned with the key M2M Root Key.

▐ The high level procedure are to � Perform mutual mId end point authentication� Perform M2M Connection Key agreement� Optionally establish a secure session over mId.� Perform RESTful procedures over the mId

22

22

ETSI M2M further keywords

� Release2

� Ongoing work for additional fonctionalities

� expected publication in 2012

� Main items discussed for Rel2:

� Protocols mapping to ETSI M2M methods (linked to TR 102966)

� Putting the basis for further abstraction work (linked to Draft TR

101584)

� Charging/billing with appropriate data recording

� Service discovery

� QoS

� Service discovery

� Security extensions

(aspects of standardization) - · pdf fileetsi m2m - onem2m – iot (aspects of...

Documents