oneM2M TS-0030Release Notes diff from v5.0.0 to v5.0.0oneM2M TS-0030Release Notes diff from v5.0.0 to v5.0.0For the purposes of the present document, the terms and definitions given in oneM2M TS-0011 [1], oneM2M TS0012 [3] and the following apply:
Abstract Device: virtual Device (i.e. a set of oneM2M resources together with an IPE) that allows a communicating entity to communicate with an Interworked Device, using an Abstract Information Model, without the need to know the technology specific Device Information Model of that Interworked Device
Abstract Information Model: Information Model of common functionalities abstracted from a set of Device Information Models
Abstraction: process of mapping between a set of Device Information Models and an Abstract Information Model according to a specified set of rules
Abstraction Application Entity: specialized AE that communicates with an IPE and facilitates Abstraction by providing Services that translate between the Abstract Information Model and the Device Information Model of the IPE
Communicating Entity: oneM2M entity (usually an AE) that communicates with the IPE for the purpose of sending/receiving data from the Interworked Device
Device Information Model: Information Model of the native protocol (e.g. ZigBee) for the physical device
Interworked Device: non-oneM2M device (NoDN) for which communication with oneM2M entities can be achieved via an Interworking Proxy Application Entity (IPE)
Interworking Proxy Application Entity: specialized AE that facititates interworking between Non-oneM2M Nodes (NoDN) and the oneM2M System.
NOTE: An IPE maps data of the NoDN into oneM2M resources (Interworked Devices). It invokes operations in the NoDN when the related oneM2M resources are modified and modifies oneM2M resources based on the output of NoDN operations
Proxied Device: virtual device (i.e. a set of oneM2M resources together with an IPE) that represents the Interworked Device in the oneM2M System
Ontology - based Interworking: Ontology-based Interworking allows interworking with many types of Area Network containing non-oneM2M devices that are described in the form of a oneM2M compliant ontology which is derived from the oneM2M Base Ontology
NOTE: Ontology-based Interworking supports the interworking variant "full mapping of the semantic of the non-oneM2M data model to Mca" as indicated in clause F.2 of oneM2M TS-0001 [2].
For the purposes of the present document, the abbreviations given in oneM2M TS-0011 [1], oneM2M TS-0012 [3] and the following apply:
CE Communicating EntityIPE Interworking Proxy Application Entity