A

PROJECT REPORT ON

A Real-Time Adaptive Algorithm

for Video Streaming Over Multiple Wireless
Access Networks
Submitted in partial fulfillment for the award of the degree of
BACHELOR OF TECHNOLOGY

in
COMPUTER SCIENCE & ENGINEERING
By
DONTHULA PRANAVI : 17Q91A05I7
SRIPADA ANUDEEP : 16Q91A05L7
T.ARAVINDARAJU : 18Q95A0505
SANJU BAGRI : 17Q91A05J4

Under the guidance of

Mr. CH. Vengaiah M. Tech

Assistant Professor, Dept. of CSE

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

MALLA REDDY COLLEGE OF ENGINEERING
(Approved by AICTE-Permanently Affiliated to JNTU-Hyderabad)
Accredited by NBA & NAAC, Recognized section 2(f) & 12(B) of UGC
New Delhi ISO 9001:2015 certified Institution
Maisammaguda, Dhulapally (Post via Kompally), Secunderabad- 500100
2020 - 2021
 MALLA REDDY COLLEGE OF ENGINEERING
(MALLA REDDY GROUP OF INSTITUTIONS)
(Approved by AICTE- Permanently Affiliated to JNTU Hyderabad)
Accredited by NBA & NAAC, Recognized under section 2(f) &12(B) of UGC
New Delhi: ISO 9001:2015 certified Institution
Maisammaguda, Dhulapally (Post via Kompally), Secunderabad- 500100

CERTIFICATE

This is to certify that the Major Project report on “A REAL-TIME

ADAPTIVE ALGORITHM FOR VIDEO STREAMING OVER MULTIPLE
WIRELESS ACCESS NETWORKS” is successfully done by the following students of
Department of Computer Science & Engineering of our college in partial fulfillment of the
requirement for the award of B.Tech degree in the year 2020-2021. The results embodied in
this report have not been submitted to any other University for the award of any diploma or
degree.

DONTHULA PRANAVI : 17Q91A05I7

SRIPADA ANUDEEP : 16Q91A05L7
T.ARAVINDARAJU : 18Q95A0505
SANJU BAGRI : 17Q91A05J4

INTERNAL GUIDE HOD PRINCIPAL

Mr. CH. Vengaiah Mr. Ch. Vijaya Kumari Dr. M. Sreedhar Reddy
Asst.Professor Assoc. Professor Professor

_________________________________________________________________________________________
Submitted for the viva voice examination held on

Internal Examiner External Examiner

i
 DECLARATION

We, Donthula Pranavi,Sripada Anudeep, T.Aravindaraju, Sanju Bagri,

with Regd.no.17Q91A05I7, 16Q91A05L7, 18Q95A0505, 17Q91A05J4, are hereby
declaring that the mini project report entitled “A Real-Time Adaptive Algorithm for Video
Streaming Over Multiple Access Networks” has done by us under the guidance of
Mr. Ch.Vengaiah,(M.Tech)Assistant Professor, Department of CSE is submitted in the
partial fulfillment of the requirements for the award of degree of BACHELOR OF
TECHNOLOGY in COMPUTER SCIENCE AND ENGINEERING.
The Results embodied in this project report have not been submitted to any other University
or Iinstitute for the award of any degree or diploma.

Signature of the Candidate,

Donthula Pranavi 17Q91A05I7

Sripada Anudeep 16Q91A05L7
T.AravindaRaju 18Q95A0505
Sanju Bagri 17Q91A05J4

Date :
Place : Maisammaguda

ii
 ACKNOWLEDGEMENT

First and foremost, we would like to express our immense gratitude towards
our institution Malla Reddy College of Engineering, which helped us to attain
profound technical skills in the field of Computer Science & Engineering, there by
fulfilling our most cherished goal.
We are pleased to thank Sri Ch. Malla Reddy, our Founder, Chairman
MRGI, Sri Ch. Mahender Reddy, Secretary, MRGI for providing this opportunity
and support throughout the course.
It gives us immense pleasure to acknowledge the perennial inspiration of
Dr. M Sreedhar Reddy our beloved principal for his kind co-operation and
encouragement in bringing out this task.
We would like to thank Dr. T. V. Reddy our vice principal, Mrs. Ch.Vijaya
Kumari, HOD, CSE Department for their inspiration adroit guidance and constructive
criticism for successful completion of our degree.
We convey our gratitude to Dr. Gladson Mario Britto R & D Coordinator and
Mr. Sayyad Rasheed Uddin, & Mr. Ch. Vengaiah, Assistant Professor, our project
coordinator for their valuable guidance.
We would like to thank Mr. Ch.Vengaiah Assistant Professor our internal
guide, for his valuable suggestions and guidance during the exhibition and completion
of this project.
Finally, we avail this opportunity to express our deep gratitude to all staff who
have contribute their valuable assistance and support making our project success.

Donthula Pranavi 17Q91A05I7

Sripada Anudeep 16Q91A05L7
T.Aravindaraju 18Q95A0505
Sanju Bagri 16Q91A0535

iii
 INDEX

LIST OF CONTENTS PAGE NO

DECLARATION i
CERTIFICATE ii
ACKNOWLEDGEMENT iii
NAME OF THE TOPIC
CHAPTER 1: INTRODUCTION 1
1.1 Objective
1.2 Synopsis
1.3 Existing System
1.4 Proposed System
1.5 System Architecture
1.6 Hardware and Software Specifications
CHAPTER 2: LITERATURE SURVEY 5
2.1 Literature Survey
CHAPTER 3: DIAGRAMS 7
3.1 Data flow Diagram
3.2 UML Diagram
CHAPTER 4: MODULES 13
4.1 User Profile Module
4.2 NDAMMM
4.3 DNEM
4.4 NDBTM
4.5 ACMPF
CHAPTER 5: CLOUD COMPUTING 19
CHAPTER 6: ALGORITHM 24

iv
CHAPTER 7: ANDROID 27
7.1 Overview of Android
7.2 Features
7.3 Linux kernel
7.4 Android Runtime
7.5 Libraries
7.6 Application Framework
CHAPTER 8: ARCHITECTURE 30
CHAPTER 9: JAVA SERVER PAGES(JSP) 34
9.1 Architecture of JSP
9.2 Advantages of JSP
CHAPTER 10: SERVLETS 36
10.1 Servlet Run Time Environment
10.2 Life Cycle of Servlet
CHAPTER 11: FEASABILITY STUDY 39
11.1 Technical Feasibility
11.2 Operational Feasibility
11.3 Economical Feasibility
CHAPTER 12: JAVA 41
12.1 J2EE Application
12.2 Servlets
CHAPTER 13: TESTING 44
CHAPTER 14: METHODOLOGY 48
14.1 Waterfall Approach
14.2 V Model

v
CHAPTER 15: SOURCE CODE 51
15.1 Web Service
15.2 Trance coder code
15.3 Android code
CHAPTER 16: SCREENSHOT 67
CHAPTER 17: CONCLUSION 75
17.1 Future Work
REFERENCES 76

vi
 CHAPTER 1
INTRODUCTION

１
 A Real-Time Adaptive Algorithm for Video
Streaming over Multiple Wireless Access Networks

OBJECTIVE:
 In this paper, we realized a prototype of this architecture to validate the feasibility of
the proposed method.
 According to the experiment, this method could provide efficient self-adaptive
multimedia streaming services for varying bandwidth environments.

DOMAIN: Cloud Computing

SYNOPSIS:
Video streaming is gaining popularity among mobile users. The latest mobile
devices, such as smart phones and tablets, are equipped with multiple wireless network
interfaces. How to efficiently and cost-effectively utilize multiple links to improve video
streaming quality needs investigation. In order to maintain high video streaming quality
while reducing the wireless service cost, in this paper, the optimal video streaming process
with multiple links is formulated as a Markov Decision Process (MDP). The reward function
is designed to consider the quality of service (QoS) requirements for video traffic, such as
the startup latency, playback fluency, average playback quality, playback smoothness and
wireless service cost. To solve the MDP in real-time, we propose an adaptive, best-action
search algorithm to obtain a sub-optimal solution. To evaluate the performance of the
proposed adaptation algorithm, we implemented a test bed using the Android mobile phone
and the Scalable Video Coding (SVC) codec. Experiment results demonstrate the feasibility
and effectiveness of the proposed adaptation algorithm for mobile video streaming
applications, which outperforms the existing state-of-the-art adaptation algorithms.

２
EXISTING SYSTEM:
In the previous service, the mobile device side exchanges information with the cloud
environment, so as to determine an optimum multimedia video. Scholars have done
numerous researches toward conventional platform (CDN) to store different movie formats
in a multimedia server, to choose the right video stream according to the current network
situation or the hardware calculation capabilities. To solve this problem, many researchers
have attempted dynamic encoding to transfer media content, but still cannot offer the best
video quality.

LIMITATIONS:
 Video communication over mobile broadband networks today is challenging due to
limitations in bandwidth and difficulties in maintaining high reliability, quality, and
latency demands imposed by rich multimedia applications.
 Increasing in network traffic by the use of multimedia content and applications.

PROPOSED SYSTEM:
 The proposed system provided an efficient interactive streaming service for
diversified mobile devices and dynamic network environments.
 When a mobile device requests a multimedia streaming service, it transmits its
hardware and network environment parameters to the profile agent in the cloud
environment, which records the mobile device codes and determines the required
parameters.
 Then transmits them to the Network and Device-Aware Multi-layer Management
(NDAMM). The NDAMM determines the most suitable SVC code for the device
according to the parameters, and then the SVC Transcoding Controller (STC) hands
over the transcoding work via map-reduce to the cloud, in order to increase the
transcoding rate.
 The multimedia video file is transmitted to the mobile device through the service.

３
ADVANTAGES:
 The network bandwidth can be changed dynamically.
 This method could provide efficient self-adaptive multimedia streaming services.

SYSTEM ARCHITECTURE:

４
HARDWARE AND SOFTWARE SPECIFICATION:
Software Requirement:

1. Language - Java (JDK 1.7)

2. OS - Windows 7- 32bit
3. MySql Server
4. Android ADK

Hardware Requirement:

1. 1 GB RAM
2. 80 GB Hard Disk
3. Above 2GHz Processor
4. Android Mobile With GPRS

５
 CHAPTER 2
LITERATURE SURVEY

６
 LITERATURE SURVEY
1) Media Cloud: When Media Revolution Meets Rise of Cloud Computing
Mingfeng Tan Computer Engineering Department San Jose State University San Jose, CA,
U.S.
mingfeng.tan@gmail.com
Media cloud provides a cost-effective and powerful solution for the coming tide of
the media consumption. Based on previous summary of the recent work on media cloud
research, in this section, we first make some suggestions on how to build the media cloud,
and then propose some potentially promising topics for future research.

2) Multimedia cloud computing

Digital Object Identifier 10.1109/MSP.2011.940269
Date of publication: 19 April 2011
This article introduces the principal concepts of multimedia cloud computing and
presents a novel framework. We address multimedia cloud computing from multimedia-
aware cloud (media cloud) and cloud-aware multimedia (cloud media) perspectives. First,
we present a multimedia-aware cloud, which addresses how a cloud can perform distributed
multimedia processing and storage and provide quality of service (QoS) provisioning for
multimedia services. To achieve a high QoS for multimedia services, we propose a media-
edge cloud (MEC)
architecture, in which storage, central processing unit (CPU), and graphics processing unit
(GPU) clusters are presented at the edge to provide distributed parallel processing and QoS
adaptation for various types of devices.

3) Seamless Support of Multimedia Distributed Applications Through a Cloud

Stefano Ferretti, Vittorio Ghini, Fabio Panzieri, Elisa Turrini
Department of Computer Science, University of Bologna
We are planning to carry out a validation and a thorough experimental assessment of
the performance of our cross-layer architecture as soon as its development will be completed.
In addition, we would like to extend our study on this class of architectures to investigate the
impact of dependability issues, such as fault tolerance and security, on their design.

７
4) Distributed Scheduling Scheme for Video Streaming over Multi-Channel Multi-
Radio Multi-Hop Wireless Networks
Liang Zhou, Xinbing Wang, Wei Tu, Gabriel-Miro Muntean, and Benoit Geller

In this paper, we have developed fully distributed scheduling schemes that jointly
solve the channel-assignment, rate allocation, routing and fairness problems for video
streaming over multi-channel multi-radio networks. Unlike conventional scheduling schemes
focus on optimal system throughput or scheduling efficiency, our work aims at achieving
minimal video distortion and certain fairness by jointly considering media-aware distribution
and network resource allocation. Extensive simulation results are provided which
demonstrate the effectiveness of our proposed schemes.

5) Toward Optimal Deployment of Communication-Intensive Cloud Applications

Pei Fan, Ji Wang National Laboratory for Parallel & Distributed Processing
National University of Defense Technology
Changsha,410073,P.R.China peifan@nudt.edu.cn,jiwang@ios.ac.cn

In this paper, we propose a clustering-based cloud node selection approach for

communication-intensive cloud applications. By taking advantage of the cluster analysis, our
approach not only considers the QoS values of cloud nodes, but also considers the
relationship (i.e., response time) between cloud nodes. Our approach systematically
combines cluster analysis and ranking methods. The experimental results show that our
approach outperforms the existing
ranking approaches.

6) Playback-Rate Based Streaming Services for Maximum Network Capacity in IP

Multimedia Subsystem
Chin-Feng Lai, Member, IEEE, and Min Chen, Senior Member, IEEE
This paper proposed cross-layer playback-rate based streaming services, which can
maintain network transmission quality and receive data before playback reliably in IMS
networks with many users. The experimental results show that the services could reduce the
overall network load without the occurrence of dropped packets.

８
CHAPTER 3
DIAGRAMS

９
 DIAGRAMS
DATAFLOW DIAGRAM

LEVEL 0:

User Mobile

Mobile
Profile

Profile
Examination

Cloud

LEVEL 1:

User Mobile

NDAM
M

DNEM

Cloud

１０
LEVEL 2:

User Mobile

Mobile
Profile

NDAMM
And DNEM

Bit Rate

SVC
Transcoding

Cloud

Streaming in
Mobile

１１
UML Diagrams
1. Use Case Diagram

Android Phone

Application

GPRS
User Cloud Server

Searching File

Reterive File

Fig.3.1.Use Case Diagram

2. Class Diagram

Fig.3.2.Class Diagram

１２
3. Activity Diagram

User

Android
Phone

Application

Search Device
Media File Configura...

Media
Profile

Cloud
Server

Retrieve
Media File

Display

Fig.3.3.Activity Diagram

１３
4. Sequence Diagram

User Application Phone Media Services Cloud

Request

Response

Search Media data

Request

Mobile Profile

User Profile

Request Data

Media Data

NDAMM

SVC Transcoding
Split Data Reducer

Maping

Result

SVC Data Formate

View Data

Fig.3.4. Sequence Diagram

１４
5. Collaboration Diagram

6: User Profile
9: SVC Transcoding

1: Request
User 3: Search Media data 7: Request Data Media Services
Application

2: Response 8: Media Data

14: View Data

11: Maping 5: Mobile Profile 4: Request

13: SVC Data Formate

10: Split Data

Cloud 12: Result

Phone

Fig.3.5.Collaboration Diagram
6.ER Diagram

Android Phone GPRS

Access Files Androidphone Device
Searh File Configuration

Use Network
Access Server User Application

File Format
View File
Use

Server

Services
Response

Multimedia
Files

Fig.3.6.ER Diagram

１５
CHAPTER 4
MODULES

１６
 MODULES

1. User Profile Module

2. Network and Device Aware Multi-Layer Management (NDAMM)
3. Dynamitic Network Estimation Module (DNEM)
4. Network and Device-Aware Bayesian Prediction Module (NDBPM)
5. Proposed Adaptive Communication and Multi-Layer Content Selection (ACMCS)

1. User Profile Module:

The profile agent is used to receive the mobile hardware environment
parameters and create a user profile. The mobile device transmits its hardware
specifications in XML-schema format to the profile agent in the cloud server. The
XML-schema is metadata, which is mainly semantic and assists in describing the
data format of the file. The metadata enables non-owner users to see information
about the files, and its structure is extensible. However, any mobile device that is
using this cloud service for the first time will be unable to provide such a profile, so
there shall be an additional profile examination to provide the test performance of the
mobile device and sample relevant information. Through this function, the mobile
device can generate an XML-schema profile and transmit it to the profile agent. The
profile agent determines the required parameters for the XML-schema and creates a
user profile, and then transmits the profile to the DAMM for identification.

User Profile Profile Agent Profile

Examination

Fig.4.1.User Profile Module

１７
2. Network and Device Aware Multi-Layer Management (NDAMM):
The NDAMM aims to determine the interactive communication frequency and
the SVC multimedia file coding parameters according to the parameters of the mobile
device. It hands these over to the STC for transcoding control, so as to reduce the
communication bandwidth requirements and meet the mobile device user’s demand for
multimedia streaming. It consists of a listen module, a parameter profile module, a
network estimation module, a device-aware Bayesian prediction module, and adaptive
multi-layer selection. The interactive multimedia streaming service must receive the user
profile of the mobile device instantly through the listen module. The parameter profile
module records the user profile and determines the parameter This is provided to both the
network estimation module and the device-aware Bayesian prediction module to predict
the required numerical values. Rw and Rh represent the width and height of the
supportable resolution for the device, CPavg and CP represent the present and average
CPU operating speed. Db and Db rate represent the existing energy of the mobile device
and energy consumption rate, and BW, BWavg, and BWstd represent the existing,
average and standard deviation values of the bandwidth. When this parameter form is
maintained, the parameters can be transmitted to the network estimation module and the
device-aware Bayesian prediction module for relevant prediction.

Para Profile

Getting Output Sending Input

from User Profile to DNEM

Listener

Fig.4.2.Network and Device Aware Multi-Layer Management

１８
3. Dynamitic Network Estimation Module (DNEM):

The DNEM is mainly based on the measurement-based prediction concept;

however, it further develops the Exponentially Weighted Moving Average (EWMA).
The EWMA uses the weights of the historical data and the current observed value to
calculate gentle and flexible network bandwidth data for the dynamic adjustment of
weights. In order to determine the precise network bandwidth value, the EWMA
filter estimates the network bandwidth value in which is the estimated bandwidth of
the No. t time interval, is the bandwidth of the No. time interval, and is the estimation
difference. For different mobile network estimations, this study considered the error
correction of estimation and the overall standard difference and estimated the
different bandwidths by adjusting the weights among which, is the moving average
weight and is the standard deviation weight. When the prediction error is greater than,
the system shall reduce the weight modification of the predicted difference; relatively,
when the prediction error is less than, the system shall strengthen the weight
modification of the predicted difference. When the changed bandwidth of the system
is greater than the standard difference, the predicted weight will increase as the
corrected value of the standard deviation is reduced. The predictor formula for the
overall mobile network quality uses the standard normal state value range concept of
plus-minus three standard deviations of statistics, referring to identify the stable or
unstable state of the current mobile network. If the present mobile network is in a
stable state, it shall conform to the following equation among which, is the
coefficient of the evaluated standard deviation. The value is almost 1.128. If the
network bandwidth value of this time cycle is within plus-minus three standard
deviations of the standard value, the present mobile network will be in a stable state;
otherwise it will be in a fluctuating state.

Providing Input
Getting Output from EWMA Used to to DBPM
NDAMM calculate
Bandwidth

Fig.4.3.Dynamitic Network Estimation Module

１９
 4. Network and Device-Aware Bayesian Prediction Module (NDBPM):

The SVC hierarchical structure provides scalability of the temporal, spatial and
quality dimensions. It adjusts along with the FPS, resolution and video variations of a
streaming bitrate: however, the question remains of how to choose an appropriate video
format according to the available resources of various devices. Hereby, in order to conform
to the real-time requirements of mobile multimedia, this study adopted Bayesian theory to
infer whether the video features conformed to the decoding action. The inference module
was based on the following two conditions:

• The LCD brightness does not always change This hypothesis aims at a hardware energy
evaluation. The literature states that TFT LCD energy consumption accounts for about 20%–
45% of the total power consumption for different terminal hardware environments. Although
the overall power can be reduced effectively by adjusting the LCD, with multimedia services,
users are sensitive to brightness; they dislike video brightness that repeatedly changes. As
changing the LCD brightness will influence the energy consumption evaluation value, the
LCD brightness of the mobile device is assumed to not able to change at will during
multimedia service.

• The energy of the mobile device shall be sufficient for playing a full multimedia video Full
multimedia service must be able to last until the user is satisfied. This assumed condition is
also the next main decision rule.

As for the three video parameters of FPS, resolution and bit rate, the bit rate depends on the
frame rate and resolution, so the Bayesian network adopts the frame rate and resolution as
the video input features and uses the bit rate as parameter considered.

Device Feature Inference Case Video Feature

Fig.4.4.Network and Device-Aware Bayesian Prediction Module

２０
5. Proposed Adaptive Communication and Multi-Layer Content
Selection (ACMCS):

When the predicted bandwidth state and the Bayesian predictive network are
determined, the cloud system will further determine the communication and the
required multimedia video files according to the information.
1) Communication Decision:
A good dynamic communication mechanism can reduce the bandwidth needs and
the power consumption of the device resulting from excessive packet transmission,
and the transmission frequency can be determined according to the bandwidth and its
fluctuation ratio based on such dynamic decision-making. The transmit mode is
engaged until the device finds a variation of the transmitted variables that exceeds a
threshold. Although the threshold can reduce the communication frequency
effectively and precisely, in this mode the mobile device must start up additional
threads for continuous monitoring; thus, the load on the device side is increased.
When the network bandwidth difference exceeds a triple standard deviation, this
indicates the present network is unstable. The overall communication frequency shall
incline to frequency to avoid errors; however, when the network bandwidth
difference is less than a triple standard deviation, the current network is still in a
stable state, and the influence on bandwidth difference can be corrected gradually.
2) SVC Multi-Layer Content Decision:
SVC is an improvement over traditional H.264/MPEG-4 AVC coding, as it
has higher coding flexibility. It is characterized by temporal scalability, spatial
scalability and SNR scalability, allowing video transmissions to be more adaptable to
heterogeneous network bandwidth. This study investigated how to determine an
appropriate multimedia video streaming service according to these three major
characteristics. First, the appropriate bandwidth interval was determined, in which
the average bandwidth was used as the standard value and each standard deviation
was the bandwidth interval segment. A quadruple standard difference is assumed to
be the boundary value. As the communication and prediction mechanisms are
constructed, the system will correct the overall threshold according to the bandwidth
variation gradually, inorder to avoid the bandwidth boundary exceeding the practical

２１
 situation. When the bandwidth interval is completed, it becomes the criterion of the
video streaming bit rate. The appropriate resolution and frame rate can then be
determined as the streaming data. When the mobile device transmits the current
network and hardware features to the cloud environment, the NDAMM will predict
the bandwidth at the next time point according to the bandwidth and standard
deviation and will identify whether the bandwidth state is stable or not. The DBPM
infers whether the multimedia video, at different resolutions and frame rates, can
complete smooth decoding and whether the hardware can provide complete video
playback services, according to the profile examination and subsequent hardware
features. When the Bayesian inference table is completed, the next communication
time can be determined, and the SVC multimedia coding applicable for the mobile
device can be provided according to the predicted and inferred network and hardware
features.

Mobile Profile Bit Rate SVC Transcoding

Fig.4.5.Proposed Adaptive Communication and Multi-Layer Content Selection

２２
 CHAPTER 5
CLOUD COMPUTING

２３
 CLOUD COMPUTING
Cloud computing is the use of computing resources (hardware and software) that are
delivered as a service over a network (typically the Internet). The name comes from the use
of a cloud-shaped symbol as an abstraction for the complex infrastructure it contains in
system diagrams. Cloud computing entrusts remote services with a user's data, software and
computation.

There are many types of public cloud computing:

 Infrastructure as a service (IaaS)

 Platform as a service (PaaS)

 Software as a service (SaaS)

 Storage as a service (STaaS)

 Security as a service (SECaaS)

 Data as a service (DaaS)

 Test environment as a service (TEaaS)

 Desktop as a service (DaaS)

 API as a service (APIaaS)

The business model, IT as a service (ITaaS), is used by in-house, enterprise IT

organizations that offer any or all of the above services.

Using software as a service, users also rent application software and databases. The
cloud providers manage the infrastructure and platforms on which the applications run. End
users access cloud-based applications through a web browser or a light-weight desktop
or mobile app while the business software and user's data are stored on servers at a remote
location. Proponents claim that cloud computing allows enterprises to get their applications
up and running faster, with improved manageability and less maintenance, and enables IT to
more rapidly adjust resources to meet fluctuating and unpredictable business demand.

２４
Cloud computing used in:

 Autonomic computing — Computer systems capable of self-management.

 Client–server model — Client–server computing refers broadly to any distributed

application that distinguishes between service providers (servers) and service requesters

(clients).

 Grid computing — "A form of distributed and parallel computing, whereby a 'super

and virtual computer' is composed of a cluster of networked, loosely coupled computers

acting in concert to perform very large tasks."

 Mainframe computer — Powerful computers used mainly by large organizations for

critical applications, typically bulk data processing such as census, industry and

consumer statistics, police and secret intelligence services, enterprise resource planning,

and financial transaction processing.

 Utility computing — The "packaging of computing resources, such as computation

and storage, as a metered service similar to a traditional public utility, such as

electricity."

 Peer-to-peer — Distributed architecture without the need for central coordination,

with participants being at the same time both suppliers and consumers of resources (in

contrast to the traditional client–server model).

 Cloud gaming - Also called On-demand gaming is a way of delivering to games to

computers. The gaming data will be stored in the provider's server, so that gaming will

be independent of client computers used to play the game.

２５
Characteristics

 Agility improves with users' ability to re-provision technological infrastructure

resources.

 Application programming interface (API) accessibility to software that enables

machines to interact with cloud software in the same way the user interface facilitates

interaction between humans and computers. Cloud computing systems typically

use REST-based APIs.

 Cost is claimed to be reduced and in a public cloud delivery model capital

expenditure is converted to operational expenditure.

This is purported to lower barriers to entry, as infrastructure is typically provided

by a third-party and does not need to be purchased for one-time or infrequent intensive

computing tasks. Pricing on a utility computing basis is fine-grained with usage-based

options and fewer IT skills are required for implementation (in-house).The e-FISCAL

project's state of the art repository contains several articles looking into cost aspects in

more detail, most of them concluding that costs savings depend on the type of activities

supported and the type of infrastructure available in-house.

 Device and location independence enable users to access systems using a web

browser regardless of their location or what device they are using (e.g., PC, mobile

phone). As infrastructure is off-site (typically provided by a third-party) and accessed via

the Internet, users can connect from anywhere.

 Virtualization technology allows servers and storage devices to be shared and

utilization be increased. Applications can be easily migrated from one physical server to

another.

２６
 Multitenancy enables sharing of resources and costs across a large pool of users thus

allowing for:

 Centralization of infrastructure in locations with lower costs (such as real

estate, electricity, etc.)

 Peak-load capacity increases (users need not engineer for highest possible

load-levels)

 Utilization and efficiency improvements for systems that are often only 10–

20% utilized.

 Reliability is improved if multiple redundant sites are used, which makes well-

designed cloud computing suitable for business continuity and disaster recovery.[30]

 Scalability and elasticity via dynamic ("on-demand") provisioning of resources on a

fine-grained, self-service basis near real-time, without users having to engineer for peak

loads.

 Performance is monitored, and consistent and loosely coupled architectures are

constructed using web services as the system interface.

 Security could improve due to centralization of data, increased security-focused

resources, etc., but concerns can persist about loss of control over certain sensitive data,

and the lack of security for stored kernels. Security is often as good as or better than

other traditional systems, in part because providers are able to devote resources to

solving security issues that many customers cannot afford. However, the complexity of

security is greatly increased when data is distributed over a wider area or greater number

of devices and in multi-tenant systems that are being shared by unrelated users. In

addition, user access to security audit logs may be difficult or impossible. Private cloud

installations are in part motivated by users' desire to retain control over the infrastructure

and avoid losing control of information security.

２７
 Maintenance of cloud computing applications is easier, because they do not need to

be installed on each user's computer and can be accessed from different places.

Virtualization

Virtualization (or virtualisation) is the creation of a virtual (rather than actual)

version of something, such as a hardware platform, operating system (OS), storage device, or
network resources.

While a physical computer in the classical sense is clearly a complete and actual
machine, both subjectively (from the user's point of view) and objectively (from the hardware
system administrator's point of view), a virtual machine is subjectively a complete machine
(or very close), but objectively merely a set of files and running programs on an actual,
physical machine (which the user need not necessarily be aware of).

Virtualization can be viewed as part of an overall trend in enterprise IT that includes

autonomic computing, a scenario in which the IT environment will be able to manage itself
based on perceived activity, and utility computing, in which computer processing power is
seen as a utility that clients can pay for only as needed.

The usual goal of virtualization is to centralize administrative tasks while improving

scalability and overall hardware-resource utilization. With virtualization, several operating
systems can be run in parallel on a single central processing unit (CPU). This parallelism
tends to reduce overhead costs and differs from multitasking, which involves running several
programs on the same OS.

２８
CHAPTER 6

ALGORITHM

２９
 ALGORITHM

Adaptive Communication and Multi-Layer Content Selection (ACMCS)

When the predicted bandwidth state and the Bayesian predictive network are
determined, the cloud system will further determine the communication and the required
multimedia video
files according to the information.
1) Communication Decision: A good dynamic communication mechanism can reduce the
bandwidth needs and the power consumption of the device resulting from excessive packet
transmission, and the transmission frequency can be determined according to the bandwidth
and its fluctuation ratio based on such dynamic decision-making. The transmit mode is
engaged until the device finds a variation of the transmitted variables that exceeds a
threshold. Although the threshold can reduce the communication frequency effectively and
precisely, in this mode the mobile device must start up additional threads for continuous
monitoring; thus, the load on the device side is increased. The communication time is shown
as:

among which, represents the corresponding factor of the bandwidth difference to the stream
flow, and is the set maximum communication time, considering the effect of (5) on network
quality, for the correction of .

When the network bandwidth difference exceeds a triple standard deviation, this indicates
the present network is unstable. The overall communication frequency shall incline to
frequency
to avoid errors; however, when the network bandwidth difference is less than a triple
standard deviation, the current network is still in a stable state, and the influence on
bandwidth difference
can be corrected gradually.

３０
2) SVC Multi-Layer Content Decision: SVC is an improvement
over traditional H.264/MPEG-4 AVC coding, as it has higher coding flexibility. It is
characterized by temporal scalability, spatial scalability and SNR scalability, allowing video
transmissions to be more adaptable to heterogeneous network bandwidth. This study
investigated how to determine an appropriate multimedia video streaming service according
to these three major characteristics. First, the appropriate bandwidth interval was determined,
in which the average bandwidth was used as the standard value and each standard deviation
was the bandwidth interval segment. Let be the bandwidth aggregate, then:

A quadruple standard difference is assumed to be the boundary value. As the communication

and prediction mechanisms are constructed, the system will correct the overall threshold
according to the bandwidth variation gradually, in order to avoid the bandwidth boundary
exceeding the practical situation. When the bandwidth interval is completed, it becomes the
criterion of the video streaming bit rate. The appropriate resolution and frame rate can then
be determined as
the streaming data. Among these, the multimedia file shall conform to the following
conditions:

As mentioned above, the system will determine the ultimate resolution and a frame rate that
are lower than each frequency range interval as the multimedia space and time features. The
file must enable the device to decode smoothly and finish the complete decoding. The
overall work flow is shown in the following Fig. 3. When the mobile device transmits the
current.

３１
network and hardware features to the cloud environment, the NDAMM will predict the
bandwidth at the next time point according to the bandwidth and standard deviation and will
identify whether the bandwidth state is stable or not. The DBPM infers whether the
multimedia video, at different resolutions and frame rates, can complete smooth decoding
and whether
the hardware can provide complete video playback services, according to the profile
examination and subsequent hardware features.

３２
CHAPTER 7
ANDROI D

３３
 ANDROID

Overview of Android

It is a free, open source mobile platform. Linux-based, multi process, Multithreaded

OS. Android is not a device or a product It’s not even limited to phones You could build a
DVR, a handheld GPS, an MP3 player, etc.Android is a software stack for mobile devices
that includes an operating system, middleware and key applications.
The Android SDK provides the tools and APIs necessary to begin developing applications
on the Android platform using the Java programming language.
 Makes mobile development easy.
 Full phone software stack including applications
 Designed as a platform for software development
 Android is open
 Android is free
 Community support
 July 2005
o Google acquired Android Inc.
 5 Nov 2007
o Open HandSet Alliance formed-
o Google, HTC, Intel, Motorola, Qualcomm,T-Mobile
 Android is the OHA first product
 12 Nov 2007
o OHA released a preview of the Android OHA
 Oct-2008
o First Device – T-Mobile G1 was released.
o Latest – Motorola Milestone released in India.
Features
 Application framework enabling reuse and replacement of components
 Dalvik virtual machine optimized for mobile devices
 Integrated browser based on the open source WebKit engine
 Optimized graphics powered by a custom 2D graphics library; 3D graphics based
on the OpenGL ES 1.0 specification (hardware acceleration optional)

３４
  SQLite for structured data storage
 Media support for common audio, video, and still image formats (MPEG4, H.264,
MP3, AAC, AMR, JPG, PNG, GIF)
 GSM Telephony (hardware dependent)
 Bluetooth, EDGE, 3G, and WiFi (hardware dependent)
 Camera, GPS, compass, and accelerometer (hardware dependent)
 Rich development environment including a device emulator, tools for debugging,
memory and performance profiling, and a plugin for the Eclipse IDE
Linux Kernel

Android relies on Linux version 2.6 for core system services such as
 security
 memory management
 process management
 network stack
 driver model
 The kernel also acts as an abstraction layer between the hardware and the rest of the
software stack.

Android Runtime

 Android includes a set of core libraries that provides most of the functionality
available in the core libraries of the Java programming language.
 Every Android application runs in its own process, with its own instance of the
Dalvik virtual machine. Dalvik has been written so that a device can run multiple
VMs efficiently.
 The Dalvik VM executes files in the Dalvik Executable (.dex) format which is
optimized for minimal memory footprint.
 The Dalvik VM relies on the Linux kernel for underlying functionality such as
threading and low-level memory management.

３５
Libraries

Android includes a set of C/C++ libraries used by various components of the Android
system. These capabilities are exposed to developers through the Android application
framework.
 System C Library
 Media Library
 Surface Manager
 LibWebCore
 SGL
 3D libraries
 Free Type
 SQLite

Application Framework

 Being a open development platform, Android offers developers the ability to build
extremely rich and innovative applications.
 Developers have full access to the same framework APIs used by the core
applications.
 Views – used to build applications (lists, grid, buttons, text boxes and even
embeddable web browser)
 Content providers – enable applications to access data from other applications or
share their own data.
 Resource manager – provides access to non-code resources such as localized strings,
graphic and layout files.
 Notification manager – enables applications to display custom alerts in status bar
 Activity manager – manages lifecycle of applications and provides navigation
backstack
 Android ships with a set of core applications including an email client, SMS program,
calendar, maps, browser, contacts, and others.
 All applications are written using the Java programming language.

３６
 CHAPTER 8
ARCHITECTURE

３７
 

ARCHITECTURE

Fig.8.Architecture

Anatomy of an Android Application

There are four building blocks for an Android application:

 Activity - a single screen

 Broadcast Receiver- to execute in reaction to an external event(Phone Ring)

 Service - code that is long-lived and runs without a UI(Media Player)

 Content Provider - an application's data to be shared with other applications

３８
Android Building Blocks

These are the most important parts of the Android APIs:

 AndroidManifest.xml
o the control file-tells the system what to do with the top-level components
 Activities
o an object that has a life cycle-is a chunk of code that does some work.
 Views
o an object that knows how to draw itself to the screen
 Intents
o a simple message object that represents an "intention" to do something
 Notifications
o is a small icon that appears in the status bar(SMS messages)
o for alerting the user
 Services
o is a body of code that runs in the background

Development Tools

The Android SDK includes a variety of custom tools that help you develop mobile
applications on the Android platform. Three of the most significant tools are:
 Android Emulator -A virtual mobile device that runs on our computer -use to
design, debug, and test our applications in an actual Android run-time environment
 Android Development Tools Plugin -for the Eclipse IDE - adds powerful
extensions to the Eclipse integrated environment
 Dalvik Debug Monitor Service (DDMS) -Integrated with Dalvik -this tool let us
manage processes on an emulator and assists in debugging
 Android Asset Packaging Tool (AAPT) – Constructs the distributable Android
package files (.apk)
 Android Debug Bridge (ADB) – provides link to a running emulator. Can copy files
to emulator, install .apk files and run commands.

３９
Life cycle of activity

Fig.8.1.Life cycle of activity

４０
 CHAPTER 9

JAVA SERVER PAGE

４１
 JAVASERVER PAGES

JavaServer Pages (JSP) is a Java technology that allows software developers to

dynamically generate HTML, XML or other types of documents in response to a Web client
request. The technology allows Java code and certain pre-defined actions to be embedded
into static content.

JSPs are compiled into Java Servlets by a JSP compiler. A JSP compiler may
generate a servlet in Java code that is then compiled by the Java compiler, or it may generate
byte code for the servlet directly. JSPs can also be interpreted on-the-fly reducing the time
taken to reload changesJavaServer Pages (JSP) technology provides a simplified, fast way to
create dynamic web content. JSP technology enables rapid development of web-based
applications that are server- and platform-independent.

Architecture OF JSP:

４２
The Advantages of JSP:

 Active Server Pages (ASP). ASP is a similar technology from Microsoft. The
advantages of JSP are twofold. First, the dynamic part is written in Java, not Visual
Basic or other MS-specific language, so it is more powerful and easier to use. Second,
it is portable to other operating systems and non-Microsoft Web servers.
 Pure Servlets. JSP doesn't give you anything that you couldn't in principle do with a
servlet. But it is more convenient to write (and to modify!) regular HTML than to
have a zillion println statements that generate the HTML. Plus, by separating the look
from the content you can put different people on different tasks: your Web page
design experts can build the HTML, leaving places for your servlet programmers to
insert the dynamic content.
 Server-Side Includes (SSI). SSI is a widely-supported technology for including
externally-defined pieces into a static Web page. JSP is better because it lets you use
servlets instead of a separate program to generate that dynamic part. Besides, SSI is
really only intended for simple inclusions, not for "real" programs that use form data,
make database connections, and the like.
 JavaScript. JavaScript can generate HTML dynamically on the client. This is a
useful capability, but only handles situations where the dynamic information is based
on the client's environment. With the exception of cookies, HTTP and form
submission data is not available to JavaScript. And, since it runs on the client,
JavaScript can't access server-side resources like databases, catalogs, pricing
information, and the like.
 Static HTML. Regular HTML, of course, cannot contain dynamic information. JSP
is so easy and convenient that it is quite feasible to augment HTML pages that only
benefit marginally by the insertion of small amounts of dynamic data. Previously, the
cost of using dynamic data would preclude its use in all but the most valuable
instances.

４３
CHAPTER 10

SERVLETS

４４
 SERVLETS

The Java Servlet API allows a software developer to add dynamic content to a Web
server using the Java platform. The generated content is commonly HTML, but may be other
data such as XML. Servlets are the Java counterpart to non-Java dynamic Web content
technologies such as PHP, CGI and ASP.NET.

Servlets can maintain state across many server transactions by using HTTP cookies,
session variables or URL rewriting.The Servlet API, contained in the Java package hierarchy
javax.servlet, defines the expected interactions of a Web container and a servlet. A Web
container is essentially the component of a Web server that interacts with the servlets. The
Web container is responsible for managing the lifecycle of servlets, mapping a URL to a
particular servlet and ensuring that the URL requester has the correct access rights.

A Servlet is an object that receives a request and generates a response based on that
request. The basic servlet package defines Java objects to represent servlet requests and
responses, as well as objects to reflect the servlet's configuration parameters and execution
environment. The package javax.servlet.http defines HTTP-specific subclasses of the generic
servlet elements, including session management objects that track multiple requests and
responses between the Web server and a client.

Servlets may be packaged in a WAR file as a Web application.Servlets can be

generated automatically by JavaServer Pages (JSP), or alternately by template engines such
as WebMacro. Often servlets are used in conjunction with JSPs in a pattern called "Model 2",
which is a flavor of the model-view-controller pattern.Servlets are Java technology's answer
to CGI programming. They are programs that run on a Web server and build Web pages.
Building Web pages on the fly is useful (and commonly done) for a number of reasons:

４５
  The Web page is based on data submitted by the user. For example the results pages
from search engines are generated this way, and programs that process orders for e-
commerce sites do this as well.
 The data changes frequently. For example, a weather-report or news headlines page
might build the page dynamically, perhaps returning a previously built page if it is
still up to date.
 The Web page uses information from corporate databases or other such sources. For
example, you would use this for making a Web page at an on-line store that lists
current prices and number of items in stock.

The Servlet Run-time Environment:

A servlet is a Java class and therefore needs to be executed in a Java VM by a service

we call a servlet engine. The servlet engine loads the servlet class the first time the servlet is
requested, or optionally already when the servlet engine is started. The servlet then stays loaded to
handle multiple requests until it is explicitly unloaded or the servlet engine is shut down.

Some Web servers, such as Sun's Java Web Server (JWS), W3C's Jigsaw and Gefion
Software's LiteWebServer (LWS) are implemented in Java and have a built-in servlet engine.
Other Web servers, such as Netscape's Enterprise Server, Microsoft's Internet Information
Server (IIS) and the Apache Group's Apache, require a servlet engine add-on module.
The add-on intercepts all requests for servlets, executes them and returns the
response through the Web server to the client. Examples of servlet engine add-ons are
Gefion Software's WAICoolRunner, IBM's WebSphere, Live Software's JRun and New
Atlanta's ServletExec.

All Servlet API classes and a simple servlet-enabled Web server are combined into
the Java Servlet Development Kit (JSDK), available for download at Sun's official Servlet
site .To get started with servlets I recommend that you download the JSDK and play around
with the sample servlets.

４６
Life Cycle OF Servlet

The Servlet lifecycle consists of the following steps:

1. The Servlet class is loaded by the container during start-up.

2. The container calls the init() method. This method initializes the servlet and must

be called before the servlet can service any requests. In the entire life of a servlet,

the init() method is called only once.

3. After initialization, the servlet can service client-requests. Each request is

serviced in its own separate thread. The container calls the service() method of

the servlet for every request. The service() method determines the kind of request

being made and dispatches it to an appropriate method to handle the request. The

developer of the servlet must provide an implementation for these methods. If a

request for a method that is not implemented by the servlet is made, the method

of the parent class is called, typically resulting in an error being returned to the

requester.

4. Finally, the container calls the destroy() method which takes the servlet out of

service. The destroy() method like init() is called only once in the lifecycle of a

Servlet.

４７
 CHAPTER 11

FEASABILITY STUDY

４８
 FEASIBILITY STUDY

Feasibility study is the test of a system proposal according to its workability, impact
on the organization, ability to meet user needs, and effective use of recourses. It focuses on
the evaluation of existing system and procedures analysis of alternative candidate system
cost estimates. Feasibility analysis was done to determine whether the system would be
feasible.
The development of a computer based system or a product is more likely plagued by
resources and delivery dates. Feasibility study helps the analyst to decide whether or not to
proceed, amend, postpone or cancel the project, particularly important when the project is
large, complex and costly.Once the analysis of the user requirement is complement, the
system has to check for the compatibility and feasibility of the software package that is
aimed at. An important outcome of the preliminary investigation is the determination that the
system requested is feasible.

Technical Feasibility:
The technology used can be developed with the current equipments and has the
technical capacity to hold the data required by the new system.

 This technology supports the modern trends of technology.

 Easily accessible, more secure technologies.

Technical feasibility on the existing system and to what extend it can support the proposed
addition.We can add new modules easily without affecting the Core Program. Most of parts
are running in the server using the concept of stored procedures.

４９
Operational Feasibility:

This proposed system can easily implemented, as this is based on JSP coding (JAVA)
& HTML .The database created is with MySql server which is more secure and easy to
handle. The resources that are required to implement/install these are available. The personal
of the organization already has enough exposure to computers. So the project is operationally
feasible.

Economical Feasibility:

Economic analysis is the most frequently used method for evaluating the effectiveness of
a new system. More commonly known cost/benefit analysis, the procedure is to determine
the benefits and savings that are expected from a candidate system and compare them with
costs. If benefits outweigh costs, then the decision is made to design and implement the
system. An entrepreneur must accurately weigh the cost versus benefits before taking an
action. This system is more economically feasible which assess the brain capacity with quick
& online test. So it is economically a good project.

５０
CHAPTER 12

JAVA

５１
 JAVA (programming language)

Java is a programming language originally developed by James Gosling at Sun

Microsystems (which is now a subsidiary of Oracle Corporation) and released in 1995 as a
core component of Sun Microsystems' Java platform. The language derives much of its
syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java
applications are typically compiled to bytecode (class file) that can run on any Java Virtual
Machine (JVM) regardless of computer architecture. Java is general-purpose, concurrent,
class-based, and object-oriented, and is specifically designed to have as few implementation
dependencies as possible. It is intended to let application developers "write once, run
anywhere". Java is considered by many as one of the most influential programming
languages of the 20th century, and widely used from application software to web application.

The original and reference implementation Java compilers, virtual machines, and class
libraries were developed by Sun from 1995. As of May 2007, in compliance with the
specifications of the Java Community Process, Sun relicensed most of their Java
technologies under the GNU General Public License. Others have also developed alternative
implementations of these Sun technologies, such as the GNU Compiler for Java and GNU
Classpath

J2EE application

A J2EE application or a Java 2 Platform Enterprise Edition application is any deployable

unit of J2EE functionality. This can be a single J2EE module or a group of modules
packaged into an EAR file along with a J2EE application deployment descriptor. J2EE
applications are typically engineered to be distributed across multiple computing tiers.

Enterprise applications can consist of the following:

 EJB modules (packaged in JAR files);

 Web modules (packaged in WAR files);

 connector modules or resource adapters (packaged in RAR files);

 Session Initiation Protocol (SIP) modules (packaged in SAR files);

５２
 application client modules;

 Additional JAR files containing dependent classes or other components required by

the application;

 Any combination of the above.

Servlet

Java Servlet technology provides Web developers with a simple, consistent

mechanism for extending the functionality of a Web server and for accessing existing
business systems. Servlets are server-side Java EE components that generate responses
(typically HTML pages) to requests (typically HTTP requests) from clients. A servlet can
almost be thought of as an applet that runs on the server side—without a face.

// Hello.java
import java.io.*;
import javax.servlet.*;

public class Hello extends GenericServlet {

public void service(ServletRequest request, ServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html");
final PrintWriter pw = response.getWriter();
pw.println("Hello, world!");
pw.close();
}
}

The import statements direct the Java compiler to include all of the public classes and
interfaces from the java.io and javax.servlet packages in the compilation.

５３
The Hello class overrides the service(ServletRequest, ServletResponse) method defined by
the Servlet interface to provide the code for the service request handler. The service() method
is passed a ServletRequest object that contains the request from the client and a
ServletResponse object used to create the response returned to the client. The service()
method declares that it throws the exceptions ServletException and IOException if a problem
prevents it from responding to the request.

The setContentType(String) method in the response object is called to set the MIME content
type of the returned data to "text/html". The getWriter() method in the response returns a
PrintWriter object that is used to write the data that is sent to the client. The println(String)
method is called to write the "Hello, world!" string to the response and then the close()
method is called to close the print writer, which causes the data that has been written to the
stream to be returned to the client.

５４
CHAPTER 13

TESTING

５５
 TESTING

The various levels of testing are:

1. White Box Testing
2. Black Box Testing
3. Unit Testing
4. Functional Testing
5. Performance Testing
6. Integration Testing
7. Objective
8. Integration Testing
9. Validation Testing
10. System Testing
11. Structure Testing
12. Output Testing
13. User Acceptance Testing

White Box Testing

 Execution of every path in the program.

Black Box Testing

 Exhaustive input testing is required to find all errors.

Unit Testing
 Unit testing, also known as Module Testing, focuses verification efforts on

the module. The module is tested separately and this is carried out at the

programming stage itself.

 Unit Test comprises of the set of tests performed by an individual

programmer before integration of the unit into the system.

 Unit test focuses on the smallest unit of software design- the software

component or module.

５６
  Using component level design, important control paths are tested to uncover

errors within the boundary of the module.

 Unit test is white box oriented and the step can be conducted in parallel for

multiple components.

Functional Testing:
 Functional test cases involve exercising the code with normal input values for
which the expected results are known, as well as the boundary values

Objective:
 The objective is to take unit-tested modules and build a program structure that
has been dictated by design.

Performance Testing:
 Performance testing determines the amount of execution time spent in
various parts of the unit, program throughput, and response time and device
utilization of the program unit. It occurs throughout all steps in the testing
process.

Integration Testing:
 It is a systematic technique for constructing the program structure while at

the same time conducting tests to uncover errors associated with in the

interface.

 It takes the unit tested modules and builds a program structure.

 All the modules are combined and tested as a whole.

 Integration of all the components to form the entire system and a overall

testing is executed.

５７
Validation Testing:
 Validation test succeeds when the software functions in a manner that can be

reasonably expected by the client.

 Software validation is achieved through a series of black box testing which

confirms to the requirements.

 Black box testing is conducted at the software interface.

 The test is designed to uncover interface errors, is also used to demonstrate

that software functions are operational, input is properly accepted, output are

produced and that the integrity of external information is maintained.

System Testing:
 Tests to find the discrepancies between the system and its original objective,
current specifications and system documentation.

Structure Testing:
 It is concerned with exercising the internal logic of a program and traversing
particular execution paths.

Output Testing:
 Output of test cases compared with the expected results created during design

of test cases.

 Asking the user about the format required by them tests the output generated

or displayed by the system under consideration.

 Here, the output format is considered into two was, one is on screen and

another one is printed format.

 The output on the screen is found to be correct as the format was designed in

the system design phase according to user needs.

 The output comes out as the specified requirements as the user’s hard copy.

５８
User acceptance Testing:
 Final Stage, before handling over to the customer which is usually carried out

by the customer where the test cases are executed with actual data.

 The system under consideration is tested for user acceptance and constantly

keeping touch with the prospective system user at the time of developing and

making changes whenever required.

 It involves planning and execution of various types of test in order to

demonstrate that the implemented software system satisfies the requirements

stated in the requirement document.

Two set of acceptance test to be run:

1. Those developed by quality assurance group.

2. Those developed by customer.

５９
 CHAPTER 14

METHODOLOGY

６０
 METHODOLOGY
Waterfall Approach
While the Waterfall Model presents a straightforward view of the software life cycle,
this view is only appropriate for certain classes of software development. Specifically, the
Waterfall Model works well when the software requirements are well understood (e.g.,
software such as compilers or operating systems) and the nature of the software development
involves contractual agreements. The Waterfall Model is a natural fit for contract-based
software development since this model is document driven; that is, many of the products
such as the requirements specification and the design are documents. These documents then
become the basis for the software development contract.
There have been many waterfall variations since the initial model was introduced by
Winston Royce in 1970 in a paper entitled: “managing the development of large software
systems: concepts and techniques”. Barry Boehm, developer of the spiral model (see below)
modified the waterfall model in his book Software Engineering Economics (Prentice-Hall,
1987). The basic differences in the various models is in the naming and/or order of the
phases.
The basic waterfall approach looks like the illustration below. Each phase is done in a
specific order with its own entry and exit criteria and provides the maximum in separation of
skills, an important factor in government contracting.

Fig.14.1.Waterfall Approach

６１
Example of a typical waterfall approach
While some variations on the waterfall theme allow for iterations back to the previous phase,
“In practice most waterfall projects are managed with the assumption that once the phase is
completed, the result of that activity is cast in concrete. For example, at the end of the design
phase, a design document is delivered. It is expected that this document will not be updated
throughout the rest of the development. You cannot climb up a waterfall.” (Murray Cantor,
Object-oriented project management with UML, John Wiley, 1998)
The waterfall is the easiest of the approaches for a business analyst to understand and work
with and it is still, in its various forms, the operational SLC in the majority of US IT shops.
The business analyst is directly involved in the requirements definition and/or analysis
phases and peripherally involved in the succeeding phases until the end of the testing phase.
The business analyst is heavily involved in the last stages of testing when the product is
determined to solve the business problem. The solution is defined by the business analyst in
the business case and requirements documents. The business analyst is also involved in the
integration or transition phase assisting the business community to accept and incorporate
the new system and processes.

V Model
The "V" model (sometimes known as the "U" model) reflects the approach to
systems development where in the definition side of the model is linked directly to the
confirmation side. It specifies early testing and preparation of testing scenarios and cases
before the build stage to simultaneously validate the definitions and prepare for the test
stages.It is the standard for German federal government projects and is considered as much a
project management method as a software development approach.
“The V Model, while admittedly obscure, gives equal weight to testing rather than treating it
as an afterthought. Initially defined by the late Paul Rook in the late 1980s, the V was
included in the U.K.'s National Computing Centre publications in the 1990s with the aim of
improving the efficiency and effectiveness of software development. It's accepted in Europe
and the U.K. as a superior alternative to the waterfall model; yet in the U.S., the V Model is
often mistaken for the waterfall…“In fact, the V Model emerged in reaction to some
waterfall models that showed testing as a single phase following the traditional development
phases of requirements analysis, high-level design, detailed design and coding. The waterfall
model did considerable damage by supporting the common impression that testing is merely
a brief detour after most of the mileage has been gained by mainline development activities.

６２
Many managers still believe this, even though testing usually takes up half of the project
time.” (Goldsmith and Graham, “The Forgotten Phase”, Software development, July
2002)As shown below, the model is the shape of the development cycle (a waterfall wrapped
around) and the concept of flow down and across the phases. The V shows the typical
sequence of development activities on the left-hand (downhill) side and the corresponding
sequence of test execution activities on the right-hand (uphill) side.

Concept of Acceptance
operations System test

System System
requirements test

Subsystem Subsystem
requirements test

Subsystem Integration
design Subsystem test

Unit Unit
design test

Code

Unit
Fig.14.2 V Model
Example of a typical V Model (IEEE)
The primary contribution the V Model makes is this alignment of testing and specification.
This is also an advantage to the business analyst who can use the model and approach to
enforce early consideration of later testing. The V Model emphasizes that testing is done
throughout the SDLC rather than just at the end of the cycle and reminds the business analyst
to prepare the test cases and scenarios in advance while the solution is being defined.
The business analyst’s role in the V Model is essentially the same as the waterfall. The
business analyst is involved full time in the specification of the business problem and the
confirmation and validation that the business problem has been solved which is done at
acceptance test. The business analyst is also involved in the requirements phases and
advises the system test stage which is typically performed by independent testers – the
quality assurance group or someone other than the development team.

６３
CHAPTER 15

SOURCE CODE

６４
 SOURCE CODE
Web service:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package com.networkqos;

import com.commondb.Common_DB;
import java.io.File;
import java.io.FileFilter;
import java.io.FilenameFilter;
import java.net.URI;
import java.net.URL;
import java.sql.ResultSet;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.WebParam;
/**
*
* @author santhosh.t
*/
@WebService(serviceName = "NewWebService")
public class NewWebService {

/**
* Web service operation
*/
@WebMethod(operationName = "signin")
public String signin(@WebParam(name = "username") String username,
@WebParam(name = "password") String password) {

６５
 try {
Common_DB cd=new Common_DB();
ResultSet rs=Common_DB.LoginCheck("psjav05", "login","username","password",
username, password);
if(rs.next()) {
return "success";
}
else {
return "username or password is invalid";
}
} catch (Exception ex) {
Logger.getLogger(NewWebService.class.getName()).log(Level.SEVERE, null, ex);
return "server temporarily not available";
}
}

/**
* Web service operation
*/
@WebMethod(operationName = "signup")
public String signup(@WebParam(name = "username") String username,
@WebParam(name = "password") String password, @WebParam(name = "email") String
email) {
try {
Common_DB cd=new Common_DB();
int rs=Common_DB.InsertTable("psjav05", "INSERT INTO
login(username,password,email) VALUES('"+username+"','"+password+"','"+email+"')");
if(rs>0) {
return "success";
}
else {
return "username is already available";
}
} catch (Exception ex) {

６６
 Logger.getLogger(NewWebService.class.getName()).log(Level.SEVERE, null, ex);
return "server temporarily not available";
}

/**
* Web service operation
*/
@WebMethod(operationName = "mobileinfo")
public String mobileinfo(@WebParam(name = "bandwidth") String bandwidth,
@WebParam(name = "networkname") String networkname, @WebParam(name =
"phonetype") String phonetype, @WebParam(name = "simstate") String simstate,
@WebParam(name = "networktype") String networktype,@WebParam(name = "osversion")
String osversion, @WebParam(name="username") String username) {
try {
Common_DB cd=new Common_DB();
int rs=Common_DB.UpdateTable("psjav05", "UPDATE login SET
bandwidth='"+bandwidth+"',networkname='"+networkname+"',phonetype='"+phonetype+"',
simstate='"+simstate+"',networktype='"+networktype+"',osversion='"+osversion+"' WHERE
username='"+username+"'");

if(rs>0) {

File file=new File("E:\\NetworkQoSService\\build\\web\\videos/");

// File[] files=file.listFiles(new FilenameFilter() {
//
// @Override
// public boolean accept(File dir, String name) {
// return name.toLowerCase().endsWith("mp4");
// }
// });
File[] files=file.listFiles();
String filenames="";

６７
 for(File filename : files) {
filenames+=filename.getName()+"@";
}
return filenames;
}
else {
return "Sorry unable to get mobile info";
}
} catch (Exception ex) {
Logger.getLogger(NewWebService.class.getName()).log(Level.SEVERE, null, ex);
return "server temporarily not available";
}

/**
* Web service operation
*/
@WebMethod(operationName = "Transcode")
public String Transcode(@WebParam(name = "filename") String
filename,@WebParam(name = "username") String username) {
try {
String filename1=null;
String formatname=null;
Common_DB cd=new Common_DB();
ResultSet rs=Common_DB.ViewParticularData("psjav05", "login", "username",
username);
if(rs.next()) {
int bandwidth=Integer.parseInt(rs.getString("bandwidth"));
String networktype=rs.getString("networktype");
String networkname=rs.getString("networkname");
String osversion=rs.getString("osversion");
String phonetype=rs.getString("phonetype");
if(osversion.startsWith("2.2")) {

６８
 filename1=filename.substring(0,filename.lastIndexOf("."));
formatname="3gp";
TransCoder.TransCode(filename, filename1,formatname , "libfaac", new
Integer(128000), 44100, 800000, 480, 360);
}
else if(filename.endsWith("3gp")){
filename1=filename;
}
else {
if(bandwidth<70) {
filename1=filename.substring(0,filename.lastIndexOf("."));
formatname="3gp";
TransCoder.TransCode(filename, filename1,formatname , "libfaac", new
Integer(128000), 44100, 800000, 176, 144);
}
else if(bandwidth>70 && 90>bandwidth) {
filename1=filename.substring(0,filename.lastIndexOf("."));
formatname="mp4";
TransCoder.TransCode(filename, filename1,formatname , "libfaac", new
Integer(200000), 65100, 3200000, 480, 360);
}
}
return filename1+"."+formatname;
}
else {
return "no file found";
}
}catch (Exception ex) {
Logger.getLogger(NewWebService.class.getName()).log(Level.SEVERE, null, ex);
return "error";
}
}
}

６９
Transcoder Code:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package com.networkqos;

import it.sauronsoftware.jave.*;
import java.io.File;
import java.util.logging.Level;
import java.util.logging.Logger;

/**
*
* @author santhosh.t
*/
public class TransCoder {
public static void TransCode(String sourcefile,String filename,String formatname,String
setCodec,Integer audioBitRate,Integer audioSamplingRate,Integer videoBitRate,int width,int
height ) {
try {
File source=new File("E:\\NetworkQoSService\\build\\web\\videos/"+sourcefile);
File target=new
File("E:\\NetworkQoSService\\build\\web\\videos1/"+filename+"."+formatname);
if(!(target.exists())) {
AudioAttributes aattrib=new AudioAttributes();
aattrib.setCodec(setCodec);
aattrib.setBitRate(new Integer(audioBitRate));
aattrib.setSamplingRate(new Integer(audioSamplingRate));
aattrib.setChannels(new Integer(2));
VideoAttributes vattrib=new VideoAttributes();
vattrib.setCodec("mpeg4");
vattrib.setBitRate(new Integer(videoBitRate));
vattrib.setFrameRate(new Integer(30));

７０
 vattrib.setSize(new VideoSize(width,height));
EncodingAttributes attrs = new EncodingAttributes();
attrs.setFormat(formatname);
attrs.setAudioAttributes(aattrib);
attrs.setVideoAttributes(vattrib);
Encoder encoder = new Encoder();
encoder.encode(source, target, attrs);
}
} catch (IllegalArgumentException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
} catch (InputFormatException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
} catch (EncoderException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
}
}
public static void main(String a[]) {
try {
File source=new File("E:/Wildlife.wmv");
File target=new File("E:/my.mp4");
AudioAttributes aattrib=new AudioAttributes();
aattrib.setCodec("libfaac");
aattrib.setBitRate(new Integer(256000));
aattrib.setSamplingRate(new Integer(65100));
aattrib.setChannels(new Integer(2));
VideoAttributes vattrib=new VideoAttributes();
vattrib.setCodec("mpeg4");
vattrib.setBitRate(new Integer(3200000));
vattrib.setFrameRate(new Integer(18));
vattrib.setSize(new VideoSize(620, 480));
EncodingAttributes attrs = new EncodingAttributes();
attrs.setFormat("mp4");
attrs.setAudioAttributes(aattrib);
attrs.setVideoAttributes(vattrib);

７１
 Encoder encoder = new Encoder();
encoder.encode(source, target, attrs);
} catch (IllegalArgumentException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
} catch (InputFormatException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
} catch (EncoderException ex) {
Logger.getLogger(TransCoder.class.getName()).log(Level.SEVERE, null, ex);
}

}
}

Android Code:
package com.networkqos;
import android.os.AsyncTask;
import android.os.Build;
import android.os.Bundle;
import android.app.Activity;
import android.app.ProgressDialog;
import android.content.Intent;
import android.telephony.PhoneStateListener;
import android.telephony.ServiceState;
import android.telephony.TelephonyManager;
import android.view.Menu;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
import android.widget.ProgressBar;
import android.widget.TextView;
import android.widget.Toast;
public class MainActivity extends Activity {
/*

７２
 * variable declaration
*/
static String
urlString,bandwidth,phonetype,simstate,networkname,networktype,osversion;
static TextView bw,ss,nt,pt,nn,uname;
static Button bn;
static ProgressBar pb;
static ProgressDialog pDialog;
static int icon;
static String username;
/*
* SIM state constants
*/
public static final String SIM_ABSENT = "Absent";
public static final String SIM_READY = "Ready";
public static final String SIM_PIN_REQUIRED = "PIN required";
public static final String SIM_PUK_REQUIRED = "PUK required";
public static final String SIM_NETWORK_LOCKED = "Network locked";
public static final String SIM_UNKNOWN = "Unknown";
/*
* Network type constants
*/
public static final String NETWORK_CDMA = "CDMA: Either IS95A or IS95B (2G)";
public static final String NETWORK_EDGE = "EDGE (2.75G)";
public static final String NETWORK_GPRS = "GPRS (2.5G)";
public static final String NETWORK_UMTS = "UMTS (3G)";
public static final String NETWORK_EVDO_0 = "EVDO revision 0 (3G)";
public static final String NETWORK_EVDO_A = "EVDO revision A (3G - Transitional)";
public static final String NETWORK_EVDO_B = "EVDO revision B (3G - Transitional)";
public static final String NETWORK_1X_RTT = "1xRTT (2G - Transitional)";
public static final String NETWORK_HSDPA = "HSDPA (3G - Transitional)";
public static final String NETWORK_HSUPA = "HSUPA (3G - Transitional)";
public static final String NETWORK_HSPA = "HSPA (3G - Transitional)";
public static final String NETWORK_IDEN = "iDen (2G)";

７３
 public static final String NETWORK_LTE = "LTE (4G)";
public static final String NETWORK_EHRPD = "EHRPD (3G)";
public static final String NETWORK_HSPAP = "HSPAP (3G)";
public static final String NETWORK_UNKOWN = "Unknown";
/*
* Phone type constants
*/
public static final String PHONE_CDMA = "CDMA";
public static final String PHONE_GSM = "GSM";
public static final String PHONE_SIP = "SIP";
public static final String PHONE_NONE = "No radio";
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
pb=(ProgressBar)findViewById(R.id.progressBar2);
bn=(Button)findViewById(R.id.bt);
bw=(TextView)findViewById(R.id.bandwidth);
pt=(TextView)findViewById(R.id.phone_type);
nt=(TextView)findViewById(R.id.network_type);
ss=(TextView)findViewById(R.id.sim_state);
nn=(TextView)findViewById(R.id.network_name);
uname=(TextView)findViewById(R.id.uname);
username=getIntent().getStringExtra("username");
uname.setText("welcome "+username+",");
icon=R.drawable.ic_launcher;
bn.setOnClickListener(new OnClickListener() {
@Override
public void onClick(View v) {
// Get the telephony system service to find out network details
final TelephonyManager tm = (TelephonyManager)
getSystemService(TELEPHONY_SERVICE);

// Update text views with readable values.

７４
 updateViews(tm)
// Since these attributes can change, we will register a
// {@code PhoneStateListener} to listen for these changes and
// update the view.
tm.listen(new PhoneStateListener() {
@Override
public void onServiceStateChanged(ServiceState serviceState) {
// Update our TextViews
updateViews(tm);
}
@Override
public void onDataConnectionStateChanged(int state) {
// A change in data connection state may be due to availability
// of a different network type
updateViews(tm);
}

}, PhoneStateListener.LISTEN_SERVICE_STATE |
PhoneStateListener.LISTEN_DATA_CONNECTION_STATE);

// calculate bandwidth
Downloadfile df=new Downloadfile();
df.execute();});}

// @Override
// protected void onResume() {
// super.onResume();
// final TelephonyManager tm = (TelephonyManager)
getSystemService(TELEPHONY_SERVICE);
//
// // Update text views with readable values.
// updateViews(tm);
// }

７５
 @Override
public boolean onCreateOptionsMenu(Menu menu) {
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.main, menu);
return true;
}
/**
* Update text views with telephony attributes.
*/
private final void updateViews(TelephonyManager tm) {

// The telephony system service returns integer constants for various

// telephony attributes.
simstate=tm.getSimSerialNumber();
phonetype=mapDeviceTypeToName(tm.getPhoneType());
networkname=tm.getNetworkOperatorName();
networktype= mapNetworkTypeToName(tm.getNetworkType());
osversion=Build.VERSION.RELEASE;
ss.setText("SIM State: " + simstate);
nt.setText("Network Type: " +networktype);
pt.setText("Phone Type: " + phonetype);
nn.setText("Network Operator: " +networkname);

/**
* Returns a string describing the current SIM state.
*/
private static String mapSimStateToName(int simState) {
switch (simState) {
case TelephonyManager.SIM_STATE_ABSENT:
return SIM_ABSENT;
case TelephonyManager.SIM_STATE_READY:
return SIM_READY;

７６
 case TelephonyManager.SIM_STATE_PIN_REQUIRED:
return SIM_PIN_REQUIRED;
case TelephonyManager.SIM_STATE_PUK_REQUIRED:
return SIM_PUK_REQUIRED;
case TelephonyManager.SIM_STATE_NETWORK_LOCKED:
return SIM_NETWORK_LOCKED;
case TelephonyManager.SIM_STATE_UNKNOWN:
return SIM_UNKNOWN;
default:
// shouldn't happen.
return null;
}
}

/**
* Returns a string indicating the phone radio type.
*/
private static String mapDeviceTypeToName(int device) {

switch (device) {
case TelephonyManager.PHONE_TYPE_GSM:
return PHONE_GSM;

case TelephonyManager.PHONE_TYPE_NONE:
return PHONE_NONE;
default:
// shouldn't happen.
return null;
}
}

/**
* Returns a string describing the network type.
*/

７７
 public static String mapNetworkTypeToName(int networkType) {

switch (networkType) {
case TelephonyManager.NETWORK_TYPE_EDGE:
return NETWORK_EDGE;
case TelephonyManager.NETWORK_TYPE_GPRS:
return NETWORK_EDGE;
case TelephonyManager.NETWORK_TYPE_UMTS:
return NETWORK_UMTS;

// case TelephonyManager.NETWORK_TYPE_HSPAP:
// return NETWORK_HSPAP;
case TelephonyManager.NETWORK_TYPE_UNKNOWN:
default:
return NETWORK_UNKOWN;
}
}
class Downloadfile extends AsyncTask<String, Void, Void> {
String list=null;
@Override
protected Void doInBackground(String... params) {
//urlString="http://llc.mtsac.edu/handouts/powerpoint.pdf";

urlString="http://download.wavetlan.com/SVV/Media/HTTP/H264/Talkinghead_Me
dia/H264_test3_Talkingheadclipped_mp4_480x360.mp4";
bandwidth=new Bandwidth().getBandwidth(urlString);

list=CallServices.getVideosFromMobileInfo(bandwidth,phonetype,networkname,sim
state,networktype,osversion,username, "mobileinfo");
return null;
}

@SuppressWarnings("deprecation")

７８
 @Override
protected void onPostExecute(Void result) {
bw.setText("Network Bandwidth: "+bandwidth+" kbps");

pb.setVisibility(View.INVISIBLE);

pDialog = new ProgressDialog(MainActivity.this);

// Set progressbar title
pDialog.setTitle("Network QoS");
pDialog.setIcon(icon);
// Set progressbar message
pDialog.setMessage("successfully retrived the list");
pDialog.setIndeterminate(false);
pDialog.setCancelable(false);
pDialog.setButton("ok", new
android.content.DialogInterface.OnClickListener(){

@Override
public void onClick(android.content.DialogInterface arg0, int
arg1) {
Intent intent1=new
Intent(getBaseContext(),VideoList.class);
intent1.putExtra("list", list);
intent1.putExtra("username", username);
startActivity(intent1);
}
});

// Show progressbar
pDialog.show();

@Override

７９
 protected void onPreExecute() {
pb.setVisibility(View.VISIBLE);

@Override
protected void onProgressUpdate(Void... values) {

}
}

８０
CHAPTER 16

SCREENSHOTS

８１
SCREENSHOTS

８２
８３
８４
８５
８６
８７
８８
８９
 CHAPTER 17
CONCLUSION

９０
 CONCLUSION

For mobile multimedia streaming services, how to provide appropriate multimedia

files according to the network and hardware devices is an interesting subject. In this study, a
set of adaptive networks and a device aware QoS approach for interactive mobile streaming
was proposed. The DNEM and DBPM were used for the prediction of network and hardware
features, and the communication frequency and SVC multimedia streaming files most
suitable for the device environment were determined according to these two modules. In the
experiment, the overall prototype architecture was realized and an experimental analysis was
carried out. The experimental data proved that the method could maintain a certain level of
multimedia service quality for dynamic network environments and ensure smooth and
complete multimedia streaming services. Cloud services may accelerate research on SVC
coding in the future. this study presented a network and device-aware Quality of Service
(QoS) approach that provides multimedia data suitable for a terminal unit environment via
interactive mobile streaming services, further considering the overall network environment
and adjusting the interactive transmission frequency and the dynamic multimedia trans
coding, to avoid the waste of bandwidth and terminal power. Finally, this study realized a
prototype of this architecture to validate the feasibility of the proposed method.

Future Work
In this work, we just consider a singleflow scenario and ignore the interference from
the other flows as well as the competitive bidding for spectrum usage from the other flows.
In a CRN with multiflows, the CR source nodes need to develop sophisticated bidding
strategies considering the competition from the peer flows, and the SSP should jointly
consider the cross-layer factors and the bidding values to determine the sharing of
theharvested spectrum.

９１
 REFERENCES

[1] M. Armbrust, A. Fox, R. Griffith, A. D. Joseph,R.Katz, A. Konwinski, G. Lee, D.

Patterson, A. Rabkin, I. Stoica, and M. Zaharia, “A view of cloud computing,” Commun.
ACM, vol. 53, p. 508, Apr. 2010.
[2] M. F. Tan and X. Su, “Media cloud:When media revolution meets rise of cloud
computing,” in Proc. IEEE 6th Int. Symp. Service Oriented Syst. Eng., 2011, pp. 251–261.
[3] W. Zhu, C. Luo, J. F. Wang, and S. P. Li, “Multimedia cloud computing,” IEEE Signal
Process. Mag., vol. 28, no. 3, pp. 59–69, 2011.
[4] G. Q. Hu, W. P. Tay, and Y. G. Wen, “Cloud robotics: Architecture, challenges and
applications,” IEEE Network, Special Issue onMachine and Robotic Networking, vol. 26, no.
3, pp. 21–28, May-Jun. 2012.
[5] S. Ferretti, V. Ghini, F. Panzieri, and E. Turrini, “Seamless support of multimedia
distributed applications through a cloud,” in Proc. IEEE 3rd Int. Conf. Cloud Comput.
(CLOUD), 2010, pp. 548–549.

９２