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

Slides:



Advertisements
Similar presentations
NetComm Wireless Remote management via TR- 069 Feature Spotlight.
Advertisements

CMDH Refinement Contribution: oneM2M-ARC-0397
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:
Chapter 10 ADO. What is ADO? ADO is a Microsoft technology ADO stands for ActiveX Data Objects ADO is a programming interface to access data in a database.
Semantic Annotation Options for Release2 Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.
Discussion on oneM2M HTTP Binding Interoperability Test Spec.
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:
Interoperability in the Cloud By Alex Espinoza
Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
REST - Introduction Based on material from InfoQ.com (Stefan Tilkov) And slides from MindTouch.com (Steve Bjorg) 1.
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
Usage Scenarios for CSE Group Name: WG2(ARC-WG) Source: Shingo Meeting Date: Agenda Item: Message.
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
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.
Cairngorm Microarchitecture. Pronunciation Cairngorm (kârn gôrm) n. yellowish-brown variety of quartz, especially found in Scottish Cairngorm mountain.
Proposal for WG3 & WG5 work area split
Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:
Overview of analysis of existing SDO M2M architectures Group Name: REQ ARC#2 Source: Alcatel-Lucent.
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.
An introduction to oneM2M
Web Technologies Lecture 10 Web services. From W3C – A software system designed to support interoperable machine-to-machine interaction over a network.
LWM2M Interworking Group Name: Architecture
Intro to Web Services Dr. John P. Abraham UTPA. What are Web Services? Applications execute across multiple computers on a network.  The machine on which.
M2M Service Session Management (SSM) CSF
Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless
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,
Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.
M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:
3GPP SCEF Interworking Discussions
LWM2M Interworking Proxy Procedures ARC Considerations
M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:
WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
DICOMwebTM 2015 Conference & Hands-on Workshop University of Pennsylvania, Philadelphia, PA September 10-11, 2015 DICOMweb Workflow API (UPS-RS) Jonathan.
Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,
CMDH and Policies Contribution: oneM2M-ARC-0603
FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,
Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, 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:
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
Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:
Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.
Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.
Protocol Bindings Joint oneM2M Call, 31 Aug 2016.
Background Data Transfer
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
Possible options of using DDS in oneM2M
Discussion about Use Case and Architecture in Developer Guide
Proposed design principles for modelling interworked devices
MAF&MEF Interface Specification discussion of the next steps
3GPP Interworking Abstraction
Considering issues regarding handling token
CMDH Refinement Contribution: oneM2M-ARC-0397R01
On Management, Abstraction & Semantics
An introduction to oneM2M
3GPP V2X Interworking Potential Impact
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Presentation transcript:

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

oneM2M-XXX-2013-XXXX Motivations To execute management commands in End Node or Intermediate Node (e.g. M2M Devices or Gateways), is one of DMG CSF’s functions. The Infrastructure Node should be able to expose management resources to M2M Network Applications. The Infrastructure Node should provide general approach or interface for M2M Network Applications to issue management commands. M2M Network Applications do not need to understand underlying management protocols between remote entities and Management Server. Existing Management protocols using non-RESTFUL commands and RPCs (e.g. BBF) need to be enabled through the DMG CSF functionality 2

oneM2M-XXX-2013-XXXX mgmtCmd and execInstance 3 0::1 1 1 “attribute” n execStatus execResult execDisable execRegArgs n “attribute” n execInstances 1 cmdType execReqArgs execEnable 1 1 0::1

oneM2M-XXX-2013-XXXX Attributes: mgmtCmd execInstance Attribute NameMandatory /Optional TypeDescription expirationTimeMRWSee clause 9.X.X Common attributes. accessRightIDMRWSee clause 9.X.X Common attributes. searchStringsMRWSee clause 9.X.X Common attributes. creationTimeMROSee clause 9.X.X Common attributes. lastModifiedTimeMROSee clause 9.X.X Common attributes. descriptionORWthe text-format description of this resource cmdTypeMWOThe type to identify the command (e.g. urn:bbf:tr069:download). execReqArgsORWStructured attribute (e.g. abstract type) to contain any command- specific arguments of the request. execEnableMROThe attribute can be blank without any value or it can contain a URI that can be used to trigger execution of using UPDATE method. 4 Attribute NameMandatory /Optional TypeDescription expirationTimeMROSee clause 9.X.X Common attributes. accessRightIDMRWSee clause 9.X.X Common attributes. creationTimeMROSee clause 9.X.X Common attributes. lastModifiedTimeMROSee clause 9.X.X Common attributes. execStatusMROThe status of. It can be initiated, started, finished, cancelled, or deleted. execResultMROThe execution result of. execDisableORWThe attribute is used to cancel using UPDATE method, execRegArgsORWStructured attribute (e.g. abstract type) to contain any command- specific arguments used to trigger this.

A Simple Use Case Description: An M2M Network Application needs to issue management commands (e.g. Download) to a remote entity (e.g. an M2M device) Required Procedures: – 1: Create a mgmtCmd Either the AE or the CSE itself create a mgmtCmd resource at an Infrastructure Node – 2: Create a command instance for each AE issue Either the AE or the CSE itself create a mgmtCmd resource at an Infrastructure Node Execute a mgmtCmd The M2M Network Application as an AE triggers to execute the mgmtCmd at the Intermediate Node/End Node via the Infrastructure Node. – 3: Retrieve a mgmtCmd The M2M Network Application as an AE retrieves execution results from the Infrastructure Node.

Create mgmtCmd CSE D2 CSE I1 (e.g. Infrastructure Node) Mcc BBF Mgmnt Server (e.g. ACS) BBF Mgmnt Client Ms DM Protocols mgmtCmd (e.g. ) AE A (e.g. M2M Network Application) AE B (e.g. User Application) CSE D1 Mcc OMA Mgmnt Client OMA Mgmnt Server Ms DM Protocols Mca

Execute mgmtCmd CSE D2 CSE I1 (e.g. Infrastructure Node) Mcc BBF Mgmnt Server (e.g. ACS) BBF Mgmnt Client Ms DM Protocols mgmtCmd (e.g. ) execInstanceA1 execInstanceA2 execInstanceB1 execInstanceB2 AE A (e.g. M2M Network Application) Mca AE B (e.g. User Application) Mca CSE D1 Mcc OMA Mgmnt Client OMA Mgmnt Server Ms DM Protocols

Execute mgmtInstance CSE D2 CSE I1 (e.g. Infrastructure Node) Y BBF Mgmnt Server (e.g. ACS) BBF Mgmnt Client Ms DM Protocols mgmtCmd (e.g. ) execInstanceA1 execInstanceA2 execInstanceB1 execInstanceB2 AE A (e.g. M2M Network Application) X AE B (e.g. User Application) X CSE D1 Y OMA Mgmnt Client OMA Mgmnt Server Ms DM Protocols

Execute management commands CSE D2 CSE I1 (e.g. Infrastructure Node) Y BBF Mgmnt Server (e.g. ACS) BBF Mgmnt Client Ms mgmtCmd (e.g. ) execInstanceA1 execInstanceB1 execInstanceC1 execInstanceC2 AE A (e.g. M2M Network Application) X AE B (e.g. M2M Network Application) AE C (e.g. M2M Network Application) X X CSE D1 Y OMA Mgmnt Client OMA Mgmnt Server Ms

Execute mgmtCmd CSE 2 (e.g. Intermediate Node/End Node ) CSE 1 (Infrastructure Node) AE 1 (e.g. M2M Network Application) Y X Management Server (e.g. ACS in BBF TR069) Management Client (e.g. CPE in BBF TR069) Ms DM Protocols Device or Gateway Normal Procedures: Step 1: AE 1 issues UPDATE method to ’s attribute execEnable. Step 2: CSE1 invokes the Management Server to trigger it to execute on Intermediate Node/End Node (i.e. device or gateway). Step 3 & 4: Management Server talks to Management Client using existing mgmt protocols, which could be non-RESTful. Step 5: Management Server passes execution results to CSE 1. Then CSE 1 stores the results in the sub-resource of. mgmtCmd (e.g. )

Retrieve mgmtCmd CSE 2 (e.g. Intermediate Node/End Node ) CSE 1 (e.g. Infrastructure Node) AE 1 (e.g. M2M Network Application) mgmtCmd (e.g. ) Y X Management Server (e.g. ACS in BBF TR069) Management Client (e.g. CPE in BBF TR069) Ms DM Protocols Device or Gateway 1 Normal Procedures: Step 1: AE 1 issues RETRIEVE method to the resource or its sub-resource (e.g. to retrieve execution status and/or execution result of ). Step 2: CSE1 returns a general response which includes the resource representation of the resource as included in Step 1. 2

Summary mgmtCmd provides a RESTful approach for realizing DMG CSF’s function. – i.e. to execute management commands in Intermediate Node/End Node such as devices or gateways. mgmtCmd can reside in Infrastructure Node and is exposed to M2M Network Applications for facilitating them to issue management commands in a RESTful and general manner. – i.e. mgmtCmd provides a unified and RESTful interface for network applications. With mgmtCmd, interactions between DMG CSF and existing Management Servers are hidden from or transparent to M2M Network Applications mgmtCmd supports multiple execution instances of the same command with improved flexibility and reduced overhead. mgmtCmd provides a good approach for conversion between RESTful methods and non-RESTful conventional management commands.