Skip to content
#edge computing Open access

A comparative analysis of edge and cloud computing architectures for rolling stock monitoring systems

Oct 2026 · Інформаційно-керуючі системи на залізничному транспорті
IoT and Edge/Fog Computing

Abstract

This paper presents a quantitative comparison of Edge- and Cloud-oriented processing of technical-condition monitoring data for high-speed railway (HSR) rolling stock, based on a verified discrete-time digital twin of a train. Unlike approaches that treat Edge and Cloud as separate, independent configurations, the model simultaneously computes both processing pipelines within a single run, including a stochastic radio channel (correlated fading, Doppler-induced degradation, HARQ with residual block error), priority-based scheduling of two traffic classes (safety-critical and monitoring), and a thermal model of the on-board computer with throttling. A hybrid architecture mode, in which Edge pre-filters monitoring traffic before forwarding it to the Cloud, is additionally implemented and empirically evaluated. The full factorial design shows that the two architectures are bottlenecked by fundamentally different mechanisms: the Cloud degrades due to the physical unavailability of the radio channel, whereas Edge degrades due to thermal throttling under insufficient cooling. The simultaneous action of both factors drives the share of the critical Both Down state to a substantial fraction of the total observation time, whereas increasing the thermal headroom of the hardware platform alone is sufficient to reduce this share several-fold. Hybrid filtering delivers a measurable reduction in network traffic both under nominal conditions and under active anomalous load, but the accompanying ML-inference compute load measurably erodes the Edge node’s thermal headroom. Local computation proved substantially more energy-costly than radio transmission of the same volume of data. The results quantitatively substantiate the need for a redundant hybrid monitoring architecture in which no single subsystem constitutes a single point of failure.

Read PDF

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

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. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

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. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

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. · 394 citations · ⚡54

Related blog posts

Microsoft Research Blog Oct 6, 2026

What AI gets wrong and what failure teaches us

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.