A Seminar Report On

ABSTRACT
Cloud computing is clearly one of today‟s most enticing technology areas due, at least in part,
to its cost-efficiency and flexibility. However, despite the surge in activity and interest there
are significant, persistent concerns about cloud computing that are impeding momentum and
will eventually compromise the vision of cloud computing as a new IT procurement model.
 LIST OF FIGURES
SNO. FIGURE NAME PAGE NO.
1 SERVICES OF CLOUD 01
2 VALUE VISIBILITY TO 02
END USER
3 CLOUD COMPUTING 03
4 DIFFERENT LAYERS OF 04
5 CLOUD COMPUTING 07
TYPES
6 MOBILE CONNECTIVITY 23
 CONTENTS

S.NO. DESCRIPTION PAGE NO.

1. INTRODUCTION 01

1.1 LIFE BEFORE CLOUD COMPUTING 01-02

1.2 CLOUD COMPUTING :A BETTER WAY 03

1.3 CLOUD STORAGE 03

1.4 DATA CLOUD 04

2. CLOUD COMPUTING ARCHITECTURE 04-05

3. CHARACTERESTICS OF CLOUD COMPUTING 05-06

3.1 COMPARISION WITH RELATED TECHNOLOGES 06

4. TYPES OF CLOUD COMPUTING 07

4.1 PUBLIC CLOUD 07

4.2 PRIVATE CLOUD 08

4.3 EXTERNAL CLOUD 08

4.4 COMMUNITY CLOUD 08

4.5 HYBRID CLOUD

5. VARIATIONS OF CLOUDS 09

5.1 INFRASTRUCTURES 10

5.2 PLATFORMS 10

S.NO. DESCRIPTION PAGE NO.

 5.3 APPLICATIONS 10

6. CLOUD COMPUTING ADVANTAGES 11

6.1 COST EFFECIENCY 11

6.2 SPEED AND SCALES 11

6.3 INNOVATION 11

6.4 CONVENIENT 12

6.5 LOCATION 12

6.6 MULTIPLE ISSUES AT ONE TIME 12

6.7 FLEXIBLE 12

6.8 DEVICE DIVERSITY 12

6.9 LOTS O STORAGE SPACE 12

6.10 CUSTOMIZE SETTING 12

7. CLOUD COMPUTING DISADVANTAGES 13

7.1 SECURITY AND PRIVACY 13

7.2 DEPENDENCY 13

7.3 HIGHER COSTS 14

7.4 DECREASED FLEXIBLE 14

7.5 KNOWLEDGE AND INTEGRATION 14

8. WHAT IS EDGE COMPUTING 14-15

S.NO. DESCRIPTION PAGE NO.

 8.1 A DEEPER EXPLORATION OF EDGE COMPUTING 16-18

9. CHARACTERSTICS OF EDGE COMPUTING 18

9.1 REDUCING LATENCY 18

9.2 MITIGATING BANDWIDTH LIMITS 18-19

9.3 USE CASES 19

10. DATA COLLECTION AND ANALYTICS 19

10.1 SECURITY 20

10.2 COMPLIANCE REQUIREMENTS 20

10.3 NETWORK FUNCTIONAL VIRTUALIZATION 20

10.4 REAL TIME 20-21

10.5 IMMERSIVE NETWORK 21

10.6 EFFECIENCY 21

10.7 SELF CONTAINED AND AUTONOMOUS SITE OPERATIONS 21

10.8 PRIVACY 22

11. SCENARIOS 22-24

12. CONCLUSION 25

13. REFERENCES 26
 1. INTRODUCTION

It can be the ability to rent a server or a thousand servers and run a geophysical
modeling application on the most powerful systems available anywhere. It can be the ability to
rent a virtual server, load software on it, turn it on and off at will, or clone it ten times to meet a
sudden workload demand. “cloud computing is a general term for anything that involves
delivering hosted services over the Internet. These services are broadly divided into three
categories:

Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) and Software-as-a-Service

(SaaS)." The name cloud computing was inspired by the cloud symbol that's often used to
represent the Internet in flowcharts and diagrams.

FIG 1.1: SERVICES OF CLOUD

Infrastructure-as-a-Service, like Amazon Web Services, provides virtual server

instances with unique IP addresses and blocks of storage on demand. Customers use the
provider's application program interface to start, stop, access and configure their virtual
servers and storage.

Platform-as-a-Service, in the cloud is defined as a set of software and product

development tools hosted on the provider's infrastructure. Developers create
applications on the provider's platform over the Internet. PaaS providers may use APIs,
website portals or gateway software installed on the customer's computer. Force.com, (an
outgrowth of Salesforce.com) and Google Applications are examples of PaaS. Developers
need to know that currently, there are not standards for interoperability or data portability

1
 in the cloud.

Software-as-a-Service cloud model, the vendor supplies the hardware infrastructure, the
software product and interacts with the user through a front-end portal. SaaS is a very broad
market. Services can be anything from Web-based email to inventory control and database
processing. Because the service provider hosts both the application and the data, the end user
is free to use the service from anywhere.

FIG 1.2: VALUE VISIBILITY TO END USER

A cloud service has three distinct characteristics that differentiate it from traditional hosting.

1.It is sold on demand, typically by the minute or the hour

2. A user can have as much or as little of a service as they want at any given time.

3. The service is fully managed by the provider. Significant innovations in virtualization and
distributed computing, as well as improved access to high-speed Internet and a weak
economy, have accelerated interest in cloud computing.
A cloud can be private or public. A public cloud sells services to anyone on the Internet.
(Currently, Amazon Web Services is the largest public cloud provider.) A private
cloud is a proprietary network or a data center that supplies hosted services to a limited
number of people. When a service provider uses public cloud resources to create their
private cloud, the result is called a virtual private cloud. Private or public, the goal of cloud
computing is to provide easy, scalable access to computing resources and IT services.

1.1 LIFE BEFORE CLOUD COMPUTING

Traditional business applications have always been very complicated and expensive. The

2
amount and variety of hardware and software required to run them are daunting. You need a
whole team of experts to install, configure, test, run, secure, and update them. When you
multiply this effort across dozens or hundreds of applications, it‟s easy to see why the
biggest companies with the best IT departments aren‟t getting the applications they need.
Small and mid-sized businesses don‟t stand a chance.

1.2 CLOUD COMPUTING: A BETTER WAY

With cloud computing, you eliminate those headaches because you‟re not managing
hardware and software-that‟s the responsibility of an experienced vendor like
salesforce.com. The shared infrastructure means it works like a utility: You only pay for
what you need, upgrades are automatic, and scaling up or down is easy.

Cloud-based apps can be up and running in days or weeks, and they cost less. With a cloud
application, you just open a browser, log in, customize the application, and start using it.
Businesses are running all kinds of apps in the cloud, like customer relationship
management (CRM), HR, accounting, and much more. Some of the world‟s largest
companies moved their applications to the cloud with salesforce.com after rigorously testing
the security and reliability of our infrastructure.

As cloud computing grows in popularity, thousands of companies are simply rebranding their
non-cloud products and services as “cloud computing.” Always dig deeper when evaluating
cloud offerings and keep in mind that if you have to buy and manage hardware and software,
what you‟re looking at isn‟t really cloud computing but a false cloud.

FIG 3:CLOUD COMPUTING

3
 1.3 CLOUD STORAGE

Over time many big Internet based companies (Amazon, Google…) have come to realize
that only a small amount of their data storage capacity is being used. This has led to the
renting out of space and the storage of information on remote servers or "clouds".
Information is then temporarily cached on desktop computers, mobile phones or other
internet-linked devices. Amazon‟s Amazon Elastic Compute Cloud(EC2) and Simple Storage
Solution (S3) are the current best known facilities

1.4 DATA CLOUD

Along with services the cloud will host data. There has been some discussion of this being
a potentially useful notion possibly aligned with the Semantic Web, though it could result
in data becoming undifferentiated.

2.CLOUD COMPUTING ARCHITECTURE

Cloud computing architecture, just like any other system, is categorized into two main
sections: Front End and Back End. Front End can be end user or client or any application
(i.e. web browser etc.) which is using cloud services. Back End is the network of servers
with any computer program and data storage system. It is usually assumed that cloud
contains infinite storage capacity for any software available in market. Cloud has different
applications that are hosted on their own dedicated server farms.

Cloud has centralized server administration system. Centralized server administers the
system, balances client supply, adjusts demands, monitors traffic and avoids congestion.
This server follows protocols, commonly known as middleware. Middleware controls the
communication of cloud network among them

4
 FIG 2.1: CLOUD COMPUTING ARCHITECTURE

Cloud Architecture runs on a very important assumption, which is mostly true. The
assumption is that the demand for resources is not always consistent from client to cloud.
Because of this reason the servers of cloud are unable to run at their full capacity. To avoid
this scenario, server virtualization technique is applied. In sever virtualization, all physical
servers are virtualized and they run multiple servers with either same or different
application. As one physical server acts as multiple physical servers, it curtails the need for
more physical machines.

As a matter of fact, data is the most important part of cloud computing; thus, data security
is the top most priority in all the data operations of cloud. Here, all the data are backed up
at multiple locations. This astoundingly increases the data storage to multiple times in
cloud compared with a regular system. Redundancy of data is crucial, which is a must-have
attribute of cloud computing.

3. CHARACTERSTICS OF CLOUD COMPUTING

1. HIGH SCALABILITY
Cloud environments enable servicing of business requirements for larger audiences,
through high scalability.
2. AGILITY
The cloud works in the „distributed mode‟ environment. It shares resources among users and
tasks, while improving efficiency and agility (responsiveness).
3. HIGH AVAILABILITY AND RELIABILITY

Availability of servers is high and more reliable as the chances of infrastructure failure are

5
 minimal.
4. MULTI-SHARING
With the cloud working in a distributed and shared mode, multiple users and applications
can work more efficiently with cost reductions by sharing common
infrastructure.
5. SERVICES IN PAY-PER-USE MODE
SLA’s between the provider and the user must be defined when offering services in pay
per use mode. This may be based on the complexity of services offered.
Application Programming Interfaces (APIs) may be offered to the users so they can access
services on the cloud by using these APIs.
6. SUPPORT FOR ALL SERVICE ORIENTED APPLICATIONS
Cloud computing has the potential to help agencies leverage modern technologies such
as computer virtualization and worldwide Internet connectivity. Some of the key business
drivers are:
a. pursuing new business opportunities, such as trialing new ideas to reach and interact
with customers over the Internet;
b. Reducing upfront costs of capital expenditure of computer equipment and related
expenses such as a physical data centre and support staff, while reducing the associated
financial risk to the agency by replacing upfront costs with reasonably predictable
operational expenditure, and only paying for the amount of computing processing and data
storage that is actually used;
c. Potentially reducing ongoing costs due to the use of infrastructure and technical
specialists that are typically shared among many customers to achieve economies of scale,
however the cost of applying controls to help address security risks especially associated
with shared infrastructure may reduce the potential cost savings of some types of cloud
computing.

d. Potentially improving business continuity and the availability of computing

Infrastructure if users have guaranteed available network connectivity, where the
infrastructure can rapidly and flexibly scale to meet peaks and troughs in usage demand,
and with the computing infrastructure
e. Potentially reducing carbon footprint due to the more efficient use of computer
hardware requiring less electricity and less air conditioning

6
3.1 COMPARISON WITH RELATED TECHNOLOGIES

Several technologies are related to cloud computing, and the cloud has emerged as a
convergence of several computing trends. It seeks to address certain key aspects that may
have been lacking in each of these trends, individually. The features of each of these
related technologies and how they compare with cloud computing has been outlined in the
table.

4. TYPES OF CLOUD COMPUTING

The cloud computing environment can consist of multiple types of clouds based on their
deployment and usage.

FIG 4.1: CLOUD COMPUTING TYPES

4.1 PUBLIC CLOUDS

This environment can be used by the general public. This includes individuals,
corporations and other types of organizations. Typically, public clouds are administrated
by third parties or vendors over the Internet, and services are offered on pay-per-use basis.
These are also called provider clouds. Business models like SaaS (Software-as-a-Service)
and public clouds complement each other and enable companies to leverage shared IT
resources and services.
Example
New York Times archive project which used 100 Amazon EC2 instances and 5.5TB of S3
storage to generate PDFs of 11 million articles for the paper‟s archives, at a small fraction
of traditional costs.
Advantages

7
 1. Public clouds are widely used in the development, deployment and management of
enterprise applications, at affordable costs.
2. Allows organizations to deliver highly scalable and reliable applications rapidly and at
more affordable costs.

Limitations
Security is a significant concern in public clouds.

4.2 PRIVATE CLOUDS

This cloud computing environment resides within the boundaries of an organization and is
used exclusively for the organization‟s benefits.These are also called “internal clouds”. They
are built primarily by IT departments within enterprises who seek to optimize utilization of
infrastructure resources within the enterprise by provisioning the infrastructure with
applications using the concepts of grid and virtualization
Advantages
1. They improve average server utilization, allow usage of low-cost servers and hardware
while providing higher efficiencies; thus reducing the costs that a greater number of servers
would otherwise entail.
2. High levels of automation, reducing operations costs and administrative overheads.

Limitations
IT teams in the organization may have to invest in buying, building and managing the clouds
independently

4.3 EXTERNAL CLOUDS

This cloud computing environment is outside of the boundaries of the organization, though it
is not necessarily a public cloud. Some external clouds make their cloud infrastructure
available to specific other organizations, but not to the general public

4.4 COMMUNITY CLOUD

This cloud involves a private cloud that is shared by several organisations with similar

8
security requirements and a need to store or process data of similar sensitivity. This model
attempts to obtain most of the security benefits of a private cloud, and most of the economic
benefits of a public cloud. An example community cloud is the sharing of a private cloud by
several agencies of the same government

4.5 HYBRID CLOUDS

This is a combination of both private (internal) and public (external) cloud computing
environments.

5. VARIATIONS OF CLOUDS
Clouds can be classified as:
1.Infrastructures
2.Platforms
3.Applications

5.1 INFRASTRUCTURES
Salient features:
1. Known also as IaaS (Infrastructure-asa- Service), acknowledged as the most potent
cloud.
2. Provides access to shared resources on need basis, without revealing details like location
and hardware to clients.
3. Provides details like server images on demand, storage, queuing, and information about
other resources, among others.
4. Vendors who provide this type of service enable cloud platforms and cloud applications.
Some may even leverage others within the space to provide competitive viability as well.
5. Offers full control of server infrastructure, not limited specifically to applications,
instances and containers

Example
Amazon’s EC2, through which users can request Linux Virtual Machine instances that are
created on the fly and billed based on actual usage.

Limitations

9
1. Service providers may demand higher prices for services offered.
2. Issues pertaining to resource and server down time.
3. Service providers may demand higher prices for services offered.

5.2 PLATFORMS
Salient features
1. Known also as PaaS (Platform-as-a- Service)
2. Empowers developers to deploy, deliver and manage their applications. They can build
applications, upload(deploy) the same into the cloud platform and simply run and test them.
3. Developers can also leverage additional benefits like authentication and data access
provided by the platform.
4. This cloud takes away the concept of servers, while providing an application centric
environment.
5. While creating this kind of cloud computing platform, a vendor “builds a cloud
platform first and then develops applications that run on it” (OR) “develops a hostable
application and then plugs it into the cloud”. But considering the advantages and
disadvantages, the latter would be the better approach.

Limitations:

Significant dependency on cloud infrastructure providers.

5.3 APPLICATIONS

Salient features
Companies host applications on the Internet and users sign up and use them, without
concerning themselves about its maintenance and where abouts. This is also called as

10
 SaaS (Software-as-a- Service).
Advantages
Mostly free, very easy to use, feature rich, easy to access and promises good consumer
adoption.
Limitations
User can only use the application and would not know the technology leveraged to develop
the application; thereby user has little control over application development

6.CLOUD COMPUTING ADVANTAGES

There are various tools and features that users will be able to track when using the cloud
computing resource. These features/tools would include:

1. Testing

2. Building applications

3. Developmental Stages

4. Network equipment

5. Hosting Maintenance

There are 10 basic cloud computing advantages that will better help you to understand the
reasons as to why people use this method for their hardware

6.1 COST EFFECTIVE

There is no need for users to invest their time and money into using stand alone servers
which would be a bit complicating to use compared to the cloud method. It is a cheaper
way to maintain the software and it will save time, as the developers keep track of updates
and maintain your programs while you use it. There is no need for replacing capital
expenditures on a regular basis. The cost of using cloud resources is very economical for
resources such as centralized, real estate, bandwidth, and power. Users will also save
money on software updates, management costs, and data storage costs

6.2 SPEED & SCALES

There is no need to purchase and setup hardware manually when using the cloud

11
computing method. Depending upon their needs the user can quickly scale up or scale
down.

6.3 INNOVATION
Users can now pay closer attention to the innovation process because they don‟t have to
manually manage other resources. Cloud computing produces a faster development pace
for prototype and testing phases. Projects at which users have to watch over for progress on
a regular basis will benefit the most because of this advantage.

6.4 CONVENIENT
Since overheads are low when sharing the same infrastructure the services are available to
use immediately. Payments are only billed for the times that the service is being utilized.
You can easily check the cost of the bill because the service provider will make them
available online for you to view.

6.5 LOCATION
Areas that have lower overheads are able to utilize this service and take advantage of the
benefits as well. Many different websites are able to be set up in the case of a disaster
recovery which helps the companies to cut costs in different ways.

6.6 MULTIPLE USERS AT ONE TIME

Cloud computing is not only cost effective, but utilizing it also helps to cut back on global
wastes. It is environmentally friendly since it is shared by multiple users. The down time
is cut in half and the resources are stretched.

6.7 FLEXIBLE
There is a high rate of flexibility when using cloud computing because people can opt out
of using it whenever they want too. This is also one of the main reasons people love to use
this method. Service level agreements are what cover the costs in this case. If the correct
quality is not provided then has to pay a penalty cost

6.8 DEVICE DIVERSITY

The cloud computing method can be accessed through various different electronic devices

12
 that are able to have access to the internet. These devices would include and iPod,
Smartphone, Laptop, or desktop computer.

6.9 LOTS OF STORAGE SPACE

When you use the internet with the cloud services then your company will have lots more
room to store the files and data that they need to store

6.10 CUSTOMIZE SETTINGS

Last but not least, you will enjoy the fact that cloud computing allows you to customize
your business applications. This is a great benefit because the world of online business is
very competitive.

7.CLOUD COMPUTING DISADVANTAGES:

The main disadvantages are S ecurity and Privacy, Dependency (loss of control),
Cost, Decreased flexibility, Knowledge And Integration.

7.1 SECURITY&PRIVACY:
The biggest concerns about cloud computing are security and privacy. Users
might not be comfortable handing over their data to a third party. This is an
even greater concern when it comes to companies that wish to keep their
sensitive information on cloud servers. While most service vendors would
ensure that their servers are kept free from viral infection and malware, it Is still a
concern considering the fact that a number of users from around the world are
accessing the server.
Privacy is another issue with cloud servers. Ensuring that a client‟s data is not
accessed by any unauthorized users is of great importance for any cloud service. To
make their servers more secure, cloud service vendors have developed password
protected accounts, security servers through which all data being transferred must
pass and data encryption techniques. After all, the success of a cloud service
depends on its reputation, and any sign of a security breach would result in a loss of
clients and business

7.2 DEPENDENCY

13
1. Quality problems with CSP (Cloud Service Providers).No influence on
maintenance levels and fix frequency when using cloud services from a CSP.
2. No or little insight in CSP contingency procedures especially backup, restore
and disaster recovery.
3. No easy migration to another CSP.
4. Measurement of resource usage and end user activities lies in the hands of the
CSP
5. Tied to the financial health of another Company.

7.3 HIGHER COSTS

While in the long run, cloud hosting is a lot cheaper than traditional technologies,
the fact that it‟s currently new and has to be researched and
improved actually makes it more expensive. Data centers have to buy or develop
the software that‟ll run the cloud, rewire the machines and fix
unforeseen problems. This makes their initial cloud offers more expensive.
Like in all other industries, the first customers pay a higher price and have to
deal with more issues than those who switch later.

7.4 DECREASED FLEXIBILITY

This is only a temporary problem, but current technologies are still in the testing stages, so
they don‟t reallyoffer the flexibility they promise. Of course, that‟ll change in the
future, but some of the current users might have to deal with the facts that their
cloud server is difficult or impossible to upgrade without losing some data, for
example

7.5 KNOWLEDGE AND INTEGRATION

More and deeper knowledge is required for implementing and managing
contracts with CSP‟s.Since all knowledge about the working of the cloud (e.g.
hardware, software, virtualization, deployment) is concentrated at the CSP, it is
hard to get grip on the CSP.

14
 Integration:
Integration with equipment hosted in other data centers is difficult to achieve.
Peripherals integration. (Bulk)Printers and local security IT equipment (e.g. access
systems) is difficult to integrate. But also (personal) USB devices or smart phones
or groupware and email systems are difficult to integrate

What whwat is Cloud Edge

Com
8 WHAT IS EDGE COMPUTING?
It is worth highlighting that many overlapping and sometimes conflicting definitions of edge
computing exist—edge computing means many things to many people. But for our purposes,
the most mature view of edge computing is that it is offering application developers and
service providers cloud computing capabilities, as well as an IT service environment at the
edge of a network.

The aim is to deliver compute, storage, and bandwidth much closer to data inputs and/or end
users. An edge computing environment is characterized by potentially high latency among all
the sites and low and unreliable bandwidth—alongside distinctive service delivery and
application functionality possibilities that cannot be met with a pool of centralized cloud
resources in distant data centers. By moving some or all of the processing functions closer to
the end user or data collection point, cloud edge computing can mitigate the effects of widely
distributed sites by minimizing the effect of latency on the applications.

Edge computing first emerged by virtualizing network services over WAN networks, taking a
step away from the data center. The initial use cases were driven by a desire to leverage a
platform that delivered the flexibility and simple tools that cloud computing users have
become accustomed to.

As new edge computing capabilities emerge, we see a changing paradigm for computing—
one that is no longer necessarily bound by the need to build centralized data centers. Instead,
for certain applications, cloud edge computing is taking the lessons of virtualization and
cloud computing and creating the capability to have potentially thousands of massively
distributed nodes that can be applied to diverse use cases, such as industrial IoT or even far-

15
flung monitoring networks for tracking real time water resource usage over thousands, or
millions, of locations.

Many proprietary and open source edge computing capabilities already exist without relying
on distributed cloud—some vendors refer to this as “device edge.” Components of this
approach include elements such as IoT gateways or NFV appliances. But increasingly,
applications need the versatility of cloud at the edge, although the tools and architectures
needed to build distributed edge infrastructures are still in their infancy. Our view is that the
market will continue to demand better capabilities for cloud edge computing

Edge computing capabilities include, but are not limited to:

1. A consistent operating paradigm across diverse infrastructures.

2. The ability to perform in a massively distributed (think thousands of global locations)
environment.
3. The need to deliver network services to customers located at globally distributed
remote locations.
4. Application integration, orchestration and service delivery requirements.
5. Hardware limitations and cost constraints.
6. Limited or intermittent network connections.
7. Methods to address applications with strict low latency requirements (AR/VR, voice,
and so forth).
8. Defencing and requirements for keeping sensitive private data local.

8.1 A DEEPER EXPLORATION OF EDGE COMPUTING


The “edge” in edge computing refers to the outskirts of an administrative domain, as close as
possible to discrete data sources or end users. This concept applies to telecom networks, to
large enterprises with distributed points of presence such as retail, or to other applications, in
particular in the context of IoT.

16
One of the characteristics of edge computing is that the application is strongly associated with
the edge location. For telecoms, “the edge” would refer to a point close to the end user but
controlled by the provider, potentially having some elements of workloads running on end
user devices. For large enterprises, “the edge” is the point where the application, service or
workload is used (e.g. a retail store or a factory). For the purposes of this definition, the edge
is not an end device with extremely limited capacity for supporting even a minimal cloud
architecture, such as an IoT or sensor device. This is an important consideration, because
many discussions of edge computing do not make that distinction.

Edge computing is similar to data center computing in that:

1. It includes compute, storage and networking resources.
2. Its resources may be shared by many users and many applications.
3. It benefits from virtualization and abstraction of the resource pool.

4.It benefits from the ability to leverage commodity hardware.

5.It uses APIs to support interoperability.

Edge computing differs from computing in large data centers in that:

1.Edge sites are as close as possible to end users. They improve the experience over high
latency and unreliable connections.
2. May require specialized hardware, such as GPU/FPGA platforms for AR/VR
functionality.
3. Edge can scale to large numbers of sites, distributed in distinct locations.
4. An edge site’s location and the identity of the access links it terminates are
significant. An application that needs to run close to its users, needs to be in the right
part of the edge. It is common for the application location to matter in edge
computing.
5. The entire pool of sites can be considered to be dynamic. Because of their physical
separation, edge sites will, in some cases, be connected to each other and the core
with WAN connections. Edge sites will join and leave the pool of infrastructure over
time.
6. Edge sites are remote and potentially unmanned, and therefore must be administered
remotely. Tools need to support intermittent network access to the site.

17
 7. Edge supports large differences in site size and scale, from data center scale down to a
single device.
8. Edge sites may be resource constrained; adding capacity to an existing site is
restricted due to space or power requirements.
9. Multi-tenancy on a massive scale is required for some of the use cases.

9. CHARACTERISTICS

Isolation of edge computing from data center clouds may be required to ensure that
compromises in the “external cloud” domain cannot impact services.
So what do we know so far about edge computing characteristics, use cases, and scenarios?
The defining need that drives cloud edge computing is the need for service delivery to be
closer to users or end-point data sources. Edge computing environments will work in
conjunction with core capacity, but aim to deliver an improved end user experience without
putting unreasonable demands on connectivity to the core. Improvements result from:

9.1 REDUCING LATENCY:

The latency to the end user could be lower than it would be if the compute was farther away
—making, for instance, responsive remote desktops possible, or successful AR, or better
gaming.

9.2 MITIGATING BANDWIDTH LIMITS: The ability to move workloads closer to the
end users or data collection points reduces the effect of limited bandwidth at a site. This is
especially useful if the service on the edge node reduces the need to transmit large amounts of
data to the core for processing, as is often the case with IoT and NFV workloads. Data
reduction and local processing can be translated into both more responsive applications and
reduces the cost of transporting terabytes of data over long distances.

But there are tradeoffs. To deliver edge computing, it is necessary to vastly increase the
number of deployments. This institutes a significant challenge to widespread edge
deployments. If managing a single cloud takes a team of ten, how can an organization cope
with hundreds or even thousands of small clouds? Some requirements include:

Standardization and infrastructure consistency are needed. Each location has to be similar; a
known quantity.

18
Manageability needs to be automated; deployment, replacement and any recoverable failures
should be simple and straightforward.

Simple, cost-effective plans need to be laid for when hardware fails.

Locally fault-tolerant designs might be important, particularly in environments that are

remote or unreachable—zero touch infrastructure is desirable. This is a question that balances
the cost of buying and running redundant hardware against the cost of outages and emergency
repairs. Considerations include
Do these locations need to be self-sufficient?

If a location has a failure, no one is going to be onsite to fix it, and local spares are unlikely.
Does it need to tolerate failures? And if it does, how long is it going to be before someone
will be available to repair it—two hours, a week, a month?
Maintainability needs to be straightforward—untrained technicians perform manual repairs
and replacements, while a skilled remote administrator re-installs or maintains software.

Physical designs may need a complete rethink. Most edge computing environments won’t be
ideal—limited power, dirt, humidity and vibration have to be considered.

9.3 USE CASES

There are probably dozens of ways to characterize use cases and this paper is too short to
provide an exhaustive list. But here are some examples to help clarify thinking and highlight
opportunities for collaboration.

Four major categories of workload requirements that benefit from a distributed architecture
are analytics, compliance, security, and NFV.

10.DATA COLLECTION AND ANALYTICS

IoT, where data is often collected from a large network of microsites, is an example of an
application that benefits from the edge computing model. Sending masses of data over often
limited network connections to an analytics engine located in a centralized data center is
counterproductive; it may not be responsive enough, could contribute to excessive latency,
and wastes precious bandwidth. Since edge devices can also produce terabytes of data, taking

19
the analytics closer to the source of the data on the edge can be more cost-effective by
analyzing data near the source and only sending small batches of condensedlosing some
information.

10.1 SECURITY

Unfortunately, as edge devices proliferate––including mobile handsets and IoT sensors––new

attack vectors are emerging that take advantage of the proliferation of endpoints. Edge
computing offers the ability to move security elements closer to the originating source of
attack, enables higher performance security applications, and increases the number of layers
that help defend the core against breaches and risk.

10.2 COMPLIANCE REQUIREMENTS

Compliance covers a broad range of requirements, ranging from geofencing, data

sovereignty, and copyright enforcement. Restricting access to data based on geography and
political boundaries, limiting data streams depending on copyright limitations, and storing
data in places with specific regulations are all achievable and enforceable with edge
computing infrastructure.

10.3 NETWORK FUNCTION VIRTUALIZATION (NFV)

Network Function Virtualization (NFV) is at its heart the quintessential edge computing
application because it provides infrastructure functionality. Telecom operators are looking to
transform their service delivery models by running virtual network functions as part of, or
layered on top of, an edge computing infrastructure. To maximize efficiency and minimize
cost/complexity, running NFV on edge computing infrastructure makes sense.

10.4 REAL-TIME

Real-time applications, such as AR/VR, connected cars, telemedicine, tactile internet Industry
4.0 and smart cities, are unable to tolerate more than a few milliseconds of latency and can be
extremely sensitive to jitter, or latency variation. As an example, connected cars will require
low latency and high bandwidth, and depend on computation and content caching near the

20
user, making edge capacity a necessity. In many scenarios, particularly where closed-loop
automation is used to maintain high availability, response times in tens of milliseconds are
needed, and cannot be met without edge computing infrastructure.

10.5 IMMERSIVE

Edge computing expands bandwidth capabilities, unlocking the potential of new immersive
applications. Some of these include AR/VR, 4K video, and 360° imaging for verticals like
healthcare. Caching and optimizing content at the edge is already becoming a necessity since
protocols like TCP don’t respond well to sudden changes in radio network traffic. Edge
computing infrastructure, tied into real-time access to radio/network information can reduce
stalls and delays in video by up to 20% during peak viewing hours, and can also vary the
video feed bitrate based on radio conditions.

10.6 NETWORK EFFICIENCY

Many applications are not sensitive to latency and do not require large amounts of nearby
compute or storage capacity, so they could theoretically run in a centralized cloud, but the
bandwidth requirements and/or compute requirements may still make edge computing a more
efficient approach. Some of these workloads are common today, including video surveillance
and IoT gateways, while others, including facial recognition and vehicle number plate
recognition, are emerging capabilities. With many of these, the edge computing
infrastructure.

10.7 SELF-CONTAINED AND AUTONOMOUS SITE OPERATIONS

Many environments, even today, have limited, unreliable or unpredictable connectivity.

These could include transportation (planes, buses, ships), mining operations (oil rigs,
pipelines, mines), power infrastructure (wind farms, solar power plants), and even
environments that should typically have good connectivity,like stores. Edge computing neatly
supports such environments by allowing sites to remain semi-autonomous and functional
when needed or when the network connectivity is not available. The best example of this
approach is the need for retail locations to maintain their point of sales (POS) systems, even
when there is temporarily no network connectivity.

21
10.8 PRIVACY

Enterprises may have needs for edge computing capacity depending on workloads,
connectivity limits and privacy. For example, medical applications that need to anonymize
personal health information (PHI) before sending it to the cloud could do this utilizing edge
computing infrastructure.

Another way to look at requirements that would benefit from cloud edge computing is by the
type of company that would deploy them. Operator applications are workloads put on edge
computing infrastructure that is built and managed by operators—telecommunications
companies, for example. Third-party applications are built by organizations to run on existing
edge infrastructure, in order to leverage others’ edge computing infrastructure. It is worth
noting that any applications could leverage any or all of the capabilities provided by a cloud
— compute, block storage, object storage, virtual networking, bare metal, or containers

11 SCENARIOS

The basic characteristic of the edge computing paradigm is that the infrastructure is located
closer to the end user, that the scale of site distribution is high and that the edge nodes are
connected by WAN network connections. Examining a few scenarios in additional depth
helps us evaluate current capabilities that map to the use case, as well as highlighting
weaknesses and opportunities for improvement.
Retail/finance/remote location “cloud in a box”: Edge computing infrastructure that supports
a suite of applications customized to the specific company or industry vertical. Often used by
the enterprise, edge computing infrastructure, ultimately coupled together into distributed
infrastructure, to reduce the hardware footprint, standardize deployments at many sites,
deliver greater flexibility to replace applications located at the edge (and to have the same
application running uniformly in all nodes irrespective of HW), boost resiliency, and address
concerns about intermittent WAN connections. Caching content or providing compute,
storage, and networking for self-contained applications are obvious uses for edge computing
in settings with limited connectivity.

Mobile connectivity: Mobile/wireless networks are likely to be a common environmental

element for cloud edge computing, as mobile networks will remain characterized by limited

22
and unpredictable bandwidth, at least until 5G becomes widely available. Applications such
as augmented reality for remote repair and telemedicine, IoT devices for capturing utility
(water, gas, electric, facilities management) data, inventory, supply chain and transportation
solutions, smart cities, smart roads and remote security applications will all rely on the
mobile network to greater or lesser degrees. They will all benefit from edge computing’s
ability to move workloads closer to the end user.

Public Network Private Network

 Latency LCore

.
FIG 11.1: MOBILE CONNECTIVITY

Network-as-a-Service (NaaS): Coming from the need to deliver an identical network service
application experience in radically different environments, the NaaS use case requires both a
small footprint of its distributed platform at the edges, and strong centralized management
tools that cross over unreliable or limited WAN network connections in support of the
services out on the edge. The main characteristics of this scenario are: small hardware
footprint, moving (changing network connections) and constantly changing workloads,
hybrid locations of data and applications. This is one of the cases that needs infrastructure to
support micro nodes—small doses of compute in non-traditional packages (not all 19in rack
in a cooled data center). NaaS will require support for thousands or tens of thousands of
nodes at the edge and must support mesh and/or hierarchical architectures as well as on
demand sites that might spin up as they are needed and shutdown when they are done. APIs
and GUIs will have to change to reflect that large numbers of compute nodes will have
different locations instead of being present in the same data center.

23
Universal Customer Premises Equipment (UCPE): This scenario, already being deployed
today, demands support for appliance-sized hardware footprints and is characterized by
limited network connections with generally stable workloads requiring high availability. It
also requires a method of supporting hybrid locations of data and applications across
hundreds or thousands of nodes and scaling existing UCPE deployments will be an emerging
requirement.

This is particularly applicable to NFV applications where different sites might need a
different set of service chained applications, or sites with a different set of required
applications that still need to work in concert. Mesh or hierarchical architectures would need
to be supported with localized capacity and the need to store and forward data processing due
to intermittent network connections. Self-healing and self-administration combined with the
ability to remotely administer the node are musts.

Satellite enabled communication (SATCOM): This scenario is characterized by numerous

capable terminal devices, often distributed to the most remote and harsh conditions. At the
same time, it makes sense to utilize these distributed platforms for hosting services,
especially considering the extremely high latency, limited bandwidth and the cost of over-
the-satellite communications. Specific examples of such use cases might include vessels
(from fishing boats to tanker ships), aircrafts, oil rigs, mining operations or military grade
infrastructure.

12. CONCLUSION:

Cloud computing is the most popular notion in IT today; even an academic report from UC
Berkeley says “Cloud Computing is likely to have the same impact on software that foundries
have had on the hardware industry.” They go on to recommend that “developers

After so many years, Cloud Computing today is the beginning of “network based
computing” over Internet in force. It is the technology of the decade and is the enabling
element of two totally new computing models, the Client-Cloud computing and the
Terminal-Cloud computing. These new models would create whole generations of
applications and business. Our prediction is that it is the beginning to the end of the

24
dominance of desktop computing such as that with the Windows. It is also the beginning of
a new Internet based service economy: the Internet centric, Web based, on demand, Cloud
applications and computing economy.

25
13.REFERENCES:

1. www.wikipedia.com
2. http://www.infoworld.com/d/cloud- computing/what-cloud-computing- really-
means-031
3. http://www.salesforce.com/cloudcom puting/
4. http://www.it- director.com/business/innovation/co ntent.php?cid=11990

26