OIC device management interworking procedure

Slides:

Advertisements

Similar presentations

Introduction to Parent Accounts from:

Advertisements

Introduction to Parent Accounts. Parent accounts on Edmodo are a great way to enable parents to stay up to date on their child’s classroom activities,

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

NetComm Wireless SMS Diagnostics and Commands Feature Spotlight.

Device Management using mgmtCmd resource

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

On Management, Abstraction & Semantics

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

VLAN Trunking Protocol (VTP)

VLAN Trunking Protocol (VTP)

oneM2M-OIC Interworking Technical Comparison

XML Datatype for list of child resource references Source: Sungchan Choi, Yong-Suk Park, Jaeho Kim (KETI) Data: PRO Introducing_DataType_for_List_of_Child-Resource-Ref.

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

C3 confidentiality classificationIntegrated M2M Terminals Introduction Vodafone MachineLink 3G v1.0 1 Vodafone MachineLink 3G SMS Diagnostics and Commands.

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: Agenda Item: ARC11/PRO11.

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: ~24.

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

Fuctional Procedure for oiC interworking

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Proposal for WG3 & WG5 work area split

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

State Devices (The Untold Story) Brian Hendricks.

Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Scenarios for oneM2M and OIC Interworking

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

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

3GPP Rel-13 Interworking discussions

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.

VLAN Trunking Protocol (VTP)

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

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

LWM2M Interworking Proxy Procedures ARC Considerations

Example mapping of KNX to oneM2M base Ontology

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jinhyeock Choi, Samsung Electronics,

3GPP R13 Small Data Delivery

Service Enabled AE (SAE)

Group multicast fanOut Procedure

Possible options of using DDS in oneM2M

NIDD Discussion Points

ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC

LWM2M Interworking with <mgmtObj> Resources

CMDH Refinement Contribution: oneM2M-ARC-0397R01

MinitorEvent(UE_Reachability)

Network Services Interface

On Management, Abstraction & Semantics

3GPP V2X Interworking Potential Impact

3GPP Interworking and use of <schedule> resource

Presentation transcript:

OIC device management interworking procedure Other suggested titles: “Benefits of oneM2M Standardization” Group Name: Architecture WG Source: Sungchan Choi, KETI, sungchan.keti@gmail.com Jieun Keum, Samsung Electronics, je.keum@samsung.com Kiran Vedula, Samsung Electronics, kiran.vedula@samsung.com SeonHyang Kim, DT&C, shkim@dtnc.net Meeting Date: <2015-11-04> Agenda Item: <WI 44: oneM2M-OIC interworking >

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

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.

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

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

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

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