oneM2M

oneM2M is a global partnership project created in 2012 by eight telecommunications and information-and-communications-technology standards development organizations: ARIB and TTC from Japan, ATIS and TIA from the United States, CCSA from China, ETSI from Europe, TSDSI from India, and TTA from South Korea. Its purpose is to develop a common technical foundation for machine-to-machine communication and Internet of Things services, reducing fragmentation among devices, networks, platforms, and applications. Rather than defining a single connectivity technology, oneM2M specifies a horizontal IoT service layer that can operate across different access networks and deployment environments. The approach separates application logic from common service functions and from the underlying communications network. This allows developers to build applications without needing to redesign them for each particular transport technology, network operator, or device ecosystem. The oneM2M architecture is organized around three broad layers. Application Entities provide application-specific logic on devices, gateways, or infrastructure platforms. Common Services Entities provide reusable functions such as registration, discovery, device management, authentication, authorization, security credential handling, data storage, buffering, synchronization, group management, and communication scheduling. The network layer supplies connectivity while remaining largely abstracted from the application developer. Standardized APIs connect applications with common service functions, enabling systems from different vendors to interoperate. The specifications are intended for a wide range of applications, including smart cities, smart grids, connected vehicles, home automation, public safety, healthcare, industrial systems, and transport management. The partnership describes its standards as open, with a transparent development process and publicly accessible deliverables. The work has also been recognized through transposition into the International Telecommunication Union Telecommunication Standardization Sector's Y.4500-series recommendations. oneM2M is not a conventional commercial company and does not principally sell hardware, software subscriptions, or consumer products. Its outputs are technical specifications, technical reports, implementation guidance, and certification or conformance-related resources developed through participating standards bodies and members. More than 200 organizations have participated or been represented in the partnership, including major network operators, technology companies, manufacturers, research organizations, and industry associations. Participation is generally organized through one of the partner standards development organizations. The partnership's influence is expressed through implementations and deployments rather than through direct retail distribution. Open-source and commercial platforms have used the oneM2M architecture for servers, gateways, devices, data brokers, and application development. Regional activity has been particularly visible in South Korea, where national IoT planning has referenced oneM2M and Busan has pursued an open platform approach for smart-city use cases. European activities have included enterprise, smart-city, and intelligent-transport trials. Overall, oneM2M positions itself as a vendor-neutral interoperability framework intended to make IoT systems more portable, scalable, and capable of using multiple networks and technologies.

oneM2M was formed in July 2012 by eight established standards development organizations representing major telecommunications and technology regions. The founding partners were ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, and TTC. The initiative emerged during a period when IoT and machine-to-machine deployments were expanding rapidly but were often built around incompatible vertical platforms, proprietary interfaces, and network-specific technologies. Its central objective was to create a shared service-layer framework that could be used across sectors and connectivity environments. The partnership was also supported by additional industry forums, consortia, and standards organizations, including the Broadband Forum, CEN, CENELEC, GlobalPlatform, the Next Generation M2M Consortium, and the Open Mobile Alliance. These relationships helped bring application and sector requirements into the technical work. Legal entities interested in developing or implementing oneM2M specifications could participate through membership in one of the partner organizations. Participating members may contribute to technical plenary meetings and working groups, where they receive voting rights, while they may attend steering activities without voting rights. The first major specification release arrived in February 2015. Release 1 established the basic horizontal architecture and a general-purpose service layer for IoT platform operators and service providers. It defined the separation between application entities, common service entities, and infrastructure or network environments, along with standardized interfaces for common functions. This architecture was designed to prevent every IoT application from having to implement its own versions of registration, discovery, device management, security, and data-handling functions. Release 2, issued in August 2016, expanded the framework with an interworking approach intended to let platforms accommodate a wider range of devices and service systems. It also strengthened end-to-end security capabilities. This release addressed a practical problem in IoT deployment: operators and application providers often needed to connect existing technologies and devices without abandoning their established systems. Cooperation with the ITU-T became an important part of the standard's international reach. In 2018, reporting from the South Korean standards community described work to bridge standardization gaps by transposing oneM2M specifications into ITU-T recommendations. The resulting ITU-T Y.4500 series gave the work a further international standards reference beyond the partnership itself. Release 3 was published in December 2018. It introduced additional value-added services designed to complement IoT capabilities associated with 3GPP networks. The release addressed issues relevant to large mobile-operator deployments, including network congestion and security, and sought to provide a path toward more scalable IoT services. Alongside formal specifications, oneM2M became associated with a growing implementation ecosystem. Projects such as Eclipse OM2M, OCEAN, ACME, tinyIoT, OS-IoT, OpenMTC, the OpenDaylight IoT Data Broker work, OASIS SI, and oneM2MTester explored or implemented portions of the architecture. These projects supported experimentation, education, interoperability testing, and deployment across servers, gateways, devices, and application platforms. The partnership's use cases have included smart-city platforms, smart grids, connected cars, home automation, public safety, healthcare, and intelligent transport. South Korea became one of the most prominent regional markets for oneM2M-oriented activity, including references in national IoT planning and an open-platform initiative in Busan. In the United Kingdom, a public-private intelligent-transport trial used a oneM2M-based platform to support journey planning and transport-event and incident-management applications across several counties. The organization's continuing role is that of a collaborative standards project rather than a conventional corporate brand: its influence depends on adoption by standards bodies, technology vendors, operators, developers, and public-sector programs.

• 2018

  Release 3 published

  [1]OneM2Men.wikipedia.org

  Release 3 added services complementing 3GPP-related IoT capabilities and addressed scalability, congestion, and security concerns in mobile-network deployments.

• 2018

  ITU-T transposition expanded international recognition

  [1]OneM2Men.wikipedia.org

  oneM2M work was transposed into the ITU-T Y.4500 series, helping connect the partnership's specifications with international telecommunications recommendations.

• 2016

  Release 2 published

  [1]OneM2Men.wikipedia.org

  Release 2 added an interworking framework for broader device and platform compatibility and enhanced end-to-end security capabilities.

• 2015

  Release 1 published

  [1]OneM2Men.wikipedia.org

  The first major release defined a general-purpose horizontal IoT architecture and service layer for platform operators and service providers.

• 2012

  oneM2M partnership established

  [1]OneM2Men.wikipedia.org

  Eight standards development organizations from Japan, the United States, China, Europe, India, and South Korea formed oneM2M to develop a common technical basis for interoperable M2M and IoT systems.

A vendor-neutral international standards partnership for interoperable IoT service-layer architecture, APIs, security, and device-to-application integration.

• IoT standard · 2015

  oneM2M Release 1

  The first major oneM2M specification release established the partnership's core horizontal architecture. It defined a vendor-independent service layer between IoT applications and communications networks, allowing common capabilities such as registration, discovery, data handling, and device management to be reused across application domains. Release 1 was intended to give platform operators and service providers a general foundation for deploying interoperable M2M and IoT systems rather than separate, proprietary stacks for each vertical.

• IoT standard · 2016

  oneM2M Release 2

  Release 2 extended the original architecture with an interworking framework designed to connect a broader range of devices and service platforms. It also enhanced security, including capabilities relevant to end-to-end protection. The release addressed the need to integrate existing IoT technologies while retaining a common service-layer model and standardized interfaces.

• IoT standard · 2018

  oneM2M Release 3

  Release 3 added value-oriented services intended to complement IoT functions associated with 3GPP mobile-network standards. Its work addressed deployment concerns such as congestion management and security in operator environments, supporting the goal of scaling oneM2M-based services across large connected-device populations.

• Software architecture and API standard · 2015

  oneM2M Service Layer and APIs

  The service-layer architecture provides common functions between applications and network connectivity. Its APIs expose functions including identification, authentication, authorization, encryption support, provisioning, device management, data aggregation, buffering, synchronization, group management, and resource discovery. By standardizing these interfaces, oneM2M seeks to let applications remain less dependent on a particular device vendor, connectivity method, or IoT platform.

• Industry interoperability and open-standard adoption

  Global

  oneM2M promotes participation by technology companies, operators, research organizations, application forums, and other standards groups so that its specifications reflect requirements from multiple IoT sectors. Its open development and publicly available deliverables support experimentation and implementation across smart-city, industrial, transport, healthcare, and consumer environments.

  Outcome. The partnership developed a broad member and implementation ecosystem and achieved international recognition through ITU-T transposition.

  Source
• South Korean smart-city and national IoT adoption

  South Korea

  oneM2M was referenced in South Korea's national IoT planning, while Busan pursued an open platform based on the standard to support a smart-city ecosystem involving industry and universities.

  Outcome. South Korea became one of the leading regional markets for oneM2M-oriented solutions and demonstrations.

  Source
• oneTRANSPORT intelligent-transport trial

  United Kingdom

  A public-private partnership used an InterDigital oneM2M-based platform in an Innovate UK-supported trial covering Buckinghamshire, Hertfordshire, Northamptonshire, and Oxfordshire. The project explored journey planning and transport-event and incident-management applications.

  Outcome. The trial demonstrated a multi-organization use case for standards-based transport data and service integration.

  Source

• 2018

  Align oneM2M specifications with international telecommunications standardsStrategy

  Background

  The partnership sought to reduce gaps between industry-developed IoT specifications and formal international telecommunications standardization.

  Action taken

  oneM2M specifications were transposed into the ITU-T Y.4500 series, following cooperation involving the partnership and participating standards organizations.

  Aftermath

  The transposition gave oneM2M architecture and service-layer work an additional international standards reference.

  Source

• 2012

  Adopt a horizontal, vendor-neutral IoT service layerStrategy

  Background

  IoT and machine-to-machine systems were developing through fragmented vertical platforms and network-specific implementations.

  Action taken

  The founding standards organizations created a shared architecture separating applications, common service functions, and network connectivity, with standardized APIs between them.

  Aftermath

  The model became the basis for subsequent oneM2M releases and implementations across multiple IoT sectors.

  Source

• Unconfirmed

  VNPT IoT Platform receives oneM2M certification[3]VNPT IoT Platform获得oneM2M认证vietnamnet.vn

  Reported: 2020-08-10

  VNPT received a oneM2M certificate for its VNPT IoT Platform. The report also says the platform would undergo further review for a GCF certificate.

1. 1OneM2Men.wikipedia.org
2. 2oneM2M official websiteonem2m.org
3. 3VNPT IoT Platform获得oneM2M认证vietnamnet.vn