1. Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR, phawkes@qti.qualcomm.com phawkes@qti.qualcomm.com Meeting Date: 2012-10-16 Agenda Item: 6 “Contributions” BENEFITS OF ONEM2M TECHNOLOGIES

2. Scope Audience: Vertical industry segment stakeholders Purpose: Trigger feedback from [the Audience] Content: Highlights potential benefits of oneM2M communication technology to [the Audience] Note: current title of presentation is a placeholder only 2

3. Outline Motivators: – Audience Priorities oneM2M intends to address Description of oneM2M Technology Benefits of oneM2M Details of Potential Functionalities Terminology 3

4. Motivators oneM2M believes that [the Audience] would like to improve the following aspects of the M2M ecosystem: – Costs: Reduce or amortize CAPEX, OPEX and Time-to-market. – Quality: transparent, certifiable quality of components & services; improved quality of the end product – Choice: Interoperable components & services from a range of providers – Opportunities: Ability to share data and resources with other stakeholders to amortize costs 4

5. DESCRIPTION OF ONEM2M TECHNOLOGY One sentence description of oneM2M technology Easy-to-digest description of oneM2M technology 5

6. One sentence description The aim of oneM2M communication technology is to standardize a set of M2M- specific transport-agnostic functions that have potential to improve the cost, quality, choice and opportunities for [the Audience]. Disclaimer: – The document is intended to be read as a broad description of how the goals of improving cost, quality, choice and opportunities might be met by technology that oneM2M is considering. – This document is not intended to be read as guidance regarding the degree of improvements (to cost, quality, choice and opportunities) that will result from oneM2M technology. 6

7. Transport protocols oneM2M protocols Transport Component Interface Transport- Agnostic Features Easy-to-digest description of oneM2M 7 Field App Cloud App oneM2M Component Transport Components

8. Easy-to-digest description of oneM2M Text showing relationship between – Applications – oneM2M Technology – Transports 8

9. BENEFITS OF ONEM2M Standardization and New Functionality 9

10. Preamble oneM2M believes that it can provide value to [the Audience] simply by standardizing transport-agnostic and vertical-agnostic protocols and components (see next slide) However, oneM2M believes that it can provide additional value to [the Audience] by providing new functionality. This document lists many functionalities oneM2M is considering. At this point in time, none of these functionalities are specified and oneM2M is currently evaluating the priority of these functionalities for the upcoming release. Some functionalities may be deferred to future oneM2M releases, or may never be included in oneM2M specifications. For the time being, we call these “potential functionalities”. Feedback from [the Audience] on the potential functionalities will be valuable in helping oneM2M prioritize its work. 10

11. Benefits of Standardization Standardizing interoperable components will enable certifiable quality of components Standardizing interoperable components enables a choice of providers of components (both software and hardware) and services. Specifying Transport-agnostic and Vertical-agnostic protocols & components lets M2M Application stakeholders choose of transport products and services independent of other decisions. Specifying Transport-agnostic and vertical-agnostic components enhance the economies of scale, reducing costs of products and services Specifying Transport-agnostic and vertical-agnostic components allows the growth of a extensive application development ecosystem reducing cost of application development and lifecycle and improved quality of the end product [Some text imported from oneM2M-REQ-2012-0013] 11

12. Overview of Potential Functionalities Sharing Data [and Sharing Components/Devices?] Security Framework & Access Control Context-Aware Processing Transport Efficiency Features Improved Reliability (of communications) Remote Device Management 12

13. Benefits of Potential Functionalities Sharing data and Context-Aware processing provides opportunities to partner with other stakeholders to amortize costs, protected by Access Control over your data supported by a strong Security framework Sharing data and Context-Aware processing also reduces traffic volume. This reduction of traffic volume, in combination with Transport efficiency features – enables better battery life, reducing costs – results in less load on Transport resources, reducing costs of transport products and services Improved reliability of communications translates to improved quality of the end product Remote device management reduces call-outs (reducing OPEX) and increases the reliability of your end products – For example, faults can be triaged and corrected remotely before products fail to the point of requiring a call-out 13

14. DETAILS OF THE POTENTIAL FUNCTIONALITIES 14

15. Transport Efficiency Features 15 Scheduling E.g. Store and Forward Remote Session Triggering Transport Efficiency Features Sharing Data Security Framework and Access Control Remote Device Management Improved Reliability Context-Aware Processing

16. Remote Device Management 16 Transport Efficiency Features Sharing Data Security Framework and Access Control Remote Device Management Improved Reliability Context-Aware Processing Reporting Data from Devices Controlling Data on Devices Log Reports Fault Reports Performance Reports Reporting Configuration Settings Updating Configurations Managing Software & Firmware Adding new Software (E.g. Applications) Software/Firmware updates Removing Software Maintenance Reporting

17. APPENDIX: TERMINOLOGY 17

18. Terminology NameDescription M2M Application (App)TBD ContentData produced or consumed by Applications Context AwareAware of the data model and/or semantics of Content GenericNot specific to any M2M Application or vertical segment oneM2M communication technology Components and protocols conforming to oneM2M specifications TransportTBD 18