oneM2M Technical Specifications
This page provides a list of oneM2M’s technical specifications, which are available in their on-line form.
Note
This is a growing list of oneM2M technical specifications as they are migrated to the new online library.
You can find additional and previous technical specifications on the oneM2M website.
Please check back for updates.
| Technical Specification | Summary |
|---|---|
| TS-0001 Functional Architecture |
End-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. |
| TS-0002 Requirements |
Informative functional role model and normative technical requirements for oneM2M. |
| TS-0004 Service Layer Core Protocol |
Specifies the communication protocol(s) for oneM2M compliant systems, including common data formats, interfaces and message sequences to support oneM2M reference points. |
| TS-0005 Management Enablement (OMA) |
Specifies the usage of OMA DM and OMA LwM2M resources and the corresponding message flows including normal cases as well as error cases to fulfill the oneM2M management requirements. Mapping between the oneM2M management related resources and the resources from OMA. Protocol translation between the oneM2M service layer and OMA. The Mca reference point, ms interface and la interface are possibly involved in this protocol translation. Resource definitions in OMA to fulfill the oneM2M management requirements. |
| TS-0006 Management enablement (BBF) |
Specifies the usage of the BBF TR-069 protocol and the corresponding message flows including normal cases as well as error cases to fulfil the oneM2M management requirements. Protocol mapping between the oneM2M service layer and BBF TR-069 protocol. The Mca reference point, ms interface and la interface are possibly involved in this protocol mapping. Mapping between the oneM2M management related resources and the TR-069 protocol RPCs and TR-181i2 data model. Specification of new TR-181 data model elements to fulfil oneM2M specific management requirements that cannot be currently translated. |
| TS-0008 CoAP Protocol Binding |
Specifies the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful CoAP binding. |
| TS-0009 HTTP Protocol Binding |
Specifies the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. |
| TS-0010 MQTT Protocol Binding |
Specifies the binding of Mca and Mcc primitives onto the MQTT protocol. |
| TS-0013 Interoperability Testing |
Interoperability Test Descriptions for oneM2M primitives as specified in TS-0001 and TS-0004, and for the CoAP, HTTP and MQTT bindings. |
| TS-0014 LWM2M Interworking |
Specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints. |
| TS-0016 Secure Environment Abstraction |
Defines an API that abstracts from the technical implementation of the secure environment |
| TS-0018 Test Suite Structure and Test Purposes |
Test suite structure and test purposes for evaluating the conformity of oneM2M implementations to the oneM2M specifications. |
| TS-0019 Abstract Test Suite and Implementation eXtra Information for Test |
Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 and oneM2M TS-0004 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467. |
| TS-0020 WebSocket Protocol Binding |
The binding of Mca and Mcc primitives onto the WebSocket binding. |
| TS-0022 Field Device Configuration |
Architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain. |
| TS-0023 SDT based Information Model and Mapping for Vertical Industries |
The oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model. |
| TS-0025 Product Profiles |
Product profiles for oneM2M. |
| TS-0026 3GPP Interworking |
This document specifies interworking between the oneM2M service layer and an underlying 3GPP network, so that relevant 3GPP features defined for Cellular IoT can be used by the oneM2M service layer for the benefit of IoT applications. |
| TS-0030 Ontology based Interworking |
The document specifies generic interworking of the oneM2M System with external systems (e.g. Area Networks containing non-oneM2M devices) that can be described with ontologies that are compliant with oneM2M's Base Ontology |
| TS-0032 MAF and MEF Interface Specification |
Specifies communication between the M2M Authentication Function (MAF) and MAF clients on Mmaf, and between the M2M Enrolment Function (MEF) and MEF clients on Mmef. |
| TS-0033 Interworking Framework |
Guidelines for interworking between external Proximal IoT technologies and the oneM2M system, including representation and exposure of non-oneM2M entities and oneM2M functions. |
| TS-0034 Semantics Support |
Semantic functions for oneM2M functional architecture including basic resource procedures and functional descriptions. |
| TS-0035 OSGi Interworking |
The document defines principles and guidelines on interworking OSGi based devices and gateways to oneM2M system. |
| TS-0040 Modbus Interworking |
The present document specifies the oneM2M and Modbus interworking technologies that enable Modbus devices and oneM2M entities produce/consume services. This includes the interworking architecture model that describes where the Modbus Interworking Proxy Entity (IPE) is hosted and how the IPE is composed with. This document describes Modbus services to oneM2M resource mapping structure and rules, followed by describing detailed interworking procedures. |
| TS-0041 SensorThings Interworking |
SensorThings interworking. |