5.4 ADN profile 3
5.4.1 Profile description
This profile defines features for normal sensor devices or software components that desire to implement oneM2M sensing services. The sensing services such as monitoring temperature, detecting illumination, collection of location information etc are characterized with collecting and uploading measurement data into a destination e.g. a repository. The scope of normal sensor devices cover those that are powered by electricity power or by battery that can be easily changed when the battery is off and have rich resources compared to resource-constraint sensor devices.
The sensing service profile defines a set of features required to implement sensing functionalities including creation and update of <container>, creation of <contentInstance> etc.
5.4.2 Profile usage examples
This profile applies to normal sensors deployed in non critial environments have relative rich resources and are powered by electricity power or by battery that can be easily changed. This profile can also apply to software components that implements sensing services.
Taking smart socket as an example, when a manufacturer-A decides to design a smart socket with oneM2M sensing service, he can refer to the Sensing Service Profile to check the fundamental features that are required to implement. The fundamental features for Sensing Service Profile are defined in Section 7.4.3 Feature Set. When another manufacturer-B also designs a smart socket complying with the Sensing Service Profile, these two smart sockets produced from two different manufacturers are interoperable potentially to work together to implement complex tasks.
5.4.3 Fundamental feature sets
Container is used for storing the measurements of sensing device and whenever there is data measured from the sensing device, the data will be sent to the CSE for storage by sending a <contentInstance> create request from the originator where the encoded measurement is included within the payload of the <contentInstance> create request.
oneM2M sensing service profile consists of minimum features to implement Data Management for Container and ContentInstance functionality shown in Table 7.4.3-1.
Table 5.4.3-1: Fundamental feature set for ADN profile 3
| Function | Feature Set | Feature | Remark |
|---|---|---|---|
| GEN | AE/GEN/00001 | At least one | Support one of the format of resource identification |
| AE/GEN/00002 | AE/GEN/00002/00001 | Support Create request targeting one resource | |
| REG | AE/REG/00002 | AE/REG/00002/00001 | Create <AE> with mandatory attributes |
| DMR | AE/DMR/00001 | AE/DMR/00001/00001 | Create <container> with no attribute set |
| AE/DMR/00002 | AE/DMR/00002/00001 | Create <contentInstance> with mandatory attributes | |
| SUB | AE/SUB/00004 | AE/SUB/00004/00001 | Receiving a notification |