1. oneM2M Partnership Project draft proposal for slide set

2. 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 2

3. 3 Founding Partners (Type 1) 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. Additional organizations are in the process of applying for a Partner status CCSA - China Communications Standards Association CHINA TTA - Telecommunications Technology Association KOREA ARIB - Association of Radio Industries and Businesses JAPAN TTC - Telecommunication Technology Committee of Japan JAPAN ASIA ETSI - European Telecommunications Standards Institute EUROPE ATIS - Alliance for Telecommunications Industry Solutions TIA - Telecommunications Industry Association NORTH AMERICA

4. 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 4

5. Partner Type 1 7 Partner Type 2 4 Member 178 Associate Member 4

6. Partners type 2 Associate members

7. 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 © 2013 oneM2M Partners oneM2M Partnership Project 7

8. Structure © 2013 oneM2M Partners oneM2M Partnership Project 8 TP (Technical Plenary) WG 1 (Requirements) WG 2 (Architecture) WG 3 (Protocols) WG 4 (Security) WG 5 (Management, Abstraction and Semantics)

9. 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 9

10. 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 10

12. Audience of this presentation M2M industry stakeholders that could possibly use and deploy oneM2M technology Integrated industry segment users of M2M solutions Examples: Healthcare provider, pipeline operator, smart meter operator, HVAC manufacturer M2M solution providers – M2M Application/Solution Developers Examples: Software/middleware developers, sensor/actuator device developers, gateway developers – M2M Service Providers E xamples: M2M service providers/M2M platform operators, network operators – M2M Solution Vendors Examples: M2M module vendors, M2M device vendors, vendors for monitoring solutions 12

13. 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 – lack of standards, seem to be major obstacles Inhibitors for large scale M2M deployments – extracts from industry reports: … a key challenge for the industry remains the complexity of developing, deploying, and managing M2M applications... This is a challenge both for mobile network operators that are trying to offer profitable services tailored to the M2M market, as well as for application developers and service providers that are trying to reduce costs, speed time to market, and simplify robust application deployments, ABI Research, M2M software platforms For many years M2M was held back by the lack of a low cost, global access medium, the fragmented nature of the ecosystem, the lack of any single killer application driving demand and the complex nature of M2M solutions leading to high-cost development and systems integration. Strategy analytics, M2M strategies 13

14. Benefits Boost M2M economies of scale and shorten time-to-market – Lower capital and operating ex – Foster and optimize future investments of all involved parties Simplify development of applications – Intra- and inter-industry integration of services – Allow same application to be used across different service platforms Leverage the worldwide network for enhanced potential of services and to expand business opportunities – Greater reach of services through broader network interoperability Reduce standardization overlap and confusion and provide ongoing standards support – Enhance interoperability – Reduce market fragmentation – Future proof services via collaboration – Enhance security and reliability 14

15. Intrinsic benefits of Standardizing Generic oneM2M Capabilities 15 Interoperable Components from multiple providers Economies of scale Large Application Development Ecosystem Large Hardware Supply Ecosystem Large Service Provider Ecosystem Improved FCQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities Note: Scalability must be designed into the system

16. DESCRIPTION OF oneM2M TECHNOLOGY 16

17. One sentence description new elevator pitch 17

18. Intrinsic benefits of Incorporating Interactions with Underlying Networks 18 Enables Simplified M2M App development by abstracting out access specific interfaces Improved FPQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities All M2M Apps can benefit from integrated qualities: e.g. secure, efficient, reliable scalable, etc. M2M App developers can leverage the Underlying Network’s capabilities in a unified way Easier to utilize a wider range of Underlying Networks

19. POTENTIAL oneM2M CAPABILITIES & THEIR BENEFITS 19

20. High Level Capabilities Connectivity Handling Capabilities – Efficient, reliable, scalable use of underlying networks Remote Device Management Capabilities – Configuration & Diagnostics of oneM2M functions Data Exchange Capabilities – Storing & sharing data between M2M Apps; event notification – Access to data: Who, what, when, why Security and Access Control Capabilities 20 # Capabilities have been grouped into these High Level Capabilities for simplified explanation – specifications might not reflect this grouping; only a preliminary set, oneM2M may define more

21. Connectivity Handling Efficient, reliable, scalable use of Underlying Networks – Delivery guidance and policies Scheduling Network selection guidance – Asynchronous Communication – Reaching device not always connected – Delivery progress reporting/confirmation – Communication Efficiency Benefits – Improved end-to-end reliability – Lower power consumption – More value extracted from underlying networks – Protection of scarce resources Example 1-1 1.Delivery guidance of sensor reading allows 24 hr delay 2.Sensor reading is held for delivery at an off-peak period Example 1-2 1.Back-End requests delivery progress reports for data sent via Device A to Device B 2.1st Report sent to Back-End when Device A receives data 3.2nd report is sent to Back- End when Device B receives data from Device A 21 Data Exchange Security and Access Control Connectivity Handling Remote Device Management

22. Managing Field from Back-End Controlling configuration of Field Devices – E.g. Settings, installation of software, updating firmware/software, provisioning Field Device Status reporting – E.g. early fault detection, performance monitoring Benefits – Reduced reliance on Field Agents – Improved quality/reliability of end-product – Scalability Example 2-1 1.Medical device is deployed to medical facility 2.Device is assigned to patient 3.Back-End provisions Device with patient-specific settings Example 2-2 1.Automatic maintenance check on HVAC unit detects fault 2.Back-End is notified of fault 3.Back-End applies further monitoring to triage fault: identifies incorrect settings 4.Back-End configures new settings, fixing fault 22 Data Exchange Security and Access Control Connectivity Handling Remote Device Management

23. Data Exchange Storing & sharing content between M2M Apps – Content Discovery – Content push/pull – Sharing between partners – Sharing while device are not reachable Event notification Semantics/ Content-awareness Benefits – Simple ways to make data available to end points Notify about and consume new data – Reduced traffic volume More value can be extracted from underlying network – New opportunities to share data & assets with partners – Scalability Example 3-1 1.Temperature sensor App generates temperature reading, stored locally 2.Back-End retrieves reading 3.HVAC unit App retrieves reading & adjusts heating/cooling level Example 3-2 1.Farmers # A & B subscribe to be notified of water level map 2.Water level map obtained 3.Farmer A & B notified 4.Only Farmer A decides to retrieve Water level map 23 # Agriculture management systems of the farmers Data Exchange Security and Access Control Connectivity Handling Remote Device Management

24. Security and Access Control Making sure the system behaves as intended Authentication Access Control Securing communications – E.g. Encryption Benefits – Protecting operation and information – Generic protocols 24 Data Exchange Security and Access Control Connectivity Handling Remote Device Management Example 4-1 1.Sensor tries to send measurement to back- end 2.Authenticates mutually with back-end 3.Requests encrypted transmission of report to back-end 4.System checks access rights 5.Delivers data to back-end

25. Summary: Benefits of Capabilities 25 Connectivity HandlingData Exchange Security and Access Control Remote Device Management Improved FPQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities Ability to share data & assets with partners Reduced traffic volume More value extracted from Underlying Networks Improved end- product quality Better power consumption Reduced Field Agent call-outs Note: Choice is an intrinsic benefit of Stds

26. FEEDBACK TEMPLATES Provided as mechanism for feedback to oneM2M 26

27. CALL TO ACTION Organizations ICT/Telecom SDO 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 http://www.onem2m.org/join.cfm

28. Feedback on High-Level Capabilities High-Level CapabilitiesPriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Data Exchange Remote Device Management Connectivity Handling Security & Access Control 28 # Capabilities have been grouped into these High Level Capabilities for simplified explanation – specifications might not reflect this grouping

29. Feedback on Connectivity Handling FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Delivery guidance Scheduling & Network selection guidance Delivery progress reporting/confirmation Communication Efficiency features 29

30. Feedback on Remote Device Management FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Controlling configuration of devices Diagnostics 30

31. Feedback on Data Exchange FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Store and Sharing content between M2M Apps Sharing between partners Content Discovery Event Notification Semantics/Content Awareness 31

32. Feedback on Security & Access Control FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Authentication Access Control Securing communications 32