M2M to IoT A Market Perspective Introduction, Some Definitions, M2M Value Chains,

IoT Value Chains, An emerging industrial structure for IoT, The international driven global
value chain and global information monopolies. M2M to IoT-An Architectural Overview
Building an architecture, Main design principles and needed capabilities, An IoT architecture
outline, standards considerations.

M2M to IoT A market perspective

M2M to IoT
A Market Perspective
The increasing interest in M2M and IoT solutions has been driven by the potential large
market and growth opportunities.
In M2M and IoT, the technology used for these solutions may be very similar, even use the
same base components but the data is managed will be different.
In an M2M solution, data remains within strict boundaries, it is used solely for the purpose.
In IoT, data may be used and reused for many different purposes.
Data can be shared between companies and value chains in internal information
marketplaces.
Data could be publicly exchanged on a public information marketplace.
These marketplaces are based on the exchange of data in order to create information
products.
Definition of M2M
Machine to machine refers to technology that allowed both wireless and wired systems to
communicate with other devices of the same type.
Global value chains
A value chain describes the full range of activities that firms and workers perform to bring a
product from its conception to end use and beyond, including design, production, marketing,
distribution, and support to the final consumer. Analysing an industry from a global value
chain (GVC) perspective permits understanding of the context of globalization on the

value-adding activities, from conception and production to end use. GVC analysis therefore
provides a holistic view of global industries both from the top down an
M2M value chain
Fig 2.1 M2M Value Chain
IoT value chains

Fig 2.2 IoT Value Chain

An emerging industrial structure for IoT
Here are four trends tech leaders might want to consider when architecting their next wireless
infrastructure.

In the industrial world, the challenge of IoT hardware design lies in the bewildering array of
use case requirements. Take temperature sensors as a simple example. Depending on criteria
like accuracy, temperature range, response time and stability, there could be hundreds of
-of-the-box wireless
sensor out there that where IoT rapid
prototyping comes in.
Hardware prototyping standards like mikroBUS allow you to build a customized IoT device
prototype in a matter of a few hours and with efficient resources. From a broad portfolio of
ready-to-use, compatible sensor, interface and wireless modules as well as compilers and
development boards, you can create the optimal hardware mix-and-match that caters to your
industrial use case. With rapid prototyping, companies can ratify the technical and business
viability of their IIoT solution in a cost-effective and agile fashion, which lays the
cornerstone for a successful roll-out.

An average factory operates with legacy industrial systems that are nowhere near being
connected. While these systems employ a number of proprietary communication protocols for
automation purposes, data is captive within discrete control loops, creating numerous data
silos on the factory floor. The lack of interoperability among these protocols further hinders
the implementation of a factory-wide monitoring and control network. Emerging retrofit
wireless connectivity now enables manufacturers to connect and acquire data from their
legacy assets and systems in a simple and cost-effective manner without costly production
downtime and invasive hardware changes. Through the use of an integration platform,
operational data can be fetched from controllers through wired-based serial and other
industrial protocols then forwarded to a remote control center using long-range wireless
connectivity.
 -Defined Radio
As no wireless solution is use-case agnostic, a typical IIoT architecture is likely to
incorporate multiple radio protocols and standards. Plus, many industrial facilities today have
already implemented wireless networks (e.g. Wi-
and look to deploy new types of connectivity to tap into other high-
critical to create an efficient and backward-compatible IIoT architecture that can
accommodate the co-existence of different wireless technologies, which is why software-
defined radio (SDR) is gaining momentum. SDR refers to a radio communication method
where the majority of signal processing is done using software, as opposed to the traditional
hardware-driven approach. IoT gateways leveraging SDR can incorporate and decode

adjustments or additions of new wireless solutions to the architecture can be achieved with
simple software updates. This allows companies to dynamically adapt to future operational
and technological changes while continuing to support legacy wireless devices in the field.
-Based IIoT Platform Design
Depending on criteria like security, reliability, data ownership and costs, companies need to
choose among an on-premise, public or private cloud deployment, or even a hybrid approach.
As the IIoT use cases and architecture scale, the decision on the deployment model and/or
cloud vendor is subject to change as well.
An IIoT platform, typically a device management platform, that comes with a portable,
container-based design renders industrial users with full flexibility in selecting their preferred
backend environment. At the same time, it enables a simple migration to another server as
needed without compromising the consistency or functionality of the application. The idea of
a container-based design is that individual applications are packaged and delivered within
discrete, standardized containers called Docker. With this modular architecture, users can
decide which specific platform functions/ applications they want to use and where to deploy
them. Thanks to its flexibility and portability, the container-based design facilitates an
interoperable and future-proof IIoT archit
needs.
The international driven global value chain and global information monopolies
GVCs make a significant contribution to international development. Value-added trade
contributes about 30% to the GDP of developing countries, significantly more than it does in
developed countries (18%) furthermore the level of participation in GVCs is associated with
stronger levels of GDP per capita growth. GVCs thus have a direct impact on the economy,
employment and income and create opportunities for development. They can also be an
important mechanism for developing countries to enhance productive capacity, by increasing
the rate of adoption of technology and through workforce skill development, thus building the
foundations for long-term industrial upgrading.
However, there are limitations to the GVC approach. Their contribution to the growth may be
limited if the work done in-country is relatively low value adding (ie. contributes only a small
part of the total value added for the product or service). In addition, there is no automatic
process that guarantees diffusion of technology, skill-building and upgrading. Developing
countries thus face the risk of operating in permanently low value-added activities. Finally,
there are potential negative impacts on the environment and social conditions, including: poor
workplace conditions, occupational safety and health, and job security. The relative ease with
which the Value Chain Governors can relocate their production (often to lower cost
countries) also create additional risks.
Countries need to carefully assess the pros and cons of GVC participation and the costs and
benefits of proactive policies to promote GVCs or GVC-led development strategies.
Promoting GVC participation implies targeting specific GVC segments and GVC
participation can only form one part of a country's overall development strategy.
de
profiles and industrial capabilities in order to select strategic GVC development paths.
Achieving upgrading opportunities through CVCs requires a structured approach that
includes:
tasks and
activities);
wth by providing the right framework conditions for trade and FDI and by
putting in place the needed infrastructure; and

M2M to IoT-An Architectural Overview

IoT Architecture Overview
IoT can be classified into a four or five-layered architecture which gives you a complete
overview of how it works in real life. The various components of the architecture include the
following:
Four-layered architecture: this includes media/device layer, network layer, service and
application support layer, and application layer.
Five-layered architecture: this includes perception layer, network layer, middleware layer,
application layer, and business layer.
Functions of Each Layer
Sensor/Perception layer: This layer comprises of wireless devices, sensors, and radio
frequency identification (RFID) tags that are used for collecting and transmitting raw data
such as the temperature, moisture, etc. which is passed on to the next layer.
Network layer: This layer is largely responsible for routing data to the next layer in the
hierarchy with the help of network protocols. It uses wired and wireless technologies for data
transmission.
Middleware layer: This layer comprises of databases that store the information passed on by
the lower layers where it performs information processing and uses the results to make
further decisions.