CURRENT STANDARDIZATION ACTIVITIES – ONEM2M GSC-18 Meeting, July 2014, Sophia Antipolis, France Document No: GSC(14)18_012 Source: ETSI Contact: Joachim Koss, Agenda Item: 5.3 Joachim Koss, Director Standardisation M2M, Gemalto, ETSI Board Member

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, July 2014, Sophia Antipolis2

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, July 2014, Sophia Antipolis3

HORIZONTAL PLATFORM VISION 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, July 2014, Sophia Antipolis4 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.

WHERE WE ARE (JULY 2014) Partner Type 17 partners Partner Type 2 4partners ARIB 12 members ATIS 15members CCSA 18members ETSI120members TIA 23members TTA 13members TTC 5members Associates Members3 associate members Total220 organizations involved in oneM2M GSC-18, July 2014, Sophia Antipolis5

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

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, July 2014, Sophia Antipolis7

WORK PROGRAMME GSC-18, July 2014, Sophia Antipolis8

DEVELOPMENT TIMELINE Package aubergine version will be made available for comment via the public-facing web site ( between TP #12 and TP #15, to Members, Partners Type 2, and to others not currently participating in oneM2Mhttp:// An 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, July 2014, Sophia Antipolis9

ONEM2M SHOWCASE 09 – 11December 2014: ETSI M2M Workshop 09December 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, July 2014, Sophia Antipolis10

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, July 2014, Sophia Antipolis11

GSC-18, July 2014, Sophia Antipolis Supplementary Slides 12

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, July 2014, Sophia Antipolis13

ONEM2M DELIVERABLES GSC-18, July 2014, Sophia Antipolis14 WITS / TRName 0001TR 0001oneM2M Use Case collection 0001TS 0002M2M Requirements 0002TR 0002Part 1: Analysis of the architectures proposed for consideration by oneM2M 0002TR 0003Part 2 Study for the merging of architectures proposed for consideration by oneM2M 0002TS 0001M2M Architecture 0003TR 0004Definitions and Acronyms 0003TR 0005Roles and Focus Areas 0004TR 0006Study of Management Capability Enablement Technologies for Consideration by oneM2M 0005TR 0007oneM2M Abstraction and Semantics Capability Enablement 0006TR 0010oneM2M Device / Gateway Classification 0007TR 0008Analysis of Security Solutions for the oneM2M System 0007TS 0003oneM2M Security Solutions 0008TR 0009oneM2M Protocol Analysis 0009TS 0004oneM2M Protocol Technical Specification 0010TS 0005oneM2M Management Enablement (OMA) 0010TS 0006oneM2M Management Enablement (BBF) 0011TS 0007oneM2M Service Components 0012TS 0008CoAP Protocol Binding Technical Specification 0013TS 0009HTTP Protocol Binding Technical Specification 0014TS 0010MQTT Protocol Binding Technical Specification 0014TR 0011MQTT Protocol Interworking Study 0014TS CRArchitecture changes for interworking published