The Road Ahead for Automotive 5G SA: Scaling Connectivity for the Vehicle Lifecycle

After years of anticipation, 5G Standalone (5G SA) wireless connectivity is moving from the future roadmap into requirements for connected vehicle programs launching in 2027 and beyond. With its cloud-native 5G core, 5G SA brings lower latency, advanced quality of service (QoS), network slicing and more flexible service delivery within reach in support of more responsive vehicle services, prioritized communications and differentiated customer experiences.

 

As an automotive original equipment manufacturer (OEM), you must plan for the gap between the promise of 5G SA and the realities of global deployment. The wireless connectivity model you choose today must support vehicles for 10 to 15 years across markets where coverage, capabilities, regulations and services will advance at different rates.

 

 

The scale of the market raises the stakes for those long-term decisions. Transforma Insights projects that the global connected vehicle fleet will grow from 876 million in 2025 to 2.1 billion in 2035, generating $72 billion in annual IoT revenue by 2035. That projected expansion makes the relationship between 5G and connected cars a long-term scalability issue, not simply a launch-year technology decision.

 

The challenge isn’t simply adopting 5G SA but deploying it at global scale while preserving the coverage, control and service continuity each vehicle will need throughout its lifecycle.

 

 

5G SA vs 5G NSA: Why the Core Network Decision Matters

 

Not all 5G networks are created equal. Two networks may both be called 5G yet offer materially different capabilities depending on the core network beneath them. Most early 5G deployments use a Non-Standalone (NSA) architecture, which combines 5G radio access with a 4G Long Term Evolution (LTE) core. This approach enabled mobile operators to introduce 5G more quickly, delivering faster speeds and greater capacity. However, the control plane (the functions that manage and control the connection) remains anchored in 4G infrastructure.

 

5G SA changes the equation. By pairing 5G radio access with a dedicated, cloud-native 5G core, 5G SA creates the foundation for lower latency, network slicing and advanced quality of service (QoS).

 

5G SA enables your connected vehicle program to prioritize latency-sensitive applications, separate critical vehicle communications from other traffic and support differentiated service levels. These capabilities are central to the broader transformation enabled by 5G for automotive industry applications.

 

Fortunately, 5G SA network launches are accelerating. The Global Mobile Suppliers Association, reports that 95 operators had launched commercial 5G Standalone services by April 2026, up 42 percent since the first quarter of 2025.

 

However, despite the increasing pace of deployment, not every market will offer the same wireless coverage or capabilities. The range of network generations (4G, 5G NSA and 5G SA) will coexist for years. GSMA Intelligence forecasts 5G will overtake 4G in 2028 and account for 57 percent of mobile connections by 2030. Even then, 4G will still represent 38 percent of connections worldwide. Transforma Insights projects that 4G LTE networks could remain operational in some markets until as late as 2040.

 

For automotive OEMs, that overlap isn’t a footnote; it’s the operating environment. So, a vehicle program you plan today may need to work across 4G, 5G NSA and 5G SA networks throughout its lifecycle. Consequently, your 5G SA architecture must capture the advantages of 5G SA wherever they are available without sacrificing coverage or service continuity where 4G remains essential.

 

 

5G SA Is Moving From Future Roadmap to Vehicle Program Requirement

 

As you define connectivity requirements for vehicles launching in 2027 and beyond, 5G SA can no longer remain a future consideration. You must evaluate its role in your architecture now, well before those vehicles reach the road.

 

Automotive sourcing timelines leave little room to wait. Contract awards may precede scaled vehicle rollout by 18 months or more, requiring you to select and qualify your connectivity model while 5G SA coverage and capabilities are still developing across markets.

 

The challenge is not simply finding technology that supports 5G SA. You need a wireless connectivity model that can meet launch requirements, operate across markets at different stages of network readiness and continue supporting each vehicle for 10 to 15 years. That makes flexibility during the transition just as important as 5G SA readiness itself.

 

 

Vehicle Lifecycles Require Connectivity That Can Go the Distance

 

Because you can’t predict when every operator will launch 5G SA or when each market will be ready to support it, you need a clear migration path. Your connectivity plan should account for how vehicles will maintain service where 5G SA is unavailable, when new capabilities can be introduced market by market and how network configurations will evolve as coverage and services mature.

 

Hardware that supports both 4G LTE and 5G SA preserves access to both network generations. With that foundation in place, over-the-air (OTA) updates can adapt firmware and network configurations as networks evolve, allowing vehicles already on the road to migrate without hardware replacement. Together, these elements give you the flexibility to move at the pace of each market while maintaining service continuity across the fleet.

 

 

Scaling 5G SA Applies Across the Connected Vehicle Ecosystem

 

Your migration path must do more than keep vehicles connected as networks change. It also must support a growing mix of connected vehicle services, each with different requirements for coverage, bandwidth, latency and quality of service. Sending a routine telematics message, for example, typically requires little bandwidth and can tolerate some delay. Downloading new vehicle software requires greater bandwidth and data capacity, while a time-sensitive road-hazard alert depends on low latency and reliable delivery.

 

Across your connected vehicle programs, those services may include:

 

• Telematics, remote diagnostics and fleet or mobility services
• Firmware, software and map updates delivered over the air
• Software-defined features and subscriptions
• EV battery monitoring and charging services
• Infotainment and in-vehicle digital experiences
• Safety and emergency calling
• Connected services supporting advanced driver assistance systems (ADAS) and future cellular vehicle-to-everything (C-V2X) applications

 

It’s worth noting that not every connected vehicle service requires full-performance 5G. Full-performance 5G telematics control units (TCUs) generally cost more than 4G LTE units and can require more complex antenna, power and thermal designs. That can make them difficult to justify for lower-throughput vehicle applications.

 

For these use cases, 5G Reduced Capability (RedCap) can provide a middle ground. RedCap is designed to reduce device complexity, cost and power consumption compared with full-performance 5G, making it a potential migration path for many automotive applications currently supported by 4G LTE. RedCap coverage is not yet available everywhere, but operators can expand it as their 5G networks mature and they prepare for future reductions in LTE coverage.

 

At the advanced end of the spectrum, however, C-V2X and services supporting ADAS may require sub-10-millisecond latency and assured quality of service. That’s where the lower latency and advanced QoS capabilities of 5G SA become especially important.

 

Keep in mind that the goal is not to overengineer connectivity for every use case. It’s to give each service the performance it needs while preserving a path to more advanced capabilities as your vehicles, services and markets evolve.

 

 

The SDV Shift Makes 5G SA a Clear Advantage

 

Your need to match connectivity to each service becomes even more important as vehicles become software-defined. In a software-defined vehicle (SDV), software increasingly shapes the vehicle’s features, functionality and value after it leaves the factory. Centralized computing and OTA delivery allow you to add capabilities, improve performance and introduce new services throughout the vehicle lifecycle.

 

The shift to SDV also changes what you need from connectivity. The network is no longer simply a channel for telematics or infotainment; it becomes delivery infrastructure for the vehicle itself. Delivering software updates across a global fleet, supporting feature subscriptions and diagnosing issues remotely all place greater demands on network capacity, responsiveness and QoS. 5G SA’s lower latency, advanced QoS and network-slicing capabilities give you more options for managing and prioritizing those workloads.

 

Of course, your entire vehicle portfolio will not become software-defined overnight. For years, you will need to support advanced SDVs alongside connected vehicles with simpler requirements, including vehicles that continue to rely on 4G LTE. Your connectivity model must accommodate those different needs, meeting the higher performance demands of SDVs without adding unnecessary cost or complexity across the broader connected vehicle fleet.

 

 

Global Scale Is the Real Test for Automotive 5G SA

 

Supporting a diverse vehicle portfolio is challenging enough in one market. Across a global program, the complexity multiplies. The same vehicle platform may launch in countries where 5G SA is widely available, emerging or years away. Each will have its own operators, regulations and commercial requirements.

 

Managing those differences country by country can quickly leave you juggling separate contracts, platforms, service-level agreements, billing processes and technical integrations. That fragmentation creates an administrative burden and makes it harder to maintain consistent service, introduce new capabilities and manage connectivity across the global fleet.

 

Your connectivity model needs to support that complexity. It must keep vehicles connected through 4G LTE or 5G NSA where 5G SA is unavailable, while allowing you to introduce 5G SA market by market. The GSMA SGP.32 Embedded Subscriber Identity Module (eSIM) specification supports that flexibility by enabling operator profiles to be provisioned and managed remotely. A vehicle manufactured in one country can be localized for service in another without replacing its physical SIM.

 

Roaming is equally important because vehicles do not remain within the markets where they are sold. A deliberate 5G SA roaming strategy can help preserve a consistent service experience and control over vehicle data as vehicles cross borders. That’s the real test of global readiness: whether you can adapt connectivity to each market without rebuilding your operating model each time.

 

 

Security and Data Control Must Be Designed Into the Connectivity Model

 

Adapting connectivity market by market shouldn’t require you to give up visibility or control. As vehicles move across networks and borders, every connected service creates another flow of data to protect. Yet many enterprise security tools can’t see traffic inside the cellular network, leaving a gap between the vehicle and the cloud systems you already secure.

 

United Nations Economic Commission for Europe (UNECE) Regulations 155 and 156 raise the stakes. They require automotive OEMs to manage cybersecurity risks and software updates systematically throughout the vehicle lifecycle. Although the regulations don’t prescribe a particular connectivity architecture, the model you choose must support the visibility and control needed to manage those responsibilities.

 

That’s difficult to add after vehicles are already on the road. Installing device agents or replacing hardware across a global fleet can be costly and, in many cases, impractical. Building network-layer visibility and centralized policy controls into your connectivity model from the start allows you to identify unusual behavior, restrict unwanted communications and apply consistent security policies as vehicles switch operators or enter new markets. Automotive cybersecurity can’t stop at the vehicle and the cloud. Your connectivity model must also help you monitor, control and protect the data moving between them.

 

Your roaming architecture shapes that control, too. With home-routed roaming, vehicle traffic returns through the home network instead of breaking out locally through a visited network. This can help you maintain centralized visibility, enforce consistent policies and control how data is routed as vehicles cross borders, especially when data sovereignty requirements differ from one market to another.

 

 

Regulatory and Technology Shifts Raise the Stakes

 

Your connectivity roadmap can’t focus only on where 5G SA is available today. It must also prepare for regulatory deadlines and evolving technical standards.

 

The European Union’s transition to Next Generation eCall (NG eCall) is a clear example. eCall, the EU’s in-vehicle emergency-calling system, can automatically call EU’s 112 emergency number, share the vehicle’s location and open a voice connection with emergency responders.

 

First-generation eCall relies on 2G and 3G networks. NG eCall moves the service to packet-switched 4G and 5G networks using the IP Multimedia Subsystem (IMS). IMS supports Voice over LTE (VoLTE) on 4G and Voice over New Radio (VoNR) on 5G. That means your module, connectivity service, voice capabilities, network coverage and testing must work together. Supporting 4G or 5G alone isn’t enough.

 

That transition is already tied to firm compliance deadlines. According to the European Emergency Number Association (EENA), Delegated Regulation (EU) 2024/1180 requires NG eCall for new vehicle types placed on the EU market after Jan. 1, 2026 and for all new vehicles placed on the market after Jan. 1, 2027. These deadlines make packet-switched eCall support an immediate design and launch consideration for automakers.

 

Because operators, markets and emergency-response centers won’t all transition at the same time, your module strategy may need to support 4G, 5G SA and both generations of eCall.

 

Additionally, the 3rd Generation Partnership Project (3GPP) standards that underpin 4G, 5G and eCall will continue to evolve. To prepare for future requirements, automakers should deploy hardware that supports both 4G LTE and 5G SA and choose connectivity that can adapt through firmware and network updates.

 

 

Where Aeris Fits in the Automotive 5G SA Ecosystem

 

Making 5G SA work across a global vehicle program takes an ecosystem of network providers, module providers, platform partners and security providers. The right ecosystem reduces complexity for automakers instead of leaving you to manage separate operators, contracts and integrations in every market.

 

Aeris brings these elements together through Aeris IoT Accelerator, the company’s IoT Connectivity Management Platform. The platform integrates more than 30 independent mobile network operators through a shared core network, management platform and value-added services layer. You get one consistent way to manage connectivity, regardless of the country or underlying operator.

 

With Aeris IoT Accelerator, you can:

 

• Expand 5G SA coverage across markets: Use the Aeris “network of networks” model to access 5G SA as it becomes available through underlying mobile network operators.
• Deploy globally under one contract: Use eSIM localization to connect vehicles through local operator profiles without managing separate agreements in every market.
• Manage connectivity through one platform: Maintain visibility and apply policies across countries and network providers from a unified interface.
• Support 4G and 5G SA side by side: Keep vehicles connected over 4G while introducing 5G SA by market, vehicle program or use case.
• Protect existing hardware investments: Migrate 5G SA-capable modules already in the field through over-the-air updates instead of replacing installed hardware.
• Secure vehicle communications with Aeris IoT Watchtower: Monitor cellular traffic and device behavior, detect anomalies and enforce security policies within the network.

 

Together, these capabilities help you manage the complexity of a global 5G SA transition without rebuilding your connectivity model for every market.

 

 

What Automakers Should Evaluate Now

 

A connectivity model selected for a 2027 vehicle program may still need to support that vehicle in 2042. As you evaluate your options, consider these questions:

 

• Can your connectivity plan support 5G SA requirements for vehicle programs launching in 2027 and beyond? Automotive platforms are designed years before launch. Building in 5G SA readiness now can reduce the risk of late redesigns as OEM requirements and operator networks evolve.
• Can your connectivity model support vehicles for 10 to 15 years? Networks, standards and connected services will change throughout the vehicle lifecycle. Your connectivity model must evolve without shortening the useful life of the vehicle’s communications system.
• Can your connectivity work across global launch markets while supporting both 4G LTE and 5G SA? Markets and operators will adopt 5G SA at different rates. Supporting both technologies allows you to launch globally without creating a separate connectivity architecture for each market.
• Can your connectivity choice avoid hardware replacement in deployed vehicles? Replacing embedded modules is expensive and often impractical. The ability to migrate vehicles with 5G SA-capable hardware through over-the-air updates helps protect your investment.
• Can your connectivity model provide consistent visibility and control across regions? Managing separate operators and platforms creates operational gaps. Centralized monitoring and policy management make it easier to control usage, troubleshoot problems and manage connectivity consistently.
• Can your connectivity model secure cellular traffic without device agents? Installing and maintaining security software in every vehicle adds complexity. Network-layer monitoring can provide traffic visibility and policy enforcement without placing another agent on the vehicle.
• Can your connectivity model support eSIM localization and maintain data control when vehicles roam? Localization can connect vehicles through appropriate local profiles, while routing control determines where their data travels. Both capabilities are important for performance, regulatory compliance and consistent security policies.
• Can your connectivity model keep pace with regulatory and standards changes? NG eCall requirements and 3GPP specifications will continue to evolve after a vehicle launches. Your connectivity model must accommodate those changes without requiring a new global deployment strategy.

 

 

Building for the Full Vehicle Lifecycle

 

5G SA isn’t simply a network upgrade; it’s part of a connected vehicle strategy that must support the full vehicle lifecycle—from module sourcing and launch through global deployment, roaming, updates, security and compliance.

 

Ultimately, the choices you make today will also affect how easily you can introduce new connected services in the future. By planning for the long road ahead, you’ll be better positioned to adapt as networks, markets, regulations and customer expectations evolve.

 

 

Automotive 5G SA: Frequently Asked Questions

 

What is 5G Standalone (5G SA)?

5G Standalone uses 5G radio access and a 5G core without depending on a 4G core. This architecture can support lower latency, network slicing and more precise QoS controls. Actual performance depends on the operator’s network, coverage and service configuration. If a device or module offers a 5G Standalone on or off setting, that setting controls whether it can connect in SA mode.

 

What is the difference between 5G NSA and 5G SA?

5G Non-Standalone (NSA) adds 5G radio to an existing 4G network and core. 5G SA uses both 5G radio and a 5G core. A device may display 5G in either case, but SA supports the complete 5G architecture, including end-to-end network slicing and the 5G QoS framework.

 

What is an intelligent connected vehicle (ICV)?

An intelligent connected vehicle combines connectivity with sensors, software and onboard computing. It can exchange information with other vehicles, road infrastructure and cloud platforms while supporting driver assistance, automated driving and cooperative perception—the sharing of sensor information to help vehicles detect hazards beyond the range or line of sight of their own sensors. The term, intelligent connected vehicle, is widely used in China’s automotive standards and policy framework, but the concept applies globally.

 

Who are the leaders in intelligent connected vehicles?

There’s no official global ranking. Leadership in intelligent connected vehicles varies by technology and market. China is a major center of ICV development, with BYD, Geely, Xiaomi Auto and automakers participating in Huawei’s intelligent automotive ecosystem among the prominent players. Volkswagen, Tesla and BMW are also advancing intelligent and connected vehicle programs globally.

 

What are the top 5G SA network benefits for enterprises?

The five primary benefits are lower latency, network slicing, more flexible QoS controls, stronger identity and signaling protections and support for evolving 3GPP standards. These capabilities can benefit connected vehicles, industrial IoT and other applications that need differentiated network performance. However, the results depend on network coverage, device capabilities and service configuration.

 

How does 5G SA roaming work for connected vehicles?

With home-routed roaming, vehicle traffic passes through the visited network and returns to the home network before reaching its destination. This model can preserve centralized routing, policy enforcement and security visibility. Local breakout routes traffic through the visited network, which can reduce latency or help address local data requirements. The right approach depends on the performance, security and data-control needs of each market. The GSMA’s 5G roaming guidelines cover both architectures.

 

Why is 5G SA a requirement for vehicle programs in 2027 and beyond?

5G SA isn’t a universal legal requirement for every vehicle launching in 2027. However, OEM requests for proposals (RFP) requirements, operator roadmaps and the shift toward 4G/5G SA-capable modules are making SA readiness important for vehicles that may remain on the road for 10 to 15 years.

 

Separately, Commission Delegated Regulation (EU) 2024/1180 requires affected new vehicles to comply with packet-switched eCall standards beginning Jan. 1, 2027. Next Generation eCall can operate over 4G or 5G and doesn’t specifically require 5G SA. However, planning for both 4G LTE and 5G SA can support compliance while reducing the risk of future hardware replacement.