Nov 2026· IEEE Transactions on Mobile Computing· Vol 25, pp. 20949-20964· 0 citations· 46 references
Abstract
This paper studies task offloading in infrastructure-free mobile edge computing (MEC), where end devices must autonomously discover candidate servers and make offloading decisions under dynamic connectivity and time-varying computing resources. However, the lack of centralized coordination incurs high overhead to acquire complete and timely server status information in device-dense environments, while independent user decisions conflict over high-performing servers. To address these challenges, we propose BACO, a backoff-based coordinated offloading scheme with three innovative designs. First, the proposed BACO framework coordinates user requests and server responses via corresponding distributed backoff processes over the shared broadcast channel. Specifically, long-waiting tasks and resource-rich servers are prioritized in backoff timer assignment, while user decision conflicts are avoided. A candidate server table at each user supports further multi-user coordination by reusing revealed server status information. Second, a salient-driven mapping algorithm is proposed to allow contending users and candidate servers to independently set backoff timers, mitigating channel collisions caused by excessive server responses by super-linearly amplifying priority differences. Third, the BACO backoff process is theoretically analyzed in terms of optimal-server revelation probability, collision probability, and backoff timer overhead, which supports environment-adaptive optimization of key backoff-related parameters under time-varying MEC environments. Extensive simulations and testbed experiments demonstrate that BACO consistently outperforms state-of-the-art baselines, reducing multi-user average offloading latency by up to 52.77% while maintaining favorable scalability and robustness in dynamic environments.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.