8
ITU-T Focus Group on M2M service layer: M2M service layer: APIs and protocols overview
tractors, medical devices, vending machines, or storage tanks, and translating it into meaningful
information for quick decisions, automated actions, and strategic analytics. The primary driver for
M2M solutions is now enabling new services, rather than just improving operational efficiency/cost
saving.
A platform is considered to be a group of technologies that are used as a base upon which
applications, processes or other technologies are developed/delivered.
Creating a platform is usually a complex and delicate task, and needs to serve multiple purposes,
but the primary purpose is to support and simplify the work of those who will be using/consuming
this platform. M2M platforms have transformed the M2M market by making device data more
accessible to application developers, and also by offering well-defined software interfaces and
making APIs available so that application developers can readily integrate information sources and
control parameters into their applications.
5.3 Types of M2M Platforms
Over the past decade, the M2M platform space has developed rapidly, and now includes the
following broad platform functions:
- Connectivity Support: it encompasses all of the most fundamental tasks that must be
undertaken to configure and support a machine-to-machine connection. In a mobile
environment, such tasks include connection provisioning, usage monitoring, and some level of
support for fault resolution.
- Service Enablement: it has extensive capabilities in terms of solution support, reporting and
provision of a software environment and APIs to facilitate solution development. Together,
Connectivity Support, and Service Enablement functions represent the ‘horizontal’ elements of
the M2M platforms industry.
- Device Management: it has typically been aligned to single device manufacturers and
potentially supports devices of multiple types and vendors connected through multiple
networks. Device management platforms essentially exist to facilitate sales of devices (and
device-centric solutions) where those devices typically require some form of non-standard
systems support (reporting, management, etc.).
- Application Support: it is characterized by the provision of tailored solutions, encompassing
connected devices potentially of multiple types, connected with multiple technologies, and
connected to the networks of multiple CSPs (Communication Service Providers).
- Solution Provider: it should be regarded typically as an enabler for a large system development
initiative, rather than as a standalone offering. These M2M platforms are generally used by
systems integrators to support turnkey and client-specific solutions.
While many of these platform type implementations have some overlapping functionality (further
complicating the M2M delivery ecosystem while simultaneously attempting to streamline it), the
end goal is similar, i.e. mainly to make sure that the data collected from all of these machines and
sensors are actually used to improve the business of the company investing in the collection.
5.4 Reference points of the M2M service layer in the component based M2M reference
model
The purpose of this document is to provide guidelines about APIs and protocols handled by M2M
service layer. It is necessary to make clear the reference points used by APIs and protocols. It is
possible to clarify the reference points by referring to figure 4 of [ITU-T FG M2M D2.1],
describing the M2M service layer reference points.