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

2. 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

3. 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 (Optional) The M2M Network Application as an AE creates a mgmtCmd resource at an Infrastructure Node (i.e. a CSE). – 2: 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. AE 1 (e.g. M2M Network Application) CSE 1 (e.g. Infrastructure Node) Intermediate Node/End Node (e.g. M2M Device) XY

4. Create mgmtCmd CSE 2 (e.g. Intermediate Node/End Node ) CSE 1 (e.g. 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 1 Normal Procedures: Step 1: AE 1 issues CREATE method to create a new mgmtCmd (e.g. ). Step 2: CSE1 create s a new mgmtCmd resource. (e.g. ) an sends the response back to AE 1. mgmtCmd (e.g. ) 2

5. 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 1 2 3 4 5 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. )

6. 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

7. 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.