Average car drivers are not engineers involved in gear box development or programing of the Engine Control Unit (ECU) , yet they are all able to drive cars very easily. One of the main reasons are well known and globally accepted interactions between the driver and the car.
You might not think of driving as a set of open interfaces for interoperability, but in fact brake and acceleration pedals or the steering wheel in a car are great examples of globally standardized interfaces for interoperability. Regardless of the car type or where in the world it is being driven, drivers can rely on the same set of driving principles and interactions with the car.
Drivers can rely on the consistent car response to a specific driver action, e.g. once the steering wheel is turned right, the car turns right or once the brake pedal is engaged, the car reduces its speed. How is all this related to IoT? Let us explain.
In various IoT related news, there are often bold headlines like, “IoT is lacking standards” or “IoT cannot be standardized because the use cases are too diverse.” Although, it is true that there is some level of uniqueness and customization for each use cases (like the color or shape of the steering wheel may be unique), there are many aspect that all IoT use cases have in common (like steering the wheel itself). Typical aspects, common to most IoT solutions are:
Controlling the communication behavior of the device is particularly important for achieving the long battery life of often small and constrained IoT devices. For the cellular network operator, it is equally important to prevent any bottlenecks to the network that can be generated by the millions of customer devices potentially transmitting or receiving data at the same time.
Today, many of above listed functions are going to be implemented with varying degrees of success and quality, because they are not relying on one consistent standard. For the IoT customer then, it is challenging to find the right integration partners having the required experience in the underlying connectivity and IoT technologies that can make IoT solutions consistently successful.
This is exactly where oneM2M standard comes in. oneM2M standard has been created through a global partnership between 8 regional Telecommunication Standardization Development Organizations* and more than 200 member companies (www.oneM2M.org). oneM2M standard defines IoT interfaces that developers can use to create IoT applications that are interoperable and consistent like steering the wheel.
Via these interfaces, developers can easily read device information or sensor data and invoke other functions listed above. This becomes similar to the application programmers creating Android or iOS applications for modern smartphones. IoT application development becomes more efficient and applications more portable. Portability also enables interoperability between different providers and avoids vendor lock-ins for the customer.
While oneM2M standard usage is already quite common in Asia (Japan and South-Korea), it is just getting started in Western countries. For example, T-Mobile Austria, a Deutsche Telekom affiliate, is spearheading research and development of oneM2M standard-based technologies while leveraging its NB-IoT connectivity. This is enabled through the close cooperation with global industry players:
Through this cooperation, feasibility of oneM2M technology for a constrained device, operating without a Micro Controller Unit (MCU) directly on the cellular modem has been proven.
The oneM2M device software:
The device uses the oneM2M mca interface to:
Experience DTAG / T-Mobile technology leadership in IoT at the MWC 2019 Chordant/InterDigital, Booth Hall 7, 7C61 & DTAG Booth Hall 3, 3M31
Please contact Andreas Neubacher email@example.com for more information about oneM2M.