Multi-access Edge Computing: The driver behind the wheel of 5G-connected cars

Fabio Giust; Vincenzo Sciancalepore; Dario Sabella; Miltiades C. Filippou; Simone Mangiante; Walter Featherstone; Daniele Munaretto

arXiv · 1803.07009

Multi-access Edge Computing: The driver behind the wheel of 5G-connected cars

Fabio Giust·Vincenzo Sciancalepore·Dario Sabella·Miltiades C. Filippou·Simone Mangiante·Walter Featherstone·Daniele Munaretto

View original source ↗Read source document ↗Export metadata ↓

Abstract

The automotive and telco industries have taken an investment bet on the connected car market, pushing for the digital transformation of the sector by exploiting recent Information and Communication Technology (ICT) progress. As ICT developments continue, it is expected that the technology advancements will be able to fulfill the sophisticated requirements for vehicular use cases, such as low latency and reliable communications for safety, high computing power to process large amount of sensed data, and increased bandwidth for on-board infotainment. The aforementioned requirements have received significant focus during the ongoing definition of the 3GPP 5G mobile standards, where there has been a drive to facilitate vertical industries such as automotive, in addition to providing the core aspects of the communication infrastructure. Of the technology enablers for 5G, Multi-access Edge Computing (MEC) can be considered essential. That is, a cloud environment located at the edge of the network, in proximity of the end-users and coupled with the service provider's network infrastructure. Even before 5G is rolled out, current mobile networks can already target support for these challenging use cases using MEC technology. This is because MEC is able to fulfill low latency and high bandwidth requirements, and, in addition, it lends itself to be deployed at the vertical industrial sector premises such as road infrastructure, air/sea ports, smart factories, etc., thus, bringing computing power where it is needed most. This work showcases the automotive use cases that are relevant for MEC, providing insights into the technologies specified and investigated by the ETSI MEC Industry Specification Group (ISG), who were the pioneer in creating a standardized computing platform for advanced mobile networks with regards to network edge related use cases.

Explore related subjects

cs.NI

Keep this discovery

BibTeX RIS

Fabio Giust, Vincenzo Sciancalepore, Dario Sabella, Miltiades C. Filippou, Simone Mangiante, Walter Featherstone, Daniele Munaretto. 2018-03-19. Multi-access Edge Computing: The driver behind the wheel of 5G-connected cars. https://arxiv.org/abs/1803.07009

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Message-Level Scheduling for RLNC-Coded Multi-Source Traffic

This paper studies weighted decoding-delay minimization for multiple RLNC-coded message streams that compete for finite processing capacity at a destination. Packet arrivals are exogenous, while the scheduler only determines the processing order of packets already available at the destination. A trace-conditioned offline scheduling formulation shows that a batch-release subclass is strongly NP-hard even with a single processing unit. Message-Aware Innovation-Deficit Scheduling (MAIDS) is then developed to prioritize each serviceable message according to its weight and remaining decoding deficit. For a single processing unit, MAIDS is shown to be exactly optimal under nonblocking progressive arrivals with equal weights and under common activation with arbitrary positive weights, while the unrestricted weighted online problem admits no universal deterministic $O(1)$ competitive ratio. Simulation results on streaming and batch benchmarks show that MAIDS consistently reduces weighted decoding delay relative to the tested baselines, remains close to the offline optimum on average, and recovers the predicted exact performance boundaries.

cs.NI↗

arXiv2026

The Towers Were Standing: A Cause Decomposition of Cellular Outages During Hurricane Helene

Hurricane Helene produced the largest absolute cell-site outage in the public FCC record, peaking at 4562 sites. The conventional model is physical: towers destroyed. Helene did destroy over 1700 miles of fibre, but almost none of it was cell sites. We present the first cause-decomposed study of the FCC's Disaster Information Reporting System, reconstructing 80 state-days and 580 county-days from 24 daily filings by two reconciled independent extractions. Damage to cell sites is negligible: 1.1% of attributed cell-site-days across six states, at most 3.8% anywhere. The sites were standing. What took them out divides by terrain: pooled, power dominates at 63.2%, but in mountainous North Carolina severed transport (backhaul) reaches 52.2% against 47.3%, and in Tennessee 69.9%. North Carolina's transport share rises from 7.0% to 85.0% across the event (\r{ho} = 0.92). Seventeen days after landfall, on 15 October, 47 sites lost transport across six contiguous North Carolina counties with no rainfall, no power loss, no damage, and recovery by the next report. Independent active-probe measurement corroborates it: responsive /24s fall 1.02% for twelve hours while Tennessee stays flat. We release the dataset. Backup power is the standard resilience investment; here it addresses the smaller half of the problem.

cs.NI↗

arXiv2026

terms.txt: A Consent and Compensation Protocol for Agentic Web Access

The open web ran on an unwritten bargain: sites admitted crawlers, and search engines sent visitors back. Public measurements show that bargain breaking under AI crawlers and agents. Automated clients now make up most requests, training dominates Cloudflare-classified crawling, and the largest AI platforms fetch thousands of pages for each visitor they return. The web's common control, robots.txt, cannot express identity, purpose, terms, or price, can be circumvented, and newer alternatives are largely proprietary CDN features. We specify terms.txt, a robots.txt-style file for per-path, per-purpose machine-access terms, plus an origin-enforced exchange using Web Bot Auth signatures, signed intent, delegation tokens, HTTP 402 negotiation, and signed receipts. We define what the exchange can enforce, audit, and leave to contract. A dependency-free implementation adds 0.20 to 0.65 ms per request on one vCPU.

cs.NI↗