Studies started in year:
 Projects and Studies


Open API for M2M applications
For further information please contact:

Anastasius Gavras
Programme Manager
Wieblinger Weg 19/4
69123 Heidelberg, Germany

Project Information
What is this Project about?

M2M is expected to evolve in a multi billion market in Europe. Currently, this development is hampered by the monolithic infrastructure of existing M2M platforms. There have been several initiatives to define steps in terms of services and capabilities that will allow migration from existing monolithic M2M infrastructure towards a flexible environment for service development and ubiquitous deployment and operation. This is a necessary prerequisite for standardization of M2M communications to become commercially successful and technically viable and path the way for a future IP-based Internet of Things.

Thus, M2M Service providers are under pressure to deliver easy to use enabling functionality, such as a general purpose messaging function, which is at the same time highly efficient, e.g. through wireless networks outperforming SMS, and offering optional confirmed and transactional message delivery.

Enabler functionality is necessary to access M2M device networks and support mass-market deployment of ubiquitous sensor services. This may form the cross industry alignment of a standardised middleware architecture, e.g. for sensor data aggregation.

What are the main objectives of this Project?

The conceptual basis of that approach is the ontology as defined in the Eurescom study P1856. In the context of this project a set of core services and capabilities, as basic or “atomic” services, have been identified that may offer basic enabler functionalities to configure and manage access and device settings of M2M platforms. Thus, the approach will combine elements of a model driven architecture approach with exact specifications in a technical, portable documentation language, such as XML and SDL. This will help to precisely specify a framework which allows the verification and refinement of the specified data models and procedures.

It is expected that this approach as sketched above will result in an agreed and stable API-specification for M2M platforms. It shall be derivable from that specification how enablers will be accessible via API method calls and Web Services. The identified M2M enabling functions will be submitted to an official standardisation body. The standards contributions shall cover so called Stage 2 (architecture and functional descriptions) and Stage 3 (protocol aspects). The targeted Standards Development Organisations (SDOs) may include ETSI TC M2M and the IETF. The focus on each SDO will depend on the impact made by contributions and the perceived progress of the standardisation process.

One of the focus points of the study would be a messaging service for M2M. The study will specify the messaging service in terms of APIs, message structure and message sequence flow.

Functions should be chosen so that their extension towards application in a M2M network of constrained devices, may be fostered, for example by offering the capability of supporting a publish/subscribe model for messages - similar to what is defined in Instant Messaging/Presence Service Technologies such as XMPP.

The study should pave the way for potential service providers to deploy an application development platform which exposes the standard set of service capability features via the standard APIs on top of a standard stack for communications, power management and sensing, provided by the operators’ M2M platform.

In particular the objectives of this study are:

  • Exact specification of an M2M API that is based on the ontology as identified in Eurescom study P1856, including the message structure and message sequence flow.
  • Detailed definition and specification of a messaging API that extends directly to M2M networks of constrained devices. This addresses the functionality at the border of the IP network and the capillary network.
  • Definition of enabler APIs that sit on top of M2M operators’ platforms and allows communication and may include but not limited to functions such as power management and sensing.
  • Validate the API against the use case of smart metering as defined by the smart metering coordination group (SMCG) at CEN/CENELEC/ETSI in response to the relevant EC directive M/411.
  • Acceptance of the above APIs by Standards Developing Organisations, e.g. in ETSI TC M2M.

Project clients and intended exploitation of results

The main clients of the results will be standards developing organisations, and experts in telecom operators involved in standardisation. For the business development the results will be useful for the definition of a value network in the future M2M market.

Project Results
Deliverable Title  No Issue date
 Description and specification of open M2M API D1 June 2010
Presentation slides D2 June 2010