Database Reference
In-Depth Information
which case is used. If M2M device is not capable of running software with IMS
UA then the M2M gateway needs to do that.
An example shows the advantage of IMS and M2M interworking is when
M2M service re-uses mechanisms from an IMS system to achieve the desired
quality of M2M service, as opposed to the solutions based on best effort connec-
tivity. When to trigger the IMS service is based on some criteria. For a certain
service, it may be enough to stay within the M2M domain, while for some other
service, after the specific criteria is met, the service is routed via IMS network.
The triggering criteria we researched in this paper is for streaming (multimedia)
services. In M2M system there is no support defined for streaming services, thus
IMS is ideal for achieving the complex M2M service where multimedia commu-
nication is needed.
5 Related Work
In [
8
] the authors introduced a new Universal Communications Framework (UCF),
which is a generic middleware solution that intermediates between underly-
ing network infrastructure and various application functions, such as mobile
Machine-to-Machine (M2M) communication. In this case, UFC is between M2M
application and IMS core. Their generic M2M communication platform that is
based on IMS technology is OpenMTC [
7
]. An OpenMTC platform is a pro-
totype implementation of an M2M middleware, aiming to provide a standard-
compliant platform for M2M services. It has been designed to act as a horizontal
convergence layer supporting multiple vertical application domains, which may
be deployed independently, or as a part of a common platform. They designed a
reference use case for smart home application, where the user gets the possibility
to configure the system for various purposes, such as home automation, security
and energy consumption control. In their energy consumption control scenario,
the user will get notifications about the devices that are still switched on, as
soon as the user exits in certain user-defined radius from home, and the user
client application presents a list of supported actions (e.g. switch off one or more
devices).
Our enhancement of previously described scenario is (i) that our approach
does not need generic middleware and (ii) that IMS is triggered only when
certain criteria is met. In this case, IMS resources are optimized since the trac
is routed through IMS network in only some cases, while for the other cases it
stays in M2M domain.
In [
13
] the authors use IMS as a basic network infrastructure for exchang-
ing M2M data. They introduced M2M gateway in the M2M domain and that
gateway is communicating with IMS core. All communication is directed over
IMS core. On the other side (application domain) there is an M2M AS (appli-
cation server) which communicates over IMS core with an M2M gateway. This
approach is similar to the proposed approach in this paper and the difference is
that in the proposed approach herein, the communication goes over M2M and
IMS network, depending whether the QoS is needed or not.
Search WWH ::
Custom Search