5 Introduction

Devices in the Field Domain that host oneM2M AEs and CSEs require configuration that permits the AE or CSE to successfully operate in the M2M Service Layer. oneM2M TS-0001 [2] and oneM2M TS-0003 [3] specifies much of what is needed to configure these devices in the Field Domain (i.e. ADN, ASN/MN). Specifically, oneM2M TS0001 [2] provides:

  • Guidance on how a CSE is minimally provisioned in Annex E of the specification including how a user AE is established within a Hosting CSE.
  • Specification of the general communication flows across the Mca and Mcc reference points in clause 8.
  • Specifications for how ASN/MN and ADN nodes and M2M Applications are enrolled in the M2M System such that the node in the Field domain can establish connectivity with a CSE. TS-0001 heavily relies on Clause 6 and on the Remote Security Provisioning Framework (RSPF) of oneM2M TS-0003 [3] to specify how the security credentials of ASN/MN and ADN nodes and M2M Applications are established in the M2M System for the enrolment of the node or M2M Application in the M2M System.
  • Specifications for how the ADN and ASN/MN nodes in the Field Domain are managed using external management technologies in clause 6.2.4 of oneM2M TS0001 [2].
  • Guidance for how the ADN and ASN/MN nodes in the Field Domain can be configured without the support of external management technologies in clause 8.1.3 in the present document.

The above clauses in oneM2M TS-0001 [2] assume that, for a M2M Application to operate in the M2M System, all required information needed to establish M2M Service operation between a Registrar or Hosting CSE and the AE or CSE in the Field Domain is configured before registration of the AE or CSE to the M2M System.

The present document specifies the additional architectural elements, resources and procedures necessary to configure ASN/MN and ADN nodes in the Field Domain in order for that device to establish M2M Service Layer operation. These architectural elements, resources and procedures are in addition to the architectural elements, resources and procedures already defined in oneM2M TS-0001 [2] and oneM2M TS-0003 [3].