1.

Internet of Things : IOT is known as the Internet of Things where things are said to be the
communicating devices that can interact with each other using a communication media. Usually
every day some new devices are being integrated which uses IoT devices for its function. These
devices use various sensors and actuators for sending and receiving data over the internet. It is an
ecosystem where the devices share data through a communication media known as the internet or
Iot is an ecosystem of connected physical object that are accessible through internet. Iot means
anything which can be connected to internet and can be controlled or monitored using internet from
smart devices or PC.

2. Machine to Machine : This is commonly known as Machine to machine communication. It is a

concept where two or more than two machines communicate with each other without human
interaction using a wired or wireless mechanism. M2M is an technology that helps the devices to
connect between devices without using internet. M2M communications offer several applications
such as security, tracking and tracing, manufacturing and facility management.

M2M is also named as Machine Type Communication (MTC) in 3GPP ( 3rd Generation Partnership
Project).

M2M is communication could carried over mobile networks, for ex- GSM-GPRS, CDMA EVDO
Networks .

In M2M communication, the role of mobile networks is largely confined to server as a transport
networks.

M2M is only subset of IoT .

Difference between IoT and M2M :

Basis of IoT M2M

Abbreviation Internet of Things Machine to Machine

Devices have objects that are Some degree of intelligence is

Intelligence
responsible for decision making observed in this.

Connection type The connection is via Network and

The connection is a point to point
used using various communication types.

Traditional protocols and

Communication Internet protocols are used such
communication technology
protocol used as HTTP, FTP, and Telnet.
techniques are used

Data is shared between other

Data is shared with only the
Data Sharing applications that are used to improve
communicating parties.
the end-user experience.

Internet connection is required for Devices are not dependent on

Internet
communication the Internet.

Type of It supports point-to-point

It supports cloud communication
Communication communication.
Basis of IoT M2M

Involves the usage of both Hardware Mostly hardware-based

Computer System
and Software. technology

A large number of devices yet scope is

Scope Limited Scope for devices.
large.

Business 2 Business(B2B) and Business

Business Type used Business 2 Business (B2B)
2 Consumer(B2C)

There is no support for Open

Open API support Supports Open API integrations.
APIs

It requires Generic commodity devices. Specialized device solutions.

Communication and device

Centric Information and service centric
centric.

Vertical system solution

Approach used Horizontal enabler approach
approach .

Devices/sensors, connectivity, data Device, area networks, gateway,

Components
processing, user interface Application server.

Smart wearables, Big Data and Cloud, Sensors, Data and Information,
Examples
etc. etc.

Use Case Example:

A Use Case Diagram is a vital tool in system design, it provides a visual representation of how users
interact with a system. It serves as a blueprint for understanding the functional requirements of a
system from a user’s perspective, aiding in the communication between stakeholders and guiding the
development process.

UML Use Case Diagram

A use case diagram is used to represent the dynamic behavior of a system. It encapsulates the
system's functionality by incorporating use cases, actors, and their relationships. It models the tasks,
services, and functions required by a system/subsystem of an application. It depicts the high-level
functionality of a system and also tells how the user handles a system.

Purpose of Use Case Diagrams

The main purpose of a use case diagram is to portray the dynamic aspect of a system. It accumulates
the system's requirement, which includes both internal as well as external influences. It invokes
persons, use cases, and several things that invoke the actors and elements accountable for the
implementation of use case diagrams. It represents how an entity from the external environment can
interact with a part of the system.
Following are the purposes of a use case diagram given below:

1. It gathers the system's needs.

2. It depicts the external view of the system.

3. It recognizes the internal as well as external factors that influence the system.

4. It represents the interaction between the actors.

Example of a Use Case Diagram

A use case diagram depicting the Online Shopping website is given below.

Here the Web Customer actor makes use of any online shopping website to purchase online. The
top-level uses are as follows; View Items, Make Purchase, Checkout, Client Register. The View
Items use case is utilized by the customer who searches and view products. The Client Register use
case allows the customer to register itself with the website for availing gift vouchers, coupons, or
getting a private sale invitation. It is to be noted that the Checkout is an included use case, which is
part of Making Purchase, and it is not available by itself.

The View Items is further extended by several use cases such as; Search Items, Browse Items, View
Recommended Items, Add to Shopping Cart, Add to Wish list. All of these extended use cases provide
some functions to customers, which allows them to search for an item. The View Items is further
extended by several use cases such as; Search Items, Browse Items, View Recommended Items, Add
to Shopping Cart, Add to Wish list. All of these extended use cases provide some functions to
customers, which allows them to search for an item.

Characteristics of the Internet of Things

1. Connectivity

2. Intelligence and Identity

3. Scalability

4. Dynamic and Self-Adapting (Complexity)

5. Architecture

6. Safety

7. Self Configuring

8. Interoperability

9. Embedded Sensors and Actuators

10. Autonomous operation

M2M Value Chain:
A value chain is associated with the creation of value it is an instantiation of exchange by a certain
set of companies within an ecosystem. It is a useful model to explain how markets create value and
how they evolve over time. While a market space composed of only competing value chains will
eventually see the overall market value decrease (as they will compete only on price), in an
ecosystem, the value chains will complement one another. It is therefore critical to be intentional
with the moving from value chains to ecosystems.

What is the IoT value chain?

The IoT value chain explains the building blocks of IoT, how value is created, who they players are,
and how they interact with each other to deliver value.

Looking at the IoT value chain as a pyramid, at the base is all the connected devices: phones, fitness
bands, connected cars, smart homes, and other devices on the consumer side; in industry, you have
things like building sensors, smart cities, and connected factories, for example.

Stepping up a level from the base brings in the network and connectivity—how devices are
connected and communicate. It’s also where service providers collect device and network data and
upload it to the cloud.

Finally, at the top of the value chain, are applications and services that are closest to the eventual
end users—enterprises and consumers.

What is M2M architecture in IoT?

M2M refers to the communication between devices without human intervention. M2M (Machine-to-
Machine) architecture facilitates the transfer of information between components and allows for the
operation of different devices without any difficulty. That's the essence of it, delivering such devices
the ability to communicate with each other, whether it's through wires or wireless transmissions, to
be able to share and take action without having many human interventions. It has established a
protocol of using a specific language so various devices, ranging from a robot to a printer, to an HVAC
system, can exchange data safely and quickly.

M2M vs. IoT comparison table

IoT M2M

Devices have objects for decision- Some degree of intelligence is observed in

Intelligence
making this

Communication
HTTP, FTP, and Telnet Traditional protocol
protocol

Internet An internet connection is required Devices aren’t dependent on the internet

 IoT M2M

Requirements Generic commodity devices Specialized device solution

Business type B2B, B2C B2B

Communication type Cloud communication Point-to-point

Examples Smart cities, Big data, etc. Sensors, data, information, etc.

Building an architecture

Architecture refers to the description of the main conceptual elements, the actual elements of a
target system, how they relate to each other, and principles for the design of the architecture. The
applied architecture is then the blueprint used to develop the actual system solution.

From a reference
architecture to a system solution.

An IoT Architecture Outline

Functional layers and capabilities of an IoT solution

10 most important considerations for IoT solutions:

• IoT Security: IoT introduces a wide range of new security risks and challenges to the IoT
devices themselves, their platforms and operating systems, their communications, and even
the systems to which they're connected.
 • IoT Analytics: IoT business models will exploit the information collected by "things" in many
ways — for example, to understand customer behavior, to deliver services, to improve
products, and to identify and intercept business moments.

• IoT Device (Thing) Management: Long-lived nontrivial "things" will require management and
monitoring. This includes device monitoring, firmware and software updates, diagnostics,
crash analysis and reporting, physical management, and security management.

• Low-Power, Short-Range IoT Networks: Selecting a wireless network for an IoT device
involves balancing many conflicting requirements, such as range, battery life, bandwidth,
density, endpoint cost and operational cost.

• Low-Power, Wide-Area Networks: Traditional cellular networks don't deliver a good

combination of technical features and operational cost for those IoT applications that need
wide-area coverage combined with relatively low bandwidth, good battery life, low hardware
and operating cost, and high connection density.

• IoT Processors: The processors and architectures used by IoT devices define many of their
capabilities, such as whether they are capable of strong security and encryption, power
consumption, whether they are sophisticated enough to support an operating system,
updatable firmware, and embedded device management agents.

• IoT Operating Systems: Traditional operating systems (OSs) such as Windows and iOS were
not designed for IoT applications. They consume too much power, need fast processors, and
in some cases, lack features such as guaranteed real-time response.

• Event Stream Processing: Some IoT applications will generate extremely high data rates that
must be analyzed in real time. Systems creating tens of thousands of events per second are
common, and millions of events per second can occur in some telecom and telemetry
situations.

• IoT Platforms: (1) low-level device control and operations such as communications, device
monitoring and management, security, and firmware updates

(2) IoT data acquisition, transformation and management

(3) IoT application development, including event-driven logic, application programming,

visualization, analytics and adapters to connect to enterprise systems.

• IoT Standards and Ecosystems: Although ecosystems and standards aren't precisely
technologies, most eventually materialize as application programming interfaces (APIs).

Reference Architecture:

Reference Model of IOT: