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

The Telco Cloud Manifesto

Telco cloud: A key enabler of the Coordination Age

The Coordination Age is coming

As we have set out in our company manifesto, STL Partners believes that we are entering a new ‘Coordination Age’ in which technological developments will enable governments, enterprises, and consumers to coordinate their activities more effectively than ever before. The results of better and faster coordination will be game-changing for society as resources are distributed and used more effectively than ever before leading to substantial social, economic, and health benefits.

A critical component of the Coordination Age is the universal availability of flexible, fast, reliable, low-latency networks that support a myriad of applications which, in turn, enable a complex array of communications, decisions, transactions, and processes to be completed quickly and, in many cases, automatically without human intervention.  The network remains key: without it being fit for purpose the ability to match demand and supply real-time is impossible.

How telecoms can define a new role

Historically, telecoms networks have been created using specialist dedicated (proprietary) hardware and software.  This has ensured networks are reliable and secure but has also stymied innovation – from operators and from third-parties – that have found leveraging network capabilities challenging.  In fact, innovation accelerated with the arrival of the Internet which enabled services to be decoupled from the network and run ‘over the top’.

But the Coordination Age requires more from the network than ever before – applications require the network to be flexible, accessible and support a range of technical and commercial options. Applications cannot run independently of the network but need to integrate with it. The network must be able to impart actionable insights and flex its speed, bandwidth, latency, security, business model and countless other variables quickly and autonomously to meet the needs of applications using it.

Telco cloud – the move to a network built on common off-the-shelf hardware and flexible interoperable software from best-of-breed suppliers that runs wherever it is needed – is the enabler of this future.

 

Table of Contents

  • Executive Summary
  • Telco cloud: A key enabler of the Coordination Age
    • The Coordination Age is coming
    • How telecoms can define a new role
  • Telco cloud: The growth enabler for the telecoms industry
    • Telecoms revenue growth has stalled, traffic has not
    • Telco cloud: A new approach to the network
    • …a fundamental shift in what it means to be an operator
    • …and the driver of future telecoms differentiation and growth
  • Realising the telco cloud vision
    • Moving to telco cloud is challenging
    • Different operator segments will take different paths