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-23 Agenda Item: 7 “Contributions” BENEFITS OF ONEM2M TECHNOLOGIES

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

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] wants improvements in the following aspects of the M2M ecosystem: – Improved Functionality-Price-Quality (FPQ) tradeoffs: [The Audience] would like improved FPQ tradeoffs in sourcing, development and integration of the components comprising their M2M solutions “Price” includes impact of CAPEX, OPEX and Time-to-market [1] – Improved Scalability: Scales to large deployments – Improved Choice: [The Audience] would like a range of providers from which to source components comprising their M2M solutions [The Audience] would like a range of options for structuring their deployment – Improved Opportunities: For example, [the Audience] would like the ability to share data and other resources by partnering with other stakeholders. By-products include improved FPQ tradeoffs and new revenue streams 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 enable improved Functionality-Price-Quality tradeoffs of future end to end M2M solutions, whilst providing scalability, greater choices and opportunities for [the Audience] by standardizing a set of valuable, generic M2M-communication capabilities that incorporate the necessary interactions with underlying networksgeneric Note – oneM2M believes that it can provide value to [the Audience] simply by “standardizing a set of … generic M2M-communication capabilities that incorporate the necessary interactions with underlying networks” (see this slide)this slide – oneM2M also believes that it can provide additional benefit to [the Audience] by providing “valuable… M2M-communication capabilities” that directly address the [Audience] Motivators.Motivators 6

7. Easy-to-digest description of oneM2M Figure & text showing relationship between – Applications – oneM2M Technology – Underlying Networks Should not imply an architecture 7

8. BENEFITS OF ONEM2M CAPABILITIES Standardization and New Functionality 8

9. Disclaimers 1.The document is intended to be read as a broad description of how the goals of “[improving] the FPQ tradeoffs, choices and partnering opportunities available to [the Audience]” 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 “the FPQ tradeoffs, choices and partnering opportunities available to [the Audience]” ) that will result from oneM2M technology. 2.This document lists many capabilities that oneM2M is considering. At this point in time, none of these capabilities are specified and oneM2M is currently evaluating the priority of these capabilities for the upcoming release. Some capabilities may be deferred to future oneM2M releases, or may never be included in oneM2M specifications. For the time being, these capabilities should be considered “potential capabilities”. Feedback from [the Audience] on the potential capabilities will be valuable in helping oneM2M prioritize its work. 9

10. Benefits of Standardization Standardization will provide specifications that can be used as the basis for certifying the quality of Components specified by oneM2M. This results in improved quality (improving the FPQ tradeoffs) available to [the Audience].Componentsimproving the FPQ tradeoffs – Note: at the time of writing, it is not clear if oneM2M will provide certification. Even if oneM2M does not provide the certification, one or more other groups may certify against part or all of the oneM2M specifications. Standardization enables multiple providers to produce interoperable Components. This provides [the Audience] with a range of providers from which to source components comprising their M2M solutions (improving choice).Componentsimproving choice Standardization enhances the economies of scale, improving the FPQ tradeoffs improved FPQ tradeoffs in sourcing, development and integration of the components comprising their M2M solutionsimproving the FPQ tradeoffs 10

11. Benefits of Standardization (2) Specifying “generic … capabilities… that incorporate the necessary interactions with underlying network” provides [the Audience] with a wider range of options for the underlying network, and the choice of underlying network can be made independently of other decisions (improving choice).improving choice Specifying “a set of valuable, generic M2M- communication capabilities” allows the growth of a extensive application development ecosystem improving the FPQ tradeoffs of the application development and lifecycle [Some text imported from oneM2M-REQ-2012-0013] improving the FPQ tradeoffs 11

12. Overview of Capabilities Sharing Content-Aware Processing Security Framework & Access Control Remote Device Management Communication Efficiency Features Communication Reliability Features 12

13. Benefits of Capabilities Sharing 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 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 13

14. Benefits of Capabilities Sharing and Content-Aware processing provides opportunities to partner with other stakeholders (additionally improving FPQ tradeoffs), protected by Access Control over your data supported by a strong Security framework Sharing and Content-Aware processing can also reduce traffic volume. This reduction of traffic volume, in combination with Communication Efficiency & Reliability features can – enable better battery life, improving FPQ tradeoffs – result in less load on Transport resources, improving FPQ tradeoffs of transport products and services Communication reliability features can translate to improved quality of the end product (improving FPQ tradeoffs). Communication reliability features can also lower load on Transport resources, improving FPQ tradeoffs of transport products and services Remote device management can reduce call-outs and increase the reliability (that is, quality), improving FPQ tradeoffs 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 14

15. DETAILS OF ONEM2M CAPABILITIES 15

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

17. Remote Device Management 17 Communication Efficiency Sharing Data Security Framework and Access Control Remote Device Management Communication 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

18. APPENDICES: Terminology References 18

19. Terminology NameDescription M2M Application (App)TBD CapabilityTBD ComponentHardware, software and services that combine to produce an M2M solution ContentData produced or consumed by Applications Content-AwareAware of the data model and/or semantics of Content GenericCommon to two or more applications or vertical segments Underlying networksAccess networks, core networks, busses and other technology assisting in data transport 19

20. References 1.“oneM2M Standardization”, 2012-04-24. Available from ftp://ftp.onem2m.org/Primary_Deliverables/ Material_for_Verticals/oneM2M Standardization_2012-04-24.zip ftp://ftp.onem2m.org/Primary_Deliverables/ Material_for_Verticals/oneM2M Standardization_2012-04-24.zip 20

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

22. Underlying Networks Interface to capabilities Easy-to-digest description of oneM2M 22 M2M App oneM2M Capabilities

23. Figure by Farooq Bari, AT&T 23