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

Slides:

Advertisements

Similar presentations

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

Advertisements

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

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

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

On a Device Information Model for devices in oneM2M

Device Management using mgmtCmd resource

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

On Management, Abstraction & Semantics

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

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

oneM2M-OIC Interworking Technical Comparison

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

3GPP Rel-13 Interworking discussions

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

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

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

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

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd.

LWM2M Interworking Object Instantiation Group Name: Architecture Source: ALU (TIA) Meeting Date: Arc 17.2 Agenda Item: LWM2M Interworking.

Fuctional Procedure for oiC interworking

AllJoyn-Interworking Discussion Group Name: TP WG2 ARC Source: Josef Blanz, Phil Hawkes, Qualcomm Inc., Meeting Date:

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

An introduction to oneM2M

Scenarios for oneM2M and OIC Interworking

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

3GPP Rel-13 Interworking discussions

OIC device management interworking procedure

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

LWM2M Interworking Group Name: Architecture

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

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,

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

OIC INTERWORKING Resource mapping

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

3GPP SCEF Interworking Discussions

LWM2M Interworking Proxy Procedures ARC Considerations

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

Example mapping of KNX to oneM2M base Ontology

oneM2M based IoT Platform Development of SK Telecom

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

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

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.

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

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.

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

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

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

Provisional Architecture for oneM2M

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Discussion about Use Case and Architecture in Developer Guide

Proposed design principles for modelling interworked devices

MAF&MEF Interface Specification discussion of the next steps

3GPP Rel-13 Interworking discussions

Proximal IoT Interworking solution discussion

3GPP Interworking Abstraction

LWM2M Interworking with <mgmtObj> Resources

An introduction to oneM2M

3GPP V2X Interworking Potential Impact

Presentation transcript:

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics, Sung Chan Choi, KETI, Seonhyang Kim, DT&C, Bahareh Sadeghi, Intel, Lionel Florit, Cisco, Meeting Date: Agenda Item:

2 Basic Sketch IPE in between – which plays the role of both oneM2M & OIC entities. Separation of OIC & oneM2M operation – The intermediary interact with OIC (& oneM2M) devices with OIC (& oneM2M) procedures respectively. oneM2M device (controller) ① oneM2M REQ OIC device (sensor & actuator) IPE ② OIC REQ ③ OIC RES ④ oneM2M RES (virtual) oneM2M device (virtual) OIC device oneM2M & OIC resource translation

3 Functional Architecture Interworking with IPE – IPE, as an intermediary, facilitates oneM2M & OIC interworking by translating oneM2M and OIC resources. Functional Entities – IPE: a specialized AE, characterized by the support of a non-oneM2M reference point, and by the capability of remapping the related data model to the oneM2M resources exposed via the Mca reference point – oneM2M CSE: an usual oneM2M common service entity (CSE) – OIC device: a logical entity which plays either OIC client or OIC server roles or both. OIC server hosts OIC resources and expose those for IoT service. OIC client accesses OIC server to manipulate OIC resources, i.e. monitoring & controlling OIC device oneM2M CSE IPE oneM2M AE virtual OIC device Mca Reference Point OIC Interface

4 oneM2M interworking with OIC via IPE OIC device MN-CSE OIC device IPE Gateway IN-CSE IN-AE ASN-AE ASN-CSE ADN-AE OIC Interface OIC Interface Mca MccMcaMccMca Deployment model based on Functional Architecture – Main entities and their interworking via reference points. Mcc

5 Interworking with IPE in detail virtual OIC devices in IPE – Replicating virtual OIC device in IPE with OIC procedures. – Binding two devices such that they are synchronized, i.e. the same resource representations virtual oneM2M devices in IPE – Mirroring virtual OIC device to virtual oneM2M device by resource mapping. – oneM2M service by manipulating virtual oneM2M device, which will reflected in the virtual & original OIC devices. IPE vOIC device /oic/res /oic/d /lightSwitch CSE /oic/res /oic/d /myLight /lightSwitch Mirroring oneM2M & OIC devices OIC device /oic/res /oic/d /lightSwitch Sync OIC devices via OIC interfaces oneM2M services with oneM2M interfaces CSE (AE) /oic/res /oic/d /myLight /lightSwitch

6 Operation procedures 1.(virtual) OIC device replication – replicating OIC device in IPE as (virtual) OIC device With synchronization binding by OIC discovery procedures. 2.(virtual) oneM2M device translation – mirroring OIC device into (virtual) oneM2M device. With proxying & translating 3.oneM2M registration & discovery – registering (virtual) oneM2M device to suitable CSE for discovery 4.oneM2M monitoring & controlling – oneM2M controller interacts with (virtual) oneM2M devices 5.oneM2M & OIC resource translation – Translating oneM2M & OIC resources to synchronize virtual devices state 6.OIC synchronization – Synchronizing virtual OIC device & OIC device With OIC Request & response via synchronization binding. Initial preparation Actual monitoring & controlling