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

Slides:

Advertisements

Similar presentations

Gateway Agent Product & Architecture

Advertisements

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

FI-WARE – Future Internet Core Platform FI-WARE Cloud Hosting July 2011 High-level description.

Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date:

WG5 - MAS Progress Report at TP #12 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

© 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

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

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

oneM2M-OIC Interworking Technical Comparison

Step by step approach Group Name: WG2

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

LWM2M Interworking Object Instantiation Group Name: Architecture Source: ALU (TIA) Meeting Date: Arc 17.2 Agenda Item: LWM2M Interworking.

Fuctional Procedure for oiC interworking

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Proposal for WG3 & WG5 work area split

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

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

Device Management with OMA Lightweight M2M

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

OIC device management interworking procedure

Role Based Access Control In oneM2m

LWM2M Interworking Group Name: Architecture

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,

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

MDB Motorola Internal Use Only 1 21-August-2006 DM/FOTA Component Overview Elliot Stewart.

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

LWM2M Interworking Proxy Procedures ARC Considerations

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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,

Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

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 Solution of Interworking between oneM2M and OSGi

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

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

Resource subscription using DDS in oneM2M

Provisional Architecture for oneM2M

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Issues of <locationPolicy> Discussion

Discussion about Use Case and Architecture in Developer Guide

MAF&MEF Interface Specification discussion of the next steps

Proximal IoT Interworking solution discussion

oneM2M Work on IoT Semantic and Data Model Interoperability

Considering issues regarding handling token

Discussion on feature catalogue

LWM2M Interworking with <mgmtObj> Resources

On Management, Abstraction & Semantics

3GPP V2X Interworking Potential Impact

CWMP BOF August 6, 2012 Redmond, WA PWG F2F Meeting

SMART HOME Expectation IN STANDARDS

Presentation transcript:

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd. ; LG Electronics Meeting Date: 2013-10-14 Agenda Item: TBD

Management Architecture Infrastructure Node CSE Application X Y(mc) Device in M2M Area Networks Management Server Z(ms) Service Layer Underlying Network DMF Intermediate/End Node Management Client Proxy Z(mc) Proxy Management Client mp Management Adapter TR-0006 studies the following device management technologies oneM2M Entities OMA DM 1.3/2.0 BBF TR069 LWM2M Management Server DM Server ACS LWM2M Server Management Client DM Client CPE LWM2M Client Management Proxy DM Gateway Proxy Module -

Mgmt Capabilities exposed over Mca Applications can manage devices using services exposed over Mca Application Software installation and settings, Configuration settings and Provisioning, Firmware Updates, Logging, Monitoring, Diagnostics, etc. N-AE Management Request 1 Mca Resource Mapping D/G-CSE N-CSE <mgmtObj> Resource OMA DM MO <mgmtObj> Resource OMA LWM2M Object Protocol Translations/ Resource Mapping <mgmtObj> Resource BBF TR-069 Object 2 (Mgmt Client) Device management technologies (Mgmt Server) 3 Management operations (OMA, BBF)

Device Management Resources Resource Instance Attribute The resource representation of a MO instance Identify the management functionality it provides <mgmtObj> 1 moID= “urn:oma:mo:oma-fumo:1.0” 1 originalMO Referring to the local path of the original MO instance on the remote entity * <moAttributes> * Leaf node of the original MO <parameters> 0-1 Intermediate node of the original MO originalMO * <moAttributes> * < parameters> The structure can be nested

originalMo: ./anyPath/fumo MO-Resource Mapping N-CSE OMA-DM FUMO mapping example OMA-DM FUMO <mgmtObj-x> moID= “urn:oma:mo:oma-fumo:1.0” originalMo: ./anyPath/fumo PkgName Executable node (<parameters> sub-resource) PkgVersion Update Command argument (<moAttributes> attribute) PkgData … Execution result (<moAttributes> attribute) State

OneM2M Request Mapping oneM2M CRUD OMA DM1.3 (DM2.0) Cmd BBF-TR069 Cmd OMA LWM2M Description CREATE Add (PUT) AddObject Create Create a <mgmtObj> resource or its sub-resource DELETE Delete (DELETE) DeleteObject Delete Delete a <mgmtObj> resource or its sub-resource. RETRIEVE Get (GET) GetParameterValues, GetParameterAttributes (Note 1) Read Retrieve management data from a <mgmtObj> resource or its sub-resource UPDATE Replace (PUT) SetParameterValues, SetParameterAttributes Write Update management data to a <mgmtObj> resource or its sub-resource Exec (EXEC) FactoryReset , Reboot, Upload, Download, ScheduleDownload, ScheduleInform, ChangeDUState (Note 2) Execute Execute a specific function which is represented by a <mgmtObj> resource or its sub-resources or attributes, or Invoke a specific TR069 RPC command represented by a <mgmtCmd> resource.

Mgmt High Level Procedures D-CSE G-CSE N-CSE N-AE <mgmtObj> created on N-CSE (by D/G/N-CSE, N-AE, or provisioning means) RESTful (C/R/U/D) access to <mgmtObj> or its components Resource mapped to existing MOs, RESTful Operation mappied to existing DM commands Device management procedures (OMA DM, LWM2M, BBF TR-069) RESTful response (status code, acquired information, …) Mcc Mca