In July 2026 a BMW iX3 placed a voice call over satellite from its own infotainment screen, with no cellular signal and no separate handset involved. Viasat delivered the demonstration with BMW Group at 5GAA Meeting Week in Munich, building on the satellite voice call it showed alongside Cubic3 at Mobile World Congress in February. The eSIM capability that lets a vehicle authenticate and connect over that network came from an earlier Cubic3 proof of concept. Connectivity everywhere for vehicles has moved out of the standards documents and into a production vehicle interface.
Munich showed what that standardisation delivers. The call ran over NB-IoT on Qualcomm’s Snapdragon Auto 5G Modem-RF Gen 2 with the Fraunhofer IIS NESC AI voice codec, carried on Viasat’s L-band network. February’s MWC demonstration and how it was built established the link. July put it behind the dashboard of a car a customer could soon buy.
The detail worth sitting with is the payload. A voice call is a few kilobits per second. Nobody streamed anything.
That is the opposite of how satellite is usually sold into automotive, where the pitch tends to arrive wrapped in megabits and rear-seat entertainment. The commercial case for satellite in vehicles is built almost entirely on small packets: position, fault codes, emergency voice, software update triggers. Once you accept that, the architecture question changes completely.
The bandwidth story is the wrong story
Satellite capacity is expensive, contended and constrained by physics that no constellation operator can argue with. Sold as a way to keep passengers entertained past the edge of cellular coverage, it fails on cost and disappoints on experience.
Sold as a way to guarantee that a vehicle is never unreachable, it works today.
The traffic that justifies a satellite link in a vehicle is measured in kilobits, and it is the traffic an OEM cannot afford to lose.
That reframing has consequences for procurement. An OEM specifying satellite as a bandwidth extension will size the system for a use case that never pays back. An OEM specifying it as a reachability guarantee will size it for emergency voice, telematics and update control, which is a far smaller and far more defensible bill of materials.
Why satellite finally fits inside the cellular stack
Satellite has been available to automotive for years. It sat outside the cellular ecosystem, needing separate hardware, separate contracts and separate engineering effort, which is why it stayed in specialist fleets.
3GPP changed that in Release 17 by adding NTN support to the standard, covering both NR-NTN and IoT-NTN. Satellite became a native bearer inside the same air interface, so chipset vendors could add it to existing silicon. The specification work is set out in the 3GPP overview of satellite network standardisation. Release 18 extended into higher frequency bands and Release 19 added reduced-capability device support.
The MWC demonstration and how it was built shows what standards alignment buys in practice. No bespoke terminal. No second network agreement. It slots into the architecture the automotive and mobile industries are already constructing.
Orbit choice then sets the boundaries of what any given link can do.
| Bearer | Round-trip latency | Coverage characteristic | Realistic automotive use today |
|---|---|---|---|
| Terrestrial cellular | Single to low tens of milliseconds | Dense where people live, absent where they do not | Everything, wherever it reaches |
| LEO satellite, roughly 500km to 2,000km | Tens of milliseconds | Strong link budget, needs many satellites for continuity | Emergency voice, telemetry, messaging, update triggers |
| GEO satellite, 35,786km | Over half a second | Very wide footprint from a fixed position | Store-and-forward telemetry, non-interactive traffic |
Figures are indicative and vary by constellation, terminal and network load.
One SIM, two bearers, and the logic that chooses
A working architecture treats terrestrial and satellite as one managed pool. The mechanism sits at the SIM layer, where an eSIM holds multiple operator profiles and switches between them over the air, following GSMA specifications for remote provisioning. The specification designed for constrained deployments is documented in the GSMA standard for eSIM IoT provisioning.
Profile switching is straightforward. The orchestration logic above it is where programmes succeed or stall, because it has to answer several questions while the vehicle is moving:
- Which bearer is reachable at this location and this speed
- Which MNO profile gives the better commercial and technical outcome in this country
- Which traffic earns a satellite link and which waits for terrestrial coverage to return
- What service guarantee applies to safety-critical messages against everything else
Cubic3 and Skylo have taken this down to the hardware, with an automotive solution unifying cellular and satellite coverage through a single SIM. That removes the dual-subscription problem that kept satellite a separate programme rather than a bearer. The orchestration runs across 200+ countries and over 550 mobile networks through the Cubic3 Cloud connectivity platform.
What connectivity everywhere for vehicles costs OEMs
The coverage promise nobody reads carefully
Ubiquitous connectivity sounds like a coverage map question. It is a contractual one. The commitment an OEM makes is a known service quality in every market where the vehicle is homologated, held for the full service life of the platform.
Three things erode that commitment quietly. Roaming agreements are negotiated country by country and expire. Several regulators restrict permanent roaming, so a vehicle exported into a market cannot indefinitely ride another operator’s agreement. Network generations sunset on national timelines, and a vehicle built today will outlive at least one of them.
Our guide to what global coverage requires at platform level covers how those commitments are structured commercially.
The stakes rise as functions move into software. A SDV platform assumes the link exists when a security patch has to reach 400,000 units inside a regulatory window, which is why the cloud architecture behind software-defined vehicle programmes and the connectivity architecture have to be designed as one system.
Where the payback shows up first
The clearest returns come from vehicles that work outside urban coverage as routine. Mining, agriculture, construction plant and long-haul freight all share one trait: an asset worth six or seven figures spends significant time somewhere a mast cannot see it.
A haulage vehicle crossing 200km of unserved terrain still reports position and diagnostic trouble codes, so a workshop prepares parts before it arrives. Agricultural machinery reports throughput during the harvest window rather than after it.
For OEMs, the revenue argument sits in connected services that stop working the moment the vehicle goes dark. In-vehicle payment is the sharpest example, because a fuel or toll transaction validated against live vehicle data needs the vehicle reachable at the point of sale. That is what FleetWallet3 in-vehicle payments depends on, and it is a service OEMs can only sell against coverage they can actually promise.
Emergency call functionality follows the same logic. Its value is concentrated precisely where terrestrial coverage runs out.
What changes between now and 6G
3GPP opened Release 20 study work for 6G at the end of 2025, with the intent that non-terrestrial access forms part of the architecture from the start rather than arriving as a retrofit. Normative specifications are expected from Release 21.
Direct-to-device services are maturing alongside, with constellations delivering standard cellular signals to unmodified handsets. Automotive inherits the chipset economics from that consumer volume, which has historically been the barrier to putting satellite capability into mass-market vehicles. Our assessment of where automotive connectivity claims meet operating reality covers what is shipping against what is being announced.
Two constraints will set the pace. Satellite spectrum allocation varies by jurisdiction and needs regulatory alignment before a global programme can depend on it. Module cost has to fall far enough that a body controller carries satellite capability without a visible bill-of-materials penalty across a model range.
For anyone specifying a platform that reaches production in 2029, the question is whether the connectivity stack can absorb a new bearer without a hardware change. That is answerable now.
Frequently asked questions
Does satellite connectivity replace cellular in vehicles?
No. Terrestrial cellular carries the overwhelming majority of vehicle data traffic and will continue to. Satellite covers the geographic gaps where terrestrial networks have no commercial reason to build, handling low-bandwidth traffic that cannot be allowed to fail.
What is NTN and why does it matter for automotive?
NTN describes satellite and high-altitude platforms operating as nodes inside the cellular network. 3GPP standardised it in Release 17, which means satellite support can be added to existing cellular chipsets rather than requiring a separate radio, terminal and subscription. That is what brings the cost into range for volume vehicle programmes.
How much bandwidth does a satellite link give a vehicle?
Current automotive NTN implementations are narrowband, suited to voice, messaging, position reporting and telemetry. Video streaming over satellite in vehicles remains a future capability rather than a current one, and specifying against it inflates cost without delivering a return.
Does satellite capability need extra hardware or a second subscription?
Not when it is implemented to the 3GPP standard. The Munich demonstration ran through the vehicle’s own infotainment system rather than a separate handset or module, and single-SIM approaches unify cellular and satellite profiles under one connectivity management layer.
When should an OEM specify satellite capability?
The decision point is the platform architecture rather than the launch date. If the connectivity stack can accept a new bearer through software and profile changes, satellite can be enabled when the commercial case matures. If it cannot, adding it later means a hardware change across the model range.
Find out where your coverage promise breaks
Request a coverage review against your homologation footprint
