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

oneM2M-XXX-2013-XXXX Background MAS WG has introduced the Ms interface 2 Infrastructure Node CSE Application X Y(mc) Device in M2M Area Networks Management Server Z(ms) Service Layer Underlying Network DMF Intermediate/End Node DMF CSE Management Client Proxy Z(mc) Proxy Management Client Management Server mp Management Adapter Ms Interface The interface between the management adapter and the management server. Using this interface, systems can perform management operations on devices through the management server.

oneM2M-XXX-2013-XXXX Problem The Ms Interface has not been specified in any standardized forms – BBF TR-131 has specified requirements that can be referenced for Ms interface Many of the deployment scenarios in the section 7.2 (Mgmt TR) cannot be guaranteed because of the unspecified Ms interface 3

oneM2M-XXX-2013-XXXX Observations What is expected for Ms Interface? – DMG CSF delivers the mgmt operation to DM Server – DM Server performs it to DM Client on behalf of DMG CSF There is a similar analogy in OMA DM – DM Server delivers the mgmt operation to the DM GW – DM GW performs it to DM Client on behalf of DM Server Observation: OMA DM itself is a good candidate for Ms interface. 4 CSE DMG CSF Infrastructure NodeEnd Node DM Server Management Domain OMA DM (Mc) Ms Interface DM Client

oneM2M-XXX-2013-XXXX OMA DM GwMO is the key enabler – GwMO Proxy Mode Operations DMG CSF can deliver management operations to the DM Client using OMA DM GwMO Related OMA DM Enabler 5 Infrastructure Node Management Domain End Node OMA DM GwMO Architecture oneM2M

oneM2M-XXX-2013-XXXX Simple Overview DMG CSF takes the role of DM Server that connects to the DM GW in the Mgmt Domain – DM Server and DM GW can be implemented on the same entity – DM GW needs to support Fanout Management Object – Transparent Mode of OMA DM GW is not applied 6 CSE DMG CSF Infrastructure NodeEnd Node DM Server Management Domain OMA DM (Mc) OMA DM (Ms) DM Client DM GW DM Server

oneM2M-XXX-2013-XXXX Example 7 CSE DMG CSF DM Server DM GW DM Client Scenario: CSE needs to update the firmware of the device Configure Fanout MO - “Fanout/ /Target: DevID” - “Fanout/ /DMCommands”: execute./fumo/update Execute “./Fanout/ /Operations/Start” execute./fumo/update (command in “Fanout/ /DMCommands” is delivered) Results

oneM2M-XXX-2013-XXXX Interworking with BBF TR-069 Adaptation mode in OMA DM Gateway – This mode provides the capabilities for CSE to manage non-OMA-DM device – The major work area of OMA DM Gateway MO V1.1 (on-going) Detailed specification will be provided for ZigBee, OpenWebNet, Bluetooth, KNX Note: BBF TR-069 is not considered in the GwMO 1.1, but general adaptation rules are described in GwMO CSE DMG CSF Infrastructure NodeEnd Node DM Server Management Domain OMA DM (Mc) OMA DM (Ms) DM Client DM GW DM Server ACS CWMP dev CWMP (Mc)

oneM2M-XXX-2013-XXXX Hierarchical DM Gateway Support 9 CSE DMG CSF Infrastructure NodeEnd Node DM Server Management Domain OMA DM (Mc) OMA DM (Ms) DM Client DM GW DM Server Hierarchical Gateway Support – CSE can manage DM Client behind multiple DM Gateways – One of the major work area of OMA DM Gateway MO V1.1 (on-going) DM GW OMA DM (Mc)

oneM2M-XXX-2013-XXXX Benefits Leveraging existing OMA DM standards – oneM2M already supports OMA DM for device managements. Why not using more? Low overall complexities for device mgmts – One Protocol Translation at DMG CSF is enough – Otherwise; Two Protocol Translations are required One at the DMG CSF The other at the Management Domain 10