tta_logo
button
IMToneM2MGSCCJK IT Standard Meeting3GPP
tabs_arrow_button

oneM2M

  • As oneM2M legal entity, TTA is actively developing and implementing oneM2M Technical Specifications and Technical Reports and provides strategic direction to oneM2M since 2012.
  • Here is 2 minutes video of oneM2M to know everything about oneM2M which is available here.
youtube_thumbnail
share

Purpose & Goals

The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. A critical objective of oneM2M is to attract and actively involve organizations from M2M-related business domains such as: telematics and intelligent transportation, healthcare, utilities, industrial automation, smart homes, etc.

oneM2M Specifications

1st release of oneM2M technical specification, issued in 2015, defined a minimum deployable horizontal common service layer.
In 2016, oneM2M delivered Release 2 which enabled interworking capabilities with other IoT proximal network technologies, an enhanced security framework, and services for describing and discovering devices and data based on semantic descriptions.
By the end of 2018, oneM2M issued its Release 3 technical specifications and some of its key features include integration capabilities between oneM2M and 3GPP standards to deliver service quality capabilities at a mobile-industry scale.
Currently, standardization work is underway on Release 4, which is expected to release within 2022, to address edge computing, enhanced 3GPP interworking, vehicular applications, and semantic interoperability among other topics.
M.1743: IMT-Advanced references to Release 11 of LTE-Advanced evolved packet core network

Scope of Standardization

oneM2M’s standardization work covers the following:
  • Use cases and requirements for a common set of Service Layer capabilities;
  • Service Layer aspects with high level and detailed service architecture, in light of an access independent view of end-to-end services;
  • Protocols/APIs/standard objects based on this architecture (open interfaces &protocols);
  • Security and privacy aspects (authentication, encryption, integrity verification);
  • Reachability and discovery of applications;
  • Interoperability, including test and conformance specifications;
  • Collection of data for charging records (to be used for billing and statistical purposes);
  • Identification and naming of devices and applications;
  • Information models and data management (including store and subscribe/notify functionality);
  • Management aspects (including remote management of entities); and
  • Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between:
    • Application and Service Layers;
    • Service Layer and communication functions
Global Activity - TTA Official Website