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

Slides:

Advertisements

Similar presentations

oneM2M and AllJoyn Interworking

Advertisements

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

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

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

REQ WG Reuse of underlying networks, 3GPP

TAKING A LOOK INSIDE Nicolas Damour

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

On a Device Information Model for devices in oneM2M

Device Management using mgmtCmd resource

On Management, Abstraction & Semantics

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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

oneM2M-OIC Interworking Technical Comparison

Step by step approach Group Name: WG2

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

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:

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

Fuctional Procedure for oiC interworking

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

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

oneM2M-AllJoyn Interworking

An introduction to oneM2M

Scenarios for oneM2M and OIC Interworking

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

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

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

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

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

Home Device Caching & Replacement Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

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:

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

Service Framework Proposal

Proximal IoT Interworking discussion

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Proposed design principles for modelling interworked devices

3GPP Rel-13 Interworking discussions

Proximal IoT Interworking solution discussion

3GPP Interworking Abstraction

LWM2M Interworking with <mgmtObj> Resources

Development Guideline for oneM2M Products and Services

On Management, Abstraction & Semantics

An introduction to oneM2M

3GPP V2X Interworking Potential Impact

Presentation transcript:

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24 Agenda Item: WI-0018

ARC Experience_and_discussion_on_IPE_Implementation Outline Current Interworking Proxy Entity KETI’s Experience on IPE Implementation AllJoyn to oneM2M Mapping Discussion 2

ARC Experience_and_discussion_on_IPE_Implementation Current IPE Interworking Proxy Entity (IPE) – 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 3 Non oneM2M interface AE: Interworking Proxy Mca Non oneM2M interface Proxy Mca Interworking proxyScenarios Supported by oneM2M Architecture Hybrid Application CSE(s) Non oneM2M interface Mca Inter-working Proxy Mca (note 1) Hybrid Application Non oneM2M interface Mca Non oneM2M Application Non oneM2M interface Inter-working Proxy Mca oneM2M native Application Mca

ARC Experience_and_discussion_on_IPE_Implementation Our Focus on IPEs 4 + over 200 service providers, industry, government, university, research, … members Interworking Proxy Entity (IPE)

ARC Experience_and_discussion_on_IPE_Implementation Our IPE Experience 5 NEST Hue Jawbone IN-CSE Non-oneM2MoneM2M IPE IN-AE (onePass App) IN-AE (ConnecThing Client) MN-CSE Mca Mcc Mca Mcc’ oneM2M Showcase (ETSI, 2014)

ARC Experience_and_discussion_on_IPE_Implementation Demo Implementation 6 ConnecThing App AllJoynGoogle Nest Jawbone U24Philips Hue Powertech Smart Plug oneM2M Service Entity (MN-CSE) Dawon DNS Smart Plug oneM2M Interworking Proxy (for AllJoyn) oneM2M Service Entity (IN-CSE) oneM2M Interworking Proxy (for Nest) oneM2M Service Entity (IN-CSE) oneM2M Interworking Proxy (for Hue) oneM2M Service Entity (IN-CSE) oneM2M Interworking Proxy (for Jawbone) Pebble NestAllJoyn OIC HueJawbone oneM2M onePass App Open API onePass App Open API onePass App Open API

ARC Experience_and_discussion_on_IPE_Implementation TIA oneM2M Showcase 7 6/1/2015, Dallas, TX, U.S. (Universal App) (Interworking scenarios) Demo videos available:

ARC Experience_and_discussion_on_IPE_Implementation KETI’s Experience Interworking Proxy Entity for AllJoyn – Proxy Function: interact with AllJoyn devices – Virtual CSE: map AllJoyn About fields to oneM2M, AllJoyn App ( ControlPanel ) object to oneM2M 8 AllJoyn Device AE Proxy Function IPE MN-CSE &Cube IN-CSE Mobius AE Mcc Mca Virtual CSE Mcc Gateway Mca About Apps AllJoyn Apps

Resource Mapping (1) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion a Tag “v a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp:// DateOfManufacture DeviceName000 SmartPlug effcf49

Resource Mapping (2) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion a Tag “v a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp:// DateOfManufacture DeviceName000 SmartPlug effcf49

Resource Mapping (3) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion a Tag “v a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp:// DateOfManufacture DeviceName000 SmartPlug effcf49

Resource Mapping (4) Example of AllJoyn App ( ControlPanel ) object Resource NameChild Resource Property Power Status, Power Consumption, Cumulative Power, Volt Value, Current Value, Frequency Value, Power Factor LabelProperty- Action On, Off Notification Action- Dialog-

ARC Experience_and_discussion_on_IPE_Implementation AllJoyn to oneM2M Mapping 13 AllJoyn Device App 1 Node Info deviceInfo softwareInfo firmwareInfo description manufacturer … Container AllJoyn Device AllJoyn App 1 AllJoyn App N AllJoyn Object 1 AllJoyn Object M App N CSEBase Container AllJoyn Entity RelationshiponeM2M Resource Structure

ARC Experience_and_discussion_on_IPE_Implementation Discussion Interworking Proxy (AE and CSE) 14 Hybrid Application CSE(s) Non oneM2M interface Mca Interworking Proxy (AE) Mca Hybrid Application Non oneM2M interface Mca Non oneM2M Application Non oneM2M interface Interworking Proxy (AE) Mca oneM2M native Application Mca Hybrid device Interworking Proxy (CSE) Hybrid deviceNon oneM2M device Interworking Proxy (CSE) oneM2M native device Mcc Mcc/ Mca Non oneM2M interface Mcc