Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management of policies

Background At TP#9, the resource type was introduced into TS-0001 It has been agreed that CMDH policies are subject to Service Management Discussions on how to map policies to mgmtObj resources started at TP#9, and were continued in some offline discussions, but are not yet concluded © 2014 oneM2M Partners MAS

Characteristics of CMDH Policies Represent a set of rules which define how remotely hosted resources can be accessed via the CMDH CSF CMDH policies are required and executed in field entities, i.e. ASN-CSE and MN-CSE CMDH policies represent rules which need to be – provisioned to field entities before these can start communication with other entities – managable remotely by the M2M service provider © 2014 oneM2M Partners MAS

Excerpt from TS-0001v0.4.3, clause The resource type represents a set of rules defining which CMDH parameters will be used by default when a request issued by a local originator (eg. locally registered AE or another CSF inside the local CSE) contains the “ec” parameter but not all other CMDH parameters. One or several resources of type may be linked as child resources of the local resource, thus defining a set of CMDH policies applicable whenever this local hosting CSE receives requests. In addition, one or several resources of type may be linked as child resources of other resources of type or, thus overriding the default set of policies for the relevant locally registered Application Entities or remote CSEs. © 2014 oneM2M Partners MAS

Options to associate CMDH policies with resources 1.Define a new parent resource of type which includes a link to a resource 2.Redefine the existing resource as a resource of type and all its child resources as of type 3.Redefine the existing resource and all its child resources as of type. Include references to child resources in form of links © 2014 oneM2M Partners MAS

Option 1 Pro: no redefinition of the existing resource type required Con: entire cmdhPolicy resource tree must be mapped to a management object of the external DM technology, no addressing of sub- resources possible Resource type fixed value “cmdhPolicySet” URI to a resource in IN-CSE URN identifying external DM technology data model path of the external management object instance on the managed entity some optional text description of cdmhPolicySet © 2014 oneM2M Partners MAS

Option 2 Resource type all children (and their children) are of resource type Pro: all resources currently defined as children of (and their children) remain individually addressable Cons: requires to keep child resources in ; possibly large memory requirements for storage in IN-CSE; existing resource and all children need to be redefined (large impact on TS-0001) © 2014 oneM2M Partners MAS

Option 3 Resource type Attributes representing links to other instances of resources Pros: all resources currently defined as children of (and their children) remain individually addressable and can most easily be mapped to MOs of external DM technology, no need for child resources, minimal memory requirements for storage in IN-CSE Cons: existing resource and children need to be redefined (large impact on TS-0001) © 2014 oneM2M Partners MAS

Proposed Way Forward We suggest to go with option 3 A corresponding CR to TS-0001 is submitted in ARC Remaining issues that still need to be resolved: – Shall resource be deleted completely in TS-0001? – Shall these be replaced by [cmdhPolicy] MOs in the field entities, or removed entirely? © 2014 oneM2M Partners MAS