Unit -1

Topics to be covered

Introduction: Definition, Characteristics of IOT, IOT Conceptual framework, IOT Architectural

view, Physical design of IOT, Logical design of IOT, Application of IOT.
-----------------------------------------------------------------------------------------------------------------------------------------
------------------

Definition-The Internet of Things, also called The Internet of Objects, refers to a wireless
network between objects. By embedding short-range mobile transceivers into a wide array of
additional gadgets and everyday items, enabling new forms of communication between
people and things, and between things themselves. The term Internet of Things has come to
describe a number of technologies and research disciplines that enable the Internet to reach
out into the real world of physical objects. Things having identities and virtual personalities
operating in smart spaces using intelligent interfaces to connect and communicate within
social, environmental, and user contexts. From any time, any place connectivity for anyone,
we will now have connectivity for anything.

Fig. 1.1 Internet of Things Accessibility

Characteristics of IOT-The no-need-to-know in terms of the underlying details of

infrastructure, applications interface with the infrastructure via the APIs.The flexibility and
elasticity allows these systems to scale up and down at will utilizing the resources of all kinds
CPU, storage, server capacity, load balancing, and databases The “pay as much as used and
needed” type of utility computing and the “always on!, anywhere and any place” type of
network-based computing. The fundamental characteristics of the IoT are as follows:
 Interconnectivity: With regard to the IoT, anything can be interconnected with the
global information and communication infrastructure.
 Things-related services: The IoT is capable of providing thing-related services within
the constraints of things, such as privacy protection and semantic consistency
between physical things and their associated virtual things. In order to provide thing-
related services within the constraints of things, both the technologies in physical
world and information world will change.

 Heterogeneity: The devices in the IoT are heterogeneous as based on different

hardware platforms and networks. They can interact with other devices or service
platforms through different networks.
 Dynamic changes: The state of devices change dynamically, e.g., sleeping and waking
up, connected and/or disconnected as well as the context of devices including
location and speed. Moreover, the number of devices can change dynamically.
 Enormous scale: The number of devices that need to be managed and that
communicate with each other will be at least an order of magnitude larger than the
devices connected to the current Internet. Even more critical will be the management
of the data generated and their interpretation for application purposes. This relates to
semantics of data, as well as efficient data handling.
 Safety: As we gain benefits from the IoT, we must not forget about safety. As both
the creators and recipients of the IoT, we must design for safety. This includes the
safety of our personal data and the safety of our physical well-being. Securing the
endpoints, the networks, and the data moving across all of it means creating a
security paradigm that will scale.
 Connectivity: Connectivity enables network accessibility and compatibility.
Accessibility is getting on a network while compatibility provides the common ability
to consume and produce data.

IOT architectural view-IoT architecture consists of different layers of technologies supporting

IoT. It serves to illustrate how various technologies relate to each other and to communicate
the scalability, modularity and configuration of IoT deployments in different scenarios. The
functionality of each layer is described below:
 Smart device / sensor layer: The lowest layer is made up of smart objects integrated
with sensors. The sensors enable the interconnection of the physical and digital
worlds allowing real-time information to be collected and processed. There are
various types of sensors for different purposes. The sensors have the capacity to take
measurements such as temperature, air quality, speed, humidity, pressure, flow,
movement and electricity etc. In some cases, they may also have a degree of memory,
enabling them to record a certain number of measurements. A sensor can measure
 the physical property and convert it into signal that can be understood by an
instrument. Sensors are grouped according to their unique purpose such as
environmental sensors, body sensors, home appliance sensors and vehicle telemetric
sensors, etc
 Gateways and Networks-Massive volume of data will be produced by these tiny
sensors and this requires a robust and high performance wired or wireless network
infrastructure as a transport medium. Current networks, often tied with very different
protocols, have been used to support machine-to-machine (M2M) networks and their
applications. With demand needed to serve a wider range of IoT services and
applications such as high speed transactional services, context- aware applications,
etc, multiple networks with various technologies and access protocols are needed to
work with each other in a heterogeneous configuration. These networks can be in the
form of a private, public or hybrid models and are built to support the communication
requirements for latency, bandwidth or security. Various gateways (microcontroller,
microprocessor) & gateway networks (WI-FI, GSM, GPRS).
 Management Service Layer-The management service renders the processing of
information possible through analytics, security controls, process modeling and
management of devices. One of the important features of the management service
layer is the business and process rule engines. IoT brings connection and interaction
of objects and systems together providing information in the form of events or
contextual data such as temperature of goods, current location and traffic data. Some
of these events require filtering or routing to post-processing systems such as
capturing of periodic sensory data, while others require response to the immediate
situations such as reacting to emergencies on patient’s health conditions. The rule
engines support the formulation of decision logics and trigger interactive and
automated processes to enable a more responsive IoT system.
 Application Layer-The IoT application covers “smart” environments/spaces in
domains such as: Transportation, Building, City, Lifestyle, Retail, Agriculture, Factory,
Supply chain, Emergency, Healthcare, User interaction, Culture and tourism,
Environment and Energy.
 Fig. 1.2 IoT Architecture
IOT conceptual view-
 The main tasks of this framework are to analyze and determine the smart activities of
these intelligent devices through maintaining a dynamic interconnection among those
devices. The proposed framework will help to standardize IoT infrastructure so that it
can receive e-services based on context information leaving the current infrastructure
unchanged. The active collaboration of these heterogeneous devices and protocols
can lead to future ambient computing where the maximum utilization of cloud
computing will be ensured.
 This model is capable of logical division of physical devices placement, creation of
virtual links among different domains, networks and collaborate among multiple
application without any central coordination system. IaaS can afford standard
functionalities to accommodate and provides access to cloud infrastructure. The
service is generally offered by modern data centers maintained by giant companies
and organization. It is categorized as virtualization of resources which permits a user
 to install and run application over virtualization layer and allows the system to be
distributed, configurable and scalable.
 Total infrastructure system can be categorized into 4 layers to receive context
supported e-services out of raw data from the Internet of Things. These 4 layers
establish a generic framework that does not alter the current network infrastructure
but create an interfacing among services and entities through network virtualization.

Fig. 1.3 IoT Conceptual View

1. Connectivity Layer-
This layer includes all the physical devices involved in the framework and the interconnection
among them. Future internet largely depends on the unification of these common objects
found everywhere near us and these should be distinctly identifiable and controllable.
This layer also involves assigning of low range networking devices like sensors, actuators,
RFID tags etc and resource management checks the availability of physical resources of all the
devices and networks involved in the underlying infrastructure. These devices contain very
limited resources and resource management ensures the maximum utilization with little
overhead. It also allows sharing and distribution of information among multiple networks or
single network divided into multiple domains.

2. Access Layer-
 Context Data will be reached to internet via IoT Gateway as captured by short range
devices in form of raw data. Access layer comprises topology definition, network
initiation, creation of domains etc. This layer also includes connection setup, intra-
inter domain communication, scheduling, packet transmissions between flow-sensors
and IoT gateway. The simulation was run later in this paper for different scenario
based on this layer. Feature management contains a feature filter which accepts only
acceptable context data and redundant data are rejected. Large number of sensor
maintains lots of features but only a small subset of features is useful generate a
context data.
 Feature filter helps to reduce irrelevant data transmission, increases the data transfer
rate of useful data and reduce energy and CPU consumption too. Number of features
can be different based on the application requirements and context data types.

3. Abstraction Layer-

 One of the most important characteristics of OpenFlow is to

add virtual layers with the preset layers, leaving the established infrastructure
unchanged. A virtual link can be created among different networks and a common
platform can be developed for various communication systems. The system is fully a
centralized system from physical layer viewpoint but a distribution of service (flow
visor could be utilized) could be maintained. One central system can monitor, control
all sorts of traffics. It can help to achieve better band-width, reliability, robust routing,
etc. which will lead to a better Quality of Services (QoS).
 In a multi-hopping scenario packets are transferred via some adjacent nodes. So,
nodes near to access points bears too much load in comparison to distant nodes in a
downstream scenario and inactivity of these important nodes may cause the network
to be collapsed. Virtual presence of sensor nodes can solve the problem where we can
create a virtual link between two sensor networks through access point negotiation.
So, we can design a three a three layer platform, where common platform and
virtualization layer are newly added with established infrastructure. Sensors need not
to be worried about reach-ability or their placement even in harsh areas. Packet could
be sent to any nodes even if it is sited on different networks.
4. Service Layer-
 Storage management bears the idea about all sorts of unfamiliar and/or important
technologies and information which can turn the system scalable and efficient. It is
not only responsible for storing data but also to provide security along with it. It also
allows accessing data effectively; integrating data to enhance service intelligence,
analysis based on the services required and most importantly increases the storage
efficiency. Storage and management layer involves data storage & system supervision,
software services and business management & operations. Though they are included
in one layer, the business support system resides slightly above of cloud computing
service whereas Open-Flow is placed below of it as presented to include
virtualizations and monitor management.
 Service management combines the required services with organizational solutions
and thus new
generation user service becomes simplified. These forthcoming services are necessit
ated to be co

interrelated and combined in order to meet the demand socio- economic factors such
as environment analysis, safety measurement, climate management, agriculture
modernization etc.

IOT Functional View-The Internet of Things concept refers to uniquely identifiable things
with their virtual representations in an Internet-like structure and IoT solutions comprising a
number of components such as
(1) Module for interaction with local IoT devices. This module is responsible for acquisition of
observations and their forwarding to remote servers for analysis and permanent storage.
(2) Module for local analysis and processing of observations acquired by IoT devices.
(3) Module for interaction with remote IoT devices, directly over the Internet. This module is
responsible for acquisition of observations and their forwarding to remote servers for
analysis and permanent storage.
(4) Module for application specific data analysis and processing. This module is running on an
application server serving all clients. It is taking requests from mobile and web clients and
relevant IoT observations as input, executes appropriate data processing algorithms and
generates output in terms of knowledge that is later presented to users.
(5) User interface (web or mobile): visual representation of measurements in a given context
(for example on a map) and interaction with the user, i.e. definition of user queries. The
Designs are shown below:

Physical Design of IOT-The Internet of Things will become part of the fabric of everyday life.
It will become part of our overall infrastructure just like water, electricity, telephone, TV and
most recently the Internet. Whereas the current Internet typically connects full-scale
computers, the Internet of Things (as part of the Future Internet) will connect everyday
objects with a strong integration into the physical world.
1. Plug and Play Integration

 If we look at IoT-related technology available today, there is a

huge heterogeneity. It is typically deployed for very specific purposes and the
configure requires significant technical knowledge and may be cumbersome. To
achieve a true Internet of Things we need to move away from such small- scale,
vertical application silos, towards a horizontal infrastructure on which a variety of
applications can run simultaneously. This is only possible if connecting a thing to the
Internet of Things becomes as simple as plugging it in and switching it on. Such plug
and play functionality requires an infrastructure that supports it, starting from the
networking level and going beyond it to the application level. This is closely
related to the aspects discussed in the section on autonomy.
 On the networking level, the plug & play functionality has to enable the
communication, features like the ones provided by IPv6 are in the directions to help in
this process. Suitable infrastructure components have then to be discovered to enable
the integration into the Internet of Things. This includes announcing the
functionalities provided, such as what can be sensed or what can be actuated.
2. Infrastructure Functionality-The infrastructure needs to support applications in finding
the things required. An application may run anywhere, including on the things themselves.
Finding things is not limited to the start-up time of an application. Automatic adaptation is
needed whenever relevant new things become available, things become unavailable or the
status of things changes. The infrastructure has to support the monitoring of such changes
and the adaptation that is required as a result of the changes.
3. Semantic Modeling of Things-To reach the full potential of the Internet of Things,
semantic information regarding the things, the information they can provide or the
actuations they can perform need to be available. It is not sufficient to know that there is a
temperature sensor or an electric motor, but it is important to know which temperature the
sensor measures: the indoor temperature of a room or the temperature of the fridge, and
that the electric motor can open or close the blinds or move something to a different
location. As it may not be possible to provide such semantic information by simply switching
on the thing, the infrastructure should make adding it easy for users. Also, it may be
possible to derive semantic information, given some basic information and additional
knowledge, e.g. deriving information about a room, based on the information that a certain
sensor is located in the room. This should be enabled by the infrastructure.
4. Physical Location and Position-As the Internet of Things is strongly rooted in the physical
world, the
notion of physical location and position are very important, especially for finding things,
but also for
deriving knowledge. Therefore, the infrastructure has to support finding things according to
location (e.g. geo-location based discovery). Taking mobility into account, localization
technologies will play an important role for the Internet of Things and may become
embedded into the infrastructure of the Internet of Things.
5. Security and Privacy-In addition, an infrastructure needs to provide support for security
and privacy functions including identification, confidentiality, integrity, non-repudiation
authentication and authorization. Here the heterogeneity and the need for interoperability
among different ICT systems deployed in the infrastructure and the resource limitations of
IoT devices (e.g., Nano sensors) have to be taken into account.

Logical design of IOT-

 The Logical design of IoT is however too abstract to be used for building directly
concrete architectures. In order to implement a compliant IoT solutions, Reference
Architectures must be defined, describing essential building blocks as well as design
choices able to select specific constructs able to deal with converging requirements
regarding functionality, performance, deployment and security, to name a few.
Interfaces among different technological functional blocks should be standardized;
best practices in terms of functionality and information usage need to be provided.
 Existing literature provides methodologies for dealing with system architectures
(hereafter called Concrete Architectures) based on Views and Perspectives. The way
that the IoT-A project illustrates the Reference Architecture (RA) is through
a matrix that provides clear technological choices in order to develop concrete
architectures. To establish the contents of this matrix we need to analyze all possible
functionalities, mechanisms and protocols that can be used for building any concrete
IoT-related architecture and to show how interconnections could take place between
selected design and technological choices. A system architect should then have a tool
to make a rational selection of protocols, functional components, and architectural
options, needed to build specific IoT systems.
 The IoT-A project sees views as a representation of one or more structural aspects of
an architecture that illustrates how the architecture addresses one or more concerns
held by one or more of its stakeholders. Some typical examples for viewpoints are
Functional, Information, Concurrency, Development, Deployment and Operational
viewpoints. However, architectural decisions often address concerns that are
common to more than one view. These concerns are often related to non-functional
or quality properties.
 The approach that the project is following is to define special perspectives to address
these aspects of a concrete architecture, emphasizing the importance of stakeholder
requirements. Therefore we are define a perspective as a collection of activities,
tactics, and guidelines that are used to ensure that a system exhibits a particular set of
related quality properties that require consideration across a number of the system’s
architectural views, where a quality property is defined as an externally visible, non-
functional property of a system such as performance, security, or scalability.
 Fig. 1.4 IoT Logical View

IOT applications-Potential applications of the IoT are numerous and diverse, permeating into
practically all areas of every-day life of individuals, enterprises, and society as a whole. The
IoT application covers smart environments/spaces in domains such as: Transportation,
Building, City, Lifestyle, Retail, Agriculture, Factory, Supply chain, Emergency, Healthcare,
User interaction, Culture and tourism, Environment and Energy. Below are some of the IoT
applications.
 IOsL (Internet of smart living)-Remote Control Appliances: Switching on and off
remotely appliances to avoid accidents and save energy, Weather: Displays outdoor
weather conditions such as humidity, temperature, pressure, wind speed and rain
levels with ability to transmit data over long distances, “mart Home Appliances:
Refrigerators with LCD screen telling what’s inside, food that’s about to expire,
ingredients you need to buy and with all the information available on a Smartphone
app. Washing machines allowing you to monitor the laundry remotely, and. Kitchen
ranges with interface to a Smartphone app allowing remotely adjustable temperature
control and monitoring the oven’s self-cleaning feature, Safety Monitoring: cameras,
and home alarm systems making people feel safe in their daily life at home, Intrusion
Detection Systems: Detection of window and door openings and violations to prevent
intruders, Energy and Water Use: Energy and water supply consumption monitoring
to obtain advice on how to save cost and resources.

 IOsC ( Internet of smart cities)-Structural Health: Monitoring

of vibrations and material conditions in buildings, bridges and historical monuments,
Lightning: intelligent and weather adaptive lighting in street lights, Safety: Digital
video monitoring, fire control management, public announcement systems,
Transportation: Smart Roads and Intelligent High-ways with warning messages and
 diversions according to climate conditions and unexpected events like accidents or
traffic jams, Smart Parking: Real-time monitoring of parking spaces availability in the
city making residents able to identify and reserve the closest available spaces, Waste
Management: Detection of rubbish levels in containers to optimize the trash
collection routes. Garbage cans and recycle bins with RFID tags allow the sanitation
staff to see when garbage has been put out.
 IOsE (Internet of smart environment)-Air Pollution monitoring: Control of CO2
emissions of factories, pollution emitted by cars and toxic gases generated in farms,
Forest Fire Detection: Monitoring of combustion gases and preemptive fire conditions
to define alert zones, Weather monitoring: weather conditions monitoring such as
humidity, temperature, pressure, wind speed and rain, Earthquake Early Detection,
Water Quality: Study of water suitability in rivers and the sea for eligibility in drinkable
use, River Floods: Monitoring of water level variations in rivers, dams and reservoirs
during rainy days, Protecting wildlife: Tracking collars utilizing GPS/GSM modules to
locate and track wild animals and communicate their coordinates via SMS.
 IOsI (Internet of smart industry)-Explosive and Hazardous Gases: Detection of gas
levels and leakages in industrial environments, surroundings of chemical factories and
inside mines, Monitoring of toxic gas and oxygen levels inside chemical plants to
ensure workers and goods safety, Monitoring of water, oil and gas levels in storage
tanks and Cisterns, Maintenance and repair: Early predictions on equipment
malfunctions and service maintenance can be automatically scheduled ahead of an
actual part failure by installing sensors inside equipment to monitor and send reports.
 IOsH (Internet of smart health)-Patients Surveillance: Monitoring of conditions of
patients inside hospitals and in old people’s home, Medical Fridges: Control of
conditions inside freezers storing vaccines, medicines and organic elements, Fall
Detection: Assistance for elderly or disabled people living independent, Dental:
Bluetooth connected toothbrush with Smartphone app analyzes the brushing uses
and gives information on the brushing habits on the Smartphone for private
information or for showing statistics to the dentist, Physical Activity Monitoring:
Wireless sensors placed across the mattress sensing small motions, like breathing and
heart rate and large motions caused by tossing and turning during sleep, providing
data available through an app on the Smartphone.
 IOsE (internet of smart energy)-Smart Grid: Energy consumption monitoring and
management, Wind Turbines/ Power house: Monitoring and analyzing the flow of
energy from wind turbines & power house, and two-way communication with
consumers’ smart meters to analyze consumption

patterns, Power Supply Controllers: Controller for AC-DC power supplies that
determines required energy, and improve energy efficiency with less energy waste for
power supplies related to computers, telecommunications, and consumer electronics
 applications, Photovoltaic Installations: Monitoring and optimization of performance
in solar energy plants.
 IOsA (internet of smart agriculture)-Green Houses: Control micro-climate conditions
to maximize the production of fruits and vegetables and its quality, Compost: Control
of humidity and temperature levels in alfalfa, hay, straw, etc. to prevent fungus and
other microbial contaminants, Animal Farming/Tracking: Location and identification of
animals grazing in open pastures or location in big stables, Study of ventilation
and air quality in farms and detection of harmful gases from excrements, Offspring
Care: Control of growing conditions of the offspring in animal farms to ensure its
survival and health, field Monitoring: Reducing spoilage and crop waste with better
monitoring, accurate ongoing data obtaining, and management of the agriculture
fields, including better control of fertilizing, electricity and watering.

Physical View-It defines different layered level component required to create the device as
mentioned in diagram.

Fig. 1.5 Physical View

Technologies behind the Internet of Things
by Digital Foundry Technologies

The internet of things (IoT) promises a smarter future. One in which a faltering bridge informs local
transportation authorities that it needs repair. Or a bridge that can warn oncoming smart cars to
prepare to drive over a frozen surface. An automated manufacturing plant that orders its own supplies
and even schedules and executes maintenance. An environment with every thing connected to and
aware of every other thing, sharing information to assist the next thing down the line or provide
feedback in any direction.
Two layers are required to actualize the reality of an insightful and intuitive everything: Application
and connectivity. The application layer is composed of physical products and services such as
intelligent cars, smart roads, and connected thermostats. Connectivity breathes life into these objects,
creating a cohesive experience that adds value to the system and its users.
Most importantly, the internet of things is about much more than just things. It is the promise to
create intelligent, connected systems, smarter than the sum of their parts, that provide real-time
analytics, useful projections, and tangible value from that data and interactivity. In addition to the set
of physical objects that make up an IoT network, there are several technologies that bring it to life.
Digital Foundry has completed a handful of projects that exist in this space. If you represent a global
business that is looking for partners to help develop an IoT project, we’d love to hear from you.
Otherwise, please enjoy this post, an introduction to the primary protocols behind the IoT
technologies: ZigBee, Thread, Z-Wave, and Wi-Fi.

ZigBee
ZigBee is a wireless mesh networking standard developed for wireless control and monitoring
applications that require long battery life. It is a simple and inexpensive way to create personal area
networks with low-power radios. The standards are maintained and published by the ZigBee
Alliance, a nonprofit association of nearly 450 global companies.
The low latency and simple, short messaging mode requirements set by the ZigBee Alliance make
Zigbee devices desirable for engineering teams working on IoT applications. Similarly, the high
standard that all manufacturers are required to meet decreases the business risk for a product owner
investing in this protocol. For most users the most important ZigBee requirement is the minimum 2-
year radio battery life, which practically eliminates the risk of a dead IoT product at the most
important time – such as a fire alarm that must be on constantly but only responds once, if ever, over
a long period of time.
In order for a radio to perform for 2 years on a single battery, ZigBee compromises the signal’s
amplitude and range. This is not a problem, however, for its primary purpose to connect equipment
that is close together and does not need high rates of data transfer. This includes most household
electronics, traffic management systems, and many industrial applications.. The mesh network
provides high reliability and security and can transmit over greater distances by going through
intermediate devices to reach distant devices.
To learn more about the ZigBee radio protocol or the ZigBee alliance, go to www.ZigBee.org to get
the latest news and in-depth articles on the global radio standards.

Thread
Thread is an IPv6-based protocol that was developed specifically for IoT smart home products. It
was released in 2014 by the Thread Group, a working group of companies such as Google, Samsung,
Arm Holdings, Yale Locks, and Silicon Labs. Intent on becoming the standard for household IoT
devices, the Thread Group announced intentions for a partnership and cross certification with the
ZigBee alliance in early 2016.
Engineers are drawn to Thread as an IP-addressable protocol that easily creates and manages secure
connections between hundreds of devices with cloud access and AES encryption. Product owners
looking to place faith in Thread’s technology can take solace from the number of innovative and
leading brands around the world that have come together to develop and support this protocol. Users
love that the security that comes with Thread’s AES encryption is enabled through simple-to-set-up
systems that are fully operational within minutes of plugging in.
One of the few critiques on Thread is its existence. Admittedly, yet another wireless communication
protocol aimed at the IoT applications market creates more fragmentation in an expanding selection
of radio platforms for wireless devices. If you want to learn more about the Thread Group, other
companies or applications that use the Thread protocol, or expand on the functionality of Thread,
visit www.ThreadGroup.org

Z-Wave
The Z-Wave wireless communications protocol was designed for home automation by a Danish
startup later acquired by Sigma Designs. Joining Sigma in the Z-Wave Alliance are Nortek Security,
ADT Corporation, Ingersoll Rand, and LG Uplus. Z-Wave is one of the most widely used IoT
wireless protocols, employed by brands such as Honeywell, AT&T, Verizon, GE, LG, and ADT
home security.
Working on a 900 MHz band, far from Bluetooth and Wi-Fi, makes Z-Wave radios practically
immune to interference and thus ideal from an engineering point of view. Product owners should
appreciate the Z-Wave full mesh network, which can link up to 232 devices for incredibly scalable
platforms that won’t be outgrown by their application. End users already enjoy many Z-Wave
products, probably without knowing it, and this wide adoption makes it a well-tested networking
protocol.
Products that use the Z-Wave wireless protocol rely Sigma Designs as the sole licensor of Z-Wave.
While this helps to maintain uniformity and reliability, it is worth noting that this could be a deal-
breaking risk for some applications.
Anyone interested in learning more about the Z-Wave wireless protocol should visit www.Z-
WaveAlliance.org to learn more about their certification policy and visit www.Z-Wave.com to learn
more about current applications and products that use Z-Wave radios.

Wi-Fi
Wi-Fi is the most generally known protocol for wireless communication across connected devices.
The standard on which it is based, IEEE 802.11, was released in 1997. In 1999, the WiFi Alliance
was formed to oversee and hold the Wi-Fi trademark, under which products using this technology are
sold.
As a commonly used home wireless local area network (WLAN) between devices this protocol
almost always has an existing network which users are already familiar with. With such broad use
there are high standards for network encryption with WPA2 and WPS satisfying the majority of
engineers and global customers. The high penetration and existing security should similarly please
product owners considering this protocol as their IoT platform’s radio standard.
Wi-Fi requires strong radios to achieve the distance and penetration necessary for a constant and
stable connection between a consumer’s desktops, laptops, mobile devices, and home network. This
strength requires the most significant power of all the traditional IoT protocols available. While high
signal strength requirements are great for connectivity and reliability, they also require high power
usage, which will usually require a Wi-Fi device to either be connected to a wall outlet, like a home
router, or to charge daily as in the case of a mobile device.
If you’re looking to learn more about the Wi-Fi protocol, its trademark, and associated products, go
to www.Wi-Fi.org.

7 Types of Industrial IoT Data Sources (And How To Use Them)

Where does industrial IoT data come from?
Most people would say it comes from assets like pumps, turbine engines and drilling rigs.
But there’s more to industrial IoT than machine data.
Machine data doesn’t tell a complete story in every case. By combining data from disparate sources you
can create new insights. And give engineers a complete view of the problem they need to solve.
In this post, I’ll show you the 7 different types of data sources you can use to create IoT applications.

1. Industrial Control Systems

IoT makes it possible to leverage the data you already have in your SCADA system or historian.
A lot of companies we talk to have been gathering data in these systems for almost 30 years. But this
data could only be used retrospectively until now.
Machine learning services like Cortana Analytics, SAP HANA and IBM Watson have opened the doors for
IoT-based predictive maintenance.
By applying a machine learning algorithm to your SCADA data, you can predict a pump failure. Or
determine the remaining useful life of a turbine engine.
If you already have a large volume of machine log data, machine learning will help you put that data to
good use.
But knowing about an imminent failure isn’t enough. That’s why our IoT Application Suite has a strong
focus on driving real-time actions.

2. Business Applications
Data silos are still very common in industrial organizations. And this leads to missed opportunities
because the data is already there. The right people just don’t have access to it when they need it.
Data from applications like your CRM, ERP or EAM can provide context that goes beyond what’s wrong
with a machine.
IoT-enabled field service can dramatically improve customer experience. Giving technicians access to
CRM data from their tablet shows them a detailed customer history. And they won’t have to call the
office to answer the customer’s questions.
You can also build upon predictive maintenance with business data. When the machine learning
algorithm predicts an asset failure you connect to your EAM system and check the warranty.
If the EAM data shows that the asset is still under warranty, you don’t send a maintenance crew.
Instead, you can have it kick off a task for someone to call out the manufacturer to fix the problem.
By automatically checking the warranty, you can prevent compromising warranties and reduce
maintenance costs.

3. Wearables
Data from smart watches and fitness trackers aren’t as useful as machine data for IIoT. But there is a
new breed of industrial wearables making a name for itself.
These new wearables promise to make difficult and often dangerous jobs safer and easier.
Data from wearable gas detection sensors can track employee exposure levels. That data can then be
displayed alongside their work schedule. This helps dispatchers adjust the schedule based on the
worker’s exposure. And ultimately it leads to fewer health issues.
Another wearable that’s gaining popularity with large mines and constructions companies is
the SmartCap. The SmartCap was created to prevent accidents. It measures truck driver fatigue
levels by monitoring their brain activity.
When it picks up driver fatigue, an alarm will trigger to stop the driver and also let their manager know
of the event. The possibilities to use this data go even further than just sounding alarms.
If you have a lot of drivers, you can use machine learning to predict where and when they are likely to
get tired. This also helps you improve schedules, routes and safety practices. You’ll know which times
and areas are high risk for fatigue.
Libelium Smart Water Sensor

4. Sensors & Devices

Advances in sensor technology have made streaming real-time data easier than ever. Temperature,
flow, pressure and humidity sensors have become big sources of industrial IoT data.
Sensors like this one from Libelium simplify remote water quality monitoring.
Process industries produce waste water that could contaminate drinking water if procedures aren’t
followed. Contamination does damage to more than the environment. It often results in a PR disaster
for the company responsible.
By monitoring water quality, you can respond to contamination faster than ever before.
But what if you could predict the contamination before it happened? That’s what the next type of data
source is for.
NYC Open Data Project

5. Open & Web Data

What’s the most common example of using open and web data? It’s usually how to improve customer
service by using social media posts. You employ a sentiment analysis algorithm and respond to negative
posts quicker.
But in this post, we’re going to cover an industrial story that builds on the water contamination
example.
Here’s how you can use web data to prevent waste water in effluent dams from overflowing and killing
cows on the farm next door.
Using online weather services, you can predict when effluent dams are likely to overflow. Which means
they are likely to contaminate water in the surrounding area.
Combine that with map data and you can also predict which specific reservoirs are in danger. This means
you can take preemptive action and prevent the contamination from happening.
Open data sources aren’t limited to weather, traffic and maps. You can also use open data from places
like the NYC Open Data project.
Thermal image captured with a drone courtesy of JSE Engineering

6. Media
Smartphones have made it possible to get real-time access to photos, videos and audio from the field.
But in industrial cases, we can go beyond using smartphones to upload a picture of a broken machine.
One way to use media as a data source in oil and gas is to stream real-time infrared images when
inspecting flare stacks. Flare systems need to be inspected regularly for fouling and corrosion.
By using a UAV to do the inspection, you can get information without interrupting operations. You also
won’t be putting workers in danger.
Keep an eye out for a more in-depth use case we’ll be publishing about this soon.
Image from ArcGIS maps

7. Location
Location data could come from mobile devices, location beacons, GIS systems or even drones (UAV’s).
You could combine GPS data from a vehicle with traffic reports to optimize your delivery routes in real-
time. Or you could place track-and-trace sensors on expensive mobile assets that often get stolen or
misplaced.
But to prove how powerful the use of real-time location data can be, let’s take the example of avoiding
accidents with mining vehicles.
Mining trucks accidents are often fatal. Like this accident in 2013, where a contractor’s Toyota Land
Cruiser collided with a loaded dump truck weighing 380 tons.
Because the truck driver is seated in such an elevated position, it is often hard to see what’s happening
directly in front of him.
Streaming real-time data from location beacons can help prevent fatal accidents like these. When a
vehicle passes a beacon, the IoT application can automatically check whether the vehicle has the correct
clearance certificate.
You can also add GPS data displays (similar to radars in aircraft) to show truck drivers where light
vehicles are around them.

Conclusion
There’s more to industrial IoT than just using machine data for predictive maintenance.
By using and combining these 7 types of industrial IoT data sources, you can enable smarter decision
making and faster responses across your organization.
You’ll see the results in your bottom line, customer happiness and your safety record.

Machine to Machine Communication (M2M) in IoT

The Internet of things (IoT) has challenges that are different from the traditional Internet in a different
massive influx of data and unpredictable network conditions. On the other hand, software-defined
networking (SDN) is a promising approach to control the network in a unified using rule-based
management, The abstractions provided by SDN enable holistic control or network using high-level
policies, without being concerned about the low-level configuration is Hemoe, it is advantageous to
address the heterogeneity and application-specifics IoT. Software-defined wide-area networking (SD-
WAN), has emerged in recent years with the aim to simplify all of this complexity and help evolve
enterprise networks into more flexible programmable architectures that can meet the changing
expectations of users, requirements of

The term "machine-to-machine" communication technology is used to describe any form of connection
between two devices that don't require human assistance. M2M cornerstone of the IoT. The Internet of
Things is a system of devices with unique identifiers (known as UID) capable of transmitting information
over a network, IoT requires no human-to-human or human-to-machine interaction. Now IoT is widely
used in industries like the automotive (autonomous car, vehicle-to-vehicle communication), logistics and
supply (supply chain tracking), manufacturing (warehouse management), banking (connected branches),
and so on. While M2M enables device-to-device communication, the Internet of Things allows multiple
machines to design a connected data network.

What is Machine-to-Machine Communication (M2M)

Machine to Machine or M2M is like two machines communicating or exchanging data without human
interaction. M2M includes serial connection, powerline connection (PLC), and wireless connection. Or
we can say that M2M communication is like cellular communication for embedded devices. IoT and
M2M are almost synonymous. The exception is that IoT prefers wireless. communication and M2M
prefer to any 2 machines - wireless or wired communication with one another According to Forbes,
M2M is a widely increasing type.of.connected device technology in the market because
M2M.technology can connect- millions of devices within a single network. M2M network is very similar
to LAN or WAN but is exclusively used to allow machines and sensors. and control to communicate.
Artificial Intelligence and Machine Learning provide the communication between systems, allowing
them to make their own autonomous choices. M2M technology was first introduced in Industrial and
Manufacturing where other technologies such as SCADA (a principle of the remote monitoring system.
that transmits data from a device into a program and presents it in the form of insights) and remote
monitoring helped remoting control and manage data from equipment. M2M is found in other areas like
healthcare, business, and insurance. M2M is also the foundation for IoT. The first use-of M2M
communication is credited to Theodore Paraskevakos, who invented this technology related to the
transmission of data over telephone lines, the basis for modern-day caller-ID.

M2M communication is a point to point communication that allows the network to transmit
information via public networking technologies such as Ethernet and cellular networks. Sensor telemetry
is one of the applications of M2M. Businesses are using M2M to remotely monitor factors such as
temperature, energy consumption, moisture, pressure, etc. The second example of M2M is.ATM. ATM's
internal computer is continually communicating with a host computer that routes appropriate banks and
accounts. The bank sends back approval codes through the host computer; allowing transactions to be
completed. The entire transaction happens remotely and without any human interaction on the bank's
side. Machine communication efficiently, automatically allowing transactions to be authorized in
seconds.
The main purpose of machine-to-machine technology is to tap into sensor data and transmit it to a
network. Unlike SCADA or other remote monitoring tools, M2M systems often use public networks and
access methods -- for example, cellular or Ethernet - to make it more cost-effective. The main
components of an M2M system include sensors and RFID. a Wi-Fi or cellular communications link, and
autonomic computing software programmed to help a network device interpret data and make
decisions. These M2M applications translate the data, which can trigger preprogrammed, automated
actions.

The benefits of M2M

Reduced costs by minimizing equipment maintenance and downtime.

Boosted revenue by revealing new business opportunities for servicing products in the field.
Improved customer service by proactively monitoring and servicing equipment before it fails or only
when it is needed.

Fig. Machine-to-Machine Communication (M2M)

Features of M2M

Low power consumption, in an effort to improve the system's ability to service M2M applications.
effectively
A network operator that provides packet-switched service
Monitoring abilities that provide the functionality to detect events.
Time tolerance, meaning data transfers can be delayed.
Time control, meaning data can only be sent or received at specific predetermined periods.
Location-specific triggers that alert or wake up devices when they enter a particular area.
The ability to continually send and receive small amounts of data.

Requirements of M2M
According to the European Telecommunications Standards Institute (ETSI), requirements of an M2M
system include:
Scalability - The M2M system should be able to continue to function efficiently more connected objects
are added.
Anonymity - The M2M system must be able to hide the identity of M2M devices when requested,
subject to regulatory requirements.
Logging - M2M systems must support the recording of important events, such as failed installation
attempts, service not operating, or the occurrence of faulty information. The logs should be available by
request.
M2M Application Communication Principles - M2M systems should enable communication between
M2M applications in the network and the M2M device or gateway using communication techniques,
such as short message service (SMS) and IP Connected devices should also be able to communicate with
each other in a peer-to-peer (P2P) manner.
Delivery Methods - The M2M system should support unicast, anycast, multicast, and broadcast
communication modes, with the broadcast being replaced by multicast or anycast whenever possible to
minimize the load on the communication network.
Message Transmission Scheduling - M2M systems must be able to control network access and
messaging schedules and should be conscious of M2M application scheduling delay tolerance.
Message Communication Path Selection - Optimization of the message communication paths within an
M2M system must be possible and based on policies like transmission failures, delays when other paths
exist, and network costs.

M2M Security

Machine-to-machine systems face a number of security issues, from unauthorized access to wireless
intrusion to device hacking. Physical security, privacy, fraud, and the exposure of mission-critical
applications must also be considered. Typical M2M security measures include making devices and
machines tamper-resistant, embedding security into the machines, ensuring communication security
through encryption, and securing back-end servers, among others. Segmenting M2M devices onto their
own network and managing device identity, data confidentiality and device availability can also help
combat M2M security risks.

M2M Standards

Machine-to-machine technology does not have a standardized device platform, and many M2M systems
are built to be task- or device-specific. Several key M2M standards, many of which are also used in IoT
settings, have emerged over the years, including:
OMA LightweightM2M, a device management protocol
MQTT, a messaging protocol
TR-069 (Technical Report 069), an application layer protocol
HyperCat, a data discovery protocol
OneM2M, a communications protocol
Google Thread, a wireless mesh protocol
AllJoyn, an open-source software framework
 Unit -2
Topics to be covered

Machine-to-machine (M2M), SDN (software defined networking) and NFV (network function
virtualization) for IOT, data storage in IOT, IOT Cloud Based Services.
-----------------------------------------------------------------------------------------------------------------------------
-----------------

Machine-to-machine (M2M)
 Machine to machine (M2M) is a broad label that can be used to describe any
technology that enables networked devices to exchange information and perform
actions without the manual assistance of humans. M2M communication is often used
for remote monitoring. In product restocking, for example, a vending machine can
message the distributor when a particular item is running low. M2M communication
is an important aspect of warehouse management, remote control, robotics, traffic
control, logistic services, supply chain management, fleet management and
telemedicine.

 It forms the basis for a

concept known as the Internet of Things (IoT). Key components of an M2M system
include sensors, RFID, a Wi-Fi or cellular communications link and autonomic
computing software programmed to help a networked device interpret data and
make decisions. The most well-known type of M2M communication is telemetry,
which has been used since the early part of the last century to transmit operational
data. Pioneers in telemetric first used telephone lines and later, on radio waves -- to
 transmit performance measurements gathered from monitoring instruments in
remote locations. The Internet and improved standards for wireless technology have
expanded the role of telemetry from pure science, engineering and manufacturing to
everyday use in products like home heating units, electric meters and Internet-
connected appliances. Products built with M2M communication capabilities are often
marketed to end users as being smart.

Fig. 2.1 M2M Communication

SDN (software defined networking)-SDN deployment will enable Internet of Things devices
to share network resources efficiently and reliably, and further cut hardware investment, but
the possibilities are still emerging. Software-defined networking will meet the Internet of
Things (IoT) at the crossroads of VPN exhaustion, uptime challenges and limited network
resources. The expected result is that SDN will help drive the expansion of IoT-enabled
devices, enable more efficient network resource sharing and improve IoT service-level
agreements (SLAs).
SDN Benefits-SDN brings three important capabilities to IoT:
 Centralization of control through software that has complete knowledge of the
network, enabling automated, policy-based control of even massive, complex
networks. Given the huge potential scale of IoT environments, SDN is critical in
making them simple to manage.

 Abstraction of the details of the many devices and protocols in the network, allowing
IoT applications to access data, enable analytics and control the devices, and add new
sensors and network control devices, without exposing the details of the underlying
infrastructure. SDN simplifies the creation, deployment and ongoing management of
the IoT devices and the applications that benefit from them.
  The flexibility to tune the components within the IoT (and manage where data is
stored and analyzed) to continually maximize performance and security as business
needs and data flows change. IoT environments are inherently dispersed with many
end devices and edge computing. As a result, the network is even more critical than in
standard application environments. “DN’s ability to dynamically change network
behavior based on new traffic patterns, security incidents and policy changes will
enable IoT environments to deliver on their promise.

Features of SDN-
 SDN will make it easier to find and fight security threats through the improved
visibility they provide into network traffic right to the edge of the network. They also
make it easy to apply automated policies to redirect suspicious traffic to, for example,
a honey net where it can be safely examined. By making networking management less
complex, SDN allows IT to set and enforce more segmented access controls.SDN can
provide a dynamic, intelligent self-learning layered model of security that provides
walls within walls and ensures people can only change the configuration of the
devices they’re authorized to “touch.” This is far more useful than the traditional
“wall” around the perimeter of the network, which won’t work with the IoT because
of its size and the fact the enemy is often inside the firewall, in the form of
unauthorized actors updating firmware on unprotected devices.
 SDN will allow IT to effectively program the network to make automatic, real-time
decisions about traffic flow. They will allow the analysis of not only sensor data, but
data about the health of the network, to be analyzed close to the network edge to
give IT the information it needs to prevent traffic jams and security risks. The
centralized configuration and management of the network, and the abstraction of
network devices, also makes it far easier to manage applications that run on the edge
of the IoT.
 For example, SDN will allow IT to fine-tune data aggregation, so data that is less
critical is held at the edge and not transmitted to core systems until it won’t slow
critical application traffic. This edge computing can also perform fast, local analysis
and speed the results to the network core if the analysis indicates an urgent situation,
such as the impending failure of a jet engine.

NFV (network function virtualization) for IOT-

 Utilizing NFV (network function virtualization) capabilities is one way to address the
IoT network challenges providing secure network resources for IoT. Network
functions virtualization (also Network function virtualization or NFV) is a network
architecture concept that uses the technologies of IT virtualization to virtualize entire
classes of network node functions into building blocks that may connect, or chain
together, to create communication services.
 NFV relies upon, but differs from, traditional server-virtualization techniques, such as
those used in enterprise IT. A virtualized network function, or VNF, may consist of one
or more virtual machines running different software and processes, on top of
standard high-volume servers, switches and storage devices, or even cloud computing
 infrastructure, instead of having custom hardware appliances for each network
function.
 For example, a virtual session border controller could be deployed to protect a
network without the typical cost and complexity of obtaining and installing physical
network protection units. Other examples of NFV include virtualized load balancers,
firewalls, intrusion detection devices and WAN accelerators.
The NFV framework consists of three main components-
 Virtualized network functions (VNFs) are software implementations of network
functions that can be deployed on a network functions virtualization
infrastructure (NFVI).

 Network functions virtualization infrastructure (NFVI) is the totality of all hardware

and software components that build the environment where VNFs are deployed. The
NFV infrastructure can span several locations. The network providing connectivity
between these locations is considered as part of the NFV infrastructure.
 Network functions virtualization management architectural framework (NFV-MANO
Architectural Framework) is the collection of all functional blocks, data repositories
used by these blocks, and reference points and interfaces through which these
functional blocks exchange information for the purpose of managing and
orchestrating NFVI and VNFs.

Software defined networking (SDN) and Network Virtualization (NV):

 It is two of the most prominent technologies to serve as key enablers for the IoT
networks of the near future. The main idea behind SDN is to separate the control
plane (where the logical procedures supporting the networking protocols are
executed and all the relevant decisions are taken) from the data plane (where the
forwarding of packets on the most suitable interface towards the intended
destination is executed).
 The main entity behind this separation is the controller, which communicates with
the network applications through the so-called northbound interface and translates
their requirements into appropriate network decisions. The controller also
communicates with the network switches that forward packets according to the
controller-installed rules. This way, SDN provides increased possibilities to smartly
route traffic, for example to balance the load over the network or to exploit
underutilized network resources in an optimal way, thereby alleviating the burden on
the network by the data onslaught of IoT.
 The term network virtualization concerns a network that allows multiple service
providers to form multiple separate and isolated virtual networks by sharing physical
resources provided by one or more different physical network infrastructure
providers.SDN (software defined networking) is another element that works in combination
with NFV while creating IoT network infrastructure. NFV in combination with SDN enable
 network to utilize distributed intelligence capacity to analyze and manage traffic flows across
the network. NFV enables SPs to assemble and provide cost effective and secure IoT
networks along with ISV partners. The complexity part can be handled with effective
implementation of NFV capabilities with IoT network.

Relevance of NFV in IoT System-NFV can play a crucial role in achieving the goal with IoT
network combining both hardware and software network features in a single virtual network.
NFV helps accelerate the deployment of new services, operations, and maintenance of a
network allowing high level of network optimization. It brings multiples benefits to service
operators and service providers including ROI. The relevance of NFV lies with the promise of
benefits across network architecture.

NFV to Enhance IoT Networking Capacity-NFV leverages couple of IT technologies to build

flexible and agile IoT network such as virtualization, standard servers, and open software. It
distributes intelligence throughout the IoT network enabling real time analytics and business
intelligence. NFV creates menu for virtual network functions (VNFs) that includes gateways,
mobile core, deep packet inspection (DPI), security, routing, and traffic management that
helps delivering customized network services for IoT. Conversely IoT drives NFV opportunity
for service providers too financially and technologically.

Data storage in IOT-The Internet of Things is creating an enormous amount of data. To

manage, access, and make use of this data, digital storage becomes a critical factor. Data
management is a broad concept referring to the architectures, practices, and procedures for
proper management of the data lifecycle needs of a certain system. In the context of IoT,
data management should act as a layer between the objects and devices generating the data
and the applications accessing the data for analysis purposes and services. The devices
themselves can be arranged into subsystems or subspaces with autonomous governance and
internal hierarchical management. The functionality and data provided by these

subsystems is to be made available to the IoT network, depending on the level of privacy
desired by the subsystem owners.
 IoT data has distinctive characteristics that make traditional relational-based
database management an obsolete solution. A massive volume of heterogeneous,
streaming and geographically-dispersed real-time data will be created by millions of
diverse devices periodically sending observations about certain monitored
phenomena or reporting the occurrence of certain or abnormal events of interest .
 Periodic observations are most demanding in terms of communication overhead and
storage due to their streaming and continuous nature, while events present time-
strain with end-to-end response times depending on the urgency of the response
required for the event. Furthermore, there is metadata that describes “Things” in
addition to the data that is generated by “Things”; object identification, location,
processes and services provided are an example of such data. IoT data will statically
 reside in fixed- or flexible-schema databases and roam the network from dynamic and
mobile objects to concentration storage points. This will continue until it reaches
centralized data stores. Communication, storage and process will thus be defining
factors in the design of data management solutions for IoT.
 A data management framework for IoT is presented that incorporates a layered,
data-centric, and federated paradigm to join the independent IoT subsystems in an
adaptable, flexible, and seamless data network. In this framework, the “Things” layer
is composed of all entities and subsystems that can generate data. Raw data, or
simple aggregates, are then transported via a communications layer to data
repositories. These data repositories are either owned by organizations or public, and

they can be located at specialized servers or on the cloud.

Organizations or individual users have access to these repositories via query and
federation layers that process queries and analysis tasks, decide which repositories
hold the needed data, and negotiate participation to acquire the data. In addition,
real-time or context-aware queries are handled through the federation layer via
 
 a sources layer that seamlessly handles the discovery and engagement of data
sources. The whole framework therefore allows a two-way publishing and querying of
data. This allows the system to respond to the immediate data and processing
requests of the end users and provides archival capabilities for later long-term
analysis and exploration of value-added trends.

IOT Data Management-Traditional data management systems handle the storage, retrieval,
and update of elementary data items, records and files. In the context of IoT, data
management systems must summarize data online while providing storage, logging, and
auditing facilities for offline analysis. This expands the concept of data management from
offline storage, query processing, and transaction management operations into online-offline
communication/storage dual operations. We first define the data lifecycle within the context
of IoT and then outline the energy consumption profile for each of the phases in order to
have a better understanding of IoT data management.

IOT Data Lifecycle-The lifecycle of data within an IoT system proceeds from data
production to aggregation, transfer, optional filtering and preprocessing, and finally to
storage and archiving. Querying and analysis are the end points that initiate (request) and
consume data production, but data production can be set to be pushed to the IoT consuming
services. Production, collection, aggregation, filtering, and some basic querying and
preliminary processing functionalities are considered online, communication- intensive
operations. Intensive preprocessing, long-term storage and archival and in-depth
processing/analysis are considered offline storage-intensive operations.
 Fig 2.2 data Production

Storage operations aim at making data available on the long term for constant
access/updates, while archival is concerned with read-only data. Since some IoT systems may
generate, process, and store data in-network for real-time and localized services, with no
need to propagate this data further up to concentration points in the system, edges that
combine both processing and storage elements may exist as autonomous units in the cycle. In
the following paragraphs, each of the elements in the IoT data lifecycle is explained.

 Querying: Data-intensive systems rely on querying as the core

process to access and retrieve data. In the context of IoT, a query can be issued either
to request real-time data to be collected for temporal monitoring purposes or to
retrieve a certain view of the data stored within the system. The first case is typical
when a (mostly localized) real-time request for data is needed. The second case
 represents more globalized views of data and in-depth analysis of trends
and patterns.
 Production: Data production involves sensing and transfer of data by the “Things”
within the IoT framework and reporting this data to interested parties periodically (as
in a subscribe/notify model), pushing it up the network to aggregation points and
subsequently to database servers, or sending it as a response triggered by queries
that request the data from sensors and smart objects. Data is usually time-stamped
and possibly geo-stamped, and can be in the form of simple key-value pairs, or it may
contain rich audio/image/video content, with varying degrees of
complexity in- between.
 Collection: The sensors and smart objects within the IoT may store the data for a
certain time interval or report it to governing components. Data may be collected at
concentration points or gateways within the network where it is further filtered and
processed, and possibly fused into compact forms for efficient transmission. Wireless
communication technologies such as Zigbee, Wi- Fi and cellular are used by objects to
send data to collection points.
 Aggregation/Fusion: Transmitting all the raw data out of the network in real-time is
often prohibitively expensive given the increasing data streaming rates and the
limited bandwidth. Aggregation and fusion techniques deploy summarization and
merging operations in real-time to compress the volume of data to be stored
and transmitted.
 Delivery: As data is filtered, aggregated, and possibly processed either at the
concentration points or at the autonomous virtual units within the IoT, the results of
these processes may need to be sent further up the system, either as final responses,
or for storage and in-depth analysis. Wired or wireless broadband communications
may be used there to transfer data to permanent data stores.
 Preprocessing: IoT data will come from different sources with varying formats and
structures. Data may need to be preprocessed to handle missing data, remove
redundancies and integrate data from different sources into a unified schema before
being committed to storage. This preprocessing

is a known procedure in data mining called data cleaning. Schema integration does
not imply brute- force fitting of all the data into a fixed relational (tables) schema, but
rather a more abstract definition of a consistent way to access the data without
having to customize access for each source's data format(s). Probabilities at different
levels in the schema may be added at this phase to IoT data items in order to handle
uncertainty that may be present in data or to deal with the lack of trust that may exist
in data sources.
 Storage/Update—Archiving: This phase handles the efficient storage and
organization of data as well as the continuous update of data with new information as
it becomes available. Archiving refers to the offline long-term storage of data that is
 not immediately needed for the system's ongoing operations. The core of centralized
storage is the deployment of storage structures that adapt to the various data types
and the frequency of data capture. Relational database management systems are a
popular choice that involves the organization of data into a table schema with
predefined interrelationships and metadata for efficient retrieval at later stages.
NoSQL key-value stores are gaining popularity as storage technologies for their
support of big data storage with no reliance on relational schema or strong
consistency requirements typical of relational database systems. Storage can also be
decentralized for autonomous IoT systems, where data is kept at the objects that
generate it and is not sent up the system. However, due to the limited capabilities of
such objects, storage capacity remains limited in comparison to the centralized
storage model.
 Processing/Analysis: This phase involves the ongoing retrieval and analysis
operations performed and stored and archived data in order to gain insights into
historical data and predict future trends, or to detect abnormalities in the data that
may trigger further investigation or action. Task-specific preprocessing may be
needed to filter and clean data before meaningful operations take place. When an IoT
subsystem is autonomous and does not require permanent storage of its data, but
rather keeps the processing and storage in the network, then in-network processing
may be performed in response to real-time or localized queries.

Data Management Framework for IOT-Most of the current data management proposals are
targeted to WSNs, which are only a subset of the global IoT space, and therefore do not
explicitly address the more sophisticated architectural characteristics of IoT.
 WSNs are a mature networking paradigm whose data management solutions revolve
mainly around in-network data processing and optimization. Sensors are mostly of
stationary, resource- constrained nature, which does not facilitate sophisticated
analysis and services.
 The main focus in WSN-based data management solutions is to harvest real-time
data promptly for quick decision making, with limited permanent storage capacities
for long-term usage. This represents only a subset of the more versatile IoT system,
which aims at harnessing the data available from a variety of sources; stationary and
mobile, smart and embedded, resource- constrained and resource-rich, real-time
and archival.
 The main focus of IoT-based data management therefore extends the provisions
made for WSNs to add provisions of a seamless way to tap into the volumes of
heterogeneous data in order to find interesting global patterns and
strategic opportunities.

IOT Cloud Based Services-As these devices start to become connected, we need a place to
send, store, and process all of the information. Setting up your own in-house system isn’t
practical anymore. The cost of maintaining, upgrading and securing a system is just too high,
and there are some great services available.
  Amazon Web Services IOT Platform-Amazon dominates the consumer cloud market.
They were the first to really turn cloud computing into a commodity way back in
2004. “ince then they’ve put a lot effort into innovation and building features, and
probably have the most comprehensive set of tools available.

 Microsoft Azure IoT Hub-Microsoft is taking their Internet of Things cloud services
very seriously. They have cloud storage, machine learning, and IoT services, and have
even developed their own operating system for IoT devices. This means they intend to
provide a complete IoT solution provider.
 IBM Watson IoT Platform-IBM is another IT giant trying to set itself up as an Internet
of Things platform authority. They try to make their cloud services as accessible as
possible to beginners with easy apps and interfaces. You can try out their sample apps
to get a feel for how it all works. You can also store your data for a specified period, to
get historical information from your connected devices.
 Google Cloud Platform-Search giant Google is also taking the Internet of Things very
seriously. They claim that Cloud Platform is the best place to build IoT initiatives,
taking advantage of Google’s heritage of web-scale processing, analytics, and
machine intelligence.

-----------------------------------------------------------------------------------------------------------------------------
-----------

Unit -3
Topics to be covered
Design Principles for Web Connectivity: Web Communication Protocols for connected devices,
Message Communication Protocols for connected devices, SOAP, REST, HTTP Restful and Web
Sockets. Internet Connectivity Principles: Internet Connectivity, Internet based
communication, IP addressing in IOT, Media Access control.
-----------------------------------------------------------------------------------------------------------------------------
--
Web Communication Protocols for connected devices-The protocols are used for
communication between machines or between a machine and server. Due to constraints in
processing capabilities and the low power requirements of IoT devices (which are generally
meant to be deployed in environments with constant battery power) with limited bandwidth
capabilities, a need was felt for dedicated standards and protocols especially designed for
IoT. Since those who manufacture IoT devices and those who create the IoT platforms are
different, this required industry standards and protocols that were not high on power
consumption, bandwidth usage, or processing power and could be adopted easily by all IoT
players— hardware manufacturers, software developers or cloud solutions/service
providers.

List of IoT communication protocols:



CoAP (Constrained Application Protocol)-Constrained Application Protocol (CoAP) is an

Internet application protocol for constrained devices (defined in RFC 7228). It enables
constrained devices to communicate with the wider Internet using similar protocols. CoAP is
designed for use between devices on the same constrained network, between devices and
general nodes on the Internet, and between devices on different constrained networks
joined by the Internet. It is an application layer protocol designed for network constrained
IoT devices like wireless sensor network nodes, and is often termed the lightweight version
of HTTP with support for REST APIs. It can run on most devices that support UDP or a
UDP analogue.

 Bluetooth and Bluetooth Low Energy-While MQTT and CoAP are infrastructure-
independent, which means that it doesn’t matter whether you’re connected to a wired or a
wireless network, Bluetooth provides only wireless communication over radio frequency
(2.4GHz spectrum in the ISM band) using an industry standard that was initially used to share
files between mobile phones and is now powerful enough to play music (Advanced Audio
Distribution Profile/A2DP), stream data, or build
your next IoT device. Bluetooth, generally, is divided into three categories.
o Bluetooth Classic: This is meant for high data rate applications like streaming audio
wirelessly.
o Bluetooth Smart or Low Energy/BLE: This is meant for low powered battery-operated
devices that stream low packets of data.
o Bluetooth SmartReady: These are essentially the ‘hub’ devices such as computers,
smartphones, etc. They support both the ‘classic’ and ‘smart’ devices.
Bluetooth is a sophisticated ad hoc networking protocol, and is now especially designed from
the ground up for IoT. It provides a stable connection and communication channel, which is
extremely low profile and low powered. An obvious example is fitness trackers, which even
though powered on throughout the day, can last for months on a single charge or run on a
coin cell battery, all thanks to BLE (Bluetooth Low Energy). Bluetooth Classic has fixed
profiles like UART over Bluetooth class and A2DP class for audio streaming. On the other
hand, Bluetooth Low Energy provides GATT or Generic Attribute Profile, which allows users
to define their own

profile using Bluetooth, like in the case of a heart rate monitor. BLE is extremely flexible and
useful in the IoT space..
Message Communication Protocols for connected devices:
 MQTT (Message Queue Telemetry Transport)-It was created about 15 years back for
monitoring remote sensor nodes, and is designed to conserve both power and memory. It is
based on the ‘Publish Subscribe’ communication model, where a broker is responsible for
relaying messages to MQTT clients. This allows multiple clients to post messages and receive
updates on different topics from a central server known as the MQTT broker. This is similar
to subscribing to a YouTube channel, where you get notified whenever a new video is
posted. Using MQTT, a connected device can subscribe to any number of topics hosted by an
MQTT broker.
SOAP-OAP (originally Simple Object Access Protocol) is a protocol specification for
exchanging structured information in the implementation of web services in computer
networks. Its purpose is to induce extensibility, neutrality and independence. It uses XML
Information Set for its message format, and relies on application layer protocols, most often
Hypertext Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP), for message
negotiation and transmission.
SOAP allows processes running on disparate operating systems (such as Windows and Linux)
to communicate using Extensible Markup Language (XML). Since Web protocols like HTTP
are installed and running on all operating systems, SOAP allows clients to invoke web
services and receive responses independent of language and platforms. SOAP provides the
Messaging Protocol layer of a web services protocol stack for web services. It is an XML-
based protocol consisting of three parts:
 an envelope, which defines the message
 
 structure and how to process it
 a set of encoding rules for expressing instances of application-defined datatypes
 a convention for representing procedure calls and responses

SOAP has three major characteristics:

 extensibility (security and Web Services Addressing are among the extensions under
development)
 neutrality (SOAP can operate over any protocol such as HTTP, SMTP, TCP, UDP, or Java
Message Service)
 independence (SOAP allows for any programming model)
As an example of what SOAP procedures can do, an application can send a SOAP request to a
server that has web services enabled—such as a real-estate price database—with the
parameters for a search. The server then returns a SOAP response (an XML-formatted
document with the resulting data), e.g., prices, location, features. Since the generated data
comes in a standardized machine-parsable format, the requesting application can then
integrate it directly.
The SOAP architecture consists of several layers of specifications for:
 Message format
 Message Exchange Patterns (MEP)
 Underlying transport protocol bindings
 Message processing models
 Protocol extensibility

REST-REST (Representational State Transfer) is an architectural style for developing web

services. REST is popular due to its simplicity and the fact that it builds upon existing systems
and features of the internet's HTTP in order to achieve its objectives, as opposed to creating
new standards, frameworks and technologies.

Advantages of REST-A primary benefit of using REST, both from a client and server's
perspective, is REST-based interactions happen using constructs that are familiar to anyone
who is accustomed to using the internet's Hypertext Transfer Protocol (HTTP).
An example of this arrangement is REST-based interactions all communicate their status
using standard HTTP status codes. So, a 404 means a requested resource wasn't found; a 401
code means the request wasn't authorized, a 200 code means everything is OK; and a 500
means there was an unrecoverable application error on the server. Similarly, details such as
encryption and data transport integrity are solved not by adding new frameworks or
technologies, but instead by relying on well-known Secure Sockets Layer (SSL) encryption
and Transport Layer Security (TLS).

Disadvantages of REST-The benefit of REST using HTTP constructs also creates restrictions,
however. Many of the limitations of HTTP likewise turn into shortcomings of the REST
architectural style. For example, HTTP does not store state-based information between
request-response cycles, which means REST-based applications must be stateless and any
state management tasks must be performed by the client.

HTTP Restful-In REST architecture, a REST Server simply provides access to resources and the
REST client accesses and presents the resources. Here each resource is identified by URIs/
Global IDs. REST uses various representations to represent a resource like Text, JSON and
XML. JSON is now the most popular format being used in Web Services.
HTTP Methods
The following HTTP methods are most commonly used in REST based architecture.
 GET − Provides a read only access to a resource.
 PUT − Used to create a new resource.
 DELETE − Used to remove a resource.
 POST − Used to update an existing resource or create a new resource.
 OPTIONS − Used to get the supported operations on a resource.

Restful Web Services-A web service is a collection of open protocols and standards used for
exchanging data between applications or systems. Software applications written in various
programming languages and running on various platforms can use web services to exchange
data over computer networks like the Internet in a manner similar to inter-process
communication on a single computer. This interoperability (e.g., between Java and Python,
or Windows and Linux applications) is due to the use of open standards. Web services based
on REST Architecture are known as Restful Web Services.

Web Sockets- WebSocket

is a computer communications protocol, providing full- duplex communication
channels over a single TCP connection. The WebSocket protocol was

standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being
standardized by the W3C.
WebSocket is a different TCP protocol from HTTP. Both protocols are located at layer 7
in the OSI model and, as such, depend on
TCP at layer 4. Although they are different, RFC 6455 states that WebSocket "is designed
to work over HTTP ports 80 and 443 as well as to support HTTP proxies and intermediaries"
thus making it compatible with the HTTP protocol. To achieve compatibility, the
WebSocket handshake uses the HTTP Upgrade header to change from the HTTP protocol to
the WebSocket protocol.

Internet Connectivity-It defines various concepts mentioned below:

Internet Service Providers (ISP)-Internet Service Provider (ISP) is a company offering access to
internet. They offer various services:
 Internet Access
 Domain name registration
 Dial-up access
 Leased line access
ISP Types- ISPs can broadly be classified into six categories as shown in the following diagram:

Fig 3.1 ISP Categories

Access Providers-They provide access to internet through telephone lines, cable Wi-Fi or fiber
optics.
Mailbox Provider-Such providers offer mailbox hosting services.
Hosting ISPS-Hosting ISPs offers e-mail, and other web hosting services such as virtual
machines, clouds etc.
Virtual ISPS-Such ISPs offer internet access via other ISP services.
Free ISPS-Free ISPs do not charge for internet services.
Connection Types-There exists several ways to connect to the internet. Following are these
connection types available:
 Dial-up Connection
 ISDN
 DSL
 Cable TV Internet connections
 Satellite Internet connections
 Wireless Internet Connections

Dial-up Connection-Dial-up connection uses telephone line to connect PC to the internet. It

requires a modem to setup dial-up connection. This modem works as an interface between
PC and the telephone line. There is also a communication program that instructs the modem
to make a call to specific number provided by an ISP.
Dial-up connection uses either of the following protocols:
 Serial Line Internet Protocol (SLIP)
 Point to Point Protocol (PPP)
The following diagram shows the accessing internet using modem:

Fig 3.2.1 Dial-up connections

ISDN-ISDN is acronym of Integrated Services Digital Network. It establishes the connection

using the phone lines which carry digital signals instead of analog signals.
There are two techniques to deliver ISDN services:
 Basic Rate Interface (BRI)
 Primary Rate Interface (PRI)
Key points:
 The BRI ISDN consists of three distinct channels on a single ISDN line: t1o 64kbps B
(Bearer) channel and one 16kbps D (Delta or Data) channels.
 The PRI ISDN consists of 23 B channels and one D channels with both have operating
capacity of 64kbps individually making a total transmission rate of 1.54Mbps.
The following diagram shows accessing internet using ISDN connection:

Fig 3.2.2 ISDN Connections

DSL-DSL is acronym of Digital Subscriber Line. It is a form of broadband connection as it

provides connection over ordinary telephone lines.
Following are the several versions of DSL technique available today:

 Asymmetric DSL (ADSL)

 Symmetric DSL (SDSL)
 High bit-rate DSL (HDSL)
 Rate adaptive DSL (RDSL)
 Very high bit-rate DSL (VDSL)
 ISDN DSL (IDSL)
All of the above mentioned technologies differ in their upload and download speed, bit
transfer rate and level of service.
The following diagram shows that how we can connect to internet using DSL technology:
 Fig 3.2.3 DSL Connections

Cable TV Internet Connection

Cable TV Internet connection is provided through Cable TV lines. It uses coaxial cable which is
capable of transferring data at much higher speed than common telephone line.
Key Points:
 A cable modem is used to access this service, provided by the cable operator.
 The Cable modem comprises of two connections: one for internet service and other for
Cable TV signals.
 Since Cable TV internet connections share a set amount of bandwidth with a group of
customers, therefore, data transfer rate also depends on number of customers using the
internet at the same time.
The following diagram shows that how internet is accessed using Cable TV connection:

Fig 3.2.4 Cable TV Connections

Satellite Internet Connection-Satellite Internet connection offers high speed connection to

the internet. There are two types of satellite internet connection: one way connection or
two way connection.
In one way connection, we can only download data but if we want to upload, we need a
dialup access through ISP over telephone line.
In two way connection, we can download and upload the data by the satellite. It does not
require any dialup connection.
The following diagram shows how internet is accessed using satellite internet connection:
 Fig 3.2.5 Satellite Connections

Wireless Internet Connection-Wireless Internet Connection makes use of radio frequency

bands to connect to the internet and offers a very high speed. The wireless internet
connection can be obtained by either Wi-Fi or Bluetooth.
Key Points:
 Wi-Fi wireless technology is based on IEEE 802.11 standards which allow the electronic
device to connect to the internet.
 Bluetooth wireless technology makes use of short-wavelength radio waves and
helps to create personal area network (PAN).

Internet based communication-In much of the world the Internet is becoming the primary
medium for communication in business. Internet communication tools save money in a
variety of ways. Email, instant messaging and social networking are all free. There are many
different kinds of Internet communications tool, such as email, VoIP, forums, online chat and
social networking among others. Using the latest tools and methods of communicating over
the Internet is essential for bringing your business into the modern age of communication
and marketing.

VoIP and Internet Telephony-It is common for voice communications to be carried out over
the Internet using voice over Internet protocol software. VoIP allows you to call a telephone
-- either a fixed or mobile phone -- over the Internet. This is often considerably cheaper than
calling from a telephone, particularly with international calls. One of the most popular
Internet telephony tools is Skype. With Skype and similar Internet telephony tools, you can
conduct free voice conversations between two computers.

 Email-The original Internet communication tool, email is still an essential tool every
business should have. In spite of this, with the rise of messaging through social networking
sites and instant messages, email is not quite as important as it used to be.
 Social Networking-Social networking is all about forming groups, sharing online content
and exchanging information. In addition to being a major part of social life in the modern
world, social networking is an invaluable tool for Internet marketing since it provides a user-
friendly and highly accessible platform upon which to exchange information on products and
services. For example, if someone likes an article on your business blog or website, he may
decide to share it with his friends over Facebook or Twitter.
 Forums-Forums, like email, have also been around since the dawn of the Internet. Forums
provide a place to exchange messages and participate in conversations. The main differences
from instant messaging are that forums are generally public and the communications are not
in real time. Forums and their regular posters and readers form communities that can be
valuable to your business.

IP addressing in IOT- We can connect Internet of Thing or device to the Internet. How we
connect depends ultimately on what we actually want to do with the device. Shown below is
a typical home network. This would normally consist of a router / firewall that connect to
your ISP (Internet Service Provider). The connection to your ISP could by via ADSL or
Ethernet using a fiber service for example.

Fig 3.3 IP addressing in Home Networks

When the home router connects to the ISP it will be assigned an IP address which is what is
used to communicate with servers or other service on the Internet. This is a public IP address
and is addressable by the internet. In the diagram above the public IP address is
111.246.59.246.
This is your public IP address you used to connect to the cactus.io server to view this
page.182.73.155.114
(If there is more than one IP then you might be connecting using a proxy server or VPN
service), be aware that this IP address will change every time that your home router is
rebooted or reconnects to the ISP. Some ISP's allow you to pay extra for a fixed IP address.
However most will not for home internet services.

Connect to a Web Server-When we enter a URL into our browser it will use a DNS server to
convert the name to an IP address. The DNS server would normally be provided by your ISP.
In the example above we are using cactus.io for the URL. The DNS server would then return
the IP address of 104.130.130.228. The browser will then try to connect to the server via the
router. The router will connect to the remote server using the public IP address assigned to
your router. The server hosting cactus.io will then send data back to your router using your
public ip address (111.246.59.246). The router will then transmit this data back to your PC
using the private IP address of 192.168.1.10.

Connect to an Internal IoT Device-We can connect to a web server running on our IoT device
by entering the IP address of http://192.168.1.45 into the browser URL. The connection will
be made in this case via the switch built into the home router. The switch knows what port
the IoT device is connected to and transmits and receives data via this port. The router has
no role in this network request as it's a private IP address and the PC and IoT device are on
the same network.

How to connect my device to the Internet

This all depends on the role of the device and we have the following options:
 Option 1) We access this device only on the home / business network
 Option 2) The device only connects to a local / remote server
 Option 3) We access this device from the Internet using a Static Public IP Address
 Option 4) We access this device from the Internet using a Dynamic Public IP Address
Option 1) Access this device only on the home / business network-In this scenario the IoT
device is configuring as a server. The easiest way is to assign a static IP address. This address
is coded into the sketch.

Fig 3.4 IP addressing in Business Network

When a client connects to the IoT device it passes through the switch and out to the device
it is connected to. No routing is required here.
Option 2) Device connects to a local / remote server-For this scenario the IoT device
initiates a connection to a local or remote server. This could be using a http REST POST or
configured as MQTT client. It could also be a custom connection method as long as it initiates
the connection to the remote service.
Because the device is creating the connection it allows us to use DHCP and a dynamically
assigned IP address.
 Fig 3.5 Client-Server Communication

In the diagram above two of the devices send a HTTP REST Post to a server in the cloud. If
the remote server accepts the connection and data it will generally respond with a 200 OK.
The client will then close the connection until the next post is sent.

Option 3) Access the Device from the Internet with Static Public IP Address
The world is running out of IPV4 IP addresses. This means ISP's are pretty strict on giving out
static IP addresses. It's much easier for them to use a dynamic pool of IP addresses to assign
to their clients.
Generally home internet services are not available with a static IP address. However you
might be able to pay extra for this functionality. Some business accounts are available with a
static IP address. The most common reason for wanting a static ip is for hosting a email
server.
In this diagram above we could use http://1.127.48.156 or http://1.127.48.156:49155 to
connect to the IoT server. In the first URL we do not specify a port number so the browser
will use the default port of 80. In the second URL we use the port 49155. By using a random
private port number we improve the security for our IoT server. If someone does a port scan
they will always check port 80 as it's a default. They might not bother scanning private port
numbers
If you have multiple IoT devices you can setup port forwarding on the router to recognize
different port numbers.

Option 4) Access the Device from the Internet with Dynamic Public IP Address-One of the
most common ways of dealing with a dynamic public (WAN) IP addresses is to use a Dynamic
DNS Service provider. Some of these services are free but most require a monthly payment.
Most routers these days support third party Dynamic DNS service providers. You configure
the router with the provider, username and password. When the router detects a WAN
interface IP address change it updates the DDNS service provider with the new IP details.
 Fig 3.7 Public IP Addressing

When you sign up with one of these providers you provide a domain name you would like to
use. In the example below the name we used is cactusio. This is a sub domain for dydns.com.
When we enter http://cactusio.dydns.com into the browser it will do a dnslookup on
cactusio.dydns.com. If it’s a valid domain it will respond with the IP address which just
happens to be the public (WAN) IP address of the home / office router.
 The office router will detect the data packet matches a record in the port forwarding table
and pass the data onto the IoT device using the static IP of 192.168.1.45. The IoT device will
respond with the appropriate html to view in the internet client browser.

Media Access control

In Layer 2 of a network, the Media Access Control (MAC) sub-layer provides addressing and
channel access control mechanisms that enable several terminals or network nodes to
communicate in a network.
The MAC sub-layer acts as an interface between the logical link control (LLC) Ethernet sub-
layer and Layer 1 (the physical layer). The MAC sub-layer emulates a full-duplex logi

communication channel in a multipoint network. This channel may provide unicast, multicast
or broadcast communication service. The MAC sub-layer uses MAC protocols to prevent
collisions. In Layer 2, multiple devices on the same physical link can uniquely identify one
another at the data link layer, by using the MAC addresses that are assigned to all ports on a
switch. A MAC algorithm accepts as input a secret key and an arbitrary-length message to be
authenticated, and outputs a MAC address.

Unit -4
Topics to be covered
Sensor Technology, Participatory Sensing, Industrial IOT and Automotive IOT, Actuator,
Sensor data Communication Protocols, Radio Frequency Identification Technology, Wireless
Sensor Network Technology.

-----------------------------------------------------------------------------------------------------------------------------
----------------

Sensor Technology
The Internet of Things (IoT) couldn’t exist without smart sensors, and the growing use of
smart technology is already transforming how manufacturers implement the IoT. Smart
sensors are also bringing more connectivity and analytics to the supply chain. There are
some things to know about how and why this is happening.

First, smart sensors are the indispensable enablers of the IoT and the industrial IoT. Smart
sensors, including radio frequency identification (RFID) tags, serve three broad purposes.
They identify items, locate them and determine their environmental conditions, all of which
have major implications for the supply chain and manufacturing. Smart sensors are
particularly useful in plants or warehouses because they can keep track of temperature and
humidity, log data for historical records and quality management, or be used as triggers for
alarms or process management.
Second, smart sensors impact the supply chain by being embedded in products, which can
help improve the manufacturing process or the products themselves. “ensors can live inside
products to create “smart products” and new revenue sources from the enhanced features.
They can also permeate the manufacturing process to monitor, control, and improve
operations, or be added to logistics to streamline how products are delivered. There are a
number of specific purposes of sensors, such as measuring temperature, humidity,
vibrations, motion, light, pressure and altitude. Companies will need to develop new
applications to take advantage of all the big data that the sensors are generating.

Third, the lower costs and more advanced capabilities of RFID tags are starting to enable
wider and more effective use. The cost of RFID, which has come down dramatically, is in
more than just the tag itself. To determine the true cost per use you have to include the
software applications and deployment costs. The combination of lowered costs for tags and
improved capabilities means that their value proposition has changed, and represents an
opportunity for enterprises to rethink RFID.

A sensor is a device that detects and responds to some type of input from the physical
environment. The specific input could be light, heat, motion, moisture, pressure, or any one
of a great number of other environmental phenomena. The output is generally a signal that
is converted to human-readable display at the sensor location or transmitted electronically
over a network for reading or further processing.
Here are a few examples of the many different types of sensors:
In a mercury-based glass thermometer, the input is temperature. The liquid contained
expands and contracts in response, causing the level to be higher or lower on the marked
gauge, which is human- readable.
An oxygen sensor in a car's emission control system detects the gasoline/oxygen ratio,
usually through a chemical reaction that generates a voltage. A computer in the engine reads
the voltage and, if the mixture is not optimal, readjusts the balance.
Motion sensors in various systems including home security lights, automatic doors and
bathroom fixtures typically send out some type of energy, such as microwaves, ultrasonic
waves or light beams and detect when the flow of energy is interrupted by something
entering its path.
A photo sensor detects the presence of visible light, infrared transmission (IR), and/or
ultraviolet (UV) energy.

Participatory Sensing - Participatory sensing is the process whereby individuals and

communities use ever- more-capable mobile phones and cloud services to collect and
analyze systematic data for use in discovery. The convergence of technology and analytical
innovation with a citizenry that is increasingly comfortable using mobile phones and online
social networking sets the stage for this technology to dramatically impact many aspects of
our daily lives.
1. Applications and Usage Models
One application of participatory sensing is as a tool for health and wellness. For example,
individuals can self-monitor to observe and adjust their medication, physical activity,
nutrition, and interactions. Potential contexts include chronic-disease management and
health behavior change. Communities and health professionals can also use participatory
approaches to better understand the development and effective treatment of disease.
The same systems can be used as tools for sustainability. For example, individuals and
communities can explore their transportation and consumption habits, and corporations can
promote more sustainable practices among employees.
In addition, participatory sensing offers a powerful “make a case” technique to support
advocacy and civic engagement. It can provide a framework in which citizens can bring to
light a civic bottleneck, hazard, personal-safety concern, cultural asset, or other data
relevant to urban and natural-resources planning and services, all using data that are
systematic and can be validated.
These different applications imply several different usage models. These models range from
public contribution, in which individuals collect data in response to inquiries defined by
others, to personal use and reflection, in which individuals log information about themselves
and use the results for personal analysis and behavior change. Yet across these varied
applications and usage models, a common workflow is emerging, as Figure 4.1 illustrates.
 Fig 4.1 Participatory Sensing Model Workflow
2. Essential Components
Ubiquitous Data Capture
While empirical data can be collected in a variety of ways, mobile phones are a special and,
perhaps, unprecedented tool for the job. These devices have become mobile computing,
sensing, and communication platforms, complete with image, audio, video, motion,
proximity, and location data capture and broadband communication, and they are capable
of being programmed for manual, automatic, and con-text-aware data capture.
Because of the sheer ubiquity of mobile phones and associated communication
infrastructure, it is possible to include people of all backgrounds nearly everywhere in the
world. Because these devices travel with us, they can help us make sustainable observations
on an intimately personal level. Collectively, they provide unmatched coverage in space and
time.
Leveraged Data Processing and Management
In some cases, the data collected with a mobile device are enough to reveal an interesting
pattern on their own. However, when processed through a series of external and cross-user
data sources, models, and algorithms, simple data can be used to infer complex phenomena
about individuals and groups. Mapping and other interactive capabilities of today's Web
enhance the presentation and interpretation of these patterns for participants. Many
applications will call for the comparison of current measures to past trends, so robust and
long term storage and management of this data is a central requirement.
The Personal Data Vault
A common feature uniting these applications is the highly individualized, and therefore
personal, nature of the data. By building mechanisms for protecting personal data directly
into the emerging participatory sensing architecture’ we can create a healthy marketplace of
content and services in which the individual has visibility and negotiating power with respect
to the use and disposition of his or her personal data streams. By specifying standard
mechanisms instead of standard policy, we enable support of diverse policies that are
tailored to particular applications and users - this is the narrow waist of this participatory-
sensing architecture. Without such architecture, critical applications will be encouraged to
create bundled, vertically integrated, non-interoperable, and nontransferable vehicles for
personal data streams, thereby making those streams opaque to their creators. By creating
such a user-transparent architecture that places individuals and communities at the locus of
control over information flow, we will simultaneously support participant rights and create a
healthier market for competitive services.
To support this function, we propose the personal data vault. It decouples the capture and
archiving of personal data streams from the sharing of that information. Instead of
individuals sharing their personal data streams directly with services, we propose the use of
secure containers to which only the individual has complete access. The personal data vault
would then facilitate the selective sharing of subsets of this information with various services
over time. Selective sharing may take the form of exporting filtered information from specific
times of day or places in space, or may import service computations to the data vault and
export resulting computational outputs. Essential to this scheme are tools to audit
information flows and support meaningful usage. Finally, legal consideration is essential to
protect and preserve the individual's control over his or her own data streams.

Industrial IOT - The IIoT is part of a larger concept known as the Internet of Things (IoT). The
IoT is a network of intelligent computers, devices, and objects that collect and share huge
amounts of data. The collected data is sent to a central Cloud-based service where it is
aggregated with other data and then shared with end users in a helpful way. The IoT will
increase automation in homes, schools, stores, and in many industries.
The application of the IoT to the manufacturing industry is called the IIoT (or Industrial
Internet or Industry 4.0). The IIoT will revolutionize manufacturing by enabling the
acquisition and accessibility of far greater amounts of data, at far greater speeds, and far
more efficiently than before. A number of innovative companies have started to implement
the IIoT by leveraging intelligent, connected devices in their factories.

Benefits of IIOT
The IIoT can greatly improve connectivity, efficiency, scalability, time savings, and cost
savings for industrial organizations. Companies are already benefitting from the IIoT through
cost savings due to predictive maintenance, improved safety, and other operational
efficiencies. IIoT networks of intelligent devices allow industrial organizations to break open
data silos and connect all of their people, data, and processes from the factory floor to the
executive offices. Business leaders can use IIoT data to get a full and accurate view of how
their enterprise is doing, which will help them make better decisions.

IIOT Protocols
One of the issues encountered in the transition to the IIoT is the fact that different edge-of-
network devices have historically used different protocols for sending and receiving data.
While there are a number of different communication protocols currently in use, such as
OPC-UA, the Message Queueing Telemetry Transport (MQTT) transfer protocol is quickly
emerging as the standard for IIoT, due to its lightweight overhead, publish/subscribe model,
and bidirectional capabilities.

Challenges of IIOT
Interoperability and security are probably the two biggest challenges surrounding the
implementation of IIoT. As technology writer Margaret Rouse observes, “A major concern
surrounding the Industrial IoT is interoperability between devices and machines that use
different protocols and have different architectures.” Ignition is an excellent solution for this
since it is cross-platform and built on open-source, IT-standard technologies.
Companies need to know that their data is secure. The proliferation of sensors and other
smart, connected devices has resulted in a parallel explosion in security vulnerabilities. This
is another factor in the rise of MQTT since it is a very secure IIoT protocol.

Future of IIOT
The IIoT is widely considered to be one of the primary trends affecting industrial businesses
today and in the future. Industries are pushing to modernize systems and equipment to
meet new regulations, to keep up with increasing market speed and volatility, and to deal
with disruptive technologies. Businesses that have embraced the IIoT have seen significant
improvements to safety, efficiency, and profitability, and it is expected that this trend will
continue as IIoT technologies are more widely adopted.
The Ignition IIoT solution greatly improves connectivity, efficiency, scalability, time savings,
and cost savings for industrial organizations. It can unite the people and systems on the plant
floor with those at the enterprise level. It can also allow enterprises to get the most value
from their system without being constrained by technological and economic limitations. For
these reasons and more, Ignition offers the ideal platform for bringing the power of
the IIoT into your enterprise.

Automotive IOT-With the number of networked sensors increasing across production,

supply chains and products, manufacturers are beginning to tap into a new generation of
systems that enables real-time, automatic interactions among machines, systems, assets and
things. The pervasiveness of connected devices is finding applicability across multiple
segments of manufacturing and “upply chain throughout the value chain. Following are the
functions provided by Automotive IOT:
 Ability to view the status of the Assets at anytime, Anywhere & Faster service response
from dealer.
 By hooking equipment into the IoT, original equipment manufacturers (OEMs) or dealers
could use that stream of data to adjust preventative maintenance schedules based on actual
wear and be able to better optimize uptime
 Understand, monitor, predict and control process variability
 Enhance equipment and process diagnostics capabilities
 IoT helps more hands-off way to track goods and the progress of work. RFID tags and
readers can play a role in this by allowing materials, locations, or tooling to essentially talk
with each other.
 Faster Response time and less operations cost for machine configuration requests that
could be services remotely

 Ability to view the entire population of connected products together marketing data and
product trends
& increased trouble shooting ability for Manufacturer’s tech support
 Real-time remote monitoring of performance
 Multi site monitoring improving the operational efficiency and reducing the site downtime
 Availability of real time data for the production environment and alerts generated to the
local administrators mobile phone reducing the clean room downtime
 Full manufacturing & SCM traceability
 Predictive Maintenance and quality

Information value loop

The suite of technologies that enables the Internet of Things promises to turn most any
object into a source of information about that object. This creates both a new way to
differentiate products and services and a new source of value that can be managed in its
own right. Realizing the IoT’s full potential motivates a framework that captures the series
and sequence of activities by which organizations create value from information: the
Information Value Loop.
 Fig 4.2 Information value loop

For information to complete the loop and create value, it passes through the loop’s stages,
each enabled by specific technologies. An act is monitored by
a sensor that creates information, that information passes through a network so that it can
be communicated, and standards—be they technical, legal, regulatory, or social—allows that
information to be aggregated across time and space. Augmented intelligence is a generic
term meant to capture all manner of analytical support, collectively used
to analyze information. The loop is completed via augmented behavior technologies that
either enable automated autonomous action or shape human decisions in a manner leading
to improved action.

Getting information around the Value Loop allows an organization to create value; how
much value is created is a function of the value drivers, which capture the characteristics of
the information that makes its way around the value loop. The drivers of information value
can be captured and sorted into the three categories: magnitude, risk, and time.

Actuator-An actuator is a component of a machine that is responsible for moving or

controlling a mechanism or system, for example by actuating (opening or closing) a valve; in
simple terms, it is a mover. An actuator requires a control signal and a source of energy. The
control signal is relatively low energy and may be electric voltage or current, pneumatic or
hydraulic pressure, or even human power. The supplied main energy source may be electric
current, hydraulic fluid pressure, or pneumatic (gas pressure). When the control signal is
received, the actuator responds by converting the energy into mechanical motion.
An actuator is the mechanism by which a control system acts upon an environment. The
control system can be simple (a fixed mechanical or electronic system), software-based (e.g.
a printer driver, robot control system), a human, or any other input.
In typical IoT systems, a sensor may collect information and route to a control center where
a decision is made and a corresponding command is sent back to an actuator in response to
that sensed input.

Fig 4.3 Sensor to Actuator Flow

There are many different types of sensors. Flow sensors, temperature sensors, voltage
sensors, humidity sensors, and the list goes on. In addition, there are multiple ways to
measure the same thing. For instance, airflow might be measured by using a small propeller
like the one you would see on a weather station. Alternatively, as in a vehicle measuring the
air through the engine, airflow is measured by heating a small element and measuring the
rate at which the element is cooling.

Communications Protocols
Sensor data Communication Protocols-Wireless sensors networks are networks of tiny,
battery powered sensor nodes with limited on –board processing storage and radio
capabilities. Nodes sense and send their reports towards a processing centre which is called
“sink”. The design of protocols and applications for such network has to be energy aware in
order to prolong the lifetime of the network, because the replacement of the embedded
batteries is a very difficult process once these nodes have been deployed. the regular nodes
sense the field, generate the data, and send them to associated nodes. Then the after
performing some processes transmit them to the BS in a multi-hop approach. Eventually the
user receives the data from the BS through the Internet.
Wireless sensor networks (WSNs) are composed of a huge number of sensor nodes. There
are many applications for WSNs and depending on the application, different types of sensors
are used, such as sensors measuring moisture, temperature, pressure and movement. WSNs
have themselves characteristics that make them different from other types of networks. One
for example is that the applicability of the networks is related to energy supply of the nodes,
so energy conservation is one of the most important challenges in these networks. Different
types of protocols for WSN are following:

Direct transmission protocols-Using a direct communication protocol, each sensor sends its
data directly
to the base station. If the base station is far away from the nodes, direct communication
will require a

large amount of transmit power from each node. This will quickly drain the battery of the
nodes and reduce the system lifetime. How- ever, the only receptions in this protocol occur
at the base station, so if either the base station is close to the nodes, or the energy required
receiving data is large, this may be an acceptable method of communication.
Minimum transfer energy protocols- In these protocols, nodes act as routers for other
nodes’ data in addition to sensing the environment. These protocols differ in the way the
routes are chosen. Some of these protocols only consider the energy of the transmitter and
neglect the energy dissipation of the receivers in determining the routes. Depending on the
real time costs of the transmit amplifier and the radio electronics, the total energy expended
in the system might actually be greater using MTE routing than direct transmission to the
base station.
Clustering protocol -A final conventional protocol for wireless networks is clustering, where
nodes are organized into clusters that communicate with a local base station, and these local
base stations transmit the data to the global base station, where it is accessed by the end-
user. This greatly reduces the distance nodes need to transmit their data, as typically the
local base station is close to all the nodes in the cluster. Thus, clustering appears to be an
energy-efficient communication protocol. However, the local base station is assumed to be a
high-energy node; if the base station is an energy-constrained node, it would die quickly, as
it is being heavily utilized. Thus, conventional clustering would perform poorly for our model
of micro sensor networks.
Genetic Algorithm- a genetic algorithm (GA) is used to create energy efficient clusters for
data dissemination in wireless sensor networks. A GA is used at the base
station, which provides energy efficient solutions to the optimizer. This provides the base
station with the ability to determine the best cluster formation that will give minimum
energy consumption during run time. The base station analyses the current network
condition and applies the GA after every iteration. The optimizer at the base station selects
the best solution based on the acquired knowledge through the GA fitness function. The
proposed fitness function is based on parameters such as energy consumption, number of
clusters, cluster size, direct distance to sink, and cluster distance. Upon completion of
iteration, the optimizer improves its decisions by receiving feedback, which is then used to
adjust the weights of the parameters of the fitness function for the next iteration
Hierarchical Cluster-Based Routing (HCR) Protocol- In HCR nodes self organize into clusters
and each cluster is managed by a set of associates called head-set. Using round-robin
technique, each associate acts as a cluster head (CH).[3] The sensor nodes transmit data to
their cluster heads, which transmit the aggregated data to the base station. Moreover, the
energy-efficient clusters are retained for a longer period of time; the energy-efficient clusters
are identified using heuristics-based approach.
Radio Frequency Identification Technology-Radio-frequency identification (RFID)
uses electromagnetic fields to automatically identify and track tags attached to objects. The
tags contain electronically stored information. Passive tags collect energy from a nearby RFID
reader's interrogating radio waves. Active tags have a local power source (such as a battery)
and may operate hundreds of meters from the RFID reader. Unlike a barcode, the tag need
not be within the line of sight of the reader, so it may be embedded in the tracked object.
RFID is one method for Automatic Identification and Data Capture (AIDC).
RFID tags are used in many industries, for example, an RFID tag attached to an automobile
during production can be used to track its progress through the assembly line; RFID-tagged
pharmaceuticals can be tracked through warehouses; and implanting RFID microchips in
livestock and pets allows for positive identification of animals.

Wireless Sensor Network Technology-Wireless sensor network (WSN) refers to a group of

spatially dispersed and dedicated sensors for monitoring and recording the physical
conditions of the environment and organizing the collected data at a central location. WSNs
measure environmental conditions like temperature, sound, pollution levels, humidity, wind,
and so on.
 These are similar to wireless ad hoc networks in the sense that they rely on wireless
connectivity and spontaneous formation of networks so that sensor data can be transported
wirelessly. Sometimes they are
called dust networks, referring to minute sensors as small as dust. WSNs are spatia
lly distributed autonomous sensors to monitor physical or environmental conditions, such

as temperature, sound, pressure, etc. and to cooperatively pass their data through the
network to a main locations. The more modern networks are bi-directional, also enabling
control of sensor activity. The development of wireless sensor networks was motivated by
military applications such as battlefield surveillance; today such networks are used in many
industrial and consumer applications, such as industrial process monitoring and control,
machine health monitoring, and so on.

A wireless sensor network (WSN) is a wireless network consisting of spatially distributed

autonomous devices using sensors to monitor physical or environmental conditions. A WSN
system incorporates a gateway that provides wireless connectivity back to the wired world
and distributed nodes (see Figure 1). The wireless protocol you select depends on your
application requirements. Some of the available standards include 2.4 GHz radios based on
either IEEE 802.15.4 or IEEE 802.11 (Wi-Fi) standards or proprietary radios, which are usually
900 MHz.

Fig 4.4 WSN Components, Gateway, and Distributed Nodes

Potential Applications-Engineers have created WSN applications for areas including health
care, utilities, and remote monitoring. In health care, wireless devices make less invasive
patient monitoring and health care possible. For utilities such as the electricity grid,
streetlights, and water municipals, wireless sensors offer a lower-cost method for collecting
system health data to reduce energy usage and better manage resources. Remote
monitoring covers a wide range of applications where wireless systems can complement
wired systems by reducing wiring costs and allowing new types of measurement
applications. Remote monitoring applications include:
 Environmental monitoring of air, water, and soil
 Structural monitoring for buildings and bridges
 Industrial machine monitoring
 Process monitoring
 Asset tracking

WSN System Architecture

Fig 4.5. WSN System Architecture

Wireless technology offers several advantages for those who can build wired and wireless
systems and take advantage of the best technology for the application. To do this, you need
flexible software architecture like the NI Lab VIEW graphical system design platform. Lab
VIEW offers the flexibility needed to connect a wide range of wired and wireless devices.

WSN Network Topologies-WSN nodes are typically organized in one of three types of
network topologies. In a star topology, each node connects directly to a gateway. In a cluster
tree network, each node connects to a node higher in the tree and then to the gateway, and
data is routed from the lowest node on the tree to the gateway. Finally, to offer increased
reliability, mesh networks feature nodes that can connect to multiple nodes in the system
and pass data through the most reliable path available. This mesh link is often referred to as
a router.
 Fig. 4.6. Common WSN Network Topologies

Components of a WSN Node-A WSN node contain several technical components. These
include the radio, battery, microcontroller, analog circuit, and sensor interface. When using
WSN radio technology, you must make important trade-offs. In battery-powered systems,
higher radio data rates and more frequent radio use consume more power. Often three
years of battery life is a requirement, so many of the WSN systems today are based on
ZigBee due to its low-power consumption.
The second technology consideration for WSN systems is the battery. In addition to long life
requirements, you must consider the size and weight of batteries as well as international
standards for shipping batteries and battery availability. The low cost and wide availability of
carbon zinc and alkaline batteries make them a common choice. To extend battery life, a
WSN node periodically wakes up and transmits data by powering on the radio and then
powering it back off to conserve energy. WSN radio technology must efficiently transmit a
signal and allow the system to go back to sleep with minimal power use. This means the
processor involved must also be able to wake power up, and return to sleep mode
efficiently. Microprocessor trends for WSNs include reducing power consumption while
maintaining or increasing processor speed. Much like your radio choice, the power
consumption and processing speed trade-off is a key concern when selecting a processor for
WSNs. This makes the x86 architecture a difficult option for battery-powered devices.
 Fig 4.7 WSN Sensor Node Components

Unit -5
Topics to be covered
IOT Design methodology: Specification -Requirement, process, model, service,
functional & operational view.IOT Privacy and security solutions, Raspberry Pi &
arduino devices. IOT Case studies: smart city streetlights control & monitoring.
-----------------------------------------------------------------------------------------------------------------------------
--

IoT Design methodology: Specification

It has two main perspectives:
1. IoT Strategy Execution-This perspective looks at IoT strategy from an
enterprise perspective, including IoT strategy definition, IoT opportunity
identification, IoT business case and IoT program management.
2. IoT Solution Delivery-This perspective looks at the individual IoT solution
and the related project. Note that it defines the interfaces to the related asset
and its organization, but usually excludes design and manufacturing of the
asset itself.
Following factors can also be considered while designing IoT product:
The IoT Expansion Card form factor is designed to be a cost-competitive solution
for several current and emerging market demands for host applications,
including:
• On-demand hardware applications — The same host application can be used
for different market segments by including unique expansion card solutions for
each segment. For example, a Wi-Fi / Bluetooth solution for one segment and an
environmental sensor for another segment.
• Electrical and feature compatibility across IoT technologies —Availability of
several data interfaces allows support for various IoT solutions. For example,
digital audio over PCM, application control and data transfer over USB, etc.
• Enables Configure/Built to Order
• Accommodates various PAN technologies, sensors, and other IoT applications
• Using the IoT Expansion Card’s modular design, all actors of the M2M value chain
can benefit.
• Host applications can, without requiring redesign, inherit new features and
interfaces for their products
• Technology specialists such as PAN, LPRF, Industrial Field buses or sensors can
bring their expansion cards to market
• System integrators and end customers can easily combine host applications and
expansion cards to fit their specialized needs

Requirement
Privacy is an essential implementation requirement. Supported by privacy laws,
almost all systems require secure communication to the cloud to ensure personal
data cannot be accessed or modified and liabilities are eliminated. Furthermore,
the management of devices and the data that appears in the cloud need to be
managed separately. Without this feature, users’ critical personal information is
not protected properly and available to anyone with management access.
 Fig .5.1 M2M System Architecture

In the system architecture diagram we show the two separate components

inside the cloud required for system management and application processing to
satisfy privacy laws. Both components may have separate billing options and can
run in separate environments. The management station may also include:
· System initialization
· Remote field service options (such as field upgrades, reset to default
parameters, and remote test)
· Control for billing purposes (such as account disable, account enable, and billing features)
· Control for theft purposes (the equivalent of bricking the device)
Given this type of architecture, there are additional protocols and programs that
should be considered:
· Custom developed management applications on cloud systems
· SNMP management for collections of sensor nodes
· Billing integration programs in the cloud
· Support for discontinuous operation using SQLite running on Unison OS to
store and selectively update data to the cloud
Billing is a critical aspect of commercial systems. Telecoms operators have
demonstrated that the monthly pay model is the best revenue choice. In addition,
automatic service selection and

integration for seamless billing is important. Also credit card dependence creates
issues including over the limit issues, expired cards and deleted accounts.
Self-supporting users are a key to implementation success, too. This includes
things like remote field service so devices never return to the factory, intelligent
or automatic configuration, online help, community help, and very intuitive
products are all key.
Application integration is also important. Today point systems predominate, but
in the future the key will be making sensors available to a broad set of
applications that the user chooses. Accuracy and reliability can substantially
influence results application results and competition is expected in this area as
soon as standard interfaces emerge. Indirect access via a server ensures security,
evolution without application changes and billing control.
Discontinuous Operation and Big Data go hand in hand. With devices connecting
and disconnecting randomly, a need to preserve data for the sensors and update
the cloud later is required. Storage limitations exist for both power and cost
reasons. If some data is critical, it may be saved while other data is discarded. All
data might be saved and a selective update to the cloud performed later.
Algorithms to process the data can run in either the cloud or the sensors or any
intermediate nodes. All of these options present particular challenges to the
sensor, cloud, communications, and external applications.
Multiple connection sensor access is also a requirement to make sensors truly
available to a broad set of applications. This connection will most likely happen
through a server to simplify the sensors and eliminate power requirements for
duplicate messages.

Process:
Three types of actions have been extensively recognized and researched in IoT design Process:
 In-context artefacts: By placing working products or prototypes in
context, we can obtain insights into how people live with networked
products in their daily lives. This allows us to understand in which ways
technology can be used to support people in their day-to-day efforts, or
which values we could focus on. A good example of this is Bill Gaver’s
history tablecloth, a digitally connected product created as an
experiential prototype. Only by living with this product on a day-to-day
basis you can fully experience and understand its functionality and value.
 Involving stakeholders: When it comes to designing with ‘novel’
technologies, it is not easy to present ideas to end users or other
 stakeholders in early stages of the design process. But the literature
thoroughly explores way to better explore concepts and early ideas. A
school book example of such a technique is Wizard of Oz testing, which
originated in the 1980s. Wizard of Oz testing comes down to providing an
end user with the illusion that a digital system is functional, whereas it is
actually being controlled manually.
 Design tools: When designing digitally connected physical products, a
design challenge is to constantly keep track of which design choices in
either medium influence each other. For example, adding a physical
button to a hardware device might be impossible because the micro
controller does not have any spare pins to use: In this case, a digital
constraint limits a physical design choice. Research by Bjorn Hartmann
(2006) and
others has been tackling these challenges. Hartmann created a set of
software and

hardware building blocks called [d.tools], which made it possible to create

working digitally connected physical prototypes more easily.

In a study in collaboration with 13 IoT startups from the ThingsCon network
across 3 major European cities — London, Amsterdam and Berlin — we set up
sessions with 4 to 5 startups in each city. During these sessions, the prime focus
was on creating a visualized timeline of the design process linked to each
startup’s product. Afterwards, all gathered processes were analyzed using the
‘Development Oriented Triangulation’ framework (DOT), which focuses on
breaking down design processes into 5 different categories:
 Library: A ‘static’ research activity, such as looking up existing work or
analyzing existing data.
 Field: Going out into the field to observe, trial, or explore something in content.
 Showroom: Creating something, usually a prototype that can be shown
and evaluated by experts.
 Workshop: Making something through prototyping or exploring a topic in a ‘hands-
on’
way.
 Lab: Testing a prototype or idea in a controlled way, not necessarily in a
realistic context of use.
Each of the 13 design processes we gathered this way was broken down using
that system. During the analysis, a clear structure emerged: All design processes
involved ‘technical’, ‘business’, and ‘user’ related design activities.
 Technical activities relate to, for instance, choosing a technology or
developing hardware.
 A business activity within the startup context is often related to
showcasing a working prototype to investors.
  Lastly, a user activity is anything that touches on users’ involvement, like a trial sessio
n,
or going out into the field to interview relevant people.

Model
The development projects for even the simplest IoT products must integrate
technical elements and effectively coordinate the activities of experts from many
disciplines across multiple organizations.
There are also new challenges posed by system testing, security, maintenance,
support, warranty, regulatory compliance, data governance, and user privacy—
IoT development faces unique obstacles in all these areas. No wonder the risks of
delays, cost overruns, and overall failures are so great.
To help companies understand the complexity of IoT device development, IoT
technology stack model can be referenced below figure 5.2. It shows IoT devices
are made up of multiple technology layers including, the physical hardware
device, IoT cloud platform, embedded software, network communication
protocols, and security.
 Fig .5.2 IoT Technology Stack Model

Service:
For sensor-driven IoT networks, suite of Internet of Things design services ranging
from IoT architecture design can be referenced as:
1. Smart Sensor Design
The smart sensor, or “edge device,” sits on the outer edge of the IoT network and collects the
granular data required by businesses, individuals, and intelligent systems. Our services
include:
 Development of custom single- or multi-function sensors
 Sensor integration (e.g. acoustic, motion, temperature, moisture)
 Smart power management (e.g. ultra-low-power states)
 Video security and data capture
 Wired or wireless networking enablement and integration
2. IoT Gateway Design
The gateway is the bridge between the sensor network and the cloud. It collects
all the data transmitted by the sensors and can also push periodic firmware
updates to them.
 Embedded software development of sensor data collection solutions
 Latency management to deliver near real-time performance
 Data flow management for large data sets
 PCB design and I/O integration (e.g. Ethernet, USB)
 Power management
 Cloud connectivity (e.g. cellular, Ethernet, Wi-Fi)
3. Sensor Networking
A business-critical requirement for any IoT network is a secure and highly reliable
connectivity infrastructure. Our services include:
 Communications firmware development and cross-platform integration
 Secure communications encryption and device identification
 Support for wireless protocols (e.g. Bluetooth 2.1 and Bluetooth Smart,
Wi-Fi, 802.xx.x, Sub-1GHz, 2.4 GHz, custom radio protocols)
 RF Design
o Co-location testing
o Certifications such as FCC part 15, ETSI, EN60251, and others
o RF tuning and optimization for discrete solutions
o 4GHz Industrial, Scientific, and Medical (ISM) bands
o 868MHz/915MHz – custom point to point and broadcast
protocols for sensor data, status messages, distributing
firmware upgrades and media content
4. Cloud Connectivity
Many types of IoT data translate into true business value via connectivity with the
cloud. Have the gateway send periodic “heartbeats” to the cloud server to let it
know that the sensor network is alive and healthy
 Have the gateway and smart sensor devices receive “pushed”
commands, configuration
and software updates
 Support for application-level system management and analytics software
Functional & Operational view
Following table summarizes functional and operational view as:

Describes how the system will be operated, administered, and supported when
Definition
it is running in its production environment
 installation and upgrade
 functional migration
 data migration
 operational monitoring and control
 alerting
Concerns  configuration management
 performance monitoring
 support
 backup and restore
 operation in third-party environments

 installation models
 migration models
 configuration management models
Models
 administration models
 support models

 lack of engagement with the operational staff

 lack of backout planning
 lack of migration planning
 insufficient migration window
 missing management tools
Pitfalls
 production environment constraints,
 lack of integration into the production environment
 inadequate backup models
 unsuitable alerting

System administrators, production engineers, developers, testers,

Stakeholders
communicators, and assessors
Applicability Any system being deployed into a complex or critical operational environment

IOT Privacy and security solutions-The IoT has to protect against attacks from
the following categories: authentication, access control, confidentiality, integrity,
and availability. Authentication involves the mutual verification of routing peers
before they share route information and ensures shared data origin is accurate.
In the IoT, authentication has to be strong and highly automated. Access control
is the prevention of unauthorized node use, i.e. making sure nodes are not
compromised. Confidentiality is the protection of information, especially when
shared over a publicly accessible medium such as air for wireless. Integrity
involves the protection of data and confirms no unauthorized modifications
occur.
 Fig .5.3 Privacy and security Architecture

A major difference between traditional Internet and the IoT is the amount of
data being collected about the user. Data is collected universally in the IoT and
this data can be used to build an invasive profile of the consumer. The
organizations recognized three major privacy concerns: facilitation of the
collection of large amounts of consumer data, using that data in ways
unexpected by the consumer, and security of data. This ubiquitous data
collection makes the Internet of Things a much more data driven economy. With
massive quantities of continuous data, new discoveries can be made, but little to
no regulation can by harmful to the consumers. Privacy issues are especially hard
to discuss because, by nature, privacy is subjective. The organizations aim to
promote three best practices: privacy by design, simplified consumer choice,
transparency. Companies have to make an effort to build consumer protection in
from the beginning.
With such an asymmetry of power between businesses and their consumers, the
organizations are looking for ways to protect users against abuse of their data.
The IoT, a data-driven ecosystem, requires a trust between the business and
consumer that exists even now. A user shares data with a business and in return
receives a service. The organizations is seeking to push businesses and
companies towards built-in security and designing security into new devices. For
the IoT, the data is usually passively and ubiquitously collected. As a result, the
organizations believes businesses will have to earn user trust and at a data level,
which means
involving the user. A similar problem exists in the energy industry. A Green Butto
n was created

in order to standardize energy usage information, allow the consumers to

download the information, and enlighten the users how their data is being used.
Empowering and educating the consumer would help facilitate the integration of
the IoT into our everyday lives.

Raspberry Pi:
1. Introduction
“Pi is a single-board computer”. Pi is a small scale computer in the size little
bigger than a credit card, it packs enough power to run games, word processor
like open office, image editor like Gimp and any program of similar magnitude.
Pi was introduced as an educational gadget to be used for protyping by hobbyists
and for those who want to learn more about programming. It certainly cannot be
a substitute for our day to day Linux, Mac or Windows PC.
Pi is based on a Broadcom SoC (System of Chip) with an ARM processor [~700
MHz], a GPU and 256 to 512 MB RAM. The boot media is an SD card [which is not
included], and the SD card can also be used for persist data. Now that you know
that the RAM and processing power are not nearly close to the power house
machines you might have at home, these Pi’s can be used as a Cheap computer
for some basic functions, especially for experiments and education. The Pi comes
in three Configurations and we will discuss the specifications of those in the
coming sections. The cost of a Pi is around $35 for a B Model and is available
through many online and physical stores.
 Fig 5.4: Raspberry Pi Board

2. System Specifications
Computer A Raspberry Pi
SD Card and a SD card reader to image the OS [These days laptops have
Storage
inbuilt card readers]
Power supply 5 volt micro USB adapter, mostly your android phone charger would work

Display An TV/Monitor with DVI or HDMI port

Display
HDMI cable or HDMI to DVI converter cable
connector
Input USB Mouse
Input USB Keyboard
Network Ethernet cable
Case If you really need one, you can get them online based on the model you
have

3. Raspberry Pi uses
It can be used in following areas/applications:
1. Retro Gaming
2. Raspberry Pi Tablet
3. Low-Cost Desktop PC
4. Raspberry Pi Cluster
5. Raspberry Pi Cloud Server
6. Raspberry Pi Media Center
7. Web Server
8. Home Automation System
9. VPN
10. Robotics

Arduino devices
1. Introduction
Arduino is an open source computer hardware and software company, project,
and user
community that designs and manufactures sin
gle board microcontrollers and microcontroller kits for building
digital devices and interactive objects that can sense and control objects in
the physical world. The project's products are distributed as open-source
hardware and software, which are licensed under the GNU Lesser General Public
License (LGPL) or the GNU General Public License (GPL), permitting the
manufacture of Arduino boards and software distribution by anyone. Arduino
boards are available commercially in preassembled form, or as do-it-
yourself (DIY) kits.
Arduino board designs use a variety of microprocessors and controllers. The
boards are equipped with sets of digital and analog input/output (I/O) pins that
may be interfaced to various expansion boards (shields) and other circuits. The
boards feature serial communications interfaces, including Universal Serial
Bus (USB) on some models, which are also used for loading programs from
personal computers. The microcontrollers are typically programmed using a
dialect of features from the programming languages C and C++. In addition to
using traditional
compiler tool chains, the Arduino project provides an integrated developme
nt environment (IDE) based on the Processing language project.
 Fig 5.5: Raspberry Pi Boar

2. System Specifications
Component Specification
Microcontroller ATmega328
Operating Voltage 5V
Input Voltage (recommended) 7-12V
Input Voltage (limits) 6-20V
Digital I/O Pins 14 (of which 6 provide PWM output)
Analog Input Pins 6
DC Current per I/O Pin 40 mA
DC Current for 3.3V Pin 50 mA
Flash Memory 32 KB (ATmega328)
SRAM 2 KB (ATmega328)
EEPROM 1 KB (ATmega328)
Clock Speed 16 MHz
Length 68.6 mm
Width 53.4 mm
Weight 25 g

3. Arduino uses
It can be used in following areas/applications:
1. Tiny Weather display
2. MIDI Controller
3. Fingerprint Scanner to Your Garage Door Opener
4. Auto-Trigger Spray Gun
5. Make Your Own Arduino
6. Add Motion-Triggered Night Lights Under the Bed
7. Mute Any Phrase You Want on Your TV
8. Add an Ambilight Sensor to Your LCD Display

9. Build a Robot Arm

10. Create a Fully Functional Computer Control Panel

IOT Case studies: Smart City Street lights control & monitoring.

Introduction-Automate street lights are necessary while we are trying to survive

in the era of smart world. Automation provides perfection and efficiency. The
goal is to automate street lighting, as current system is facing many problems. A
user has to deal with numerous problems like maintenance problem, timer
problem, connectivity problem, display problem. The solution to these problems
is IoT Based Street Lights.
“treet lights are one of the main city’s assets which provide safe roads, inviting
public areas, and enhanced security in homes, businesses, and city centers. As
they use in average 40% of a city’s electricity spending which leads to
power consumption.
Following are the issues of existing electric system. Connectivity issue-In existing
system, connections of street light are done manually. As each connection
requires different contractors and if any one of them is not available then it will
leads to functionality problem of street lights.
1. Timer Problem-Contractors needs to manage timer settings manually. As
timer requires twelve hour of continuous electricity supply, and if in case it is not
available, it will delay further timer settings.
2. Maintenance problem-If any of the streets light gets failed or any problem occurs, it’s
not
resolved immediately.
3. Incorrect Readings-Sometimes exact readings are not shown on to the display.
So we cannot conclude how much energy is being consumed which give rise in
high billing.
“treetlights are among a city’s strategic assets providing safe roads, inviting
public areas, and enhanced security in homes, businesses, and city centers.
However, they are usually very costly to operate, and they use in average 40% of
a city’s electricity spending.
This project describes a new economical solution of street light control systems.
The control system consists of wireless technology. Base server can control the
whole city’s street lights by just sending a notification using network.

Component descriptions
1. Energy efficiency using SSL-SSL is nothing but the smart street light system.
The SSL system, a framework for fast, reliable, and power efficient street lamp
switching based on pedestrians’ location and personal desires of safety . In the
developed prototype user location, detection as well as safety zone definition
and announcement of other configuration information is accomplished using
standard Smartphone capabilities. An application on the phone is periodically
sending location and other information to the SSL server. For street lamp control,
each and every lamppost is extended with a ZigBee-based radio device, receiving
control information from the SSL server via multi-hop routing.

2. Embedded Platform for IoT applications- For embedded platforms, CoAP

(Constraint Application protocol) is used for IOT applications. The main idea of
this protocol is to provide a lightweight protocol for resource-oriented
applications run on constrained networks. For
reducing the burdens of manufacturers, we have designed our software
framework for embedded system nodes to allow IoT service development with
minimal efforts. As this framework supports application-layer API, which does
not affect the existing codes and hides network-layer functions, product
manufacturers only need to append a simple CoAP service definition, network
driver, and physical network adapter to start IoT services on nodes.

3. Electrical power saving using VANET-The huge amount of electrical power of

many countries is consumed in lighting the streets. However, vehicles pass with
very low rate in specific periods of time and parts of the streets are not occupied
by vehicles over time. An efficient autonomous street lighting control and
monitoring system based on the innovative technology named as Vehicular Ad-
Hoc Networks (VANET) is proposed. The system can be integrated with
VANET to reduce the cost and use the rich services and communication features
of VANET. Huge energy can be saved without affecting the visibility and the
safety of the drivers. It can extend the lifetime of the lamps. It can automatically
monitor the street lighting equipment’s and warn the maintenance traffic
authority upon failure detection in any place of the streets.

4. Fully controlled street lights using Raspberry-pi and Zigbee-The Raspberry-Pi

has been chosen for its low costs and for the possibility to drive also a WiMAX
modem/router which allows to make the data system visible by a web site
accessible by Internet also for areas very far from the city and not reached
neither by the ADSL line nor by 3G signals. Intelligent lighting of the lamp, the
storage of the functioning data, and their sharing by a local communication
wireless mesh realized by ZigBee devices that send information to the
coordinator lamp equipped with a RaspberryPi card.

5. System-Raspberry-Pi is used to provide interface between user and system. It

is connected to wireless network and relay circuit which will pass the operational
admin’s message to the system. Then relay circuit operate the commands like ON
Lights, OFF Lights, Alter ON, Alter OFF onto the connected array of street light.
Our system includes two admin: System admin and Operational admin. System
admin handles log messages and operational admin. System admin can add,
delete and view operational admin. Once the operational admin added to the
system by the system admin then operational admin can log in to the system. For
example, operational admin choose the city and area from database to ON or
OFF the street lights. And if any fault occurs in the functioning of street lights
then relay circuit will send the faulty street light’s IP address to the operational
admin then operation admin will resolve the problem.
Fig 5.6: System architecture of system