oneM2M Logo transparent 196x130

Standards for M2M and the Internet of Things

TR-0045 Implementation introduction

Assumptions

Assumptions are presented as below in order to ensure the semantic annotation and discovery use case can be correctly implemented:

  • Security is not considered in the current use case.

  • HTTP binding of oneM2M primitives is used in the current use case.

  • XML serializations of oneM2M primitives are used in the current use case.

  • All mandatory HTTP headers are presented in the HTTP requests while optional headers are selectively used in the current use case.

  • All mandatory resource attributes for resources presented in the current use case are presented in the HTTP requests while optional resource attributes are selectively used in the current use case.

  • All AEs in the current use case are initially registered with the IN-CSEs and the identifier of the AEs are assigned by it acting as the Registrar CSE of the AE.

  • All resources created in the current use case are addressable with the oneM2M Resource Identifier form of Hierarchical address.

  • Short names for the representation of the resources and attributes are used in the current use case.

  • Default access control policy has already been created under IN-CSE.

  • All request originators send Blocking Requests for accessing resources located in CSEs.

Role of Entities

1) oneM2M service platform (IN-CSE)

The oneM2M service platform is modelled as an IN-CSE and is responsible for

  • handling the registration requests from all ADN-AEs in the use case;
  • creating and managing the resource structures for storing sensor information and semantic annotations;
  • executing semantic resource discovery.

2) Temperature sensor applications (ADN-AE1, ADN-AE2, ADN-AE3 and ADN-AE4)

Each of the temperature sensor applications are modelled as an ADN-AE and are responsible for:

  • measuring the sensor information;
  • registering the temperature sensors with the IN-CSE;
  • creating container resources named "temperature";
  • creating content instance resources under the container "temperature" that contain the temperature measurements.

3) Semantic Annotation Application (ADN-AE5)

The semantic annotation application, which is expected to run on a smartphone or other device with user interface is responsible for the following:

  • enable the user to create semantic annotations for resources representing sensors;
  • create semantic descriptor resources as child resources of sensor AE resources that contain the semantic annotations.

4) Semantic Discovery Application (ADN-AE6)

The semantic discovery application, which is expected to run on a user device, is responsible for the following:

  • enable the user to formulate the semantic filter for the semantic discovery (in SPARQL);
  • retrieve the semantic annotation for discovered resources;
  • retrieve sensor measurements based on the semantic annotations.
Subscribe to oneM2M News Please enter your name and email address, then click on submit.
Alternatively, you can send an email from your preferred email application with a blank subject to
Listserv@list.etsi.org with subscribe oneM2M_News in the message body.

Subscribe to oneM2M News

Your Name(*)
Please let us know your name.

Your Email(*)
Please let us know your email address.