group name: onem2m wg1 requirements source: phil hawkes, rapporteur “benefits of onem2m...
TRANSCRIPT
Group Name: oneM2M WG1 RequirementsSource: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
[email protected] Meeting Date: 2012-10-25Agenda Item: 7 “Contributions”
BENEFITS OF ONEM2M TECHNOLOGIES
Scope
2
• Audience: Vertical industry segment stakeholders• Purpose: Trigger feedback from [the Audience]
on oneM2M requirements• Duration: 1 hr presentation (including questions,
but not including generating feedback) • Content: – Highlights potential benefits of oneM2M
communication technology to [the Audience]– Provides avenue for feedback on requirements
• Note: current title of presentation is a placeholder only
Outline
• Motivators: – Audience Priorities oneM2M intends to address
• Description of oneM2M Technology– Simple description– Implicit Benefits of oneM2M standardization
effort• oneM2M Capabilities and Directed Benefits• Conclusion• Feedback Template
3
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!]
Motivators• [Audience] priorities oneM2M aims to address– Improved Functionality-Price-Quality (FPQ)
tradeoffs• Sourcing, developing and integrating Components• “Price” CAPEX, OPEX and Time-to-market [1]
– Enhanced Scalability – Greater Choice• Range of providers for sourcing, developing and
integrating Components– Greater Opportunities• E.g. ability to share data and other resources by
partnering with other stakeholders.
5
Editor: Francois Ennesser had comments on “Choice”. Further discussion is required.
DESCRIPTION OF ONEM2M TECHNOLOGY
One sentence description of oneM2M technologyEasy-to-digest description of oneM2M technology
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 Networks.
7
Easy-to-digest description of oneM2M
• Figure & text showing relationship between– Applications– oneM2M Technology– Underlying Networks
• Should not imply an architecture
8
Underlying Networks
Example only
9
M2M App M2M App
oneM2M Capabilities
Summary of Benefits
1. Implicit benefits– Benefits of standardizing generic
capabilities– Benefits of incorporating interactions
with underlying networks2. Directed benefits– Benefits of valuable capabilities directly
addressing the Motivators
10
Benefits of Standardizing Generic Capabilities
11
Improved FPQ Tradeoffs
Enhanced Scalability
Greater Choice
Greater Opportunities
Specifications might be used as the basis for certifying #
interoperability & quality
Specifications might be used as the basis for certifying #
interoperability & quality
Interoperable Components from multiple providers Interoperable Components from multiple providers
Economies of scaleEconomies of scale
Extensive Application Development Ecosystem
Extensive Application Development Ecosystem
# Note: at the time of writing, oneM2M has not decided what role (if any) oneM2M might play in certification. It is possible that one or more other groups may certify against part or all of the oneM2M specifications.
Editor: “Certifying” may need further discussion. See email from Eanny Bae
Benefits of Incorporating Interactions with Underlying Networks
12
Wider range of options for the [Audience] in selecting an underlying network
Wider range of options for the [Audience] in selecting an underlying network
Application developers can ignore details of usage of underlying network (simplifying development) while benefiting from integrated efficiency, reliability & scalability of communications
Application developers can ignore details of usage of underlying network (simplifying development) while benefiting from integrated efficiency, reliability & scalability of communications
Improved FPQ Tradeoffs
Enhanced Scalability
Greater Choice
Greater Opportunities
Editor: Should “Benefiting from integrated efficient, reliability& scalability” be a separate item?
ONEM2M CAPABILITIES & DIRECTED BENEFITS
oneM2M Capabilities & Their Benefits
13
Goal of this document
• Previous Section: – Implicit Benefits independent of the capabilities that
oneM2M chooses to support• This section:– Capabilities & their features being considered– Directed benefits of these
capabilities/features/requirements • Objective of document– oneM2M wants feedback on what it is considering,
to help prioritize its work
14
Sharing Capability
15
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
Content-Aware Processing
16
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?
Security Framework and Access Control
17
oneM2M-to-oneM2M class
App-to-oneM2M classSharing
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
IdentityStatic 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.
Remote Device Management
18
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 ConfigurationsManaging Software & Firmware
Adding new Software (E.g. Applications)Software/Firmware updates
Removing Software
Maintenance Reporting
Provisioning
Editor: : I would appreciate the help of a remote device management expert(s) /advocate(s) to improve this page and provide notes. Any volunteers?
Communication Control
19
Interface to M2M-specific features of the underlying network
Communication Control
Sharing
Content-Aware Processing
Remote Device Management
Security Framework and Access Control
Network selection & scheduling
Content Delivery Guidance
Delivery confirmation /Progress reporting
Robustness in presence of lossy links
Communication Scalability Features
Directed Benefits
20
Communication Control Sharing
Security Framework and Access ControlRemote Device Management
Content-Aware Processing
Improved FPQ Tradeoffs
Enhanced Scalability
Greater Choice
Greater Opportunities
Ability to share data & assets with partners
Ability to share data & assets with partners
Reduced traffic
volume
Reduced traffic
volume
More value extracted from
underlying network
More value extracted from
underlying network
Improved end-product
quality
Improved end-product
quality
Better power consumptionBetter power consumption
Reduced field agent call-outs
Reduced field agent call-outs
Conclusion
• Summary– Why? FPQ tradeoff, scalability, choice, quality– How? Standardizing valuable generic M2M
capabilities integrated with underlying networks– Outline: Potential capabilities and features
• What do we want from you?– Feedback on these potential capabilities &
features in order to help oneM2M prioritize its work
21
FEEDBACK TEMPLATEProvide as mechanism for feedback to oneM2M
22
Feedback on MotivatorsMotivator Priority
(0=Low, 10 = Critical)Comments
(E.g. clarification audience requirements)
2014 2015+
Improved Functionality, Price, Quality Tradeoffs
Enhanced Scalability
Greater Choice
Greater Opportunity
23
Feedback on Sharing (1)
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
Field-Backend Sharing
Field-Field Sharing
Backend-Backend Sharing
Sharing with multiple Apps
Sharing with partners
Notification
24
Feedback on Sharing (2)Feature Priority
(0=Low, 10 = Critical)Comments
(E.g. clarification audience requirements)<Hints provided in angle brackets – feel
free to delete hints2014 2015+
Content Origin
Content Delivery Guidance
<Note: Discussed further under “Communication Control”>
Searchable tags
Vertical-specific metadata
<what data types would be helpful to support>
Proprietary metadata <what data types would be helpful to support>
Using metadata <How would you like to use metadata?>
Metadata-aware processing
<What metadata-aware processing would you value. See examples below>
25
Feedback on Content-Aware Processing
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
26
Feedback on Content-Aware Processing
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
27
Feedback on Security Framework and Access Control
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
28
Feedback on Remote Energy Management
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
29
Feedback on Communication Control
Feature Priority (0=Low, 10 = Critical)
Comments(E.g. clarification audience requirements)
2014 2015+
30
APPENDICES
TerminologyReferences
31
TerminologyName Description
M2M Application (App) TBD
App-to-App
Capability TBD
Component Hardware, software and services comprising an M2M solution
Content Data produced or consumed by Applications
Content-Aware Aware of the data model and/or semantics of Content
Generic Common to two or more applications or vertical segments
Underlying networks Access networks, core networks, busses and other technology assisting in data transport
32
References
1. “oneM2M Standardization”, 2012-04-24. Available from ftp://ftp.onem2m.org/Primary_Deliverables/Material_for_Verticals/oneM2M Standardization_2012-04-24.zip
33
OLD SLIDES – DELETE BEFORE PUBLICATION
Saved here in case they are useful in future.
34
Figure by Farooq Bari, AT&T
35
Figure by Tim Carey, ALU
36
Summary of CapabilitiesCapability Features Sharing Sharing 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.
37
NOTE: Initial text to explain partitioning of features.