7.1 Representation of non-oneM2M Proximal IoT Devices

From a device management perspective in oneM2M, a device is represented using a <node> resource. All management related capabilities of a device are then represented using child resources (<mgmtObj> children or [flexNode] child and its <flexContainer> children) of this <node> resource. This principle shall also be applied for non-oneM2M Proximal IoT devices (which are NoDNs), i.e. all aspects of device management of a device subject to device management methods defined in oneM2M should be exposed by using child resources of a <node> resource. The <node> resource instances representing device management aspects of non-oneM2M Proximal IoT devices shall be created by the responsible IPE on the IPE's Registrar CSE.

Note

The CSE-based DM approach uses <mgmtObj> children of the <node> resource, as described in clause 10.2.8 of oneM2M TS-0001 [2] and Annex D of oneM2M TS-0004 [8]. For the IPE-based DM approach with Smart Device Template (SDT), as presented in this document, the IPE creates on its registrar CSE a [flexNode] <flexContainer> specialization as child of the <node> resource, and exposes the device management capabilities of the device as <flexContainer> specializations mapping DM SDT modules, children of the [flexNode] resource. The operations on these DM SDT modules are presented in clause 8.

If the device complies to oneM2M-defined information models - such as the ones defined in oneM2M TS-0023 [3] - the device should be represented using the respective specializations of resources specified in oneM2M. For example, a home domain device for a light as defined in oneM2M TS-0023 [3] is represented using the corresponding specializations of <flexContainer> defined by the [deviceLight] resource type. If the information model of the device is not defined by oneM2M, a <flexContainer> may also be used with its containerDefinition attribute configured with a URI linking to the schema definition for that device type specified by the respective organization. Also if the <flexContainer> resource represents a non-oneM2M Proximal IoT device, the resource may be linked with the corresponding <node> resource that is used to reflect device management aspects of the device or to indicate relationship(s) to applications on the device represented by <AE> resource instances, if applicable. The instances of specializations of <flexContainer> resource types representing non-oneM2M Proximal IoT devices shall be created by the responsible IPE on the IPE's Registrar CSE. The preferred parent resource for such specialization of <flexContainer> resource instances is the IPE's own <AE> resource instance. The linkage between an instance of a specialization of the <flexContainer> resource type, representing a non-oneM2M Proximal IoT device, and the corresponding <node> resource instance, that is used to reflect device management aspects or relationships to applications of the device, shall be established as follows:

A nodeLink attribute of the <flexContainer> specialization instance, representing the non-oneM2M Proximal IoT device, shall point to the <node> resource instance, which contains a [flexNode] <flexContainer> specialization that has as children <flexContainer> resources corresponding to SDT DM module classes defined in TS-0023 clause 5.8.For devices that do not follow any standardized information model nor have any management requirements, there is no distinct resource types to be instantiated in the oneM2M system for the representation of the device.