1. Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless (ndamour@sierrawireless.com)ndamour@sierrawireless.com Meeting Date: 2014-04-07 Agenda Item: tbd

2. Problem statement 1/2 Management objects have been defined as a resource type that can be “instantiated” into firmware, memory, etc. Yet these different “instances” have some common attributes (mgmtDefinition, objectID, objectPath, description) and some specific attributes => are we not looking in reality at different resource types sharing some common attributes?

3. Problem statement 2/2 We want to make some resources manageable through DM technologies: cmdhPolicy, statsConfig => we make them “instances” Some resources may be managed by DM technologies or not: schedule, locationPolicy? => do we also make them “instance”? Answer: NO, we only need the attributes!

4. Proposal - Theory The “core” resource structure represents the Service Plane of oneM2M and the core CSFs: – Addressing, Identification and Registration – Discovery – Data Management & Repository – Subscription & Notification – Group Management – Communication Management & Delivery Handling – Location – Network Service Exposure

5. Proposal - Theory Other planes constitute the “enabler CSFs”: – The Security Plane (Security CSF) injects the common attributes it needs (accessControlPolicyID) onto the resources it will affect (currently: all!) – The Management Plane (Management CSF) injects the attributes it needs (mgmtDefinition, objectID, objectPath, description) onto the resources it will affect (i.e. for which DM technology is used) – The Charging Plane (Service Charging and Accounting CSF) may inject attributes onto resources for the purpose of collecting statistics when these resources are used.

6. Proposal - Practice The common attributes should comprise: – General purpose attributes: resourceType, parentID, creationTime, expirationTime, lastModifiedTime, versionTag, labels, creator, link, announceTo, announcedAttribute – “Injected” Security Enabler attributes: accessControlPolicyID – “Injected” Management Enabler attributes: mgmtDefinition, mgmtObjectID, mgmtObjectPath, mgmtDescription To solve our problem, any resource that needs to be managed through an external DM technology will have these attributes defined