Interoperability Between Machine-to-Machine Communication System and IP Multimedia Subsystem - Interoperability and Open-Source Solutions for the Internet of Things - page 102

At first glance, it is hard to make connections between IMS networks and
M2M systems, since M2M systems are not conceived as multimedia commu-
nication systems, but are simply seen as systems where only different numer-
ical sensor data, sensor event information, and remote control commands can
be exchanged. However, the IMS architecture defines several components that
are capable of providing functionalities needed for an M2M type of communi-
cation. Functionalities provided by IMS, like authentication and authorization
mechanisms, charging support, interworking with legacy network, QoS assur-
ance, presence and user data management, already exist in the IMS architecture.
Therefore, these IMS components can be reused for the M2M type of commu-
nication, if the operators have already deployed an IMS network. With reusing
the existing standard IMS components, the operators can reduce their costs of
service deployments, as well as reduce the time to market for new services. On
the other hand, an IMS service can benefit by using data from M2M system and
IMS can customize service based on that data.
Section 2 describes Machine-to-Machine communication standards and sys-
tem architecture. ETSI M2M is used as the base standard in this paper. In
Sect. 3 , IP multimedia subsystem (IMS) is introduced and Sect. 4 explains the
interworking between IMS and M2M. The proposed solution is compared with
the related work in Sect. 5 ; and Sect. 6 explains the use case in the home security
area, that uses interworking between IMS and M2M. Finally, Sect. 7 concludes
the paper.
2 Machine-to-Machine Communication Standards
and System Architecture
The European Telecommunication Standards Institute (ETSI) has a Technical
Committee (TC M2M), which goal was to set the standard of the application
layer that is independent of the underlying communication network. The result
was published as a set of technical reports and standards that specify functional
architecture, and interfaces. The interfaces follow RESTful approach and HTTP
and Constrained Application Protocol (CoAP), standardized by the IETF, were
chosen as an application protocol. ETSI collaborates with other standardization
bodies (e.g. 3GPP, OMA, Broadband Forum, ZigBee Alliance, KNX, Z-Wave)
and is involved in their standardization activities, in order to minimize the num-
ber of standards. The next step was to avoid the creation of competing M2M
standards. Thus, ETSI started a global initiative oneM2M (similar to 3GPP)
to develop one global M2M specification. Currently, oneM2M is working on the
first draft and ETSI M2M is the only available standard. This is the reason that
this paper is based on interoperability between IMS and ETSI M2M.
ETSI M2M architecture is shown in Fig. 1 . ETSI proposes a high-level archi-
tecture of M2M system that consists of a device and gateway domain , and a
network domain [ 11 ].
The device and the gateway domain consist of M2M devices, M2M gate-
ways and an M2M area network. Every M2M device runs its own M2M Device