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

Slides:

Advertisements

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Advertisements

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All ETSI Standardization Activities on M2M communications Joachim Koss, ETSI Board Member Document No:

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

CURRENT STANDARDIZATION ACTIVITIES – ONEM2M GSC-18 Meeting, July 2014, Sophia Antipolis, France Document No: GSC(14)18_012 Source: ETSI Contact:

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.

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All Consolidated M2M standards boost the industry Li Li (Thomas) CCSA(Huawei) Document No: GSC16-PLEN-73.

OneM2M Partnership Project draft proposal for slide set.

Authors list to be completed.

Authors list to be completed.

Introduction to MDA (Model Driven Architecture) CYT.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

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,

What and Why? Next steps for oneM2M Semantics Group Name: WG5 Source: Joerg Swetina, Martin Bauer (NEC) Meeting Date: Agenda Item: WI-0005 oneM2M-MAS

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:

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Introduction to Grids By: Fetahi Z. Wuhib [CSD2004-Team19]

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

An introduction to oneM2M

Ontology Resource Discussion

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.

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,

M2M Study Item 3GPP2 Orlett W. Pearson May | 3GPP2 M2M Study Item | May GPP2 M2M This study will include the following study targets: 

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

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:

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

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

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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:

ATIS’ Machine-to-Machine (M2M) Activity

Status of Active Work Items Level of Completeness

© 2017 InterDigital, Inc. All Rights Reserved.

ControlLogix 5580 Controller

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Consolidated M2M standards boost the industry

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

oneM2M Work on IoT Semantic and Data Model Interoperability

Overview of E2E Security CRs

ETSI Standardization Activities on M2M communications

An introduction to oneM2M

Current standardization activities – oneM2m

TIA TR-50 M2M-Smart Device Communications

ATIS’ Machine-to-Machine (M2M) Activity

Presentation transcript:

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR, Meeting Date: Agenda Item: 6 “Contributions” ALTERNATIVE INITIAL TEXT FOR BENEFITS PRESENTATION

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

Outline Description Benefits Terminology 3

DESCRIPTION One sentence description of oneM2M Easy-to-digest description of oneM2M 4

One sentence description The aim of oneM2M communication technology is to enable cost savings for M2M Application stakeholders 5

Easy-to-digest description of oneM2M Text & Figure showing relationship between – Applications – M2M Service Layer – Transport 6

BENEFITS High Level View of Benefits More Details of Benefits 7

High level view of Benefits 8 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports Less load on Transport Resources, Lower OPEX, Better battery life Economies of Scale, Reliability Lower development costs

Reusable Components 9 Efficient Use of Transports Common Common Functionality supporting efficient use of transport Reusable App Components Cost Savings Simplified Application Development Reusable Service Layer Components Reusable Device Management Components Common Common App-to-App Security Framework Common Common Remote Device Management Framework

Common Common Functionality Efficient Use of Transports 10 Cost Savings Reusable Components 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 Content Sharing Reliability Content Grouping & Filtering Reducing size of exchanges Transmitting only essential data Compact Representation Context-Aware Intelligent Processing Access Control Service-to-Service & App-to-Service Security Frameworks Service layer takes care of Transport details

Simplified App Development 11 Cost Savings Reusable Components Simplified Application Development Efficient Use of Transports Developers can focus on developing & enhancing features of their Apps Service layer takes care of Transport details Developers expertise is reusable across multiple Apps Common Common App-to-App Security Framework Common Common Remote Device Management Framework

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

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

Terminology NameDescription M2M Application (App)TBD CommonStandardized, Generic and Transport-Agnostic 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 14