Clouds

Page 1 of 11

Clouds

By | December 2012
Page 1 of 11
1. INTRODUCTION
In recent years, weak mobile devices such as smartphones, mobile Internet devices, and netbooks have become popular. Examples include the Apple iPhone [2], Google Android Phone [1, 7], RIM Blackberry Phone [3], and netbooks from several vendors. Tablets are also gaining attraction thanks to Apple’s new iPad [6]. Moreover, weak devices are embedded in vehicles and TVs (e.g., Ford SYNC [4] and Google TV [5]). These devices support exciting new applications that provide a connected Internet experience to users. Now users manage their Facebook and Twitter notifications; capture, edit, and upload photos and videos; handle their finances; and play computer games. Users also have growing demand for running more resource-demanding applications, the kinds of applications they run on laptops or desktops, such as rich media applications using diverse inputs like cameras and sensors. Examples include photo and video editing and synthesis, 3D modeling for constructing avatars, scene recognition, object recognition, image search, and augmented reality [12, 13, 18, 23]. Currently these applications running on weak devices are structured such that they are statically partitioned between the weak device and a server running in the cloud. Two representative application partitions are as follows. First, most of an application’s processing is done at the server(s) in the

cloud, and the end-user device runs simple tasks such as UIs, acting like a thin client. For example, Facebook and Tweeter clients belong to this category. Second, most of an application’s processing is performed at the client as exhibited in interactive, graphics-intensive games. These different partitions incur different costs (e.g., execution time, energy consumption, etc.). However, partitioning applications statically does not provide optimal user experience as more and more applications are used in diverse environments and inputs. That is, there is no single partitioning that fits all due to...