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-09 Agenda Item: 6 “Contributions” PROPOSED 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 Generic Remote Device Management Framework Simplified Application Development Efficient Use of Transports Less load on Transport Resources, Lower OPEX, Better battery life Economies of Scale, Reliability Lower device /software lifecycle costsLower development costs

9. Alternative High level view of Benefits 9 Simplified Application Develop- ment Efficient use of Transport Cost Savings Economies of Scale Remote Device Management

10. Economies of Scale – Reusable Components 10 Reusable Components Efficient Use of Transports Standardized, Generic, Transport-agnostic service layer Reusable Apps Generic Sharing Framework Generic Context-Aware Framework Generic End-to- End Security Framework? Generic Service Layer Security Framework Cost Savings Generic Remote Device Management Framework Simplified Application Development Independent App, Service & Transport Layers Reusable Service Layer

11. Efficient Use of Transports 11 Cost Savings Economies of Scale - Reusable Components Generic Remote Device Management Framework 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 Generic Content Sharing Reliability Generic Content Grouping & Filtering Reducing size of exchanges Transmitting only essential data Compact Representation Generic Context-Aware Intelligent Processing Generic Access Control Generic Service Layer Security Framework Generic Service layer takes care of Transport details Reducing size of exchanges

12. Common Remote Device Management Framework 12 Cost Savings Reusable Components Generic Remote Device Management Framework 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

13. Simplified App Development 13 Cost Savings Reusable Components Generic Remote Device Management Framework Simplified Application Development Efficient Use of Transports Developers can focus on developing & enhancing Apps Generic, Transport-agnostic, standardized service layer with consistent API App implementation is reusable Apps interoperate w/ all Service Layers across any transport Generic Service layer takes care of Transport details

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

15. 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 M2M Service LayerTBD oneM2M communication technology Components and protocols conforming to oneM2M specifications TransportTBD 15