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-11 Agenda Item: 6 “Contributions” ALTERNATIVE INITIAL TEXT FOR BENEFITS PRESENTATION

2. Scope Audience: oneM2M Partners and Members Purpose: use to trigger feedback from vertical industry segment stakeholders Content: highlights potential benefits of oneM2M communication technology to vertical industry segment stakeholders 2

3. Outline Description Benefits Terminology 3

4. DESCRIPTION One sentence description of oneM2M Easy-to-digest description of oneM2M 4

5. One sentence description The aim of oneM2M communication technology is to enable cost savings for M2M Application stakeholders 5

6. Easy-to-digest description of oneM2M Text & Figure showing relationship between – Applications – M2M Service Layer – Transport 6

7. BENEFITS High Level View of Benefits More Details of Benefits 7

8. High level view of Benefits 8 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports Less load on Transport Resources, Lower OPEX, Better battery life Economies of Scale, Reliability Lower development costs

9. Reusable Components 9 Efficient Use of Transports Common Common Functionality supporting efficient use of transport Reusable App Components Cost Savings Simplified Application Development Reusable Service Layer Components Reusable Device Management Components Common Common App-to-App Security Framework Common Common Remote Device Management Framework

10. Common Common Functionality Efficient Use of Transports 10 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports Optimal use of Transport Resources Scheduling E.g. Store and Forward Remote Session Triggering Reducing number of exchanges Content Sharing Reliability Content Grouping & Filtering Reducing size of exchanges Transmitting only essential data Compact Representation Context-Aware Intelligent Processing Access Control Service-to-Service & App-to-Service Security Frameworks Service layer takes care of Transport details

11. Simplified App Development 11 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports Developers can focus on developing & enhancing features of their Apps Service layer takes care of Transport details Developers expertise is reusable across multiple Apps Common Common App-to-App Security Framework Common Common Remote Device Management Framework

12. Details of Common Remote Device Management Framework 12 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports 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 Generic Remote Device Management Framework

13. APPENDIX: TERMINOLOGY Name(s) for whole or part of a oneM2M system 13

14. Terminology NameDescription M2M Application (App)TBD CommonStandardized, Generic and Transport-Agnostic 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 M2M Service LayerTBD oneM2M communication technology Components and protocols conforming to oneM2M specifications TransportTBD 14