IoT ASSIGNMENT – 2

Name:- SHRISHTI SINGH

Roll No. :- 1906139
Section:- IT-2
1.Home Automation
a. Smart Lighting: -

Step 1: Purpose and requirement specification

Purpose: should allow controlling of lights in a home remotely.

Behaviour: It should have auto and manual modes. In auto mode the system measures
the light level of the room and switches on the light accordingly. In manual mode the
system provides the option to the use for switching on/off the light.
System management requirement: provides remote monitoring and control functions
Data analysis requirements: should perform local analysis of data
Application Deployment Requirement: should be deployed locally on the device but
should not be accessible remotely.
Security Requirement: should have basic user authentication capabilities

Step 2: Process Specification

When the auto mode is chosen, the system monitors the light level. If the light level is
low, the system changes the state of light to “on”. Whereas if the light level is high, the
system changes the light level to “off”. When the manual mode is chosen the system
checks the light set by the user and accordingly sets the lighting.

Step 3: Domain Model Specification

Physical Entity: Room in the home and the light appliance to be controlled
Virtual Entity: There is virtual entity for the room to be monitored and for the appliance
to be controlled
Device: Single-board minicomputer which has light sensor and actuator
Resource: The on-device resource is the operating system that runs on the single-board
mini computer
Service: There are three services:
 A service that sets the mode to auto or manual, or retrieves the current mode
 A service that sets the light appliance state to on/off or retrieves the current light
stare
 A controller service that runs the native service on the device.
Step 4: Information Model Specification

There are two virtual Entities – a virtual entity for the light appliance and one for room.
The figure below shows the information model for home automation system.

Step 5: Service Specification

The mode service sets mode to auto or manual or retrieves the current mode. The stare
service sets the light appliance state to on/off or retrieves the current light state. The
controller service monitors the light level in auto mode and switches the light on/off
and updates the status in the database.

Controller service: -
Mode service: -

State service: -

Step 6: IoT Level Specification

We shall use level-1 for deployment of home automation system shown as below: -

Step 7: Functional View Specification

Device: the device FG includes a single board mini-computer, a light sensor and a relay
switch.
Communication: Communication protocols used in home automation are: - 802.11(link
layer), IPV4/IPV6(network layer), TCP (Transport layer), and HTTP(application layer).
The communication API used in the home automation system is REST-based API.
Services: There are two REST services (mode and state service) and one native service
(controller service).
Management, Security and Application: IoT devices maps to the Device FG and the
Management FG. Resources map to the Device FG and communication FG. Controller
service maps to the services FG. Web services map to services FG. Database maps to the
management FG and security FG. Application maps to the application FG, Management
FG and security FG.
These views can be visualised in the diagram below: -
Step 8: Operational View Specification

Devices: Computing device (raspberry Pi), light dependent resistor (sensor), relay
switch (actuator)
Communication API’s: REST APIs
Communication Protocols: 802.11(link layer), IPV4/IPV6(network layer), TCP
(Transport layer), and HTTP (application layer).
Services:
1. Controller Service – Hosted on device, implemented in python and run as native
service
2. Mode service – REST-full web service, hosted on device, implemented with Django-
REST framework
3. State service – REST-full web services, hosted on device, implemented with Django-
REST framework
Application:
 Web Application – Django Web Application
 Application Server – Django App Server
 Database Server – MySQL
Security:
 Authentication: Web App, Database
 Authorization: Web App, Database
Management:
 Application Management - Django App management
 Database Management – MySQL DB Management
 Device Management – Raspberry Pi device Management

Step 9: Device and Component Integration

Schematic Diagram as shown below is designed

Step 10: Application Development

The application developed has controls for the mode and the light. In the auto mode the
system controls the light while when auto mode is disables, the light is controlled by the
user.

b. Home Intrusion Detection

Step 1: Purpose and Requirements Specification

The purpose of home intrusion detection system is to detect intrusions using sensors
(such as PRI sensors and door sensors) and raise alerts, if necessary.

Step 2: Process Model Specification

Each room in the home has a PRI motion sensor and each door has door sensor. These
sensors can detect motion or opening of doors. Each sensor is read at regular intervals
and the motion detection or door opening events are stored and alerts are sent.

Step 3: Domain Model Specification

The domain model includes physical entities for room and door and the corresponding
virtual entities. The device here is a single-board mini computer which has PRI and door
sensors attached to it. The domain model is also included in the services involved in the
system
Step 4: Information Model Specification

The information model defines the attributes of room and door virtual entities and their
possible values. The room virtual entity has an attribute ‘motion’ and the door virtual
entity has an attribute ‘state’.

Step 5: Service Specification

The services are derived from the process specification and the information model. The
system has three services: -
1. A RESTful web service that retrieves the current state of a door from the database
or sets the current state of a door to open/closed
2. A RESTful web service that retrieves the current motion in a room or sets the
motion of a room to yes/no
3. A native controller services that runs on the device and reads the PIR and door
sensors and calls the REST services for updating the state of rooms and doors in the
database.
Door service: -

Room service: -

Controller service: -
Step 6: IoT level specification

We shall use level-2 for deployment of home intrusion system shown as below:-

Step 7&8: Functional view specification & Operational view Specification

The system uses Django framework for web application and REST service. The Django
web application is backed by a MySQL database. The IoT device used here is Raspberry
Pi along with PIR and door sensors
Step 9&10: Device and component integration & application development

Schematic diagram of the home intrusion detection system can be seen below

Sensors deployed in parking can be seen in the image below

2.Cities
a. Smart Parking

Step 1: Purpose and requirement specification

The purpose of a smart parking system is to detect the number of empty parking slots
and send the information over the internet to smart parking application backends.
Sensors are used for each parking slot, to detect whether the slot is empty or occupied.
This information is aggregated by a local controller and then sent over the Internet to a
server.

Step 2: Process Model Specification

Each parking slot has an ultrasonic sensor fixed above, which can detect the presence of
a vehicle in the slot. Each sensor is read at regular intervals and the state of the parking
slot (empty or occupied) is updated in the database.
Step 3: Domain Model Specification

The domain model includes a physical entity for the parking slot and the corresponding
virtual entity. The device here is a single -board mini computer which has ultrasonic
sensor attached to it. The domain model also includes the services attached to it.
Step 4: Information model specification

The information model defines the attribute (state) of the parking slot virtual entity
with two possible values (empty and occupied)

Step 5: Service Specification

The services are derived from the process specification and information model. The
smart parking system has two services: -
 A service that monitors the parking slots (using ultrasonic sensors) and updates the
status in a database on the cloud (REST web service)
 A service that retrieves the current state of the parking slots (controller native
service)
Controller Service: -

State Service: -

Step 6: IoT level specification

We shall use level-2 for deployment of smart parking system shown as below: -
Step 7 & 8: Functional View Specification & Operational view Specification

The functional view and the operation view specifications for smart parking system are
similar to home intrusion detection system. The system uses Django framework for web
application and REST service. The Django web application is supported by a MySQL
database. The IoT device used is Raspberry Pi along with the ultrasonic sensors. The
figure below shows the sensors deployed in parking.
Step 9 & 10: Device and component integration & Application Development

The schematic diagram of smart parking system is shown below.

Smart parking web application UI

3. Environment
a. Weather Monitoring System

Step 1: Purpose and process Specification

The purpose of the weather monitoring system is to collect data on environmental

conditions such as temperature, pressure, humidity and light in an area using multiple
end nodes. The nodes send the data to the cloud where the data is aggregated and
analysed.

Step 2: Process Model Specification

The process specification shows that the sensors are read after fixed intervals and the
sensor measurements are stored.

Step 3: Domain Model Specification

The physical entity is the environment which is being monitored. There is a virtual
entity for the environment. Devices include temperature sensors, pressure sensor,
humidity sensor, light sensor and single board minicomputer. Resources are the
software components which can be either on-device or network-resources. Services
include the controller service which monitors the temperature, humidity and light and
sends the readings to the cloud.
Step 4: Information model specification

There is one virtual entity for the environment being sensed. The virtual entity has
attributes – temperature, pressure, humidity and light.

Step 5: Service Specification

The service specification is derived from process and information model for the
weather monitoring system.
The controller service runs as a native service on the device and monitors temperature,
pressure, humidity and light once every 15 seconds. The controller service calls the rest
service to store these measurements in the cloud.
Step 6: IoT level specification

We shall use level-6 for deployment of weather monitoring system. The system consists
of multiple nodes placed in different locations for monitoring temperature, humidity
and pressure in an area. The end nodes are equipped with various sensors (such as
temperature, humidity and light). The end nodes send the data to the cloud and the data
is stored in a cloud database.

Step 7 & 8: Functional and operational view specification

The figure below shows the mapping deployment label to functional groups for thr
weather monitoring system
The figure below is an example of mapping functional groups to operational view
specifications for weather monitoring system.

Step 9 &10: Device and component Integration & Application Development

The schematic diagram for weather monitoring system is shown below. The devices and
component used here are Raspberry Pi mini computer, temperature sensor, humidity
sensor, pressure sensor and LDR sensor.
b. Weather Reporting Bot
This case study is about a weather reporting bot which reports weather information by
sending tweets on twitter. The schematic diagram can be seen below. The end-node
comprises of a Raspberry Pi mini-computer, temperature, humidity, pressure and light
sensors. USB webcam is also attached to the device.
The controller service obtains the temperature, humidity, pressure and light readings
from the sensors, every 30 minutes. At the same time an image is captured from the
webcam attached to the device. The sensor readings and the captured image is then sent
as tweet on Twitter. Twitter REST API is used for sending tweets.

c. Air pollution monitoring

Used to monitor emission of harmful gases by factories and automobiles using gaseous
and meteorological sensors. Just like weather monitoring system, it uses level-6
deployment and also the system design steps are similar to that of weather monitoring
system.
The system consists of multiple nodes placed in different locations for monitoring air
pollution in an area. The end nodes are equipped with CO and NO2 sensors. The end
nodes send the data to the cloud and the data is stored in a cloud database. A cloud-
based application is used for visualizing the data.
The end node includes a Raspberry Pi mini-computer, MICS-2710 NO2 sensor and
MICS- 5525 CO sensor. An A/D converter (MCP3008) is used for converting analog
inputs from the sensors to digital. The controller service runs as a native service on the
device and obtains the sensor readings every 10 seconds. The controller service calls
the Xively REST service to store there measurements in the cloud.

d. Forest Fire Detection

It uses a number of monitoring nodes deployed at different locations in a forest. Each
monitoring node collects measurements on ambient conditions such as temperature
and humidity to predict whether a fire has broken out.
The system is based on a level-5 IoT deployment with multiple end nodes and one
coordinator node. The end nodes perform sensing and the coordinator node collects
data from the end nodes and sends to the cloud.
The figure below shows the schematic diagram of forest fire detection end node. The
end node includes Raspberry Pi mini-computer and DHT-22 temperature and humidity
sensor.
Xbee is used for wireless communication between end node and coordination node.

Coordinator node: -
4. Agriculture
a. Smart Irrigation
IoT devices and soil moisture sensors are used to determine the amount of moisture in
the soil and release the flow of water through the irrigation pipes when the moisture
levels go below a certain threshold. Data on the moisture levels is also collected in the
cloud where it is analysed to plan watering schedules.
It uses level-6 deployment design methodology for its implementation. The system
consists of multiple nodes placed in different locations for monitoring soil moisture in a
field. The end nodes send the data to the cloud and the data is stored in a cloud database.
A cloud-based application is used for visualizing the data. The schematic diagram of
smart irrigation system is shown below.
The end node includes raspberry Pi mini-computer and soil moisture sensor. A solenoid
valve is used to control the flow of water through the irrigation pipe. When the moisture
level goes below a threshold, the valve is opened to release water.

5. Productive Applications
a. IoT Printer
IoT printer prints a daily briefing every morning. The daily briefing comprises of the
current weather information, weather predictions for the day and the user’s schedule
for the day.
The schematic diagram of IoT printer is shown below: -