Ericsson CEO’s strong statements on 5G SA, WRC 27, and AI in networks

At the Technology Policy Institute Forum in Aspen, Colorado this week, Ericsson CEO Börje Ekholm made many comments about “The Future of Wireless & Global Connectivity.”  To begin with, he said it’s super critical for western nations, including the U.S., to increase their 5G Stand Alone (SA) network deployments.  5G network operators need 5G SA to take full advantage of the platform to support apps and services that are optimized for low latency, higher uplink prioritization and network slicing. “It’s hard to monetize something you don’t have,” Ekholm said. “The network has to be built for 5G SA.”

Ekholm’s 5G SA comments echo those of Magnus Ewerbring, Ericsson’s chief technology officer – Asia Pacific, who strongly asserted that 5G SA is the way for wireless network operators to monetize and differentiate their 5G networks. 

Ekholm noted that China has prioritized 5G SA and has more than 4 million base stations deployed, estimating that this represents about ten times what’s been deployed in the US. China has been able to monetize that by supporting advanced robotics and automation in tens of thousands of factories. China is “highly competitive,” has “enormous scale, domestically,” and has made 5G SA a priority, the Ericsson CEO said.  Western countries needs to take China’s 5G SA efforts “seriously” and invest more in their wireless infrastructure as it’s a competitive imperative. 

Status of 5G SA network deployments:

A recent Heavy Reading (now part of Omdia) operator survey found that 35% of respondents said they have deployed 5G SA, with 20% expecting to be live by year-end. Some 41% cited “new or better services” as the primary driver for 5G core investment.

After a very slow start during the past five years, Téral Research says the migration to 5G SA has increased.  Of the total 354 commercially available 5G public networks reported at the end of 1Q25, 74 are 5G SA –  up from 49 one year ago.  This growth is being driven by the success of fixed wireless access (FWA), a wider range of 5G SA-compatible devices, and the rise of voice over new radio (VoNR). Téral is also seeing increased adoption of private cloud for SA core deployments, with data sovereignty concerns shaping CSP strategies. Network slicing, which requires 5G SA, is moving from theory to practice—now extending to critical use cases like military applications.

3GPP URLC specifications are still not finalized and approved:

It should be noted that the 3GPP specifications for URLLC (Ultra-Reliable Low-Latency Communication) in the 5G SA core network and 5G NR access network are not considered 100% completed or finalized. URLLC relies on both the 5G NR (Radio Access Network) and the 5G Core network to achieve its goals. URLLC is vital for various industrial applications requiring real-time control and automation, such as the Industrial Internet of Things (IIoT), virtual reality, and autonomous vehicles. 

3GPP Release 16 introduced significant enhancements for URLLC in the 5G New Radio (NR) access and 5G Core network. While Release 16 was “frozen” in July 2022, work on URLLC enhancements, particularly in the Radio Access Network (RAN), was not fully completed. These enhancements are crucial for 3GPP NR to meet the ITU-R M.2410 minimum performance requirements for URLLC for ultra-high reliability and ultra low latency.

 3GPP Technical Specifications (TS) and Technical Reports (TR) become “official” standards when transposed into corresponding publications of the 3GPP Organizational Partner (like ETSI)  or the standards body ((ITU-R)) acting as publisher for the Partner (ATIS for ITU-R). Once a Release is frozen (see definition in TR 21.900) and all work items completed, 3GPP specifications are officially transposed and published by the Organizational Partners, as a part of their standards series.

………………………………………………………………………………………………………………………………………………………………………..

Ekholm also said that strong western representation at ITU-R’s WRC-27 “is critically important.”  That’s because licensed spectrum is likewise critical for the next generation of automation, self-driving vehicles and AI applications that will require a “truly reliable” and low-latency network, he added without mentioning the incomplete 3GPP URLLC specs.

AI is the most fundamental technology we’ve seen so far,” he said. Ericsson has already been able to generate a 10% boost in spectrum efficiency using AI tools. While AI will no doubt erase some jobs, he’s also optimistic it will create new ones.  Like so many analysts, Ekholm expects  Gen AI to drive more traffic and new capabilities. “The criticality of the connectivity layer will become even more important,” he added.

References:

https://www.lightreading.com/5g/ericsson-ceo-calls-for-bigger-push-toward-5g-sa

https://www.tpiaspenforum.tech/agenda

Ericsson reports ~flat 2Q-2025 results; sees potential for 5G SA and AI to drive growth

Ookla: Uneven 5G deployment in Europe, 5G SA remains sluggish; Ofcom: 28% of UK connections on 5G with only 2% 5G SA

Ookla: Europe severely lagging in 5G SA deployments and performance

Téral Research: 5G SA core network deployments accelerate after a very slow start

Vision of 5G SA core on public cloud fails; replaced by private or hybrid cloud?

Latest Ericsson Mobility Report talks up 5G SA networks and FWA

3GPP Release 16 5G NR Enhancements for URLLC in the RAN & URLLC in the 5G Core network

 

2 thoughts on “Ericsson CEO’s strong statements on 5G SA, WRC 27, and AI in networks

  1. 3GPP Release 18 indicates the completion of several normative URLLC-related features, but this refers to additional enhancements (such as timing resiliency and tighter scheduling for low latency) rather than the full, original Release 16 URLLC requirements in the RAN spec being declared 100% finished.

    Since robust synchronization and low latency are always the main goal of service providers, positive expectation is held for this feature with respect to further applications, especially with the fast uptake of more diverse services requiring ultra-low latency in future.

    https://www.3gpp.org/technologies/ran3-rel-18

  2. From Heavy Reading:

    5G standalone (SA) deployments are becoming more widespread, but identifying the services potential for 5G SA remains a challenge. While 5G SA provides the opportunity to access new or better 5G services, such as RedCap and network slicing, service providers continue to grapple with how best to package 5G SA services and communicate the value of 5G SA to consumers and enterprise customers.

    Gabriel Brown of Heavy Reading likens the difference between 5G non-standalone and 5G SA to driving a 20-year-old car in good condition to a newer model vehicle. Or, using a five-year-old iPhone versus the iPhone 16. In both cases, the older model will do the job required but there’s a stark difference in the features of the latest model.

    “You’re not going to notice a few milliseconds of difference on your phone but I think incrementally we’re going to see basically better service,” says Brown.

    The big Chinese (state owned) network operators and T-Mobile have been running 5G SA at scale for years, he adds. In addition, Reliance Jio in India is running a huge 5G SA network and has ten network slice types available in commercial operations, and EE in the UK has reached 50% population coverage for 5G SA. There’s plenty of evidence that 5G SA deployments at scale are doable so that supports a forecast of broader adoption, Brown.

    In Heavy Reading’s 2025 5G SA Core Operator Survey, 35% of respondents said 5G SA is already generally available nationwide in their company’s wide area network, and 20% said it would be generally available by the end of the year.

    During the podcast, Brown also explains the difference between 5G SA and 5G Advanced.
    https://www.lightreading.com/5g/5g-standalone-deployments-are-scaling-now-comes-the-hard-part

Leave a Reply to Alan Weissberger Cancel Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*