oneM2M is a global partnership of standards bodies defining a common IoT service layer — registration, discovery, data management, subscription and access control — intended to sit between device protocols and applications so that vertical IoT deployments do not each reinvent it. It is one of the few IoT standards that specifies an API rather than a wire protocol.
oneM2M
oneM2M is a global partnership of standards bodies defining a common IoT service layer — registration, discovery, data management, subscription and access control — meant to sit between device protocols and applications so that every vertical IoT deployment does not reinvent it. It is one of the few IoT standards that specifies an API rather than a wire protocol.
- A service layer, not a transport - It sits above MQTT, CoAP and HTTP rather than competing with them.
- Resource-oriented - A tree of resources with CRUD semantics and subscription, which maps onto HTTP more naturally than most IoT standards do.
- A partnership of partnerships - ETSI, TIA, TTA, ARIB, CCSA, TSDSI and TTC, which gives it global standing and a slow cadence.
- Specifications published openly - Technical specifications are downloadable from the site.
oneM2M is the IoT stack’s attempt to standardise the layer where fragmentation actually hurts. Device protocols are already plural and that is survivable; what is not survivable is every platform inventing its own registration and subscription semantics. Whether it succeeded is a fair question — most commercial IoT platforms shipped their own service layer anyway — but it is the right thing to have standardised, and it is API-shaped in a way LoRaWAN and its peers are not.
Industry: IoT
