Making Sense of the Telco Cloud

In recent years the cloudification of communication networks, or “telco cloud” has become a byword for telecom modernisation. This Telecoms.com Intelligence Monthly Briefing aims to analyse what telcos’ transition to cloud means to the stakeholders in the telecom and cloud ecosystems. Before exploring the nooks and crannies of telco cloud, however, it is worthwhile first taking an elevated view of cloud native in general. On one hand, telco cloud is a subset of the overall cloud native landscape, on the other, telco cloud almost sounds an oxymoron. Telecom operator’s monolithic networks and cloud architecture are often seen as two different species, but such impressions are wrong.

(Here we are sharing the opening section of this Telecoms.com Intelligence special briefing to look into how telco cloud has changing both the industry landscape and operator strategies.

The full version of the report is available for free to download here.)

What cloud native is, and why we need it

“Cloud native” have been buzz words for a couple of years though often, like with many other buzz words, different people mean many different things when they use the same term. As the authors of a recently published Microsoft ebook quipped, ask ten colleagues to define cloud native, and there’s good chance you’ll get eight different answers. (Rob Vettor, Steve “ardalis” Smith: Architecting Cloud Native .NET Applications for Azure, preview edition, April 2020)

Here are a couple of “cloud native” definitions that more or less agree with each other, though with different stresses.

The Cloud Native Computing Foundation (CNCF), an industry organisation with over 500 member organisations from different sectors of the industry, defines cloud native as “computing (that) uses an open source software stack to deploy applications as microservices, packaging each part into its own container, and dynamically orchestrating those containers to optimize resource utilization.”

Gabriel Brown, an analyst from Heavy Reading, has a largely similar definition for cloud native, though he puts it more succinctly. For him, cloud native means “containerized micro-services deployed on bare metal and managed by Kubernetes”, the de facto standard of container management.

Although cloud native has a strong inclination towards containers, or containerised services, it is not just about containers. An important element of cloud native computing is in its deployment mode using DevOps. This is duly stressed by Omdia, a research firm, which prescribes cloud native as “the first foundation is to use agile methodologies in development, building on this with DevOps adoption across IT and, ideally, in the organization as well, and using microservices software architecture, with deployment on the cloud (wherever it is, on-premises or public).”

Some would argue the continuous nature of DevOps is as important to cloud native as the infrastructure and containerised services. Red Hat, an IBM subsidiary and one of the leading cloud native vendors and champions for DevOps practices, sees cloud native in a number of common themes including “heavily virtualized, software-defined, highly resilient infrastructure, allowing telcos to add services more quickly and centrally manage their resources.”

These themes are aligned with the understanding of cloud native by Telecoms.com Intelligence, and this report will discuss cloud native and telco cloud along this line. (A full Q&A with Azhar Sayeed, Chief Architect, Service Provider at Red Hat can be found at the end of this report).

The main benefits of cloud native computing are speed, agility, and scalability. As CNCF spells it out, “cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil.”

To adapt such thinking to the telecom industry, the gains from migrating to cloud native are primarily a reflection of, and driven by, the increasing convergence between network and IT domains. The first candidate domain that cloud technology can vastly improve on, and to a certain degree replace the heavy infrastructure, is the support for the telcos’ own IT systems, including the network facing Operational Support Systems and customer facing Business Support System (OSS and BSS).

But IT cloud alone is far from what telcos can benefit from the migration to cloud native. The rest of this report will discuss how telcos can and do embark on the journey to cloud native, as a means to deliver true business benefits through improved speed, agility, and scalability to their own networks and their customers.

The rest of the report include these sections:

  • The many stratifications of telco cloud
  • Clouds gathering on telcos
  • What we can expect to see on the telco cloud skyline
  • Telco cloud openness leads to agility and savings — Q&A with Azhar Sayeed, Chief Architect, Service Provider, Red Hat
  • Additional Resources

The full version of the report is available for free to download here.

Dish adds more credibility to OpenRAN with Mavenir selection

Mavenir has boasted of signing new US entrant Dish as its latest customer, as the emerging telco sets its sights on the most enviable of tasks; a greenfield network deployment.

Like Rakuten in Japan, Dish is able to embrace the OpenRAN movement like few others can around the world. Without being inhibited by legacy technologies or traditional operational models, the Dish team can build a network from scratch, without making compromises or concessions. It is a dream-come-true for any network engineers; the opportunity to deploy a network exactly as you would want to.

“The open and intelligent architecture of our greenfield network will give us the ability to source a diverse technology ecosystem, including US-based solution providers,” said Marc Rouanne, Chief Network Officer at Dish, and former Nokia executive.

“Mavenir will help us lay the foundation for an innovative software-defined network with the flexibility, intelligence and scalability to deliver applications that will redefine the US wireless industry.”

As part of the agreement, Mavenir will provide Dish with a cloud-native OpenRAN software, which the new telco hopes will underpin the US’ first software-defined 5G wireless broadband network.

While the obvious and most proclaimed benefit of the OpenRAN ecosystem is a wider array of suppliers, all promising there is no such thing as vendor lock-in, another significant upside to the OpenRAN movement is on the operational side of the business.

According to Tareq Amin, Chief Technology Officer at Rakuten, commoditised hardware and open software can lead to a 40% reduction in CAPEX costs for network deployment, but it is in the operations team that the real benefits can be seen. Amin has said the operations team should not exceed 350 employees when the entire network has been deployed, compared to thousands which are employed by rivals.

This is a considerable cost saving for Rakuten, which has allowed it to create 5G tariffs to challenge the status quo. At 2,980 Yen per month, Rakuten is offering mobile connectivity services at roughly half the price of competitors. Customers will have to wait for the full network deployment to experience the full wonder of cut-price Rakuten data, but this is an incredibly disruptive move.

The prospect of pricing disruption in the US is a very interesting one, as it is one of the most expensive markets in the developed world for data.

Market Average Revenue Per User (ARPU)
USA 30.85
UK 16.00
Italy 11.55
Netherlands 13.48
Australia 22.65
Canada 36.67

2020 ARPU estimates from Omdia’s World Information Series (USD – $)

Although there has been much protest over the formation of Dish as a replacement for Sprint in the US mobile industry, this is a positive sign. There are of course plenty of hurdles which need to be overcome, however the construction of an OpenRAN network presents the opportunity for Dish to be incredibly disruptive on pricing when it is launched.

Dish only exists thanks to the merger of Sprint and T-Mobile US, though the major opposition to this transaction was on the grounds of competition. Firstly, critics questioned whether moving to three major MNOs was in the best interest of the consumer, and secondly, opponents wondered whether Dish would be able to create an offering which would match more established rivals.

Eyes should be kept on Japan to see whether Rakuten is a disruption or a minor irritation, but the promise of OpenRAN has been very glorious to date.

While the promise of starting from scratch is very attractive to a telco, Heavy Reading Lead Analyst Gabriel Brown notes, that is a significant issue as well. Starting from nothing means there is nothing there and in a country the size of the US, building a nationwide 5G network is no simple task.

One concession forced on Sprint/T-Mobile US by the Department of Justice was to offer Dish an attractive MVNO style agreement for seven years. This was one element bundled into the $5 billion deal to purchase the Boost prepaid service from Sprint. During this seven-year period, Dish will have to build its own 5G network, a monumental task according to Light Reading’s Mike Dano.

Firstly, work has to stop on the NB-IOT network it was currently deploying. Secondly, Dish has got to find the cash to pay for the 5G network. Thirdly, work will begin on the core network, which Dish executives say will be completed within Year One. Finally, comes the access network.

As part of the agreement with the Department of Justice in greenlighting the Sprint/T-Mobile US merger, Dish will have to option to purchase any cell sites which the merger duo plan to decommission thanks to overlap. Outside of these purchases, Dish will have to deploy backhaul and radio equipment into the major cities, with a promise 20% of the US population will be covered by June 2022.

Thanks to the software-defined ambitions of Dish, a significant chunk of this deployment work can be saved, due to the weightier role of the data centre. That said, the US is a country with a population of 328 million spread over 9,147,590 km2, it is 3,937% larger than the UK. As much as we can talk about the advantages an OpenRAN network will offer Dish over its rivals, it will have to build it first.

An optimist will point towards a future where the OpenRAN-powered Dish can offer disruptive pricing strategies, similar to what has been done in India and will be done in Japan, to turn the US telco market on its head. The pessimist in the group will point out this is a company which has never built a network before, with a CTO who has vendor experience not telco, and a country which is monstrously large, geographically diverse and bureaucratically varied.