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

2. Audience of this presentation M2M industry stakeholders that could possibly use and deploy oneM2M technology Vertically integrated industry segment users of M2M solutions Examples: Healthcare provider, pipeline operator, smart meter operator, HVAC manufacturer M2M solution providers – M2M Application/Solution Developers Examples: Software/middleware developers, sensor/actuator device developers, gateway developers – M2M Service Providers E xamples: M2M service providers/M2M platform operators, network operators – M2M Solution Vendors Examples: M2M module vendors, M2M device vendors, vendors for monitoring solutions 2

3. Outline Current State of Affairs Motivators: – M2M industry segment stakeholders’ priorities oneM2M intends to address Description of oneM2M Technology – Simple description – Intrinsic benefits of oneM2M standardization effort Potential oneM2M Capabilities and their benefits Conclusion Feedback Template 3

4. Current state of affairs M2M has been around for several decades now – some deployments date back more than 20 years. However M2M markets are struggling to realise the full M2M market potential Fragmentation, provisioning, efficiency, integration complexity, scalability – and – lack of standards, seem to be major obstacles Inhibitors for large scale M2M deployments – extracts from industry reports: … a key challenge for the industry remains the complexity of developing, deploying, and managing M2M applications... This is a challenge both for mobile network operators that are trying to offer profitable services tailored to the M2M market, as well as for application developers and service providers that are trying to reduce costs, speed time to market, and simplify robust application deployments, ABI Research, M2M software platforms For many years M2M was held back by the lack of a low cost, global access medium, the fragmented nature of the ecosystem, the lack of any single killer application driving demand and the complex nature of M2M solutions leading to high-cost development and systems integration. Strategy analytics, M2M strategies 4

5. Motivators M2M industry stakeholders’ priorities oneM2M aims to address – Improved Functionality-Cost-Quality (FCQ) tradeoffs Investment and Time-to-market: Sourcing, developing and integrating Components of your M2M solutions Efficient administration and management – Greater Choice Range of providers from which you can source Components of your M2M solutions Range of providers who can develop and integrate Components of your M2M solutions – Greater Opportunities E.g. ability to share data and other assets by partnering with other stakeholders. – Enhanced Scalability 5

6. Intrinsic benefits of Standardizing Generic oneM2M Capabilities 6 Interoperable Components from multiple providers Economies of scale Large Application Development Ecosystem Large Hardware Supply Ecosystem Large Service Provider Ecosystem Improved FCQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities Note: Scalability must be designed into the system

7. DESCRIPTION OF ONEM2M TECHNOLOGY 7

8. One sentence description oneM2M aims to enable improved Functionality-Cost-Quality tradeoffs of future end-to-end M2M solutions, whilst providing scalability, greater choices and opportunities for M2M industry stakeholders by standardizing a set of valuable, generic M2M-communication Capabilities that incorporate the necessary interactions with Underlying Networks. 8

9. Interface to capabilities Simple Visual Model 9 M2M App oneM2M Service Layer Capabilities Underlying Network Capabilities

10. Intrinsic benefits of Incorporating Interactions with Underlying Networks 10 Enables Simplified M2M App development by abstracting out access specific interfaces Improved FPQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities All M2M Apps can benefit from integrated qualities: e.g. secure, efficient, reliable scalable, etc. M2M App developers can leverage the Underlying Network’s capabilities in a unified way Easier to utilize a wider range of Underlying Networks

11. POTENTIAL ONEM2M CAPABILITIES & THEIR BENEFITS 11

12. High Level Capabilities # Connectivity Handling Capabilities – Efficient, reliable, scalable use of underlying networks Remote Device Management Capabilities – Configuration & Diagnostics of oneM2M functions Data Exchange Capabilities – Storing & sharing data between M2M Apps; event notification – Access to data: Who, what, when, why Security and Access Control Capabilities 12 # Capabilities have been grouped into these High Level Capabilities for simplified explanation – specifications might not reflect this grouping; only a preliminary set, oneM2M may define more

13. Connectivity Handling Efficient, reliable, scalable use of Underlying Networks – Delivery guidance and policies Scheduling Network selection guidance – Asynchronous Communication – Reaching device not always connected – Delivery progress reporting/confirmation – Communication Efficiency Benefits – Improved end-to-end reliability – Lower power consumption – More value extracted from underlying networks – Protection of scarce resources Example 1-1 1.Delivery guidance of sensor reading allows 24 hr delay 2.Sensor reading is held for delivery at an off-peak period Example 1-2 1.Back-End requests delivery progress reports for data sent via Device A to Device B 2.1st Report sent to Back-End when Device A receives data 3.2nd report is sent to Back- End when Device B receives data from Device A 13 Data Exchange Security and Access Control Connectivity Handling Remote Device Management

14. Managing Field from Back-End Controlling configuration of Field Devices – E.g. Settings, installation of software, updating firmware/software, provisioning Field Device Status reporting – E.g. early fault detection, performance monitoring Benefits – Reduced reliance on Field Agents – Improved quality/reliability of end-product – Scalability Example 2-1 1.Medical device is deployed to medical facility 2.Device is assigned to patient 3.Back-End provisions Device with patient-specific settings Example 2-2 1.Automatic maintenance check on HVAC unit detects fault 2.Back-End is notified of fault 3.Back-End applies further monitoring to triage fault: identifies incorrect settings 4.Back-End configures new settings, fixing fault 14 Data Exchange Security and Access Control Connectivity Handling Remote Device Management

15. Data Exchange Storing & sharing content between M2M Apps – Content Discovery – Content push/pull – Sharing between partners – Sharing while device are not reachable Event notification Semantics/ Content-awareness Benefits – Simple ways to make data available to end points Notify about and consume new data – Reduced traffic volume More value can be extracted from underlying network – New opportunities to share data & assets with partners – Scalability Example 3-1 1.Temperature sensor App generates temperature reading, stored locally 2.Back-End retrieves reading 3.HVAC unit App retrieves reading & adjusts heating/cooling level Example 3-2 1.Farmers # A & B subscribe to be notified of water level map 2.Water level map obtained 3.Farmer A & B notified 4.Only Farmer A decides to retrieve Water level map 15 # Agriculture management systems of the farmers Data Exchange Security and Access Control Connectivity Handling Remote Device Management

16. Security and Access Control Making sure the system behaves as intended Authentication Access Control Securing communications – E.g. Encryption Benefits – Protecting operation and information – Generic protocols 16 Data Exchange Security and Access Control Connectivity Handling Remote Device Management Example 4-1 1.Sensor tries to send measurement to back- end 2.Authenticates mutually with back-end 3.Requests encrypted transmission of report to back-end 4.System checks access rights 5.Delivers data to back-end

17. Summary: Benefits of Capabilities 17 Connectivity HandlingData Exchange Security and Access Control Remote Device Management Improved FPQ Tradeoffs Enhanced Scalability Greater Choice Greater Opportunities Ability to share data & assets with partners Reduced traffic volume More value extracted from Underlying Networks Improved end- product quality Better power consumption Reduced Field Agent call-outs Note: Choice is an intrinsic benefit of Stds

18. FEEDBACK TEMPLATES Provided as mechanism for feedback to oneM2M 18

19. Feedback on High-Level Capabilities # High-Level CapabilitiesPriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Data Exchange Remote Device Management Connectivity Handling Security & Access Control 19 # Capabilities have been grouped into these High Level Capabilities for simplified explanation – specifications might not reflect this grouping

20. Feedback on Connectivity Handling FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Delivery guidance Scheduling & Network selection guidance Delivery progress reporting/confirmation Communication Efficiency features 20

21. Feedback on Remote Device Management FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Controlling configuration of devices Diagnostics 21

22. Feedback on Data Exchange FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Store and Sharing content between M2M Apps Sharing between partners Content Discovery Event Notification Semantics/Content Awareness 22

23. Feedback on Security & Access Control FeaturePriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Authentication Access Control Securing communications 23

24. APPENDICES Terminology 24

25. Terminology NameDescription M2M Application (App)TBD Back-EndTBD CapabilityThe ability to provide a set of outcome ComponentHardware, software and services comprising an M2M solution ContentData produced or consumed by Applications Content-AwareAware of the data model and/or semantics of Content Field AgentA person performing “in situ” management of Field Devices Field DevicesRemote Devices GenericCommon to two or more applications or vertical segments Underlying networksAccess networks, core networks, busses and other technology assisting in data transport 25