JSS Mahavidhyapeetha

JSS Academy of Technical Education

Kengeri – Uttarhalli Main Road, Bengaluru – 560060

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING

COURSE NAME: Cloud Computing and Its Applications

COURSE CODE: 17CS742

TOPIC:
SECURE INTEGRATION OF IoT AND CLOUD
COMPUTING

Done By:
Pujit Y G [1JS17CS073]
Semester/Branch: 7th SEM, ‘B’ SEC
INTRODUCTION

CLOUD COMPUTING
Cloud computing is on demand availability of computing resources, maybe in
the form of platform, Infrastructures or software. Cloud Computing is usually
used to describe data centres available to many people over the network. The
clouds, often have methods distributed over multiple points from main servers.
If the distance to the customer is relatively close, it may be designated an edge
server.
Cloud computing model is generally pay per use, which makes the system even
more complex if the vendor doesn’t go by the service level agreement.

INTERNET OF THINGS

It describes the network of physical objects, which are embedded with sensors,
data storage, and other technologies which are connected with each other and
communicates information.
The term is evolved due to convergences of many technologies and concept like
machine learning, Real time data mining and analytics etc. There are several
concerns in the field of IOT such as data privacy and security.

NOW HOW ABOUT COMBINING IOT WITH CLOUD COMPUTING AND

REDEFINING THE FUTURE?
PROBLEM STATEMENT

In the real time processing, a replacement emerging technology where the

need of connecting smart devices with cloud through Internet has raised. IoT
devices processed information is to be stored and accessed with a help of
powerful computing infrastructure, an efficient storage infrastructure for
heterogeneous systems and software which configures and controls these
differentdevice.
A lot of challenges to be addressed are listed with this new emerging
technology because it needs to be compatible with the latest 5G mobile
devices too.

WHY IS IT IMORTANT TO ADDRESS THE PROBLEM?

In case cloud is merged with IOT with full success rate then, it would be
every economical for the customers in the long run. Since the policy of the
cloud is pay-as-you-go, customers would pay only for the necessary
resources, and redirect the rest of the fund to other places.
The most important is with respect to security of the data, in case we lose
our mobile or laptop, we will be losing the precious data along with the
device. In case the data is stored in cloud, customers need not fear about data
theft or leakage. The optimum capacity of the infrastructure is used, so the
solution provided increases the overall efficiency.
Merging IOT to Cloud results in more elastic and scalable, whether in
bandwidth, storage or any other resource.
DISCUSSION
The combination of Internet of things and other concepts such as Internet,
Big Data is still in developing stage.
Quality of service may be a vital factor which is measured supported the
bandwidth, the processing speed and therefore the service itself which it
provides. There is no clear global scale strategy is lasting or permanent for
the utilization of unique ID or indexed spaces of various object’s types.
There is no acceleration, momentum and further development of the IoT
reference architecture like Architecture Reference Model (ARM) for Internet
of Things projects. There has been limited progress in semantic
interoperability for the sensor data exchange in heterogeneous environments.
There are some problems in developing a transparent innovation approach,
information trust and ownership on Internet of Things, as simultaneously
maintaining the safety and privacy in an environment may be a complex
task. There are some problems in business development that embraces the
complete potential of the web of Things. Large-scale testing and learning
environments, which facilitate testing with complex sensor networks and
thru feedback and knowledge cause innovation, are achieved within the
lower levels.
Only alittle amount of rich user interfaces has been developed and wish
attention within the integration areas because the new generation devices are
emerging belonging to 5G.
A Protocol for IoT Connectivity

No matter how sophisticated edge-to-cloud IoT communications get, it all

comes right right down to two-way data communications over the online
between a tool and a far off service.
Starting at the transport layer, device-to-cloud communications generally
happen over TCP (Transmission Control Protocol) or UDP (User Datagram
Protocol) channels. TCP is connection-oriented and reliable, meaning that
each data packet sent requires acknowledgement that it had been received.
But with great reliability comes great overhead, and sometimes for an IoT
application, the TCP header are often larger than the payload itself. UDP on
the opposite hand, is connectionless and unreliable, meaning that it allows
for the loss of knowledge packets within the interest of speed. TCP is used
where data must get through whereas UDP is employed where some data
loss is suitable (e.g., when streaming videos).
At the appliance layer, HTTP (HyperText Transfer Protocol) has become
one among the foremost standardized protocols for web-based
communications. it had been developed as a request-response model from
the client-server era where clients (e.g., browsers), open a TCP connection to
send requests to servers (e.g., web servers) that return responses. TLS is
usually employed to secure HTTP communication over TCP, while DTLS
performs similar functionality over UDP. This setup are often employed by
IoT devices to speak with the online servers employing a RESTful/SOAP
web service.
For example, devices can ask the server over a TCP/IP connection using
HTTP GET/POST methods, and deliver the payloads formatted in XML,
JSON, or another format. Each step (TCP/IP, HTTP, XML/JSON) keeps
adding overhead to the payload, which is that the only relevant information
that the top application is trying to find.
Hence, another application-layer protocol, MQTT (Message Queuing
Telemetry Transport), has become popular for IoT. It’s a light-weight
protocol with a little code footprint suitable for constrained environments
like embedded IoT devices. Most notably, it works on a publish-subscribe
model that facilitates one-to-many communications between devices through
a central MQTT “broker”–just the type of communications you'd typically
need for IoT!

HOW IS IT DIFFERENT?

Device-to-cloud communication working over standard OSI-model protocols

provides the backbone for cloud services. IoT-device-to-cloud
connectivity are often achieved on both specialized hardware like the
MDM9206 LTE Modem and more general-purpose devices like the
Snapdragon mobile platforms.

More generally, this device-to-cloud architecture provides a rich set of options for
processing on IoT devices and/or the cloud. However, at the top of the day, it’s
all about how well you'll implement two-way data communications over the
web between a tool and a foreign service.

LIMITATIONS OF INTEGRATING IOT AND CLOUD

Server costs will increase.

For areas with strict capitalization, the situation of the info must be
discussed with the cloud service provider.
If the setup is originally designed with traditional specification , drastic
changes could also be needed.
For areas with strict capitalization, the situation of the info must be
discussed with the cloud service provider.

PLAGARISM REPORT