Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Published byDorothy Barker Modified over 9 years ago

Similar presentations

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

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

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

3 ARC-2015-2022-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

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

5 ARC-2015-2022-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)

6 ARC-2015-2022-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

7 ARC-2015-2022-Experience_and_discussion_on_IPE_Implementation TIA oneM2M Showcase 7 6/1/2015, Dallas, TX, U.S. https://youtu.be/FngoyncRhCMhttps://youtu.be/FngoyncRhCM (Universal App) https://youtu.be/zHfIQwLBPsMhttps://youtu.be/zHfIQwLBPsM (Interworking scenarios) Demo videos available:

8 ARC-2015-2022-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

9 Resource Mapping (1) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion14.06.00a Tag “v14.06.00a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp://www.xxx.co.kr DateOfManufacture2014-11-18 DeviceName000 SmartPlug effcf49

10 Resource Mapping (2) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion14.06.00a Tag “v14.06.00a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp://www.xxx.co.kr DateOfManufacture2014-11-18 DeviceName000 SmartPlug effcf49

11 Resource Mapping (3) Example of AllJoyn About object (device information) Resource NameValue ModelNumber0.0.1 DescriptionPLUG IOE device DefaultLanguageen AJSoftwareVersion14.06.00a Tag “v14.06.00a” DeviceIdc8da2fe2fb54afe42a5db73dfeffcf49 MaxLength32 HardwareVersion0.0.1 AppNameControllee SupportedLanguagesen SoftwareVersion0.0.1 AppIdC8DA2FE2FB54AFE42A5DB73DFEFFCF49 ManufacturerCompany A(EN) SupportUrlhttp://www.xxx.co.kr DateOfManufacture2014-11-18 DeviceName000 SmartPlug effcf49

12 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-

13 ARC-2015-2022-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

14 ARC-2015-2022-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

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

Similar presentations

oneM2M and AllJoyn Interworking

oneM2M and AllJoyn Interworking
SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: 2014-05-07 Discussion  Source: OBERTHUR Technologies Information  Contact:

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Is a Node or not Node? ARC-2014-1194-Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

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

IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit
REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP
TAKING A LOOK INSIDE Nicolas Damour

TAKING A LOOK INSIDE Nicolas Damour
Discussion on oneM2M HTTP Binding Interoperability Test Spec.

Discussion on oneM2M HTTP Binding Interoperability Test Spec.
On a Device Information Model for devices in oneM2M

On a Device Information Model for devices in oneM2M
Device Management using mgmtCmd resource

Device Management using mgmtCmd resource
On Management, Abstraction & Semantics

On Management, Abstraction & Semantics
Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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.

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

oneM2M-OIC Interworking Technical Comparison
Step by step approach Group Name: WG2

Step by step approach Group Name: WG2
End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date: 2015-05-18.

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:
PRO-2014-0516R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

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

3GPP Rel-13 Interworking discussions
TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: 2014-06-07 Agenda Item: ARC11/PRO11.

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: 2014-03-03 Agenda Item: WI-0005 oneM2M-MAS-2014-0335.

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: 2013-12-10.

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

Similar presentations

Ads by Google