Presentation is loading. Please wait.

Presentation is loading. Please wait.

Fuctional Procedure for oiC interworking

Published byHenry Fields Modified over 8 years ago

Similar presentations

Presentation on theme: "Fuctional Procedure for oiC interworking"— Presentation transcript:

1 Fuctional Procedure for oiC interworking
Other suggested titles: “Benefits of oneM2M Standardization” Group Name: Architecture WG Source: Jinhyeock Choi,Samsung Electronics, Jieun Keum, Samsung Electronics, Sung Chan Choi, KETI, Meeting Date: < > Agenda Item: <WI 44: oneM2M-OIC interworking >

2 oneM2M & OIC resource translation
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) IPE OIC device (sensor & actuator) (virtual) oneM2M device ① oneM2M REQ ② OIC REQ ④ oneM2M RES ③ OIC RES (virtual) OIC device oneM2M & OIC resource translation

3 Main operations (virtual) OIC device representation
replicating OIC device in IPE as (virtual) OIC device With OIC discovery procedures. (virtual) oneM2M device representation translating OIC device into (virtual) oneM2M device. With virtual CSE (?) oneM2M discovery oneM2M controller finds (virtual) oneM2M devices oneM2M monitoring & controlling oneM2M controller interacts with (virtual) oneM2M devices on2M2M & OIC resource translation Translating oneM2M & OIC resources to synchronize virtual devices state OIC synchronization Synchronizing virtual OIC device & OIC device With OIC Request & response via BINDING (?).

4 Actual monitoring & controlling
Main operations (virtual) OIC device representation replicating OIC device in IPE as (virtual) OIC device With OIC discovery procedures. (virtual) oneM2M device representation translating OIC device into (virtual) oneM2M device. With virtual CSE (?) oneM2M discovery oneM2M controller finds (virtual) oneM2M devices oneM2M monitoring & controlling oneM2M controller interacts with (virtual) oneM2M devices on2M2M & OIC resource translation Translating oneM2M & OIC resources to synchronize virtual devices state OIC synchronization Synchronizing virtual OIC device & OIC device With OIC Request & response via BINDING (?). Initial preparation Actual monitoring & controlling

5 Main operations (virtual) OIC device representation
replicating OIC device in IPE as (virtual) OIC device With OIC discovery procedures. (virtual) oneM2M device representation translating OIC device into (virtual) oneM2M device. With virtual CSE (?) oneM2M discovery oneM2M controller finds (virtual) oneM2M devices oneM2M monitoring & controlling oneM2M controller interacts with (virtual) oneM2M devices on2M2M & OIC resource translation Translating oneM2M & OIC resources to synchronize virtual devices state OIC synchronization Synchronizing virtual OIC device & OIC device With OIC Request & response via BINDING (?). OIC operation oneM2M & OIC translation oneM2M operation oneM2M operation oneM2M & OIC translation OIC operation

6 (virtual) OIC device representation
Overview (What) replicating OIC device in IPE as (virtual) OIC device, (IPE as OIC server (?) ) ensuring two OIC devices to be synchronized, i.e. having the same resource representation Methods (How) Using OIC discovery to acquire the OIC device information GET to /oic/res (from IPE) POST to /factoryResource (from OIC device) Establishing the relationship between two OIC devices . Link with “binding” relationship This is OIC specific procedure, outside of oenM2M scope. Also some ideas still unspecified in OIC. IPE GET /oic/res OIC device OIC Client Response /oic/res Bind GET /oic/d /oic/d Bind /oic/res Bind Response /lightSwitch Bind /oic/d Bind GET /lightSwitch /lightSwitch Bind Response

7 (virtual) oneM2M device representation
Overview (What) translating OIC device into (virtual) oneM2M device. Methods (How) Virtual CSE IPE OIC Client /myLight /oic/res /oic/d /oic/res Bind /lightSwitch /oic/d Bind /lightSwitch /lightSwitch value Bind

8 oneM2M discovery Overview (What) Methods (How)
oneM2M controller finds (virtual) oneM2M devices Methods (How) Usual oneM2M procedures IPE oneM2M device OIC Client /myLight oneM2M REQ /oic/res AE or CSE /oic/d /oic/res Bind /lightSwitch oneM2M RES /oic/d Bind /lightSwitch /lightSwitch value Bind

9 oneM2M monitoring & controlling
Overview (What) oneM2M controller interacts with (virtual) oneM2M devices Methods (How) Usual oneM2M procedures Need consideration regarding OIC REQ/ RES procedures Blocking or Non-blocking procedure IPE oneM2M device OIC Client /myLight oneM2M REQ /oic/res AE or CSE /oic/d /oic/res Bind /lightSwitch oneM2M RES /oic/d Bind /lightSwitch /lightSwitch value Bind

10 on2M2M & OIC resource translation
Overview (What) Translating oneM2M & OIC resources to reflect oneM2M resource change into OIC resource & vice versa. Methods (How) More structural approach would help. IPE OIC Client /myLight /oic/res /oic/d /oic/res Bind /lightSwitch /oic/d Bind /lightSwitch /lightSwitch Bind value value

11 OIC synchronization Overview (What) Methods (How)
Synchronizing virtual OIC device & OIC device i.e. all of their resources have the same representation. Methods (How) Binding to establish the relationship between (virtual) OIC device & the original device (similar to CoAP Observe binding) Usual CoAP procedure for resource UPDATE. UPDATE procedure can be initiated by both. IPE POST /lightSwitch "value": False OIC Client /oic/res /myLight Bind /oic/res Response /oic/d Bind /oic/d /lightSwitch Bind /oic/res Bind POST /lightSwitch "value": False /lightSwitch value /oic/d Bind /lightSwitch /lightSwitch Bind value Response value

12 Appendix

13 Functional Architecture
Interworking with IPE IPE, as an intermediary, facilitates oneM2M & OIC interworking in between. Functional Entities IPE: a specialized AE which maps OIC devices to oneM2M resources & exposes those via Mca (or Mcc) 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 oneM2M CSE IPE OIC device oneM2M AE virtual OIC device Mca (or Mcc) Reference Point OIC Interface

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

15 Interworking with OIC via virtual devices
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 vCSE (AE) vCSE (AE) vOIC device OIC device /myLight /myLight /oic/res /oic/res /oic/res /oic/res /oic/d /oic/d /oic/d oneM2M services with oneM2M interfaces /oic/d Mirroring oneM2M & OIC devices Sync OIC devices via OIC interfaces /lightSwitch /lightSwitch /lightSwitch /lightSwitch value value

Download ppt "Fuctional Procedure for oiC interworking"

Similar presentations

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:
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
Discussion on oneM2M HTTP Binding Interoperability Test Spec.

Discussion on oneM2M HTTP Binding Interoperability Test Spec.
Device Management using mgmtCmd resource

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

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

On Management, Abstraction & Semantics
RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: 2013-10-21 Agenda Item:

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.

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
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: 2013-11-19 Agenda Item:

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: 2015-03-25 Agenda Item:

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
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
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: 2013-11-26 Agenda Item:

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: 2014-04-07 Agenda Item: Management.

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

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.

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

Similar presentations

Ads by Google