Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

Slides:



Advertisements
Similar presentations
STAMP STAMP: Low-cost Customizable Tablet. STAMP About AllGo 7 years, 75 people Embedded multimedia product design services Hardware, Firmware/DSP, Software,
Advertisements

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All ETSI Standardization Activities on M2M communications Joachim Koss, ETSI Board Member Document No:
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:
1 Short presentation title Name Organisation Contact details © EPoSS 2015EPoSS Brokerage Workshop on IoT Large Scale Pilots, London,
Requirements Structure 2.0 Clark Elliott Instructor With debt to Chris Thomopolous and Ali Merchant Original Authors.
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.
OneM2M Partnership Project draft proposal for slide set.
Authors list to be completed.
Contribution since August,2008 National MSME Conclave 19 November, 2014 Use of ICT to make MSME more competitive and sustainable Tapan K. Patra Director.
RUP Requirements RUP Artifacts and Deliverables
Authors list to be completed.
Summary Device protocols tied intimately to applications. A need to significantly reduce critical data update times. Current network bandwidth consumption.
Introduction to ISO 9001:2000.
SAML Right Here, Right Now Hal Lockhart September 25, 2012.
Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.
Service Transition & Planning Service Validation & Testing
An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
DIME WG IETF 82 Dime WG Agenda & Status THURSDAY, November 17, 2011 Jouni Korhonen & Lionel Morand.
OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.
Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
Geneva, Switzerland, April 2012 Introduction to session 7 - “Advancing e-health standards: Roles and responsibilities of stakeholders” ​ Marco Carugi.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,
Jeju, 13 – 16 May 2013Standards for Shared ICT TIA TR-50 M2M-Smart Device Communications Dr. Jeffery Smith Chief Innovation and Technology Officer/EVP.
Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:
Proposal for WG3 & WG5 work area split
Architectural Principles for Services Group Name: WG2- ARC Source: Tim Carey, ALU, Meeting Date: Agenda Item:
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
An introduction to oneM2M
TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
State of Georgia Release Management Training
Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Potential use case for discussion – Street Light Automation Group Name: WG1/2 Source: Cisco Meeting Date: Joint-REQ-ARC-WGs-call Agenda Item: Use cases.
WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.
Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:
WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.
TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,
WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:
Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.
WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Status of Active Work Items Level of Completeness
Possible options of using DDS in oneM2M
WPM ad-hoc group report TP#24
Release Timeline Discussion R2 and beyond
WPM ad-hoc group report TP#25
ATIS Cybersecurity DOCUMENT #: GSC13-GTSC6-12 FOR: Presentation
ETSI Standardization Activities on M2M communications
3GPP Status.
An introduction to oneM2M
TIA TR-50 M2M-Smart Device Communications
SMART HOME Expectation IN STANDARDS
Desktop App Assure Service Microsoft Representative Name June 7, 2019
Presentation transcript:

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR, Meeting Date: Agenda Item: 6 “Contributions” BENEFITS OF ONEM2M TECHNOLOGIES

Scope Audience: Vertical industry segment stakeholders Purpose: Trigger feedback from [the Audience] Content: Highlights potential benefits of oneM2M communication technology to [the Audience] Note: current title of presentation is a placeholder only 2

Outline Motivators: – Audience Priorities oneM2M intends to address Description of oneM2M Technology Benefits of oneM2M Details of Potential Functionalities Terminology 3

Motivators oneM2M believes that [the Audience] would like to improve the following aspects of the M2M ecosystem: – Costs: Reduce or amortize CAPEX, OPEX and Time-to-market. – Quality: transparent, certifiable quality of components & services; improved quality of the end product – Choice: Interoperable components & services from a range of providers – Opportunities: Ability to share data and resources with other stakeholders to amortize costs 4

DESCRIPTION OF ONEM2M TECHNOLOGY One sentence description of oneM2M technology Easy-to-digest description of oneM2M technology 5

One sentence description The aim of oneM2M communication technology is to standardize a set of M2M- specific transport-agnostic functions that have potential to improve the cost, quality, choice and opportunities for [the Audience]. Disclaimer: – The document is intended to be read as a broad description of how the goals of improving cost, quality, choice and opportunities might be met by technology that oneM2M is considering. – This document is not intended to be read as guidance regarding the degree of improvements (to cost, quality, choice and opportunities) that will result from oneM2M technology. 6

Transport protocols oneM2M protocols Transport Component Interface Transport- Agnostic Features Easy-to-digest description of oneM2M 7 Field App Cloud App oneM2M Component Transport Components

Easy-to-digest description of oneM2M Text showing relationship between – Applications – oneM2M Technology – Transports 8

BENEFITS OF ONEM2M Standardization and New Functionality 9

Preamble oneM2M believes that it can provide value to [the Audience] simply by standardizing transport-agnostic and vertical-agnostic protocols and components (see next slide) However, oneM2M believes that it can provide additional value to [the Audience] by providing new functionality. This document lists many functionalities oneM2M is considering. At this point in time, none of these functionalities are specified and oneM2M is currently evaluating the priority of these functionalities for the upcoming release. Some functionalities may be deferred to future oneM2M releases, or may never be included in oneM2M specifications. For the time being, we call these “potential functionalities”. Feedback from [the Audience] on the potential functionalities will be valuable in helping oneM2M prioritize its work. 10

Benefits of Standardization Standardizing interoperable components will enable certifiable quality of components Standardizing interoperable components enables a choice of providers of components (both software and hardware) and services. Specifying Transport-agnostic and Vertical-agnostic protocols & components lets M2M Application stakeholders choose of transport products and services independent of other decisions. Specifying Transport-agnostic and vertical-agnostic components enhance the economies of scale, reducing costs of products and services Specifying Transport-agnostic and vertical-agnostic components allows the growth of a extensive application development ecosystem reducing cost of application development and lifecycle and improved quality of the end product [Some text imported from oneM2M-REQ ] 11

Overview of Potential Functionalities Sharing Data [and Sharing Components/Devices?] Security Framework & Access Control Context-Aware Processing Transport Efficiency Features Improved Reliability (of communications) Remote Device Management 12

Benefits of Potential Functionalities Sharing data and Context-Aware processing provides opportunities to partner with other stakeholders to amortize costs, protected by Access Control over your data supported by a strong Security framework Sharing data and Context-Aware processing also reduces traffic volume. This reduction of traffic volume, in combination with Transport efficiency features – enables better battery life, reducing costs – results in less load on Transport resources, reducing costs of transport products and services Improved reliability of communications translates to improved quality of the end product Remote device management reduces call-outs (reducing OPEX) and increases the reliability of your end products – For example, faults can be triaged and corrected remotely before products fail to the point of requiring a call-out 13

DETAILS OF THE POTENTIAL FUNCTIONALITIES 14

Transport Efficiency Features 15 Scheduling E.g. Store and Forward Remote Session Triggering Transport Efficiency Features Sharing Data Security Framework and Access Control Remote Device Management Improved Reliability Context-Aware Processing

Remote Device Management 16 Transport Efficiency Features Sharing Data Security Framework and Access Control Remote Device Management Improved Reliability Context-Aware Processing 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

APPENDIX: TERMINOLOGY 17

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 oneM2M communication technology Components and protocols conforming to oneM2M specifications TransportTBD 18