1. oneM2M Partnership Project

2. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners oneM2M Partnership Project 2

3. 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:http://www.oneM2M.org – 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 © 2013 oneM2M Partners oneM2M Partnership Project 3

4. Founding Partners The partnership project was founded by 7 Partner Type 1 organisations: – ARIB (Association of Radio Industries and Businesses) - Japan ARIB – ATIS (Alliance for Telecommunications Industry Standards) - USA ATIS – CCSA (China Communications Standards Association) - China CCSA – ETSI (European Telecommunications Standards Institute) - Europe ETSI – TIA (Telecommunications Industry Association) - USA TIA – TTA (Telecommunications Technology Association) - Korea TTA – TTC (Telecommunications Technology Committee) - Japan TTC © 2013 oneM2M Partners oneM2M Partnership Project 4

5. 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 oroneM2M Partnership agreement http://www.onem2m.org/join.cfm © 2013 oneM2M Partners oneM2M Partnership Project 5

6. Scope & Objectives To develop globally agreed-upon M2M end-to-end specifications using common use cases and architecture principles across multiple M2M applications to connect M2M devices with application servers worldwide with an access independent view of end-to-end services To define a Service Layer platform with high level and detailed service architecture including protocols/APIs/standard objects based on this architecture (open interfaces & protocols); focus on interoperability, test and conformance specifications Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: – Application and Service Layers – Service Layer and communication functions Security and privacy aspects (authentication, encryption, integrity verification) © 2013 oneM2M Partners oneM2M Partnership Project 6

7. Structure SC (Steering Committee) FC (Finance Committee) Marcom (Marketing & Communications) LG (Legal Group) MandP (Methods & Procedures) © 2013 oneM2M Partners oneM2M Partnership Project 7 TP (Technical Plenary) WG 1 (Requirements) WG 2 (Architecture) WG 4 (Security) WG 5 (Management, Abstraction and Semantics)

8. Deliverables WG1 - Requirements – Technical Report (TR): oneM2M Use cases collection – Technical Report (TR): Benefits of oneM2M technology – Technical Specification (TS): oneM2M Requirements WG2 - Architecture – Technical Report (TR) Part 1: Analysis of the architectures for transfer to oneM2M Part 2: Study for the merging of the architectures proposed for transfer to oneM2M and resolve critical potential gaps – Technical Specification (TS): M2M Architecture WG 4 - Security and WG 5 – Management, Abstraction and Semantics are currently drafting a new work items The target is to have a minimal deployable solution available by the end of 2013. © 2013 oneM2M Partners oneM2M Partnership Project 8

9. Contacts For general enquiries please do not hesitate to contact the oneM2M Secretariat at: oneM2M_Contact@list.oneM2M.org oneM2M_Contact@list.oneM2M.org For a more detailed contact list please refer to this web page: http://www.onem2m.org/contact.cfm http://www.onem2m.org/contact.cfm © 2013 oneM2M Partners oneM2M Partnership Project 9