History and Milestones

OpenMTC_Roadmap_2017 In 2008 first activities where seen in the Telecommunication industry towards what we call today Internet of Things (IoT). Thoese days the folks thought our telecommunication infrastructure could be useful not only for voice calls and sending short message services (SMS). Standardization for Machine Type Communication (MTC) was started by ETSI in 2011. The team at Faunhofer FOKUS, with a long history in NGN platforms, found the idea of horizontal service platform for machine- to- machine communication a valuable approach. A small team started to implement first features of the machine type communication framework specified by ETSI. This lead to the first release of OpenMTC in April 2012. In July 2012 oneM2M was formed by worldwide leading SDOs from the telecommunication industry. The oneM2M specification adopted the horizontal service layer approach defined by ETSI. ETSI is still contributing and disseminating oneM2M. As a logical consequence the team decided to follow the oneM2M specifications in the future, where a transition from ETSI to oneM2M architecture implementation took place between 2013 and 2014. Today most of the oneM2M Rel. 2 core features are implemented in OpenMTC.

Transition to OSS

In the last couple of years hundreds of IoT platforms emerged. The IoT landscape has a huge diversity of existing standards and platforms. We believe that interoperability is the key to success for the Internet of Things. OpenMTC provides ready-to-use, vendor-agnostic IoT middleware to gain hands-on experiences. Thus we stimulate adoption of the worldwide oneM2M standard. Furthermore, the open source community will foster the integration of new features and interoperability among other protocols and technologies.


OpenMTC is licensed under Eclipse Public License v1.0 (EPL1.0)
FAQ about the license are answered here