Unit 2: Introduction to IoT - Subjective Questions

Internet of Things (IoT) is a network of physical objects, devices, sensors, actuators, and software systems that collect, exchange, and act on data through communication networks, often the Internet.

Fundamental characteristics:

• Connectivity: Devices communicate with gateways, cloud platforms, or other devices using wired or wireless networks.
• Sensing: Sensors collect environmental or operational data such as temperature, location, motion, pressure, or humidity.
• Intelligence: Data is processed at the edge, gateway, or cloud to generate useful decisions.
• Actuation: Actuators perform actions based on received commands, such as switching off a motor or opening a valve.
• Interoperability: Devices from different vendors should communicate through common protocols and standards.
• Scalability: IoT systems must support a large number of constrained devices.

The main objective of IoT is to connect the physical and digital worlds so that monitoring, automation, prediction, and control can be performed efficiently.

A typical IoT architecture consists of multiple layers that move data from physical devices to users and control commands back to devices.

Major layers:

• Perception or device layer: Contains sensors, RFID tags, cameras, meters, and actuators. It senses real-world conditions and performs physical actions.
• Network or communication layer: Transfers data between devices, gateways, edge nodes, and cloud services using protocols such as Wi-Fi, Bluetooth Low Energy, Zigbee, LoRaWAN, and cellular networks.
• Processing or middleware layer: Stores, filters, analyzes, and manages collected data. This layer may use edge computing, fog computing, or cloud computing.
• Application layer: Provides user-facing services such as smart home dashboards, health monitoring applications, industrial automation systems, and smart city solutions.
• Business layer: Handles policies, billing, analytics, reporting, compliance, and business decision-making.

Data generally flows upward from sensors to applications, while control commands flow downward from applications to actuators.

The network layer is responsible for delivering packets from a source IoT device to a destination device or service across one or more networks.

Key functions of the network layer in IoT:

• Logical addressing: Uses IP addresses, especially IPv6, to identify devices.
• Routing: Selects paths for forwarding packets through mesh networks, gateways, and the Internet.
• Packet forwarding: Moves packets between network nodes.
• Inter-network communication: Enables constrained sensor networks to communicate with cloud systems and enterprise networks.
• Adaptation for constrained devices: Supports mechanisms such as 6LoWPAN to carry IPv6 packets over low-power wireless links.

IPv6 is important in IoT because it provides a very large address space. The theoretical number of IPv6 addresses is , which is sufficient for billions of connected devices.

Common IoT network-layer technologies include IPv6, RPL, 6LoWPAN, and ICMPv6.

IPv4 and IPv6 are Internet Protocol versions used for addressing and routing packets. IPv6 is generally more suitable for large-scale IoT deployments.

Why IPv6 benefits IoT:

• It provides unique addresses for a huge number of devices.
• It improves end-to-end connectivity.
• It supports auto-configuration.
• Its simplified header can reduce processing overhead.
• It works well with 6LoWPAN for constrained wireless networks.

6LoWPAN stands for IPv6 over Low-Power Wireless Personal Area Networks. It is an adaptation layer that allows IPv6 packets to operate efficiently over constrained wireless networks such as IEEE 802.15.4.

IEEE 802.15.4 frames have a small maximum payload size, commonly 127 bytes. A standard IPv6 header alone is 40 bytes, so direct transmission can create excessive overhead.

Functions of the 6LoWPAN adaptation layer:

• Header compression: Compresses IPv6 and UDP headers to reduce packet size.
• Fragmentation and reassembly: Splits packets that are larger than the link-layer frame size and reassembles them at the receiver.
• Mesh addressing: Supports forwarding across multi-hop low-power networks.
• IPv6 support: Enables constrained devices to participate in IPv6-based networks.

A simplified protocol stack is:

Thus, 6LoWPAN bridges the gap between Internet protocols and low-power sensor networks.

The transport layer provides end-to-end communication between IoT applications and services. In IoT, transport protocols must operate efficiently despite limited bandwidth, battery capacity, memory, and processing power.

Important transport-layer requirements:

• Low overhead: Protocol headers and control messages should be small.
• Reliability when required: Some applications, such as industrial control, need reliable delivery.
• Low latency: Real-time monitoring and control require quick communication.
• Congestion control: Prevents excessive packet loss when many devices communicate at once.
• Security support: Data should be protected during transmission.
• Compatibility: The transport layer should work with Internet-based applications and cloud services.

Common protocols:

• UDP: Lightweight, connectionless, and suitable for constrained applications such as CoAP.
• TCP: Reliable and connection-oriented, commonly used with HTTP and MQTT.
• QUIC: A modern transport protocol that combines reliability, encryption, and reduced connection setup time in some IoT-cloud scenarios.

The choice depends on the application's reliability, latency, energy, and message-size requirements.

TCP is suitable when:

• Data loss is unacceptable.
• A device uploads logs, records, or firmware images.
• MQTT is used for reliable broker-based communication.

UDP is suitable when:

• Devices have tight energy and bandwidth constraints.
• Small sensor readings are transmitted frequently.
• Low latency is more important than guaranteed delivery.

In practical IoT systems, TCP and UDP are selected according to application requirements rather than treating one as universally better.

The application layer provides protocols and services through which IoT devices, gateways, cloud platforms, and end users exchange meaningful application data.

Responsibilities of the IoT application layer:

• Defines message formats and communication models.
• Supports device monitoring and remote control.
• Enables data collection, visualization, alerts, and analytics.
• Integrates devices with cloud platforms and enterprise systems.
• Provides security mechanisms such as authentication and encryption support.

Common IoT application-layer protocols:

• MQTT: Lightweight publish-subscribe protocol commonly used for telemetry.
• CoAP: Lightweight REST-based protocol designed for constrained devices.
• HTTP/HTTPS: Web protocol used for cloud APIs and web applications.
• AMQP: Message-oriented protocol for reliable enterprise communication.
• XMPP: Messaging protocol that can support device communication.
• DDS: Data-centric protocol used in real-time and industrial systems.

Application-layer protocol selection depends on device capability, communication pattern, latency, reliability, and security needs.

MQTT, or Message Queuing Telemetry Transport, is a lightweight application-layer messaging protocol designed for low-bandwidth, high-latency, or unreliable networks.

MQTT uses a publish-subscribe model involving three entities:

• Publisher: Sends a message to a named topic.
• Broker: Receives messages from publishers and distributes them to relevant subscribers.
• Subscriber: Receives messages for topics it has subscribed to.

For example, a temperature sensor may publish data to the topic building/floor1/temperature. A dashboard and alert service can subscribe to the same topic.

Important MQTT features:

• Small protocol overhead.
• Decoupling between sender and receiver.
• Topic-based communication.
• Quality of Service levels:
  • QoS 0: At most once delivery.
  • QoS 1: At least once delivery.
  • QoS 2: Exactly once delivery.
• Retained messages and last-will messages.
• Support for persistent sessions.

MQTT is widely used in smart homes, remote monitoring, industrial telemetry, and cloud-connected IoT systems.

CoAP, or Constrained Application Protocol, is a lightweight web transfer protocol designed for constrained IoT devices and low-power, lossy networks.

CoAP follows a REST-style model similar to HTTP. It uses methods such as:

• GET for retrieving a resource.
• POST for creating or submitting data.
• PUT for updating a resource.
• DELETE for removing a resource.

CoAP Observe allows a client to register interest in a resource and receive updates when its state changes. This is useful for events such as changing temperature, motion detection, or device status.

CoAP is preferred where low energy consumption and compact messages are important, while HTTP is often used for direct integration with web services.

CoSIP can be understood as a protocol approach for communication and service interaction in constrained IoT environments. Its purpose is to support efficient exchange of service-related information among resource-constrained devices, gateways, and applications.

A CoSIP specification should clearly define the following aspects:

• Message structure: Fields for device identity, service request, response, payload, timestamp, and status.
• Addressing and identification: A method to uniquely identify devices, services, and endpoints.
• Communication model: Whether communication is request-response, publish-subscribe, event-driven, or hybrid.
• Transport binding: Whether the protocol operates over UDP, TCP, or another transport mechanism.
• Resource discovery: How a device discovers services and available resources.
• Reliability: Acknowledgement, retransmission, duplicate detection, and timeout behavior.
• Security: Authentication, authorization, confidentiality, integrity, and key management.
• Interoperability: Compatibility with IPv6, 6LoWPAN, gateways, and standard IoT platforms.

The specification must minimize packet size and processing requirements while still providing reliable, secure, and interoperable service communication.

IoT uses different communication technologies depending on range, data rate, energy consumption, cost, and deployment environment.

Short-range technologies:

• Bluetooth Low Energy (BLE): Low power and suitable for wearables, medical sensors, and nearby devices.
• Zigbee: Supports low-power mesh networks for home and building automation.
• Wi-Fi: Offers higher data rates but generally consumes more power.
• NFC and RFID: Used for identification, access control, inventory tracking, and proximity-based communication.

Long-range technologies:

• LoRaWAN: Long range, low data rate, and low power; used in agriculture and smart-city applications.
• NB-IoT: Cellular low-power wide-area technology for massive IoT connectivity.
• LTE-M: Cellular technology supporting mobility and comparatively higher data rates.
• 4G/5G: Used for high-bandwidth, low-latency, or mobile IoT applications.

Wired technologies:

• Ethernet, CAN bus, Modbus, and industrial fieldbuses are common where reliability and stable power are available.

The selected technology must match the required communication range, battery life, data volume, reliability, and cost.

An IoT system is built from hardware, software, communication, and data-processing components.

Main components:

• Sensors: Measure physical values such as temperature, pressure, light, sound, position, or humidity.
• Actuators: Perform physical actions, such as controlling motors, locks, valves, lights, or alarms.
• Embedded controller: A microcontroller or processor reads sensor data, executes logic, and controls communication.
• Connectivity module: Provides network access through Wi-Fi, BLE, Zigbee, cellular, LoRaWAN, Ethernet, or another technology.
• Gateway: Aggregates local device data, performs protocol translation, filters data, and connects local networks to the Internet.
• Cloud or edge platform: Stores data, runs analytics, manages devices, and exposes application APIs.
• User application: A web dashboard, mobile app, or enterprise application used to monitor and control devices.
• Security mechanisms: Include identity management, encryption, authentication, secure boot, and access control.

Together, these components enable sensing, communication, processing, decision-making, and actuation.

An IoT gateway is an intermediate device or software service that connects local IoT devices and networks to cloud platforms, enterprise systems, or the Internet.

Major functions of an IoT gateway:

• Protocol translation: Converts between protocols such as Zigbee, BLE, Modbus, CoAP, MQTT, and HTTP.
• Data aggregation: Collects data from several sensors before forwarding it upstream.
• Edge processing: Filters, analyzes, or responds to data locally to reduce latency and cloud traffic.
• Security enforcement: Performs authentication, encryption, firewalling, certificate handling, and access control.
• Device management: Supports configuration, monitoring, diagnostics, and firmware updates.
• Offline operation: Stores data locally and forwards it after connectivity is restored.

For example, a smart factory gateway can collect data from multiple industrial sensors using Modbus and publish summarized data to a cloud platform using MQTT.

Edge computing processes data directly on sensors, controllers, or nearby devices. It is useful for real-time actions such as stopping a machine after detecting a hazardous condition.

Fog computing extends cloud capabilities closer to the network edge through gateways, routers, or local servers. It is useful for coordinating data from many nearby devices.

Cloud computing provides scalable storage, machine learning, dashboards, and global device management. It is suitable for historical analysis and centralized services.

A practical IoT architecture often combines all three approaches.

An IoT platform is a software environment that helps developers connect devices, manage data, build applications, and operate IoT deployments.

Examples of IoT platforms:

• AWS IoT Core
• Microsoft Azure IoT Hub
• IBM Watson IoT Platform
• Google Cloud IoT-based services
• ThingsBoard
• ThingSpeak
• Arduino IoT Cloud
• Blynk

Features expected from an IoT platform:

• Device connectivity: Support for MQTT, HTTP, CoAP, WebSockets, or other protocols.
• Device registry: Maintains device identities and metadata.
• Authentication and authorization: Controls which users and devices may access services.
• Data ingestion: Receives telemetry from connected devices.
• Storage and analytics: Stores data and supports reporting, rules, and machine learning.
• Dashboard support: Visualizes sensor values, alarms, and device states.
• Device management: Enables remote configuration, monitoring, and over-the-air firmware updates.
• Integration APIs: Connects IoT data with databases, enterprise systems, mobile apps, and cloud services.

The appropriate platform depends on scale, cost, protocol support, security requirements, and integration needs.

Smart homes:

• Smart thermostats adjust temperature based on occupancy and user preferences.
• Smart locks, cameras, smoke detectors, and lighting systems provide automation and security.
• Energy meters help reduce electricity consumption.

Healthcare:

• Wearable devices monitor heart rate, oxygen level, activity, and sleep patterns.
• Remote patient-monitoring systems send health data to doctors.
• Smart medication dispensers issue reminders and record medicine usage.

Agriculture:

• Soil-moisture sensors guide irrigation decisions.
• Weather stations measure rainfall, temperature, humidity, and wind conditions.
• Livestock tracking systems monitor the location and health of animals.

Industry:

• Sensors monitor machine temperature, vibration, pressure, and energy use.
• Predictive maintenance identifies possible equipment failure before breakdown.
• Asset tracking improves inventory visibility and logistics.

These applications use real-time data collection and automated decisions to improve efficiency, safety, cost control, and service quality.

IoT security and privacy are critical because IoT devices collect sensitive data and may directly control physical systems.

Major security challenges:

• Weak authentication: Default or weak passwords can allow unauthorized access.
• Insecure communication: Unencrypted messages can be intercepted or modified.
• Insecure firmware: Vulnerable firmware can be exploited by attackers.
• Lack of updates: Many devices do not receive timely security patches.
• Botnet attacks: Compromised IoT devices can be used for distributed denial-of-service attacks.
• Physical tampering: Devices deployed in public or remote locations may be physically accessed.

Privacy challenges:

• Location tracking through smart devices.
• Collection of personal health, activity, audio, or video data.
• Unclear ownership and sharing of collected data.
• Profiling of users from behavioral information.

Mitigation methods:

• Use strong authentication and unique device credentials.
• Encrypt data in transit and at rest.
• Apply secure boot and signed firmware updates.
• Follow least-privilege access control.
• Minimize collection of personal data.
• Maintain audit logs and security monitoring.

IoT deployments face several challenges because they combine heterogeneous devices, communication networks, software platforms, and physical environments.

Technical challenges:

• Interoperability: Devices may use different protocols, data formats, and vendor-specific interfaces.
• Scalability: Managing thousands or millions of devices requires efficient addressing, messaging, and data processing.
• Power constraints: Battery-powered devices require energy-efficient hardware and communication protocols.
• Network reliability: Wireless links may suffer from interference, packet loss, and intermittent connectivity.
• Data management: Continuous sensor streams create large volumes of data that must be stored and analyzed.
• Latency: Time-critical systems need rapid response from the device or edge layer.
• Security: Connected devices increase the attack surface.

Operational challenges:

• Device installation and maintenance.
• Remote monitoring and fault diagnosis.
• Firmware upgrades over the air.
• Compliance with privacy and safety regulations.
• Cost of connectivity, hardware replacement, and cloud services.

Successful IoT design requires planning for the complete device lifecycle, from deployment to retirement.

IoT protocol selection should be based on application requirements rather than choosing a protocol only because it is popular.

Selection criteria:

• Communication range: Short-range, local-area, or wide-area coverage.
• Power availability: Battery-powered devices need low-energy protocols.
• Data size and frequency: Small periodic readings need lightweight messaging.
• Latency requirement: Emergency control may require local and immediate communication.
• Reliability: Critical data may need acknowledgements and retransmissions.
• Scalability: The network should support the expected number of devices.
• Security: Encryption, authentication, and secure device management are required.
• Cost: Hardware, network subscription, and cloud costs must be considered.

Smart irrigation example:

• Soil-moisture sensors periodically collect readings.
• Sensors can use LoRaWAN or Zigbee because they send small data packets and should operate on batteries.
• A field gateway aggregates sensor data.
• The gateway can use MQTT over TCP/TLS to send telemetry securely to a cloud platform.
• The cloud analyzes moisture thresholds and weather forecasts.
• Commands are returned to a controller that activates irrigation valves.
• For immediate local control, edge logic can open a valve when moisture falls below a predefined threshold.

This combination provides low-power sensing, long-range communication, secure cloud integration, and reliable control.