1 / 56

A Survey of Mobile Cloud Computing: Architecture, Applications, and Approaches

A Survey of Mobile Cloud Computing: Architecture, Applications, and Approaches. Introduction. Mobile devices Mobile computing(MC) Challenges with resources and communication Cloud computing(CC) MC + CC = Mobile cloud computing(MCC) Definition, architecture, advantages

amie
Download Presentation

A Survey of Mobile Cloud Computing: Architecture, Applications, and Approaches

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A Survey of Mobile Cloud Computing: Architecture, Applications, and Approaches

  2. Introduction Mobile devices Mobile computing(MC) Challenges with resources and communication Cloud computing(CC) MC + CC = Mobile cloud computing(MCC) Definition, architecture, advantages Use of MCC in applications Issues in MCC and how to address them Future research A Survey of Mobile Cloud Computing

  3. What is Mobile Cloud Computing? Infrastructure Storage and computing Centralized computing platform Access for a broad range of users Less demanding for mobile device A Survey of Mobile Cloud Computing

  4. Architecture of MCC A Survey of Mobile Cloud Computing

  5. Cloud Architecture A Survey of Mobile Cloud Computing

  6. Advantages of MCC Extended battery lifetime Data storage capacity Processing power Improving reliability Dynamic provisioning Scalability Multitenancy Ease of integration A Survey of Mobile Cloud Computing

  7. Applications of Mobile Cloud Computing Mobile commerce Business model Three classes: Finance, Advertising and Shopping Various challenges Mobile learning Electronic learning Limitation in traditional m-learning applications A Survey of Mobile Cloud Computing

  8. Applications of Mobile Cloud Computing Mobile healthcare Decrease treatment time Access medical records Patient monitoring/health-aware Coordinate resources Mobile gaming Offload game engine computations MAUI Other practical applications A Survey of Mobile Cloud Computing

  9. Issues and Approach of MCC Integrating two technologies Low bandwidth Availability Heterogeneity A Survey of Mobile Cloud Computing

  10. Issues and Approach of MCC Computing offloading In static environment Efficiency of offloading Partitioning Components in java program Data size and execution time Online statistics In dynamic environment Re-offload failed subtasks Three step to application structuring Three step using MAUI with code portability A Survey of Mobile Cloud Computing

  11. Issues and Approach of MCC Security Mobile users Mobile applications Privacy A Survey of Mobile Cloud Computing

  12. Issues and Approach of MCC Security Data on clouds Integrity Authentication Digital rights management A Survey of Mobile Cloud Computing

  13. Issues and Approach of MCC Enhancing the efficiency of data access A Survey of Mobile Cloud Computing

  14. Issues and Approach of MCC Enhancing the efficiency of data access Pocket cloudlet Random file structure A Survey of Mobile Cloud Computing

  15. Issues and Approach of MCC Context-aware mobile cloud services Mobile Service Clouds Service cloud paradigm Service gateway Framework for providing context-aware mobile services Based on algorithm Consider several contexts A Survey of Mobile Cloud Computing

  16. Issues and Approach of MCC A Survey of Mobile Cloud Computing

  17. Open issue and future research directions Low bandwidth Dramatic increase of mobile and cloud user 4G Network and Femto cell might be promising solution to overcome bandwidth limitation 4G network Significantly increases bandwidth capacity 100 Mbits/s(LTE advanced standard) and 128 Mbits/s (WirelessMAN-advanced), 14.4Mbits/s(3G) Improves mobile coverage area,smoothering quicker handoff ,varied services.

  18. Open issue and future research directions • Femtocell • Small cellular base station (used in a small area) • Hay Systems Ltd (HSL) develops service to combine femtocell and CC, provide highly secure, economical and scalable network • Connects via internet to cloud to gain access to their operator networks • Mobile operators connect with cloud enabling their subscribers to gain access to their network when using femtocell connected to the cloud • Coverage is likely to be consistent and has capacity to limit the how many people are permitted to log on.

  19. Open issue and future research directions • Network access management • Improves bandwidth coverage besides the link performance • Cognitive radio is a possible solution • Increases the efficiency of the spectrum utilization • Allow unlicensed user to use spectrum allocated for licensed users. (solves spectrum scarcity saves millions dollars of network provider) • Based on recognition of radio resource availability in heterogeneous wireless environment • MCC user should be able to perceive the radio availability without interference with traditional services.

  20. Open issue and future research directions • Quality of service • Congestion due to limited wireless bandwidth, network disconnection, signal attenuation caused by user’s mobility (degrades QoS significantly) • Clone cloud and cloudlets might be promising solution to reduce network delay • Clone cloud • Brings power of CC on mobile • Mechanism to clone the entire set of data and app on to the cloud and communicate with copy of own • Execute operation on the clone and re-integrate the result back to the phone.

  21. Open issue and future research directions • Quality of service • Cloudlets • Resource enriched computer or cluster of computer well connected to internet • Can be used by nearby mobile device • If user do not want to offload on cloud can use cloudlets and avoid communication delay

  22. Open issue and future research directions • Pricing • Using MCC service involves both MSP and CSP • How the price will be divided among different entities • Example user playing game (gaming application) • Has to pay game service provider, MSP and CSP • How the price paid by game player is divided among them • The business model should be carefully designed for pricing and revenue sharing

  23. Open issue and future research directions • Standard Interface • Mobile user interact and communicate with cloud via web interface which is not ideal way • The HTML 5 can be promising solution • HTML 5 Websockets offers good interface • Extensive performance evaluation and feasibility study is required to ensure it works well with MCC

  24. Open issue and future research directions • Service convergence • Single cloud may not meet users demand • Mobile user can utilize a multiple clouds in unified fashion • Sky computing is a potential solution • Sky cloud computing will give platform for user to use cross-cloud computing and use mobile services and application • To offer service to user in unified way the service integration need to be explored

  25. Cloud Structure with mobile wireless device • Cloud is brought closer to the users to avoid communication latency of Internet • Best leverage cloud Resource to execute mobile applications

  26. Cloud Structure with mobile wireless device • Local cloud and Back–end cloud • LTE Base stations or WiFi access points for accessing cloud • Back-end cloud facility of servers interconnected with wire links • Access to Back –end cloud from mobile client via wireless link • Small sized local cloud placed at point of wire less access

  27. Cloud Structure with mobile wireless device • Local cloud and Back-end cloud connected and controlled by same provider • Vm migration to balance the load at each server

  28. Lifetime of a Task in the Cloud • Total time spent by task in the cloud • Stages of the task • Upload • Task Assignment • Execution • Migration • Download

  29. The state evolution of a task during its lifetime

  30. Lifetime of a Task in the Cloud • Upload • When new task generated • Source code and input data uploaded to cloud via wireless link betn user and corresponding point of wireless access • Vm initialization • Either executed in the local cloud or forwarded over internet to back-end cloud

  31. Lifetime of a Task in the Cloud • Task Assignment • Once data uploaded to data center • Local dispatcher assigns server for the task • Vm is created for task and assigned to physical server • Execution • Real processing within the cloud • New vmintialized for task and immediate execution

  32. Lifetime of a Task in the Cloud • Migration • Transfer of Vm from current server to new one • Occur multiple time • Accompanying data volume transferred for new vminitialization • Download • Retrieval of the final result by mobile user • Once computation finished result downloaded by user immediately using its current technology • Host not in wireless range of mobile user, data transferred to accessible server • die(); // kernel oops

  33. Issues on Task scheduling and migration in the cloud • Task placement and performed by Vm manager • Task placement helps to balance load at each server to some extent • Cannot guarantee the Quality of Service (QoS) due highly volatile cloud • Task migration a promising option provides fine tuned means of balancing load throughout the system • But Vm migration induces delay (should be accounted) • Stop execution of vm at current server • Move accompanying data to new server • Initialize new vm • Cloud providers faces inherent tradeoff in selecting optimal migration strategy • Optimization of clients QoE, reducing execution time • Reduced execution time better for computing with other providers rises larger residual processing capacity • Fully exploit the task consolidation to reduce operating cost(turning off the underutilized servers.)

  34. Issues on Task scheduling and migration in the cloud • When to migrate and where? • QoS is being violated for long time • Execution time at new server is smaller than current • Information about the current server and tentative server is required • Efficient Vm Scheduling for accurate prediction of multi tenancy cost. • Prior knowledge of resource pattern for each task is required for modeling contention • Extensive profiling of different types of cloud; characterization through profiling impractical as significantly diverse task exists in cloud • Multi tenancy cost estimated through online measurement when task being executed (suggestion)

  35. Issues on Task scheduling and migration in the cloud • The task generate new data as time passes • The Vm characterized by time varying volume of accompanying data • May increase decrease or remain same over time • Video compression , complex scientific complex calculation • The challenge stem form • Highly dynamic nature, user mobility, continuously evolving population at servers • Time varying processing capacity of server due to multitenancy, evolving accompanying data of each vm

  36. Challenges in Designing efficient Migration Mechanism for the cloud • Workload uncertainty • Unpredictability of multitenancy effects • Unknown evolution of accompanying data volume • Time varying network link capacity • Partial availability of cloud related information

  37. Modes of Task Migration • Centralized Migration policy • Server Initiated Migration: Towards reducing the complexity of migration decision • Task-Autonomic Migration

  38. Centralized Migration policy • From the provider point of view efficient migration mechanism maximize the performance of whole system • Tasks moved from overloaded server to underutilized servers • Three dimensional space search for selecting optimal migration strategy • For each server of the system, for each of its tasks the performance gain of migration to candidate servers should be estimated

  39. Centralized Migration Policy flow chart

  40. Centralized Migration policy • For efficient migration strategy following things are taken into account • Data volume • Residual processing burden • Multitenancy • Mobility

  41. Server initiated migration • Distributed migration mechanism • Server enable to decide for migration of its active task • Migration initiated when server overloaded and about to violate SLA • 2 dimensional search • For each active task anticipated gain for each possible migration to new server ; maximum gain selected • Impact of migration on destination not accounted(aggerate reduction of hosted task+migrating task)

  42. Task-autonomic migration • Distributed migration • Initiated by task itself ( instead of delegating cloud) • Migration done when beneficial execution time including migration delay. • Extreme competition for least loaded servers.

  43. Characteristics of different mode of migrations

  44. Evaluation of migration benefits and impact of mobility Indicative migration of mobile task throughout its lifetime under three scenarios.

  45. Evaluation of migration benefits and impact of mobility f

  46. Evaluation of migration benefits and impact of mobility f

  47. Evaluation of migration benefits and impact of mobility f

  48. Future challenges and open direction • Energy efficiency consideration of Task Migration • Server load migration and Integration of Renewable Sources • Impact of Multitenancy • Modeling Future cloud Ecosystems

  49. Energy efficiency consideration of task migration • Critical issue in large data center with many dispersed servers • Energy consumption> number of active servers > increasing server load • Task migration saves energy consumption by reducing no of the active servers or by reducing energy consumption of individual server • Contradiction • Relative amount of energy consumption of servers when idle or loaded and dependence of energy consumption on a physical machine load • Derive analytical model

  50. Server load migration and integration of renewable sources • General policy is to build co-located renewable energy source for minimization of dependence with main power grid • o/p of these sources stochastic and time varying • Task migration on data center changes power demand. • Balance the power supply and demand by migration control

More Related