© 2015 oneM2M Enrico Scarrone oneM2M Steering Committee Vice Chair M2M/IoT standard coordination-Telecom Italia ONEM2M INTERWORKING.

Slides:

Advertisements

Similar presentations

A global Service layer platform for M2M communications

Advertisements

TP#2 Election Process Group Name: TP Source: Victoria Gray, ETSI, Meeting Date: Agenda Item: 6.3,

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

Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date:

IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

ITU Workshop on "Future Trust and Knowledge Infrastructure", Phase 1 Geneva, Switzerland, 24 April 2015 Session 4 – IoT data platform based on oneM2M Dr.

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

On a Device Information Model for devices in oneM2M

On Management, Abstraction & Semantics

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

3GPP Rel-13 Interworking discussions

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

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

Workshop with IEEE P2413 oneM2M Other suggested titles:

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24.

Guidelines for: Release Maintenance, Small Enhancement and Feature Work Items Group Name: TP15 Source: Mow Convenor, (Scarrone Enrico, Telecom Italia)

Fuctional Procedure for oiC interworking

oneM2M-AllJoyn Interworking

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

An introduction to oneM2M

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

LWM2M Interworking Group Name: Architecture

M2M Service Session Management (SSM) CSF

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

SE abstraction scenarios Group Name: SEC Source: Claus Dietze, Giesecke & Devrient Meeting Date: Agenda Item: WI SE abstraction.

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

3GPP SCEF Interworking Discussions

LWM2M Interworking Proxy Procedures ARC Considerations

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

Example mapping of KNX to oneM2M base Ontology

MoW Report Group Name: TP21 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

Possible Solution of Interworking between oneM2M and OSGi

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jinhyeock Choi, Samsung Electronics,

Jeju, 13 – 16 May 2013Standards for Shared ICT oneM2M Project Presenter: Luis Jorge Romero oneM2M Steering Committee Chairman Document No: GSC17-PLEN-38.

How does Generic Interworking work?

SEMANTICS OF SMART APPLIANCES INITIATIVE Presenter

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Proximal IoT Interworking discussion

2nd Interoperability testing issues

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

GRUPPO TELECOM ITALIA The IoT 5G Network Infrastructures and the IoT Data Store & Share Platform: challenges and opportunities Roberto Gavazzi – TIM Technology.

Proposed design principles for modelling interworked devices

3GPP Rel-13 Interworking discussions

Solving the IoT Platform Challenge

Proximal IoT Interworking solution discussion

oneM2M Work on IoT Semantic and Data Model Interoperability

LWM2M Interworking with <mgmtObj> Resources

Presenter: Luis Jorge Romero oneM2M Steering Committee Chairman

ETSI Standardization Activities on M2M Communications

On Management, Abstraction & Semantics

An introduction to oneM2M

3GPP V2X Interworking Potential Impact

ETSI Standardization Activities on M2M Communications

Current standardization activities – oneM2m

Workshops Hackathon Posters & demos ETSI Explainers

Presentation transcript:

© 2015 oneM2M Enrico Scarrone oneM2M Steering Committee Vice Chair M2M/IoT standard coordination-Telecom Italia ONEM2M INTERWORKING

© 2015 oneM2M OneM2M is an interworking framework Interworking Proxy Entity AE CSE Mca Mcc IPE Mca Etc.

© 2015 oneM2M3 Non oneM2M applications Hybrid Application CSE(s) Non oneM2M interface Mca Inter- working Proxy Mca Hybrid Application Non oneM2M interface Mca Non OneM2M Application Non oneM2M interface Inter-working Proxy Mca OneM2M native Application Mca

© 2015 oneM2M4 For common shared data models Sensor/Meter CSE Protocol 1 AE Inter-working Proxy Mca Utiliy Application Mca Sensor/Meter Protocol 2 AE Inter-working Proxy Mca Device/Gateway CSE Mcc Gateway/Infrastructure Node Protocol translation Common Data model Awareness Basic Communicati on only data model AE Inter-working Proxy Protocol 3

© 2015 oneM2M5 And for specific data models Sensor/Meter CSE Mbus/COSEM AE Inter-working Proxy Mca Utiliy Application Mca Sensor/Meter Zigbee telco Profile AE Inter-working Proxy Mca Device/Gateway CSE Mcc Gateway/Infrastructure Node Common Data model Awareness Specific Data model Awareness Basic Communicati on only data model

© 2015 oneM2M6 What is missing ? Release one provides the framework. Common semantic and semantic interworking is left to companies and interested organizations (e.g. the SAREF initiative of EU DG- connect via ETSI SmartM2M). Semantic Support is one of the primary target for Release 2 Additionally in Release 2 some interested organization/companies are going to define in oneM2M some relevant cases (see next presentations).

© 2015 oneM2M7 Thank You!