1. DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., yinjiaxin@huawei.com Meeting Date: 2014-7-28 Agenda Item: TBD

2. Current DM Execute The Originator shall be an IN-AE. The Originator shall request to execute a management command which is represented by an resource or its attribute by using an UPDATE operation. The request shall address the executable resource or its attribute and shall contain an empty body. Executable attribute include: Update for Firmware management Install, Uninstall, Activate and Deactivate for Software management Currently they are executed by sending Update to address the attribute without cn

3. Partial Addressing oneM2M supports partial retrieve, partial update, partial create and partial delete Which only manipulates attribute level of a resource. fr: AE to: CSE- ID/container op: Retrieve cn: attribute1 fr: AE to: CSE- ID/container op: Update cn: attribute2=value-x fr: AE to: CSE- ID/container op: Update cn: attribute3=value-y fr: AE to: CSE- ID/container op: Update cn: attribute1=NULL Partial RetrievePartial UpdatePartial CreatePartial Delete replace attribute2 from old value to value-x when attribute3 don’t have a value at first, value-y is newly assigned delete an attribute by assign value as NULL Inconsistency with DM Execute!

4. Solutions 1.Make DM execute an exception for partial Update. Update can address attribute for DM execute case. 2.Make all executable attributes to virtual resources. resources that have no representation, when addressed, triggers some operation (execute). 3.Design an reserved word for executable attributes Update: fr: IN-AE to: /cseBase/node1/firmware1 cn: update=EXECUTE 4.Change the current partial addressing Allow addressing attribute level 5.Add one additional request parameter exec exec=update-firmware exec=install-software Influences Inconsistency in the current ARC TS in addressing attributes Seems a big change currently The value of attribute is meaningless while confusing. Seems to have impact on partial create and partial delete. But more elegant for partial Update and partial Retrieve. What’s our decision? Seems option 3 is the only compromise? One new request parameter makes the current attribute nothing but for information

5. Thanks!