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 Changes shown: underline = new text 2

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

4. Motivators oneM2M believes that [the Audience] would like to see improvements in 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 Flexibility of deployment details – 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 oneM2M aims to reduce cost while improving the quality, choice and opportunities of [the Audience] by standardizing a set of commonly-needed, M2M-communication-specific capabilities that incorporate the necessary interactions with transport-layer functions. OLD: 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. Easy-to-digest description of oneM2M Figure & text showing relationship between – Applications – oneM2M Technology – Transports Should not imply an architecture 7

8. BENEFITS OF ONEM2M Standardization and New Functionality 8

9. Preamble oneM2M believes that it can provide value to [the Audience] simply by “standardizing a set of commonly-needed, M2M-communication- specific capabilities that incorporate the necessary interactions with transport-layer functions” (see next slide) However, oneM2M believes that it can provide additional value to [the Audience] by providing new functionality directly addressing the [Audience] Motivators.Motivators 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, these functionalities should be considered “potential functionalities”. Feedback from [the Audience] on the potential functionalities will be valuable in helping oneM2M prioritize its work. 9

10. 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 commonly-needed, M2M-communication-specific capabilities that incorporate the necessary interactions with transport-layer functions lets M2M Application stakeholders choose of transport products and services independent of other decisions. Specifying commonly-needed, M2M-communication-specific capabilities enhance the economies of scale, reducing costs of products and services Specifying commonly-needed, M2M-communication-specific capabilities 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] 10

11. Overview of Functionalities Exposed? M2M Functions (available to End User/Devices) – Sharing Data [and Sharing Components/Devices?] – Content-Aware Processing – Security Framework & Access Control – Remote Device Management Hidden? Transport-Aware Functions – Transport Efficiency Features – Transport Reliability Features 11

12. Benefits of Functionalities Sharing data and Content-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 Content-Aware processing can also reduce traffic volume. This reduction of traffic volume, in combination with Transport efficiency features & Transport reliability features can – enable better battery life, reducing costs – result in less load on Transport resources, reducing costs of transport products and services Transport reliability features can translate to improved quality of the end product. Transport reliability features can also lower load on Transport resources, reducing costs of transport products and services Remote device management can reduce call-outs (reducing OPEX) and increase the reliability (that is, quality) of [the Audience’s] end products – For example, faults can be triaged and corrected remotely before products fail to the point of requiring a call-out 12

13. DETAILS OF ONEM2M FUNCTIONALITIES 13

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

15. Remote Device Management 15 Transport Efficiency Features Sharing Data Security Framework and Access Control Remote Device Management Improved Reliability Content-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

16. APPENDIX: TERMINOLOGY 16

17. Terminology NameDescription M2M Application (App)TBD CapabilityTBD ContentData produced or consumed by Applications Content-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 17

18. OLD SLIDES – DELETE BEFORE PUBLICATION Saved here in case they are useful in future. 18

19. Transport protocols oneM2M Functions Transport- Aware Transport Component Interface Transport- Agnostic* Interface Easy-to-digest description of oneM2M 19 Tailored Component Generic Generic Component Generic Generic Component Transport Components Tailored Component Access Network *Some functions may be transport-aware. Transport- Aware Transport Components Generic Generic Component Transport- Aware Transport Components Generic Generic Component

20. Figure by Farooq Bari, AT&T 20