Imagine this: your telephone rings, but the caller speaks a language you don’t understand. However clear the connection is, however good the communication skills of both parties are, however often what is said is repeated, or however important the information to be communicated is: there will not be any common understanding.
And it is exactly the same with machines. They also need a “common language” to pass on data in a way that is understandable and useful. The complex connections in the Internet of Things (IoT) are especially affected by this. If a parking sensor, a water meter, a fridge, a car or a production machine want to communicate with a cloud, engineers need to have taught them the same language beforehand.
Before now, major implementation efforts were necessary for every IoT client, in order to convert the data generated by objects or machines in such a way that it could be used logically by IoT cloud services. In the future, this will be more efficient: a standard like oneM2M creates a level which can be communicated with over a wide array of sectors – whether it’s the smart home, healthcare, automotive or other industries.
The standard for all sectors
oneM2M was developed by the organization of the same name, which wanted to create a uniform standard specifically for the M2M and IoT market. Supported by 230 members at present – among them Deutsche Telekom as well as such notable partners as Cisco, ATIS, TTC and ETSI – the declared goal is to establish a single, horizontal platform for exchanging and sharing data among all possible applications. As a software, oneM2M works like an operating system to ensure a consistent framework within which various technologies can work successfully together. It will be possible to integrate this service layer into the widest range of hardware and software designs, simply as it is. oneM2M consists of three entities:
• Application Entity (AE), which communicates with the connected application
• Common Service Entity (CSE), which provides the usual IoT functions for the applications
• Network Service Entity (NSE), which controls the applications’ access to the network
Like the releases of standardization body 3rd Generation Partnership Project (3GPP), oneM2M boasts a broad spectrum of specifications, for instance for architecture, tests and security measures like “Security by Design”.