oneM2M Logo transparent 196x130

Standards for M2M and the Internet of Things

Introduction-Implementation

Assumptions

  • All the applications are server capable;
  • Devices and application entites are independently addressable with host names resolved by DNS network services;
  • Host port number 8080 is reserved for oneM2M services;
  • Security is not considered in the current use case;
  • HTTP binding of oneM2M primitives is used in the current use case;
  • Both XML and JSON 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;
  • The IN-CSE and MN-CSE in the current use case are deployed within the same oneM2M Service Provider domain;
  • All AEs in the current use case are initially registered with CSEs and the identifier of the AEs are assigned by the Registrar CSE of the AE accordinlgy, starting with a character of ‘C’;
  • 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 and it is used for MN-CSE registration with IN-CSE;
  • All request originators send Blocking Requests for accessing resources located in CSEs.

 

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.