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

2. Scope 2 Audience: Vertical industry segment stakeholders Purpose: Trigger feedback from you on oneM2M requirements Duration: 1 hr presentation (including questions, but not including generating feedback) Content: – Highlight potential benefits oneM2M communication technology can provide to you – Provides avenue for feedback on requirements Note: current title of presentation is a placeholder only

3. Outline Current State of Affairs Motivators: – Vertical stakeholder 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 4 Fragmented market Niche products and solutions Custom design, custom engineering Various industry segments reproducing effort in order to solve their own problems Etc. NOTE: This slide should provide a pre-frame for the rest of the discussion. Describe what oneM2M participants see in the marketplace. This then leads to motivators. [CALL FOR VOLUNTEER(S) TO COMPLETE!]

5. Motivators [Audience] priorities oneM2M aims to address – Improved Functionality-Price-Quality (FPQ) 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. DESCRIPTION OF ONEM2M TECHNOLOGY One sentence description of oneM2M technology Easy-to-digest description of oneM2M technology 6

7. 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 Networks. 7

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

9. Underlying Networks Interface to capabilities Example only 9 M2M App oneM2M Capabilities

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

11. Intrinsic benefits of Incorporating Interactions with Underlying Networks 11 Enables Simplified M2M App development with access independent view 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 M2M- specific capabilities in a unified way Easier to utilize a wider range of Underlying Networks

12. POTENTIAL ONEM2M CAPABILITIES & THEIR BENEFITS 12

13. Goal of this document Previous Section: – Intrinsic benefits that are independent of the capabilities that oneM2M chooses to support Objective of document – oneM2M wants feedback on requirements regarding what oneM2M technology should be capable of – That is, feedback on potential capabilities, to help prioritize its work This section: – Some potential capabilities & their benefits 13

14. High Level Capabilities # Sharing Capabilities – Storing & sharing content between M2M Apps; event notification – Who, what, when, why Remote device management Capabilities – Configuration & Diagnostics Communication control Capabilities – Efficient, reliable, scalable use of underlying networks Security and Access Control Capabilities 14 # Capabilities have been grouped into these High Level Capabilities for simplified explanation – specifications might not reflect this grouping

15. Sharing Storing & sharing content between M2M Apps – Sharing between partners – Content Discovery Event notification Semantics/ Content- awareness Benefits – Reduced traffic volume More value can be extracted from underlying network – New opportunities to share data & assets with partners – Scalability Example 1-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 1-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 Sharing Security and Access Control Communication Control Remote Device Management # Agriculture management systems of the farmers

16. Remote Device Management Managing Field from Back-End Controlling configuration of Field Devices – E.g. Settings, installation of software, updating firmware/software, provisioning Diagnostics – 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 16 Sharing Security and Access Control Communication Control Remote Device Management

17. Communication Control Efficient, reliable, scalable use of Underlying Networks – Delivery guidance – Network Selection & Scheduling – Delivery progress reporting/confirmation – Communication Efficiency Benefits – Improved end-to-end reliability – Lower power consumption – More value extracted from underlying networks Example 3-1 1.Delivery guidance of sensor reading allows 24 hr delay 2.Sensor reading is held for delivery at an off-peak period Example 3-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 17 Sharing Security and Access Control Communication Control Remote Device Management

18. 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 Examples?? [Editor: I suspect that it will be difficult to have security examples that do not imply an architecture. Suggestions welcome!] 18 Sharing Security and Access Control Communication Control Remote Device Management

19. Summary: Benefits of Capabilities 19 Communication ControlSharing 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

20. Conclusion Summary – Why? FPQ tradeoff, scalability, choice, quality – How? Standardizing valuable generic M2M Capabilities integrated with underlying networks – Outline: Potential Capabilities & Benefits What do we want from you? – Feedback on these potential Capabilities in order to help oneM2M prioritize its work 20

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

22. Feedback on Motivators MotivatorPriority (0=Low, 10 = Critical) Comments (E.g. clarification audience requirements) 20142015+ Improved Functionality, Price, Quality Tradeoffs Enhanced Scalability Greater Choice Greater Opportunity 22

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

24. Feedback on Sharing 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 24

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

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

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

28. APPENDICES Terminology 28

29. 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 29

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

31. Figure by Farooq Bari, AT&T 31

32. Figure by Tim Carey, ALU 32

33. Summary of Capabilities Capability Features SharingSharing of content between M2M Applications. Support for sharing with partners. Content is opaque. Standardized metadata provides control. Possible processing of visible data includes: filtering; aggregating; simple arithmetic ops (average, sum, etc.) Content-Aware Processing Sharing Capability features plus processing with varying degree of “understanding” of Content data elements: e.g. data type, data value and/or semantics. Security Framework & Access Control Provisioning, access control, authentication and security mechanisms for protecting oneM2M capabilities. Support for enabling App-to-App security. Remote Device Management Provisioning. Remote reporting from Device (e.g. for maintenance) and remote configuring (e.g. settings, software and firmware management). Communication Efficiency & Reliability Selecting and establishing connectivity on an underlying network. Scheduling communication. Delivery confirmation/progress reporting. Robustness in the presence of lossy links. Broadcast/multicast support. 33 NOTE: Initial text to explain partitioning of features.

34. Sharing Capability 34 Sharing content between M2M Apps Control via Standardized Metadata Sharing Content-Aware Processing Remote Device Management Security Framework and Access Control Content Origin Metadata Other … Content Delivery Guidance Notification Communication Control Searchable tags

35. Content-Aware Processing 35 Data-Type-Aware Procedure Language Sharing Content-Aware Processing Remote Device Management Security Framework and Access Control Data-Type-Aware Description Language Data-Type- Aware Processing Semantics- Aware Processing Semantics-Aware Procedure Language Semantics-Aware Description Language Filtering/Searching Aggregating content Simple Arithmetic Operations (sum, mean, max, min) Communication Control Editor: : I would appreciate the help of a semantics/ content- aware processing expert(s) /advocate(s) to improve this page and provide notes. Any volunteers?

36. Security Framework and Access Control 36 oneM2M-to-oneM2M class App-to-oneM2M class Sharing Content-Aware Processing Remote Device Management Security Framework and Access Control Security Framework Classes Authentication Framework Passphrase High-Entropy Key Certificate Static root of trust Dynamic root of trust App-to-App class Identity Static Identity Dynamic Identity Access Control Communication Control Editor: Does this go into too much detail? Editor: Do we need to go into further detail on access control? I think not.

37. Communication Control 37 Communication Control Sharing Content-Aware Processing Remote Device Management Security Framework and Access Control Network selection & scheduling Content Delivery Guidance Delivery confirmation /Progress reporting Communication Scalability Features

38. Remote Device Management 38 Communication Control Sharing Content-Aware Processing Remote Device Management Security Framework and Access Control 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 Provisioning

39. [TITLE TBD] Standardizing generic capabilities incorporating interactions with underlying networks has intrinsic benefit independent of how we design oneM2M Capabilities – These benefits highlighted for your information in next two slides Valuable M2M capabilities – Other benefits depend on design of Capabilities – Heart of presentation: Feedback on potential Capabilities -what will be valuable to you 39