The OpenMTC platform is a prototype implementation of an M2M
middleware aiming to provide a standard-compliant platform for
Our customers and research partners use the OpenMTC platform
to interconnect various sensors and actuators from different
vertical domains with a cloud-enabled, open platform, which
aggregates collected data, forwards data to the application and
mediates instructions to end devices for event-based control.
- International Standards
- Optimizing Network
- M2M and H2M Convergence
International Standards Alignment
OpenMTC is aligned with international M2M standards such as ETSI
M2M, oneM2M, OMA LWM2M and 3GPP. Standard compliant platforms
foster the integration and the interworking process of different
products in either the field domain or the infrastructure
domain. Thanks to the support of the Diameter protocol, the
OpenMTC leverages the functionalities supported by the deployed
network infrastructure such as authentication, authorization,
device connectivity status, and QoS policy management.
For optimizing the power consumption of end-devices, OpenMTC can
be integrated with 3GPP core elements to retrieve the
connectivity status without maintaining a keep-alive channel.
Interfacing with 3GPP core elements of the Evolved Packet Core
(EPC) allows triggering the core network additionally for
application-specific QoS requirements or network-assisted
The OpenMTC gateway can be deployed in various kinds of hardware
including constrained hardware such as Arduino and Raspberry Pi.
It can be also deployed in Linux-compatible or
Android-compatible devices. The backend platform can be deployed
in a cloud-based infrastructure and thus can scale horizontally
according to your needs.
Thanks to the Open eXtensible Service Platform (OpenXSP), you
can develop M2M (Machine-to-Machine) and H2H (Human-to-Human)
services over a common horizontal layer. The OpenXSP is polyglot
and allows service development and platform extensions in Java,
OpenMTC supports different transport protocols such as HTTP,
CoAP and Websocket. This will allow supporting different type of
domain-specific applications with various interaction models,
such as push/pull or subscribe/notification model. It allows the
applications and the end devices to interact in real-time over
the Web or any other IP-based network even via multicast with
very low overhead in communications.
The OpenMTC solution has been designed to act as a horizontal
convergence layer in terms of a Machine-to-Machine (M2M)
middleware for machine type communication supporting
multiple vertical domains.
Those domains are usually the classic M2M verticals (market
segments) such as transport and logistics, utilities, automotive,
eHealth, etc. which can be deployed independently or as part of a
OpenMTC mainly consist of two common M2M capability layers, a
front-end in the field domain and a back-end, cloud-based platform
in the infrastructure domain. Those layers follow the oneM2M
standards in oneM2M-TS-0001 and the ETSI Technical Committee M2M
in TS 102.921 and TS 102.690.
The OpenMTC gateway runs on different hardware platforms like
Android, Arduino and Raspberry Pi and supports different protocols
and various local access technologies like ZigBee, FS20 and
Bluetooth. Both front-end and back-end nodes support common
service capabilities that can be used by the applications through
open interfaces. The front-end and back-end nodes are able to use
different transport protocols, such as HTTP, CoAP and Websockets.
The OpenMTC platform is an R&D implementation of an M2M
middleware aiming to provide a standard-compliant platform for M2M
- Smart Building
- Industry 4.0
- Tracking & Tracing
- Smart Grid