Vehicle roaming solutions are no longer a background infrastructure concern; they are a direct determinant of whether a connected vehicle delivers on its promise or frustrates the driver the moment it crosses a border.
For OEMs, the challenge is well understood in principle but frequently underestimated in practice. A vehicle leaving the home network of its primary MNO partner enters a world of fragmented agreements, variable signal quality, escalating data costs and regulatory obligations that differ country to country. The result, when roaming is handled poorly, is a degraded in-vehicle experience, inflated connectivity spend and a support burden that scales badly across a global fleet.
This post examines why vehicle roaming breaks down, what global vehicle connectivity solutions look like, and how OEMs can approach multi-network integration, cost management, user experience and regulatory compliance in a way that actually holds up at scale.
Why vehicle roaming is harder than it looks
Consumer smartphones roam without much friction today because the GSMA has spent decades standardising roaming agreements and because handsets carry eSIM profiles that can switch operators on demand. Connected vehicles operate in a different environment entirely.
A car is not a phone. It may carry multiple connectivity modules serving navigation, OTA update delivery, in-vehicle commerce, emergency call (eCall) compliance and telematics simultaneously. Each service may have different latency, bandwidth and availability requirements. Roaming a vehicle means maintaining all of those services in parallel, across a network that was not selected for that vehicle’s specific needs.
The underlying commercial structure adds further complexity. Traditional roaming agreements between MNOs are bilateral: they cover a defined set of services at agreed rates. When a vehicle manufacturer deploys vehicles across 30 or 40 markets, the number of bilateral relationships required becomes unmanageable. Most OEMs do not manage those relationships directly, they depend on connectivity platforms to aggregate them. The quality of that aggregation is what separates a vehicle that stays connected from one that drops services at the border.
Multi-network Integration for Connected Vehicles
The foundation of any effective vehicle roaming solution is multi-network integration: the ability to select, switch between and manage connectivity across multiple MNOs without manual intervention or service interruption.
eSIM technology, governed by GSMA specifications SGP.02 and SGP.22 for consumer and M2M The applications, respectively, provide the mechanism. A vehicle carrying an eSIM can hold multiple operator profiles and switch between them based on signal quality, cost or availability, without a physical SIM swap and without taking the vehicle off the road.
The practical requirement, however, goes beyond having an eSIM in the vehicle. Effective multi-network integration demands:
- A connectivity platform with pre-negotiated access to MNOs across the target markets, removing the need for the OEM to manage bilateral agreements
- Real-time network steering logic that selects the best available network based on defined parameters, not just whichever network happens to respond first
- Fallback routing that maintains critical services – particularly eCall and OTA — even when preferred networks are unavailable
- Centralised profile management that allows OEMs to push connectivity policy changes across their entire deployed fleet without physical access to vehicles
The emerging SGP.31 and SGP.32 specifications for IoT eSIM management points toward a future where this kind of remote, scalable profile orchestration is standardised. For OEMs planning connectivity architecture today, building toward those specifications rather than around them is worth the additional planning effort.
Managing roaming costs across a connected fleet
Data roaming costs have fallen significantly in many markets over the past decade, but they remain a material line item for any OEM operating vehicles at scale. A connected vehicle can consume several gigabytes per month across navigation updates, streaming, telematics and OTA delivery. Multiply that across hundreds of thousands of vehicles in roaming markets and the cost exposure becomes significant.
The problem is not just the headline rate. It is the visibility gap. Many OEMs do not know, in real time, what their vehicles are consuming on which networks in which markets. Billing comes in arrears, often aggregated in ways that make per-vehicle or per-service analysis difficult. By the time an anomaly is visible, it has already compounded.
Effective cost management in vehicle roaming requires the same principle that good fleet spend management requires generally: visibility before the fact, not reconciliation after it.
The practical mechanisms include consumption thresholds set at the vehicle or service level, with automated alerts or cutoffs when usage approaches defined limits. They include preferential network selection that routes traffic to the lowest-cost available network when service quality requirements are met. They include detailed usage analytics broken down by vehicle, market, service type and time period, so that OEMs can identify where costs are concentrated and why.
For SDV architectures specifically, where OTA update delivery may represent large, periodic data bursts, scheduling those updates for periods when vehicles are on home networks or connected to Wi-Fi reduces roaming data consumption considerably. That requires the update orchestration layer and the connectivity management layer to share information — which is not always the case in architectures where those functions are managed separately.
Roaming and the in-vehicle user experience
From the driver’s perspective, roaming should be invisible. The navigation system should not freeze at the French border. Music streaming should not cut out in a tunnel in Belgium. The vehicle’s digital services should behave the same way they did at home. That expectation is reasonable. Delivering against it is harder than it appears, for a reason that goes beyond raw network availability.
Connected vehicle services are not all equivalent in their tolerance for network interruption. Navigation can cache route data and function intermittently. Voice calls via VoLTE cannot. Telematics data can buffer and transmit when connectivity is restored. Emergency services cannot. OTA updates can be paused and resumed. Real-time traffic data cannot.
A vehicle roaming solution that treats all data traffic the same way will consistently fail some services in favour of others. Effective solutions apply QoS policies that prioritise traffic by service type, ensuring that safety-critical and compliance-related services are maintained even when overall bandwidth is constrained.
There is a secondary experience dimension that often goes unaddressed: transparency. When a vehicle does experience degraded connectivity during a roaming event, drivers and fleet operators benefit from knowing why. Connected vehicle analytics can surface that information, correlating connectivity events with location, network, time of day and vehicle type — making it possible to identify patterns and address root causes rather than treating each incident as isolated.
Regulatory compliance in cross-border vehicle connectivity
The regulatory picture for connected vehicles crossing borders is genuinely complex, and it is not standing still. UNECE WP.29 regulations governing cybersecurity and software update management apply to vehicles sold in most major markets and impose requirements that touch directly on connectivity architecture. EU data localisation rules affect where vehicle data can be processed and stored. eCall mandates require a minimum level of voice connectivity in all EU markets regardless of commercial roaming arrangements.
For OEMs, the compliance risk is not theoretical. A vehicle that loses eCall capability in a roaming market because its connectivity platform has not maintained the required voice path is a compliance failure with legal consequences. A vehicle that transmits personal data across a network path that falls outside the approved data processing boundaries creates GDPR exposure.
These are not edge cases. They are foreseeable failure modes in any vehicle roaming architecture that has not been designed with regulatory compliance as a first-order constraint rather than an afterthought.
The practical response is to map regulatory requirements market by market before deploying connectivity in those markets, and to select a connectivity platform that has already done that mapping and built compliance into its network steering and data routing logic. OEMs should expect their connectivity partners to demonstrate, not just assert, that their architecture satisfies the requirements of each target market.
What an effective vehicle roaming solution actually requires
Pulling the preceding considerations together, the specification for a vehicle roaming solution that holds up in practice looks something like this.
It needs pre-integrated MNO relationships across target markets, so that the OEM is not building bilateral agreements from scratch. It needs eSIM-based profile management that can be updated remotely, at scale, without physical access to vehicles. It needs intelligent network steering that selects by quality and cost, not just availability. It needs QoS policies that protect safety and compliance services regardless of overall network conditions. It needs real-time visibility into consumption and cost controls at the vehicle and service levels. It needs data routing that satisfies the regulatory requirements of each market. And it needs analytics that make roaming performance visible enough to be managed proactively rather than investigated retrospectively.
Automotive connectivity a demanding specification. It is also the right one. Connected vehicles operate in a complex, multi-market environment, and the connectivity infrastructure supporting them needs to match that complexity rather than paper over it.
To see how Cubic3’s connected vehicle platform manages roaming across global markets, explore our connected vehicle solutions.
Frequently asked questions about vehicle roaming solutions
What is a vehicle roaming solution?
A vehicle roaming solution is the combination of hardware, software, and network agreements that allows a connected vehicle to maintain data and voice connectivity when operating outside its primary network operator’s coverage area. It typically involves eSIM technology, multi-MNO agreements and intelligent network steering logic managed by a connectivity platform.
Why is roaming more complex for connected vehicles than for smartphones?
Connected vehicles run multiple simultaneous services with different connectivity requirements – navigation, telematics, OTA updates, emergency calls, and in-vehicle commerce, among others. Each service has different latency, bandwidth and availability needs. A smartphone roaming event affects one user and one service profile. A vehicle roaming event must maintain a portfolio of services in parallel, often subject to regulatory mandates that smartphones are not.
How does eSIM help with vehicle roaming?
eSIM allows a vehicle to carry multiple operator profiles and switch between them without a physical SIM swap. Under SGP.22 and the emerging SGP.31/32 framework, those profiles can be managed remotely by a connectivity platform, meaning OEMs can update connectivity policy across their entire deployed fleet without requiring vehicle access.
What are the main regulatory requirements affecting vehicle roaming in Europe?
The primary regulatory considerations include UNECE WP.29 requirements for cybersecurity and OTA update management, EU GDPR rules on data localisation and processing, and the mandatory eCall voice connectivity requirement for vehicles sold in EU markets. A compliant vehicle roaming solution must satisfy all three regardless of which network the vehicle is currently using.
How can OEMs control roaming data costs at scale?
Effective cost management requires real-time consumption visibility at the vehicle and service level, automated alerts or cutoffs when usage approaches defined thresholds, preferential network selection that routes traffic to the lowest-cost qualifying network, and scheduling of high-volume data transfers such as OTA updates for periods when vehicles are on home networks or Wi-Fi.
