Reusing Spare Vehicle Computing Capacity: Is It Viable, Profitable and Sustainable?

Vehicular Cloud Computing (VCC) is viable, profitable, and sustainable for task offloading in urban areas, as demonstrated by arXiv:2609.29731.

Viability: Vehicles absorb most offloaded traffic within tens of milliseconds, satisfying stringent latency constraints. The system maintains low failure rates at high vehicle densities, with vehicles serving 97% of tasks at 30 units and nearly all beyond 60.

Profitability: Participation yields $0.87 to $4.13 per vehicle-month, equivalent to 33 to 157 km of monthly driving range. Over an 18.4-year vehicle lifetime, this amounts to $194 to $924. VCC’s cost per served task is up to 8,241 times lower than edge computing at off-peak loads due to zero capital expenditure.

Sustainability: VCC reduces life-cycle CO2 emissions by over 99% compared to edge infrastructure. While edge servers emit up to 8.5 tons of CO2 over their lifetime, a VCC vehicle adds only 6 to 300 grams annually.

• Scope and problem. The paper examines Vehicular Cloud Computing (VCC), a model in which spare compute resources already present in vehicles—such as processors used for infotainment, telematics, or driver-assistance functions—are repurposed to execute offloaded tasks for end users. Rather than provisioning new edge or cloud infrastructure, VCC treats the vehicle fleet as a distributed, opportunistic compute fabric. The central issue is that this idea has strong conceptual appeal but has lacked rigorous quantitative evidence on whether it can actually operate at useful scale, generate economic returns, and remain environmentally defensible.

• Key contributions and insights. The work contributes by framing VCC as a systems-level viability question spanning technical capacity, economics, and sustainability. It likely evaluates whether idle vehicle compute is available in sufficient quantity, at the right times and locations, and with enough performance and reliability to support realistic workloads. It also examines the economic conditions under which vehicle owners, operators, or service providers would be incentivized to participate, and contrasts VCC with more conventional deployment options such as dedicated edge nodes or data-center execution. The resulting insight is that VCC’s promise depends not only on hardware availability but on the interplay of fleet density, traffic patterns, task demand, pricing, energy efficiency, and lifecycle impacts.

• Why it matters. This is important because VCC could reduce the need for additional compute infrastructure and improve resource utilization in a networked vehicle ecosystem, but only if it is viable in practice. By quantifying the trade-offs among profitability, service feasibility, and sustainability, the paper provides evidence that can guide platform designers, automotive OEMs, cloud/edge operators, and policymakers. It helps move VCC from a speculative architectural idea toward a deployable model with clearer deployment criteria and business logic.