oneM2M Logo transparent 196x130

Standards for M2M and the Internet of Things

The oneM2M Executive Viewpoint Series features business insights from senior executives in companies that are commercializing products and services based on oneM2M.

“The TP#39 meeting focused on new, Release 4 use case requirements, device data models, and feature enhancements as well as market adoption activities”

March 2019 - Dale Seed, Convida Wireless

oneM2M Technical Plenary (TPs) meetings are regularly scheduled events over the calendar year. Through this forum, oneM2M members have an opportunity to meet face-to-face to define the oneM2M technology roadmap, discuss and reach consensus on technical contributions towards the standard and test their oneM2M-based solutions with one another.
In this Executive Interview, Dale Seed, of Convida Wireless, shares his observations from the TP#39 event.

Read more ...

"During oneM2M's TP#38, we started work on important domains - industrial, vehicular and fog/edge architectures - in addition to laying the groundwork for semantic interoperability and tools to help user adoption"

January 2019 - oneM2M Technical Plenaries (TPs) are regular events over the calendar year where members have an opportunity to review progress on different work items and agree decisions about the oneM2M standard. This Executive Interview focuses on developments at TP#38 which was hosted by ARIB and TTC in Kanazawa, Japan. Dale Seed (Convida Wireless) shares his observations from the event.

Read more ...

Get oneM2M news

Be among the first to find out what oneM2M is doing. Join the oneM2M news e-mail list to receive news from oneM2M as soon as it's published! 


Yes! I want to receive news from oneM2M

Subscribe to oneM2M News Please enter your name and email address, then click on submit.
Alternatively, you can send an email from your preferred email application with a blank subject to with subscribe oneM2M_News in the message body.

Subscribe to oneM2M News

Your Name(*)
Please let us know your name.

Your Email(*)
Please let us know your email address.