1. Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., yinjiaxin@huawei.com Meeting Date: 2014-3-10 Agenda Item: TBD

2. Current statues Please refer to ARC-2014-1194- Node_resolution as the background

3. Problem list Issue one: – How to represent devices in the M2M Area Network in our current resource structure? Issue two: – What resource to address if AE wants to manage something? Issue three: – How to correlate the physical device id and something in the service layer? Issue four: – What is the resource structure relate to management? © 2013 oneM2M Partners 3

4. Issue One We use Node to represent MN\ASN\ADN currently Do we still use Node to represent devices in the M2M Area Network? Or do we introduce a new resource type (attachedDevice as an example)? May be a little hard since TS0001 has frozen. Decision Point 1 Decision Point 2

5. Issue Two: We currently address Node to manage memory, storage, power and topology. We currently address application to manage corresponding software. We need to attach the other mgmtObjs to some where. We also need to solve the inconsistencies such as storage, power and networkTopology.

6. Issue Two Proposal – Attach every mgmtObj to Node – Delete storage as it’s a not supported mgmtObj – Change Power to battery – Change networkTopology to areaNwkInfo – Delete software under application Decision Point 3

7. Issue Three M2M-Node-ID is the identifier to ADN, ASN and MN. Seems M2M-Node-ID is a volunteer identifier for service layer representative of devices. Need to consider the relationship between Node-ID and CSE-ID – 1:1, one CSE per Node (Suggested from my side in R1) – m:1, multiple CSEs per Node is where the identifier of physical device (devId) is kept. – Multiple per Node? The Node may be distributed over several devices. Distributed system or backup case. – Only one per Node? Restrict to one Node one physical device – may be shared by multiple Node? Multiple Nodes running on one physical device. Virtual machine case, sandboxed Node instances.

8. Issue Three Proposal – Node and CSE one to one mapping – One Node could have multiple – As well as one can be shared by multiple Nodes. Decision Point 4

9. Issue Four hostedCSEId 11 nodeLink 0…1 0…1 0…1 0…n

10. Issue Four-Proposal Decision Point 5 hostedCSEId 0…n 0…1 nodeLink 0…1 0…1 nodeLink 0…1 Management shall only be performed through IN All Node attached to only IN All mgmtObj can only be found under Node Management Adaptor on ASN-CSE and MN- CSE can communicate with IN-CSE to update corresponding Node resource over Mcc r/p

11. Thanks!