Unit I: Introduction to Wireless Sensor

Networks and its Applications

❖ WSN / Basics of WSN Technology / Overview:

# Overview (covers everything of WSN)

1. Wireless Sensor Network (WSN) is a group of small, wireless devices

called sensor nodes or motes that collect and share data about the
environment.
2. WSN is self-configuring and works without fixed infrastructure,
making it ideal for remote or large-scale monitoring.
3. Each sensor node typically has a sensor, microcontroller, radio
transceiver, and battery for operation.
4. Sensor nodes communicate with each other using radio signals and
pass data through multi-hop communication to a central sink or base
station.
5. WSNs are used to monitor conditions like temperature, humidity,
pressure, sound, motion, and pollutants.
6. The base station (sink) collects data from all nodes and acts as a
bridge between users and the network.
7. WSN nodes perform various tasks such as data sensing, aggregation,
routing, synchronization, and target tracking.
8. WSN nodes are resource-constrained with limited power, processing
capability, storage, and communication bandwidth.
 9. Sensor nodes can operate in either continuous mode or event-driven
mode depending on the application.
10. WSN technology is widely used in industrial automation, smart
cities, environmental monitoring, defence, and healthcare systems.

❖ Characteristics of WSN:

1. Dense Node Deployment

Sensor nodes are placed very close to each other in the area of
interest to ensure good data coverage.
2. Battery-Powered Nodes
Sensor nodes usually run on batteries and are placed in areas where
changing batteries is hard.
3. Limited Resources
Nodes have very low energy, limited processing power, and small
memory capacity.
4. Self-Configurable
Nodes organize themselves into a network automatically after
deployment, without human help.
5. Application Specific
WSNs are designed for specific tasks (like pollution monitoring,
temperature sensing, etc.). Network design depends on the use case.
6. Unreliable Nodes
Nodes are often placed in rough environments, so they can get
damaged or stop working easily.
7. Frequent Topology Change
The network structure keeps changing due to node failures, energy
loss, or new nodes being added.
8. No Global ID
Because there are many sensor nodes, giving each a unique global ID
is hard and increases overhead.

❖ Classification of WSN:

1. Static and Mobile WSN

• Static WSN: Sensor nodes are fixed and do not move.
 • Mobile WSN: Sensor nodes can move (used in applications like
animal monitoring).

2. Deterministic and Nondeterministic WSN

• Deterministic WSN: Sensor node positions are pre-planned and
fixed.
• Nondeterministic WSN: Sensor node positions are random due to
harsh environments, requiring complex control systems.

3. Single Base Station and Multi Base Station

• Single Base Station: One base station is placed close to the sensor
region, all nodes communicate through it.
• Multi Base Station: Multiple base stations are placed in different
locations. Sensor nodes send data to the nearest one.

4. Static Base Station and Mobile Base Station

• Static Base Station: The base station is fixed near the sensing area.
• Mobile Base Station: The base station moves around to balance the
data load on sensor nodes.

5. Single-hop and Multi-hop WSN

• Single-hop WSN: Sensor nodes send data directly to the base
station.
• Multi-hop WSN: Data is sent through other nodes (like cluster heads)
to save energy.

6. Self Reconfigurable and Non-Self Configurable WSN

• Self Reconfigurable: Nodes can organize and manage the network on
their own.
• Non-Self Configurable: Nodes depend on an external control unit to
collect and manage data.

7. Homogeneous and Heterogeneous WSN

• Homogeneous WSN: All sensor nodes have the same energy,
processing, and storage capability.
• Heterogeneous WSN: Some nodes have higher power and
capabilities compared to others. Processing and communication
tasks are distributed accordingly.

❖ Commercial and Scientific Approach of WSN:

• Commercial Approach of WSN:

• This refers to how Wireless Sensor Networks (WSNs) are used in real-
world industries and services for automation, monitoring, safety, and
efficiency.
• It focuses on improving daily life, business operations, and
infrastructure through smart technologies.
1. Smart Homes and Buildings:
• Used for automation like lighting, heating, cooling, and security
systems.
2. Industrial Monitoring:
• Monitors machinery health, factory automation, and production line
efficiency.
3. Environmental Monitoring:
• Detects pollution levels, temperature, humidity, and weather
conditions.
4. Agricultural Applications:
• Tracks soil moisture, crop health, and optimizes irrigation.
5. Health Care Monitoring:
• Supports patient health tracking, remote diagnostics, and elderly
care systems.

• Scientific Approach of WSN:

• This refers to how WSNs are used in research and academic fields
to gather precise data, conduct experiments, and monitor
environmental or biological phenomena.
• It helps scientists in data-driven analysis, simulations, and
discoveries in various domains like space, climate, and health.
1. Remote Environmental Research:
• Collects data from deserts, glaciers, oceans, or volcanoes.
2. Wildlife and Habitat Monitoring:
• Studies animal movement and natural ecosystems.
3. Climate Change Studies:
• Gathers long-term data on temperature, CO₂, and weather patterns.
4. Medical Research:
• Monitors patient vitals in experimental treatments and trials.
5. Structural Health Monitoring:
• Tracks stress or damage in bridges, tunnels, and buildings.

❖ Architecture of WSN / layered network architecture:

• The most common wireless sensor network architecture

follows the OSI architecture Model.
• The architecture of the WSN includes five layers and three
cross layers.
• Mostly in sensor n/w, we require five layers, namely application,
transport, n/w, data link & physical layer.
• These layers of the WSN are used to accomplish the n/w and
make the sensors work together to raise the complete efficiency
of the network.
• The architecture used in WSN is sensor network architecture.
• There are 2 types of wireless sensor architectures: Layered
Network Architecture, and Clustered Architecture.
1. Application Layer
• Provides the interface for user-level tasks and applications.
• Supports services like:
o Query dissemination
o Node localization
o Time synchronization
o Network security
• Examples:
o SMP (Sensor Management Protocol): Manages tasks like
moving and scheduling nodes, syncing, etc.
o SQDDP: Helps users send queries and get data from the
network.

2. Transport Layer
• Ensures end-to-end data delivery between sensor nodes and the
sink.
• Handles reliability, but traditional transport protocols like TCP are not
suitable for WSNs due to energy and storage limits.
• WSN-specific protocols are designed for energy efficiency and
minimal communication overhead.

3. Network Layer
• Responsible for routing data from source nodes to sink nodes.
 • Can use single-hop (direct) or multi-hop (via intermediate nodes)
communication.
• Must handle:
o Efficient path selection
o Energy savings
o Long-range vs. short-range communication trade-offs

4. Data Link Layer

• Manages data framing, error control, medium access, and data
transmission.
• Ensures reliable point-to-point and point-to-multipoint
communication.
• Key feature: MAC (Medium Access Control) protocols
o Share communication medium efficiently
o Balance energy use, throughput, and delay

5. Physical Layer
• Converts bit streams to signals suitable for transmission.
• Deals with:
o Medium and frequency selection
o Carrier generation
o Signal modulation and detection
o Data encryption
• Also handles electrical and mechanical interfaces of sensors.

❖ Sensor Node Structure / Block diagram of sensor node:

 • A wireless sensor node is the core component of a Wireless Sensor
Network (WSN).
• Each node is equipped with essential components that allow it to
sense, process, and communicate data.
• Due to energy constraints, especially in battery-powered nodes,
efficient operation is vital for prolonged network lifetime.
• A typical wireless sensor node consists of four main components:

1. Sensing Unit:

• The sensing unit consists of various types of sensors such as:

o Thermal sensors
o Magnetic sensors
o Vibration sensors
o Chemical sensors
o Biosensors
o Light sensors
• These sensors detect physical parameters from the surrounding
environment.
• The sensors generate analog signals, which are converted into digital
signals using an Analog-to-Digital Converter (ADC).
• These digital signals are then forwarded to the processing unit for further
analysis.

2. Processing Unit:

• This is the central unit responsible for executing tasks and controlling the
operations of other components.
• It consists of a microcontroller or microprocessor.
• It processes the data collected by the sensing unit using pre-loaded
algorithms and decision-making codes.
• The processor is responsible for:
o Managing communication with other nodes
o Running sensing applications
o Controlling energy-efficient operations
• The energy usage of the processor depends on the complexity of tasks
being performed.

3. Communication Unit:

• The communication unit is responsible for transmitting and receiving data

between sensor nodes and the base station.
• It typically consists of an RF transceiver.
• This unit handles wireless communication, enabling nodes to work
collaboratively within the network.
• The communication unit can operate in four modes:
1. Transmit – Sending data to other nodes or the base station
2. Receive – Receiving data from other nodes
3. Idle – On but not transmitting or receiving
4. Sleep – Minimal power consumption mode

4. Power Unit:

• The power unit supplies energy to all the components of the sensor node.
• It usually consists of batteries or energy harvesting systems (such as solar
panels).
• Since recharging or replacing batteries in many applications is difficult,
energy efficiency is critical.
• Managing power consumption is crucial to ensure a long network
lifetime, especially in applications where nodes transmit data only
occasionally.

• Key Issues in Sensor Node Structure:

1. Power Supply
o Limited battery life.
o Hard to recharge or replace in remote areas.
2. Processing Power
o Small microcontrollers with low speed and memory.
o Limited ability to handle complex tasks.
3. Memory
o Very small RAM and storage.
o Difficult to store large data or programs.
4. Communication
o Wireless communication consumes a lot of energy.
o Limited range and data rate.
5. Sensing Accuracy
o Sensor quality affects accuracy.
o Needs calibration and may get affected by the environment.
6. Size and Cost
o Must be small and low-cost.
o Limits the choice of components.
7. Security
 o Low processing power makes it hard to use strong encryption.
o Vulnerable to attacks.

❖ Basic Sensor network architectural elements:

• Sensor networks consist of both hardware and software

components.
• These components work together to sense data from the
environment, process it, and transmit it efficiently while conserving
energy.

• Hardware Elements
The basic hardware components of a wireless sensor network
include:
1. Sensor Unit-
• Detects data (like temperature, gas, sound, light).
• Can be passive (low power, like humidity sensor) or active (high
power, like radar).
2. Processing Unit-
• Small microcontroller to process the sensed data.
3. Memory-
• Stores program and temporary data.
4. Communication Unit-
• Wireless module (like ZigBee, Wi-Fi, Bluetooth) to send/receive data.
5. Power Unit-
• Battery or solar panel.
• Most energy is used in communication, so power-saving is important.
6. ADC (Analog to Digital Converter)-
• Converts analog signals from sensors into digital signals for
processing.

• Software Elements
The software architecture of sensor networks is designed to handle
limited resources and dynamic environments. It consists of:

1. Operating System-
• Special lightweight OS like TinyOS.
• Uses very less memory and is energy efficient.
2. Middleware-
• Helps with coordination between nodes (like time sync, data sharing,
etc.)
3. Transport Protocols-
• For secure, low-energy, and reliable data sending.
4. Routing Protocols-
• Data-centric routing: Routes based on data type, not node address.
• Includes in-network data aggregation to reduce extra messages.
5. Computation & Data Processing-
• Nodes do basic processing, fusion, and filtering of data themselves.
• Saves energy and reduces unnecessary data transfer.
6. Data Management-
• Stores data locally or sends important info to a central sink.
• Supports queries, indexing, and global summaries.
7. Security-
• Lightweight encryption, signatures to keep data safe and accurate.

❖ ISSUES AND CHALLENGES IN DESIGNING WSN / factors

influencing WSN:

1. Random Node Deployment (No Fixed Topology)-

• Sensor nodes are scattered randomly, so there’s no neat network
structure.
• Makes planning and communication hard.
2. Very Limited Resources-
• Nodes have low memory, less computing power, and limited battery.
• Can't perform heavy tasks like a regular computer.
3. Difficult Maintenance-
• WSNs are often deployed in harsh or remote areas.
• So, repairing or replacing nodes is tough.
4. Unreliable Communication-
• Wireless signals face interference, signal drops, or delays.
• Makes data transfer unreliable.
5. Power is Limited and Non-Rechargeable-
• Most sensor nodes work on small batteries.
• In many cases, they can’t be recharged or replaced.
6. Security Issues-
• Sensor networks are open to the air, so hacking or data theft is
possible.
• Ensuring secure communication is hard due to resource limits.
7. Node Failures and Network Changes-
• Nodes can die or stop working, and new ones might be added.
• Keeping the network running smoothly is a big challenge.

❖ Wireless Sensor network environment:

A wireless network connects devices without cables. It uses radio

waves to send and receive data. It’s used in homes, offices, cities,
and sensor networks (WSNs).

• Main Features of a Wireless Network-

1. No Wires Needed
o Data is sent through the air using radio waves.
o No physical cables are needed for communication.
2. Supports Connectivity
o Physical Connectivity: Devices connect using wireless signals
over short or long distances.
o Logical Connectivity: Maintains the structure of the network
and enables multi-hop routing.
• Key Challenges in Wireless Sensor Networks (WSNs)-
1. Limited Power
o Sensor nodes have small batteries that cannot be recharged or
replaced.
o Power-saving is important.
2. Weak Communication
o Limited speed (bandwidth)
o Noisy or unreliable signals
o Security concerns
3. Less Computing Power
o Sensor nodes have limited memory and processing power.
o They can't run complex algorithms.
4. Uncertain Data
o Data may be mixed with noise or affected by environment.
o Sensor placement may impact accuracy.

• Key Components of a Wireless Network--

1. Wireless Devices
o End Devices: Smartphones, laptops, tablets, IoT devices, and
sensors.
o Adapters: Devices like Wi-Fi dongles that help non-wireless
devices connect to a wireless network.
2. Access Points (APs)
o Access Points: Connect wireless devices to a wired network.
o Router: Directs data between the wireless network and the
internet. In homes, a router usually has a built-in access point.
3. Communication Protocols
o Wi-Fi (IEEE 802.11): Used for home and office networks.
o Bluetooth: Short-range communication (like headphones and
smartwatches).
o Zigbee and Z-Wave: For low-power devices in home
automation.
o Cellular Networks (3G, 4G, 5G): For mobile devices over large
areas.
4. Wireless Security
o Encryption: Protects the data being transmitted (e.g., WPA2,
WPA3).
 oAuthentication: Only authorized devices can connect (e.g.,
passwords, certificates).
5. Network Topologies
o Infrastructure Mode: Devices connect through a central router
or access point.
o Ad-Hoc Mode: Devices communicate directly with each other.

❖ Sensor Taxonomy:

• Sensor taxonomy refers to the classification of sensors based

on various characteristics such as the type of data they
measure, their power source, functionality, mobility,
communication mode, and application area.
• This classification helps in choosing the appropriate sensor for
a specific purpose in a wireless sensor network.
1. Based on the Physical Quantity Measured
This is the most common way to classify sensors. Sensors are chosen
based on the type of physical parameter they are designed to sense.
• Temperature sensors measure heat or temperature. Example: LM35,
DHT11.
• Pressure sensors detect force or pressure applied on a surface.
• Light sensors measure the intensity of light. Example: Light
Dependent Resistor (LDR).
• Humidity sensors measure the moisture content in the air.
2. Based on Power Source
Sensors can be categorized by whether they require an external power
source or not.
• Active sensors need an external power source to operate. For
example, ultrasonic sensors send out a signal and measure its
reflection.
• Passive sensors do not require external power. They detect natural
energy such as infrared or sound from the environment.
Thermocouples are an example.
3. Based on Output Type
Sensors are also classified by the type of output they generate.
 • Analog sensors produce a continuous signal that varies over a range.
Example: A temperature sensor giving different voltages for different
temperatures.
• Digital sensors give a binary output, usually either 0 or 1,
representing off or on conditions. Example: Digital infrared sensors.
4. Based on Communication Type
Sensors may communicate data through wired or wireless means.
• Wired sensors use cables or physical connections to transmit data.
These are rarely used in wireless networks.
• Wireless sensors use radio waves to send data without any physical
connection. They are commonly used in WSNs and can use
technologies like Wi-Fi, Zigbee, LoRa, or Bluetooth.
5. Based on Application Area
Sensors can also be categorized by where they are used.
• In environmental monitoring, sensors like temperature, humidity,
and gas sensors are used.
• In healthcare, sensors such as ECG, pulse, and temperature sensors
are common.
• In industrial monitoring, sensors for vibration, gas, and pressure are
used.
6. Based on Sensing Technique
This classification depends on how the sensor detects and converts the
physical quantity into electrical signals.
• Optical sensors detect light or colour changes, such as LDRs.
• Mechanical sensors sense movement, pressure, or strain.
Accelerometers fall in this category.
• Thermal sensors measure temperature using heat detection.
Thermistors are a common example.

❖ Mote Anatomy:
A mote is a small, self-contained sensor node in a Wireless Sensor
Network (WSN). It performs three main functions:
1. Sensing: Collects data from the environment (e.g., temperature,
humidity, pressure).
2. Processing: Processes data minimally (e.g., simple calculations).
3. Communicating: Transmits the processed data to other nodes or a
central system in the network.

• Key Components of a Mote:

1. Sensor(s):
o Function: Measures environmental factors (e.g., temperature,
light, humidity).
o Examples: Temperature sensor, light sensor, motion sensor.
2. Analog-to-Digital Converter (ADC):
o Function: Converts the analog signals from sensors into digital
values so that the microcontroller can process them.
3. Microcontroller:
o Function: The "brain" of the mote. It controls everything,
including processing sensor data, managing power, and
handling communication.
o Key Role: Executes logic for data processing and network
communication.
4. Memory:
 o Function: Stores the program, sensor data, and temporary
information (e.g., variables or intermediate results).
o Types: Usually includes both RAM (for temporary storage) and
Flash memory (for storing program code and persistent data).
5. Transceiver:
o Function: A communication module that allows the mote to
send and receive data wirelessly to other nodes in the network.
o Technology: Typically uses radio communication, such as Wi-
Fi, Bluetooth, Zigbee, or LoRa.
6. Power Source:
o Function: Powers the mote. Most motes are battery-operated
but may also include energy-harvesting methods like solar
panels to extend their operation.

• Important Aspects of Mote Design in WSN:

1. Low Power Consumption:
o Motes are usually battery-powered, so it's important to
minimize energy usage.
o Motes use sleep modes, optimize data transmission, and have
power-saving protocols to reduce energy consumption.
2. Small Size:
o Motes are compact and lightweight, making them easy to
deploy in large quantities over wide areas (e.g., across a forest
or building).
3. Robustness:
o Motes must be durable to withstand different environmental
conditions, such as extreme temperatures, humidity, or
physical impacts, depending on where they are placed.

❖ Application of WSN:

1. Military Applications of WSN:

1. Battlefield Surveillance – Monitor enemy movements and detect
intrusions.
2. Border Monitoring – Track illegal crossings or smuggling activities.
3. Landmine Detection – Deploy sensors to detect buried explosives.
4. Enemy Tracking – Follow enemy vehicle or troop movements.
 5. Targeting Systems – Help weapons systems lock onto accurate
targets.
6. Soldier Health Monitoring – Track soldier’s health status in real-time.
7. Remote Area Communication – Set up ad-hoc networks in combat
zones.
8. Environmental Monitoring – Detect chemical, biological, or
radiological threats.

2. Civil Applications of WSN:

1. Traffic Monitoring – Measure traffic flow and control signal timing.
2. Smart Parking – Show available parking spots using sensors.
3. Structural Health Monitoring – Detect cracks or damage in bridges
and buildings.
4. Disaster Management – Monitor earthquakes, floods, and landslides.
5. Water Quality Monitoring – Check pollution levels in lakes and rivers.
6. Waste Management – Detect bin levels to optimize garbage
collection.
7. Public Safety – Monitor crowd movement in public events.
8. Air Quality Monitoring – Detect harmful gases and pollution levels in
cities.

3. Medical/Health Applications of WSN:

1. Patient Monitoring – Track heart rate, temperature, and BP remotely.
2. Emergency Response – Alert doctors/nurses if a patient needs urgent
care.
3. Elderly Care – Monitor movement and detect falls of senior citizens.
4. Hospital Asset Tracking – Locate wheelchairs or medical equipment.
5. Implant Monitoring – Track performance of devices like pacemakers.
6. Body Area Networks (BAN) – Tiny sensors on the body collect health
data.
7. Health Data Logging – Collect long-term health trends for diagnosis.
8. Infection Control – Monitor hygiene compliance in hospitals.

4. Commercial Applications of WSN:

1. Smart Homes – Control lights, doors, temperature using sensors.
2. Smart Offices – Monitor energy use and room occupancy.
3. Inventory Management – Track stock in real-time using sensor tags.
 4. ATM Security – Detect tampering or unauthorized access.
5. Retail Analytics – Monitor customer foot traffic patterns.
6. Building Automation – Control HVAC, lighting, and fire alarms.
7. Smart Hotels – Manage lighting and room service automatically.
8. Smart Shopping Carts – Detect product selection and automate
billing.

5. Industrial Applications of WSN:

1. Machine Monitoring – Detect vibrations or overheating in machinery.
2. Predictive Maintenance – Alert when machines need service before
failure.
3. Energy Management – Optimize power usage in factories.
4. Production Line Monitoring – Track speed, errors, or stops in the line.
5. Safety Monitoring – Detect toxic gas leaks or temperature rise.
6. Inventory Control – Monitor raw material and product movement.
7. Remote Equipment Control – Control machines from far-off
locations.
8. Quality Control – Check parameters like temperature, humidity in
real-time.

6. Agricultural Applications of WSN:

1. Soil Moisture Monitoring – Help decide when to irrigate.
2. Weather Monitoring – Track rainfall, temperature, humidity.
3. Pest Detection – Detect insect movement or plant disease early.
4. Crop Health Monitoring – Use sensors and drones to check crop
condition.
5. Greenhouse Automation – Control light, temperature, and irrigation.
6. Precision Farming – Apply fertilizers/pesticides only where needed.
7. Water Level Monitoring – Check tank or canal levels automatically.
8. Livestock Tracking – Monitor animal movement and health.

❖ Various WSN Standards / Various Sensor network

technologies in WSN:
1. ZigBee
• Made for small devices that talk wirelessly.
• Uses very low power – good for long battery life.
• Used in smart homes and industrial machines.
 • Slower than Wi-Fi, but more energy-saving.
• Range: around 100 meters.
• Cheap and reliable for many connected sensors.

2. Wi-Fi
• Same as what we use for internet at home.
• Sends data very fast.
• Uses more power, so battery drains faster.
• Good for things like security cameras, phones, or laptops.
• Range: around 50 meters indoors.
• Easy to connect to internet.

3. Lora WAN
• “LoRa” means Long Range.
• Sends small amounts of data over big distances (up to 10 km).
• Uses very little power – batteries can last years.
• Can work without Wi-Fi or mobile network.
• Best for rural or wide-area WSNs.

4. RFID
• Used to identify and track objects.
• Works when a scanner comes close to a tag (like an ID card).
• Very short range – usually few cm to a few meters.
• One-way communication – tag sends ID to reader.
• Very cheap and simple.

5. 6LoWPAN
• Helps tiny sensors talk to the internet using IPv6.
• Made for small, low-power devices.
• Adds internet features to things like ZigBee.
• Helps sensors work like websites/devices online.
• Uses less power and works well with limited memory.

6. Cellular (3G, 4G, 5G, NB-IoT)

• Same network as your phone SIM card.
• Can send data from anywhere with signal.
• Perfect for tracking vehicles, smart meters, or remote areas.
• Reliable and secure.
• Needs SIM cards and data plans (can cost more).
• Great for real-time and far-away data.

❖ WSN Vs Traditional Wireless Adhoc network:

Unit V: Operating Systems and Hardware
for Wireless Sensor Networks

➢ INTRODUCTION:

• The operating system in WSN helps control sensing, data processing,

communication, and power use.
• It manages all parts of the hardware, so they work smoothly without
problems.
• The OS makes it easier for software to use the hardware by hiding
complex hardware details.
• Normal OS used in computers have more power, but WSN OS works
with small, low-power devices.
• WSN OS must be small and efficient because sensor nodes have
limited memory and slow processors.
• It must save energy because sensor nodes often run on battery.
• The OS must match the needs of the WSN application it supports.
• Special design is needed to make the OS work well in tiny sensor
devices.

➢ Operating System Design Issues for WSNs:

1. Process Management and Scheduling

WSN OS must handle tasks efficiently with minimal switching and
 copying to save energy. Real-time schedulers like EDF can be used,
but with fewer processes.
2. Memory Management
Sensor nodes have very little memory, so sharing memory between
tasks is better than giving each task its own memory like in traditional
OS.
3. Kernel Model
Event-driven and Finite State Machine (FSM) models are suitable
because WSNs work on events like data reception, sensor activation,
or low battery alarms.
4. Application Program Interface (API)
APIs must be simple and modular to allow easy access to hardware
and enable flexible application development.
5. Code Upgrade and Reprogramming
The OS should allow remote updates and reprogramming of sensor
nodes to change functionality or improve energy efficiency after
deployment.
6. File System Absence
Most sensor nodes don’t have external storage, so WSN OSs don’t
include traditional file systems and must manage data without one.
7. Power Management
The OS must manage power smartly, such as putting the system to
sleep when idle and waking it up on important events, to extend
battery life.

➢ Different OS used for WSN:

• TinyOS:

1. TinyOS is a lightweight OS made for Wireless Sensor Networks

(WSNs) that allows direct access to hardware when needed.
2. It uses an event-driven model, meaning it responds quickly to events
like receiving data or sensing something, which saves energy.
3. TinyOS supports high concurrency using very little memory, making it
ideal for small sensor nodes.
4. It avoids using stacks for tasks, which reduces memory usage and
increases speed compared to traditional thread-based OSes.
5. The CPU sleeps when idle, saving power, and wakes up only when a
task or event occurs.
6. TinyOS uses a simple FIFO (First-In-First-Out) scheduler to manage
tasks efficiently with very low memory requirements.
7. Each TinyOS component has four parts: command handlers, event
handlers, a frame (for memory), and tasks.
8. Commands are non-blocking and return quickly, improving
performance even when waiting for hardware actions.
9. TinyOS components are modular, meaning they can easily connect
with each other like building blocks using function calls.
10. Three types of components exist in TinyOS:
• Hardware abstraction (e.g., sensors, radios)
• Synthetic hardware (adds extra functionality to real hardware)
• High-level software components (used for advanced tasks and logic)

• Mate:

1. Mate works on top of TinyOS and is one of its components.

2. It is a byte-code interpreter, designed to make TinyOS easier for
non-experts.
3. Programs are stored in capsules, each with 24 instructions, and
each instruction is 1 byte.
4. Capsules include type and version info, making it easy to update
code across the network.
5. Mate supports hop-by-hop code injection, allowing the entire
network to be programmed wirelessly.
6. There are 4 types of capsules: message send, message receive,
timer, and subroutine.
7. Mate uses a beaconless ad hoc routing protocol (BLESS) and can
create new routing protocols.
8. Mate can be triggered by events and acts as both a virtual machine
and a tool to manage the network.

• MANTIS:

1. MANTIS is a small operating system that helps quickly deploy

applications in sensor networks.
 2. It has a layered structure, including multithreading, task
scheduling, and network protocols.
3. The MANTIS kernel is very small, using less than 500 bytes of
RAM.
4. MANTIS is written in C, making it easy for programmers to use.
5. Each thread in MANTIS uses fixed memory and stores thread
info in a global table.
6. MANTIS schedules threads based on priority, and it switches
tasks when the timer interrupts.
7. It uses a 4-layer network protocol, including application,
network, MAC, and physical layers.
8. MANTIS supports features like reprogramming, testing
environments, and remote access to monitor nodes.

• EYES OS:

1. EYES OS is small in memory and coding, designed for power

efficiency.
2. It uses an event-driven model and task scheduling with FIFO,
priority, or deadline-based methods (like EDF).
3. Tasks are triggered by events and run without blocking,
ensuring smooth performance.
4. EYES OS provides an API for both local and network
components to access node data and network details.
5. The local component allows access to sensor data, resource
availability, and setting parameters.
6. The network component helps in data transmission,
reception, and retrieving network information.
7. EYES OS enables efficient code distribution, minimizing
communication and resource usage during updates.
8. The code update process includes four steps: initialization,
code building, verification, and loading, with multiple update
options.

• PIC OS:
1. PicOS is designed for microcontrollers with limited RAM (e.g., 4 kB).
2. All tasks in PicOS share the same global stack and act as coroutines
with multiple entry points.
3. Tasks in PicOS work as Finite State Machines (FSMs), triggered by
events.
4. CPU cycles are multiplexed among tasks, but tasks can only be
preempted at FSM state boundaries.
5. PicOS is lightweight and supports multitasking but may not be ideal
for real-time applications.

➢ TinyOS in detail:

• TinyOS is a lightweight operating system specifically designed

for Wireless Sensor Networks (WSNs).
• It is built to run efficiently on resource-constrained hardware
platforms, like sensor nodes that have very little memory and
limited processing power.
• Key Features of TinyOS:
1. Small Memory Footprint
• TinyOS is designed to use very little memory, ideal for tiny sensor
nodes.
• It avoids complex features like file systems.
• Uses only static memory allocation to keep the system simple and
predictable.
2. Simple and Layered Design
• Components are arranged in layers for better organization:
o Lower layers interact directly with hardware (like sensors,
radios).
o Higher layers are designed for the application logic.
• This helps in creating modular and manageable systems.
3. Component-Based Architecture
• TinyOS applications are built using components, each handling a
specific task.
• Components are “wired” together using the nesC programming
language.
• Some components are purely software, while others wrap around
hardware functions.
4. Types of Components
• Hardware Abstraction Components: Directly handle hardware like
sensors, radios, etc.
• Synthetic Hardware Components: Simulate complex hardware
behavior and are built over the hardware abstraction layer.
5. Example – Field Monitor Application
• In the Field Monitor application, sensor nodes collect data like
temperature or light.
• They send this data to a base station using ad hoc routing.
• Components communicate using commands, events, and tasks.
• Working of TinyOS:
• Each application is built into the operating system and uses only the
required components.
• Components are connected in a way that events flow from hardware
to software and actions (commands) flow from software to hardware.
• The OS handles communication using event-driven mechanisms,
which are lightweight and fast.
• Advantages of TinyOS:
1. Low Code & Data Requirement:
o Perfect for small devices; it uses minimal RAM and ROM.
2. Fast Event Handling:
o Events (like sensor triggers) are processed quickly.
o Tasks are posted and context switches happen at high speed.
3. Efficient Modularity:
 o Code is highly modular—only necessary components are
included.
o Easy to manage and extend the system with new
functionalities.

➢ MANTIS in detail:

• MANTIS (Multimodal system for Networks of In-situ wireless Sensors)

is a multithreaded embedded OS for Wireless Sensor Networks
(WSNs).
• Designed for small devices with limited resources.
• Written in standard C – simple and easy for programmers.
• Enables quick deployment of WSN applications.
• Key Features:
1. Multithreaded Scheduling:
o Supports multiple threads.
o Uses pre-emptive scheduling with time slicing.
o Threads run independently.
2. Memory Efficient:
o Kernel uses less than 500 bytes of RAM.
o Each thread gets fixed memory.
o Thread info stored in a global thread table.
3. Thread Management:
o Priority-based scheduler with round-robin within same priority.
o Timer interrupt triggers context switching.
o Device drivers handle other interrupts.
4. Layered Network Stack:
o Stack includes Application, Network, MAC, Physical layers.
o Each layer is a user-level thread.
o Uses standard API for communication between layers.
5. Advanced Features:
o Dynamic binary update (reprogram nodes remotely).
o Remote shell and command server to inspect memory/status.
• Working of MANTIS OS:
• Follows a layered structure for clarity and modularity.
• Supports I/O synchronization using mutexes.
• Scheduler runs threads based on priority and time slicing.
• Network protocol stack works through threads for each layer.
• All parts (kernel + scheduler + stack) are compact and efficient.
• Advantages:
1. Easy to Program:
o Uses standard C, known to most developers.
2. Low Resource Usage:
o Ideal for low-RAM environments.
3. Modular and Flexible:
o Threaded structure allows easy management of tasks and
networking.
4. Quick Deployment:
o Good for fast testing and prototyping of WSN applications.
5. Remote Access:
o Allows reprogramming and status monitoring remotely.

➢ MATE OS in detail:
 • Mate is a byte-code interpreter that runs on top of TinyOS.
• Designed for non-expert programmers to quickly and easily
program sensor networks.
• Acts as a virtual machine and execution environment for
applications, especially useful for UC-Berkeley motes that
lack hardware protection.
• Key Features:
1. Capsule-Based Code:
o Programs split into capsules (24 one-byte instructions).
o Includes version info for easy updates.
2. Hop-by-Hop Programming:
o Capsules self-deploy across the network.
o Newer versions get installed automatically.
3. BLESS Routing Support:
o Uses beaconless ad hoc routing.
o Allows custom routing protocols too.
4. Event-Driven:
o Runs on event triggers, ideal for sensors.
5. Four Capsule Types:
o Message send, Message receive, Timer, Subroutine.
• Working:
• Mate runs on TinyOS, interpreting capsule bytecode.
• Capsules spread and update the network via hop-by-hop injection.
• Event-driven tasks manage sensor operations efficiently.
• Advantages:
• Simple programming for beginners.
• Quick deployment over the whole network.
• Supports routing and modular updates.
• Memory-efficient (1-byte instructions).
• Useful for sensor node management.

➢ MAGNET OS in detail:

• MagnetOS is a distributed adaptive operating system designed

for energy-efficient application adaptation in wireless sensor
networks.
• Unlike other OSes, it supports network-wide adaptation
without burdening the application itself.
• Key Features:
1. Application Adaptation:
o Automatically adapts to changes in node resources.
o Ensures stable and efficient performance.
2. Energy Conservation:
o Uses power-aware algorithms to reduce energy use.
o Extends network lifetime by optimizing communication.
3. Single System Image (SSI):
o Appears as one unified Java Virtual Machine across the
network.
o Makes programming and object management easier.
4. Static & Dynamic Components:
o Static: Rewrites bytecode and adds adaptation instructions.
o Dynamic: Handles monitoring, object creation, and migration.
5. Object Placement Control:
o Programmers can manually place objects or override
automatic decisions.
o Ensures flexibility in application design.
• Working of MagnetOS:
• MagnetOS provides a unified Java-based platform for all nodes (SSI).
• It rewrites applications at the byte-code level to add energy-saving
features.
• It uses NetPull (hop-by-hop) and NetCenter (multi-hop) algorithms to
move app components and reduce energy use.
• Unlike fixed endpoint routing, it moves endpoints to save energy.
• Advantages of MagnetOS:
• Automatic adaptation reduces app complexity.
• Efficient energy use increases node and network lifetime.
• Scalable design supports large sensor networks.
• Programmers have control and flexibility over object placement.

(Hardware: Examples like)

➢ EYES Nodes in detail:

• EYES OS is an embedded operating system specifically designed for

Wireless Sensor Networks (WSNs).
• It is built with the goal of being memory-efficient, power-aware, and
capable of distribution and reconfiguration.
• The system is designed to perform tasks like sensing, computation,
and communication with minimal energy consumption, making it
ideal for long-term use in sensor networks.
• Key Features:
1. Event-Driven Model:
o Tasks are triggered by specific events like sensor data changes.
o Once an event occurs, it initiates the task.
2. Task Scheduling:
 o Supports different scheduling methods:
▪ FIFO (First In, First Out)
▪ Priority-based scheduling
▪ Deadline-based scheduling (e.g., Earliest Deadline First -
EDF)
3. Low Power Consumption:
o After completing a task, the system enters sleep mode to save
energy.
4. API for Local and Network Functions:
o Local API: Access sensor node data and resource information.
o Network API: Allows sending/receiving data and retrieving
network info.
5. Node Localization & Boot-Time Functions:
o Boot-Time Functions: Upload software modules during boot.
o Node Localization: Provides location info of nodes in the
network.
• How It Works:
1. Event-Triggered Tasks:
o Tasks are performed only when triggered by specific events
(e.g., sensor data changes).
2. Task Scheduling:
o Once an event happens, a task is scheduled based on the
selected method (FIFO, priority, or deadline-based).
3. Computation and Sleep Mode:
o After completing a task, the system enters sleep mode to save
power until the next event triggers.
4. Communication:
o EYES OS facilitates data transmission and reception between
sensor nodes.
• Advantages:
1. Memory Efficient:
o Designed for low memory usage, making it suitable for small
sensor nodes.
2. Energy Efficient:
o Its event-driven model ensures low energy consumption,
extending battery life.
3. Flexible Task Management:
 o Multiple task scheduling methods allow efficient use of
resources.
4. Modular and Scalable:
o Functions can be adapted for different applications and
network sizes.
5. Easy Network Communication:
o Simple API for handling communication between sensor
nodes.

➢ BT Nodes in detail:
• BT nodes are wireless sensors that use Bluetooth for short-range
communication (up to 100 meters).
• They connect with devices like gateways, mobile phones, and PCs.
Key Features:
• Wireless Communication: Uses Bluetooth protocol for data
exchange.
• Low Power: BLE (Bluetooth Low Energy) saves battery—great for
WSNs.
• Data Sharing: Sends sensor data to gateways or other nodes.
• Topologies:
o Piconet: One master, multiple slaves.
o Scatternet: Multiple connected piconets.
• How BT Nodes Work:
• Bluetooth Stack: Includes radio, baseband, L2CAP, and application
layers.
• Device Discovery: Finds nearby devices using inquiry and connects
via pairing.
• Data Transmission: Uses L2CAP for reliable data sending.
• Power Saving: Uses idle and low-power modes to save energy.
• Network Interface: Can connect to Wi-Fi, ZigBee, or cellular for wider
access.
• Advantages:
• Short-Range, Low Power
• Easy Integration with smartphones/laptops
• Scalable – add more nodes easily
• Secure – supports encryption and authentication
• Applications:
• Environment Monitoring – temperature, humidity sensors
• Healthcare – wearable health devices
• Industry – factory automation
• Smart Homes – automated lights, thermostats
• Asset Tracking – track goods in warehouses

➢ Scatter web in detail:

• A Scatter Web is formed by connecting multiple Bluetooth piconets.

• A piconet has 1 master and up to 7 slaves.
• A bridge node connects two or more piconets.
• Why Use Scatter Web in WSNs?
• To connect more sensor nodes beyond a single piconet limit.
• To cover larger areas using Bluetooth.
• To save power with Bluetooth Low Energy (BLE).
• How It Works:
1. Nodes form small groups (piconets).
2. Some nodes act as bridges between piconets.
3. Data moves across the network via bridge nodes.
4. Final data reaches a gateway or base station.
• Advantages:
• Scalable – Add more nodes easily.
• Energy-efficient – Uses BLE.
• Wider range – Covers large areas.
• Flexible – Works even if some nodes move or fail.
• Applications:
• Smart farming – Soil and weather sensors across fields.
• Healthcare – Wearable devices in hospitals.
• Industries – Monitoring machines and equipment.
• Smart cities – Traffic and pollution sensors.

➢ Programming tool: nesC:

1. nesC is a version of C made specially for TinyOS, used in

wireless sensor networks (WSNs).
2. It helps write code in a modular way, using building blocks
called components.
3. Each component has two parts: interface (what it does) and
implementation (how it works).
4. Interfaces are of two types: "provides" (services it offers) and
"uses" (services it needs).
5. There are two kinds of function calls: "commands" go down,
and "events" come up the system layers.
6. A component can use and provide the same interface or use it
more than once with different names.
7. Two types of components: Modules (contain logic/code) and
Configurations (connect components).
8. Use the keyword call to run a command and signal to send an
event.
9. To connect interfaces, use the -> operator in configurations
(like wiring blocks).
10. No dynamic memory in nesC—everything is created
before the program runs.
11. Every full nesC application is a configuration that
includes a Main component.
12. Tasks are special functions that are posted to run later
using the post keyword.
13. Use the atomic block to protect shared data from being
changed at the same time by events and tasks.
14. Code is either asynchronous (from interrupts) or
synchronous (from tasks).
15. Shared variables used in asynchronous code must be in
atomic blocks, unless marked as norace.
➢ Introduction to Network Simulator 3 (ns-3):

• NS-3 is an open-source network simulator used for research

and education in computer networking.
• It simulates wired, wireless, and mobile networks, allowing
users to test and analyze network protocols and traffic.
• Purpose:
• Simulate network protocols like TCP/IP, Wi-Fi, LTE.
• Analyze network performance such as latency and throughput.
• Validate new algorithms or protocols before real-world deployment.
• Key Features:
• Modular architecture: Can be extended with C++/Python.
• Realistic: Emulates real-world protocols like Wi-Fi, LTE, 5G.
• Scalable: Supports large-scale simulations (thousands of nodes).
• Integration: Works with tools like Wireshark and Gnu plot.
• Architecture:
• Built around a discrete-event simulation core (events processed in
chronological order).
• Includes Core Components: Event Scheduler, Nodes, Net Devices,
Channels, and Protocol Stacks.

A] Core Components:
• Event Scheduler: Manages the simulation timeline.
• Node: Represents devices like routers or smartphones.
• NetDevice: Models network interfaces (Wi-Fi, Ethernet).
• Channel: Models communication links.
• Protocol Stack: Models different network layers.
B] Modules:
• Internet Module: Implements protocols like TCP, UDP, IPv4, IPv6.
• Wi-Fi Module: Models IEEE 802.11 standards.
• LTE/5G Module: Simulates cellular networks.
• Applications: Models traffic generators (e.g., HTTP, VoIP).
C] Helpers: Make it easy to configure nodes and networks (e.g.,
InternetStackHelper, WifiHelper).
D] Simulation Workflow:
1. Scripting: Write a simulation script (C++/Python).
2. Setup: Create nodes, install protocol stacks, configure devices and
channels.
3. Run: Execute the simulation and generate event traces.
4. Analysis: Parse logs or use tools like Flow Monitor.
• Key Applications:
• Wireless Networks: Test Wi-Fi MAC protocols, ad-hoc routing (AODV,
OLSR).
• IoT: Simulate networks like Lora WAN, Zigbee, and 6LoWPAN.
• 5G/6G: Model mm Wave, massive MIMO, and network slicing.
• Delay-Tolerant Networks (DTNs): Study routing in networks with
intermittent connectivity.
• Advantages over NS-2:
• Modern Codebase: Written in C++ (with Python bindings), unlike NS-
2’s old Tcl/OOP hybrid.
• Better Realism: More accurate emulation of protocols and hardware.
• Active Development: Regular updates with contributions from the
community.
Unit II: Wireless Transmission Technology
and Medium Access Control Protocols

➢ OSI Reference Model in MAC Architecture / Self

Organising MAC:
(MAC layer related to wsn)

1. The OSI reference model consists of seven layers:

Application, Presentation, Session, Transport, Network, Data
Link, and Physical layers.
2. In the context of wireless networks, Figure 5.1 shows the
logical architecture of the Data Link Layer (DLL) for shared
medium access.
3. The Physical Layer (PHY) lies at the bottom and defines the
transmission medium and network topology.
4. The physical layer handles all necessary functions for bit-level
transmission and reception over the wireless medium.
• Key services provided by the physical layer include:
• Encoding and decoding of signals.
• Preamble generation and removal to support synchronization.
• Transmission and reception of bitstreams.
5. Directly above the physical layer is the MAC (Medium Access
Control) sublayer.
 6. The MAC sublayer is responsible for assembling data into
frames by adding headers and trailers.
7. It adds a header with addressing information and a trailer for
error detection to each frame before transmission.
8. Upon receiving a frame, the MAC sublayer disassembles it to
extract the address and error control fields.
9. It performs address recognition, error detection, and
sometimes error recovery.
10. The MAC sublayer also regulates access to the shared
wireless medium according to application performance needs.
11. Above the MAC sublayer is the LLC (Logical Link
Control) sublayer.
12. The LLC sublayer provides a direct interface to the upper
layer protocols.
13. It is mainly used to hide the details of the physical
network from upper layers and supports interoperability.
14. Despite its function, the LLC sublayer is rarely used, as
network layer protocols typically handle interoperability in
modern networks.
• OTHER LAYERS:
15. The Data Link Layer (DLL) is divided into two sublayers:
LLC (Logical Link Control) and MAC (Medium Access Control).
16. The Network Layer is responsible for routing and
addressing, determining the best path for data packets across
interconnected networks (e.g., IP).
17. The Transport Layer ensures reliable data delivery,
handles error correction and flow control (e.g., TCP/UDP
protocols).
18. The Session Layer manages sessions or connections
between applications—establishing, maintaining, and
terminating links.
19. The Presentation Layer handles data translation,
encryption, and compression, ensuring that data from the
application layer is understandable across systems.
20. The Application Layer interacts directly with the user
and provides services like email, file transfer, and web
browsing.
 ➢ MAC Protocol used in Data link layer:
(Design Challenges/Fundamentals/Strategies to solve problem
faced)

• Fundamentals of MAC Protocols:

Coordination Challenge: Nodes must coordinate access to the shared channel,

but this coordination itself consumes bandwidth and adds complexity.
Spatial Distribution: Nodes are physically separated, making it hard to
instantly know each other's status due to propagation delays.
Overhead vs. Intelligence Trade-off: Better decision-making by protocols
may increase overhead, while lowering overhead may reduce decision quality.
Types of Information: MAC protocols use different types of information —
predetermined, dynamic global, and local — for access decisions.
Information Spectrum: Protocols vary in the amount of information used,
from minimal to perfect, affecting coordination efficiency and overhead.
Efficiency vs. Performance: Using global info improves performance but
wastes bandwidth; local info saves overhead but may harm performance.
Core Trade-off: Most MAC techniques are based on balancing protocol
efficiency and communication overhead to manage shared media access
effectively.

• Classification of MAC Protocols:

• In WSNs, saving energy is crucial because sensor nodes often run on

batteries.
• MAC protocols control how nodes access the communication medium,
and poor MAC design can waste a lot of energy.
• The content classifies MAC protocols into two main types:
 • Schedule-Based MAC Protocols:

• Schedule-based MAC protocols in WSNs aim to improve energy

efficiency and extend network lifetime by avoiding contention between
nodes.
• These protocols typically use TDMA (Time Division Multiple Access),
where time is divided into slots.
• Nodes are assigned specific time slots to transmit or receive data, and
outside these slots, they enter sleep mode to conserve energy.
Key Features:
1. Energy Efficiency: Nodes only operate during assigned slots, reducing
unnecessary energy use.
2. Scalability & Adaptability: These protocols adapt to changes in traffic
load and network topology.
3. Time Synchronization: Many protocols require synchronized time slots,
which can be challenging and costly in distributed networks.
Examples:
• SMACS: Uses a hybrid TDMA/FH (frequency-hopping) method for
unsynchronized network topologies, reducing the need for global
synchronization.
• Bluetooth: Uses a centralized TDMA-based protocol with frequency-
hopping for short-range communication, where a master node polls slave
devices for data transmission.
• LEACH (Low-Energy Adaptive Clustering Hierarchy): A hierarchical
protocol where nodes form clusters, and cluster heads communicate with
 the base station using TDMA, reducing collisions and energy
consumption.

•TDMA (Time Division Multiple Access): Time is divided into slots. Each
node transmits in its assigned slot. Energy-efficient as nodes sleep outside their
slots.
Advantages:
• Reduced collisions and overhearing.
• Low-duty cycle operation, which extends network lifetime.
Disadvantages:
• Difficult and costly time synchronization.
• Limited scalability and adaptability to node mobility or network changes.
• Cluster-based communication may not support peer-to-peer
communication directly.
In short, schedule-based protocols optimize energy use but may face challenges
in synchronization, scalability, and adaptability.

• Random Access-Based Protocols for WSNs:

• Traditional random access (contention-based) protocols require no

coordination among nodes, leading to potential collisions.
• Colliding nodes back off randomly before trying again.
• These protocols, however, are energy inefficient due to collisions,
idle listening, overhearing, and high control overhead.
Enhanced Random Access Protocols:
ALOHA:
• A simple protocol where nodes transmit when they have data. If a
collision occurs, they retry after a random time.
• Senses the channel before transmitting to avoid collisions.
• Waits if the channel is busy.
• Backs off randomly if a collision occurs.
CSMA (Carrier Sense Multiple Access):
• Nodes sense the channel before transmitting to avoid collisions. If the
channel is busy, they wait and try again later.
• Transmits anytime without checking the channel.
• Retransmits randomly if a collision happens.
• Inefficient when many nodes transmit at once.
Advantages of Enhanced Protocols:
1. Reduced energy consumption.
2. Lower collisions and overhearing.
 3. Better suited to dynamic traffic conditions.
Limitations:
1. Performance depends on traffic patterns and environment.
2. Frequent events can still lead to energy inefficiency.
3. Complexity increases with multiple channels or radios.

• Hybrid MAC:
Hybrid MAC is a combination of contention-based and scheduled-based MAC
protocols.
• It utilizes the benefits of both methods by adapting the strategy based on
network conditions.
• For low traffic uses contention-based (e.g., CSMA).
• For high traffic: switches to scheduled-based (e.g., TDMA).
• Example: Z-MAC (Zebra MAC) protocol.
• Advantage: Provides efficient channel utilization, flexibility, and better
performance in dynamic networks.

• Cross-Layer MAC:

• Cross-layer MAC integrates MAC layer functionalities with other OSI

layers (e.g., physical, network, application).
• It improves overall system performance by sharing information across
layers.
• Enables adaptive control based on channel condition, energy level, QoS
requirements, etc.
• Example: Energy-aware MAC where MAC adapts based on battery
status (from physical layer).
• Advantage: Enhances energy efficiency, QoS, and real-time performance
in WSNs and IoT.

• Design Challenges of MAC Protocols:

1. Energy Efficiency
• Sensor nodes operate on limited battery power, so MAC protocols must
minimize energy consumption from collisions, idle listening, and
overhearing.
2. Synchronization
 • Schedule-based protocols like TDMA require time synchronization,
which is difficult to achieve and maintain in distributed environments.
3. Collision Avoidance
• Preventing data collisions is essential to avoid retransmissions and
conserve energy, especially in dense node deployments.
4. Scalability
• MAC protocols must function efficiently as the number of nodes
increases and adapt to dynamic network sizes.
5. Latency and Delay
• Ensuring timely data delivery is a challenge, particularly in event-driven
or real-time applications.
6. Adaptability to Traffic Patterns
• Network traffic can vary greatly; protocols must handle low, bursty, or
unpredictable traffic efficiently.
7. Topology Changes and Mobility
• MAC protocols should adapt to changes like node failure, new node
addition, or node mobility without degrading performance.

• Strategies to solve MAC protocol problems in WSNs:

Duty Cycling – Nodes sleep when not needed to save energy.

Collision Avoidance – Use CSMA or RTS/CTS to avoid packet collisions.
Adaptive Scheduling – Adjust active/sleep times based on traffic.
Data Aggregation – Combine data to reduce number of transmissions.
Clustering – Group nodes; cluster head handles main communication.
Lightweight Synchronization – Use simple methods to sync time among
nodes.
Multi-Channel Use – Use separate channels for data and control to reduce
interference.
 ➢ IEEE 802.15.4 / LRWPAN:

• IEEE 802.15.4 supports low-power, low-cost wireless networks for

home automation, healthcare, industrial monitoring, etc.
• It's designed for applications that need long battery life and simple,
reliable communication.
• Often used with ZigBee, which builds on this standard for wireless
personal area networks (WPANs).
Key Features:
1. Low Power: Long battery life (months or years).
2. Low Cost: Affordable for small devices.
3. Reliable: Consistent, secure communication.
• Layer Structure:
1. Physical (PHY) Layer:
• Defines the network interface and the radio channel (e.g., 2.4 GHz,
868/915 MHz).
• Includes features like energy detection, channel assessment, and
low-power operations.
2. MAC (Medium Access Control) Layer:
• Handles network association, disassociation, and access to the
medium (using CSMA or beaconing).
• Operates in beaconing mode (for always-active devices) or
nonreasoning mode (for unslotted, random access).
3. Network Layer:
• Supports network configuration, topology management, device
discovery, and routing.
• Supports three topologies: star, mesh, and cluster tree.
4. Security Layer:
 • Provides encryption (AES), access control, and data integrity to
secure communication.
• Protects against unauthorized access, data tampering, and replay
attacks.
5. Application Layer:
• Includes ZigBee-specific components like APS (Application Support
Sublayer) and ZDO (ZigBee Device Object).
• Manages device roles, security keys, and application-specific
functions.
Key Security Features:
• Encryption: Keeps messages private.
• Access Control: Only authorized devices can join.
• Data Integrity: Prevents data tampering.

Que] Difference / WSN available/advance wireless technologies:

➢ Radio Frequency requirement for WSN:

• The radio frequency (RF) requirements for Wireless Sensor Networks

(WSNs) vary based on the specific application, environment, and
communication protocol being used.
• However, here are some general RF requirements for WSNs:

1. Frequency Bands:
• Common bands: 2.4 GHz, 868 MHz, 915 MHz, 433 MHz.
2. Low Power Operation:
• Low transmit power (-30 dBm to 0 dBm) for energy efficiency.
• Short communication range (typically 10 to 100 meters).
3. Bandwidth:
• WSNs require low bandwidth, such as 250 kbps for 2.4 GHz (IEEE
802.15.4).
4. Modulation Scheme:
• Efficient modulation like O-QPSK (for 2.4 GHz) or BPSK (for lower
frequencies).
5. Transmission Range:
• Typically, 10–100 meters, with some extended ranges beyond 100 meters.
6. Interference Management:
• Protocols use Clear Channel Assessment (CCA) and frequency hopping
to avoid interference.
7. Security:
• Encryption like AES and authentication to secure data.

➢ Radio Technology Primer:

• Radio technology is crucial in WSNs as it enables wireless

communication between sensor nodes.
• Radio technology in Wireless Sensor Networks (WSNs) uses the
electromagnetic spectrum as an unguided medium for point-to-
point or broadcast communication between sensor nodes.
• This section provides an overview (primer) of key concepts in radio
technology used in WSNs.
1. Radio Frequency (RF):
• Refers to the electromagnetic wave frequencies used to transmit
data wirelessly.
• WSNs commonly operate in RF bands like 868 MHz, 915 MHz, and
2.4 GHz.
• RF signals are used to carry sensor data across nodes.
2. Frequency Band (e.g., 2.4 GHz, 868 MHz):
• Defines the range of frequencies allocated for wireless
communication.
• 2.4 GHz: Commonly used, globally accepted, supports higher data
rates.
• 868 MHz / 915 MHz: Used in Europe/North America, better for long-
range, lower data rate.
3. Modulation Schemes (ASK, PSK):
• Techniques used to encode digital data into analog radio signals.
o ASK (Amplitude Shift Keying): Changes signal amplitude.
o PSK (Phase Shift Keying): Changes signal phase.
• The choice affects range, energy use, and error rate.
4. Multi-hop Communication:
• Data is passed from node to node (hopping) until it reaches the base
station.
• Saves energy and increases network coverage.
• Essential in large or dense WSN deployments.
5. Data Rate and Throughput:
• Data rate: Number of bits transmitted per second (bps).
• Throughput: Actual data successfully delivered over the network.
• WSNs trade off high throughput for energy efficiency.
6. Range:
• Distance over which a wireless signal can travel effectively.
• Affected by antenna design, power, and environment.
• Longer range may consume more power.
7. Channel Access Methods:
• Rules to manage how multiple nodes share the wireless medium.
• Common methods:
o CSMA/CA (Carrier Sense Multiple Access with Collision
Avoidance)
o TDMA (Time Division Multiple Access)
• Ensures efficient and collision-free communication.
8. Power Consumption:
• WSN nodes usually run on batteries, so low power is critical.
• Radio transmission is a major power consumer.
• Duty cycling and efficient protocols help save power.
 ➢ Data Dissemination and gathering in WSN:

• In a Wireless Sensor Network (WSN), communication between sensor

nodes and the base station (sink) plays a critical role.
• This communication is typically categorized into two processes: Data
Dissemination and Data Gathering.

1. Data Gathering:
Definition:
Data gathering is the process of collecting sensed data from sensor nodes and
transmitting it to the base station or sink node for further processing and
analysis.
Key Features:
• Involves periodic or event-driven data reporting.
• Often utilizes multihop communication to reach the sink.
 • May include data aggregation at intermediate nodes to eliminate
redundancy and save energy.
Purpose:
• To monitor environmental or physical conditions (e.g., temperature,
humidity, motion).
• To provide real-time or delayed reporting of collected data.
Advantages:
• Minimizes data redundancy through aggregation.
• Reduces energy consumption by transmitting less data.
• Extends network lifetime by decreasing communication frequency.
• Ensures data reliability and accuracy through aggregation.

2. Data Dissemination:
Definition:
Data dissemination refers to the process of distributing queries, commands, or
configuration information from the sink to the sensor nodes.
Key Features:
• Used when the sink wants to query specific information from sensors.
• Can be broadcasted or selectively routed to relevant nodes.
• Ensures sensors are aware of when, what, and how to sense or respond.
Purpose:
• To control sensor behaviour.
• To initiate data collection or event monitoring.
Advantages:
• Efficiently distributes information.
• Scales well in large networks.
• Can reduce energy consumption if protocols are adaptive.
• Provides fault tolerance with multiple paths.

➢ WSN Physical layer/ Approaches for WSN in physical

layer:
The Physical Layer is the lowest layer in the WSN protocol stack. It handles
the transmission and reception of raw bits over the wireless
communication medium.
Key Functions:
1. Frequency Selection: Choosing suitable radio frequency for data
transmission.
2. Modulation and Demodulation: Converting digital data to analog
signals for transmission and vice versa.
3. Bit Transmission and Reception: Sending and receiving streams of
bits.
4. Error Detection: Identifying any transmission errors at the hardware
level.
5. Encryption: Basic data security during transmission.
6. Hardware Interface: Interfacing with components like antennas and
radio chips.
This layer directly interacts with the hardware and is crucial for reliable and
energy-efficient communication.

• Approaches for Physical Layer in WSNs:

1. Radio Communication Technologies
WSNs commonly use low-power, short-range wireless standards such as:
• IEEE 802.15.4: Widely used in ZigBee and similar protocols.
• Bluetooth Low Energy (BLE): For short-range, low-energy
communication.
• Wi-Fi (IEEE 802.11): Used when higher data rates are needed.
• LoRa/LoRaWAN: For long-range, low-power data transmission in
sparse deployments.
2. Modulation Techniques
Used to convert digital data into radio signals:
• Amplitude Shift Keying (ASK)
• Frequency Shift Keying (FSK): Common in WSNs due to low
complexity and energy efficiency.
• Phase Shift Keying (PSK): Used when better reliability is needed.
• Direct Sequence Spread Spectrum (DSSS): Improves resistance to
interference.
3. Energy-Efficient Hardware Design
• Using radios that support low power modes and sleep scheduling.
 • Adaptive transmission power based on distance to reduce energy
usage.
4. Error Control Mechanisms
• Forward Error Correction (FEC): Adds redundancy for error detection
and correction without retransmission.
• Automatic Repeat Request (ARQ): Requests retransmission when an
error is detected (less common in WSNs due to energy constraints).
5. Duty Cycling
• Turning off radio transceivers during idle periods to save power.
• Essential for extending the operational lifetime of sensor nodes.

➢ Traffic Adaptive Medium Access in detail:

• Traffic Adaptive Medium Access refers to a type of MAC protocol that

adjusts its behaviour (such as access method, timing, or slot allocation)
depending on the amount of data traffic in the network.
• It aims to improve performance like throughput, delay, energy efficiency,
and fairness. When traffic is low, the system may use contention-based protocols
(e.g., CSMA) to avoid unnecessary overhead.
• When traffic is low, the system may use contention-based protocols (e.g.,
CSMA) to avoid unnecessary overhead.
• When traffic is high, it may switch to scheduled access (e.g., TDMA or
polling) to reduce collisions.
• The MAC layer monitors traffic conditions in real-time and adapts access
strategy accordingly.

• Key Features:

• Dynamic Slot Allocation: Increases/decreases time slots based on the

number of active nodes.
• Load-aware Behaviour: Adjusts channel access depending on current
traffic.
• Energy Efficiency: Saves power during low traffic periods.
• Collision Reduction: Avoids collisions in high traffic situations.
• Advantages:
• Improves channel utilization.
• Minimizes collision and delay.
• Ensures fair access to medium.
• Supports QoS (Quality of Service) under varying load conditions.
➢ Protocol Stack for WSN:
Que] Physical layer protocol for WSN:
Que] Various WSN network Protocols:

1. Application Layer
• Directed Diffusion: A data-centric protocol that uses attribute-value pairs
to route data efficiently.
• Sensor Management Protocols: Enable configuration, querying, and
monitoring of sensor nodes remotely.

2. Transport Layer
• STCP (Sensor Transmission Control Protocol): Ensures reliable transport
with minimal energy usage by using selective acknowledgments.
• RCRT (Rate-Controlled Reliable Transport): Provides end-to-end
reliability and congestion control using feedback-based rate adjustments.

3. Network Layer
• LEACH (Low-Energy Adaptive Clustering Hierarchy): A clustering
protocol that rotates cluster heads to balance energy consumption.
• PEGASIS (Power-Efficient Gathering in Sensor Information System):
Forms a chain among nodes to transmit data to the sink, reducing energy
use.
• AODV (Ad hoc On-Demand Distance Vector): Finds routes on-demand
and maintains them only while needed.
• SPIN (Sensor Protocols for Information via Negotiation): Uses data
negotiation to eliminate redundant transmissions and save energy.

4. Data Link Layer (MAC Layer)

• TDMA (Time Division Multiple Access): Allocates time slots to nodes,
preventing collisions and saving energy.
• CSMA (Carrier Sense Multiple Access): Nodes sense the channel before
transmitting to avoid collision.
• S-MAC (Sensor MAC): Introduces sleep schedules and synchronization
to reduce energy consumption.

5. Physical Layer
• IEEE 802.15.4: Standard for low-rate wireless personal area networks
(used in ZigBee).
• Bluetooth: Short-range communication with moderate data rates and
energy efficiency.
• ZigBee: Built on IEEE 802.15.4; offers low-power, low-data rate wireless
communication ideal for WSNs.

Que] Challenge & Issues in WSN network Protocols:

1. Energy Efficiency
• Sensor nodes run on batteries.
• Protocols must save power to increase network life.

2. Scalability
• WSN may have hundreds or thousands of nodes.
• Protocols must work well even if the network size increases.

3. Limited Bandwidth
• Wireless links have low data rates.
• Protocols should reduce unnecessary data transmission.

4. Reliable Data Transmission

• Wireless signals can be lost or interrupted.
• Protocols must ensure important data reaches the base station correctly.

5. Node Mobility
• In some applications, sensor nodes may move.
• Protocols must quickly update routes and connections.

6. Security
• Sensor nodes are easily accessible and vulnerable to attacks.
• Protocols should provide data encryption and secure routing.
 Unit III: Transport Control Protocols for
Wireless Sensor Networks

➢ Transport Control Protocols for Wireless Sensors

Networks:
Que] What is TCP for WSN?
• TCP is a connection-oriented protocol that ensures reliable data
transfer over the Internet.
• It establishes a connection between two endpoints before data
transmission begins.
• It provides:
o Reliable delivery (lost data is retransmitted)
o Ordered delivery (data arrives in sequence)
o Error-checked transmission (using checksums)
• Three-way handshake mechanism is used to establish the
connection between sender and receiver.
• Sliding window mechanism is used to control the flow of data
between endpoints.
• TCP provides congestion control mechanisms to:
o Prevent network overload
o Improve overall network performance
• TCP operates over the IP layer, using its services to achieve:
o Reliable
o Orderly
o Controllable
o Elastic transmission

• How TCP Works:

1. Connection Establishment
• TCP uses a three-way handshake to set up a connection between
sender and receiver.
• Each connection is uniquely identified by the IP address and port
number of both devices.
 • Example: Multiple connections can exist using the same IP but
different port numbers.
2. Data Transmission
• Data is sent in small chunks called segments.
• Each segment has a sequence number to maintain the correct order.
• TCP uses ACK (Acknowledgment) to confirm successful delivery.
• If data is lost, TCP resends it.
• TCP uses a sliding window mechanism to control how much data can
be sent at once.
• Flow control ensures the sender doesn't overwhelm the receiver.
3. Disconnection
• After all data is sent and received, TCP closes the connection and
frees the resources.

Que] Traditional & Existing TCP?

1. Traditional TCP:

Traditional TCP refers to the original versions of the TCP protocol developed
for wired networks, such as TCP Tahoe and TCP Reno.
Features:
• Designed assuming packet loss only happens due to network
congestion, not due to wireless errors.
• Uses three basic mechanisms:
o Slow Start
o Congestion Avoidance
o Fast Retransmit
• Performs well in stable, low error wired networks but poorly in
wireless or mobile environments.
Example:
TCP Reno is a traditional version of TCP, commonly used in early internet
systems.
• Key Features:
o Uses slow start, congestion avoidance, and fast retransmit.
o Reduces data sending rate immediately after packet loss,
assuming congestion.
Example Use Case:
A desktop computer connected to a wired LAN—data loss is rare and
usually due to congestion, so Reno works well here.

2. Existing TCP Variants:

Definition:
These are improved versions of TCP created to overcome the limitations of
traditional TCP, especially in wireless, mobile, and high-speed networks.
Features:
• Can differentiate between congestion loss and random loss (like in
wireless).
• Better bandwidth utilization and faster recovery after packet loss.
• Some focus on delay minimization (e.g., TCP Vegas), others on
maximum throughput (e.g., TCP BBR).
Example:
TCP BBR is a modern TCP variant developed by Google for better
performance on today’s internet.
• Key Features:
o Focuses on bandwidth estimation and round-trip delay instead
of relying on packet loss.
o Maintains high throughput and low latency, even in wireless or
high-speed networks.
Example Use Case:
Streaming HD videos over a 4G/5G mobile network or Wi-Fi—BBR adjusts
the sending rate based on real-time measurements, avoiding unnecessary
slowdown.

Que] Performance of TCP?

• In this section a quantitative comparison of WSN congestion and loss
performance is presented.
• The measure used for congestion comparison is energy consumption,
which is calculated for end-to-end and hop-by-hop cases.
• The other measure is loss performance, which is based on cache and non-
cache approaches, as discussed earlier.

1. Congestion Control Approaches:

A. End-to-End Approach
 • Source node adjusts the data rate based on feedback.
• Congestion is detected late → higher packet loss and more energy usage.
• Similar to traditional TCP.
B. Hop-by-Hop Approach
• Each node checks for congestion and informs the previous node.
• Faster reaction to congestion → less packet loss, better energy efficiency.
• More suitable for WSN.

2. Packet Loss Recovery Methods:

A. Non-Cache Recovery (End-to-End ARQ)
• Packets are retransmitted from the source if lost.
• Causes higher retransmissions and lower energy efficiency when success
rate drops.
B. Cache-Based Recovery (Hop-by-Hop ARQ)
• Lost packets are retransmitted from the nearest node (not from source).
• Fewer retransmissions, more energy saving.

3. Other Loss Recovery Techniques:

• FEC (Forward Error Correction): Adds extra bits for self-correction at the
receiver.
→ Commonly uses Reed-Solomon codes in WSN.
• ARQ (Automatic Repeat Request): Retransmits if ACK is not received.
→ Types: Stop-and-Wait, Go-Back-N, Selective Repeat.
• Hybrid ARQ: Combines FEC and ARQ. First tries to correct, then
requests retransmission if needed.

Que] Performance issues of TCP?

1. High Energy Consumption
• Frequent retransmissions and acknowledgments drain battery-powered
sensor nodes.
2. Poor Congestion Detection
• Traditional TCP detects congestion late, causing packet loss and delays.
3. Inefficient in Wireless Links
• Assumes packet loss is due to congestion, not due to wireless link errors.
4. End-to-End Retransmission Overhead
• Retransmissions from source to destination increase traffic and energy
usage.
5. Delay in Loss Recovery
• Packet loss recovery takes longer in traditional end-to-end TCP methods.
6. Limited Scalability
• TCP struggles in large sensor networks with many nodes and hops.
7. Lack of Cross-Layer Optimization
• TCP does not adapt well to WSN-specific needs like energy-aware
routing or MAC layer feedback.

Que] Design issues of TCP?

1. Reliability
→ Make sure all data reaches correctly and completely.
→ Detect and fix transmission errors.

2. Congestion Control
→ Avoid traffic jams in the network.
→ Adjust data sending rate as per network load.

3. Flow Control
→ Don't overload the receiver with too much data.
→ Match sending speed to receiving speed.

4. Efficiency
→ Use minimum network resources.
→ Reduce extra overhead (like headers, retransmissions).

5. Scalability
→ Work well even when many users or devices connect.
→ Support multiple applications smoothly.

6. Security
→ Protect data from hackers or misuse.
→ Ensure safe and private transmission.

7. Adaptability
→ Work in different network types (wired, wireless, low power).
→ Handle changes in network conditions.

8. Interoperability
→ Must work well with other layers/protocols.
→ Allow communication between different systems/devices.
 Que] Why TCP not work well in WSN?

TCP doesn't work well in Wireless Sensor Networks (WSNs) because:

1. Energy Consumption: TCP needs a lot of energy for tasks like packet
acknowledgment and retransmissions, which is not ideal for battery-
powered sensor nodes.
2. Packet Loss: WSNs have high packet loss due to wireless interference,
but TCP constantly retransmits lost packets, wasting energy and causing
delays.
3. Low Bandwidth: WSNs often have limited bandwidth, and TCP’s
congestion control is inefficient in such environments.
4. Latency: TCP introduces delays with its acknowledgment and
retransmission processes, which is not good for real-time applications in
WSNs.
5. High Overhead: TCP’s reliability mechanisms (like flow control and
error checking) create unnecessary overhead in WSNs, where simplicity
is often needed.
6. Scalability Issues: TCP doesn’t handle large networks of thousands of
nodes well, which is common in WSNs.
7. Changing Topologies: WSNs often have dynamic topologies (nodes
moving or failing), and TCP struggles to adapt to these changes.

Que] Design of Transport protocol:

• Designing a transport protocol for a Wireless Sensor Network (WSN)
involves addressing the unique challenges that WSNs face, such as
limited energy, unreliable communication, and varying network
topologies.
• Here’s a simplified design for a transport protocol in Wireless Sensor
Networks (WSNs):
1. Energy Efficiency:
• Minimize Overhead: Keep messages small to save energy.
• Sleep Modes: Nodes "sleep" when not transmitting data to save power.
• Adaptive Power: Adjust transmission power based on distance and
conditions.
2. Reliability:
• Error Detection: Use simple checks (like checksums) for errors.
 • Selective Acknowledgment: Acknowledge only important messages to
save energy.
3. Scalability:
• Clustering: Group nodes into clusters to reduce network traffic.
• Data Aggregation: Combine data at intermediate nodes to reduce the
amount sent.
4. Packet Loss:
• Partial Retransmissions: Only resend important parts of a lost packet.
• Error Correction: Use techniques to fix small errors without
retransmitting.
5. Delay:
• Low Latency: Prioritize urgent messages to reduce delays.
• Store-and-Forward: Temporarily store data if the network is busy, then
send it later.
6. Congestion Control:
• Light Congestion Control: Reduce data rate if congestion is detected.
• Load Balancing: Spread out traffic to avoid overloading any node.
7. Dynamic Topologies:
• Adapt to Changes: Reroute data if nodes fail or move.
• Monitor Link Quality: Adjust communication based on link strength.

Que] Traditional TCP & UDP in WSN?

• TCP (Transmission Control Protocol) and UDP (User Datagram Protocol)
are two traditional transport layer protocols that are widely used for
communication over networks.
• Here’s a simplified explanation of each:
• TCP (Transmission Control Protocol):
TCP is a reliable, connection-oriented protocol, which means it ensures that data
is delivered accurately and in order. It is used when reliability is crucial, like in
web browsing, email, and file transfer.
Key Features:
1. Connection-Oriented:
o Before transmitting data, a connection is established between the
sender and receiver using a process called a handshake (three-way
handshake).
2. Reliability:
o Ensures data is delivered correctly and in order. If any packet is
lost or corrupted, TCP will retransmit it.
3. Flow Control:
 o Manages the rate at which data is sent, preventing the receiver
from being overwhelmed with too much data at once.
4. Congestion Control:
o Controls the rate of data transmission to avoid network congestion
by adjusting the flow based on network conditions.
5. Acknowledgments:
o The receiver sends an acknowledgment for each packet received. If
no acknowledgment is received, the sender retransmits the packet.
6. Error Detection:
o TCP checks for errors using checksums and ensures data integrity
during transmission.
Example:
• Web browsing (HTTP), file transfer (FTP), and email (SMTP) use TCP
because they require guaranteed delivery and error-free communication.

• UDP (User Datagram Protocol):

UDP is a connectionless, unreliable protocol, meaning it sends data without
establishing a connection or ensuring delivery. It is used in scenarios where
speed is more important than reliability.
Key Features:
1. Connectionless:
o No connection is established before data is sent. Data is just sent as
packets (called datagrams) without checking whether the receiver
is ready to receive it.
2. Unreliable:
o UDP does not guarantee that the data will be delivered, nor does it
check for errors. If packets are lost or arrive out of order, UDP does
not try to fix it.
3. Low Overhead:
o UDP has minimal overhead compared to TCP because it does not
perform error checking, retransmissions, or congestion control.
4. Faster:
o Since UDP does not have the overhead of establishing a connection
or ensuring reliable delivery, it is faster than TCP, making it
suitable for real-time applications.
5. No Flow or Congestion Control:
o UDP does not manage flow or congestion control, meaning it may
send data as fast as the application requires.
Example:
• Streaming media (like video or audio), online gaming, and DNS queries
use UDP because they need fast delivery and can tolerate some data loss
(such as dropped video frames or minor glitches in a game).

Que] Crushing transport layer protocols:

1. TCP (Transmission Control Protocol):

• Type: Connection-oriented and reliable.
• Features:
o Establishes a connection using a three-way handshake.
o Ensures ordered and error-free data delivery.
o Uses acknowledgments and retransmissions for lost packets.
o Implements flow control and congestion control.
• Applications: Used in web browsing (HTTP), email (SMTP), file
transfer (FTP) where reliability is crucial.

2. UDP (User Datagram Protocol):

• Type: Connectionless and unreliable.
• Features:
o Does not establish a connection before sending data.
o No guarantees for packet delivery, order, or duplication.
o Minimal overhead, making it faster than TCP.
o No flow or congestion control mechanisms.
• Applications: Used in real-time applications like video streaming,
online gaming, and DNS where speed is more important than
reliability.

3. SCTP (Stream Control Transmission Protocol):

• Type: Connection-oriented and reliable.
• Features:
o Supports multi-streaming to avoid blocking issues.
o Allows multi-homing for network path redundancy.
o Ensures reliable and sequenced message delivery.
• Applications: Used in signaling systems in telecom (e.g., VoIP).

4. DCCP (Datagram Congestion Control Protocol):

• Type: Connection-oriented but unreliable.
• Features:
o Provides congestion control like TCP.
o Does not guarantee reliable delivery like TCP.
o Suitable for applications needing timely delivery but willing to
tolerate some loss.
• Applications: Used in multimedia streaming and voice
communication.

5. Transport Protocols in Wireless Sensor Networks (WSNs)

• Need for Special Protocols: Traditional protocols like TCP/UDP are
not suitable for WSNs due to:
o Limited energy and processing power.
o Unreliable and low-bandwidth wireless links.
o Frequent topology changes and node failures.
• Examples:
o PSFQ (Pump Slowly Fetch Quickly): Reliable data
dissemination with low energy cost.
o CODA (Congestion Detection and Avoidance): Manages
congestion in WSNs.
o RMST (Reliable Multi-Segment Transport): Supports
fragmented packet transmission.
 Que] Routing Challenges and design issues in wireless
sensor network:
Que] Issues & Challenges in routing protocol at network
layer:

• Routing is a critical aspect of wireless sensor networks (WSNs)

that involves finding the optimal path for data transmission
between the sensor nodes and the sink node.
• However, WSNs pose several challenges and design issues that
make routing in these networks complex.
• Here are some of the key challenges and design issues in WSN
routing:
1. Energy Efficiency
• Sensor nodes have limited battery life.
• Routing should minimize energy use to extend the network's lifespan.
• Techniques used:
o Data aggregation (combine data to reduce transmission)
o Clustering (group nodes to reduce communication cost)
o Sleep scheduling (turn off idle nodes to save power)

2. Scalability
• WSNs may consist of hundreds or thousands of nodes.
• Routing protocols must work efficiently even as the network grows.
• Examples:
o LEACH (Low Energy Adaptive Clustering Hierarchy)
o PEGASIS (Power-Efficient Gathering in Sensor Information
Systems)

3. Dynamic Topology
• The network can change due to node movement, failure, or environmental
effects.
• Routing must adjust quickly to these changes.
• Examples:
o AODV (Ad-hoc On-demand Distance Vector)
o DSR (Dynamic Source Routing)
4. Quality of Service (QoS)
• Some applications (like health monitoring or military) need fast and
reliable data delivery.
• Routing must ensure minimum delay, low packet loss, and high
reliability.
• Examples:
o AQM (Active Queue Management)
o CEDAR (Cluster-based Energy-Delay Aware Routing)

5. Security
• WSNs are vulnerable to attacks like eavesdropping, data tampering, and
denial-of-service.
• Routing must ensure data confidentiality, integrity, and availability.
• Examples:
o SPINS (Security Protocols for Sensor Networks)
o SEAD (Secure Efficient Distance Vector Routing)

6. Data Redundancy (Additional Challenge)

• Many nodes may sense the same data, causing repeated transmissions.
• This wastes energy and bandwidth.
• Routing protocols should remove duplicate data before transmission
using data fusion or aggregation techniques.

7. Limited Bandwidth
• Wireless links in WSNs offer low data rates.
• Routing must be efficient to avoid congestion and packet loss.
• Solution: Minimize control message overhead and use lightweight
protocols.

Que] Routing Strategies in WSN:

• Routing strategies in WSNs decide how data is sent from one node
to another efficiently while saving energy.
• There are three main types of routing strategies:
1. Proactive Routing Strategies:
• What it does: Maintains up-to-date routing information all the time.
• How it works:
 o Each node keeps a routing table with details about its neighbors.
o Routing info is constantly updated, even if no data needs to be sent.
• Goal: Reduce delay in data delivery.
• Use when: Low latency is required.
• Example protocols: DSDV (Destination-Sequenced Distance Vector),
OLSR (Optimized Link State Routing).

2. Reactive Routing Strategies:

• What it does: Creates routes only when needed.
• How it works:
o When data needs to be sent, the source broadcasts a Route Request
(RREQ).
o The route is formed only after receiving a Route Reply (RREP).
• Goal: Save energy by avoiding unnecessary routing overhead.
• Use when: Data is sent infrequently, or energy saving is more important
than delay.
• Example protocols: AODV (Ad hoc On-Demand Distance Vector), DSR
(Dynamic Source Routing).

3. Hybrid Routing Strategies:

• What it does: Combines both proactive and reactive approaches.
• How it works:
o Maintains basic routing info proactively (low overhead).
o Builds detailed routes reactively when needed.
• Goal: Balance between low delay and energy efficiency.
• Use when: Network has changing traffic and mobility.
• Example protocols: ZRP (Zone Routing Protocol), TORA (Temporally
Ordered Routing Algorithm).

Que] Functions of Routing in WSN:

• Routing should minimize energy use to extend the network's lifespan.
• Routing protocols must work efficiently even as the network grows.
• The network can change due to node movement, failure, or environmental
effects. Routing must adjust quickly to these changes.
• Routing must ensure minimum delay, low packet loss, and high
reliability.
• Routing protocols should remove duplicate data before transmission
using data fusion or aggregation techniques.
• Routing must be efficient to avoid congestion and packet loss.
• Routing must ensure data confidentiality, integrity, and availability.

Que] Routing Protocols at network layer / Sensor network

routing protocol:

• The routing protocols define how nodes will communicate with

each other and how the information will be disseminated through
the network.
• There are many ways to classify the routing protocols of WSN.
1. Node centric:
• In node centric protocols the destination node is specified with some
numeric identifiers, and this is not expected type of communication in
Wireless sensor networks.
• E.g. Low energy adaptive clustering hierarchy (LEACH).
• LEACH is a routing protocol that organizes the cluster such that the energy
is equally divided in all the sensor nodes in the network.
• In LEACH protocol several clusters are produced of sensor nodes and one
node defined as cluster head and act as routing node for all the other nodes
in the cluster.
2. Data-centric:
• In most of the wireless sensor networks, the sensed data or
information is far more valuable than the actual node itself.
• Therefore, data centric routing techniques the prime focus is on the
transmission of information specified by certain attributes rather than
collecting data from certain nodes.
• Eg: Sensor protocols for information via negotiation (SPIN)
 • SPIN is abbreviation of sensor protocol for information via
negotiation. This protocol is defined to use to remove the deficiency
like flooding and gossiping that occurs in other protocols.
• Three messages namely ADV, REQ and DATA are used in SPIN.
The node broadcast an ADV packet to all the other nodes that it has
some data.
[Link]-initiated (Dst-initiated):
• Protocols are called destination-initiated protocols when the path setup
generation originates from the destination node.
• Examples are directed diffusion (DD) & LEACH.
• Directed diffusion is a data centric routing technique.
• It uses this data centric technique for information gathering and
circulating.
4. Source-initiated (Src-initiated):
In these types of protocols, the source node advertises when it has data to
share and then the route is generated from the source side to the destination.
Examples is SPIN.

Que] Spin Routing protocol in detail:

• SPIN is a data-centric routing protocol designed for Wireless

Sensor Networks (WSNs).
• It focuses on efficient data dissemination using negotiation and
resource-adaptive mechanisms to eliminate redundant data
transmission and conserve energy.
• Features of SPIN:
1. Data Advertisement Mechanism – Nodes advertise data before
transmitting, reducing unnecessary transmissions.
2. Negotiation-based Transmission – Uses metadata to describe data
and only transmits when a node is interested.
3. Resource Adaptiveness – Nodes make decisions based on their
available resources like energy, bandwidth.
4. Three-Stage Protocol – Uses three types of messages: ADV
(advertisement), REQ (request), and DATA.
5. Localized Algorithms – Each node makes routing decisions locally
without relying on global network information.
• Working of SPIN:
1. ADV Message – A node with new data sends an ADV message to
neighbors describing the data.
2. REQ Message – Neighboring nodes interested in the data send a REQ
message.
3. DATA Message – After receiving the REQ, the sender transmits the
actual data.
This negotiation process helps in reducing duplicate data transmission
and avoids flooding the network.
• Advantages of SPIN:
1. Reduces Redundant Data – Prevents the transmission of duplicate
data, saving energy and bandwidth.
2. Energy Efficiency – Advertisement and negotiation reduce
unnecessary data exchange.
3. Scalability – Works well with growing network sizes due to localized
decision-making.
4. Flexibility – Adaptable to various network conditions based on
available resources.
5. Simplicity – The protocol is easy to implement with minimal
overhead.
• Disadvantages of SPIN / Routing Strategies:
1. Not Reliable for Critical Data Delivery – Does not guarantee delivery,
which is not ideal for time-sensitive applications.
2. Assumes Meta-Data Support – Requires that nodes can interpret
metadata, which may not be feasible in all cases.
3. Unfit for High-Density Networks – In very dense networks, negotiation
can still lead to increased overhead.
4. No Global Topology Awareness – It might not always find the most
optimal path for long-distance communication.

Que] LEACH Routing algorithm in detail:

• LEACH is a hierarchical, cluster-based routing protocol designed to
minimize energy consumption in Wireless Sensor Networks.
• It organizes the nodes into clusters, each led by a Cluster Head (CH), and
rotates the CH role periodically to balance energy usage across the
network.
• Features of LEACH:
• Clustering-Based Protocol – Divides network into clusters, improving
scalability and manageability.
• Randomized CH Rotation – Distributes energy load evenly among all
nodes.
• Data Aggregation – CHs perform local data fusion, reducing the amount
of data transmitted to the base station.
• Self-Organizing – Nodes independently decide roles, eliminating the need
for centralized control.
• TDMA Scheduling – Time Division Multiple Access is used to avoid
collisions within clusters.
•
• Working of LEACH (Simplified)
1. Setup Phase:
• Some nodes randomly become Cluster Heads (CHs).
• CHs send ads to nearby nodes.
• Other nodes choose the CH with the strongest signal and join its cluster.
2. Steady-State Phase:
• CHs collect data from cluster members.
• CHs combine (aggregate) the data to remove duplicates.
• CHs send the final data to the base station.
3. Round Rotation:
• After some time, new CHs are selected to save energy and continue the
process.

• Advantages of LEACH:
1. Energy Efficiency – Reduces energy consumption through data
aggregation and CH rotation.
2. Load Balancing – Dynamic CH rotation helps in evenly distributing
energy usage.
3. Scalability – Works well in large-scale networks due to the hierarchical
structure.
4. Improved Lifetime – Helps in extending the network lifetime by
minimizing long-range communication for regular nodes.
5. Reduced Latency – Local communication within clusters decreases
communication delay.

• Disadvantages of LEACH:
1. Random CH Selection – May result in uneven CH distribution or
selection of low-energy nodes as CHs.
2. Assumes Uniform Energy Levels – Not suitable for heterogeneous
networks with varying node capabilities.
3. Not Suitable for Large Area Networks – Direct transmission from CHs to
the base station is inefficient over long distances.
4. No Mobility Support – LEACH assumes stationary nodes and CHs; it
does not perform well in mobile environments.
5. Single-Hop Communication – Assumes CHs can directly communicate
with the base station, which is unrealistic in large networks.

Que] CODA:
CODA – Congestion Detection and Avoidance (WSN)
• Main Components:
1. Congestion Detection
2. Open-loop Hop-by-Hop Backpressure
3. Closed-loop End-to-End Multisource Regulation

• Working of CODA:
1. Congestion Detection:
• Monitors buffer occupancy and wireless channel load.
• If either exceeds a set threshold → congestion is detected.
2. Hop-by-Hop Backpressure (Open-loop):
• Congested node sends a backpressure signal to its upstream neighbor.
• Upstream node reduces its data sending rate using methods like AIMD
(Additive Increase Multiplicative Decrease).
 3. End-to-End Regulation (Closed loop):
• If a node sends more than its allowed rate:
o It sets a "regulation bit" in the event packet.
• Sink receives this packet:
o If regulation bit is set, it sends an ACK to source nodes asking
them to reduce their rate.
• When congestion clears:
o Sink sends another ACK asking nodes to increase their rate.
• Advantages:
• Detects congestion early.
• Uses both local (hop-by-hop) and global (end-to-end) control.
• Helps in managing multisource traffic.
• Disadvantages:
1. Unidirectional control (only from sensor to sink).
2. No reliability mechanism (packet loss not handled).
3. Slow response in heavy congestion (ACKs may get lost).

Que] GARUDA:
GARUDA – Transport Control Protocol (Downstream Reliability)
• Key Concept:
• Downstream reliability protocol
• Based on a two-tier node architecture

• Architecture:
1. Core Nodes:
o Selected at every 3i hops from the sink (where i is an integer).
o Handle packet recovery and reliable delivery.
2. Non-Core Nodes:
o All other nodes.
o Each non-core node selects a nearby core node.
o Use core nodes to recover lost packets.

• Main Functions:
1. WFP (Wait for First Packet) Pulse:
o Used to ensure successful delivery of the first packet.
o Repeated WFP pulses improve reliability.
2. Pulse Transmission:
o Helps calculate the hop number.
 o Used to select core sensor nodes.
o Supports forming the two-tier architecture.

• Advantages:
• Ensures reliable delivery of the first packet.
• Efficient packet recovery using core nodes.
• Reduces network overhead by localizing recovery to core nodes.

Que] PEGASIS:

• Designed to improve energy efficiency and network lifetime in

Wireless Sensor Networks (WSNs).

2. Key Features:
• Based on chain-based routing instead of clusters.
• Each node only communicates with a close neighbor.
• Data fusion is performed at each node to reduce the amount of data
transmission.
• Only one node transmits to the base station (sink) in each round.
3. Working:
Chain Formation:
• Nodes form a chain using a greedy algorithm.
• Each node communicates with the nearest neighbor in the chain.
Data Gathering:
• In a round, data is passed from one node to another along the chain.
• Each node aggregates its data with the received data before passing it
forward.
Leader Selection:
• One node is chosen as the leader/head node in each round.
• This leader sends the final aggregated data to the base station.
• Leader is rotated among all nodes to balance energy consumption.
4. Advantages:
• Reduces communication distance between nodes.
• Minimizes energy consumption by avoiding long-distance transmissions.
• Increases network lifetime compared to LEACH.
• Less overhead due to elimination of dynamic cluster formation.
Que] ATP:
ATP – Ad Hoc Transport Protocol (WSN)
• Key Concept:
• End-to-end transport protocol with receiver and network-assisted
feedback.

• Main Features:
1. End-to-End Feedback Control:
o Feedback is assisted by both receiver and network nodes.
o Helps adjust sending rate dynamically.
2. Uses SACK (Selective Acknowledgment):
o Recovers lost packets efficiently.
o Only retransmits missing packets, not all.
3. Delay-Based Rate Calculation:
o Intermediate nodes compute D, the total delay:
▪ D = sum of queuing + transmission delay.
o Required rate = 1 / D (inverse of delay).
4. Separation of Congestion and Reliability:
o Congestion control and reliability mechanisms are handled
separately.
o Results in better fairness and higher throughput than traditional
TCP.
• Advantages:
• Efficient packet loss recovery using SACK.
• Higher throughput than TCP in ad hoc networks.
• Better fairness among multiple flows.

Que] ESRT:
ESRT – Event-to-Sink Reliable Transport (WSN)
• Key Concept:
• Provides upstream reliability and congestion control.
• Works using end-to-end feedback between sink and sensor nodes.

• Main Features:
1. Reliability Computation:
o Calculates r = rate of successful packet delivery over a time period.
2. Reporting Frequency Adjustment:
o Determines required reporting frequency (f) using a function:
f = G(r)
o Adjusts sensor data rate to match required reliability.
3. Sink-to-Sensor Communication:
o Sink broadcasts updated frequency (f) to all sensors using a high-
power channel.
4. End-to-End Control:
o Entire control is from sink to sensors, based on global reliability
feedback.
• Advantages:
• Ensures desired reliability at the sink.
• Controls congestion by adjusting reporting rate.
• Helps in energy conservation by reducing unnecessary transmissions.
• Suitable for event-driven WSN applications.

Que] What is Authenticity? / Digital Signatures:

• Authenticity refers to the assurance that a message:
• Is from the genuine sender, and
• Has not been altered during transmission.
It verifies the origin and integrity of the data.

Message Authentication Code (MAC)

A MAC is used to ensure the integrity and authenticity of a message
using a shared secret key.
• Working:
1. Sender and receiver share a secret key.
2. Sender generates a MAC using the key and the message.
3. The MAC is sent along with the message.
4. Receiver uses the same key to compute the MAC.
5. If the computed MAC matches the received one, the message is authentic
and unchanged.
Key Points:
• Uses symmetric key.
• Only parties with the shared key can verify authenticity.
• Fast and efficient.

• Digital Signature:
 A digital signature uses asymmetric key cryptography to verify
authenticity and integrity.
1. Sender has a private key (Ks) and a public key (Kp).
2. Sender generates a signature (S) using the private key and message:
o S = Sign (M, Ks)
3. Sender sends both the message (M) and the signature (S).
4. Receiver verifies the signature using the sender’s public key:
o Verify (S, M, Kp)
5. If verification is successful, the message is authentic.
Key Points:
• Uses asymmetric keys (private/public).
• Only the sender can generate the signature.
• Anyone with the public key can verify the signature.

Unit IV: Middleware and Network

Management for Wireless Sensor
Networks

• Middleware is usually below the application level and on top of the

operating systems and network protocols.
• Acts as an interface between applications and network protocols to
handle the special features of WSNs.
• Helps manage limited resources like bandwidth, computation,
communication, and energy.
• Supports dynamic topology due to node mobility, energy depletion,
and varying radio ranges.
• Enables quality of service (QoS) by adapting system behaviour to
meet application needs.
• Simplifies application development by hiding the complexity of
lower-level system details.
• Sits between the application layer and lower layers to ensure
efficient and flexible operation.
Que] WSN Middleware Principles?

• Use simple localized algorithms that work by talking to nearby nodes.

• Adjust quality vs resource use with adaptive fidelity (trade-offs).
• Focus on data-centric methods – work with data, not specific
sensors.
• Include application knowledge to save energy and use resources
better.
• Middleware should be lightweight – use less memory and power.
• Make QoS trade-offs because not all apps can get full quality at once.
• Understand features of both apps and protocols for smart decisions.
• Build a smart link between apps and network based on current
conditions.
• Provide services that control and manage the network smartly.
• If needed, middleware can tell apps to reduce their demands for
better performance.

Que] WSN Middleware Architecture in detail:

• Middleware sits between the application and network protocols.

• It collects info from both applications and protocols to make decisions.
• Sometimes, it can interact directly with the operating system, skipping the
network layer.
• Middleware’s main goal is to adjust network settings and save energy
while keeping good performance.
➔ Key Layers in WSN Middleware Architecture:
1. Application Layer:
o Where user applications run, such as environmental monitoring or
smart city applications.
2. Middleware Layer:
o Task Management: Schedules and manages sensor tasks like data
collection and processing.
o Communication Services: Manages communication between nodes
(handles routing, data transmission).
o Data Aggregation: Reduces data redundancy by combining sensor
data before transmission.
o Query Processing: Processes high-level queries (e.g., "average
temperature") from users.
o Resource Management: Manages energy, memory, and processing
resources efficiently.
3. Network Layer:
o Handles routing, data transmission, and topology management
between sensor nodes.
4. Sensor Hardware Layer:
o The physical components of the sensor network (sensors,
processors, communication units).

➔ Main Functions of Middleware:

• Energy Efficiency: Optimizes power usage to prolong the network's
lifetime.
• Data Aggregation: Combines data from multiple sensors to minimize
communication.
• Task Scheduling: Ensures efficient execution of network tasks.
• Query Handling: Allows users to query sensor data easily without dealing
with low-level details.
• Security: Ensures safe communication between nodes in the network.

Middleware simplifies communication, data management, and energy

optimization in WSNs.
It ensures efficient and scalable sensor network operation, making it
easier to develop and manage applications.
 +------------------------------------+
| Application Layer |
| (User Applications, User Interface) |
+------------------------------------+
|
|
+------------------------------------+
| Middleware Layer |
| (Task Scheduling, Data Aggregation, |
| Communication, Resource Mgmt.) |
+------------------------------------+
|
|
+------------------------------------+
| Network Layer |
| (Routing, MAC, Topology Mgmt) |
+------------------------------------+
|
|
+------------------------------------+
| Sensor Hardware Layer |
| (Sensing, Processing, Communication) |
+------------------------------------+

Que] MANNA Architecture in detail:

(Management Architecture for Sensor Network)
 • MANNA is a comprehensive management framework designed
specifically to address the unique challenges of managing Wireless
Sensor Networks.
• It adapts traditional network management concepts and introduces
WSN-specific functionalities.

➔ Three Management Dimensions in MANNA:

MANNA’s architecture is structured along three dimensions

a) Function Areas (Management Functions):

These are inspired by SNMP’s five traditional management areas:
• Fault Management:
Detects, isolates, and corrects faults in the network.
• Configuration Management:
Most critical function in MANNA; it manages sensor node configurations
and supports other functions like fault and performance management.
• Performance Management:
Monitors network performance metrics like throughput, latency, and
energy consumption.
• Security Management:
Ensures authentication, encryption, and access control in WSN
communication.
• Accounting Management:
Tracks resource usage and operational cost—less emphasized in WSNs
but still considered.
b) Management Levels:
MANNA adopts a hierarchical approach to management:
1. Network Element Level:
o Direct interaction with individual sensor nodes.
o Basic data collection and control.
2. Network Element Management Level:
o Local management of grouped nodes or clusters.
o Performs localized monitoring and fault detection.
3. Network Management Level:
o Manages the entire WSN.
o Handles routing protocols, topology changes, and energy
management.
c) WSN Functionalities Introduced by MANNA:
MANNA goes beyond traditional management and incorporates essential WSN-
specific functions:
 • Configuration: Setup and dynamic reconfiguration of sensor nodes.
• Maintenance: Handles battery levels, replacements, or recovery from
failures.
• Sensing: Ensures accurate and timely sensing of environmental data.
• Processing: Includes local data processing and compression to save
energy.
• Communication: Manages routing, data transmission, and reliability.

➔ Three Architectural Elements of MANNA:

a) Functional Architecture
• Defines key management entities:
o Manager: Controls and monitors the network.
o Agent: Embedded in sensor nodes to carry out manager’s
instructions.
o MIB (Management Information Base): A database that stores
information about network status and configurations.
• Also defines the location scheme for placing managers and agents.
b) Physical Architecture
• The hardware and network topology where functional components
(managers, agents, MIBs) are deployed.
• Can include cluster heads, gateways, base stations, etc.
c) Information Architecture
• Provides an object-oriented model to:
o Represent and map manageable network resources.
o Define classes and objects for different entities.

➔ Features:
1. Three-dimensional management: Combines function areas, management
levels, and WSN functionalities.
2. Centralized configuration management: All other functions rely on
configuration.
3. Lightweight protocol: Ensures energy-efficient communication.
4. Object-oriented model: Maps network resources using managed object
classes.
5. Hierarchical levels: Manages from individual nodes to business-level
operations.
Que] Middleware Data Related Functions? / Data Compression
& Data Storage:

Since WSN is a data-centric device, middleware would contain data

management functions such as data dissemination, data compression, and data
storage.

A] DATA DISSEMINATION-

• Data dissemination refers to the process of transmitting sensed data from

sensor nodes to a special node called the sink for analysis, control, and
management.
• A data dissemination protocol is required to ensure effective and reliable
transmission of data from the nodes to the sink.
• Routing protocols focus on finding a path between source and destination
nodes, but Data dissemination protocols ensure successful data delivery
specifically from sensor nodes to the sink.
➔ Phases of Data Dissemination Protocols
• Initial Phase: Triggered by the sink by sending a query to sensor nodes.
o The query contains information such as:
▪ Type of data required
▪ Frequency of data reporting
▪ Time duration for reporting
• Data Transmission Phase: Sensor nodes report the data to the sink.
o Data can be transmitted in either broadcast or unicast mode.
o Performance can be improved using techniques like routing, data
replication, and caching.
• Data dissemination protocols are essential for efficient, reliable, and
energy-aware communication in WSNs.
• They differ from standard routing by focusing on sink-oriented data flow
and network-specific optimizations.

B] DATA COMPRESSION-

• Communication components consume most of the energy in WSNs.

• Computation consumes less energy than communication.
 • Data compression increases computational energy slightly but reduces the
number of transmissions, saving overall energy.
➔ Features of WSNs That Support Data Compression:
1. Data Correlation: Data from neighboring sensor nodes is often correlated,
especially in dense deployments.
2. Tree-like Topology: Data correlation increases as it flows from sensor
nodes toward the sink.
3. Event as a Random Process: Events can be modeled as continuous-time
random processes; sampling can help extract meaningful data.
4. Application Semantics: Applications may allow for data aggregation or
data fusion.
5. Error Tolerance: Many applications can tolerate small errors, allowing
reduced data reporting and sampling frequency.
➔ Common Data Compression Techniques in WSNs:
1. Information Theoretic–Based Techniques
o Example: DISCUS (Distributed Source Coding using Syndromes)
o Based on Slepian–Wolf coding.
o Designed for dense sensor networks.
o Uses correlations between data from parent and child nodes.
o Compression happens at nodes; decompression occurs at the sink
or in cooperation with nodes.
2. Data Aggregation–Based Techniques
o Example: TAG (Tiny Aggregation Service)
o Performs aggregations like MIN, MAX, SUM based on application
needs.
o Effective only when applications support such semantic operations.
o Challenge: Selecting the correct aggregation point in the network.
3. Adaptive Sampling of Random Processes
o Reduces the sampling frequency when some error tolerance is
allowed.
o Saves energy while maintaining acceptable accuracy in data
collection.
• Data compression helps reduce energy consumption in WSNs.
• Compression is effective due to data correlation and application-level
flexibility.
• Different techniques are chosen based on application type, network
structure, and data sensitivity.

C] DATA STORAGE-
 • Sensor nodes collect raw data and analyzed results (e.g., event details,
location).
• Data needs to be stored for future analysis, querying, and decision-
making.
➢ Types of Data Storage Techniques
1. Local Storage (LS)
• Each sensor node stores the data it collects.
• Simple to implement.
• Not energy-efficient for frequent queries, especially from distant nodes.
• Advantage: During queries, data location is already known.
2. Data-Centric Storage (DCS)
• Data is stored based on event type at special nodes called home nodes,
not necessarily where the data was sensed.
• Queries are routed to the relevant home node based on data type.
• Advantages:
o Energy efficient.
o Easy load balancing using distributed hash tables.
• Limitation: Cannot trace data origin (provenance).
3. Provenance-Aware Data Storage (PADS)
• Designed for applications that need to know where the data came from.
• Data is stored locally like LS.
• An index or pointer is stored at a home node (like DCS).
• Advantage: Combines the benefits of both LS and DCS.
4. Multiresolution Storage (MRS)
• Data is classified into multiple levels:
o Level 0: Raw data (shortest storage time)
o Level 1: Medium level detail
o Level 2: Coarse summary (longest storage time)
• Ensures differentiated storage based on data importance.
• Advantages:
o Good load balancing
o Low communication overhead

Que] Existing Middleware in detail:

A] MiLAN:
• MiLAN defines two classes of applications: data-driven applications
(collect and analyze data) and state-based applications (in which
application requirements.
 • Data-driven: Focus on collecting and analyzing data.
• State-based: Application behavior changes based on received data.
• Allows applications to actively influence the network and sensors.
• Aims to meet QoS (Quality of Service) needs while extending application
lifespan.
• Information Required by MiLAN-
1. Variables important to the application.
2. QoS requirements for each variable.
3. QoS levels that sensors can provide.

➔ Working Mechanism:

• Application gives a feasible set of sensors (fa) based on QoS.

• MiLAN discovers network conditions (sensor types, modes, energy).
• Finds a network feasible set (fn).
• Chooses optimal sensors from the overlap to fulfil QoS and extend
application life.

➔ Features:
• Dynamically configures the network based on application needs.
• Suggests routing protocol modifications for saving energy.
• Not ideal for applications with only one variable of interest.

B] IrisNet (Internet-Scale Resource-Intensive Sensor Networks

Services):
1. Purpose:
• Extends traditional WSNs into a worldwide sensor web.
• Integrates both high bit rate sensors (like webcams) and low bit
rate WSNs.

2. Architecture:
• Two-tier system:
• Sensing Agents (SAs): Collect and process data from sensors.
• Organizing Agents (OAs): Store service-specific data in a
distributed database.

3. Data Handling:
• Uses XML to represent sensor data in a structured way.
 • Employs adaptive data placement to reduce query time and
network load.

4. Senselets:
• Small programs uploaded to SAs.
• Control how SAs collect, process, and send data to nearby OAs.
• Senselets are small programs uploaded to SAs to control how data
is collected, processed, and sent to nearby OAs

5. Features and Limitations:

• Supports data collection, filtering, combining, and distributed
queries.
• Not optimized for resource-limited WSNs (doesn't use localized
algorithms or consider WSN constraints).
• WSNs as it does not consider localized algorithms or WSN
application features.

C] AMF (Adaptive Middleware Framework):

1. Purpose: Reduces energy consumption in data collection by balancing
resource usage and application QoS requirements.
2. Approximate Data Collection: Collects data at predetermined accuracy
levels while meeting application QoS needs.
3. Components:
• Sensor-side: Manages sensor-state and adapts precision based on the
data.
• Server-side: Manages application quality, data translation, adaptive
precision, sensor selection, data management, and fault tolerance.
4. Energy-efficient Message-updating: Sensors send updates only when
the measurement exceeds previous values or predicted error levels.
5. Active Sensors List: The server keeps an active list of sensors and their
historical data for better management.
6. Prediction-based Adaptation: Uses prediction models to adjust sensor
data collection based on network status.
7. Trade-off between Resource and Quality: Reduces sampling
frequency without compromising data accuracy.

D] DSWare (Data Service Middleware):

1. Position in Architecture: Resides between the application and network
layers, providing a database-like abstraction.
2. Components:
• Data Storage: Manages data replication across multiple physical nodes.
• Data Caching: Monitors data usage and adjusts the number of copies or
their location.
• Group Management: Ensures localized cooperation among sensor
nodes.
• Event Detection: Detects compound events and calculates confidence
levels for event occurrence.
• Data Subscription: Minimizes communication between sensor nodes.
• Scheduling: Performs real-time query scheduling.
3. Data Replication: Data is replicated across physical nodes mapped to a
single logical node using hash-based mapping.
4. Event Detection: Uses a confidence function to detect compound events.
A report is sent only when the event reaches a threshold confidence level.
5. Energy Efficiency: Optimizes energy use through reliable event
detection and phase/validity interval mechanisms.
6. Event Registration: Uses SQL language to register and cancel events.
7. Network Protocol: Network protocol selection is static and independent
of applications.
8. Limitations: Cannot capture specific application requirements.

Que] Challenge in design of middleware:

Energy Use: Middleware needs to save energy since sensor nodes have
limited battery life.
Scalability: It must work well as the network grows and data volume.
Real-time Processing: It should handle data and tasks in real-time for time-
sensitive applications.
Diverse Components: It must support various sensor types, communication
methods, and protocols.
Fault Handling: The system should be resilient to node failures and network
issues.
 Data Management: Efficiently storing, retrieving, and managing large data is
a challenge.
Quality of Service (QoS): It needs to meet specific requirements like data
accuracy and speed.
Security: Ensuring secure communication and data privacy is crucial.
Adaptability: The system should adjust to changing network conditions or
application needs.
Integration: It must work well with existing infrastructure and various
applications.

Que] Applications of middleware:

Environmental Monitoring: Middleware helps in integrating data from
sensors to monitor environmental conditions like temperature, humidity, and air
quality.
Health Monitoring: Middleware supports applications that collect and
analyze health data, such as patient vital signs, for remote health monitoring.
Smart Cities: It enables various smart city applications like traffic
monitoring, waste management, and energy usage optimization through data
from sensor networks.
Agriculture: Middleware facilitates precision farming by integrating data
from sensors that monitor soil conditions, weather, and crop health.
Industrial Automation: Middleware is used to monitor industrial machinery,
track production processes, and ensure safety through data collection from
sensor nodes.
Disaster Management: Middleware can support emergency response systems
by gathering data from sensors placed in disaster-prone areas to detect hazards
like earthquakes, floods, or fires.
Military Applications: Middleware enables surveillance, reconnaissance, and
battlefield monitoring by collecting and analyzing sensor data in real-time.
Smart Homes: Middleware allows for smart home automation systems to
integrate various sensors for tasks like temperature control, security, and energy
management.

Que] NETWORK MANAGEMENT REQUIREMENTS:

Network Management in WSN is the process of administrating and
coordinating all sensor nodes and network resources to achieve reliable
data communication, efficient energy use, fault handling, and performance
monitoring in real-time.
• A communication network includes physical devices (links, nodes,
terminals, servers), protocols, and the information being carried
(applications).
• Protocols transport information efficiently, securely, and reliably,
supporting the communication between devices.
➔ Need for Network Management (NM):
• Ensures cooperation between heterogeneous devices and software entities
in the network.
• Helps identify, diagnose, and restore network faults.
• Optimizes system performance (e.g., congestion control, route changes).
• Gathers and analyzes user behavior for future network planning and
capacity evolution.
➔ NM Functions:
• Monitors network status.
• Detects faults and abnormalities.
• Manages, controls, and configures network components.
• Improves network efficiency and application performance.
• NM collects real-time data from devices.
• Information is stored in a Management Information Base (MIB) for each
device.
• An agent in each device collects and reports information to a central
network management system.
Network management acts as an application that performs monitoring, fault
detection, and performance optimization tasks.

Que] ISSUES / Challenges during network management in

WSN:

Naming:
• Low-Level Naming: Uses node addresses, independent of the application
but dependent on topology and location.
• High-Level Naming: Application-dependent and location-independent.
Built on top of low-level naming.
• Application-Oriented Low-Level Naming: More efficient for WSNs as it
avoids mapping overhead and location dependency, making it suitable for
energy efficiency and fault tolerance.

Localization:
• Knowing the location of sensor nodes is crucial for many applications
(e.g., tracking, location-based routing, and security).
• GPS: Provides precise location data but is costly for large networks.
• Non-GPS Localization: More practical, either hardware-dependent (using
signal strength) or topology-dependent (using "seed nodes" with known
locations).
• Localization Schemes:
o Centralized: A central node calculates and informs sensor nodes of
their locations.
o Distributed: Each sensor node determines its own location
independently.
o Range-Based: Requires range information like time of arrival or
angle of arrival.
o Range-Free: Seed nodes broadcast location information to help
other nodes estimate their locations.

Maintenance:
• Involves replacing batteries, maintaining connectivity, and configuring
nodes for long-term operation.
• Fault tolerance and hardware backup strategies are crucial for ensuring
network resilience.

Fault Tolerance:
• Addresses issues caused by hardware or software failures using
techniques like multipath routing or redundant connections to ensure
continued network functionality.

Energy Efficiency:
• Minimizing energy consumption is crucial for sensor networks, where
nodes are often battery-powered. Techniques include low-power
communication, efficient routing, and energy-aware algorithms.

Scalability:
 • Managing a large number of sensor nodes in a network requires scalable
solutions for data collection, routing, and maintenance, especially in
dynamic or large-scale deployments.

Security:
• Protecting the network from unauthorized access, data tampering, and
attacks is vital. Security mechanisms, such as encryption and
authentication, are required to safeguard the network’s integrity and
privacy.

Que] Design issues in network management / Performance

issues:
Scalability: Must handle large numbers of nodes without performance
loss.
Energy Efficiency: Need to conserve energy as sensor nodes are
battery-powered.
Fault Tolerance: Ensure the network continues working despite node
failures or environmental issues.
Real-time Monitoring: Need to adapt to changes and collect data in
real time.
Localization: Accurately determine sensor node locations without
expensive hardware like GPS.
Data Aggregation: Minimize data transmission by aggregating
information to save bandwidth and energy.
Security and Privacy: Protect sensitive data with encryption and
secure communication.
Heterogeneity: Manage diverse sensor nodes with different
capabilities efficiently.

Que] Performance and Traffic Management Issues in (WSNs):

• WSNs have limited energy, bandwidth, and processing power, so

managing traffic is crucial.
• Too much data can cause congestion, delay, and packet loss.
 • Traffic control (like data aggregation and smart routing) helps
improve speed, reduce energy use, and keep the network working
smoothly.
• Some issues are:
Limited Bandwidth: WSNs have low data rates; too much traffic can
cause delays and packet loss.
Congestion: High traffic from many nodes can cause network
congestion, leading to reduced performance.
Packet Loss: Due to wireless interference, collisions, or buffer
overflow, data packets may be dropped.
Latency: Delay in data delivery can affect real-time applications like
fire or gas leak detection.
Energy Drain: More traffic means more energy used for transmission,
reducing node lifespan.
Load Balancing: Uneven traffic can overload some nodes; traffic must
be distributed evenly.
Routing Overhead: Managing routes in a dynamic network consumes
bandwidth and energy.
Data Redundancy: Multiple nodes may sense the same data, causing
unnecessary traffic.

Que] Fundamentals of network security-challenges and

attacks:

➔ Fundamentals of Network Security in WSN:

1. Confidentiality
Confidentiality ensures that sensitive data transmitted through the
network is not accessed by unauthorized parties. In WSNs, data
confidentiality is crucial because sensor nodes often collect private or
critical information. Encryption techniques are used to protect the data
during transmission.
2. Integrity
Data integrity guarantees that information sent over the network is not
tampered with or altered during transmission. Attacks such as data
modification or injection can compromise integrity. Message
authentication codes (MACs) are often used to ensure data integrity.
3. Authentication
Authentication ensures that data is exchanged between trusted nodes.
 Each node must verify the identity of other nodes before accepting data or
commands. This prevents malicious nodes from impersonating legitimate
ones.
4. Availability
The network services must be available whenever required. Attacks like
Denial of Service (DoS) or jamming can disrupt the network and make it
unavailable. Security mechanisms should ensure minimal disruption and
energy-efficient recovery.
5. Freshness
Data freshness implies that the data is recent and has not been reused by
an adversary. This is particularly important to prevent replay attacks.
Nonces or timestamps can be used to ensure freshness.

➔ Challenges in Securing WSNs:

1. Resource Constraints
Sensor nodes have limited computational power, memory, and battery
life. These limitations restrict the use of complex encryption or
authentication algorithms, making security implementation challenging.
2. Unattended Operation
Sensor nodes are often deployed in remote or hostile environments,
making them vulnerable to physical attacks, tampering, or theft. Secure
node management becomes difficult.
3. Scalability
WSNs may consist of hundreds or thousands of nodes. Implementing a
scalable security mechanism that works efficiently across all nodes is a
significant challenge.
4. Dynamic Topology
Due to node failure, addition, or mobility, the network topology changes
frequently. Security protocols must adapt to these changes without
compromising protection.
5. Node Capture
If a node is physically captured by an attacker, its stored information such
as cryptographic keys can be extracted and misused, threatening the
whole network.

➔ Types of Attacks in WSN:

1. Eavesdropping
In this passive attack, an adversary listens to communication between
nodes to gather confidential information. It violates the confidentiality of
the network.
 2. Wormhole Attack
Two or more malicious nodes establish a tunnel between them and replay
packets, causing routing confusion. Nodes near one attacker may wrongly
believe they are close to another node in the network.
3. Denial of Service (DoS)
This attack overwhelms nodes or communication links with traffic,
making them unavailable for legitimate use. It affects the availability of
network services.
4. Replay Attack
Previously captured messages are retransmitted to create confusion or
gain unauthorized access. This compromises both freshness and
authentication.

Que] TRADITIONAL NETWORK MANAGEMENT MODELS:

➔ Simple Network Management Protocol (SNMP):

• SNMP is widely used for managing traditional networks.

• Three main components:
1. NMS (Network Management System): Software that
monitors/controls devices.
2. Managed Elements: Devices like routers, switches, servers, etc.
3. Agents: Software on devices that collects status info and stores it in
MIB (Management Information Base).
• Data exchange happens using PDUs (Protocol Data Units).
o 5 PDU types: For reading data, configuring devices, and detecting
events (Trap messages).
• Advantages:
o Simple and widely used.
• Disadvantages:
o High bandwidth use (gets one value at a time).
o Not suitable for full network-level management.

➔ Telecom Operation Map (TOM):

• TOM is a model for telecom network and service management.

• Designed by TeleManagement Forum.
• It includes:
o Vertical layers:
 ▪ Network & systems management
▪ Service operations
▪ Customer care
o Horizontal functions:
▪ Service fulfillment
▪ Service assurance
▪ Billing
• Limitation:
o Not specific to WSNs, but its structured approach can help design
WSN management systems.

Que] Applications of network management in WSN:

Monitoring Network Health:
• Checks the status of sensor nodes (active/inactive, battery level).
• Ensures connectivity between nodes.

Fault Detection & Recovery:

• Identifies malfunctioning or failed nodes.
• Supports automatic recovery through rerouting or node replacement.

Energy Management:
• Controls node activity to save battery.
• Helps in scheduling sleep and active cycles of nodes.

Data Traffic Management:

• Balances load to avoid congestion.
• Optimizes routing paths to reduce delay and packet loss.

Security Management:
• Detects unusual activity or intrusions.
• Manages encryption keys and access control.

Configuration Management:
• Helps in updating software or settings of sensor nodes remotely.

Localization and Naming:

• Tracks the physical location of sensor nodes.
• Assigns and manages unique identifiers for communication.