Mobile Code Offloading from Concept to Practice, and Beyond
Huber [email protected]
HKUST, Hong Kong, 2014
Outline
• Background (Concept)• Problem statement (Practice)• Solutions (Beyond)• Conclusions
Background
• What is code offloading?– Type of binding between mobile and cloud– Move a computational task from one place to
another • What is the purpose?
– What, when, where, how?– Release the smartphone from intensive processing– Increase performance of the mobile apps, in terms
of responsiveness
Background
• Which are the components of a code offloading architecture?– Mobile
• Code profiler• System profilers• Decision engine
– Cloud-based surrogate• Server
Problem statement
• Code offloading outcome is mostly negative– Partial answer to what, when, where, and how
Problem statement
• Inaccurate code profiling • Low effectiveness to detect resource intensive
code
Problem statement
• Integration complexity– Code annotations– Introduce the mechanisms within the mobile
platform
Solutions
• Massive data analysis with cloud• Mobile crowdsourcing (implicit)• Exploitation of the cloud surrogate
Evidence-aware Mobile Code Offloading
• Characterization of the offloading process
Conclusions and future directions
• The characterization of the offloading process can enhance the outcome of code invocation.
• Increasing the acceleration of the offloading process is the next reasonable step to overcome a negative impact.
• Offloading systems powered by SOA– Energy as a service?
