Telco Cloud Deployment Tracker: 5G core deep dive

Deep dive: 5G core deployments 

In this July 2022 update to STL Partners’ Telco Cloud Deployment Tracker, we present granular information on 5G core launches. They fall into three categories:

  • 5G Non-standalone core (5G NSA core) deployments: The 5G NSA core (agreed as part of 3GPP Release in December 2017), involves using a virtualised and upgraded version of the existing 4G core (or EPC) to support 5G New Radio (NR) wireless transmission in tandem with existing LTE services. This was the first form of 5G to be launched and still accounts for 75% of all 5G core network deployments in our Tracker.
  • 5G Standalone core (5G SA core) deployments: The SA core is a completely new and 5G-only core. It has a simplified, cloud-native and distributed architecture, and is designed to support services and functions such as network slicing, Ultra-Reliable Low-Latency Communications (URLLC) and enhanced Machine-Type Communications (eMTC, i.e. massive IoT). Our Tracker indicates that the upcoming wave of 5G core deployments in 2022 and 2023 will be mostly 5G SA core.
  • Converged 5G NSA/SA core deployments: this is when a dual-mode NSA and SA platform is deployed; in most cases, the NSA core results from the upgrade of an existing LTE core (EPC) to support 5G signalling and radio. The principle behind a converged NSA/SA core is the ability to orchestrate different combinations of containerised network functions, and automatically and dynamically flip over from an NSA to an SA configuration, in tandem – for example – with other features and services such as Dynamic Spectrum Sharing and the needs of different network slices. For this reason, launching a converged NSA/SA platform is a marker of a more cloud-native approach in comparison with a simple 5G NSA launch. Ericsson is the most commonly found vendor for this type of platform with a handful coming from Huawei, Samsung and WorkingGroupTwo. Albeit interesting, converged 5G NSA/SA core deployments remain a minority (7% of all 5G core deployments over the 2018-2023 period) and most of our commentary will therefore focus on 5G NSA and 5G SA core launches.

Enter your details below to request an extract of the report

75% of 5G cores are still Non-standalone (NSA)

Global 5G core deployments by type, 2018–23

  • There is renewed activity this year in 5G core launches since the total number of 5G core deployments so far in 2022 (effective and in progress) stands at 49, above the 47 logged in the whole of 2021. At the very least, total 5G deployments in 2022 will settle between the level of 2021 and the peak of 2020 (97).
  • 5G in whichever form now exists in most places where it was both in demand and affordable; but there remain large economies where it is yet to be launched: Turkey, Russia and most notably India. It also remains to be launched in most of Africa.
  • In countries with 5G, the next phase of launches, which will see the migration of NSA to SA cores, has yet to take place on a significant scale.
  • To date, 75% of all 5G cores are NSA. However, 5G SA will outstrip NSA in terms of deployments in 2022 and represent 24 of the 49 launches this year, or 34 if one includes converged NSA/SA cores as part of the total.
  • All but one of the 5G launches announced for 2023 are standalone; they all involve Tier-1 MNOs including Orange (in its European footprint involving Ericsson and Nokia), NTT Docomo in Japan and Verizon in the US.

The upcoming wave of SA core (and open / vRAN) represents an evolution towards cloud-native

  • Cloud-native functions or CNFs are software designed from the ground up for deployment and operation in the cloud with:​
  • Portability across any hardware infrastructure or virtualisation platform​
  • Modularity and openness, with components from multiple vendors able to be flexibly swapped in and out based on a shared set of compute and OS resources, and open APIs (in particular, via software ‘containers’)​
  • Automated orchestration and lifecycle management, with individual micro-services (software sub-components) able to be independently modified / upgraded, and automatically re-orchestrated and service-chained based on a persistent, API-based, ‘declarative’ framework (one which states the desired outcome, with the service chain organising itself to deliver the outcome in the most efficient way)​
  • Compute, resource, and software efficiency: as a concomitant of the automated, lean and logically optimal characteristics described above, CNFs are more efficient (both functionally and in terms of operating costs) and consume fewer compute and energy resources.​
  • Scalability and flexibility, as individual functions (for example, distributed user plane functions in 5G networks) can be scaled up or down instantly and dynamically in response to overall traffic flows or the needs of individual services​
  • Programmability, as network functions are now entirely based on software components that can be programmed and combined in a highly flexible manner in accordance with the needs of individual services and use contexts, via open APIs.​

Previous telco cloud tracker releases and related research

Each new release of the tracker is global, but is accompanied by an analytical report which focusses on trends in given regions from time to time:

Enter your details below to request an extract of the report

Telco Cloud: Why it hasn’t delivered, and what must change for 5G

Related Webinar – 5G Telco Clouds: Where we are and where we are headed

This research report will be expanded upon on our upcoming webinar 5G Telco Clouds: Where we are and where we are headed. In this webinar we will argue that 5G will only pay if telcos find a way to make telco clouds work. We will look to address the following key questions:

  • Why have telcos struggled to realise the telco cloud promise?
  • What do telcos need to do to unlock the key benefits?
  • Why is now the time for telcos to try again?

Join us on April 8th 16:00 – 17:00 GMT by using this registration link.

Telco cloud: big promises, undelivered

A network running in the cloud

Back in the early 2010s, the idea that a telecoms operator could run its network in the cloud was earth-shattering. Telecoms networks were complicated and highly-bespoke, and therefore expensive to build, and operate. What if we could find a way to run networks on common, shared resources – like the cloud computing companies do with IT applications? This would be beneficial in a whole host of ways, mostly related to flexibility and efficiency. The industry was sold.

In 2012, ETSI started the ball rolling when it unveiled the Network Functions Virtualisation (NFV) whitepaper, which borrowed the IT world’s concept of server-virtualisation and gave it a networking spin. Network functions would cease to be tied to dedicated pieces of equipment, and instead would run inside “virtual machines” (VMs) hosted on generic computing equipment. In essence, network functions would become software apps, known as virtual network functions (VNFs).

Because the software (the VNF) is not tied to hardware, operators would have much more flexibility over how their network is deployed. As long as we figure out a suitable way to control and configure the apps, we should be able to scale deployments up and down to meet requirements at a given time. And as long as we have enough high-volume servers, switches and storage devices connected together, it’s as simple as spinning up a new instance of the VNF – much simpler than before, when we needed to procure and deploy dedicated pieces of equipment with hefty price tags attached.

An additional benefit of moving to a software model is that operators have a far greater degree of control than before over where network functions physically reside. NFV infrastructure can directly replace old-school networking equipment in the operator’s central offices and points of presence, but the software can in theory run anywhere – in the operator’s private centralised data centre, in a datacentre managed by someone else, or even in a public hyperscale cloud. With a bit of re-engineering, it would be possible to distribute resources throughout a network, perhaps placing traffic-intensive user functions in a hub closer to the user, so that less traffic needs to go back and forth to the central control point. The key is that operators are free to choose, and shift workloads around, dependent on what they need to achieve.

The telco cloud promise

Somewhere along the way, we began talking about the telco cloud. This is a term that means many things to many people. At its most basic level, it refers specifically to the data centre resources supporting a carrier-grade telecoms network: hardware and software infrastructure, with NFV as the underlying technology. But over time, the term has started to also be associated with cloud business practices – that is to say, the innovation-focussed business model of successful cloud computing companies

Figure 2: Telco cloud defined: New technology and new ways of working

Telco cloud: Virtualised & programmable infrastructure together with cloud business practices

Source: STL Partners

In this model, telco infrastructure becomes a flexible technology platform which can be leveraged to enable new ways of working across an operator’s business. Operations become easier to automate. Product development and testing becomes more straightforward – and can happen more quickly than before. With less need for high capital spend on equipment, there is more potential for shorter, success-based funding cycles which promote innovation.

Much has been written about the vast potential of such a telco cloud, by analysts and marketers alike. Indeed, STL Partners has been partial to the same. For this reason, we will avoid a thorough investigation here. Instead, we will use a simplified framework which covers the four major buckets of value which telco cloud is supposed to help us unlock:

Figure 3: The telco cloud promise: Major buckets of value to be unlocked

Four buckets of value from telco cloud: Openness; Flexibility, visibility & control; Performance at scale; Agile service introduction

Source: STL Partners

These four buckets cover the most commonly-cited expectations of telcos moving to the cloud. Swallowed within them all, to some extent, is a fifth expectation: cost savings, which have been promised as a side-effect. These expectations have their origin in what the analyst and vendor community has promised – and so, in theory, they should be realistic and achievable.

The less-exciting reality

At STL Partners, we track the progress of telco cloud primarily through our NFV Deployment Tracker, a comprehensive database of live deployments of telco cloud technologies (NFV, SDN and beyond) in telecoms networks across the planet. The emphasis is on live rather than those running in testbeds or as proofs of concept, since we believe this is a fairer reflection of how mature the industry really is in this regard.

What we find is that, after a slow start, telcos have really taken to telco cloud since 2017, where we have seen a surge in deployments:

Figure 4: Total live deployments of telco cloud technology, 2015-2019
Includes NFVi, VNF, SDN deployments running in live production networks, globally

Telco cloud deployments have risen substantially over the past few years

Source: STL Partners NFV Deployment Tracker

All of the major operator groups around the world are now running telco clouds, as well as a significant long tail of smaller players. As we have explained previously, the primary driving force in that surge has been the move to virtualise mobile core networks in response to data traffic growth, and in preparation for roll-out of 5G networks. To date, most of it is based on NFV: taking existing physical core network functions (components of the Evolved Packet Core or the IP Multimedia Subsystem, in most cases) and running them in virtual machines. No operator has completely decommissioned legacy network infrastructure, but in many cases these deployments are already very ambitious, supporting 50% or more of a mobile operator’s total network traffic.

Yet, despite a surge in deployments, operators we work with are increasingly frustrated in the results. The technology works, but we are a long way from unlocking the value promised in Figure 2. Solutions to date are far from open and vendor-neutral. The ability to monitor, optimise and modify systems is far from ubiquitous. Performance is acceptable, but nothing to write home about, and not yet proven at mass scale. Examples of truly innovative services built on telco cloud platforms are few and far between.

We are continually asked: will telco cloud really deliver? And what needs to change for that to happen?

The problem: flawed approaches to deployment

Learning from those on the front line

The STL Partners hypothesis is that telco cloud, in and of itself, is not the problem. From a theoretical standpoint, there is no reason that virtualised and programmable network and IT infrastructure cannot be a platform for delivering the telco cloud promise. Instead, we believe that the reason it has not yet delivered is linked to how the technology has been deployed, both in terms of the technical architecture, and how the telco has organised itself to operate it.

To test this hypothesis, we conducted primary research with fifteen telecoms operators at different stages in their telco cloud journey. We asked them about their deployments to date, how they have been delivered, the challenges encountered, how successful they have been, and how they see things unfolding in the future.

Our sample includes individuals leading telco cloud deployment at a range of mobile, fixed and converged network operators of all shapes and sizes, and in all regions of the world. Titles vary widely, but include Chief Technology Officers, Heads of Technology Exploration and Chief Network Architects. Our criteria were that individuals needed to be knee-deep in their organisation’s NFV deployments, not just from a strategic standpoint, but also close to the operational complexities of making it happen.

What we found is that most telco cloud deployments to date fall into two categories, driven by the operator’s starting point in making the decision to proceed:

Figure 5: Two starting points for deploying telco cloud

Function-first "we need to virtualise XYZ" vs platform-first "we want to build a cloud platform"

Source: STL Partners

The operators we spoke to were split between these two camps. What we found is that the starting points greatly affect how the technology is deployed. In the coming pages, we will explain both in more detail.

Table of contents

  • Executive Summary
  • Telco cloud: big promises, undelivered
    • A network running in the cloud
    • The telco cloud promise
    • The less-exciting reality
  • The problem: flawed approaches to deployment
    • Learning from those on the front line
    • A function-first approach to telco cloud
    • A platform-first approach to telco cloud
  • The solution: change, collaboration and integration
    • Multi-vendor telco cloud is preferred
    • The internal transformation problem
    • The need to foster collaboration and integration
    • Standards versus blueprints
    • Insufficient management and orchestration solutions
    • Vendor partnerships and pre-integration
  • Conclusions: A better telco cloud is possible, and 5G makes it an urgent priority

NFV Deployment Tracker: North American data and trends

Introduction

NFV in North America – how is virtualisation moving forward in telcos against global benchmarks?

Welcome to the sixth edition of the ‘NFV Deployment Tracker’

This report is the sixth analytical report in the NFV Deployment Tracker series and is intended as an accompaniment to the updated Tracker Excel spreadsheet.

This extended update covers seven months of deployments worldwide, from October 2018 to April 2019. The update also includes an improved spreadsheet format: a more user-friendly, clearer lay-out and a regional toggle in the ‘Aggregate data by region’ worksheet, which provides much quicker access to the data on each region separately.

The present analytical report provides an update on deployments and trends in the North American market (US, Canada and the Caribbean) since the last report focusing on that region (December 2017).

Scope, definitions and importance of the data

We include in the Tracker only verified, live deployments of NFV or SDN technology powering commercial services. The information is taken mainly from public-domain sources, such as press releases by operators or vendors, or reports in reputable trade media. However, a small portion of the data also derives from confidential conversations we have had with telcos. In these instances, the deployments are included in the aggregate, anonymised worksheets in the spreadsheet, but not in the detailed dataset listing deployments by operator and geography, and by vendor where known.

Our definition of a ‘deployment’, including how we break deployments down into their component parts, is provided in the ‘Explanatory notes’ worksheet, in the accompanying Excel document.

NFV in North America in global context

We have gathered data on 120 live, commercial deployments of NFV and SDN in North America between 2011 and April 2019. These were completed by 33 mainly Tier-One telcos and telco group subsidiaries: 24 based in the US, four in Canada, one Caribbean, three European (Colt, T-Mobile and Vodafone), and one Latin American (América Móvil). The data includes information on 217 known Virtual Network Functions (VNFs), functional sub-components and supporting infrastructure elements that have formed part of these deployments.

This makes North America the third-largest NFV/SDN market worldwide, as is illustrated by the comparison with other regions in the chart below.

Total NFV/SDN deployments by region, 2011 to April 2019

total NFV deployments by region North America Africa Asia-Pacific Europe Middle East

Source: STL Partners

Deployments of NFV in North America account for around 24% of the global total of 486 live deployments (or 492 deployments counting deployments spanning multiple regions as one deployment for each region). Europe is very marginally ahead on 163 deployments versus 161 for Asia-Pacific: both equating to around 33% of the total.

The NFV North America Deployment Tracker contains the following data, to May 2019:

  • Global aggregate data
  • Deployments by primary purpose
  • Leading VNFs and functional components
  • Leading operators
  • Leading vendors
  • Leading vendors by primary purpose
  • Above data points broken down by region
  • North America
  • Asia-Pacific
  • Europe
  • Latin America
  • Middle East
  • Africa
  • Detailed dataset on individual deployments

 

Contents of the accompanying analytical report:

  • Executive Summary
  • Introduction
  • Welcome to the sixth edition of the ‘NFV Deployment Tracker’
  • Scope, definitions and importance of the data
  • Analysis of NFV in North America
  • The North American market in global context
  • SD-WAN and core network functions are the leading categories
  • 5G is driving core network virtualisation
  • Vendor trends: Open source and operator self-builds outpace vendors
  • Operator trends: Verizon and AT&T are the clear leaders
  • Conclusion: Slow-down in enterprise platform deployments while 5G provides new impetus