Unit-2

M2M
• M2M:-Machine-to-machine communication, or M2M, is exactly : two
machines “communicating,” or exchanging data, without human
interfacing or interaction:
•
• Machine to Machine refers to the technologies that allows wired /
wireless system to communicate with the devices of same ability.

• M2M uses a device (sensor, meter, etc.) to capture an ‘event’

(temperature, inventory level, etc.), which is relayed through a
network (wireless, wired or hybrid) to an application (software
program), that translates the captured event into meaningful
information (e.g., items need to be restocked).
Radio Technologies for M2M
 • M2M Architecture
• M2M Device Domain:
• M2M Device:
A device capable of replying to request for data contained within that device or
capable of transmitting data contained within those devices autonomously
• M2M Area Network:
Provide connectivity between M2M Devices and M2M Gateways
• M2M Gateway:
Use M2M capabilities to ensure M2M Devices inter-working and interconnection to
the communication network

• Network Domain:
• M2M Communication Networks:
Communications between the M2M Gateway(s) and M2M application.
E.g. Access Networks ( LTE, WiMAX, and WLAN) and Internet
• Applications Domain:
• M2M Applications:
Contains the middleware layer where data goes through various application
services and is used by the specific business-processing engines
M2M Architecture
 M2M Vs IoT
• M2M systems use point-to-point communications between machines, sensors and
hardware over cellular or wired networks, while IoT systems rely on IP-based
networks to send data collected from IoT-connected devices to gateways, the cloud
or middleware platforms.

A real life example of this dissimilarity could be found in telemedicine. Let

us imagine a solution that connects a sensor monitoring the heart rate of a
patient to an external application which lets the doctor know the patient
needs attention. Such kinds of solutions could easily be provided by the
M2M technology.

On the other hand, if we take a sensor and integrate it with an interactive

pillbox that would advise the patient to take the medicine and, moreover,
would be able to send alerts to their family members’ smartphones that the
medicine has not been taken from the pillbox, it would definitely involve an
IoT approach.
• M2M = > Embedded Technology + Network Technology
Let us take a practical example.
• - You have an "Air conditioning unit" in your home. For switching ‘OFF’ and ‘ON’, you use
remote control. Here both devices (or machines), AC and Remote have an embedded system
inside it that is communication over Low range RF frequency. Since both machines are
communicating without using Internet, that’s why it is Machine to Machine (M2M)
communication.

• For IoT usecase, Internet will also be involved, :

• - Now assume your AC is a “Smart AC” that is connected to the internet (This is a "Thing"
connected to the internet). Now, imagine it's a hot summer day and you have left for home
from your work. You would like your home to be cool enough by the time you enter it. So,
When you leave from your office, you can remotely switch ON the air conditioning unit of
your home using your mobile (another "Thing" connected to the internet). This very simple
application using Internet but involves Human Intervention.

• A further extension to this concept with “Autonomous Mode” (without Human

Intervention) is :
• - Your mobile will command your home A/C that you are leaving the office (it can detect your
GPS co-ordinates and decide you are on the move) and depending on the temperature, the
A/C will be switched ‘ON’ by your mobile itself, and the mobile will simply notify you that
the A/C is ON.
 Difference between M2M and IOT
• Communication Protocols:
• M2M and IoT can differ in how the communication between the machines
or devices happens.

• M2M uses non-IP based communication protocols for communication

within the M2M area networks which includes ZigBee,
Bluetooth,6LoWAN, IEEE 802.15.4 etc.

• IoT protocols include HTTP, CoAP, WebSocket, MQTT, XMPP, DDS,

AMQP etc.

• M2M is usually on the protocols below the network layer.

• IOT is usually on the protocols above the network layer

Home M2M Architecture
 Value Chains
• Global value chains A value chain describes the full range of activities that firms
and workers perform to bring a product from its origin to end use and beyond,
including design, production, marketing, distribution, and support to the final
customer

• It is a useful model to explain how markets create value and how they evolve over
time.

• M2M value chains : A value chain is the full range of activities – including design,
production, marketing and distribution – businesses conduct to bring a product or
service from conception to delivery.
• M2M value chains solutions are generally internal to a company’s
business processes and do not included extensive interactions with other
parties, it includes :

• ✔ Inputs ✔ Production/Manufacture ✔ Processing ✔Packaging ✔

Distribution/Marketing
M2M value chains

•M2M value chains are internal to one company and cover one
solution.

• Reasons for using M2M vary from project to project and company to
company.

• It can include things such as cost reductions through streamlined

business processes, product quality improvements, and increased
health and safety protection for employees.

• Input and output of the value chains as follows:

• Inputs
• Inputs are the base raw ingredients that are turned into a product. Examples
could be cocoa beans for the manufacture of chocolate or data from an
M2M device that will be turned into a piece of information.

• Production/Manufacture: Production/Manufacture refers to the process

that the raw inputs are put through to become part of a value chain. For
example, cocoa beans may be dried and separated before being transported
to overseas markets. Data from an M2M solution, meanwhile, needs to be
verified and tagged for provenance.

• Processing
• Processing refers to the process whereby a product is prepared for sale. For
example, cocoa beans may now be made into cocoa powder, ready for use
in chocolate bars. For an M2M solution, this refers to the aggregation of
multiple data sources to create an information component something that is
ready to be combined with other data sets to make it useful for corporate
decision-making.
• Packaging
• Packaging refers to the process whereby a product can be branded as would be
recognizable to end-user consumers. For M2M solutions, the data will have to be
combined with other information from internal corporate databases, for example,
to see whether the data received requires any action.
• This data would be recognizable to the end-users that need to use the information,
either in the form of visualizations or an Excel spreadsheet.

• Distribution/Marketing
• This process refers to the channels to market for products. An M2M solution will
have produced an Information Product that can be used to create new knowledge
within a corporate environment examples include more detailed scheduling of
maintenance based on real-world information or improved product design due to
feedback from the M2M solution.
• As mentioned previously, M2M value chains are internal to one company and
cover one solution. IoT Value Chains, meanwhile, are about the use and reuse of
data across value chains and across solutions.

• M2M value chains are internal to one company and cover one solution. IoT Value
Chains, meanwhile, are about the use and reuse of data across value chains and
 IoT value chains
• An IoT solution is formed of several building blocks or components, and
each of these building blocks forms part of the IoT value chain.

• The IoT value chain illustrates how the different components, in

combination with one another or separately, add value to the overall IoT
solution and, in turn, for the end user. Furthermore, each component is
developed by a range of companies, some of which play several roles in the
IoT value chain.
Components of the IoT value chain
• Devices. This category includes existing devices such as smart meters or
vehicles in which the connectivity component has been integrated into the
product design

• Sensor and actuators are connected to the device. Sensors are able to
capture data from the environment (for example, temperature). Actuators
respond to instructions and make changes in the device (for example,
adjusting the temperature on a thermostat).

• Communications hardware enables the device to connect to the network

to send the data from the sensors to the backend systems. This can
include hardware for connecting wirelessly via BlueTooth, Wi-Fi, ZigBee,
LoRa, cellular (for example GSM, 5G, NB-IoT, LTE-M) or a number of
proprietary technologies, or over a fixed network. Some devices will have
hardware to connect to multiple types of network.

• The connectivity network, which can be cellular, fixed or satellite, delivers

the data from the sensors over the internet or a private network
connection to the user’s backend systems.
• Backend systems include the servers to collect and analyse the data
coming from the sensors and from other sources (for example, weather
forecast data). These backend systems can be found in the public or private
cloud, or on on-premises hardware. For very simple systems, the backend
can be a standard PC.

• Software platforms such as device management, security and data

analytics ensure that IoT devices are functioning correctly and have not
been compromised. Such platforms also include data analytics software to
make sense of the data and improve business processes, as well as data
bases to store the data.

• This area also includes services such as billing and customer support.
IoT value chain
 SDN/NFV Architecture
• The development of IoT has resulted in large-scale IoT networks with vast numbers
of heterogeneous devices, which are facing the following problems
• . (i) Difficulties in control and management. IoT applications serve different
purposes and are deployed in isolated ways. Heterogeneous devices are
geographically distributed and used in various application domains.

• (ii) Difficult to program and configure the devices. On account of the huge
difference of devices’ capabilities, especially the constrains in memory, bandwidth
and energy, it is difficult to program or configure the devices with new functions in
a unified and efficient way.

• (iii) Long service provisioning time. The deployment of a new IoT service requires
the whole cycle of developing the new service, including installing new sensors,
setting up connections to the network infrastructure, and testing the functions.

• (iv) Resources have not been fully used. Data and devices have not yet been
considered to be network resources. Moreover, scalability, flexibility, complexity,
security as well as efficient data, traffic and device management are also challenges
for the IoT networks. An essential reason behind these problems is that the IoT
networks lack flexibility, intelligence, and application-specific controls
 So, why we need/want NFV(/SDN)?
1. Virtualization: Use network resource without worrying about where it is
physically located, how much it is, how it is organized, etc.
2. Orchestration: Manage thousands of devices
3. Programmable: Should be able to change behavior on the fly.
4. Dynamic Scaling: Should be able to change size, quantity
5. Automation
6. Visibility: Monitor resources, connectivity
7. Performance: Optimize network device utilization
8. Multi-tenancy: a single instance of software runs on a server and
serves multiple tenants. A tenant is a group of users who share a common
access with specific privileges to the software instance
9. Service Integration
10. Openness: Full choice of modular plug-ins
Note: These are exactly the same reasons why we need/want SDN.
• Software-Defined Networking:

• SDN refers to the ability to program the network.

• SDN makes the network programmable (which means network admins can
quickly make adjustments to the network based on changing requirements).

• SDN is made possible by separating the control plane (the brains of the
network) from the data plane (the muscle of the network)
 Traditional network Router In
Summary
• Typical Networking Software
– Management plane
– Control Plane – The brain/decision maker
– Data Plane – Packet forwarder
 Imagine IF The Network
is……..!!!
Control Plane SDN
Logically-centralized control Concept:
Smart Separate
API to the data plane
Control plane
Separated and Data
plane.
Dumb,
fast

Switches

Data Plane
 Planes of Networking

• Data Plane:
• All activities involving as well as resulting from data packets sent by the end user,
e.g.,Forwarding
• Fragmentation and reassembly
• Replication for multicasting

• Control Plane:
• All activities that are necessary to perform data plane activities but do not involve end-user
data packets
• Making routing tables
• Setting packet handling policies (e.g., security)
• Base station beacons announcing availability of services
 Planes of Networking

• Management Plane:
• All activities related to provisioning and monitoring of the networks Fault, Configuration,
Accounting, Performance and Security (FCAPS).
• Instantiate new devices and protocols (Turn devices on/off)
• Optional
• May be handled manually for small networks.

• Services Plane:
• Middlebox services to improve performance or security, e.g., Load Balancers, Proxy Service,
Intrusion Detection, Firewalls, SSL Off-loaders
• Optional :
• Not required for small networks
• . Software-defined networking (SDN) technology is characterized by separating
the control and data plane, providing programmability and standardized APIs. SDN
enables a global view of the network and provides capabilities to use network
resources efficiently. Therefore, SDN reduces the overhead of network management
and improves the flexibility of networks

• SDN is a software layer, it provides advantages such as reduced manual efforts,

dynamic scalability, and central management of network devices. To understand
better, consider the following: In traditional networks, each network device in
enterprise or data centre is configured manually, something which is not only
error-prone, but also requires manual reconfiguration (a highly tedious and time-
consuming task) whenever there’s a change in network.

• SDN, on the other hand, aims to have a holistic view of the network - you can
configure/monitor/troubleshoot network devices with ease from central point,
avoiding a lot of manual effort, hence saving time and money in the process.
• SDN enables networking elements (i.e., switches in Figure 1b) on the data plane to
be dynamically configured by the controllers on the control plane. New services can
be programmed and injected into the SDN controllers through a standard
northbound API, which correspondingly configures the routing tables of the
switches (i.e., flow tables), guiding the switches to forward the packets or flows of
the user applications through a standard southbound API. SDN benefits networks
with:

• A global view of the whole network, including its resources. Hence, network
resources can be used more efficiently.
• Reduced overhead of network management, due to software-configured devices
and network resources that expose uniform interfaces through standard abstractions.
• Improved network flexibility through programmability, i.e., new network services
can be provided on the fly through standard APIs and network function
abstractions.
• SDN Architecture : Network Devices (Data Plane)
• Data Plane is consist of various Network devices both physical and Virtual. The
main duty of data plane is Forwarding. In the previous traditional networks, both
control and data plane was in the same device. But with SDN, network devices has
only data plane. So, the main role of these network devices is only Forwarding the
data. This provide a very efficient Forwarding mechanism.
• SDN Architecture : SDN Controller (Control Plane)
• SDN Controller is the Center of the SDN Architecture and the most important one
of SDN Architecture Components. In other words, SDN Controller is the brain of
the system. The control of all the data plane devices are done via SDN Controller.
It also controls the Applications at Application Layer. SDN Controller
communicate and control these upper and lower layer with APIs through Interfaces.
• Open Flow is the protocol used in SDN, that is used to communicate forwarding
plane and control plane of the network. In other words, the communication between
Controller and the Network Devices are done with Open Flow.

• It allows operations, manuplations on Network Devices over Open Flow Interface .

• Open Flow has some common roles:
• • Open Flow allows separation of control and data planes in the network.
•It provides centralization of the control.
• Open Flow uses Flow based control mechanism.
• Takes advantage routing tables in Ethernet switches and routers.
Basic OpenFlow: How Does it Work?
• Controller manages the traffic (network
flows) by manipulating the flow table at
switches.
– Instructions are stored in flow tables.
• When packet arrives at switch, match the
header fields with flow entries in a flow
table.
• If any entry matches, performs indicated
actions and update the counters.
• If Does not match, Switch asks controller by
Control Plane : sending a message with the packet header.

Flow Table (has 3 sections)

Communicate
via secure
Channel
Flow table

Data Plane

Match the packet header

• the southbound interface function is to
enable communication between the SDN
controller and the network nodes (both
physical and virtual switches and routers)
so that the router can discover network
topology, define network flows and
implement requests relayed to it via
northbound APIs.

• southbound APIs include communication

with the switch fabric, network
virtualization protocols, or the integration
of a distributed computing network

• The northbound interface describes the

area of protocol-supported communication
between the controller and applications or
higher layer control programs.
• northbound APIs include management
solutions for automation and orchestration,
and the sharing of actionable data between
systems.
• Southbound SDN
• In SDN, southbound interfaces is the OpenFlow protocol specification that enables
communication between controllers and switches and other network nodes, which is
with the lower-level components. This further lets the router to identify network
topology, determine network flows and implement request sent to it via northbound
interfaces.
• Southbound Interface allows the SDN Controller (the Control Plane) to interact
with the devices

• Northbound SDN
• Contradictory to southbound API, northbound interfaces allows communication
among the higher-level components. While the traditional networks use firewall or
load balancer to control data plane behavior , SDN installs applications that uses the
controller and these applications communicate with the controller through its
northbound interface.
• Northbound Interface allows the user (the Application Plane) to interact with
the SDN Controller (the Control Plane) through a web interface or a RESTful API
script.
 Software-Defined Network with key
Abstractions
Network
Well-defined API Virtualization
Traffic Other
Routin
Application Security Enginee Applicati
g ring ons Network Map
Plane
Abstraction
Control Network Operating System
Plane Instructio
ns
Instructio Instructio Instructio
ns ns ns

Forwar
Separation of Data
ding
and Control Plane
Forwar
Forwar ding
Data Plane ding

Forwar
ding
 Virtualization
• Virtualization is the ability to run multiple operating systems on a single physical
system and share the underlying hardware resources

• It is the process by which one computer hosts the appearance of many computers.

• Virtualization is used to improve IT throughput and costs by using physical

resources as a pool from which virtual resources can be allocated.

• Software called a hypervisor connects directly to that hardware and allows you
to split 1 system into separate, distinct, and secure environments known as virtual
machines (VMs).

• These VMs rely on the hypervisor’s ability to separate the machine’s resources
from the hardware and distribute them appropriately.
• The physical hardware, equipped with a hypervisor, is called the host,
while the many VMs that use its resources are guests.

• These guests treat computing resources—like CPU, memory, and storage

as a pool of resources that can easily be relocated.

• Operators can control virtual instances of CPU, memory, storage, and other
resources, so guests receive the resources they need when they need them.
• Virtualization can be applied broadly to just about everything that you
could imagine:
• Memory
• Networks
• Storage
• Hardware
• Operating systems
• Applications
 NFV
Network functions virtualization (NFV) is the replacement of network
appliance hardware with virtual machines. The virtual machines use
a hypervisor to run networking software and processes such as routing and load
balancing.

NFV allows for the separation of communication services from dedicated

hardware, such as routers and firewalls.

This separation means network operations can provide new services

dynamically and without installing new hardware.

Deploying network components with network functions virtualization takes

hours instead of months like with traditional networking. Also, the virtualized
services can run on less expensive, generic servers instead of proprietary
hardware.
Additional reasons to use network functions virtualization include:

➢Pay-as-you-go: Pay-as-you-go NFV models can reduce costs because businesses

pay only for what they need.

➢Fewer appliances: Because NFV runs on virtual machines instead of physical

machines, fewer appliances are necessary and operational costs are lower.

➢Scalability: Scaling the network architecture with virtual machines is faster and
easier, and it does not require purchasing additional hardware.
NFV architecture consists of:

➢Virtualized network functions (VNFs)are software applications that deliver

network functions such as file sharing, directory services, and IP configuration.

➢Network functions virtualization infrastructure (NFVi) consists of

the infrastructure components—compute, storage, networking—on a platform to
support software, such as a hypervisor like KVM(Kernel-Based Virtual
Machine) or a container management platform, needed to run network apps.

➢Management, automation and network orchestration (MANO) provides the

framework for managing NFV infrastructure and provisioning new VNFs.
• What are the advantages of NFV?
• NFV reduces the need for dedicated hardware to deploy and manage
networks by offloading network functions into software that can run on
industry-standard hardware and can be managed from anywhere within the
operator’s network

• It includes:
• Reduce network functions of hardware
• Reduce space needed for network hardware
• Reduce network power consumption
• Reduce network maintenance costs
• Easier network upgrades
• Longer life cycles for network hardware
• Reduce maintenance and hardware costs
As a result, virtualization of currently used hardwares (routers, firewalls, load balancers
etc) has achieved. By using a standard IT virtualization and Cloud technologies, a newly
define NFV Architecture introduced. With this new NFV Arhitecture network functions
are implemented as software.
 Relation between Software-defined networking (SDN) and NFV

➢NFV and SDN are not dependent on each other, but they do have similarities. Both
rely on virtualization and use network abstraction, but how they separate functions and
abstract resources is different.

➢SDN separates network forwarding functions from network control functions with the
goal of creating a network that is centrally manageable and programmable. NFV
abstracts network functions from hardware. NFV supports SDN by providing the
infrastructure on which SDN software can run.

➢NFV and SDN can be used together, depending on what you want to accomplish, and
both use commodity hardware. With NFV and SDN, you can create a network
architecture that is more flexible, programmable, and uses resources efficiently.
 Storage in IoT
• The IoT technology infrastructure:
• Four major building blocks of IoT:
• Hardware: This is where data is produced. The hardware layer includes the
physical devices with their in-built microprocessors, sensors, actuators and
communication hardware.

• Communication: This is where data gets transported. This part of the technology
infrastructure ensures the hardware is connected to the network, via proprietary
or open-source communication protocols.

• Software backend: This is where data is managed. The software backend manages
all connected devices and networks and provides the necessary data integration as
well as the interface to other systems (e.g., ERP-system).

• Applications: This is where data is turned into value. In the application layer, IoT
use cases get presented to the user (B2C or B2B). Most of the applications run on
smart phones, tablets, PCs or other devices/things and “do something valuable”
with the data.
 IoT Cloud Based Services
• Service models: This consists of the particular types of services that you can
access on a cloud computing platform.
• Cloud Providers offer services that can be grouped into three categories.
• 1. Software as a Service (SaaS): In this model, a complete application is offered to
the customer, as a service on demand. A single instance of the service runs on the
cloud & multiple end users are serviced. On the customers‟ side, there is no need
for upfront investment in servers or software licenses, while for the provider, the
costs are lowered, since only a single application needs to be hosted & maintained.
Today SaaS is offered by companies such as Google, Salesforce, Microsoft, Zoho,
etc.
• 2. Platform as a Service (Paas): Here, a layer of software, or development
environment is encapsulated & offered as a service, upon which other higher levels
of service can be built. The customer has the freedom to build his own applications,
which run on the provider‟s infrastructure. To meet manageability and scalability
requirements of the applications, PaaS providers offer a predefined combination of
OS and application servers, such as LAMP platform (Linux, Apache, MySql and
PHP), restricted J2EE, Ruby etc. Google‟s App Engine, Force.com, etc are some of
the popular PaaS examples.
• 3. Infrastructure as a Service (Iaas): IaaS provides basic storage and computing
capabilities as standardized services over the network. Servers, storage systems,
networking equipment, data centre space etc. are pooled and made available to
handle workloads. The customer would typically deploy his own software on the
infrastructure. Some common examples are Amazon, GoGrid, 3 Tera, etc.
• 4. Storage as a service: The capability provided to the consumer is use the storage
from the remote servers as from the local storage. Some of this model provide the
database storage others provide the storage used to store and retrieve any files. This
model is used in almost every cloud service.

• 5. Information as a service: The capability provided to the consumer is the

consumer can retrieve the information (traffic state, stock price, weather and so on)
through public API.

• 6. Process as a service: The capability provided to the consumer is the business

process which can easily compose several different systems on your demand
through the manage tools, you can use it as a system and change it agilely.

• 7. Integration as a service: The capability provided to the consumer is delivery the

Enterprise application integration technology as the service and can be accessed
anytime and anywhere.

• 8. Security as a service: The capability provided to the consumer is delivery the

security system through the Internet.
• 9. Management as a service: The capability provided to the consumer is delivery
the hardware and network states of the system to consumer and the consumer can
use this information to manage their remote system.

• 10. Testing as a service: The capability provided to the consumer is delivery the
service can be used to test their remote application or local application.
END