Device Management A unified way of managing devices

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

Management Architecture Application X Infrastructure Node Intermediate/End Node CSE DMF Device in M 2 M Area Networks Proxy Management Client mp Y(mc) Management Adapter Proxy DMF Management Adapter Management Client Management Server Service Layer Underlying Network Z(mc) Z(ms) Management Server • TR-0006 studies the following device management technologies one. M 2 M Entities OMA DM 1. 3/2. 0 BBF TR 069 LWM 2 M Management Server DM Server ACS LWM 2 M Server Management Client DM Client CPE LWM 2 M Client Management Proxy DM Gateway Proxy Module - one. M 2 M-XXX-2013 -XXXX 2

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 1 D/G-CSE Resource Mapping Mca N-CSE <mgmt. Obj> Resource OMA DM MO OMA LWM 2 M Object <mgmt. Obj> Resource BBF TR-069 Object 2 (Mgmt Client) Device management technologies one. M 2 M-XXX-2013 -XXXX 3 Management operations (OMA, BBF) Management Request (Mgmt Server) Protocol Translations/ Resource Mapping 3

Device Management Resources Resource Instance Attribute The resource representation of a MO instance Identify the management functionality it provides <mgmt. Obj> 1 1 * * mo. ID= “urn: oma: mo: oma-fumo: 1. 0” original. MO <mo. Attributes> Referring to the local path of the original MO instance on the remote entity Leaf node of the original MO <parameters> 0 -1 original. MO * <mo. Attributes> * Intermediate node of the original MO < parameters> The structure can be nested one. M 2 M-XXX-2013 -XXXX 4

MO-Resource Mapping N-CSE OMA-DM FUMO mapping example OMA-DM FUMO <mgmt. Obj-x> mo. ID= “urn: oma: mo: oma-fumo: 1. 0” original. Mo: . /any. Path/fumo Pkg. Name Executable node (<parameters> subresource) Pkg. Version Update Command argument (<mo. Attributes> attribute) Pkg. Data … Execution result (<mo. Attributes> attribute) one. M 2 M-XXX-2013 -XXXX State 5

One. M 2 M Request Mapping one. M 2 M CRUD OMA DM 1. 3 (DM 2. 0) Cmd BBF-TR 069 Cmd CREATE Add (PUT) Add. Object Create a <mgmt. Obj> resource or its subresource DELETE Delete (DELETE) Delete. Object Delete a <mgmt. Obj> resource or its subresource. RETRIEV E Get (GET) Get. Parameter. Values, Get. Parameter. Attributes (Note 1) Read Retrieve management data from a <mgmt. Obj> resource or its sub-resource UPDATE Replace (PUT) Set. Parameter. Values, Set. Parameter. Attributes (Note 1) Write Update management data to a <mgmt. Obj> resource or its sub-resource UPDATE Exec (EXEC) Factory. Reset , Reboot, Upload, Download, Schedule. Inform, Change. DUState (Note 2) Execute a specific function which is represented by a <mgmt. Obj> resource or its sub-resources or attributes, or Invoke a specific TR 069 RPC command represented by a <mgmt. Cmd> resource. one. M 2 M-XXX-2013 -XXXX OMA LWM 2 M Description 6

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