1. OIC device management interworking procedure
Other suggested titles:
“Benefits of oneM2M Standardization”
Group Name: Architecture WG
Source: Sungchan Choi, KETI,
Jieun Keum, Samsung Electronics,
Kiran Vedula, Samsung Electronics,
SeonHyang Kim, DT&C,
Meeting Date: < >
Agenda Item: <WI 44: oneM2M-OIC interworking >

2. Introduction
This presentation introduces possible interworking method of Device Management for OIC interworking
Introduction of OIC DM
Resource mapping for OIC DM
Procedure illustration for OIC DM interworking

3. OIC Device Management oic/mnt (maintenance) oic/mon (monitoring)
OIC supports simple device management with two OIC resources, oic/mon and oic/mnt
oic/mon (monitoring)
Resource which collects Device Statistics like packets sent, packets received, last acted time etc.
oic/mnt (maintenance)
Resource which enables execute actions on resources like Reboot, Factory Reset and Start Statistics Collection etc.
These resources can be mapped to oneM2M <container> and <contentInstance> as same with other OIC resources for interworking.

4. OIC mon -> oneM2M Resource Mapping
Container
Monitoring
Resource URI: /oic/mon
Resource type: Container
rt: oic.wk.mon
Resource ID
if: oic.if.r
Resource Name
n: Monitoring
Parent ID
av: <res. def.>
Expiry Time
lat: <res. def.>
Creation Time
Last Modified Time
ds: <res. def.>
State Tag
OIC
Creator
Property title
Property name
Value type
Value rule
Unit
Acc ess mo de
Man dato ry
Description
Availability av
boolean
0 (not available)
1 (available) R
yes
Indicates if the device is available or not to provide service even though it is discoverable on the network
LastedActedTim e
lat
integer
sec
Indicates the elapsed time in seconds after the device was invoked or acted upon
DeviceStatistics ds
CSV no
Contains Device Statistics Info as a CSV of integers in that order (no. of received packets, no. of sent packets)
CurrentNrofInstances
CurrentByteSize
oneM2M

5. OIC mnt -> oneM2M Resource Mapping
Maintenance
Resource URI: /oic/mnt
Container
Resource type: Container
rt: oic.wk.mnt
Resource ID
if: oic.if.rw
Resource Name
n: Mainenance
Parent ID
fr: <res. def.>
Expiry Time
rb: <res. def.>
Creation Time
ssc: <res. def.>
Last Modified Time
OIC
State Tag
Property title
Prope rty name
Value type
Acces s mode
Mand atory
Description
Factory_Reset fr
boole an
R, W
yes
0 – No action (Default*), 1 – Start Factory Reset
After factory reset, this value shall be changed back to the default value
After factory reset all configuration and state data will be lost
Reboot rb
0 – No action (Default), 1 – Start Reboot
After Reboot, this value shall be changed back to the default value
The reboot shall be finished within 60 seconds
StartStatCollec tion
ssc
Yes
0 – No collection of statistics, 1 – Starts collecting statistics
Toggles between collecting and not collecting any device statistics (ds property in /oic/mon) depending on the value being 0 or 1
Creator
CurrentNrofInstances
CurrentByteSize
oneM2M

6. Monitoring
OIC client in IPE sends “RETRIEVE Request” message to the OIC device in Legacy OIC domain.
OIC device responds to the request message with the “/oic/mon” resource.
Based on the response message, IPE sends oneM2M resource CREATE request to the MN-CSE (conainer, contentInstance)
MN-CSE sends oneM2M resource CREATE response to the IPE
Assuming “/oic/mon” resource is synchronized with <container>, <contentInstance> in MN-CSE
In order to perform OIC device monitoring from oneM2M AE,
IN-AE sends <contentInstance> RETRIVE request to the MN-CSE via IN-CSE
MN-CSE sends <contentInstance> RETRIVE response to the IN-AE via IN-CSE

7. Diagnostics and maintenance
Precondition:
“/oic/mnt” resource in OIC device is already synchronized with <container>, <contentInstance> in MN-CSE.
IPE sends <subscription> CREATE request to the MN-CSE in order to receive notification message (Related event type is direct child resource creation)
MN-CSE sends <subscription> CREATE response to the IPE
IN-AE sends <contentInstance> CREATE request to the MN-CSE via IN-CSE
MN-CSE sends CREATE response to the IN-AE via IN-CSE
<contentInstance> creation triggers notification message delivering to the IPE
Based on notification message, OIC client sends “/oic/mnt” UPDATE request to the OIC Device in Legacy OIC domain
OIC Device send UPDATE response to the OIC client in IPE