UNIT -2
MACHINE TO MACHINE COMMUNICATION
M2M system architecture OR M2M communication
Machine-to-Machine (M2M) refers to networking of machines (or
devices) for the purpose of remote monitoring and control and data exchange.
Figure shows the end-to- end architecture for M2M systems comprising of
M2M area networks, communication network and application domain.
Figure: M2M System Architecture
An M2M area network comprises of machines (or M2M nodes) which
have embedded hardware modules for sensing, actuation and communication.
Various communication protocols can be used for M2M local area networks
such as ZigBee, Bluetooth, Wireless M-Bus, Power Line Communication
(PLC), 6LOWPAN, IEEE 802.15.4, etc. These communication protocols
provide connectivity between M2M nodes within an M2M area network.
The communication network provides connectivity to remote M2M area
networks. The communication network can use either wired or wireless
networks (IP-based). While the M2M area networks use either proprietary or
non-IP based communication protocols, the communication network uses IP-
based networks.
Since non-IP based protocols are used within M2M area networks, the
M2M nodes within one network cannot communicate with nodes in an external
network. To enable the communication between remote M2M area networks,
M2M gateways are used.
Figure shows a block diagram of an M2M gateway. The communication between the
M2M nodes and the M2M gateway is based on the communication protocols which
are native to the M2M area network.
FIG: BLOCK DIAGRAM M2M GATEWAY
M2M gateway performs protocol translations to enable IP-connectivity
for M2M area networks.
M2M gateway acts as a proxy performing translations from/to
native protocols to/from Internet Protocol (IP).
With an M2M gateway, each node in an M2M area network appears as
a virtualized node for external M2M area networks.
The M2M data is gathered into point solutions such as enterprise
applications, service management applications, or remote monitoring
applications.
M2M has various application domains such as smart metering, home
automation, industrial automation, smart grids, etc. M2M solution designs
(such as data collection and storage architectures and applications) are
specific to the M2M application domain.
Write down the differences between IoT and M2M
Although both IoT and M2M involves networking of machines, they differ
in terms of underlying Technologies, System Architecture, and type of
applications. The differences between IoT and M2M are described as follows:
Communication Protocols:
M2M and IoT can differ in how the communication between the machines or
devices happens.
M2M uses either proprietary or non-IP based communication protocols for
communication within the M2M area networks. Commonly uses M2M
protocols include ZigBee, Bluetooth, 6LOWPAN, IEEE 802.154. Z-Wave, etc.
The focus of communication in M2M is usually on the protocols below the
network layer. The focus of communication in loT is usually on the protocols
above the network layer such
as HTTP, COAP, WebSockets, MQTT, XMIP, DDS, and AMQP. etc., as
shown in Figure.
Figure: Difference of M2M and IoT Protocols
Machines in M2M vs Things in loT:
The "Things" in loT refers to physical objects that have unique identifiers
and can sense and communicate with their external environment (and user
applications) or their internal physical states.
Things have software components for accessing, processing, and storing
sensor information, or controlling actuators connected.
IoT systems can have heterogeneous things (e.g., a home automation IoT
system can include IoT devices of various types, such as fire alarms, door
alarms, lighting control devices, etc.) M2M systems, in contrast to loT.
Typically have homogeneous machine types within an
M2M area network.
Hardware vs Software Emphasis:
While the emphasis of M2M is more on hardware with embedded modules.
The emphasis of loT is more on software, loT devices run specialized
software for sensor data collection, data analysis and interfacing with the
cloud through IP-based communication.
Data Collection & Analysis:
M2M data is collected in point solutions and often in on-premises storage
infrastructure.
In contrast to M2M, the data in loT is collected in the cloud (can be public,
private or hybrid cloud).
The analytics component analyses the data and stores the results in the
cloud database. The loT data and analysis results are visualized with
the cloud-based applications.
Applications:
M2M data is collected in point solutions and can be accessed by on-
premises applications such as diagnosis applications, service management
applications, and on premises enterprise applications. IoT data is collected
in the cloud and can be accessed by cloud applications.
Q. Write down the differences between IoT and M2M ?
What is Interoperability?
Interoperability is a characteristic of a product or system, whose interfaces are
completely understood, to work with other products or systems, present or future,
in either implementation or access, without any restrictions.
Communicate meaningfully
Exchange data or services
Handle the heterogeneity
Interoperability as a general term
Iot uses different devices from different vendors
Why interoperability is important in context of IOT?
To fulfill the iot objectives
Physical objects can interact with any other physical objects and can share
their information
Any device can communicate with other devices anytime from anywhere
Machine to machine communication (M2M), Device to Device communication
(D2D), Device to Machine communication (D2M)
Seamless device integration with IoT network
Why interoperability is required?
Heterogeneity
Different wireless communication protocols such as ZigBee (IEEE 802.15.4),
Bluetooth (IEEE 802.15.1), GPRS, 6LowPAN and Wi-Fi (IEEE 802.11)
Different wired communication protocols like ETHERNET (IEEE 802.3) and
Higher Layer LAN Protocols (IEEE 802.1)
Different programming languages used in computing systems and websites such as
JavaScript, JAVA, C, C++, PHP and Python
Different hardware platforms such as Crossbow, NI etc.,
Different operating systems
As an example for sensor node: TinyOS, SOS, Mantis OS, RETOS and mostly
vendor specific OS
As an example for Personal computer: WINDOWS, Mac, Unix Different
databases: DB2, MySQL, ORACLE Sybase etc.,
Different data
representation
Different control models
Syntactic or semantic interpretations
Different types of interoperability
• User interoperability
• Interoperability problem between a user and a device
• Device interoperability
• Interoperability problem between two different devices
1. User interoperability:
User Interoperability The following problems need to be solved
Device identification and categorization for discovery
Syntactic interoperability for device interaction
Semantic interoperability for device interaction
Example of Device and User Interoperability ,
Using IoT, both A and B provide a real-time security service
A is placed at Delhi, India, while B is placed at Tokyo, Japan
A, B, U use Hindi, Japanese, and English language, respectively
User U wants real-time service of CCTV camera from the device A and B
Device identification and categorization for discovery
There are different solutions for generating unique address
Electronic Product Codes (EPC)
Universal Product Code (UPC)
Uniform Resource Identifier (URI)
IP Addresses ( IPv6)
Syntactic Interoperability for Device Interaction
The interoperability between devices and device user in term of message
formats
The message format from a device to a user is understandable for the user’s
computer
On the other hand, the message format from the user to the device is executable
by the device
Some popular approaches are
Service-oriented Computing (SOC)-based architecture
Web services
RESTful web services
Open standard protocols such as IEEE 802.15.4, IEEE 802.15.1, and
WirelessHART*
Closed protocols such as Z-Wave
Middleware technology
Software middleware bridge
Dynamically map physical devices with different domains
Based on the map, the devices can be discovered and controlled, remotely
Cross-context syntactic interoperability
Collaborative concept exchange
Using XML syntax
Semantic Interoperability for Device Interaction
The interoperability between devices and device user in term of message’s
meaning.
The device can understand the meaning of user’s instruction that is sent from
the user to the device.
Similarly, the user can understand the meaning of device’s response sent from
the device.
2. Device Interoperability
Solution approach for device interoperability
Universal Middleware Bridge (UMB)
Solves seamless interoperability problems caused by the heterogeneity of
several kinds of home network middleware.
UMB creates virtual maps among the physical devices of all middleware home
networks.
It also Creates a compatibility among these middleware home networks
Middleware Bridge UMB consists
UMB Core (UMB-C) UMB Adaptor (UMB-A)
Introduction to Arduino Programming
What is Arduino?
Arduino is an open source electronic platform based on easy to use hardware
and software.
