Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea...

Experience and Discussion on Interworking Proxy Implementation

Group Name: WG2Source: Korea Electronics Technology Institute (KETI)Meeting Date: 2015-07-20~24Agenda Item: WI-0018

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


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


Proxy

Mca

Interworking proxy Scenarios Supported by oneM2M Architecture

Hybrid Application

CSE(s)


Mca

Inter-working Proxy

Mca (note 1)

Hybrid Application


Mca

Non oneM2M Application


Inter-working Proxy

Mca

oneM2M native Application

Mca


Our Focus on IPEs

4

+ over 200 service providers, industry, government, university, research, … members

Interworking Proxy Entity (IPE)


Our IPE Experience

5

NEST

Hue

Jawbone

IN-CSE

Non-oneM2M oneM2M

IPE

IPE

IN-AE(onePass App)

IN-AE(ConnecThing

Client)

MN-CSE

Mca

Mcc

Mca

Mcc’

oneM2M Showcase

(ETSI, 2014)


Demo Implementation

6

ConnecThing App

AllJoyn Google Nest

Jawbone U24 Philips Hue

PowertechSmart Plug

oneM2MService Entity(MN-CSE)

Dawon DNSSmart Plug

oneM2M Interworking

Proxy (for AllJoyn)

oneM2MService Entity

(IN-CSE)

oneM2M Interworking

Proxy (for Nest)

oneM2MService Entity

(IN-CSE)

oneM2M Interworking

Proxy (for Hue)

oneM2MService Entity(IN-CSE)

oneM2M Interworking

Proxy (for Jawbone)

Pebble

NestAllJoyn

OIC

HueJawbone

oneM2M

onePassApp

OpenAPI

onePassApp

OpenAPI

onePassApp

OpenAPI


TIA oneM2M Showcase

7

6/1/2015, Dallas, TX, U.S.https://youtu.be/FngoyncRhCM (Universal App)https://youtu.be/zHfIQwLBPsM (Interworking scenarios)

Demo videos available:

https://youtu.be/FngoyncRhCM


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

AllJoyn Device

AE

Proxy Function

IPE

MN-CSE

&Cube

IN-CSE

Mobius

AE

Mcc

Mca

Virtual CSEMcc

Gateway

Mca

About

Apps

AllJoyn Apps

AllJoyn Apps

Resource Mapping (1)• Example of AllJoyn About object (device information)

Resource Name Value

ModelNumber 0.0.1

Description PLUG IOE device

DefaultLanguage en

AJSoftwareVersion 14.06.00a Tag “v14.06.00a”

DeviceId c8da2fe2fb54afe42a5db73dfeffcf49

MaxLength 32

HardwareVersion 0.0.1

AppName Controllee

SupportedLanguages en

SoftwareVersion 0.0.1

AppId C8DA2FE2FB54AFE42A5DB73DFEFFCF49

Manufacturer Company A(EN)

SupportUrl http://www.xxx.co.kr

DateOfManufacture 2014-11-18

DeviceName 000 SmartPlug effcf49

< oneM2M CSEBase/remoteCSE (VirtualCSE) >


Resource Name Value

ModelNumber 0.0.1


DefaultLanguage en



MaxLength 32


AppName Controllee








< oneM2M remoteCSE (VirtualCSE)/node/deviceInfo >


Resource Name Value

ModelNumber 0.0.1


DefaultLanguage en



MaxLength 32


AppName Controllee








< oneM2M remoteCSE (VirtualCSE)/AE >

Resource Mapping (4)• Example of AllJoyn App (ControlPanel) object

Resource Name Child Resource

Property Power Status,Power Consumption,Cumulative Power,Volt Value,Current Value,Frequency Value,Power Factor

LabelProperty -

Action On,Off

Notification Action -

Dialog -


AllJoyn to oneM2M Mapping

13

AllJoyn Device <remoteCSE>

App 1<AE>

Node Info <node>

deviceInfo <mgmtObj>

softwareInfo <mgmtObj>

firmwareInfo <mgmtObj>

description

manufacturer

……

Container

AllJoyn Device

AllJoyn App 1

AllJoyn App N

AllJoynObject 1

AllJoynObject M

App N<AE>

CSEBase

Container

Container

Container

AllJoyn Entity Relationship oneM2M Resource Structure


Discussion

• Interworking Proxy (AE and CSE)

14

Hybrid Application

CSE(s)


Mca

Interworking Proxy (AE)

Mca

Hybrid Application


Mca

Non oneM2M Application


Interworking Proxy (AE)

Mca

oneM2M native Application

Mca

Hybrid device

Interworking Proxy (CSE)

Hybrid device Non oneM2M device

Interworking Proxy (CSE)

oneM2M native device

MccMcc/Mca

Mcc/Mca




Mcc Mcc

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea...

Documents

Transcript of Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea...