Realizing Ms Interface with OMA DM Group Name

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, seungk. park@lge. com, LG Electronics Meeting Date: 2013 -10 -15 Agenda Item: TBD

Background • MAS WG has introduced the Ms interface Application X Infrastructure Node Intermediate/End Node CSE DMF Device in M 2 M Area Networks Proxy Management Client mp Management Adapter Proxy Y(mc) DMF Management Client Management Server Service Layer Underlying Network Z(mc) one. M 2 M-XXX-2013 -XXXX Management Adapter Z(ms) 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. Management Server 2

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 one. M 2 M-XXX-2013 -XXXX 3

Observations Infrastructure Node Management Domain End Node CSE DMG CSF Ms Interface DM Server OMA DM (Mc) DM Client • 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. one. M 2 M-XXX-2013 -XXXX 4

Related OMA DM Enabler • OMA DM Gw. MO is the key enabler – Gw. MO Proxy Mode Operations • DMG CSF can deliver management operations to the DM Client using OMA DM Gw. MO Architecture one. M 2 M-XXX-2013 -XXXX Infrastructure Node Management Domain End Node 5

Simple Overview Infrastructure Node Management Domain CSE DM Server DMG CSF DM Server OMA DM (Ms) OMA DM (Mc) End Node DM Client DM GW • 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 one. M 2 M-XXX-2013 -XXXX 6

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

Interworking with BBF TR-069 Infrastructure Node Management Domain CSE DM Server DMG CSF DM Server OMA DM (Ms) End Node OMA DM (Mc) DM Client CWMP (Mc) CWMP dev DM GW ACS • 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 V 1. 1 (on-going) • Detailed specification will be provided for Zig. Bee, Open. Web. Net, Bluetooth, KNX • Note: BBF TR-069 is not considered in the Gw. MO 1. 1, but general adaptation rules are described in Gw. MO 1. 0 one. M 2 M-XXX-2013 -XXXX 8

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

Benefits • Leveraging existing OMA DM standards – one. M 2 M 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 one. M 2 M-XXX-2013 -XXXX 10