Current standardization activities – oneM2m Document No: GSC(14)18_012 Source: ETSI Contact: Joachim Koss, joachim.koss@gemalto.com Agenda Item: 5.3 Current standardization activities – oneM2m Joachim Koss, Director Standardisation M2M, Gemalto, ETSI Board Member GSC-18 Meeting, 22-23 July 2014, Sophia Antipolis, France

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 potential Fragmentation, provisioning, efficiency, integration complexity, scalability and increasing number of IOT/M2M organisations seem to be major obstacles Key challenges: M2M Communications meets non-ICT Industry sectors Make intelligent use of information, enabled by connected IT SDO/Fora roadmaps are not coordinated GSC-18, 22-23 July 2014, Sophia Antipolis

Organizations in the IOT/M2M area IOT/M2M is a huge topic ranging from connectivity all the way to data models and semantics. One cannot expect the work to focus in a single place. The following list contain examples, many more exist: Alljoyn – open source project ETSI / oneM2M IEEE P2413—Standard for an Architectural Framework for the Internet of Things IETF ISA 100  (Industrial IOT) ISO/IEC JTC1 /WG7: project named IOT RA ITU Y 2066 and Y2067: Recommendation about IOT OpenInterconnec ZigBee Z-Wave The issues are when SDO/Fora roadmaps are not coordinated when SDOs compete on similar subjects GSC-18, 22-23 July 2014, Sophia Antipolis

HORIZONTAL PLATFORM VISION 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. The oneM2M Standard is designed specially to give a simplified & unified layer as a service to various partners aiming at sharing their respective information = a common Platform to share data among various Application domains initially having different data models GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Where we are (JuLY 2014) Partner Type 1 7 partners Partner Type 2 4 partners ARIB 12 members ATIS 15 members CCSA 18 members ETSI 120 members TIA 23 members TTA 13 members TTC 5 members Associates Members 3 associate members Total 220 organizations involved in oneM2M GSC-18, 22-23 July 2014, Sophia Antipolis

Management, Abstraction, Semantics WG5 oneM2M - Organization Legal Finance Steering Committee (Partners) Methods & Processes MARCOM Technical Plenary (Members / Partners) Method of Work Work Programme Requirements WG1 Management, Abstraction, Semantics WG5 Architecture WG2 Protocols WG3 Security WG4 GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Technical progress 15 Work Items approved by TP Covering requirements, architecture, protocols, security, and management, abstraction and semantics. Approved documents: TR Use Case – Approved. (Work has started on V 2) TS Requirements – Approved TR Architecture Part 1 – Approved TR Architecture Part 2 – Approved TR Management Capability Enablement Technologies TR Analysis of Security Solutions Work continuing on 6 Technical Reports and 9 Technical Specifications Target date for first package of specifications – August 2014 GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Work programme V1.0.0 TP#12 V1.1.0 TP#15 GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Development timeline Package aubergine version 1.0.0 will be made available for comment via the public-facing web site (http://www.oneM2M.org) between TP #12 and TP #15, to Members, Partners Type 2, and to others not currently participating in oneM2M An email reflector will be established for the purpose of receiving comments At TP #15, approved CRs are applied to aubergine and the package is approved as version 1.1.0, and ratified Between TP #12 and TP #15, work is expected to ramp up on an updated package (lime) to include new functionality GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis oneM2M Showcase 09 – 11 December 2014: ETSI M2M Workshop 09 December 2014 : oneM2M Showcase Preliminary concept Session 1: Set the Stage - Business Focus Session 2: Event Introduction & Technical Overview Session 3: Showcase Sessions (#1 - #3) Session 4: Chairs panel Session 4: Showcase Sessions (#4 - #6) Panel - Wrap-up Note: Showcase Exhibits remain open for the whole Workshop GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Showcase objectives Demonstrations will clearly illustrate the capabilities of the oneM2M Service Layer Platform and have the following objectives: One Business Application can access different devices and/or data through flexible access rights allocation Cross-Sector dialogue: efficient use of data (storage/transmission) as different Applications can commonly access to the same device data through flexible access rights allocation Interworking between multiple oneM2M Service Layer Platforms oneM2M Service Layer Platform provides functions for M2M applications across different industry segments Creating Business Applications using the standardized oneM2M Service Layer Platform needs low investment and development time to access data (including access control) Sharing of components and infrastructure leads to lower investments GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis Supplementary Slides GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis M2M Service Layer Middleware - supporting secure end-to-end data/control exchange between M2M devices and customer applications by providing functions for provisioning & activation, security, connectivity, buffering, aggregation, device management, etc. a software layer / “Platform”: CSE=Common Services Entities sits between M2M applications and communication HW/SW normally rides on top of IP provides functions that M2M applications across different industry segments commonly need => horizontal layer GSC-18, 22-23 July 2014, Sophia Antipolis

GSC-18, 22-23 July 2014, Sophia Antipolis oneM2M DELIVERABLES published WI TS / TR Name 0001 TR 0001 oneM2M Use Case collection TS 0002 M2M Requirements 0002 TR 0002 Part 1: Analysis of the architectures proposed for consideration by oneM2M TR 0003 Part 2 Study for the merging of architectures proposed for consideration by oneM2M TS 0001 M2M Architecture 0003 TR 0004 Definitions and Acronyms 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 TS 0003 oneM2M Security Solutions 0008 TR 0009 oneM2M Protocol Analysis 0009 TS 0004 oneM2M Protocol Technical Specification 0010 TS 0005 oneM2M Management Enablement (OMA) 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 Specification 0014 TS 0010 MQTT Protocol Binding Technical Specification TR 0011 MQTT Protocol Interworking Study TS 0001 - CR Architecture changes for interworking GSC-18, 22-23 July 2014, Sophia Antipolis