ABSTRACT

Internet of Things (IoT) is the interconnection of physical objects or devices

that can transmit and receive data through the internet without human involvement. With the
advancement in IoT devices particularly in healthcare sector, huge amount of data is collected
from different sensors and all this data are transferred and stored in cloud. It becomes difficult to
handle such huge amount of data in cloud specially the healthcare data where it requires real time
data computation and storage. Security of the data is also major challenge in cloud. Fog
computing is the answer to overcome the challenges. Fog nodes works at the edge side and
enhances data security, accuracy, consistency and reduces the latency rate which is an important
factor for application like medical data. Implementation work is also described in the paper
where a digital human temperature sensor device is built using DS18B20 temperature sensor.
The data collected from it is being encrypted in fog node using Advance Encryption
Standard(AES) algorithm and it is send to cloud. Therefore, the security of the health care data is
enhanced using Fog computing.

1|Page
 1.INTRODUCTION
1.1 PROBLEM STATEMENT
With the advancement in IoT devices particularly in healthcare sector, huge amount of data is
collected from different sensors and all this data are transferred and stored in cloud. System
ensure safety on cloud from attacker or insider, this can prove helpful in government
organization or any IT-industry. The data collected from it is being encrypted in fog node using
Advance Encryption Standard (AES) algorithm and it is send to cloud. Fog computing
overcomes the scalability and reliability issues which is there in the traditional IoT-cloud
architecture. In Medical Diagnosis it is important to measure accurate pulse rate for prediction of
diseases. So, continuous monitoring of pulse rate with portable low cost system will always be in
need. System will take the information about the pulse using pulse rate sensor and predict the
chances of heart attack. Therefore, the security of the health care data is enhanced using Fog
computing. In the world of technology where we are living in, almost all the devices are
connected to internet. The number of IoT devices are increasing in an exponential rate and all
these devices are relying on cloud computing system for data computation and storage. It
becomes a bottle neck problem when it comes to realtime data operation which is the major
drawback in the existing IoT healthcare system [1]. In order to overcome the problem Fog
Computing concept has been introduced.

Fog Computing [2] in an archetype that extends the cloud computing platform. Fog acts as a
middle layer between the cloud server and the end devices. It is not the complete replacement of
cloud, rather it complements the functionality of cloud. Fog works closer to the edge devices and

2|Page
provides computing resources to these devices. Fog computing overcomes the scalability and
reliability issues which is there in the traditional IoT-cloud architecture. Since Fog nodes works
at the edge side and more geographically distributed as in (Fig:1), it enhances data security
[4][5], accuracy, consistency and reduces the latency rate which is an important factor for
application like medical data. As well as the overall bandwidth to cloud is saved, thus achieving
better quality of service(QoS).

1.2 PROBLEM SOLUTION

The solution to the above problem is to implement an AES algorithm [14] [15] in the fog node.
AES standard uses a symmetric block cipher technique to encrypt and decrypt the data. By
implementing such technique in the middle layer it provides double security of the data, one at
the fog layer and another the traditional security system in cloud. AES uses 16 bytes block
plaintext and key size which can be 128, 192 or 256-bits. Combining together it will produce a
cipher text as an output.

AES works on 4×4 column major order matrix. To convert the plaintext to cipher text it performs
multiple round of transformation depending on the key size. For 128-bits (16 bytes) – 10 cycles.
For 192-bits (24 bytes) – 12 cycles. For 256-bits (32 bytes) – 14 cycles. In this paper it will
describe the 256-bits key size AES algorithm [16].

A. AES algorithm:
In AES algorithm [13] each round consist of four steps and the plain text is divided into
16-byte block which is represented into 4×4 matrix. It creates a chain of substitution and
permutation network. Substitution- replacing inputs by specific outputs.

The rounds in AES operates on Substitution and Permutation network and each step is invertible.
The stages of encryption as in Fig4. Includes

(i) Key Expansion at the first stage

(ii) Initial Round where the AddRoundKey step will be performed

(iii) Rounds where the above mentioned cycle will be performed according to the size of the
key used and

(iv)Final Round which includes Byte substitution, ShiftRows and AddRoundKey. For
decryption it is just the inverse of encryption.

3|Page
 2.LITERATURE SURVEY
2.1 WORKING
There are different types of cryptography techniques used for privacy and security of the data.
Encryption is broadly divided into asymmetric and symmetric encryption. In the asymmetric
encryption technique, it uses two different key- a public key (for encryption) and a private key
(for decryption). In the symmetric encryption it uses only one key which is called the private key
which is used for both encryption and decryption. Symmetric encryption [6] is extremely
secured, simpler and 1000 times faster and as it uses only one secret key for both encryption and
decryption i.e. less computation power needed. This paper focuses on the symmetric encryption
technique called Advance Encryption Standard (AES). There are other older algorithms before
AES which are 3-DES and DES. Data Encryption Standard [7] (DES) uses 16-bits block size
plaintext and a 56-bits key size to generate a 64-bits Cipher text which is quite a weak encryption
algorithm. It can easily be cracked within 24 hours by using Brute force technique. So it cannot
be considered as a secure technique for encrypting sensitive medical data. Triple Data
Encryption Standard (3DES) is similar to DES except the key size can have 56 ,112 or 168 bits
but have same 16-bits block size. It is better than DES but still can be easily cracked. In order to
overcome the above issues AES algorithm is introduced. AES [11] [16] is a symmetric block
cipher standard adopted by the U.S government. It is considered to be more effective, advanced
and secured standard.

2.2 IMPLEMENTATION
In implementation a small IoT system is developed for collecting the data. A digital temperature
sensor is build using Arduino. Fig5: Circuit Diagram for Digital Temperature Sensor. The
hardware component used in this system are:

i) Arduino Uo R3 microcontroller

ii)USB Cabe

iii)4.7KΩ resistor

iv)DS18B20 Digital Temperature Sensor

v) Bread Board

vi)Wires An Arduino code is written in the Arduino IDE in order to run the system and the code
is uploaded to the Arduino broad for its performance. The DS18B20 sensor on the board will
sense the temperature data from the user and the data can be seen in the serial monitor of the
IDE. The Arduino itself doesn’t have data storage memory of its own. In order to save the data a
PLXDAQ interface is used. This software collects the data from the sensor directly and saves as

4|Page
an excel file. Fig6: Data collected in excel file. In order to encrypt the collected data an AES
algorithm is applied using PYTHON programming language. It is implemented using key size of
256-bits because larger the key size the operation rate reduces. 256-bits key size is large enough
and it will take years to figure out the possible key even by using Brute Force technique. So it is
impossible to crack the key by attackers. After encryption, the encrypted data can be stored to
cloud. There are multiple ways to get a cloud service provider [18] [19] [20], one of the easiest
and most convenient is the Amazon Web Services(AWS). AWS is a subservient of Amazon.com
that provides an circuit.

5|Page
 3.SYSTEM ANALYSIS
3.1 EXISTING SYSTEM

Currently in existing system the network such for computing tasks can be executed, and provide
tradeoffs with respect to requirements relevant to healthcare. Review indicates that (1) there is a
significant number of computing tasks in healthcare that require or can benefit from fog
computing principles, (2) processing on higher network tiers is required due to constraints in
wireless devices and the need to aggregate data, and (3) privacy concerns and dependability
prevent computation tasks to be completely moved to the cloud. Hence, security is the major
problem in existing system. Therefore; this system is not a very good way of securing data.

Disadvantages

To enhance the data security in IoT disease prediction system using fog computing. System will
take the information about the pulse using pulse rate sensor and predict the chances of heart
attack. The data entered by patient will be stored on cloud and get secured by using fog
computing. System will make use of random forest classifier to predict percentage of chance of
heart attack and will use AES algorithm to secure data.

3.2 PROPOSED SYSTEM

In the proposed system a three tier architecture [model is considered as in fig2. First layer will be
the Edge devices which will collect the data and this data will be transferred to the middle layer.
The middle layer will be the fog layer; encryption process of the collected data will be performed
in this layer. The encrypted data from the middle layer will then be send to the third layer which
is the cloud layer. In the cloud the final encrypted data will be permanently stored.

In this system we are implementing Random Forest Algorithm to carry out diagnosis of heart
disease and AES algorithm to secure the data generated by system. AES uses 16 bytes block
plaintext and key size which can be 128, 192 or 256-bits.

➢ In order to share data in the cloudlet, we use users’ similarity and reputation to build up trust
model. Based on the measured users’ trust level, the system determines whether data sharing
is performed.

6|Page
 ➢ The proposed system divides data in remote cloud into different kinds and utilizes
encryption mechanism to protect them respectively.
➢ The Proposed system proposes collaborative IDS based on cloudlet mesh to protect the
whole healthcare system against malicious attacks.
Advantages

➢ The security is more due to Collaboration Intrusion and Detection system.

➢ Implemented Cloudlet based data sharing which will give more security on
outsourced cloud data.
SYSTEM REQUIREMENTS

➢ H/W System Configuration:-

➢ Processor - Pentium –IV

➢ RAM - 4 GB (min)

➢ Hard Disk - 20 GB

➢ Key Board - Standard Windows Keyboard

➢ Mouse - Two or Three Button Mouse

➢ Monitor - SVGA

Software Requirements:
➢ Operating System - Windows XP
➢ Coding Language - Java 1.8
➢ Front End - HTML,CSS,JAVASCRIPT,JSP
➢ Back End - JDBC
➢ Database - MySQL 5.1.44
➢ IDE Tool: - Netbeans 8.1/8.2

7|Page
 4. SYSTEM DESIGN
4.1CLASS DIAGRAM

Cloud Server
Login, View all patients and authorize, View all doctors and authorize,
Vliew all patient Cloudlet data with enc format, View Patient data
Methods access request and authorize, View all Cloudlet Intruders details, View
patient details recovered details, View No.Of same symptoms in Chart,
View No.Of Patients refered same doctor in Chart,
Name,password,patient name,doctor name,chart,symptoms
Members
Attacker
Doctor Attacker
Enter patient name and inject
some false data.
Attacker
Register and Login,View Profile, View patient details and give
solution like Medicine details,Medical prescription details, View all Patient name,wrong data
Methods patient Medical prescription Details

Name,password,address,email,contactnumber,prescription
details,medicine details,patient details

Members
Register
Login, Register
Methods Register (), Reset ()
User Name, Password Login
Methods
User Name, Password, E-
Login (), Reset (),
Members mail, Mobile, Address, DOB,
Register ().
Members Gender, Pin code.

Patient
Wearable Device
Register and Login,View profile, Request Data Access
permission from cloudlet and view Response, Access Your data
Login, Collect Patient data and Upload to
Methods and select doctor from combo box and send to corresponding
Cloudlet, View all patient collecte data in
doctor, View doctor response with Medical prescription, Verify
enc format with digital sign
your data and recover, View and delete your details
Name,password,patient data,
Members name,password,address,contact number,doctor name,medical
pid,pname,paddress,pcno,pemail,ppulse,pec
prescription
g,pSymptoms,browse

8|Page
 4.2 Flow Chart : Wearable Device

Start

Device Login

Yes No
Login

Collect Patient data and Upload to

Username & Password
Cloudlet
Wrong

View all patient collecte data in enc

format with digital sign Logout

9|Page
 Flow Chart : Cloud Server

Start

Cloud Server Login

Yes No
Login

View all patients and authorize Username &

Password Wrong

View all doctors and

authorize

Vliew all patient Cloudlet data with Log Out

enc format

View Patient data access

request and authorize

View all Cloudlet Intruders details

View patient details recovered details

View No.Of same symptoms in Chart

View No.Of Patients refered same

doctor in Chart

10 | P a g e
 Flow Chart : Doctor

Start

Doctor Login

Yes No
Login

View patient details and give Username &

solution Password Wrong

View all patient Medical prescription Log Out

Details

11 | P a g e
 Flow Chart : Patient

Start

Patient Login

Yes No
Login

Request Data Access permission Username &

from cloudlet and view Response Password Wrong

Access Your data and select

doctor

Log Out
View doctor response with Medical
prescription

Verify your data and recover

View and delete your details

12 | P a g e
 4.3 Architecture Diagram

CLOUD SERVER

Patient

Doctor

Wearable Device
Attacker

13 | P a g e
 4.4 SEQUENCE DIAGRAM

Server
Device Patient Cloud
Doctor
Attacker Provider
Add Login
details View all
patients,docto
Collect Patient data r and
and Upload to Cloudlet authorize

View patient
Vliew all
details and
give solution patient
Cloudlet data
View all patient collecte
data in enc format Request Data View
View all Enter
Access Patient
patient patient
permission from data
Medical name and
cloudlet and access
prescription inject some
view Response request
Details false data.
and
authorize

View doctor
response with
Medical View No.Of
prescription same
symptoms,
Verify your data
Patients
and recover
refered same
doctor in
Chart

View and View patient

delete your details
details recovered
detailsdetail
s
View all
Cloudlet
Intruders
details

14 | P a g e
4.5 Use case :Cloud Server

View all patients,

doctors and authorize,

Vliew all patient Cloudlet

data

View Patient data access

request and authorize

Cloud Server

View all Cloudlet Intruders

, patient details recovered
details

View No.Of same

symptoms, Patients
refered same doctor in
Chart

15 | P a g e
➢ Use case : Patient

Request Data Access

permission from cloudlet

Patient
Access Your data and select
doctor

View doctor response with

Medical prescription

Verify your data and recover

and delete your details

Doctor

View patient details and

give solution

View patient details and give

solution

View all patient Medical

prescription Details

16 | P a g e
Wearable Device Collect Patient data and
Upload to Cloudlet

View all patient collecte

data in enc format

Intruder

Enter patient name and

inject some false data.

17 | P a g e
 5. IMPLEMENTATION
Modules

• Wearable Device
In this module, the wearable device Collect Patient data and Upload to Cloudlet like
pid,pname,paddress,pcno,pemail,ppulse,pecg,pSymptoms,brwose and attach about
symptoms with Digital sign,add pimage(Encrypt all parametes except pname) and View
all patient collecte data in enc format with digital sign.

• Cloud Server
The Cloud server manages which is to provide data storage service for the wearable
devices and also View all patients and authorize and View all doctors and authorize
,Vliew all patient Cloudlet data with enc format ,View Patient data access request and
authorize ,View all Cloudlet Intruders details and View patient details recovered details
,View No.Of same symptoms in Chart(Symptom name vs No. Of Patients),View No.Of
Patients refered same doctor in Chart(Doctor name vs No.Of Patients).
• Patient
In this module, the patient Register and Login, View profile ,Request Data Access
permission from cloudlet and view Response, Access Your data and select doctor from
combo box and send to corresponding doctor and View doctor response with Medical
prescription, Verify your data and recover and View and delete your details.
• Doctor
The doctor is the one who will perform the following operations such as Register and
Login,View Profile, View patient details and give solution like Medicine details,Medical
prescription details View all patient Medical prescription Details.
• AES Algorithm

Advanced Encryption Standard (AES) algorithm is the most common and widely
symmetric block cipher algorithm used in worldwide. This algorithm has an own
particular structure to encrypt and decrypt sensitive data and is applied in hardware and
software .

18 | P a g e
6.SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific testing
requirement.

TYPES OF TESTS

Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of components is
correct and consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

19 | P a g e
Functional test

Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or

special test cases. In addition, systematic coverage pertaining to identify Business process flows;
data fields, predefined processes, and successive processes must be considered for testing.
Before functional testing is complete, additional tests are identified and the effective value of
current tests is determined.

System Test
System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.

White Box Testing

White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose. It is
used to test areas that cannot be reached from a black box level.

20 | P a g e
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot “see” into it. The test provides inputs and
responds to outputs without considering how the software works.

6.1 Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.

Features to be tested
• Verify that the entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page.

6.2 Integration Testing

Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects.

21 | P a g e
 The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

6.3 Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant participation
by the end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

SYSTEM TESTING

TESTING METHODOLOGIES
The following are the Testing Methodologies:

o Unit Testing.
o Integration Testing.
o User Acceptance Testing.
o Output Testing.
o Validation Testing.

Unit Testing

Unit testing focuses verification effort on the smallest unit of Software design that
is the module. Unit testing exercises specific paths in a module’s control structure to ensure
complete coverage and maximum error detection. This test focuses on each module individually,
ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.
During this testing, each module is tested individually and the module interfaces
are verified for the consistency with design specification. All important processing path are
tested for the expected results. All error handling paths are also tested.

22 | P a g e
Integration Testing

Integration testing addresses the issues associated with the dual problems of
verification and program construction. After the software has been integrated a set of high order
tests are conducted. The main objective in this testing process is to take unit tested modules and
builds a program structure that has been dictated by design.
The following are the types of Integration Testing:
1)Top Down Integration

This method is an incremental approach to the construction of program structure.

Modules are integrated by moving downward through the control hierarchy, beginning with the
main program module. The module subordinates to the main program module are incorporated
into the structure in either a depth first or breadth first manner.
In this method, the software is tested from main module and individual stubs are
replaced when the test proceeds downwards.

2. Bottom-up Integration

This method begins the construction and testing with the modules at the lowest level in
the program structure. Since the modules are integrated from the bottom up, processing required
for modules subordinate to a given level is always available and the need for stubs is eliminated.
The bottom up integration strategy may be implemented with the following steps:

▪ The low-level modules are combined into clusters into clusters that
perform a specific Software sub-function.
▪ A driver (i.e.) the control program for testing is written to coordinate test case
input and output.
▪ The cluster is tested.
▪ Drivers are removed and clusters are combined moving upward in the
program structure
The bottom up approaches tests each module individually and then each module is module is
integrated with a main module and tested for functionality.

23 | P a g e
 OTHER TESTING METHODOLOGIES

User Acceptance Testing

User Acceptance of a system is the key factor for the success of any system. The system
under consideration is tested for user acceptance by constantly keeping in touch with the
prospective system users at the time of developing and making changes wherever required. The
system developed provides a friendly user interface that can easily be understood even by a
person who is new to the system.

Output Testing

After performing the validation testing, the next step is output testing of the proposed

system, since no system could be useful if it does not produce the required output in the specified

format. Asking the users about the format required by them tests the outputs generated or

displayed by the system under consideration. Hence the output format is considered in 2 ways –

one is on screen and another in printed format.

Validation Checking

Validation checks are performed on the following fields.

Text Field:

The text field can contain only the number of characters lesser than or equal to its size.
The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect entry
always flashes and error message.
Numeric Field:

The numeric field can contain only numbers from 0 to 9. An entry of any character
flashes an error messages. The individual modules are checked for accuracy and what it has to
perform. Each module is subjected to test run along with sample data. The individually tested
modules are integrated into a single system. Testing involves executing the real data

24 | P a g e
information is used in the program the existence of any program defect is inferred from the
output. The testing should be planned so that all the requirements are individually tested.
A successful test is one that gives out the defects for the inappropriate data and produces
and output revealing the errors in the system.

Preparation of Test Data

Taking various kinds of test data does the above testing. Preparation of test data
plays a vital role in the system testing. After preparing the test data the system under study is
tested using that test data. While testing the system by using test data errors are again uncovered
and corrected by using above testing steps and corrections are also noted for future use.
Using Live Test Data:

Live test data are those that are actually extracted from organization files. After a system

is partially constructed, programmers or analysts often ask users to key in a set of data from their

normal activities. Then, the systems person uses this data as a way to partially test the system. In

other instances, programmers or analysts extract a set of live data from the files and have them

entered themselves.

It is difficult to obtain live data in sufficient amounts to conduct extensive testing. And,
although it is realistic data that will show how the system will perform for the typical processing
requirement, assuming that the live data entered are in fact typical, such data generally will not
test all combinations or formats that can enter the system. This bias toward typical values then
does not provide a true systems test and in fact ignores the cases most likely to cause system
failure.
Using Artificial Test Data:

Artificial test data are created solely for test purposes, since they can be generated to test all
combinations of formats and values. In other words, the artificial data, which can quickly be
prepared by a data generating utility program in the information systems department, make
possible the testing of all login and control paths through the program.

25 | P a g e
The most effective test programs use artificial test data generated by persons other than those
who wrote the programs. Often, an independent team of testers formulates a testing plan, using
the systems specifications.

The package “Virtual Private Network” has satisfied all the requirements specified as per
software requirement specification and was accepted.

USER TRAINING

Whenever a new system is developed, user training is required to educate them about the
working of the system so that it can be put to efficient use by those for whom the system has
been primarily designed. For this purpose the normal working of the project was demonstrated to
the prospective users. Its working is easily understandable and since the expected users are
people who have good knowledge of computers, the use of this system is very easy.

MAINTAINENCE

This covers a wide range of activities including correcting code and design errors. To reduce the
need for maintenance in the long run, we have more accurately defined the user’s requirements
during the process of system development. Depending on the requirements, this system has been
developed to satisfy the needs to the largest possible extent. With development in technology, it
may be possible to add many more features based on the requirements in future. The coding and
designing is simple and easy to understand which will make maintenance easier.

TESTING STRATEGY :

A strategy for system testing integrates system test cases and design techniques into a well
planned series of steps that results in the successful construction of software. The testing
strategy must co-operate test planning, test case design, test execution, and the resultant data
collection and evaluation .A strategy for software testing must accommodate low-level tests
that are necessary to verify that a small source code segment has been correctly implemented
as well as high level tests that validate major system functions against user requirements.

Software testing is a critical element of software quality assurance and represents the ultimate
review of specification design and coding. Testing represents an interesting anomaly for the

26 | P a g e
software. Thus, a series of testing are performed for the proposed system before the system is
ready for user acceptance testing.

SYSTEM TESTING:

Software once validated must be combined with other system elements (e.g. Hardware, people,
database). System testing verifies that all the elements are proper and that overall system
function performance is achieved. It also tests to find discrepancies between the system and its
original objective, current specifications and system documentation.

UNIT TESTING:

In unit testing different are modules are tested against the specifications produced during the
design for the modules. Unit testing is essential for verification of the code produced during the
coding phase, and hence the goals to test the internal logic of the modules. Using the detailed
design description as a guide, important Conrail paths are tested to uncover errors within the
boundary of the modules. This testing is carried out during the programming stage itself. In this
type of testing step, each module was found to be working satisfactorily as regards to the
expected output from the module.

In Due Course, latest technology advancements will be taken into consideration. As part
of technical build-up many components of the networking system will be generic in nature so
that future projects can either use or interact with this. The future holds a lot to offer to the
development and refinement of this project.

27 | P a g e
7.OUTPUT SCREEN

28 | P a g e
29 | P a g e
30 | P a g e
31 | P a g e
32 | P a g e
 8.CONCLUSION
The System Analyse the pulse rate and Predicts the Heart Diseases. The data in the system is
secured by using AES algorithm which is mostly used to encrypt the data. Stored data predict the
patients health report by using random forest algorithm. System enhances data security, accuracy
consistency, reduces the latency rate and enhances the overall quality of service. The data stored
on the Fog can be stored in a secure way. The system maintains data integrity. System protects
against misuse of real user data. Fog computing architecture is able to overcome the security
challenges of the traditional IoT cloud architecture to some extent. By introducing fog as a
middle layer and performing at the edge side it enhances data security, accuracy, consistency,
reduces the latency rate and enhances the overall quality of service. In the near future IoT-Fog-
cloud architecture will be widely used as more and more IoT devices are developed and the
increasing demand for fast computation. The implementation can be enhanced in future by
developing a reliable real time data monitoring system application with the mentioned
architecture as a core. And to give a computational prove of how much fog can enhance the
traditional IoTCloud architecture.

33 | P a g e
 9.BIBILOGRAPHY
[1]Kraemer, Frank Alexander, Anders Eivind Braten, Nattachart Tamkittikhun, and David
Palma. "Fog Computing in Healthcare–A Review and Discussion." IEEE Access 5 (2017): 9206-
922

[2] Khan, Saad, Simon Parkinson, and Yongrui Qin. "Fog computing security: a review of
current applications and security solutions." Journal of Cloud Computing 6, no. 1 (2017): 19.

[3] Fog Computing Architecture, https://www.slideshare.net/saisharansai/fogcomputing-

46604121, July 2018.

4. Al Hamid, Hadeal Abdulaziz, Sk Md Mizanur Rahman, M. Shamim Hossain, Ahmad

Almogren, and Atif Alamri. "A Security Model for Preserving the Privacy of Medical Big Data
in a Healthcare Cloud Using a Fog Computing Facility With Pairing-Based Cryptography." IEEE
Access 5 (2017): 22313-22328.

5. Alrawais, Arwa, Abdulrahman Alhothaily, Chunqiang Hu, and Xiuzhen Cheng. "Fog
computing for the internet of things: Security and privacy issues." IEEE Internet Computing 21,
no. 2 (2017): 34-42.

6. Elminaam, Diaa Salama Abdul, Hatem Mohamed Abdul Kader, and Mohie Mohamed
Hadhoud. "Performance evaluation of symmetric encryption algorithms." IJCSNS International
Journal of Computer Science and Network Security 8, no. 12 (2008): 280-286.

7. Coppersmith, Don, Donald Byron Johnson, and Stephen M. Matyas. "A proposed mode for
triple-DES encryption." IBM Journal of Research and Development 40, no. 2 (1996): 253-262.

8. Gia, Tuan Nguyen, Mingzhe Jiang, AmirMohammad Rahmani, Tomi Westerlund, Pasi
Liljeberg, and Hannu Tenhunen. "Fog computing in healthcare internet of things: A case study
on ecg feature extraction." In Computer and Information Technology; Ubiquitous Computing
and Communications; Dependable, Autonomic and Secure Computing; Pervasive Intelligence
and Computing (CIT/IUCC/DASC/PICOM), 2015 IEEE International Conference on, pp. 356-
363. IEEE, 2015.

34 | P a g e
9. Mukherjee, Mithun, Rakesh Matam, Lei Shu, Leandros Maglaras, Mohamed Amine Ferrag,
Nikumani Choudhury, and Vikas Kumar. "Security and privacy in fog computing: Challenges."
IEEE Access 5 (2017): 19293- 19304.

10. Shrestha, N. M., Abeer Alsadoon, P. W. C. Prasad, L. Hourany, and A. Elchouemi.

"Enhanced e-health framework for security and privacy in healthcare system." In Digital
Information Processing and Communications (ICDIPC), 2016 Sixth International Conference on,
pp. 75-79. IEEE, 2016.

11. Wang, Qixu, Dajiang Chen, Ning Zhang, Zhe Ding, and Zhiguang Qin. "PCP: A
PrivacyPreserving Content-Based Publish–Subscribe Scheme With Differential Privacy in Fog
Computing." IEEE Access 5 (2017): 17962- 17974.

12. Wanve, Balu, Rahul Kamble, Sachin Patil, and Jayshree Katti. "Framework for client side
AES encryption technique in cloud computing." In Advance Computing Conference (IACC),
2015 IEEE International, pp. 525-528. IEEE, 2015.

13. Vishwanath, Akhilesh, Ramya Peruri, and Jing (Selena) He. Security in fog computing
through encryption. DigitalCommons@ Kennesaw State University, 2016.

14. Sadikin, Mohamad Ali, and Rini Wisnu Wardhani. "Implementation of RSA 2048-bit and
AES 256-bit with digital signature for secure electronic health record application." In Intelligent
Technology and Its Applications (ISITIA), 2016 International Seminar on, pp. 387-392. IEEE,
2016.

15. Shao, Fei, Zinan Chang, and Yi Zhang. "AES encryption algorithm based on the high
performance computing of GPU." In Communication Software and Networks, 2010. ICCSN'10.
Second International Conference on, pp. 588-590. IEEE, 2010.

16. Shao, Fei, Zinan Chang, and Yi Zhang. "AES encryption algorithm based on the high
performance computing of GPU." In Communication Software and Networks, 2010. ICCSN'10.
Second International Conference on, pp. 588-590. IEEE, 2010.

17. Umamaheswari E, Ajay DM, Umang Sindal, Scope of Internet of Things: A Survey, Asian
Journal of Pharmaceutical and Clinical Research, April 2017

35 | P a g e
18. D M Ajay, Umamaheswari.E, an initiation for testing the security of a cloud service provider.
Smart Innovation, Systems, Technologies. Switzerland: Springer Publications; 2016. p. 35- 41.

19. D M Ajay, Umamaheswari.E, Why, how cloud computing- How not and cloud security
issues. Global Journal of Pure and Applied Mathematics (GJPAM) 2016;12(1):1-8

20. D M Ajay, Umamaheswari E, Evaluating the Efficiency of Security Mechanisms in Cloud

Environments, International Journal of Control Theory and Applications, Vol. 9, No.51, 2016

36 | P a g e