Unit 1
Unit 1
(AnLECTURE
AutonomousHANDOUTS
Institution)
(Approved by AICTE, New Delhi, Accredited by NAAC & Affiliated to Anna University)
Rasipuram - 637 408, Namakkal Dist., Tamil Nadu
IT IV / VII L
Introduction : IoT comprises things that have unique identities and are connected to internet. By 2020 there will
be a total of 50 billion devices /things connected to internet. IoT is not limited to just connecting things to the internet but
also allow things to communicate and exchange data.
Definition: A dynamic global n/w infrastructure with self configuring capabilities based on standard and interoperable
communication protocols where physical and virtual ―things have identities, physical attributes and virtual personalities
and use intelligent interfaces, and are seamlessly integrated into information n/w, often communicate data associated with
users and their environments.
Characteristics:
1) Dynamic & Self Adapting: IoT devices and systems may have the capability to dynamically adapt with the changing
contexts and take actions based on their operating conditions, user‘s context or sensed environment. Eg: the surveillance
system is adapting itself based on context and changing conditions.
2) Self Configuring: allowing a large number of devices to work together to provide certain functionality.
3) Inter Operable Communication Protocols: support a number of interoperable communication protocols and can
communicate with other devices and also with infrastructure.
4) Unique Identity: Each IoT device has a unique identity and a unique identifier(IP address).
5) Integrated into Information Network: that allow them to communicate and exchange data with other devices and systems
Applications of IoT:
1) Home
2) Cities
3) Environment
4) Energy
5) Retail
6) Logistics
7) Agriculture
8) Industry
9) Health & Life Style
Functional Requirements
Functional requirements define the products and features that the IoT system must deliver. There are
seven categories of requirements to consider when developing any IoT initiative for private or public
institutions.
1. Feature requirements: What are the high-level expectations of the solution? This is the general goal of the
initiative.
2. Business requirements: This is a description of the new or improved capabilities the user must be able to do as a
result of the new system.
3. Nonfunctional requirements: This defines the service level expectations of the system such as availability,
reliability, scalability, security, backup, and disaster recovery.
4. Functional requirements: This is a description of the functions that the user requires from the system. It should
contain a process model, data entities, user stories, and use cases.
5. System design requirements: This defines the interaction of the IoT system with other systems.
6. IoT data management requirements: This describes how the data will be ingested and analyzed. The following
four areas need to be defined:
o Ingestion: how the data will be collected and integrated into one data source
o Analytics: defines the predictive analytics models and data analysis requirements
o Communications: who needs to be informed when an alarm is identified
o Persistence: defines how long the data needs to be retained
7. Reports and dashboards: This defines the reports and dashboards that users need to rapidly analyze and respond
to data collected.
Video Content / Details of website for further learning (if any):
https://www.futurithmic.com/2019/02/27/functional-view-developing-iot-service
Important Books/Journals for further learning including the page nos.:
Net reference
Course
Faculty
Introduction : IOT is not just internet-connected consumer devices. In fact, IOT is the technology
that builds systems capable of autonomously sensing and responding to stimuli from the real world
without human intervention. We therefore need to develop a process flow for a definite framework over
which an iot solution is built.
Prerequisite knowledge for Complete understanding and learning of Topic:
Network Topologies
Internet Protocols
Routing Techniques
Computer Hardware
Detailed content of the Lecture:
Iot can be classified into a four or five-layered architecture which gives you a complete overview of how it works in real
life. The various components of the architecture include the following:
Four-layered architecture: this includes media/device layer, network layer, service and
application support layer, and application layer.
Five-layered architecture: this includes perception layer, network layer, middleware layer,
application layer, and business layer. The iot architecture generally comprises of these 4
stages:
Stage 1 (sensors/actuators):
A thing in the context of “internet of things”, should be equipped with sensors and actuators
thus giving the ability to emit, accept and process signals.
Sensors collect data from the environment or object under measurement and turn it into useful
data. Think of the specialized structures in your cell phone that detect the directional pull of
gravity—and the phone's relative position to the “thing” we call the earth—and convert it into
data that your phone can use to orient the device.
Actuators can also intervene to change the physical conditions that generate the data. An
actuator might, for example, shut off a power supply, adjust an air flow valve, or move a
robotic gripper in an assembly process.
Stage 2 (data acquisition systems):
The data from the sensors starts in analog form. That data needs to be aggregated and
converted into digital streams for further processing downstream.
Data acquisition systems (das) perform these data aggregation and conversion functions. The
das connects to the sensor network, aggregates outputs, and performs the analog-to-digital
conversion. The internet gateway receives the aggregated and digitized data and routes it over
wi-fi, wired lans, or the internet, to stage 3 systems for further processing.
Intelligent gateways can build on additional, basic gateway functionality by adding such
capabilities as analytics, malware protection, and data management services. These systems
enable the analysis of data streams in real time.
Although delivering business insights from the data is a little less immediate at the gateway
than it would be when sent directly from the sensor/actuator zone, the gateway has the
compute power to render the information in a form that is more understandable to business
stakeholders.
Gateways are still edge devices—they’re external to the data center—so geography and
location matter. In the pump example, if you have 100 pump units and want to process data on-
premises, you might have instant data at the pump level, aggregate the information to create a
plantwide view for the facility, and pass the data on to the data center for companywide view.
Das and gateway devices may end up in a wide variety of environments, from the factory floor
to mobile field stations, so these systems are usually designed to be portable, easy to deploy,
and rugged enough to withstand variations in temperature, humidity, dust, and vibration.
Stage 3 (edge analytics):
Once IOT data has been digitized and aggregated, it's ready to cross into the realm of it.
However, the data may require further processing before it enters the data center. This is where
edge it systems, which perform more analysis, come into play.
Edge it processing systems may be located in remote offices or other edge locations, but
generally these sit in the facility or location where the sensors reside closer to the sensors, such
as in a wiring closet.
Because IOT data can easily eat up network bandwidth and swamp your data center resources,
it's best to have systems at the edge capable of performing analytics as a way to lessen the
burden on core it infrastructure.
Stage 4 (cloud analytics):
Data that needs more in-depth processing, and where feedback doesn't have to be immediate,
gets forwarded to physical data center or cloud-based systems, where more powerful it systems
can analyze, manage, and securely store the data.
It takes longer to get results when you wait until data reaches stage 4, but you can execute a more in-depth analysis, as well
as combine your sensor data with data from other sources for deeper insights. Stage 4 processing may take place on-
premises, in the cloud, or in a hybrid cloud system, but the type of processing executed in this stage remains the same,
regardless of the platform.
Course
Faculty
MUTHAYAMMAL ENGINEERING COLLEGE
(AnLECTURE
AutonomousHANDOUTS
Institution)
(Approved by AICTE, New Delhi, Accredited by NAAC & Affiliated to Anna University)
Rasipuram - 637 408, Namakkal Dist., Tamil Nadu
IT IV / VII L
Introduction : Web 3.0 is the next generation of Internet technology that heavily relies on the use of machine
learning and artificial intelligence (AI). It aims to create more open, connected, and intelligent websites and web
applications, which focus on using a machine-based understanding of data.
Web 3.0, while not fully defined, could leverage peer-to-peer (P2P) technologies like blockchain, open-source
software, virtual reality, Internet of Things (IoT), and more.
No central point of control: Since middlemen are removed from the equation, user data will no longer be controlled by
them. This reduces the risk of censorship by governments or corporations and cuts down the effectiveness of Denial-of-
Service (DoS) attacks.
Increased information interconnectivity: As more products become connected to the Internet, larger data sets provide
algorithms with more information to analyze. This can help them provide more accurate information that accommodates
the specific needs of the individual user.
More efficient browsing: When using search engines, finding the best result used to be quite challenging. However,
over the years, they have become better at finding semantically-relevant results based on search context and metadata.
This results in a more convenient web browsing experience that can help anyone find the exact information they need
with relative ease.
Web 2.0 also introduced social tagging systems, but those can be manipulated. With smarter algorithms, manipulated
results can be filtered by AI.
Improved advertising and marketing: No one likes being bombarded with online ads. However, if the ads are relevant
to one's interests and needs, they could be useful instead of being an annoyance. Web 3.0 aims to improve advertising by
leveraging smarter AI systems, and by targeting specific audiences based on consumer data.
Better customer support: When it comes to websites and web applications, customer service is key for a smooth user
experience. Due to the massive costs, though, many web services that become successful are unable to scale their
customer service operations accordingly. Through the use of smarter chatbots that can talk to multiple customers
simultaneously, users can enjoy a superior experience when dealing with support agents.
Video Content / Details of website for further learning (if any):
https://academy.binance.com/en/articles/the-evolution-of-the-internet-web-3-0-
explained
Course
Faculty
Introduction: The arrival of the IoT concept and its worldwide attention is closely relevant to environmental,
societal, and economic challenges such as climate change, environment protection, energy saving, and globalization. For
these reasons the IoT is increasingly used in a large number of sectors. Key sectors in this context are transportation,
healthcare, energy and environment, safety and security, logistics, and manufacturing.M2M and embedded mobile devices
are sending mobile data to
Servers that are increasingly useful and valuable to ERPs.
Prerequisite knowledge for Complete understanding and learning of Topic:
Network Topologies
Internet Protocols
Routing Techniques
Computer Hardware
Detailed content of the Lecture:
Introduction: Applications of the Internet of Things (IoT) have spread across an enormously large number of
industry sectors, he development of the vertical applications in these sectors is unbalanced. It is very important to sort out
those vertical applications and identify common underpinning
Technologies that can be used across the board, so that interconnecting, interrelating, and synergized grand integration and
new creative, disruptive applications can be achieved.
Prerequisite knowledge for Complete understanding and learning of Topic:
Network Topologies
Internet Protocols
Routing Techniques
Computer Hardware
Detailed content of the Lecture:
Device: Devices are essentially the “things” that make up the Internet of Things. If your
business is looking to implement more IoT applications, you’re going to need a wireless solution that
can support the many devices that will live on your network, and ensure that your applications run
seamlessly and smoothly. Depending on the size of your business, this could be anywhere from
hundreds, to thousands of “things” working together on a single network.
Data: One of the main functions of IoT is to gather an immense amount of data to improve
operations and functionality. Going back to our previous examples, this data could be made up of hours
of surveillance footage, tens of thousands of steps you take during a day, or your entire music library.
These examples are basic, gathering information from a single device for an individual. Now imagine
the amount of data being collected on an enterprise level – when HVAC, monitoring, security and
many other devices are being used – it’s going to be in most facets of businesses and buildings.
Analytics: Now that we have established that there is a large amount of data being collected, it
is important to recognize the third pillar of IoT – analytics. Being able to analyze all the information
being gathered is what makes IoT applications useful and influential. It’s the data analytics that helps
optimize device usage and user benefits.
Connectivity: Connectivity is what enables the previous three pillars to work (together).
Devices must be connected to transfer data. Data cannot be sent or received without reliable high-
bandwidth connectivity that supports real-time data flow from the many devices living on a network.
Without connectivity, there would be no data to analyze and no analytics available to optimize systems
and create efficiencies. IoT deployments would lack scalability.
DNA of IoT
DNA comprised of three building blocks:
1. D – Digital Transformation
2. N – Networks
3. A – Applications
What differentiates a successful planning, execution, implementation, and adoption of IoT in a
company is their maturity of their DNA.
1. It’s an utmost important factor to get the mindset ready with their strategy in adopting Digital Services
within the company. We might be talking Digital Economy or Big Data Analytics whatsoever but without a Champion that
can break down all the barriers especially in the mindset, that company will be doom within the next 3-4 years when
everyone else has increased their productivity multiple folds and create new revenue streams by adopting digital services.
Both front-end and back-end systems must be in digital form. Interacting with customers no longer sufficient with a human
but must extend the reach using online and mobile services. We have to do away with pen and paper process to be more
competitive. Everything MUST be in digital format otherwise your business will be eaten away by your competitor.
2.
3. Taking control of your assets utilization and understand how your customer use your products are very
important. Thus, the assets MUST get connected to allow the companies to monitor their pattern of usage. Find the best
connectivity options regardless whether it’s inside a building or outside. It can be either a fixed or wireless, short-range or
long-range, low-speed or high-speed network – everything depends on the kinds of data that the sensor transmits.
4.
1. Get ready to transform your new process workflow. It will never be the same again. IoT will break down
unnecessary barriers and automate the process flow. You might face some resistance internally when these new processes
will obsolete many manual tasks and jobs. However, with the new process, you might need new applications to manage and
thus new jobs are created. Thus, you will see many applications are custom built due to the legacy systems that need to be
integrated. But it also opens up unlimited possibilities for new applications to be created for companies who wish to replace
their old systems or just wanting to adopt a new business.
Video Content / Details of website for further learning (if any):
https://www.favoriot.com/the-dna-of-internet-of-things-iot/
Important Books/Journals for further learning including the page nos.:
Honbo Zhou,” The Internet of Things in the Cloud: A Middleware Perspective”, CRC Press,2012.pp-55-94, 95-128.
Course
Faculty
MUTHAYAMMAL ENGINEERING COLLEGE
(AnLECTURE
AutonomousHANDOUTS
Institution)
(Approved by AICTE, New Delhi, Accredited by NAAC & Affiliated to Anna University)
Rasipuram - 637 408, Namakkal Dist., Tamil Nadu
IT IV / VII L
Topic of Lecture: The Toolkit Approach for End-user Participation in the Internet of
Things
Introduction : Today, there are many end-user programming tools available, but in the Internet of Things domain,
this concept is relatively new. Some pioneer examples include solutions, such as d.tools and Pachube, but also Web2.0,
Mash-ups, Twitter and Facebook are suitable backplanes for this kind of applications. Another level of development support
is various hardware concepts and solutions, such as RFIDs, Arduino, Violet, NFC, barcodes and many more. Appropriate
user programmability could transform a system, multiplying the effectiveness of programmers and users. This article
discusses how end-users can be empowered with new building blocks and tools, analogous to those that were emerging
during the early phases of Internet growth. Accelerators, frameworks and toolkits are introduced, which would allow
everybody to participate in the Internet of Things in the same manner as in the Internet through Wikis, Blogs etc.
Prerequisite knowledge for Complete understanding and learning of Topic:
Network Topologies
Internet Protocols
Routing Techniques
Computer Hardware
Detailed content of the Lecture:
Participatory Design PD applications are diverse in their perspectives, backgrounds, and areas of concern,
leading to a lack of a single definition. However, in its essence, PD represents an approach towards assessment, design and
development of various systems in which people, destined to actually use these systems, play the major role in designing
and in the decision-making process. In other words, users are the co-designers of the systems. The PD approach emerged in
the mid 1970s in Scandinavia, under the name cooperative design. It was born out of the labor union’s push for workers to
have more democratic control in their work environment (Ehn 1989). However, when presented to the US community, due
to the strong separation between managers and workers, participatory was the more appropriate description of the process,
where managers and workers did not sit and work together, but rather work separately on the same problems, thus
participating in the solution finding process.
Pioneer projects included: • Norwegian Iron and Metal Workers Union (NJMF) project, that took a first move from
traditional research to working with people (Ehn and Kyng 1987), Utopia project (Bodker et al. 1987), (Ehn 1988), whose
major achievements were the experience-based design methods, developed through the focus on hands-on experiences,
emphasising the need for technical and organisational alternatives, and • Florence project (Bjerknes and Bratteteig 1995)
which has started a long line of Scandinavian research projects in the health sector, giving voice to nurses during the
development of work and IT in hospitals.
Course
Faculty
MUTHAYAMMAL ENGINEERING COLLEGE
(An Autonomous Institution)
(Approved by AICTE, New Delhi, Accredited by NAAC & Affiliated to Anna University)
LECTURE HANDOUTS
Rasipuram - 637 408, Namakkal Dist., Tamil Nadu
L
IT IV / VII
Introduction : There are several historical stories that linguistically unite humanity across the planet: the Tower of
Babel, Enmerkar and the Lord of Aratta, Xelhua, and Toltecs. Middleware deals
with the babble between distributed systems and has a similar objective in bringing linguistic or communicative unity to
disparate technological systems.
Prerequisite knowledge for Complete understanding and learning of Topic:
Network Topologies
Internet Protocols
Routing Techniques
Computer Hardware
Detailed content of the Lecture:
Middleware
Enables applications running across multiple platforms tocommunicate with each other
Shields the developer from dependencies on network pro-tocols, operating systems, and
hardware platforms
It is a software layer that lies between the operating system and the applications on each site of the system
◾ Hides heterogeneity and location independence
◾ Increases software portability
◾ Provides common functionality needed by many applications
◾ Aids application interoperability
◾ Aids scalability
◾ Helps integrate legacy facilities
Course
Faculty
Introduction : A number of middleware systems have been built using various combinations of standard services;
the Internet Protocol is one that’s often used. CORBA has also been used as a model for distributed embedded services.
The Common Object Request Broker Architecture (CORBA) [Obj06] is widely used as an
architecture for middleware services. It is not itself a specific protocol; rather it is a metamodel that
describes object-oriented services. CORBA services are provided by objects that combine functional
interfaces as well as data. An interface to an object is defined in an interactive data language (IDL).
The IDL specification is language-independent and can be implemented in many different programming
languages. This means that the application and the object need not be implemented in the same
programming language. IDL is not a complete programming language; its main job is to define interfaces.
Both objects and the variables carried by objects have types.
Object request broker
An object request broker (ORB) connects a client to an object that provides a service. Each object
instance has a unique object reference. The client and object need not reside on the same machine; a
request to a remote machine can invoke multiple ORBs. The stub on the client side provides the interface
for the client while the skeleton is the interface to the object. The object logically appears to be a single
entity, but the server may keep a thread pool running to implement object calls for a variety of clients.
Because the client and the object use the same protocol, as defined by the IDL, the object can provide a
consistent service independent of the processing element on which it is implemented.
Course
Faculty
IoT security has become the subject of scrutiny after a number of high-profile incidents where a common
IoT device was used to infiltrate and attack the larger network. Implementing security measures is critical to ensuring the
safety of networks with IoT devices connected to them.
A number of challenges prevent the securing of IoT devices and ensuring end-to-end security in an IoT
environment. Because the idea of networking appliances and other objects is relatively new, security
has not always been considered top priority during a product's design phase. Additionally, because IoT
is a nascent market, many product designers and manufacturers are more interested in getting their
products to market quickly, rather than taking the necessary steps to build security in from the start.
A major issue cited with IoT security is the use of hardcoded or default passwords, which can
lead to security breaches. Even if passwords are changed, they are often not strong enough to prevent
infiltration.
Another common issue facing IoT devices is that they are often resource-constrained and do
not contain the compute resources necessary to implement strong security. As such, many devices do
not or cannot offer advanced security features. For example, sensors that monitor humidity or
temperature cannot handle advanced encryption or other security measures. Plus, as many IoT devices
are "set it and forget it" -- placed in the field or on a machine and left until end of life -- they hardly
ever receive security updates or patches. From a manufacturer's viewpoint, building security in from
the start can be costly, slow down development and cause the device not to function as it
should.Connecting legacy assets not inherently designed for IoT connectivity is another security
challenge. Replacing legacy infrastructure with connected technology is cost-prohibitive, so many
assets will be retrofitted with smart sensors. However, as legacy assets that likely have not been
updated or ever had security against modern threats, the attack surface is expanded.
In terms of updates, many systems only include support for a set timeframe. For legacy
and new assets, security can lapse if extra support is not added. And as many IoT devices stay in the
network for many years, adding security can be challenging.
Course
Faculty