0% found this document useful (0 votes)
3 views23 pages

Cloud Computing

Cloud computing delivers computing services over the internet, evolving from mainframe time-sharing in the 1960s to modern SaaS, PaaS, and IaaS models. It consists of core components like client devices, datacenters, and various service models, each with distinct benefits and disadvantages. Security in cloud computing is crucial, addressing concerns like data breaches and insecure APIs, while employing encryption and access controls to protect data at rest, in transit, and in use.

Uploaded by

miracleclicks0
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views23 pages

Cloud Computing

Cloud computing delivers computing services over the internet, evolving from mainframe time-sharing in the 1960s to modern SaaS, PaaS, and IaaS models. It consists of core components like client devices, datacenters, and various service models, each with distinct benefits and disadvantages. Security in cloud computing is crucial, addressing concerns like data breaches and insecure APIs, while employing encryption and access controls to protect data at rest, in transit, and in use.

Uploaded by

miracleclicks0
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 23

Cloud Computing

1. Cloud Computing: History & Evolution


Definition:
Cloud Computing is the delivery of computing services (like servers, storage, databases,
networking, software) over the internet (“the cloud”) to offer faster innovation, flexible
resources, and economies of scale.
History and Evolution:
Era/Year Milestone
1960s Concept of time-sharing on mainframes (John McCarthy).
1990s Emergence of Virtualization (VMware) – running multiple OS on one machine.
2002 Amazon launched AWS (Amazon Web Services).
2006 Google Docs launched – cloud-based documents.
2008+ Cloud becomes mainstream – SaaS, PaaS, IaaS models evolve.
📌 Exam Tip: Remember mainframe → virtualization → web services → SaaS evolution
order.

2. Components of Cloud Computing


Core Components:
Component Description
Client Devices End-users access cloud (mobiles, PCs).
Datacenters Physical servers that store all cloud data.
Virtualization Allows multiple OS on a single physical server.
Cloud Services SaaS, PaaS, IaaS.
Network Internet connectivity, backbone of cloud.
Storage Scalable cloud storage (S3, Google Drive, etc.).
Example: You open Google Drive on your phone (client device), store files in the cloud
(storage), managed by a datacenter.

✅ 3. Requirements of Cloud Computing


To function properly, a cloud computing system needs:
Requirement Why It’s Needed
High Bandwidth Internet For real-time data transfer.
Virtualization Efficient use of physical resources.
Service-Oriented Architecture (SOA) Helps in designing modular apps/services.
Scalability So system can grow easily.
Automation For quick provisioning and deployment.
Security Protect data from threats.
Resource Pooling Share computing resources across users.
📌 Trick to Remember: BVSASR → Bandwidth, Virtualization, SOA, Automation,
Scalability, Resource pooling

4. Benefits & Disadvantages of Cloud Computing


Benefits:
Benefit Explanation
Cost-Effective Pay-as-you-go model, no upfront hardware cost.
Scalable Scale resources up/down based on need.
Reliable Data backup, disaster recovery.
Benefit Explanation
Accessible Access from anywhere.
Faster Deployment New resources deployed in minutes.
Example: A startup uses AWS instead of buying servers. Saves money and scales as they
grow.

Disadvantages:
Disadvantage Explanation
Downtime Internet/cloud failure can stop services.
Security & Privacy Storing sensitive data in cloud can be risky.
Vendor Lock-in Hard to switch providers once data is stored.
Limited Control Less control over infrastructure.
Scenario: If AWS goes down, Netflix can face downtime. This is a disadvantage of cloud
dependency.

5. Cloud Computing Models & Services

5.1 Deployment Models


These define how the cloud is deployed and who has access to it.
Deployment
Description Real-time Example
Model
Cloud services are offered over the Google Drive, Dropbox, Microsoft
internet and shared among multiple Azure, AWS are public cloud platforms
Public Cloud
users. Managed by third-party where anyone can create an account and
providers. store data.
Used exclusively by one
IBM Cloud Private used by banks or
organization. Offers more control and
Private Cloud government agencies to host sensitive
security. Can be hosted on-site or by
data on their own infrastructure.
a third party.
A hospital stores patient records on a
A combination of public and private
Hybrid Cloud private cloud but uses a public cloud for
clouds that work together.
sending appointment reminders via SMS.
Shared infrastructure for a specific Several universities sharing computing
Community community with common concerns resources and collaborating on research
Cloud like security, compliance, or projects through a common cloud
jurisdiction. platform.
Exam Tip: In a question, always specify who owns the infrastructure, who accesses it,
and why it's chosen.

5.2 Service Models


These define the layer or level of service provided in the cloud environment.

1. IaaS (Infrastructure as a Service)

 Provides virtualized computing resources over the internet: servers, storage, networking.
 Users install their own OS and applications.

Real-time Example:
Amazon EC2 allows users to rent virtual servers and configure them as needed. You control
what OS to install, what software to run, and when to shut it down.
Use Case:
Startups needing scalable infrastructure without buying physical servers.

2. PaaS (Platform as a Service)

 Provides a platform allowing customers to develop, run, and manage applications


without handling the infrastructure.
 Includes OS, databases, development tools.

Real-time Example:
Google App Engine allows developers to deploy applications without worrying about the
server setup.
Use Case:
A developer building a web app can use PaaS to focus on coding while the platform handles
hosting, scaling, and load balancing.

3. SaaS (Software as a Service)

 Delivers software applications over the internet.


 Users don’t manage any infrastructure or platform.

Real-time Example:
Gmail is SaaS. You only need a browser and an internet connection. You don’t manage email
servers or software updates.
Use Case:
Small businesses using Microsoft 365 for email, document editing, and storage without
buying any hardware.

Service Model Comparison Table


Feature IaaS PaaS SaaS
User Control High (OS, apps) Medium (apps only) Low (just usage)
Example AWS EC2, Google Compute Google App Engine Gmail, Dropbox
User Type IT Admins, DevOps Developers End Users

6. Architecture: The NIST Model, Cloud Cube Model

6.1 The NIST Model (National Institute of Standards and


Technology)
The NIST Cloud Computing Model is a widely accepted reference model that defines the
essential characteristics, service models, and deployment models of cloud computing.

A. Five Essential Characteristics


Characteristic Description Real-Time Example
Users can provision computing You can create a virtual machine in
1. On-demand
resources like servers or storage AWS or Azure in minutes using a
self-service
without human interaction. dashboard.
Services are available over the
2. Broad network Google Drive and Dropbox can be
network and accessed through
access accessed via browser, mobile apps, etc.
standard mechanisms.
3. Resource Resources are pooled to serve A data center serving many companies
pooling multiple customers using multi- simultaneously using virtualization.
Characteristic Description Real-Time Example
tenant models.
Netflix automatically scales resources
4. Rapid Resources can be scaled up or
during peak hours (evening) and scales
elasticity down quickly to meet demand.
down during off-peak.
Resource usage is monitored, AWS bills based on compute hours
5. Measured
controlled, and billed based on used, data stored, or bandwidth
service
usage. consumed.

B. Three Service Models


(Already covered in Point 5):

 IaaS

 PaaS

 SaaS

C. Four Deployment Models


(Also covered earlier):

 Public Cloud

 Private Cloud

 Hybrid Cloud

 Community Cloud

6.2 The Cloud Cube Model (by Jericho Forum)


The Cloud Cube Model helps organizations evaluate cloud services by considering four
dimensions:
A. Four Dimensions of Cloud Cube Model
Dimension Options Real-Time Example
Refers to ownership and Internal: Private cloud hosted in a bank.
1. Internal/External
location of infrastructure. External: AWS for a startup.
Whether services use open
Open: OpenStack. Proprietary: Microsoft
2. Proprietary/Open standards or proprietary
Azure uses its own standards.
ones.
Perimeterised: Only accessible within
3. Perimeterised/De- Security boundary of the
firewall. De-perimeterised: Accessible
perimeterised cloud.
from anywhere, like Google Docs.
Who manages the
Insourced: Managed by internal IT team.
4. Insourced/Outsourced services: in-house or a
Outsourced: Managed by AWS.
third-party vendor.

7. Capacity Planning: Baseline & Metrics, Load Testing,


Network Capacity, Scaling

7.1 What is Capacity Planning?


Capacity Planning is the process of determining and managing IT infrastructure
resources (compute, storage, bandwidth, etc.) so that they can meet current and future
demands efficiently without over-provisioning or under-provisioning.

7.2 Defining Baseline and Metrics


A. Baseline
A baseline is the measurement of normal resource usage under standard workloads.
It helps you understand:

How much CPU, RAM, Disk, Network your system normally uses.

When performance deviates from normal.

Real-time Example:
An e-commerce website records average CPU usage as 30% during normal hours. This is
the baseline.
B. Metrics
Metrics are quantitative measures used to track system performance.
Metric Meaning Example
CPU Utilization % of CPU being used 40% average usage
Memory Usage RAM being consumed 3GB used out of 8GB
Metric Meaning Example
Disk I/O Read/write rate on storage 100MB/sec
Network Bandwidth Data transmitted/received 50 Mbps incoming
Latency Time to respond to requests 200 ms

7.3 Load Testing


Load Testing is a method of simulating real-world usage on an application to check how it
performs under expected and peak load conditions.
Goals of Load Testing:

 Identify system bottlenecks.

 Ensure system can handle expected users.

 Determine scaling needs.

Real-time Example:
Before launching a shopping sale event, Amazon does load testing to ensure their servers can
handle traffic from millions of users simultaneously.
Tools used for Load Testing:

 Apache JMeter

 LoadRunner

 Locust

7.4 Network Capacity


Network Capacity is the maximum amount of data that can be transmitted over a network in a
given time, usually measured in Mbps or Gbps.
Factors affecting network capacity:

 Bandwidth: Higher bandwidth = more data transfer.

 Latency: Delay in data transfer.

 Packet Loss: Lost packets reduce effective capacity.

Real-time Example:
Video conferencing on Zoom requires stable network capacity (~3 Mbps per HD stream). A
drop in network capacity may lead to lags or video freeze.

7.5 Scaling
Scaling is the process of increasing or decreasing resources as needed to meet demand.
A. Types of Scaling:
Type Description Real-Time Example
Vertical Scaling Add more power (CPU/RAM) to Increasing RAM from 8GB to 32GB
(Scale-Up) a single server. in an EC2 instance.
Horizontal Scaling Add more servers to distribute Adding more app servers when user
(Scale-Out) the load. traffic spikes.

B. When to Scale:
Trigger Action
CPU usage consistently over 80% Scale up (vertical) or add more instances (horizontal)
Spike in user traffic Horizontal scaling
Memory shortage Scale up with more RAM
8. Understanding Virtualization: Virtualization Technologies,
Load Balancing and Virtualization, Understanding
Hypervisors

8.1 What is Virtualization?


Virtualization is the technique of creating a virtual version of something—such as hardware
platforms, storage devices, or network resources—on top of physical hardware using
software.

8.2 Virtualization Technologies


There are various types of virtualization based on what you’re virtualizing.

A. Hardware Virtualization
Definition: It allows you to run multiple operating systems (VMs) on a single physical
machine (host).
Real-time Example:
Running Windows, Linux, and macOS on a single Dell server in a data center using VMware
ESXi.

B. Operating System-Level Virtualization


Definition: Creates containers that share the same OS kernel but are isolated environments.
Real-time Example:
Using Docker to run different services like a web server, database, and cache engine in
isolated containers on the same machine.

C. Storage Virtualization
Definition: Pools physical storage from multiple devices into a single storage unit.
Real-time Example:
A company combines SSDs and HDDs from multiple devices into a single virtual drive for
backup using NetApp or VMware vSAN.

D. Network Virtualization
Definition: Combines multiple network resources into a single virtual network.
Real-time Example:
Creating Virtual LANs (VLANs) for different departments in an organization using Cisco
switches.

Summary Table:
Type Use Case Tool/Tech Used
Hardware Virtualization Run multiple OSs VMware, VirtualBox
OS-Level Lightweight isolated environments Docker, LXC
Storage Virtualization Unified storage across devices NetApp, vSAN
Network Virtualization Logical separation of networks VLANs, SDN

8.3 Load Balancing and Virtualization


Definition: Load balancing is the process of distributing workloads evenly across multiple
virtual machines or containers to avoid overloading any single one.

Why used in virtualization?

 To maximize resource utilization.

 To increase availability and reliability.

 To ensure consistent performance.

Real-time Example:
Amazon Web Services (AWS) runs hundreds of virtual machines. An Elastic Load Balancer
(ELB) distributes incoming traffic from users to the VMs with the least load.

Diagram Tip:
You may be asked to draw:

A Load Balancer with 3 virtual servers behind it.

Arrows showing traffic distributed evenly.

8.4 Understanding Hypervisors


A Hypervisor is software that creates and manages virtual machines (VMs) by abstracting
hardware resources.

Types of Hypervisors:
Type Description Example
Type 1 (Bare- Installed directly on physical
VMware ESXi, Microsoft Hyper-V
Metal) hardware
Oracle VirtualBox, VMware
Type 2 (Hosted) Runs on top of an existing OS
Workstation

Real-time Example:

Type 1: In a data center, servers run VMware ESXi directly to host multiple client VMs.

Type 2: A developer runs Ubuntu VM on Windows using VirtualBox for testing code.
✅ Quick Comparison:
Feature Type 1 Type 2
Performance High Moderate
Use Case Enterprise servers Development/testing
OS Dependency None Depends on host OS
9. Securing Cloud: Security Mapping, Security Concerns
related to Cloud, Securing Data, Encryption

9.1 Security Mapping in Cloud Computing


Security mapping refers to the alignment of security requirements and controls with cloud
components like data storage, applications, and infrastructure.
Security mapping means matching each part of a cloud system with the right security
measures to protect it from threats.

Key Mapped Areas:


Cloud Component Security Concern Example Control
Data Storage Unauthorized access Encryption, Access Control
Applications Injection attacks, data leaks Web Application Firewall (WAF)
Virtual Machines VM isolation and control Hypervisor Hardening
Network Snooping, DDoS Firewalls, VPN, IDS

Real-Time Example:
In AWS, Identity & Access Management (IAM) maps access roles to specific resources
like S3 buckets to control who can read/write.

9.2 Security Concerns in Cloud


Cloud introduces new risks due to shared resources, multi-tenancy, and remote access.

Major Concerns:

 Data Breach

When sensitive data is accessed by unauthorized users.

Example: Misconfigured S3 bucket leaking user data.

 Insecure APIs

Cloud services expose APIs that, if poorly secured, can be entry points for attackers.

Example: Unauthenticated API access allowing full control of cloud storage.

 Account Hijacking
Compromising cloud credentials to access services.

Example: Phishing email stealing login to Google Cloud account.

 Denial of Service (DoS)

Flooding cloud servers with requests to crash or slow services.

Example: DDoS attack on an Azure-hosted website.

 Data Loss

Data deletion or corruption due to malware or user error.

Example: Ransomware on Google Drive files.

9.3 Securing Data in Cloud


Securing data in the cloud means protecting it at all three stages:
Stage Description Example Solution
At Rest Stored in disk/cloud storage AES Encryption, IAM
In Transit Moving between servers/networks HTTPS, VPN, TLS
In Use When data is being processed Encrypted Memory, Isolation

Real-Time Example:
Google encrypts Gmail data at rest and uses TLS to protect emails while in transit between
servers.

Access Control for Data Security:

 Role-based access (RBAC): Only authorized roles can access resources.

 Multi-Factor Authentication (MFA): Verifies user identity via password + OTP.

9.4 Encryption in Cloud Computing


Encryption is the process of converting data into unreadable form, so only authorized users
can access it with a decryption key.

Types of Encryption:
Type Purpose Example Use
Symmetric Same key for encrypt & decrypt File storage (AES)
Type Purpose Example Use
Asymmetric Public-private key pair Email encryption (PGP)
Homomorphic Operate on encrypted data directly Privacy-preserving cloud apps

Where Encryption is Applied in Cloud:

 Storage: Encrypt files using AES-256 in S3 or Azure Blob Storage.

 Communication: Use HTTPS (SSL/TLS) for secure API and browser access.

 Databases: MySQL with Transparent Data Encryption (TDE).

Real-Time Example:
Microsoft Azure provides automatic encryption of stored data and manages encryption keys
through Azure Key Vault.
10. Using the Mobile Cloud: Connecting to the Cloud,
Feature Phones and the Cloud, Using Smartphones with the
Cloud

10.1 Connecting to the Cloud


Mobile devices connect to cloud services via the internet using mobile networks (3G/4G/5G
or Wi-Fi). The cloud acts as the backend infrastructure that performs tasks like:

 Storing data

 Running applications

 Performing processing remotely

Key Technologies Used:

 HTTP/HTTPS for web-based cloud apps

 REST APIs to access cloud services (like Google Drive or Dropbox)

 SDKs (Software Development Kits) for cloud platforms like Firebase, AWS Mobile

Real-Time Example:
When you use Google Photos on your phone, it automatically uploads pictures to Google
Cloud over Wi-Fi or mobile data, making them accessible from any device.

10.2 Feature Phones and the Cloud


Feature phones are basic mobile devices that support limited functionality—usually no app
store or high processing power, but can still use cloud services in simplified ways.
How Feature Phones Use the Cloud:

 Via SMS gateways (e.g., bank balance check via SMS)

 USSD codes to perform cloud-based actions (e.g., checking mobile balance or


transferring money)

 Voice-based systems for agricultural/weather information

Real-Time Example:
In rural India, farmers use USSD-based apps to get real-time weather updates and crop
prices using cloud-hosted data, even on Nokia feature phones.

10.3 Smartphones and the Cloud


Smartphones have high processing power, support app stores, and offer full cloud integration.
They use cloud services to run apps without storing or processing data locally.
How Smartphones Use the Cloud:

 Cloud Storage – Google Drive, iCloud, OneDrive

 Cloud Computing – Google Docs or MS Word online (real-time editing)

 Cloud-Based Apps – Instagram, WhatsApp (media stored in cloud)

 Streaming Services – Netflix, Spotify use cloud to deliver content

Real-Time Example:
You open the YouTube app on your smartphone, search a video, and stream it. All videos are
hosted on Google Cloud, and your device just plays them in real time.
11. Introduction to Internet of Things (IoT)

11.1 Definition of IoT


The Internet of Things (IoT) refers to a network of physical objects ("things") embedded with
sensors, software, and connectivity that enables them to collect, exchange, and act on data
without human intervention.

Real-Time Example:
A smartwatch that tracks your heart rate and sends the data to a mobile app via Bluetooth or
Wi-Fi is part of the IoT ecosystem.
11.2 Characteristics of IoT
1. Connectivity:
Devices must be connected to a network (Wi-Fi, Bluetooth, cellular, etc.)
→ Example: A smart bulb connected to your home Wi-Fi.
2. Intelligence:
Devices make intelligent decisions (e.g., turn off when not in use).
→ Example: Smart thermostat adjusting temperature based on your routine.
3. Dynamic Nature:
Devices may move or change state.
→ Example: GPS-enabled delivery trucks updating their location in real-time.
4. Sensing:
Devices can sense physical conditions (temperature, motion, etc.).
→ Example: Motion sensors in smart home security systems.
5. Heterogeneity:
Devices are different (sensors, actuators, smartphones) but still communicate.
→ Example: A fridge (with temp sensor) talking to your phone app.
6. Scale:
IoT systems may have millions of connected devices.
→ Example: Smart cities monitoring traffic, pollution, lighting.
7. Security:
Since data is sensitive, encryption and secure communication is essential.
→ Example: Health IoT devices encrypt patient data.
11.3 Physical Design of IoT
The physical design of an IoT system includes the actual hardware components and interfaces
used to build it.

1. Sensors
What it does:
Captures real-world data — temperature, motion, light, humidity, gas levels, etc.
Examples of Sensors:

1) Temperature & Humidity Sensor (DHT11/DHT22) – used in smart farming and home
AC systems.

2) PIR Sensor (Motion Detection) – used in automatic lights and security alarms.

3) Gas Sensor (MQ-2) – used in kitchens to detect LPG leaks.

4) Light Sensor (LDR) – used in smart streetlights to turn on/off based on light levels.

5) Soil Moisture Sensor – used in smart irrigation systems.

Memory Tip:
"Sensors sense" – they feel what’s going on around them.

2. Actuators
What it does:
Takes action based on sensor data. It's the device that moves or changes something.
🛠Examples of Actuators:

1. Motor or Servo Motor – opens/rotates valves, fans, or doors (e.g., smart window).

2. Relay Module – acts like a switch to turn AC devices on/off (e.g., geysers, lamps).

3. Buzzer – alerts or alarms you when an event occurs.


4. LEDs – turn on/off as indicators (e.g., LED blinks when door opens).

Memory Tip:
"Actuators act" – if the system wants to do something, the actuator does it.

3. Microcontrollers / Processing Unit


What it does:
Acts as the brain of the IoT system. It receives sensor data, processes it, and tells the actuator
what to do.
Examples:

1) Arduino UNO – used in basic IoT projects.

2) ESP8266 / NodeMCU – has Wi-Fi built in; used for cloud-connected devices.

3) Raspberry Pi – more powerful (can run Linux); used for complex tasks like facial
recognition, data logging.

Memory Tip:
"Microcontrollers control the micro world."

4. Communication Modules
What it does:
Connects the IoT device to other devices or the cloud.
Types:

1. Wi-Fi Module (ESP8266, built into NodeMCU) – for home automation.

2. Bluetooth Module (HC-05/HC-06) – for short-range communication (e.g.,


smartwatches).

3. ZigBee Module (XBee) – used in smart city networks; low power.

4. GSM Module (SIM800L) – sends SMS/data via mobile networks.

5. LoRa Module – long-range, low power for smart farming or villages.

Memory Tip:
Communication modules are the "mouths and ears" – they let devices talk to each other or to
the internet.

5. Power Supply
What it does:
Powers up all the components.
Types:
1) Battery (Li-ion, AA, Coin cell) – for wearables or wireless sensors.

2) Power Adapter / USB – for Raspberry Pi, NodeMCU.

3) Solar Panel – used in environmental or agricultural IoT to power outdoor devices.

🧠 Memory Tip:
"No power, no IoT" – every component needs energy to work.

11.4 Logical Design of IoT


The logical design defines how data flows, how devices communicate, and what software
components are involved.

Key Concepts:
 Device Layer:
Physical devices/sensors/actuators.
 Network Layer:
Ensures data moves between devices & cloud (via IP, Wi-Fi, etc.).
 Data Processing Layer:
Where the collected data is analyzed (edge or cloud processing).
 Application Layer:
End-user applications that visualize or act on data.
→ Example: Mobile apps for smart homes.

IoT Communication Models:


Device-to-Device:
→ Smart watch to smartphone via Bluetooth.
Device-to-Gateway:
→ Sensor data to a hub before reaching the cloud.
Device-to-Cloud:
→ Smart plug sending usage data directly to AWS cloud.
Back-End Data Sharing:
→ IoT health device shares data with doctors via cloud platform.

12. Domain Specific IoTs and IoT Enabling Technologies

12.1 Domain-Specific IoT Applications


IoT can be applied across various domains, each using sensors, connectivity, and data
processing tailored to their unique needs. Here's a breakdown:

1. Home Automation

Objective: Automate household functions for comfort, security, and energy efficiency.

Examples:

 Smart lights that turn off when no one is in the room (motion sensors).
 Smart thermostats (e.g., Nest) adjusting temperature based on your routine.

 Smart locks with app-based remote access.

2. Environment Monitoring

Objective: Monitor air, water, weather, and pollution levels.

Examples:

 IoT sensors for air quality monitoring (PM2.5, CO2 levels).

 Water level sensors in dams/reservoirs.

 Soil moisture and temperature sensors for environmental studies.

3. Smart Cities

Objective: Improve public services, reduce waste, and optimize resources.

Examples:

 Smart traffic lights adjusting timing based on vehicle flow.

 Waste bins with sensors alerting when full.

 Street lights that dim or brighten based on pedestrian movement.

4. Energy Management

Objective: Optimize energy usage, reduce loss, and use smart grids.

Examples:

 Smart meters that track usage and send data to providers.

 Solar panels with IoT-based monitoring systems.


 Grid load balancing using real-time data from sensors.

5. Retail

Objective: Enhance customer experience, improve inventory management.

Examples:

 Smart shelves that alert when stock is low.

 Beacons that send offers to nearby shoppers.

 RFID-based real-time inventory tracking.

6. Agriculture

Objective: Improve productivity and resource use (precision agriculture).

Examples:

 Soil moisture sensors controlling irrigation automatically.

 Drones for crop health imaging.

 Weather data integration for planting/harvesting decisions.

7. Logistics & Supply Chain

Objective: Track goods, optimize delivery, and reduce losses.

Examples:

 GPS trackers in delivery trucks for real-time location.

 Temperature/humidity sensors in perishable goods transport.

 RFID-based product movement monitoring in warehouses.


8. Industry (Industrial IoT / IIoT)

Objective: Monitor machinery, automate production, predict maintenance.

Examples:

 Vibration sensors predicting equipment failure.

 Automated robots in assembly lines.

 Central dashboards showing production KPIs from all machines.

9. Healthcare & Lifestyle

Objective: Enable remote health monitoring and smart wellness solutions.

Examples:

 Wearables tracking heart rate, sleep, oxygen (e.g., Fitbit).

 Remote patient monitoring for chronic illness (e.g., glucose monitors).

 Smart pill dispensers alerting patients.

12.2 IoT Enabling Technologies


These technologies make IoT possible by supporting its infrastructure and operation:
Technology Role in IoT Real-Time Example
Sensors & Actuators Collect data and perform actions Temperature sensor in a smart AC
Enable communication (Wi-Fi, 5G in self-driving cars for low-
Connectivity
ZigBee, 5G, etc.) latency control
Store and analyze large data AWS IoT Core managing data
Cloud Computing
volumes from sensors
Handle and extract insights from Weather data analytics for climate
Big Data
vast data modeling
Artificial Intelligence AI in CCTV cameras detecting
Make intelligent decisions from data
(AI) unusual activity
Blockchain Secure data and ensure transparency Tracking food supply chain origins
Control devices and interface with Raspberry Pi running a smart
Embedded Systems
hardware home controller
13. IoT Platform Design Methodology
13.1 Introduction to IoT Design Methodology
Designing an IoT system involves a step-by-step structured approach to ensure the correct
functioning of devices, data collection, communication, and processing.
The IoT Platform Design Methodology provides a roadmap for building complete IoT
solutions — from idea to deployment. It ensures:

 Efficient design

 Seamless device integration

 Scalable and secure architecture

13.2 Steps in IoT Design Methodology


Here are the seven essential steps involved in designing any IoT-based system:

Step 1: Define the Purpose and Requirements

 Identify the problem you're solving.

 Decide what you want the system to do and who will use it.

✅ Example: Monitor environmental temperature and humidity in a specific region.

Step 2: Select the Sensors and Actuators

 Based on the purpose, choose suitable sensors (to collect data) and actuators (to perform
actions).

✅ Example: Use DHT11 or DHT22 sensor for temperature and humidity.

Step 3: Choose the IoT Communication Protocol

 Select how the device will communicate data.

 Options include Wi-Fi, Bluetooth, Zigbee, LoRa, NB-IoT, etc.

✅ Example: Use Wi-Fi if data needs to be sent to cloud servers frequently.

Step 4: Choose a Microcontroller or Development Board

 Pick a board to connect sensors and handle data transmission.

✅ Example: Use Raspberry Pi or Arduino Uno.

Step 5: Design the Data Flow and Storage


 Decide how data will move through the system and where it will be stored.

✅ Example: Data is collected → transmitted via Wi-Fi → stored in cloud storage like
Firebase or AWS.

Step 6: Develop the Application Layer

 Create dashboards, mobile/web apps to visualize or control the system.

✅ Example: A web dashboard showing real-time temperature and humidity readings.

Step 7: Test, Deploy, and Maintain

 Check the system's performance, fix issues, and maintain it over time.

✅ Example: Run the system for 7 days, track anomalies, and fix sensor errors.

13.3 Case Study: IoT System for Weather Monitoring


Let’s apply the above steps to a real-time case:

Objective: Monitor weather conditions (temperature & humidity) and send real-time data to
the cloud for analysis.

Step Design Element Example


1. Define purpose Track weather parameters in remote areas Used in farming regions
2. Choose sensors DHT11 (Temp. & Humidity) sensor Connected to board
Wi-Fi module (e.g., ESP8266 or inbuilt in
3. Communication Sends data to cloud
Pi)
4. Microcontroller Raspberry Pi or Arduino Controls the system
5. Data flow Sensor → Board → Wi-Fi → Cloud DB Firebase or ThingSpeak
6. Application layer Web dashboard using HTML + JS Graphs for readings
7. Testing & deployment Monitor for 1 week in real world Fix calibration issues
14. IoT Physical Devices and Endpoints
This section focuses on the hardware part of an IoT system. These are the real-world
components that collect data and interact with the environment.

14.1 Basic Building Blocks of an IoT Device


An IoT device typically consists of the following main components:
Component Description Real-Time Example
Sensor collects data (e.g., temperature); Smart thermostat uses temp
Sensor/Actuator Actuator performs actions (e.g., turn fan sensor and actuator to control
on) AC
Small computer on a chip to control
Microcontroller Arduino, ESP32
devices
Communication Used to send/receive data (Wi-Fi, ESP8266 Wi-Fi module sends
Module Bluetooth, etc.) data to cloud
Battery, USB, or solar used to power the A weather sensor in the forest
Power Supply
device uses a solar panel
Interface Units GPIO pins, I2C, UART, etc., for Raspberry Pi uses GPIO pins
Component Description Real-Time Example
connecting components for LEDs
All these work together to form a complete IoT endpoint — a device at the edge of the
network that interacts with the physical world.

14.2 Raspberry Pi: Overview


The Raspberry Pi is one of the most popular devices used in IoT systems. It's a small-sized,
low-cost, full-featured computer that can:

 Run Linux-based operating systems (like Raspbian)

 Connect to the internet via Ethernet/Wi-Fi

 Control sensors and devices using GPIO pins

✅ Use case: In weather monitoring systems, Raspberry Pi can read data from sensors, connect
to the cloud, and display real-time info on a dashboard.

14.3 Raspberry Pi Interfaces


Raspberry Pi provides several types of interfaces for connecting external devices:
Interface Type Description Use Case
GPIO (General Purpose Used to connect LEDs, sensors, Connect motion sensor to
Input/Output) switches detect intrusion
Communication between ICs Connect multiple sensors
I2C (Inter-Integrated Circuit)
using just two wires like accelerometers
High-speed communication Interface with high-speed
SPI (Serial Peripheral Interface)
with peripherals displays
UART (Universal Asynchronous Serial communication (for Connect with GPS module
Receiver-Transmitter) debugging or modules) or GSM modem
For display and peripherals like
HDMI/USB Ports Turn Pi into a mini PC
keyboard/mouse
These interfaces allow the Pi to be a central hub in an IoT system.

14.4 About the Raspberry Pi Board


Here's a quick overview of the components you'll find on a Raspberry Pi board (e.g.,
Raspberry Pi 4):
Component Description
CPU ARM-based processor for computation
RAM Ranges from 1 GB to 8 GB depending on model
USB Ports Connect keyboard, mouse, cameras, etc.
HDMI Port For connecting a display
MicroSD Slot Storage and OS boot device
GPIO Pins 40 pins for connecting external hardware
Camera and Display Ports For video projects
Wi-Fi and Bluetooth For wireless communication
Power Supply Port Uses USB-C or micro-USB for power
✅ Example Project: Using Raspberry Pi to:

 Read sensor data from DHT11 (GPIO)


 Upload data to ThingSpeak (Wi-Fi)

 Show live charts on a web dashboard

15. Internet of Things Security


Topics: Introduction, Overview of Governance, Privacy, and Security Issues
This section focuses on how to protect IoT systems from misuse, data breaches, and
unauthorized access.

15.1 Introduction to IoT Security


The Internet of Things (IoT) connects billions of devices, from smartwatches to smart home
systems, which collect and share data over the internet.
Because these devices are often:

 Small and low-powered

 Connected to public networks

 Not manually monitored

…they become prime targets for cyberattacks.


Why is IoT security important?

 Devices control sensitive systems (e.g., smart locks, healthcare monitors)

 Breaches can lead to data theft, surveillance, or physical damage

 Ensures trust in smart systems like smart cities, factories, and hospitals

15.2 Overview of Governance in IoT


Governance in IoT refers to policies, procedures, and controls used to manage IoT devices
and data safely and legally.
Aspect Description Real-Time Example
Device Lifecycle Secure onboarding, updates, and Smart bulbs receive firmware
Management decommissioning of devices updates over time
Only authorized users or apps can Only the owner can control the
Access Control
access data or control devices smart home system
Ensuring systems follow legal and GDPR for privacy in EU,
Compliance
industry standards HIPAA for health devices
Keeping records of what was accessed Logs in smart surveillance
Audit Trails
and by whom cameras
✅ Governance ensures that IoT is secure, accountable, and legally compliant.

15.3 Privacy in IoT


IoT systems collect personal and behavioral data, which raises major privacy concerns.
Concern Example
Unintentional Data Collection Smart speakers recording conversations accidentally
Users don’t know what data is collected by their fitness
Lack of User Control
trackers
Data Sharing Without Consent Smart appliances selling usage data to advertisers
To ensure privacy:

 Use end-to-end encryption

 Provide user control over data collection

 Implement privacy by design (consider privacy from the start)

15.4 Common Security Issues in IoT


Here are the most common and dangerous vulnerabilities in IoT systems:
Issue Description Example
Default passwords or no Hackers accessing IP cameras with
Weak Authentication
login required default "admin/admin" login
Unencrypted Smart meter sends user usage info
Data sent in plain text
Communication without encryption
Devices not getting A smart TV remains vulnerable to old
Lack of Updates
security patches bugs
Devices can be tampered Attacker opens a smart lock to extract
Physical Attacks
with physically hardware info
Devices hijacked into Smart DVRs used in DDoS attacks on
Botnets (like Mirai)
zombie networks websites

How to Improve IoT Security


Technique Explanation
Use Strong Authentication Two-factor authentication, unique credentials
Encrypt All Communication SSL/TLS protocols to protect data transmission
Update Firmware Regularly Patch known vulnerabilities quickly
Secure APIs Prevent malicious code injection through app interfaces
Monitor Device Behavior Detect unusual traffic or data patterns

✅ Real-World Example:
A smart city has thousands of IoT-enabled traffic lights. Without encryption and
authentication, attackers could manipulate signals and cause accidents. With proper IoT
security, such systems are safeguarded against intrusions.

You might also like