oneM2MDraft proposal for slide set

This is not intended to be a oneM2M presentation.

It is a collection of source material slides which can be used by presenters who are putting together a presentation

More sections and slides will be added as the slides are created.

Introduction

• On July 24, 2012 seven of the world’s leading ICT Standards Development Organizations (SDOs) launched a new global organisation: the oneM2M Partnership Project: http://www.oneM2M.org to: – cooperate in the production of globally applicable, access-

independent M2M Service Layer specifications, including Technical Specifications and Technical Reports related to M2M Solutions and

– ensure the most efficient deployment of machine to machine (M2M) communications systems

© 2014 oneM2M PartnersoneM2M Global Partnership

3

4

Founding Partners (Type 1)

In addition BroadBand Forum, Personal Connected Health Alliance (Continua), Home Gateway Initiative, the Open Mobile Alliance and Next Generation M2M Forum have been accepted as a oneM2M Partners Type 2. Additional organizations are in the process of applying for a Partner status

Participation

• There are 4 levels of participation:– Partner Type 1– Partner Type 2– Member– Associate Member

• Further details can be found:• in the oneM2M Partnership agreement or• http://www.onem2m.org/join.cfm © 2014 oneM2M Partners

oneM2M Global Project5

Partners Type 2

• Broadband Forum• Home Gateway Initiative• Next Generation M2M • Open Mobile Alliance• Personal Connected Health Alliance (Continua)

Associate members

• Ministry of Science, ICT and Future Planning (MSIP) (Korea)• National Institute of Standards and Technology (NIST) (USA)• United States Department of Transportation (USA)

Scope & Objectives• 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© 2014 oneM2M Partners

oneM2M Global Project8

Structure

© 2014oneM2M PartnersoneM2M Global Project

9

Deliverables• WG1 - Requirements

– oneM2M Use cases collection (TR) (Approved)– Definitions and Acronyms (TS) (Approved)– Roles and Focus Areas (TR)– oneM2M Requirements (TS) (Approved)

• WG2 - Architecture – Analysis of the architectures for transfer to oneM2M (TR)

(Approved)– Study for the merging of the architectures proposed for transfer to

oneM2M and resolve critical potential gaps (TR) (Approved)– One M2M Functional Architecture (TS) (Approved)– oneM2M Service Components (TS)

© 2014 oneM2M Partners

oneM2M Global Project10

Deliverables• WG3 - Protocols

– oneM2M Protocols Analysis (TR) (Approved)– MQTT Protocol Interworking Study (TR) – oneM2M Protocol Technical Specification (TS)– COAP Protocol Binding (TS)– HTTP Protocol Binding (TS)– MQTT Protocol Binding (TS)

• WG4 - Security – Analysis of Security Solutions for the oneM2M System (TR)

(Approved)– oneM2M Security Solutions (TS) (Approved)

© 2014 oneM2M Partners

oneM2M Global Project11

Deliverables

• WG 5 – Management, Abstraction and Semantics

– Study of Management Capability Enablement Technologies for Consideration by oneM2M (TR) (Approved)

– oneM2M Abstraction and Semantics Capability Enablement (TR) (Approved)

– oneM2M Device / Gateway Classification (TS)– oneM2M Management Enablement (OMA) (TS)– oneM2M Management Enablement (BBF) (TS)

© 2014 oneM2M Partners

oneM2M Global Project12

Request for Comment1. TS 0001 - M2M Architecture2. TS 0002 - M2M Requirements3. TS 0003 - oneM2M Security Solutions4. TS 0004 - oneM2M Protocol Technical Specification5. TS 0005 - oneM2M Management Enablement (OMA)6. TS 0006 - oneM2M Management Enablement (BBF)7. TS 0008 - CoAP Protocol Binding Technical Specification8. TS 0009 - HTTP Protocol Binding Technical Specification9. TS 0011 - Definitions and Acronyms

1. TS 0001 - M2M Architecture2. TS 0002 - M2M Requirements3. TS 0003 - oneM2M Security Solutions4. TS 0004 - oneM2M Protocol Technical Specification5. TS 0005 - oneM2M Management Enablement (OMA)6. TS 0006 - oneM2M Management Enablement (BBF)7. TS 0008 - CoAP Protocol Binding Technical Specification8. TS 0009 - HTTP Protocol Binding Technical Specification9. TS 0011 - Definitions and Acronyms

http://www.onem2m.org/candidate_release/index.cfm

The public comment phase will end 01st Nov 2014 and this candidate release of oneM2M specifications will be updated for approval by the oneM2M Technical Plenary

in January 2015 for publication by the oneM2M Partners.

Dates to note:

• TP 13 22-26 October 2014 Phoenix USA• TP 14 10-14 November 2014 Korea• TP 15 19-23 January 2015 USA• TP 16 16-20 March Europe• TP 17 18-22 May Japan• TP 18 20-24 July USA• TP 19 07 11 Sept Europe• TP 20 16-20 November China

09th - 11th Dec 2014 in Sophia Antipolis France : oneM2M showcase and M2M workshop.

http://www.etsi.org/M2MWORKSHOP

14

15

Invitation

OrganizationsICT/Telecom SDOOthers standards and specifications setting organizationsIndustry groupsAssociationsSpecific technology organizations

Individual CompaniesService 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

http://www.onem2m.org/join.cfm

Contacts

• For general enquiries please do not hesitate to contact the oneM2M Secretariat at: oneM2M_Contact@list.oneM2M.org

• For a more detailed contact list please refer to this web page: http://www.onem2m.org/contact.cfm

© 2014 oneM2M Partners

oneM2M Global Project16