scispace - formally typeset
Search or ask a question

Showing papers by "Eemil Lagerspetz published in 2013"


Proceedings ArticleDOI
11 Nov 2013
TL;DR: During a deployment to a community of more than 500,000 devices, Carat diagnosed thousands of energy anomalies in the wild and increased a user's battery life by 11% after 10 days (compared with 1.9% for the control group).
Abstract: We aim to detect and diagnose energy anomalies, abnormally heavy battery use. This paper describes a collaborative black-box method, and an implementation called Carat, for diagnosing anomalies on mobile devices. A client app sends intermittent, coarse-grained measurements to a server, which correlates higher expected energy use with client properties like the running apps, device model, and operating system. The analysis quantifies the error and confidence associated with a diagnosis, suggests actions the user could take to improve battery life, and projects the amount of improvement. During a deployment to a community of more than 500,000 devices, Carat diagnosed thousands of energy anomalies in the wild. Carat detected all synthetically injected anomalies, produced no known instances of false positives, projected the battery impact of anomalies with 95% accuracy, and, on average, increased a user's battery life by 11% after 10 days (compared with 1.9% for the control group).

176 citations


Proceedings ArticleDOI
TL;DR: This paper presents the first independent study of malware infection rates and associated risk factors using data collected directly from over 55,000 Android devices, and indicates that the application set does serve as an inexpensive method for identifying the pool of devices on which more expensive monitoring and analysis mechanisms should be deployed.
Abstract: There is little information from independent sources in the public domain about mobile malware infection rates. The only previous independent estimate (0.0009%) [12], was based on indirect measurements obtained from domain name resolution traces. In this paper, we present the first independent study of malware infection rates and associated risk factors using data collected directly from over 55,000 Android devices. We find that the malware infection rates in Android devices estimated using two malware datasets (0.28% and 0.26%), though small, are significantly higher than the previous independent estimate. Using our datasets, we investigate how indicators extracted inexpensively from the devices correlate with malware infection. Based on the hypothesis that some application stores have a greater density of malicious applications and that advertising within applications and cross-promotional deals may act as infection vectors, we investigate whether the set of applications used on a device can serve as an indicator for infection of that device. Our analysis indicates that this alone is not an accurate indicator for pinpointing infection. However, it is a very inexpensive but surprisingly useful way for significantly narrowing down the pool of devices on which expensive monitoring and analysis mechanisms must be deployed. Using our two malware datasets we show that this indicator performs 4.8 and 4.6 times (respectively) better at identifying infected devices than the baseline of random checks. Such indicators can be used, for example, in the search for new or previously undetected malware. It is therefore a technique that can complement standard malware scanning by anti-malware tools. Our analysis also demonstrates a marginally significant difference in battery use between infected and clean devices.

57 citations


01 Jan 2013
TL;DR: This paper follows the history of the term “cloud” from the beginning of the Internet to the era of cloud computing, and ponders its past and current meaning, arguing that outsourcing is the primary meaning of “ cloud”.
Abstract: This paper follows the history of the term “cloud” from the beginning of the Internet to the era of cloud computing, and ponders its past and current meaning We argue that outsourcing is the primary meaning of “cloud” We discuss elasticity and its significance in cloud computing Elasticity is a key cost-cutting measure, especially for startup companies, but is not a requirement for cloud systems We discuss the simple service layer model and the role of software components on different layers We refine the model to better capture real-world use cases This is achieved by dividing the layers into solutions and solutions further into components Finally, we define a new computing business model In this model, a company manages the entire computing experience of users We conclude with discussion of the new business model and the possibilities it offers for users of the cloud

3 citations