Tag: CNF

The Telco Cloud Manifesto 2.0

Nearly two years on from our first Telco Cloud Manifesto published in March 2021, we are even more convinced that going through the pain of learning how to orchestrate and manage network workloads in a cloud-native environment is essential for telcos to successfully create new business models, such as Network-as-a-Service in support of edge compute applications.

Since the first Manifesto, hyperscalers have emerged as powerful partners and enablers for telcos’ technology transformation. But telcos that simply outsource to hyperscalers the delivery and management of their telco cloud, and of the multi-vendor, virtualised network functions that run on it, will never realise the true potential of telco cloudification. By contrast, evolving and maintaining an ability to orchestrate and manage multi-vendor, virtualised network functions end-to-end across distributed, multi-domain and multi-vendor infrastructure represents a vital control point that telcos should not surrender to the hyperscalers and vendors. Doing so could relegate telcos to a role as mere physical connectivity and infrastructure providers helping to deliver services developed, marketed and monetised by others.

In short, operators must take on the ‘workload’ of transforming into and acting as cloud-centric organisations before they shift their ‘workloads’ to the hyperscale cloud. In this updated Manifesto, we outline why, and what telcos at different stages of maturity should prioritise.

Two developments have taken place since the publication of our first manifesto that have changed the terms on which telcos are addressing network cloudification:

  • Hyperscale cloud providers have increasingly developed capabilities and commercial offers in the area of telco cloud. To telcos uncertain about the strategy and financial implications of the next phase of their investments, the hyperscalers appear to offer a shortcut to telco cloud: the possibility of avoiding doing all the hard yards of developing the private telco cloud, and of evolving the internal skills and processes for deploying and managing multi-vendor VNFs / CNFs over it. Instead, the hyperscalers offer the prospect of getting telco cloud and VNFs / CNFs on an ‘as-a-Service’ basis – fundamentally like any other cloud service.
  • In April 2021, DISH announced it would build its greenfield 5G network with AWS providing much of the virtual infrastructure layer and all of the physical cloud infrastructure. In June 2021, AT&T sold its private telco cloud platform to Microsoft Azure. In both instances, the telcos involved are now deploying mobile core network functions and, in DISH’s case, all of the software-based functions of its on a hyperscale cloud. These events appear superficially to set an example validating the idea of outsourcing telco cloud to the hyperscalers. After all, AT&T had previously been a champion of the DIY approach to telco cloud but now looked as though it had thrown in the towel and gone all in with outsourcing its cloud from Azure.

Two main questions arise from these developments, which we address in detail in this second Manifesto:

  • Should telcos embarked or embarking on a Pathway 2 strategy outsource their telco cloud infrastructure and procure their critical network functions – in whole or in part – from one or more hyperscalers, on an as-a-Service basis?
  • What is the broader significance of AT&T’s and DISH’s moves? Does it represent the logical culmination of telco cloudification and, if so, what are the technological and business-model characteristics of the ‘infrastructure-independent, cloud-native telco’, as we define this new Pathway 4? Finally, is this a model that all Pathway 3 players – and even all telcos per se – should ultimately seek to emulate?

In this second Manifesto, we also propose an updated version of our pathways describing telco network cloudification strategies for different sizes and types of telco to implement telco cloud. We now have four pathways (we had three in the original Manifesto), as illustrated in the figure below.

The four telco cloud deployment pathways in STL’s Telco Cloud Manifesto 2.0

Source: STL Partners, 2023

Existing subscribers can download the Manifesto at the top of this page. Everyone else, please go here.

If you wish to speak to us about our new Manifesto, please book a call.

Table of contents

  • Executive Summary
    • Recommendations
  • Pathway 1: No way back
    • Two constituencies at operators: Cloud sceptics and cloud advocates
  • Pathway 2: Hyperscalers – friend or foe?
    • Cloud-native network functions are a vital control point telcos must not relinquish
  • Pathway 3: Build own telco cloud competencies before deploying on public cloud
    • AT&T and DISH are important proof points but not applicable to the industry as a whole
    • But telcos will not realise the full benefits of telco cloud unless they, too, become software and cloud businesses
  • Pathway 4: The path to Network-as-a-Service
    • Pathway 4 networks will enable Network-as-a-Service
  • Conclusion: Mastery of cloud-native is key for telcos to create value in the Coordination Age

Related research

Our telco cloud research aligned to this topic includes:

 

Capturing the 5G SA opportunity: towards a multi-vendor approach

The 5G SA opportunity

5G SA is an exciting prospect for telecoms operators. With many operators’ revenues from traditional connectivity beginning to stagnate, or even decline, there is increased pressure for operators to create differentiation and offer new services, including by expanding across the value chain from connectivity-only providers.

STL Partners has described this new era, whereby operators must shift their business models to adapt to the new demands, as the Coordination Age 2. From the 1850s until around 1990, the Communications Age enabled people to communicate over long distances via telephony. Next came the Information Age, in which people could directly access content and applications, increasingly provided by non-telecommunications players. In the Coordination Age, ‘things’ are increasingly connecting to other ‘things’, leading to an exponential increase in volumes of data, but thanks to advanced analytics and artificial intelligence (AI) we can also address some of the most pressing issues facing the world today: ensuring resource efficiency and improving productivity to help us to do more with less.

Operators need to define their role in the emerging coordination age


Source: STL Partners

Transitioning to the Coordination Age requires operators to shift their goals and business models accordingly. Operators will need to offer or enable tightly coupled network services and applications to different industries, and continue to refresh, optimise and scale at an unprecedented rate.

Enter your details below to download an extract of the report

The transformative potential of 5G SA

5G SA, in comparison to its NSA counterpart, is the evolution of 5G that can deliver on the promises associated with the next generation of cellular networking. 5G SA is intended to be cloud native and adopt cloud-native principles. Without SA, 5G networks are less able to quickly launch new services, enable new use cases, or introduce more scalable, automated operating models.

The opportunities to which 5G SA is expected to give rise have been explored extensively in previous STL research. The ‘full potential’ of 5G SA includes promises around higher throughput, greater capacity, the ability to leverage enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine type communications (mMTC). In summary; do more (including enabling more connections at any given time), faster (down to a latency of a few milliseconds) and at a lower cost (through a variety of actors, including lower power consumption than 4G). These new capabilities are exciting for operators: enabling operators to develop powerful new applications for their customers with truly differentiated use cases.

One particular opportunity that 5G SA represents is network slicing. Slicing can be defined as ‘a mechanism to create and dynamically manage functionally discrete, virtualised networks over a common infrastructure,’ and has been the subject of several STL reports. The increased flexibility and agility of network slicing can enable operators to provide unique policies and differentiated services to their enterprise customers and recoup the substantial investments that rolling out 5G SA requires. However, the benefits and opportunities of 5G SA have implications far beyond the new services it can enable. For the first time, 5G is cloud-native by design, with modular service-based architecture giving
rise to greater flexibility and programmability. Furthermore, it leverages IT concepts of virtualization, cloudification, and DevOps processes. This does not so much enable as actively encourage a more agile operating model. Some of the exciting features of 5G SA include:

  • Automation – Increased automation throughout the network, including deployment, orchestration, assurance, and optimisation can give rise to “zero touch” networks that do not require human intervention, and can self repair and update autonomously on an ongoing basis. The aim of network automation is to reduce human error and the time taken to resolve issues through closed-loop network assurance.
  • Disaggregation – Relies on an open standard network operating system whereby different functional components of networking equipment can be deployed individually and then combined in a modular, fit for purpose way, to suit the requirements of an operator’s network. This architecture relies on the interworking between the multi-vendor components within the 5G core. Disaggregation can allow vendors to offer best in class capabilities for each individual component, providing operators with unprecedented choice and customizability.
  • Avoiding vendor lock-in through a diversified supply base – One of the key benefits of a disaggregated approach to the 5G core is to break vendor lock-in that has tended to dominate legacy approaches. Vendor lock-in can be a key limitation on the speed of innovation and service deployment.
  • Agility – Adopting a continuous improvement and development means accelerated innovation and speed of deployment. A software-orientated infrastructure can enable changes in business processes such as product development management to happen at a greater pace and speed time to market for new revenue generating products and features.
  • Scalability through adopting ‘hyperscale economics’ – Explored by STL Partners in previous research, this term describes the emulation of business and software practices developed by hyperscalers to deliver service innovation at scale whilst simultaneously reducing the level of capex relative to revenue.

Cloud native is the only way to truly unlock the benefits of 5G thanks to the automation, efficiency,
optimisation and mode of delivery that it enables. Ultimately, it allows operators to maximise the
opportunity of 5G to develop differentiated services to consumer and enterprises customers.

 

Table of Contents:

  • Executive Summary
    • Recommendations
  • Preface
  • The 5G SA opportunity
    • The transformative potential of 5G SA
    • 5G SA requires operators to develop and foster a new set of skills
    • Some open questions remain around 5G SA
  • The early adopter 5G SA landscape
    • Orange
    • Vodafone
    • Dish
  • Tier 2 and Tier 3 operator approaches to 5G SA
    • Adherents to a single vendor approach
    • Proponents of a multi-vendor approach
    • Several factors can influence an operators’ vendor strategy
  • Recommendations

Related research

Enter your details below to download an extract of the report

Telco Cloud Deployment Tracker: Will vRAN eclipse pure open RAN?

Is vRAN good enough for now?

In this October 2022 update to STL Partners’ Telco Cloud Deployment Tracker, we present data and analysis on progress with deployments of vRAN and open RAN. It is fair to say that open RAN (virtualised AND disaggregated RAN) deployments have not happened at the pace that STL Partners and many others had forecast. In parallel, some very significant deployments and developments are occurring with vRAN (virtualised NOT disaggregated RAN). Is open RAN a networking ideal that is not yet, or never will be, deployed in its purest form?

In our Telco Cloud Deployment Tracker, we track deployments of three types of virtualised RAN:

  1. Open RAN / O-RAN: Open, disaggregated, virtualised / cloud-native, with baseband (BU) functions distributed between a Central Unit (CU: control plane functions) and Distributed Unit (DU: data plane functions)
  2. vRAN: Virtualised and distributed CU/DU, with open interfaces but implemented as an integrated, single-vendor platform
  3. Cloud RAN (C-RAN): Single-vendor, virtualised / centralised BU, or CU only, with proprietary / closed interfaces

Cloud RAN is the most limited form of virtualised RAN: it is based on porting part or all of the functionality of the legacy, appliance-based BU into a Virtual Machine (VM). vRAN and open RAN are much more significant, in both technology and business-model terms, breaking open all parts of the RAN to more competition and opportunities for innovation. They are also cloud-native functions (CNFs) rather than VM-based.

Enter your details below to request an extract of the report

2022 was meant to be the breakthrough year for open RAN: what happened?

  • Of the eight deployments of open RAN we were expecting to go live in 2022 (shown in the chart below), only three had done so by the time of writing.
  • Two of these were on the same network: Altiostar and Mavenir RAN platforms at DISH. The other was a converged Parallel Wireless 2G / 3G RAN deployment for Orange Central African Republic.
  • This is hardly the wave of 5G open RAN, macro-network roll-outs that the likes of Deutsche Telekom, Orange, Telefónica and Vodafone originally committed to for 2022. What has gone wrong?
  • Open RAN has come up against a number of thorny technological and operational challenges, which are well known to open RAN watchers:
    • integration challenges and costs
    • hardware performance and optimisation
    • immature ecosystem and unclear lines of accountability when things go wrong
    • unproven at scale, and absence of economies of scale
    • energy efficiency shortcomings
    • need to transform the operating model and processes
    • pressured 5G deployment and Huawei replacement timelines
    • absence of mature, open, horizontal telco cloud platforms supporting CNFs.
  • Over and above these factors, open RAN is arguably not essential for most of the 5G use cases it was expected to support.
  • This can be gauged by looking at some of the many open RAN trials that have not yet resulted in commercial deployments.

Global deployments of C-RAN, vRAN and open RAN, 2016 to 2023

Image shows global deployments of C-RAN, vRAN and open RAN, 2016 to 2023

Source: STL Partners

Previous telco cloud tracker releases and related research

Enter your details below to request an extract of the report

5G standalone (SA) core: Why and how telcos should keep going

Major 5G Standalone deployments are experiencing delays…

There is a widespread opinion among telco industry watchers that deployments of the 5G Standalone (SA) core are taking longer than originally expected. It is certainly the case that some of the world’s leading operators, and telco cloud innovators, are taking their time over these deployments, as illustrated below:

  • AT&T: Has no current, publicly announced deadline for launching its 5G SA core, which was originally expected to be deployed in mid-2021.
  • Deutsche Telekom: Launched an SA core in Germany on a trial basis in September 2022, having previously acknowledged that SA was taking longer than originally expected. In Europe, the only other opco that is advancing towards commercial deployment is Magenta Telekom in Austria. In 2021, the company cited various delay factors, such as 5G SA not being technically mature enough to fulfil customers’ expectations (on speed and latency), and a lack of consumer devices supporting 5G SA.
  • Rakuten Mobile: Was expected to launch an SA core co-developed with NEC in 2021. But at the time of writing, this had still not launched.
  • SK Telecom: Was originally expected to launch a Samsung-provided SA core in 2020. However, in November 2021, it was announced that SK Telecom would deploy an Ericsson converged Non-standalone (NSA) / SA core. By the time of writing, this had still not taken place.
  • Telefónica: Has carried out extensive tests and pilots of 5G SA to support different use cases but has no publicly announced timetable for launching the technology commercially.
  • Verizon: Originally planned to launch its SA core at the end of 2021. But this was pushed back to 2022; and recent pronouncements by the company indicate a launch of commercial services over the SA core only in 2023.
  • Vodafone: Has launched SA in Germany only, not in any of its other markets; and even then, nationwide SA coverage is not expected until 2025. An SA core is, however, expected to be launched in Portugal in the near future, although no definite deadline has been announced. A ‘commercial pilot’ in three UK cities, launched in June 2021, had still not resulted in a full commercial deployment by the time of writing.

…but other MNOs are making rapid progress

In contrast to the above catalogue of delay, several other leading operators have made considerable progress with their standalone deployments:

  • DISH: Launched its SA core- and open RAN-based network in the US, operated entirely over the AWS cloud, in May 2022. The initial population coverage of the network was required to be 20%. This is supposed to rise to 70% by June 2023.
  • Orange: Proceeding with a Europe-wide roll-out, with six markets expected to go live with SA cores in 2023.
  • Saudi Telecom Company (STC): Has launched SA services in two international markets, Kuwait (May 2021) and Bahrain (May 2022). Preparations for a launch in Saudi Arabia were ongoing at the time of writing.
  • Telekom Austria Group (A1): Rolling out SA cores across four markets in Central Europe (Bulgaria, Croatia, Serbia and Slovenia), although no announcement has been made regarding a similar deployment in its home market of Austria. In June 2022, A1 also carried out a PoC of end-to-end, SA core-enabled network slicing, in partnership with Amdocs.
  • T-Mobile US: Has reportedly migrated all of its mobile broadband traffic over to its SA core, which was launched back in 2020. It also launched one of the world’s first voice-over-New Radio (VoNR) services, run over the SA core, in parts of two cities in June 2022.
  • Zain (Kuwait): Launched SA in Saudi Arabia in February 2022, while a deployment in its home market was ongoing at the time of writing.
  • There are also a number of trials, and prospective and actual deployments, of SA cores over the public cloud in Europe. These are serving the macro network, not edge or private-networking use cases. The most notable examples include Magenta Telekom (Deutsche Telekom’s Austrian subsidiary, partnering with Google Cloud); Swisscom (partnering with AWS); and Working Group Two (wgtwo) – a Cisco and Telenor spin-off – that offers a multi-tenant, cloud-native 5G core delivered to third-party MNOs and MVNOs via the AWS cloud.
  • The three established Chinese MNOs are all making rapid progress with their 5G SA roll-outs, having launched in either 2020 (China Telecom and China Unicom) or 2021 (China Mobile). The country’s newly launched, fourth national player, Broadnet, is also rolling out SA. However, it is not publicly known what share of the country’s reported 848 million-odd 5G subscribers (at March 2022) were connected to SA cores.
  • At least eight other APAC operators had launched 5G SA-based services by July 2022, including KT in South Korea, NTT Docomo and SoftBank in Japan and Smart in the Philippines.

Enter your details below to request an extract of the report

Many standalone deployments in the offing – but few fixed deadlines

So, 5G standalone deployments are definitely a mixed bag: leading operators in APAC, Europe, the Middle East and North America are deploying and have launched at scale, while other leading players in the same regions have delayed launches, including some of the telcos that have helped drive telco cloud as a whole over the past few years, e.g. AT&T, Deutsche Telekom, Rakuten, Telefónica and Vodafone.

In the July 2022 update to our Telco Cloud Deployment Tracker, which contained a ‘deep dive’ on 5G core roll-outs, we presented an optimistic picture of 5G SA deployments. We pointed out that the number of SA and converged NSA / SA cores. We expect to be launched in 2022 outnumbered the total of NSA deployments. However, as illustrated in the figure below, SA and converged NSA/SA cores are still the minority of all 5G cores (29% in total).

We should also point out that some of the SA and converged NSA / SA deployments shown in the figure below are still in progress and some will continue to be so in 2023. In other words, the launch of these core networks has been announced and we have therefore logged them in our tracker, but we expect that the corresponding deployments will be completed in the remainder of 2022 or in 2023, based on a reasonable, typical gap between when the deployments are publicly announced and the time it normally takes to complete them. If, however, more of these predicted deployments are delayed as per the roll-outs of some of leading players listed above, then we will need to revise down our 2022 and 2023 totals.

Global 5G core networks by type, 2018 to 2023

 

Source: STL Partners

Table of contents

  • Executive Summary
  • Introduction
    • Major 5G Standalone deployments are experiencing delays
    • …but other MNOs are making rapid progress
    • Many SA deployments in the offing – but few fixed deadlines
  • What is holding up deployments?
    • Mass-market use cases are not yet mature
    • Enterprise use cases exploiting an SA core are not established
    • Business model and ROI uncertainty for 5G SA
    • Uncertainty about the role of hyperscalers
    • Coordination of investments in 5G SA with those in open RAN
    • MNO process and organisation must evolve to exploit 5G SA
  • 5G SA progress will unlock opportunities
    • Build out coverage to improve ‘commodity’ services
    • Be first to roll out 5G SA in the national market
    • For brownfield deployments, incrementally evolve towards SA
    • Greenfield deployments
    • Carefully elaborate deployment models on hyperscale cloud
    • Work through process and organisational change
  • Conclusion: 5G SA will enable transformation

    Related research

    Previous STL Partners reports aligned to this topic include:

  • Telco Cloud Deployment Tracker: 5G core deep dive
  • Telco cloud: short-term pain, long-term gain
  • Telco Cloud Deployment Tracker: 5G standalone and RAN

Enter your details below to request an extract of the report

VNFs on public cloud: Opportunity, not threat

VNF deployments on the hyperscale cloud are just beginning

Numerous collaboration agreements between hyperscalers and leading telcos, but few live VNF deployments to date

The past three years have seen many major telcos concluding collaboration agreements with the leading hyperscalers. These have involved one or more of five business models for the telco-hyperscaler relationship that we discussed in a previous report, and which are illustrated below:

Five business models for telco-hyperscaler partnerships

Source: STL Partners

In this report, we focus more narrowly on the deployment, delivery and operation by and to telcos of virtualised and cloud-native network functions (VNFs / CNFs) over the hyperscale public cloud. To date, there have been few instances of telcos delivering live, commercial services on the public network via VNFs hosted on the public cloud. STL Partners’ Telco Cloud Deployment Tracker contains eight examples of this, as illustrated below:

Major telcos deploying VNFs in the public cloud

Source: STL Partners

Enter your details below to request an extract of the report

Telcos are looking to generate returns from their telco cloud investments and maintain control over their ‘core business’

The telcos in the above table are all of comparable stature and ambition to the likes of AT&T and DISH in the realm of telco cloud but have a diametrically opposite stance when it comes to VNF deployment on public cloud. They have decided against large-scale public cloud deployments for a variety of reasons, including:

  • They have invested a considerable amount of money, time and human resources on their private clouddeployments, and they want and need to utilise the asset and generate the RoI.
  • Related to this, they have generated a large amount of intellectual property (IP) as a result of their DIY cloud– and VNF-development work. Clearly, they wish to realise the business benefits they sought to achieve through these efforts, such as cost and resource efficiencies, automation gains, enhanced flexibility and agility, and opportunities for both connectivityand edge compute service innovation. Apart from the opportunity cost of not realising these gains, it is demoralising for some CTO departments to contemplate surrendering the fruit of this effort in favour of a hyperscaler’s comparable cloud infrastructure, orchestration and management tools.
  • In addition, telcos have an opportunity to monetise that IP by marketing it to other telcos. The Rakuten Communications Platform (RCP) marketed by Rakuten Symphony is an example of this: effectively, a telco providing a telco cloud platform on an NFaaS basis to third-party operators or enterprises – in competition to similar offerings that might be developed by hyperscalers. Accordingly, RCP will be hosted over private cloud facilities, not public cloud. But in theory, there is no reason why RCP could not in future be delivered over public cloud. In this case, Rakuten would be acting like any other vendor adapting its solutions to the hyperscale cloud.
  • In theory also, telcos could also offer their private telcoclouds as a platform, or wholesale or on-demand service, for third parties to source and run their own network functions (i.e. these would be hosted on the wholesale provider’s facilities, in contrast to the RCP, which is hosted on the client telco’s facilities). This would be a logical fit for telcos such as BT or Deutsche Telekom, which still operate as their respective countries’ communications backbone provider and primary wholesale provider

BT and Deutsche Telekom have also been among the telcos that have been most visibly hostile to the idea of running NFs powering their own public, mass-market services on the public and hyperscale cloud. And for most operators, this is the main concern making them cautious about deploying VNFs on the public cloud, let alone sourcing them from the cloud on an NFaaS basis: that this would be making the ‘core’ telco business and asset – the network – dependent on the technology roadmaps, operational competence and business priorities of the hyperscalers.

Table of contents

  • Executive Summary
  • Introduction: VNF deployments on the hyperscale cloud are just beginning
    • Numerous collaboration agreements between hyperscalers and leading telcos, but few live VNF deployments to date
    • DISH and AT&T: AWS vs Azure; vendor-supported vs DIY; NaaCP vs net compute
  • Other DIY or vendor-supported best-of-breed players are not hosting VNFs on public cloud
    • Telcos are looking to generate returns from their telco cloud investments and maintain control over their ‘core business’
    • The reluctance to deploy VNFs on the cloud reflects a persistent, legacy concept of the telco
  • But NaaCP will drive more VNF deployments on public cloud, and opportunities for telcos
    • Multiple models for NaaCP present prospects for greater integration of cloud-native networks and public cloud
  • Conclusion: Convergence of network and cloud is inevitable – but not telcos’ defeat
  • Appendix

Related Research

 

Enter your details below to request an extract of the report

Why and how to go telco cloud native: AT&T, DISH and Rakuten

The telco business is being disaggregated

Telcos are facing a situation in which the elements that have traditionally made up and produced their core business are being ‘disaggregated’: broken up into their component parts and recombined in different ways, while some of the elements of the telco business are increasingly being provided by players from other industry verticals.

By the same token, telcos face the pressure – and the opportunity – to combine connectivity with other capabilities as part of new vertical-specific offerings.

Telco disaggregation primarily affects three interrelated aspects of the telco business:

  1. Technology:
    • ‘Vertical’ disaggregation: separating out of network functions previously delivered by dedicated, physical equipment into software running on commodity computing hardware (NFV, virtualisation)
    • ‘Horizontal’ disaggregation: breaking up of network functions themselves into their component parts – at both the software and hardware levels; and re-engineering, recombining and redistributing of those component parts (geographically and architecturally) to meet the needs of new use cases. In respect of software, this typically involves cloud-native network functions (CNFs) and containerisation
    • Open RAN is an example of both types of disaggregation: vertical disaggregation through separation of baseband processing software and hardware; and horizontal disaggregation by breaking out the baseband function into centralised and distributed units (CU and DU), along with a separate, programmable controller (RAN Intelligent Controller, or RIC), where all of these can in theory be provided by different vendors, and interface with radios that can also be provided by third-party vendors.
  2. Organisational structure and operating model: Breaking up of organisational hierarchies, departmental siloes, and waterfall development processes focused on the core connectivity business. As telcos face the need to develop new vertical- and client-specific services and use cases beyond the increasingly commoditised, low-margin connectivity business, these structures are being – or need to be – replaced by more multi-disciplinary teams taking end-to-end responsibility for product development and operations (e.g. DevOps), go-to-market, profitability, and technology.

Transformation from the vertical telco to the disaggregated telco

3. Value chain and business model: Breaking up of the traditional model whereby telcos owned – or at least had end-to-end operational oversight over – . This is not to deny that telcos have always relied on third party-owned or outsourced infrastructure and services, such as wholesale networks, interconnect services or vendor outsourcing. However, these discrete elements have always been welded into an end-to-end, network-based services offering under the auspices of the telco’s BSS and OSS. These ensured that the telco took overall responsibility for end-to-end service design, delivery, assurance and billing.

    • The theory behind this traditional model is that all the customer’s connectivity needs should be met by leveraging the end-to-end telco network / service offering. In practice, the end-to-end characteristics have not always been fully controlled or owned by the service provider.
    • In the new, further disaggregated value chain, different parts of the now more software-, IT- and cloud-based technology stack are increasingly provided by other types of player, including from other industry verticals. Telcos must compete to play within these new markets, and have no automatic right to deliver even just the connectivity elements.

All of these aspects of disaggregation can be seen as manifestations of a fundamental shift where telecoms is evolving from a utility communications and connectivity business to a component of distributed computing. The core business of telecoms is becoming the processing and delivery of distributed computing workloads, and the enablement of ubiquitous computing.

Enter your details below to request an extract of the report

Telco disaggregation is a by-product of computerisation

Telco industry disaggregation is part of a broader evolution in the domains of technology, business, the economy, and society. This evolution comprises ‘computerisation’. Computing analyses and breaks up material processes and systems into a set of logical and functional sub-components, enabling processes and products to be re-engineered, optimised, recombined in different ways, managed, and executed more efficiently and automatically.

In essence, ‘telco disaggregation’ is a term that describes a moment in time at which telecoms technology, organisations, value chains and processes are being broken up into their component parts and re-engineered, under the impact of computerisation and its synonyms: digitisation, softwarisation, virtualisation and cloud.

This is part of a new wave of societal computerisation / digitisation, which at STL Partners we call the Coordination Age. At a high level, this can be described as ‘cross-domain computerisation’: separating out processes, services and functions from multiple areas of technology, the economy and society – and optimising, recombining and automating them (i.e. coordinating them), so that they can better deliver on social, economic and environmental needs and goals. In other words, this enables scarce resources to be used more efficiently and sustainably in pursuit of individual and social needs.

NFV has computerised the network; telco cloud native subordinates it to computing

In respect of the telecoms industry in particular, one could argue that the first wave of virtualisation (NFV and SDN), which unfolded during the 2010s, represented the computerisation and digitisation of telecoms networking. The focus of this was internal to the telecoms industry in the first instance, rather than connected to other social and technology domains and goals. It was about taking legacy, physical networking processes and functions, and redesigning and reimplementing them in software.

Then, the second wave of virtualisation (cloud-native – which is happening now) is what enables telecoms networking to play a part in the second wave of societal computerisation more broadly (the Coordination Age). This is because the different layers and elements of telecoms networks (services, network functions and infrastructure) are redefined, instantiated in software, broken up into their component parts, redistributed (logically and physically), and reassembled as a function of an increasing variety of cross-domain and cross-vertical use cases that are enabled and delivered, ultimately, by computerisation. Telecoms is disaggregated by, subordinated to, and defined and controlled by computing.

In summary, we can say that telecoms networks and operations are going through disaggregation now because this forms part of a broader societal transformation in which physical processes, functions and systems are being brought under the control of computing / IT, in pursuit of broader human, societal, economic and environmental goals.

In practice, this also means that telcos are facing increasing competition from many new types of actor, such as:

  • Computing, IT and cloud players
  • More specialist and agile networking providers
  • And vertical-market actors – delivering connectivity in support of vertical-specific, Coordination Age use cases.

 

Table of contents

  • Executive Summary
    • Three critical success factors for Coordination Age telcos
    • What capabilities will remain distinctively ‘telco’?
    • Our take on three pioneering cloud-native telcos
  • Introduction
    • The telco business is being disaggregated
    • Telco disaggregation is a by-product of computerisation
  • The disaggregated telco landscape: Where’s the value for telcos?
    • Is there anything left that is distinctively ‘telco’?
    • The ‘core’ telecoms business has evolved from delivering ubiquitous communications to enabling ubiquitous computing
    • Six telco-specific roles for telecoms remain in play
  • Radical telco disaggregation in action: AT&T, DISH and Rakuten
    • Servco, netco or infraco – or a patchwork of all three?
    • AT&T Network Cloud sell-off: Desperation or strategic acuity?
    • DISH Networks: Building the hyperscale network
    • Rakuten Mobile: Ecommerce platform turned cloud-native telco, turned telco cloud platform provider
  • Conclusion

Enter your details below to request an extract of the report

2020 in review and focus on North America: How should telcos do cloud?

Tenth update of the Telco Cloud Tracker

This report accompanies the tenth release of STL Partners’ ‘Telco Cloud Tracker’ database. This contains data on deployments of NFV (Network Functions Virtualisation), SDN (Software Defined Networking) and cloud-native network functions (CNFs) in the networks of the leading telcos worldwide. This analytical report focuses on trends in North America, set in global context.

Download the report extract

Scope and content of the Tracker

The data in the tenth update covers the period up to the end of January 2021, although reference is made in the report to events and deployments after that date. The data is drawn predominantly from public-domain information contained in news releases from operators and vendors, along with reputable industry media. However, it also includes a smaller set of deployment data disclosed to us confidentially by operators and vendors. This information is added to the aggregate data sections of the ‘Tracker’ spreadsheet, which do not refer to the specific solutions supplied or the operators where they were deployed.

We apply the term ‘deployment’ to refer to the total set of virtual network functions (VNFs), CNFs or SDN technology, and their associated management software and infrastructure, deployed at an operator – or at one or more of an operator’s opcos or natcos – in order to achieve a defined objective or support particular services (in the spreadsheet, we designate these as the ‘primary purpose’ of the deployment). For example, this could be:

  • to implement a virtualised mobile core
  • to launch a software-defined WAN (SD-WAN) service
  • or to construct a ‘telco cloud’ or NFV infrastructure (NFVi): a cloud infrastructure platform on which virtualised network services can be introduced and operated.

Accordingly, some of the deployments contained in the database comprise multiple elements, which are listed separately, including details about the category of NFV / SDN / CNF, and vendor and product name where known.

In addition to these mainly public-domain deployments, there are many non-publicised deployments that are inevitably omitted from the ‘Tracker’. However, the ever-growing ‘Tracker’ database now constitutes a considerable body of research that in our view offers a reliable snapshot of the overall market and the main trends in the evolution of telco cloud. In addition, as the ‘Tracker’ contains details only of deployments in live, commercial telco networks (either completed or in progress), this provides a useful corrective to the hype of some vendors’ pronouncements about agreements with operators, which often relate only to collaboration arrangements and preliminary trials, rather than commercial roll-outs.

The one exception to this rule of including only deployments that are implemented to support commercial services is a limited set of data on some of the current live network trials of open and / or virtual RAN (vRAN). The reason for making this exception is the very high level of interest currently in open RAN.

In terms of the telcos included, we limit the database mainly to Tier-One international and national telecoms operators, along with national fixed and mobile operators in smaller markets. For subsequent updates, we may expand the range and types of service providers included, because telco cloud is opening up opportunities for new players to provide cloud- and CNF-based connectivity and related services that are competing strongly with classic telco services.

SD-WAN in focus

In this update of the Tracker we have included a deep dive on SD-WAN, which was one of the main early drivers of SDN/NFV deployments, particularly among North American operators. It is worth exploring in more detail because, as it evolves into an increasingly cloud-centric and cloud-native service, it is emerging as another battleground between operators, hyperscalers and vendors.

5G is driving deployments – but will it drive business model change?

This is the first update to the ‘Telco Cloud Tracker’ in 2021, which provides an opportunity to review 2020 and discuss the key trends in 2021.

Despite the global pandemic, the pace of virtualised network function (VNF) deployments has continued at a strong level.

Total deployments by region, 2016 to 2021

Our projection is that the final number of deployments in 2020 will be at around the same level as 2019 (182 in total). Many live deployments are confirmed some time after the event, swelling the totals for previous years. Accordingly, some of the deployments currently recorded as ‘in progress’ will be added to the tally for 2020.

5G core dominates the scene but is done largely via single-vendor, ‘vertical’ NFV

The main driver of deployments in 2020 was 5G network launches around the world, particularly in the second half of the year. This meant that many Non-standalone (NSA) 5G cores – the platform supporting almost all live 5G networks – also went live, as is illustrated below:

 Deployments by leading network function, 2016 to 2021

We recorded 76 completed deployments of NSA cores in 2020, up from 56 in 2019. A further ten deployments were either completed or pending in the first quarter of 2021.

Table of content

  • Executive Summary
    • 5G core drives deployments
    • SD-WAN: Telco value moves from the WAN to the edge
    • The industry is facing an existential question: How should telcos do cloud?
    • Conclusion from North America analysis: Can a brownfield MNO be more cloud-native than a greenfield one?
  • Introduction
    • Tenth update of the Telco Cloud Tracker
    • Scope and content of the Tracker
    • SD-WAN in focus
  • 5G is driving deployments – but will it drive business model change?
    • 5G core dominates the scene but is done largely via single-vendor, ‘vertical’ NFV
    • The industry faces an existential question: how should telcos do cloud?
    • Focus on North America: four divergent answers to the existential question
  • SD-WAN: While WAN moves to the cloud, new software-defined value migrates to the edge
    • SD-WAN was one of the success stories of the first phase of SDN / NFV
    • SD-WAN has been largely made in America
    • Changes accelerated by Covid favour SD-WAN vendors over telcos – but telcos retain strengths in key areas
    • Main opportunities currently for telcos in SD-WAN, and challenge from vendors
    • ‘SD’ moves towards the edge, while ‘WAN’ moves to the cloud
  • Conclusion: Can a brownfield MNO be more cloud-native than a greenfield one?

 

Download the report extract